We have moved ahead of the TWRP 22.214.171.124 originally available in orig-development, to 126.96.36.199, and eventually to 188.8.131.52 too. Enjoy!
What is aw3som3?
Developers have long tried to sqeeze in ROMs into legacy devices with low internal memory, and one of the ways to do this was by using custom tailored mtd_parts, which gave the kernel a partition table to use, with resized partitions. This was widely used on many devices like the HTC G1, MT3G, Hero, Evo4G, Desire, etc.
While that was a viable option for the HTC Pico, a small "problem" that popped up was that different phones have different NAND Devices, with different partition tables and pagesizes. Incase the modified custom mtd_parts even accidentally touched the boot partition, or has been offset'ed out of the available space, a partition would be lost.
As a solution, dynamically obtain 32 mB from userdata partition, and 48 mB from the cache partition, and hax the partition table as soon as the information is got from ATAG. This should make this method work on *almost* all Pico's out there, which have partition layouts as misc:recovery:boot:system:cache:userdata:devlog and partitions in the order misc:rec..cache:devlog:userdata.
original layout : recovery:boot:system:cache:devlog:userdata:misc
new layout : recovery:boot:misc:devlog:userdata:cache:system
In case you want to modify any of the partition size defines, there are three defines, CACHE_SIZE_LEAVE, USERDATA_SIZE_LEAVE, and DEVLOG_SIZE_LEAVE. This, will leave that much mB as defined, and take the rest, put it in system partition. The default defines are: 8, 4 and 1 respectively.
You may clone this repo, and follow the following steps:
- download and compile kernel from android-4.4-recovery branch from https://github.com/thewisenerd/android_kernel_htc_pico
- put compiled zImage (arch/arm/boot/zImage) in root directory (i.e. cloned directory)
- run the following command to repack recovery ./repack.sh
- output recovery would be in output/recovery.img
- TWRP 184.108.40.206: http://forum.xda-developers.com/show...&postcount=125
- TWRP 220.127.116.11: http://forum.xda-developers.com/show...&postcount=108(26 sep 2014)
- Modified TWRP 18.104.22.168: http://forum.xda-developers.com/show...&postcount=106(14 sep 2014)
- Modified TWRP 22.214.171.124: http://forum.xda-developers.com/show...&postcount=104(11 sep 2014)
- Modified TWRP 126.96.36.199: http://forum.xda-developers.com/show...4&postcount=97 (05 sep 2014)
- Modified TWRP 188.8.131.52: http://forum.xda-developers.com/show...3&postcount=69 (09 Aug 2014)
- Modified TWRP 184.108.40.206: http://forum.xda-developers.com/show...0&postcount=65 (08 Aug 2014)
- Modified TWRP 220.127.116.11: http://forum.xda-developers.com/show...1&postcount=58 (30 Jul 2014)
- Modified TWRP 18.104.22.168 (resized): http://forum.xda-developers.com/show...40&postcount=6
- Modified TWRP 22.214.171.124: http://d-h.st/I4L
Kernel: You may use CodyKernel or the kernel provided by your ROM's developer that supports aw3som3.
Q: How to use?
- Wipe the system, data and cache partition.
- fastboot flash the given recovery.img.
- wipe the system, data and cache partitions, again. preferably use flash_erase on the partitions.
- flash your preferred ROM
- flash the given kernel, *with* aw3som3
- you're good to go!
you can get the patches here:
I've moved all the partition re-laying, resizing, etc, to a separate file, in drivers/misc, which should help keep clean the nand_partitions.c file, and we would have to worry only about one file, and related code. It also means that awesom3 is reduced to one patch
awesom3, Tool/Utility for the HTC Pico (Explorer)
Last Updated 2014-10-21