Develop Bugs

Unable to restore nandroids

Ok, simply put, I am not able to restore a nandroid properly. I tried 2 different ones and when I reboot the phone just after the completion from recovery, it hangs on the white HTC screen forever (waited 40-50 mins before I took the battery out, with no luck). The "older" nandroid was restored succesfully a couple of weeks ago, so that's not the problem.
Any ideas? Thanks.

S-off and custom hboot image?
If yes make sure the hboot is not to small.
Sent from my HTC Desire using XDA App

Nope, S-ON. Recovery is AmonRA if it even matters, and the nandroids are MIUI_Au roms.

Sorry for double-posting, but just wanted to say I finally managed to restore the nandroid.
If it happens to anyone else, what i did was flashing the same exact rom the nandroid had in it. After that, back to recovery, wipe all user data and dalvik cache, and restore the nandroid.
Maybe it's something related to the kernel and not the rom itself. Anyway it's fixed.

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

Nandroid backup rebboting after udating to clockwork recovery 3?

Hello,
I just got back my desire from repair and have rooted it again using unrevoked, my main rom i flashed was cyanogen 7, i made a backup and then i thought i would s-off and update to clockwork recovery 3....everything was successful.
But when i try out other roms then decide to restore my nandroid back up of cyanogen 7 messeges pop up quickly saying all the apps and stuff have stopped unexpectedly and then the phone reboots again and again.
Can some one help please.
Cheers.

Just do a full wipe and fresh install then backup again.
Sent from CM7

Meaple said:
Just do a full wipe and fresh install then backup again.
Sent from CM7
Click to expand...
Click to collapse
Hi,
I have done this 3 times and the nandroid backup still reboots, only way to fix it is to install cyanogen on top of it and it fixes it.
I think i will need to try with a sense rom and see if it happens too.
Thanks.

Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7

And if you did some fancy formatting to your SD card. Well, Might think about that also....

Meaple said:
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
Click to expand...
Click to collapse
I have deleted the old backup and made new one's each time after a full wipe, the card is formatted correctly and working fine, i have only had this problem after i updated clockwork mod and s-off.

Unlock/Root/Custom Rom warranty question

I know it says unlocking my device will void the warranty, but is there any way I can re-lock it later on so I could send it in for repairs or something in the event I have to do that? Would they be able to tell if I had previously unlocked it?

Yes...you can simply restore the device and relock the bootloader. The toolkit in the stickies in Verizon galaxy nexus development makes all that very easy.
Sent from my Galaxy Nexus using xda app-developers app

Awesome, just needed confirmation I could do that if I had any problems. Thanks!

You can flash the stock images and relock the bootloader, and they can't tell.

One more question. I have CWM installed and made a backup in it (plus an apps backup in Titanium)
If I, say, install CM9 and something weird happens (for instance, the radio magically stops working), will restoring from that CWM backup restore stuff like the radio and such (in addition to my stock 4.0.2 ROM, etc)??
EDIT: So I've backed up my apps with Titanium, but now the guide I am using says to wipe my device in CWM before installing a new ROM. If I do that, won't it also wipe the backup I just made?

Matt08642 said:
One more question. I have CWM installed and made a backup in it (plus an apps backup in Titanium)
If I, say, install CM9 and something weird happens (for instance, the radio magically stops working), will restoring from that CWM backup restore stuff like the radio and such (in addition to my stock 4.0.2 ROM, etc)??
Click to expand...
Click to collapse
CWM backs up your ROM, kernel, recovery and data. Not your radio or bootloader. But all the radios are available in the radio thread and all the boot loaders are available in the bootloader thread
Matt08642 said:
EDIT: So I've backed up my apps with Titanium, but now the guide I am using says to wipe my device in CWM before installing a new ROM. If I do that, won't it also wipe the backup I just made?
Click to expand...
Click to collapse
No, a wipe in CWM will not wipe /sdcard.
Sent from my Galaxy Nexus using Tapatalk 2

Flashing and restoring between GB and JB

Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks

Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?

mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks

dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.

mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks

dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.

CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?