Develop Bugs

Amon Ra 2.2.1 nandroid restore problem

Hi,
Made a complete nandroid backup, with all options selected in amon ra 2.2.1. Flashed MIUI to try it out and decided to go back to Myn's.
Upon selecting nandroid restore, I get nothing but the splashscreen and it hangs there. I left it on for over 30 mins in case it was working and I couldn't tell, but unfortunately it just hung.
I had a2sd installed, is it possible that because the ext partition was blown away that this is causing issues ???
Edit: DISREGARD ..... SOLVED ON SECOND NANDROID ATTEMPT

-Protos said:
Hi,
Made a complete nandroid backup, with all options selected in amon ra 2.2.1. Flashed MIUI to try it out and decided to go back to Myn's.
Upon selecting nandroid restore, I get nothing but the splashscreen and it hangs there. I left it on for over 30 mins in case it was working and I couldn't tell, but unfortunately it just hung.
I had a2sd installed, is it possible that because the ext partition was blown away that this is causing issues ???
Edit: DISREGARD ..... SOLVED ON SECOND NANDROID ATTEMPT
Click to expand...
Click to collapse
I had a similar problem only I made a backup on one phone, then when i got a new phone (same 0004 hardware version), I tried restoring the backup and it failed 2 or 3 times. not sure what was going on.

How long would you say it takes to restore the nandroid backup?

I understand you solved the problem, but I wanted to mention this: If you are using ROM Manager it is a good idea to make a CWM backup as well as an Amon RA nandroid. If one doesn't work, the other may! And, if you are not using ROM manager, you might want to think about it. Also, if you are not making multiple backups, you might want to think about that as well.

Can I flash nandroid backup of tmous 2.2 on 2.1?

So I was trying to backup a nandroid of the beta official tmous 2.2. I have two phones, one has the beta official 2.2 and the other stock 2.1. I rooted both, did a titanium backup of both, installed system recovery and ran backup of both. Then I went and loaded the 2.2 backup sd card onto the 2.1 phone and ran system backup and restored the backup. You are probably cringing by now...so it installed the backup and rebooted, and , is now in bootloop on the M logo. Can I somehow restore using the backups, or do I have to flash using rsdlite and use one of the roms on here?
Thanks in advance to any that can help!!! My wife just said she will not buy another phone for me, on my 4th phone within the last year...bricking it is a first though

So that's what you did...
To fix the 2.1 phone you bricked, try restoring the 2.1 nandroid you made.
If I'm correct, Moto's locked bootloader saved you and stopped Recovery from loading the new kernel that's used by FroYo. Which is why you're bootlooping...
If I'm wrong, you'll have to flash the leaked FroYo SBF and restore the FroYo Nandroid you made onto it...

yea, as you know I was trying to make a 2.2 tmous nandroid backup to post on here, but since I'm a noob at this I didn't want to post a possible corrupt nandroid, so I wanted to make sure it was good by trying it out. I couldn't restore the 2.1 nandroid, so I went ahead and flashed the UK 2.34. Thank goodness it worked.
So, now how can I flash the 2.2 nandroid backup onto this UK 2.34 to verify that I made a correct nandroid backup? Is it possible? I am thinking that it would have worked if I wiped data and cashe, wich I forgot to do that the first time...

well, just figured out that wiping didn't have anything to do with it...as I'm back to bootloop. Flashing the 2.34 again

The way you can test your nandroid backup is by booting into recovery, make a backup, wiping the phone, making another backup, and then booting the phone. This will allow you to see what is actually on the backup. Yes you will have to reboot and play around a bit to check, but it should be free and clear of things, at that point reboot into recovery, and restore your rom. That will mean that the second backup you made will be exactly what you just experienced. Hope that helps.

thanks. On a side note, last night when I was researching how to recover, I could have sworn I came across nandroid backups of the tmous 2.2 in the development section...Beach Head...have you looked in there (I think I saw it posted in the thread about the tmous 2.2 OTA update, thought I saw several people post a nandroid backup in the thread). Anyway, I still plan on getting this uploaded as soon as possible, but thought you might want to check in that thread...

You can restore nandroid backup of 2.2 when you are on 2.1. But you will have bootloop. It's beacause you have new kernel (from 2.2) that is not compatibile with bootloader. After restoring nandroid you should try flashing a 2.2tmo_boot only .sbf http://www.mediafire.com/?pkjkk75emk6x83f . Maybe that help. But i really not tested this with tmobile roms. With jboogie mods its working fine. Also remember about gsm fix if you use phone not in US. All 3g fixeS are in this topic http://forum.xda-developers.com/showthread.php?t=944258 . You should use the file with the frequencies of your country. If somethings go wrong you should flash 2.1 rom sbf (version that you are using now).

[Q] [Help] Nandroid Fail

This isn't like some of the other nandroid fail threads i've encountered.
I had a full nandroid backup of my tmobile g2 (eng hboot) and I lost that device. I got an exact replacement, rooted it (no eng hboot), installed rom manager only and flashed clockwork. I then copied my nandroid backup to the clockwork/backups directory and did a restore.
The phone booted successfully with cyanogen 7 nightly 22 flashed but the only problem is that it seems to have done a fresh install...as in there are no apps, no data, just cyanogen 7 nightly 22. It appears it didn't restore anything except the rom itself. Any ideas? thanks in advance.
ps. ive done multiple data wipes, and tried 2 different nandroid backup files on the new phone.

Did you have darktremors a2sd installed on the old ROM? CWM3 seems to have an issue for some with seeing the sd-ext partition and won't back it up. So when you select 'restore' in CWM it *successfully* completes the nandroid restore correct, no errors? It would be odd for it to give you a 'restore complete' message if it ran into any errors.

pretty sure I don't have a2sd installed on the old rom. first time i'm hearing of it. I don't recall getting any errors after restoring the backup but I will try again and double check. I also have much older backups that I can try to restore and see if those go through

Well I think this needs more attention if it's really not restoring the nandroids fully. Seems like it's restoring the system.img and whatnot just not the data.img. Maybe try it with ADB and see if it works. I've never had to do it that way but I know it can be done, you may have to run it in a shell.

I tried restoring a nandroid backup from February, which I believe was backed up with an older version of clockwork, and it was completely successful. This tells me that either the new clockwork is not backing up correctly or it's getting corrupted.
I then tried restoring 3 different backups and they did not give me any errors but failed to restore my data. hmmm

[Q] Best way of updating Redux?

I've installed Redux and enjoyed it on my phone for over a month now. However, I see there is a newer version out. What is the best way of updating (bearing in mind I've got quite a few apps that I don't want to install)?
TIA

You can just flash the new Redux version with the Rom Manager or with the Recovery. You dont have to wipe because you're already on Redux.
Nothing would be deleted. But it's helpfull to do a nandroid backup (a nandroid backup will backup everything on your phone (Apps, Data, Settings,...)) with Rom Manager or Recovery if something goes wrong with the update.

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