So, given that all instructions were followed to the letter on my Canadian ROW Thinkpad tablet and when I try to boot into the recovery kernel it just reboots again, any ideas?
Yes, the tablet was rooted.
Yes, I corrected the filename.
Yes, my output matches the output indicated by others in this thread.
Yes I tried both a reboot via power cycle and reboot via ROM Manager "reboot into recover"
CODE REMOVED
Reboot via power button.
Lenovo logo shows up, hit Vol+
"Booting Recovery Kernal Image" shows up in the top corner
Tablet goes black and vibrates again(indicating a reboot)
Lenovo logo appears again.
I can repeat the above steps at this point and the same happens. if I don't, it boots normally.
CODE removed
Any help is greatly appreciated.
Who got it working and on what type of model(16, 32, 64 GB) and who didn't get it working and on what type of model?
Who got it working and on what type of model(16, 32, 64 GB) and who didn't get it working and on what type of model?
The sizes aren't different, 4.29megs is 4452352 bytes.
I'm running 0074 ROW on model 1838CTO.
And if someone has directions for undoing the steps so I can restore the original recovery image for now I would be grateful
I did backup the file...but didn't we also overwrite a partition via the DD command? Is the .sh file all there was to restoring the original recovery mode?
---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------
I think we can safely say the CWR port doesn't work on ROW.
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:e1f132b3fc2b0f8a6ba8479e4a98e6191d5dbe0a; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3158016:6f7d9da82d8b610a8e86b9601f270e56a317e754 EMMC:/dev/block/mmcblk0p1 e3f40337cc1c778d8d5c55ce67faf42f44e2f170 3512320 6f7d9da82d8b610a8e86b9601f270e56a317e754:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
tpt 16gb, sd 32gb
Restore failed /data folder
I've tried to flash the zip that correct the /sdcard problem for Transformer.
Didn't work
Wipe erase sdcard data and backup have problem of md5 (restore is skipped because md5 check failed)
This is the original install-recovery.sh file
Code:#!/system/bin/sh if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:e1f132b3fc2b0f8a6ba8479e4a98e6191d5dbe0a; then log -t recovery "Installing new recovery image" applypatch EMMC:/dev/block/mmcblk0p2:3158016:6f7d9da82d8b610a8e86b9601f270e56a317e754 EMMC:/dev/block/mmcblk0p1 e3f40337cc1c778d8d5c55ce67faf42f44e2f170 3512320 6f7d9da82d8b610a8e86b9601f270e56a317e754:/system/recovery-from-boot.p else log -t recovery "Recovery image already installed" fi
Note this line:
applypatch EMMC:/dev/block/mmcblk0p2:3158016:6f7d9da82d8b610a8e86b9601f270e56a317e754 EMMC:/dev/block/mmcblk0p1 e3f40337cc1c778d8d5c55ce67faf42f44e2f170 3512320 6f7d9da82d8b610a8e86b9601f270e56a317e754:/system/recovery-from-boot.p
Could the other blocks be backups of former recoveries?
brw------- root root 7, 1 2012-01-24 00:57 loop1
brw------- root root 7, 2 2012-01-24 00:57 loop2
brw------- root root 7, 3 2012-01-24 00:57 loop3
brw------- root root 7, 4 2012-01-24 00:57 loop4
brw------- root root 7, 5 2012-01-24 00:57 loop5
brw------- root root 7, 6 2012-01-24 00:57 loop6
brw------- root root 7, 7 2012-01-24 00:57 loop7
brw------- root root 179, 0 2012-01-24 00:57 mmcblk0
brw------- root root 179, 1 2012-01-24 00:57 mmcblk0p1
brw------- root root 259, 2 2012-01-24 00:57 mmcblk0p10
brw------- root root 179, 2 2012-01-24 00:57 mmcblk0p2
brw------- root root 179, 3 2012-01-24 00:57 mmcblk0p3
brw------- root root 179, 4 2012-01-24 00:57 mmcblk0p4
brw-rw---- root system 179, 5 2012-01-24 00:57 mmcblk0p5
brw------- root root 179, 6 2012-01-24 00:57 mmcblk0p6
brw------- root root 179, 7 2012-01-24 00:57 mmcblk0p7
brw------- root root 259, 0 2012-01-24 00:57 mmcblk0p8
brw------- root root 259, 1 2012-01-24 00:57 mmcblk0p9
brw------- root root 179, 8 2012-01-24 00:57 mmcblk1
brw------- root root 179, 9 2012-01-24 00:57 mmcblk1p1
#cat /proc/partitions
major minor #blocks name
7 0 9216 loop0
179 0 31259648 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 786432 mmcblk0p3
179 4 921600 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 143360 mmcblk0p8
259 1 20480 mmcblk0p9
259 2 28811264 mmcblk0p10
179 8 16186368 mmcblk1
179 9 16182272 mmcblk1p1
#
What's output of cat /proc/partitons on different versions of tab?
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# cat /proc/partitions
major minor #blocks name
7 0 9216 loop0
179 0 31259648 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 786432 mmcblk0p3
179 4 921600 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 143360 mmcblk0p8
259 1 20480 mmcblk0p9
259 2 28811264 mmcblk0p10
179 8 30355456 mmcblk1
179 9 30351360 mmcblk1p1
#
adb push cwr_ventana_2.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/cwr_recovery_2.img of=/dev/block/mmcblk0p1
the CWM images are down does anyone have them and could please reuplaod them?
I can compile ROW versions with my kernel. Can you tell me what steps you took to exclude /data/media(I'm quite new at this)?
Also, are your config files uploaded somewhere for the 32 and 64 gig models(I can generate only for 16GB at the moment)?