[WIP] Ideapad K1 CWM recovery port

---

Greetings,

I am looking for assistance trying to port CWM recovery to the Lenovo K1.

Where I'm At
I have compiled CWM Recovery from the source and have successfully flashed it to the device with working buttons. The recovery can mount all partitions except /misc. I have successfully flashed update.zip's, and verified the files were in place via adb. The problem is once I boot into CWM (Even if I don't flash anything) I cannot boot back to the OS, without reflashing everything

For example:
1. I flash the Chinese rom with my recovery.img in place via nvflash
2. Once it boots I move a blank update.zip & update.xml to the Download dir on the internal storage
3. Reboot
4. Automatically tries to go into Recovery
5. Get an error image (Blank update.zip wouldn't flash of course). Hold down Power Button until device powers off.
6. Power on and device goes right into CWM.
At this point even if I just reboot the device goes right back into CWM. The recovery is very functional, I am able to flash update.zip's, mount almost all partitions, and access via adb.

According to djmwj there needs to be an update.zip and update.xml file in the /sdcard/Download dir to boot into recovery. These can be blank files. They are deleted on every reboot, so you have to put them back each time.
-This only works for me on the Chinese rom

Partitions
/dev/block/mmcblk0p1 - /recovery
/dev/block/mmcblk0p2 - /boot
/dev/block/mmcblk0p3 - /system
/dev/block/mmcblk0p4 - /cache
/dev/block/mmcblk0p5 - ?? 2MB
/dev/block/mmcblk0p6 - blob
/dev/block/mmcblk0p7 - /data
/dev/block/mmcblk0p8 - /data/temp
/dev/block/mmcblk1p1 - /sdcard

recovery.fstab
# mount point fstype device [device2]

/boot mtd /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p7 /dev/block/mmcblk0p8
/mis mtd ??
/recovery mtd /dev/block/mmcblk0p1
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p3
/sd-ext yaffs2 ??


Please let me know if you would like a copy of the recovery.img or the modified files from the CWM source. Also if anyone has any suggestions to get it rebooting to the OS. If I can get that working it should be ready for an initial release.

Would this help?
http://rootzwiki.com/topic/13407-alp...ck-rooted-rom/

He seems to have it flashing and booting a rooted version of the stock rom. He mentions some issues but doesn't list them (unless you count not having lenovo market as an issue.)

I'm waiting for this to root my K1, any update?

---------- Post added at 12:54 PM ---------- Previous post was at 12:53 PM ----------

Originally Posted by gallahad2000

Would this help?
http://rootzwiki.com/topic/13407-alp...ck-rooted-rom/

He seems to have it flashing and booting a rooted version of the stock rom. He mentions some issues but doesn't list them (unless you count not having lenovo market as an issue.)

He is actually the same guy.

Originally Posted by leo_bsb

He is actually the same guy.

That's what I get for not paying any attention. I think he's at the same place as everyone else: They've got a rooted rom but need a copy of the userdata img or all of the original .apks to restore all of the third-party apps.

He just posted Alpha 2.0!

*Edit: I helped him pull the lenovo .apks from my stock K1, so there may be another update soon*

I think I can help you. If you want to launch a recovery and you have root(#) then on the Lenovo you just issue this command "/system/bin/misc_command FOTA" and then reboot. It will launch CWM or the stock recovery. No need to make dummy update.zip files.

Take a look at http://forum.xda-developers.com/show...9&postcount=50

You should be able to download that tool, replace the recovery.img in the image folder with your CWM and then flash to 13_13_US. You'll have to comment (change) out the boot sequence so CWM doesn't get replaced on reboots. This is why it only works once for you and then you have to flash it again.

Also, if you get root. You should be able to dd back in the recovery blob without flashing which would work for one reboot and then it gets replaced again with stock.

So you could:
1. dd of=/dev/block/mmcblk0p1 if=/sdcard/Download/recovery.img
2. /system/bin/misc_command FOTA
3. reboot
Note: this assumes you have root and should launch CWM for you. However CWM will be replaced back with the stock recovery on the next reboot unless you comment out those commands in the start up.


Hope this helps, let me know,
TD

Thanks, but I already created an app/widget that reboots into recovery. I watched logcat while applying an OTA update to see what intent was called. The app basically puts a blank update.zip in place and calls the intent. This method does not cause you to reflash the recovery image each time. You reboot to recovery as many times as you would like.

All my work is posted over a rootzwiki

Originally Posted by khanning88

Thanks, but I already created an app/widget that reboots into recovery. I watched logcat while applying an OTA update to see what intent was called. The app basically puts a blank update.zip in place and calls the intent. This method does not cause you to reflash the recovery image each time. You reboot to recovery as many times as you would like.

All my work is posted over a rootzwiki

Nice, got a link for the download of CWM?

Originally Posted by timmyDean

Nice, got a link for the download of CWM?

http://rootzwiki.com/topic/13407-alp...-111029-build/