Develop Bugs

Couple of noob nandroid q's

Short and sweet:
1. I'm using the recovery that comes with Toast's 2of2 method (this is Amon Ra?) The Nand/ext backup fails for me and I read in a thread that's expected, but I can't find it again with the forum search. How would I fix this, and is it necessary? Is the regular Nandroid backup good enough?
2. Does a Nandroid backup include the kernel? If I push a custom kernel and have problems, will a Nand restore revert me to the kernel I had when I made the backup?
Thanks for the help in advance.

yes and yes
the ext bkup fails bc you dont have a ext partition yet

1. Do you have an EXT partition on your card? If not then you can just use the straight Nandroid backup.
2. Yes a Nandroid should back up the kernel at the point you made the back up. (not 100% sure but 99% )

I hate to hijack the thread but it looks looks like it died down a little and in my search effort this is the closest to what my question is. so to save making a new post on something probably answered before.
I am a relative noob. (i know sad) but i am learnign fast. I was wondering what exactly a nandroid back up does and does not back up.
I am doing the Starting over method to get back to stock 1.47(rooted) to see if it fixes 4g and think i can just nandroid after doing the method described to get my rom back etc. My only fear is that by nandrioding what ever benefit i got from starting over will be reverted.
Srry for the long explaination but basically if i Nandroid is it basically a complete image changing literally everything back to the previous state(ala HDD img)? If not will doing the starting over method then nandroiding revert me back to having the problem again?
Thanks in advance.

Nandroid backs up your entire system config. Radio, software, kernel, rom, etc. As long as you don't unroot, your system will be exactly the way it was after you restore.
Omega, if you do the back to stock root and then restore Nandroid, I'm pretty sure it will be as if you never did the back to stock. Pretty sure but not 100% positive.
Sent from my EVO using xda App

Nandroid does NOT back up or restore your radio, wimax, boot or recovery partitions
AFAIK nand only backs up your system and userdata partitions, not positive about the cache or misc partitions.

nebenezer said:
Nandroid does NOT back up or restore your radio, wimax, boot or recovery partitions
AFAIK nand only backs up your system and userdata partitions, not positive about the cache or misc partitions.
Click to expand...
Click to collapse
Thank you very much. This should mean that once i do the starting over i should then be able to just nandroid back to my rom without having to redo my kernal/theme/rom and it shouldn't mess up my wimax radio again.

omegasun18 said:
Thank you very much. This should mean that once i do the starting over i should then be able to just nandroid back to my rom without having to redo my kernal/theme/rom and it shouldn't mess up my wimax radio again.
Click to expand...
Click to collapse
Correct .
*edit- looks like I'm wrong about the boot partition. I just unzipped a nand and there's a boot.img in there.. still shouldn't affect radio or wimax though

[Q] Custom Roms stuck on boot screen

hi people
i tried flashing a few roms (OD, CM and Pays), but while they flash fine, all of them get stuck at their boot screen (the animation keeps looping). is there any reason for this?
i have an ext3 partition and i haven't updated the radio (4.05.00.11 from orange) but from what i gather that should only affect the camera.

brpqzme said:
hi people
i tried flashing a few roms (OD, CM and Pays), but while they flash fine, all of them get stuck at their boot screen (the animation keeps looping). is there any reason for this?
i have an ext3 partition and i haven't updated the radio (4.05.00.11 from orange) but from what i gather that should only affect the camera.
Click to expand...
Click to collapse
Happened to me but not anymore as I:
1. In recovery mode, do a full wipe, cache wipe and Davlik wipe.
2. have learnt to be patient as some custom ROMS, on their first boot can take up to 10 minutes!!
3. after the first boot I then reboot/turn off then restart the phone.
Since then not many problems.
Hope this helps.
Cheers
Aussie

I'll give that a shot! I did wait quite a while, though (20mins for OD)
If I make a nandroid, then do a full wipe and then restore nandroid, will I be back to where I originally started, or does a full wipe delete some stuff not backed up in a nandroid backup?

some roms also need a ext partition on the sd card to work, so make sure you read carefully before choosing a custom rom.....................sudeki300

Updating the radio would be a smart idea.
There is a Froyo compatible radio suitable for OrangeUK on the forums, no idea which one tho (you'll have to flash and re-flash). Or just pay the few quid to unlock the phone.
As far as your custom rom. Best advice is to nandroid, backup your SD-Card and reformat. Partition your SD for EXT2. EXT3 will put undue writes on your SD because of the journaling, thus reducing the overall lifespan of that card.
Stick back your data and flash your new rom. It should take about 5-8 minutes to boot, then you can restore your apps (if you titaniumed/mybackuped) and enjoy custom rom goodness.

ah ok. those steps sound simple enough, i'll try it
so just to clarify, nandroid backs up the data that a full wipe deletes, correct? (sorry if that's a very obvious question!)

[Q] Force closes long lag times, other problems so un-root/re-root or something else?

So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance

When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.

The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.

loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks

MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.

loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..

MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.

loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.

If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.

jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks

[Q] unable to backup system!

hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA

saadislam said:
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
eventcom said:
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
Click to expand...
Click to collapse
yes, my phone is rooted and s-offed n work well before this and sorry guys previously I was using ClockWorkMod v3.2.0.0..i downgraded to ClockWorkMod v2.5.0.7 to flash radio..but it didn't succeed..So, i flashed through fastboot method and it succeeded.i was able to do a backup after flashing the radio..all went well and 1 day wen i try 2 make a backup in the same ClockWorkMod v2.5.0.7 it stucked in backing up system..

eddykuhan said:
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
(...)
i was able to do a backup after flashing the radio..all went well
Click to expand...
Click to collapse
I see. I already thought that it doesn't have to do with recovery - just wanted to make sure
I suggest you to try reflashing the ROM first - but better make sure that you avoid leftovers of your current "system":
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- reboot
try a nandroid backup again afterwards
if this doesn't help either my suggestion would be to do a complete wipe:
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- wipe all / factory reset
- (I usually do an additional format "system", "data" as well - just to make sure)
- wipe "cache"
- wipe "dalvik-cache"
- flash CM7
- flash gapps 20110828
- reboot
see, if everything went ok then reboot in recovery and do a partial restore of your data (backup & restore/advanced)
reboot again (see if everything works) and reboot into recovery again to try your nandroid backup
There's another thing coming to my mind: do you have enough space left on your sdcard? I never had that problem so I'm not sure if CWM spits out an error about that...

Just for the info, Cwm doesnt give any error if low on space. It just keeps going on with backup.
Sent from my HTC Wildfire using XDA

So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!

Agreed. This is very strange. Have you flashed anything else we should know about that has anything to do with the system partition? Tweaks ect?
Sent from my HTC Sensation using xda premium

slymobi said:
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
hi,
-after upgraded cwm to 5.0.2.0 and i'm still not able to backup
-im using custom mtd
-in matter fact i can restore my old nandroid backup
the story like this after i restore my old nandroid i cannot do backup same ROM again.
and i also tried to wipe dalvik cache from advanced and format cache from mounts and storage then tried a backup and it still fails..:crying:
guys thanks for your feedback im going to do a full wipe and reinstall Rom.!!

eddykuhan said:
-im using custom mtd
Click to expand...
Click to collapse
just to make sure: have you flashed the bravoboot file after the nandroid backup?
If you did, well, a full wipe might be a good idea anyway - but: have you tried my initial suggestion - to format just system? if this is the point where the nandroid backup fails this could be enough to solve your problem...
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- flash the bravoboot file
- reboot
If everything works again you could try to do a partial restore of "data" (in CWM / Backup and Restore / Advanced Restore)
But don't forget to flash the bravoboot file after that one again - and better don't try to restore system again - just data (and sd-ext, .android-secure whatever you like)

Maybe you can try to do backup in 3.x.x.x version of cwm? I had similar problem to yours (I was on 2.5.x.x v CWM) and after it everything worked

I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?

cweijden said:
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
Click to expand...
Click to collapse
Got it solved... I also use MTD partitioning (http://forum.xda-developers.com/showthread.php?t=1233340) and probably have forgotten to flash a required zip after restoring a backup. According to the instructions this should have left me with a white screen. That didn't happen, but it left me unable backing up my system for a while. After repartitioning as suggested by eventcom I was able to make backups again.

Cyanogenmod - Stock and S-Off

Hi all,
Please excuse the n00b questions, recent convert from iOS.. and apologies if this has been covered 1000 times, I could not find what I was looking for with the search function.
I currently own an HTC Desire (Bravo GSM) running 2.2.2 which I have set to Rooted/S-Off. I've been reading about Cyanogenmod and want to give 7.2 a go however I would like to have the option of being able to restore exactly what I've got currently i.e. retaining the Rooted/S-Off without having to go through Revolutionary again etc if at all possible.
There are plenty of guides detailing how to install Cyanogenmod which look straightforward, and I've seen mention of restoring to stock being easy, however there isn't much in the way of info regarding retaining my current Rooted/S-Off status and how to actually perform the restore. I've installed ClockworkMod/Nandroid and have copied the contents of the SD card to my PC as I understand the SD card is cleared during Cyanogenmod's install.
If anyone could give me an insight on whether my aims are possible and a quick guide to restoring (ie, which files I'd need to chuck back onto the SD card to restore), I'd be most grateful.

S-off, root, cwm recovery, SD card partition and the radio survive every time you install a new ROM. You don't/can't back them up. When you do a nandroid backup, it backs up all your data (apps, messages, etc).
Since you already took a nandroid backup, you're good to flash cyanogen mod. Just ensure you've partitioned your SD card correctly and full wipe is done before flashing.
Sent from my Nexus 10 using XDA Premium HD app

Dont forget, download gapps to flash after the rom.

Gentlemen, I can see why this forum is so highly regarded. Thank you.
Could anyone let me know if a guide exists to restore from the Nandroid backup?

I would also recommend 4ext recovery, its way better than CWM recovery.
And just so u know if uv made a nandroid backup using CWM recovery, u wont be able to restore it with 4ext recovery (if that makes sense)
So first thing, google 4ext recovery, download and install the "4ext recovery updater app" then open the app and flash 4ext recovery. Once thats done ul have to backup all important files etc + nandroid backup and save to PC coz ul need to partition ur sdcard and that will wipe everything.
Theres a guide in my sig for partitioning with 4ext.

After reading this some time ago, I wonder why everyone wants or needs S-Off.
https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm

mzrdisi said:
After reading this some time ago, I wonder why everyone wants or needs S-Off.
https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
Click to expand...
Click to collapse
U need s-off because the desire internal memory is piss poor and with s-off u can change ur hboot to maximize data/user memory. Also u can use fastboot commands, flash radio etc etc.
Desire internal memory partition is 250/40/147 (system, cache,data) so if u flash a custom rom that is only 80mb then ur wasting 170mb in system partition so by using a custom hboot u can maximize ur data partition. Like if u use a rom like mildwild and the rom is 80mb then u can use a hboot that i made where the partition layout is 90/5/342 so ur not wasting any mb

jmcclue said:
U need s-off because the desire internal memory is piss poor and with s-off u can change ur hboot to maximize data/user memory. Also u can use fastboot commands, flash radio etc etc.
Desire internal memory partition is 250/40/147 (system, cache,data) so if u flash a custom rom that is only 80mb then ur wasting 170mb in system partition so by using a custom hboot u can maximize ur data partition. Like if u use a rom like mildwild and the rom is 80mb then u can use a hboot that i made where the partition layout is 90/5/342 so ur not wasting any mb
Click to expand...
Click to collapse
That's a great point. And now I realize I posted my response in the completely wrong forum, somehow. Haha

mzrdisi said:
That's a great point. And now I realize I posted my response in the completely wrong forum, somehow. Haha
Click to expand...
Click to collapse
Haha i was wondering coz u posted a link for the htc One. The htc desire, u really need s-off but for newer devices u dont (not sure if u can even s-off them anyway) coz they all have enough memory and an unlocked bootloader is enough in my opinion.