Develop Bugs

oops - screwed up rom upgrade nandroid restore

hi all,
so I saw that unrevoked3 is out and read that it makes installing other ROM's really easy.
so I installed the windows hboot driver and unrevoked3 automatically installed ClockworkMod 2.5.0.1
i didn't really know what todo next so I did a nandroid backup... that took a while, so I assumed it had backedup everything (old rom + apps + user settings etc)
anyways then I rebooted back into my stock ROM and copied opendesire 2.2 onto the SD.
then I rebooted into ClockworkMod and installed the opendesire2.2.zip
then I tried booting normally and it sort of sat on the initial screen for a long while, so I rebooted back into CWM and did a wipe/factory reset.
then rebooted again.
this time it loaded up opendesire fine.
after playing around for a bit I wanted to go back to my old rom.
so i rebooted into CWM and just did a nandroid restore...
now when I boot into my old ROM I am missing all my apps.
the home screens are blank
there is a new "super user privs" app
various other things are missing.
so what did I do wrong?
doesn't nandroid backup everything?
Cheers
D.

I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...

Hi, got my first andriod, the desire, only 6 weeks ago so still a n00b myself! Hopefully someone can answer better and correct my mistakes but here goes:
With Linux you have to be a root (or superuser) to access, modify, execute, etc any and all files. Our Desires, with stock ROMS, do not allow us to do these things - hence we need to 'root' our phones.
I think the internal memory of the phones has two parts - one holds the ROM (the operating system) and the other is a 'cache' which holds user/system info relevant to the ROM. The cache is specific to the ROM which is why if you change from say the stock ROM to opendesire you need to wipe the cache. However, if you upgrade the ROM, eg opendesire 2.1 to opendesire 2.2 you do not need to wipe the cache.
To be able to access the part of the phone which holds both the ROM and the cache you need to be root/superuser. If unrevoked worked without errors and you have been able to change ROMS (i recommend ROM manager) then you have 'rooted' your phone.
When ROM manager asks if you wish to back up your ROM I think it only backs up the cache, not the ROM itself, as that would already be on your SD card as a .zip file.
If you wish to go back to stock I think you need to download stock ROM, use ROM manager to install it, then go back to ROM manager and use the backup/restore option and restore your initial backed up cache.
Hope this helps a little!

tephra said:
I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...
Click to expand...
Click to collapse
You rooted the phone when you ran Unrevoked3, that's why you have superuser permissions.
It doesn't install a different boot loader, it installs a new recovery which allows you to easily flash custom roms without having to use fake-flash.
Something must have gone wrong during your nandroid backup.

ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...

tephra said:
ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...
Click to expand...
Click to collapse
You shouldn't need a goldcard with ClockworkMod, I didn't need one for my branded Desire.

HELP! Boot loop on stock ROM

Hi guys!
I am sorry if this has already been answered somewhere, but I searched pretty thoroughly and I couldn't find a solution
I am trying to S-OFF an HTC Desire for a friend of mine and install CyanogenMod using this guide http://forum.xda-developers.com/showthread.php?t=1016084.
We rooted the phone without any issues, but before going through Alpharev I decided to make a nandroid backup through the phone's original recovery image (just as advised on Alpharev's site: "We try to leave the current ROM and datastructures completely intact. It is, however, advised to ALWAYS nandroid backup your phone before you run this procedure.
You will then always have a correct/current backup to fall back on in case something breaks."). So I just went into the Backup and Recovery menu and I chose backup.
Unfortunately after backing up, the phone went into a boot loop. We tried taking-out the battery and even doing a hard reset but nothing helped. Eventually we flashed the original RUU from O2 (it's an O2 Germany phone) and this fixed the issue.
I am a bit concerned since I wasn't able to find anyone who had the same problem and it is a bit weird that the phone should go into a boot loop without even installing another ROM or anything - just trying to do a backup of the stock ROM. I am thus a bit hesitant to go on with the S-OFF...
Any help would be deeply appreciated!

Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?

Thanks! Do you know why the boot loop could happen?
Moscow Desire said:
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Click to expand...
Click to collapse

I suppose, there was some code that didn't get deleted due to the rooting process, if you used unrevoked. Although it rarely happens, sometimes it does.
Or maybe it didn't like some Application. Who knows. All it takes, is 1 peice of bad code.
With AlphaRev, although many use it, I believe it changes your bootloader code.
And, you can sometimes have problems as well.
But follow the steps I mentioned, and you should be ok.
Just make sure you create and use the Gold Card first.

The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App

TheGhost1233 said:
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Right - I thought about that, but then I was hesitant, because I figured if it went into a boot loop then it probably did not create the backup image properly... So can I still restore the backup image now? It is saved on the sdcard so it should be intact after the RUU, right?

It "should be", but, one can only assume so.
Typically, I make a couple of backups each week. One never knows. Yeah, it will tell you successsful. but, better safe than sorry.

[Q] evo 4g will not boot out of recovery

I tried to update my phone to Gingerbread rom using this guide
http://forum.xda-developers.com/showthread.php?t=1109272
My problem is that I can not boot out of recovery or boot at all. I still have S-off and can still get into the boot loader. I was using a Unrevoked 3 with stock Froyo before I tried to update. I did a NanDroid backup and it still won't restore the rom I had before.It gives me an error " Error while flashing boot image" . I am using Clockword Mod v2.5.0.1. I tried updating the PC36IMG.zip file in hboot, but still won't boot. I am fully able to get into recover and hboot. Will someone please help!

did you name it pc26img? it should be PC36IMG.

Yeah , it is PC36IMG.zip

bz1906 said:
I tried to update my phone to Gingerbread rom using this guide
http://forum.xda-developers.com/showthread.php?t=1109272
My problem is that I can not boot out of recovery or boot at all. I still have S-off and can still get into the boot loader. I was using a Unrevoked 3 with stock Froyo before I tried to update. I did a NanDroid backup and it still won't restore the rom I had before.It gives me an error " Error while flashing boot image" . I am using Clockword Mod v2.5.0.1. I tried updating the PC36IMG.zip file in hboot, but still won't boot. I am fully able to get into recover and hboot. Will someone please help!
Click to expand...
Click to collapse
Well that was probably the most confusing method you could've tried to update.
The reason you're most likely getting the boot.img error, is because the nandroid backup that you're trying to restore, was created when you were on a different bootloader. If you followed the method that you linked to, I'm pretty sure that the new bootloader would've been installed with that. Since it's a different bootloader, your nandroid backups (from when you were on an older bootloader) will not work. You'll have to get the phone booting, and then start making a 'new set' of nandroid backups. Your old ones will most likely be no good now.
I would suggest that you download a new rom, and try to flash it after performing a full and thorough wipe. I would suggest using Amon Ra to perform a full wipe and do your flashing. I'll attatch a PC36IMG of Amon Ra version 2.3. Put that file on your sd card, then boot to the bootloader, and select yes to let it flash. Then boot to recovery, wipe everything in there, except for your SD card. Then flash a rom from scratch and you should be good

Great will try this right now. I was using rom manager to do all backups and restores also. If that helps any.

bz1906 said:
Great will try this right now. I was using rom manager to do all backups and restores also. If that helps any.
Click to expand...
Click to collapse
I would suggest using Amon Ra from now on, and flash everything manually from within recovery, instead of using ROM Manager. And by the way, the recovery you're going to install will NOT work with ROM manager. You can still download roms using rom manager if you'd like, but don't try to use it to actually flash anything for as long as you're on Amon Ra recovery.
So if you're not familiar with recovery, you should be able to figure it out relatively quickly. Just boot to recovery, selct 'wipe'. Select wipe all user data. Also wipe system and boot, and sd ext if your card is partitioned. Then go back to the main menu in recovery, and select 'flash zip from sd card'. Then find the rom that you loaded onto the sd card, select it and flash it. If its an AOSP rom, don't forget to flash teh gapps. Good luck.
EDIT: I would use one of these ROMS if you're looking for the stock OTA updated.
http://forum.xda-developers.com/showthread.php?t=1110733
http://forum.xda-developers.com/showthread.php?t=1038701

That did the trick . Thanks for all the patience and help.

bz1906 said:
That did the trick . Thanks for all the patience and help.
Click to expand...
Click to collapse
You're very welcome. I'm glad you got it squared away. Good work.

[Q] Help Flashing Custom ROM

Hi had the official 2.3 RUU installed on my Desire, I have used Reveloutinary.io to S off my phone, i have now r0oted my phone.
I have created an ext 3 partition on the SD card and took a nandroid backup.
The info i really need is my HBOOT v is 6.93, i want to install the "[ROM][15/08][STABLE][Sense2.1+3.0 GB]InsertCoin CM7 HBOOT/STOCK 1.1.1" on my phone, the question i have is can i simply flash the ROM straight on the phone, or will i have to downgrade the ROM to an official 2.2 RUU first.....
Sorry for the noobness but this is my first post ever so please go easy on me.

If you successfully s-off'd you dont need to downgrade anything, just copy the ROM to the SD Card and for this particular ROM make sure your ext partition is atleast 1GB.
Then Full Wipe/Factory rest + Cache wipe + Dalvik Cache Wipe in recovery.
Now flash the .zip file, after turning off signature verification (should be under "install from sdcard")
Also make sure you download right version of the ROM.
Stock A2SD version if you didnt changed HBOOT, and CM7 version if you changed your HBOOT to CM7.
Also if this is your first ROM, then take a look if you have any WIFI/GSM problems after you booted up, if so it means you might need to update your radio to 32.56.00.32U_5.17.05.23 (search forum for it, there are guides how to flash it too), if you dont have any issues then just ignore it.

Thank you so much for your help, will try it tomorrow and see how i get on.

I jumped the gun and tried it, i took an online backup using My backup pro and whe i have come to restore all of my apps and settings it has restored nothing.
Is there anything i have missed off this?

Sorry no idea i have no experience with My backup pro.. using Titanium Backup.

[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.