Hi guys. As for now booting into recovery directly will cause data partition zeroed. Now I figured out a (very twisted) hack to get it around:
1. Interchange the partition name of partition 7 and partiton 17 using parted.
Now old boot is new recovery, old recovery is new boot
2. Cold start will always enter recovery. By rebooting into "recovery", we can get into normal mode. Now no matter how messed-up the norm mode is, zeroing of data will never be triggered.
3. When flashing a zip containing a kernel, the installscript will ask to write the kernel file into "/dev/block/platform/msm_sdcc.1/by-name/boot". There are two ways to solve this:
a). Adjust install script to point to "by-name/recovery"
b). CWM/TWRP modify the softlink "by-name/boot", and redirect it into mmcblk0p7, the real boot partition.
4. Cold start will be longer and more troublesome, but we can modify CWM/TWRP to reboot automatically into normal mode unless the user intervened. Something like hroark13's homebutton trick can do it.
Extra finding: enter fastboot
I made a mistake of interchanging 7<->1 instead of 7<->17 at the first time, and fastboot magically showed up when I tried to boot into recovery.
So I did more research, and discovered that: as long as aboot can not find a partition called "recovery", or was feed in a wrong format, it will go into fastboot. So the easiest way is to rename "recovery" into something else, and change it back when we are done with fastboot.
I tried boot an normal kernel without loking patch, using "fastboot boot", and it will boot
.
Now with fastboot, developing and test will be much easier and in more rapid pace. And these hack may work more lg/other devices rather than F6. I think it will be awesome.
Do you guys think it is worth implementing on our ROMs?
1. Interchange the partition name of partition 7 and partiton 17 using parted.
Now old boot is new recovery, old recovery is new boot
2. Cold start will always enter recovery. By rebooting into "recovery", we can get into normal mode. Now no matter how messed-up the norm mode is, zeroing of data will never be triggered.
3. When flashing a zip containing a kernel, the installscript will ask to write the kernel file into "/dev/block/platform/msm_sdcc.1/by-name/boot". There are two ways to solve this:
a). Adjust install script to point to "by-name/recovery"
b). CWM/TWRP modify the softlink "by-name/boot", and redirect it into mmcblk0p7, the real boot partition.
4. Cold start will be longer and more troublesome, but we can modify CWM/TWRP to reboot automatically into normal mode unless the user intervened. Something like hroark13's homebutton trick can do it.
Extra finding: enter fastboot
I made a mistake of interchanging 7<->1 instead of 7<->17 at the first time, and fastboot magically showed up when I tried to boot into recovery.
So I did more research, and discovered that: as long as aboot can not find a partition called "recovery", or was feed in a wrong format, it will go into fastboot. So the easiest way is to rename "recovery" into something else, and change it back when we are done with fastboot.
I tried boot an normal kernel without loking patch, using "fastboot boot", and it will boot
.Now with fastboot, developing and test will be much easier and in more rapid pace. And these hack may work more lg/other devices rather than F6. I think it will be awesome.
Do you guys think it is worth implementing on our ROMs?
