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 rom issues!

so i was trying superfly 1.2 froyo rom and decided i wanted to go back to slidemeroot5r1, i used rom manager to resoter nandroid backup but when the phone rebooted all my apps were dead links on the phone i couldnt use market app or google maps or anything useful so i tried to do a fresh install of the rom and it fails while installing at "line 302 system" i think thats what it says
it did reboot to some rom but im not sure what it is and i still dont have market to download rom manager
im sure this is a bit confusing as i may have left out an important details but
any help would be appreciated
thanks

From clockwork recovery did you do a nandroid or did you reflash using "install zip from sdcard"
Sent from my T-Mobile myTouch 3G Slide using XDA App

My guess, and this is totally out in left field, is that the superfly rom either doesn't use a2sd or something. If you previously used a ROM that did, then some versions of clockwork didn't correctly grab the SD-EXT partition (mine still errors) so I wonder if the actual location where the apps lived is no longer around...
Or I could be totally crazy...

Well I learned from flashing various roms that the easiest was to avoid issues is to wipe using the partitions menu in clockwork recovery
First...
Insure all partitions are mounted.
Second...
Format each partition, to exclude sdcard
However all of these will be formated if you select "factory wipe" and flash a new rom.
Factory wipe clears data and cache when you install a rom most should also format system, boot and sd-ext prior to installing anything.
Edit: insure your using the latest recovery from clockwork
Ver. 2.5.0.1
Sent from my T-Mobile myTouch 3G Slide using XDA App

hello
so the first time going from froyo to slidemeroot5r1 i used rom manager to initate my nandroid back up
that ruined all apps that i had on my phone,(including market and others) i then tried to install through clockwork and sd card zip which had the same results
i was able to reinstall a fresh install of slidemeroot5r1
after i had a fresh install i tried to reinstall a nandroid backup and had the same result as before
which really confuses me because i had used my nandroid backups before to restore my phone so i dunno what got corrupted
maybe because i updated to the new radio???
anyways im back to where i want to be for now
thanks

Upgrading to GB on the DInc

Hey guys, so I'm a noob and need a little bit of help. I just downloaded this:
http://forum.xda-developers.com/showthread.php?t=1219407
Now, what do I do with it? Also, will I lose all of my data by flashing this onto my phone? (ie: my texts and my homescreens, etc?)
Thanks!

are you rooted? if not...
http://www.jonamerica.com/technology/updated-root-the-htc-droid-incredible/
once you have clockwork recovery and all that, boot into recovery, 'flash rom from sd card' (after putting the zip file on ur sd) and ur good.
If you dont want to lose everything, after root, download titanium backup and run that. you will be able to apply most of your stuff back on once you flash a new rom.

howbout some thnx -.-'

I'll give you some thanks for that succinct explanation of steps to take.
I'm ready to root with unrevoked - guessing I should use the "flash and recover" version instead of their "forever" one?
I installed Titanium backup, which I'll use after rooting to backup pretty much everything that it can grab.
Then, I'll use the SD card-based install that you mentioned.
I've read that I should do a full wipe before installing the OTA ROMs being offered - is another tool needed for that, please?
- ooofest

You've got it. The newest version of Unrevoked has made the "forever" one obsolete.
You will be able to perform all the wipes required from within Clockwork Recovery.
Also, make a clockwork backup (nandroid) as soon as you have root, so if you run into any problems flashing roms you have something to restore.

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