Compiled ROW CWR image and ROW diff discussion

---

UPDATE(Feb 07, 2012): Updating this with most recent info and installation instructions:


ROW 16GB with /data/sdcard fix
http://everyrandom.com/files/downloa...ery_row_16.img

ROW 32GB with /data/sdcard fix
http://everyrandom.com/files/downloa...ery_row_32.img

ROW 64GB with /data/sdcard fix
http://everyrandom.com/files/downloa...ery_row_64.img


Again, use at your own risk. 32GB and 64GB versions have not been tested.


NOTE: Backup has been tested, but recovery hasn't, though I'd be surprised if it didn't. This is a USE AT YOUR OWN RISK image. Also, I noticed my tablet rebooted once or twice while attempting to backup. This was likely due to the 9% battery indicator, but I figure I'd warn you just in case. If you leave your tablet to backup and you get back to it and you see your launcher unlock screen, it rebooted and likely didn't finish so you'll have to try again(again, I'm pretty sure this was just due to me having run down my battery).


WARNING: The following assumes you haven't installed any CWR image yet. If you've already installed CWR successfully, follow the 'Update Steps'.
Installation Steps:

adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1

Uninstallation Steps:

adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh 
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1

Update Steps:

adb push recovery_ventana_row16.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/dev/block/mmcblk0p1 of=/data/local/recovery_backup_image.img
dd if=/data/local/recovery_ventana_row16.img of=/dev/block/mmcblk0p1

If CWR randomly reboots on you when you either try to do a backup or simply stay on the menu too long, try the following(thanks stewarta):

• Boot into CWR. Then select to reboot the device(not "Reboot recovery", just the normal reboot).
• Allow it to boot into full Android.
• Reboot the device again and re-enter CWR. It should no longer be rebooting.

I don't know why the above happens or fixes it. If it doesn't work for you, please do the following:

• Boot into CWR. Either wait at the menu screen or attempt a backup(we want to provoke a reboot)
• On reboot, hit Vol+ to enter CWR again.
• Select 'Advanced'.
• Select 'report recovery'. It will tell you at the bottom where the log is stored. Make a note of it.
• Boot into full Android and use your favourite file manager to get the log. Paste its contents in this thread.

And once again thanks to Koshu, logxen and jcase and everyone else involved. They did most of the work. I mostly just hit "make".
____________________________________

So with that out of the way:

The kernel is the only change between jcase's port and the ROW version. The BuildConfig and such are untouched.

So why does it work? I would imagine a recovery image would be beyond caring about region of even the kernel version of the main OS. I can't imagine they'd have altered the hardware between builds, especially as ROW merits as much attention as bundling Canada and Berlin...

So, any ideas as to what could cause the difference? Could it be the nvflash signing keys? Could there be a driver inconsistency? Anyone have any ideas on how to troubleshoot at that level seeing as it doesn't look like Android even logs anything that early in the boot process.

Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.

Originally Posted by fhing

Many thanks to realyst2k and every one made this work.
Just wondering can we replace the ROW rom with the US rom in CWR? The lenovo ftp already has a US image.

I didn't do anything but make using the ROW kernel extracted from my tablet. Koshu and jcase deserve those thanks more than I.

As far as a US image, go to the following post. Koshu has US CWR images for all models.


http://forum.xda-developers.com/show...&postcount=106

Once again thank you realyst2k for compiling CWR for ROW.
I have TPT ROW 16GB. I backuped with no problem. Only one question, when backuping /data folder it skips /data/media folder which is internal memory same as /mnt/sdcard. From one side it's OK because it can contain up to 10G data and it would be hard to backup it, but from other side resetting to factory defaults also deletes /mnt/sdcard and so you need backup it also. I am little confused?!?!?! What is the situation in other tablets with internal storage?

It skips that mountpoint on purpose. I believe this is how the Transformer does it too. The reasoning aside from potentially gigantic backups and recoveries, is that it can also prevent a proper backup since it could easily overpower the filesystem on some SD cards(especially if you consider the 32GB model).

It's not needed in any case. CWR is made to do a NAND backup, which are your OS files and such. You can use Titanium Backup if you need to backup your media.

@realyst2k:
(SOLVED)

Originally Posted by stewarta

@realyst2k:
I couldn't get this to work:


I followed the UPDATE steps but even though the file permissions are okay (rw-rw-rw) it could not read the file at the last step. Probably something simply ....

Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).

If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.

If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).

Originally Posted by realyst2k

Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).

If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.

If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).

Thanks for the speedy reply. That was the first thing I checked .... the second was that I can still do Nand backups ... and I can. I'll copy it into the directory and try that command line again.

---------- Post added at 03:31 AM ---------- Previous post was at 02:54 AM ----------

Originally Posted by realyst2k

Make sure the image file actually is in your /data/local directory(you can use a file manager like root explorer).

If it's named differently(remember, it's case sensitive), adjust the name in the dd command accordingly.

If it isn't there, put it there(again, you can use root explorer if you have trouble using the the adb push command).

@realyst2k: Guess what it was .... the download file name is ventana_recovery_row_32.img. Compare that with the command line below ...

dd if=/data/local/recovery_ventana_row_32.img of=/dev/block/mmcblk0p1

So that was never going to work until I renamed the file. Duh! Boots into CWR, so I did my usual trick of booting into CWR, doing nothing and booting back into Android OS. Now back in CWR and doing a Nandroid backup without any issues at all. So thank you once again.
Might uninstall CWR over Easter and get OTA2. Perhaps not ... might just wait for ICS in May/June.

OTA 2 and Root with CWR

---

@realyst2k Being impatient, I decided to rename the install-recovery.sh and the install-recovery.sh.forrecovery and install the OTA and see what was what.
It installed fine. I've lost root, so I will have a go at using the original method of rooting the TPT. Oddly, Root Explorer works, but SuperUser (chainsdd) is not logging this fact. NSTools seems to work as well (reports the scheduler is Noop).
Anyway, long story short, I will report more tomorrow. When I have more time.
Happy Easter.

OTA2 = No Root

---

(SOLVED)