awesom3: dynamic partition table resizing ~ twrp 2.8.0.0
- Thread starter thewisenerd
- Start date
-
- Tags
- development
Why the device boots automatically to recovery when its charging the battery while its turned off? Where I can disable this?
That's normal. Only stock and yannou recovery don't have that behavior
Sorry for asking again but no one answered and i really need this recovery(to flash omnirom) so can any1 help?
G
gauravrai
Guest
I was trying to install cm11 weekly 6 with latest aw3som3 twrp recovery but device is not booted. after flashing cm11, weekly fix, gapps....i did reboot. device rebooted with htc splash screen then it returned back to twrp recovery. any help?
Happened with me too! So reverted back to previous recovery.. Maybe it ain't working on *weak* Pico :/
Sent from my Explorer A310e using XDA Free mobile app
Not working on every device bro. Different phones have different partition sizes.. Maybe that's what messing...
Sent from my Explorer A310e using XDA Free mobile app
Flash the 30th July aw3som3 recovery and problem will be solved.
Sent from my HTC Explorer A310e using XDA Premium 4 mobile app
G
gauravrai
Guest
It's because the kernel has to be in sync with the recovery's partition allocation. Ask the ROM's OP, ie. kirmaniarslan, to merge in the patches with his kernel source. Apparently, his kernel sources aren't in sync with Cody Kernel, so, I can't do much about it.
G
gauravrai
Guest
As he left the weeklies development can you suggest us to use latest cody kernel. will it work?
omni rom build#8 help
hello i want to try omni rom build#8 i flashed aw3som3 recovery from here http://xdaforums.com/showpost.php?p=53704940&postcount=6 it worked for cm11 build#6 but when i flash omni rom build#8 with this recovery i end in bootloop i also flashed boot.img which is needed for omni rom to boot but still i face bootloop.
also in this recovery when i install rom it displays install zip successfully but when i do reboot it displays no os installed.
can any tell if latest aw3som3 recovery is needed for omni rom if yes please give link of latest aw3som3 recovery.
hello i want to try omni rom build#8 i flashed aw3som3 recovery from here http://xdaforums.com/showpost.php?p=53704940&postcount=6 it worked for cm11 build#6 but when i flash omni rom build#8 with this recovery i end in bootloop i also flashed boot.img which is needed for omni rom to boot but still i face bootloop.
also in this recovery when i install rom it displays install zip successfully but when i do reboot it displays no os installed.
can any tell if latest aw3som3 recovery is needed for omni rom if yes please give link of latest aw3som3 recovery.
the thing is this, everytime i flash this recovery it freezes at twrp logo and starts blinking, already done wipe before flashing recovery, tried to flash Yannou's recovery before flashing and the end result is always the same, is there any possible solution or i just can't flash this one?
try this method of mine http://xdaforums.com/showpost.php?p=53900614&postcount=457
thank me If I helped
try this method of mine http://xdaforums.com/showpost.php?p=53900614&postcount=457
thank me If I helped
Looooool, when i flashed it and tried the result was the same, stuck on the twrp logo and the screen started to blink, then i had a crazy idea to remove the sd card(only possible thing that could be making this blinking because i tried a lot of solutions) and guess what!?!? it finally started ahaha
Last edited:
updates to the recovery!
Download: http://www.mediafire.com/download/zg6zghinrw1d6ke/twrp_05_sep_2014.img
- updated sources to TWRP 2.7.1.0 (till 01 sep 2014)
- removed TW_EXCLUDE_SUPERSU := true
- removed TW_NO_EXFAT := true
Download: http://www.mediafire.com/download/zg6zghinrw1d6ke/twrp_05_sep_2014.img
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
33This started out as a little side project on the OmniROM threads, and it's about time some things are clarified, and what exactly done, is explained.
Currently, only a modified version of TWRP 2.7 recovery is available, and we *might* support other recoveries soon
We have moved ahead of the TWRP 2.7.0.0 originally available in orig-development, to 2.7.1.0, and eventually to 2.8.0.0 too. Enjoy!
What is aw3som3?
I've changed the partition table layout, without modifying the actual mtdblock<n>, thus no further fstab/ramdisk editing is required.
table: 0->misc::1->recovery::2->boot::3->system::4->cache::5->userdata::6->devlog
original layout : recovery:boot:system:cache:devlog:userdata:misc
new layout : recovery:boot:misc:devlog:userdata:cache:system
To developers:
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
Downloads:
- TWRP 2.8.0.0: http://xdaforums.com/showpost.php?p=56168368&postcount=125
[*] TWRP 2.8.0.0: http://xdaforums.com/showpost.php?p=55685051&postcount=108(26 sep 2014)
[*] Modified TWRP 2.8.0.0: http://xdaforums.com/showpost.php?p=55430289&postcount=106(14 sep 2014)
[*] Modified TWRP 2.8.0.0: http://xdaforums.com/showpost.php?p=55375649&postcount=104(11 sep 2014)
[*] Modified TWRP 2.7.1.0: http://xdaforums.com/showpost.php?p=55246774&postcount=97 (05 sep 2014)
[*] Modified TWRP 2.7.0.0: http://xdaforums.com/showpost.php?p=54709263&postcount=69 (09 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://xdaforums.com/showpost.php?p=54688800&postcount=65 (08 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://xdaforums.com/showpost.php?p=54484381&postcount=58 (30 Jul 2014)
[*] Modified TWRP 2.7.0.0 (resized): http://xdaforums.com/showpost.php?p=53704940&postcount=6
[*] Modified TWRP 2.7.0.0: 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?
A:- 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!
Sources
you can get the patches here:
PS#1: 0001-aw3som3-hax-the-partition-table.patch
PS#2: 0002-aw3som3-set-msm_nand_data.parts-later.patch
PS#3: 0003-aw3som3-rearrange-and-relay-the-partition-table.patch
PS#1 (26Sep'14):
0001-awesom3-hax-the-partition-table.patch
0002-awesom3-allow-a-128-mB-userdata.patch
XDA:DevDB Information
awesom3, Tool/Utility for the HTC Pico (Explorer)
Contributors
thewisenerd
Version Information
Status: Stable
Created 2014-10-21
Last Updated 2014-10-2121the recovery has been resized, hopefully. get another beta here: http://www.solidfiles.com/d/e6d39a02c4/recovery.img
hopefully, we're just a few commits away from a complete partition table rewrite... I've decided to move devlog to the beginning, then, a 4 mB cache (you shouldn't need more), and the rest for the /system partition. What about /data? sd-ext becomes /data partition by default. I posted a poll on the FB group and most of the people are clearly fed up with internal memory being very low hence, already using sd-ext by default, why "waste" the data partition?
This would stay in beta till some more time.
a new build of twrp should be out any time soon... the kernel, slimmered down to 1.8 mB without affecting actual functionality, *and* adding back support for ext2/3 and exfat and ntfs.
the recovery's size has been slimmered too, by modifying its ramdisk compression. you might not be much interested in all that, but you should see the change in recovery size from this build itself.
and finally, here's the boot.img: http://d-h.st/5jK
proof that it works (otherwise which no one's going to download anyways):
as we are going to use complete /data partition + some moar of cache partition, 112 +9a major update to the recovery.
i've changed the partition table layout, without modifying the actual mtdblock<n>, thus helping to keep first things first.
table: 0->misc::1->recovery::2->boot::3->system::4->cache::5->userdata::6->devlog
actual layout: recovery::boot::system::cache::devlog::userdata::misc
new layout: recovery::boot::misc::devlog::userdata::cache::system
Also, instead of taking 32 mB from userdata, 48 mB from cache, I've modified the logic a lil', thus, keeping 3 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.
Also, I've added some sanity checks, thus, if one/more partitions aren't as they should be, the partition table wouldn't be touched at all.
Code will be cleaned up and commit'ed later.
Yes, this will mean, you would need to recompile the kernels for existing ROMs using aw3som3, or even otherwise, yet, that's up to you and your (rom's) developers.
And, this does mean, that it would be an sd-ext for /data shift. You don't want to? that's still going to be your problem. Or, maybe your developers could compile a kernel, and a recovery that has some more allocation. still, *your* problem.
Download: http://www.mediafire.com/download/69m79oie00115bn/recovery.img
patches: up in my github. check first post.
what's the benefit: frankly, I don't see any. But, hey! When I can get a ~440 mB /system partition out of my phone, why not?
Also, to differentiate between normal and aw3som3 recoveries, I've added a lil' text to the recovery.
it should look like the below:
and some proof:
821Oct2014
- 128 mB userdata partition
- Fix wiping crash when block device is not present (credits to Ethan Yonker)
- mtp: fix log spam: findNode not finding a node is not an error (credits to that)
- Update reference to 24-hour clock (credits to Captain Throwback)
- display cpu temperature in twrp use TW_NO_CPU_TEMP := true to disable display use TW_CPU_CUSTOM_PATH := path to set custom path (credits to Jenkins)
- Add support for TrueType fonts (credits to Vojtech Bocek)
- Fix exfat-fuse handling (credits to Dees Troy)
- performance profile support (credits to Tom Hite)
- mtp: cleanup, fixes and performance improvements (credits to that)
- Update RECOVERY_VARIANT blocking to use project-path-for (credits to Matt Mower)
- Attempt to fix md5 issue with backups (credits to Captain Throwback)
- applypatch: add support for BML partitions (credits to Conn O'Griofa)
- atime is access time, let's just use mtime (credits to Jenkins)
- Remove extra slashes from zip path in openrecovery (credits to Matt Mower)
- Fixes for exfat-fuse (credits to Captain Throwback)
- recovery: Fix adb with linux 3.10 (credits to Benoit Goby)
- ADB sideload command not work (credits to Da Zhou)
- Check sehandle before fixing permissions (credits to Dees Troy)
- Attempt to automatically identify data/media devices (credits to Ethan Yonker)
Download: https://www.mediafire.com/?fhu591s552uo5nd
P.S. Something kewl for the recovery coming soon (z31s1g's "TWRP Materialised" theme as soon as it releases)
8twrp 2.8.0.0
changelog
- Fix handling of MTP fork/child process (upstream)
- Include no strict aliasing for MTP (upstream)
- Additional checks to prevent partitioning internal storage (upstream)
- pico: use twrp.fstab (help unify recovery compilation with device tree)
- removed UMS
- updated MTP configs (Sachin Thomas)
- aw3som3 -> awesom3
download: http://www.mediafire.com/download/m1bdj23g36bg1lp/recovery.img
note:
- I've thought about the removal of UMS and felt that it was the right thing to do. Keeping both UMS and MTP sure caused some amount of unnoticeable conflict, which caused either one of them to work, not the other. And since TWRP seems to have moved to UMS by default (so is android-4.4), it would be the right thing to do.
- aw3som3 -> awesom3: this means a considerably big change. 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 (this), and is officially renamed (for awesom3 is easier to 'spell' (one '3')).
