• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Should I get the CM7 HBOOT?

Abdur

Android Enthusiast
Sep 30, 2010
252
34
So... I have hit the dreaded Internal memory limit again, and was wondering if I should/could just flash the CM7 HBOOT, and that should fix things. (Root explorer says that I have over 100 mb of free space in the /system area.)
I was simply wondering about the process...
Should I do a nandroid, flash the new HBOOT and then restore data?

OR

Do I have to install CM7 all over again and restore data via Titanium?
 
Just did it, and everything went smoothly. Didnt even need the nandroid. :)

Thanks Paul.

(Thanks SU for the FAQ)

EDIT: Dan, I didnt have to restore anything (did take a nandroid) All apps work fine thus far, and my internal memory spiked. :D All is well so far :)
 
Upvote 0
Hows that possible. Once you flash hboot you have changed the partition table and existing data in /system and /data will be out of sync.

i think its slightly different with hboots as opposed to custom mtds as the boot.img isnt modified or patched to the new sizes
theoretically it can work, from what i understand there is more a risk of unbootable rom due to hboot change than the partitions being out of sync
 
Upvote 0
i think its slightly different with hboots as opposed to custom mtds as the boot.img isnt modified or patched to the new sizes
theoretically it can work, from what i understand there is more a risk of unbootable rom due to hboot change than the partitions being out of sync

I have not understood I think. We have come from windows or Linux where if you change the partition table then its re installation time. I mean all the starting addresses and sizes of the partitions must change.
 
Upvote 0
I have not understood I think. We have come from windows or Linux where if you change the partition table then its re installation time. I mean all the starting addresses and sizes of the partitions must change.

mtd is not a physical partition layout though, you are adapting the sizes by specifying values not creating partitions with container alignment etc

with that theory you have, you wouldnt be able to nandroid and restore as the image size that is stored within nand would not match that of the new layout you have created.

this is layout, not partitioning.
custom MTD is different as you have to patch the boot to take the new sizes and patch the recovery to flash to those tables
 
Upvote 0
mtd is not a physical partition layout though, you are adapting the sizes by specifying values not creating partitions with container alignment etc

with that theory you have, you wouldnt be able to nandroid and restore as the image size that is stored within nand would not match that of the new layout you have created.

this is layout, not partitioning.
custom MTD is different as you have to patch the boot to take the new sizes and patch the recovery to flash to those tables
Thanks for your time.
How is custom mtd different from custom hboot?
 
Upvote 0
i just explained on the end

hboot predefines the mtdlayout via the bootloader.
custom MTD overrides the predefined layout by patching the recovery to only flash to a certain layout size specified and then patching the boot.img of the rom to only work within those constraints.
if you do not patch boot or you do not patch recovery with custom MTD then it will bootloop.
custom MTD can be used on any sized hboot for this reason as it bypasses the bootloader specifications.

this is why it will behave differently and why a customMTD will need the de nandroid restored and a boot.img repatched afterwards so it can work with the new size changes
 
  • Like
Reactions: Tyseyh
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones