After Nandroid Backup Crashing - Desire General

Has anyone had any problems with a Nandroid Backup?
I have tried twice and had same results - when running unrEVOked 3.21 on my desire, it roots - I go into Clockwork recovery and run a Nandroid Backup which completes successfully.
I then boot up my phone and it hangs on the HTC screen and/or boot loops to the HTC screen again.
I've not actually needed the backup yet as I've flashed custom roms that I'm happy with (like now) and set up as normal and/or ran RUU to go back to stock, which I did the first time it occurred...
Just thought it was an oddity that I'd mention in case I am doing something wrong.
Cheers

Nah, I am seeing this a lot. Quite common for some weird reason. Just ignore it really. When ever I get a hang or bootloop, I just flash the thing again.

That's fine then - just thought it was me - the first time I rooted and backed up it all worked fine - just since then..

Lothaen said:
That's fine then - just thought it was me - the first time I rooted and backed up it all worked fine - just since then..
Click to expand...
Click to collapse
Similar problem here. I had done S-off with Alpharev and found that i could not backup any ROM. i had to install new roms but could not backup any. if i did backup, the phone just freezes at backing up system and thsn nothing worked. pulled battery out and rebooted, my phone just freezes at splash image. finally, i tried flashing the recovery image from CWM ver 4.0.0.5 and all seems working fine now. you should give it a try.

so update CWM and it will work?
mine was s-on by the way.
cheers

Related

[Q] [solved] Bootloops with every ROM except last nandroid backup

Hi,
I have a strange problem here:
My Desire keeps bootlooping with every ROM I flash, even if I flash the ROM thats currently running stable on my device for weeks now.
Its a T-MOB (debranded) wit HBOOT 0.80.0000 and AMOLED display.
I'm not using A2SD ROMs.
I can only recover the phone if I use my last nandroid backup.
I tried factory-reset from phone - bootloop. Wiping from recovery - bootloop.
Tried flashing some ROMs (including exactly the one I currently run) - bootloop.
The loop starts on the 2nd bootscreen (the animated one).
Any ideas would be helpful. I thought about applying a RUU - but if that causes a bootloop afterwards... there would be no way to recover from that I fear.
as stated in many posts, this is a sdcard problem.
formatt your card to fat32 and flash the rom. don't forget to backup important data.
Regards
Marios
Thanks for your reply mariosraptor - I did read several posts explaining that bootlooping is a sdcard issue - I reformatted the card but still get bootloops.
So I tried some different stuff - and successfully flashed several 2.1 images without getting bootloops.
Flashing any 2.2 ROM afterwards got me bootloops again, so I'm still not sure if my loops are caused by the corrupt sd.
Now I took my goldcard and flashed the stock 1.21.405.2 image (lost root during the process but thats no issue).
Do you think its safe to apply the 2.09.405.8 OTA my phone is offering now?
If its really the other sd that was causing the issues it should be safe...
Will I still be able to flash back to an old version with the goldcard (via PB99IMG.zip)?
I know that the OTA comes with a new HBOOT but I still can root it with Unrevoked afterwards. But I'm not sure if I can recover the phone if its looping after the OTA
Solved: replaced sdcard, rooted with Unrevoked, flashed 2.2 ROM - no more bootloops
Old sdcard -> trash (have been using it for almost 2 years, still from my HTC Magic)
happy you solved your prob.

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.
OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager
Older Recovery versions are available on "dougpiston.com" just follow the directions.
www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.
Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip
Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

Clockworkmod: Error while restoring /data!

I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
I've discovered the log function under Advanced of CWM. This is what the log is ending with:
tar: can't remove old file data/system/packages.xml: Operation not permitted
#92997temp.dumpefs1.binefs2.binefs3.binS30edt_perms.logzipalign.log.cid.info.psm.info.mac.infoentropy.datbatterystats.binuiderrors.txtusage-20120304usage-20120305usage-20120229usage-20120301usage-20120302usage-20120303packages.xmlError while restoring /data!
Click to expand...
Click to collapse
I Googled around, and came up with this:
http://forum.xda-developers.com/showthread.php?t=1461658
Again, the Galaxy Nexus, with the same problem being this data/system/packages.xml file, and the same solution being Fastboot.
What the heck is going on? Is it possible for us to use Fastboot on our T989's?
manekineko said:
I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
Click to expand...
Click to collapse
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
manekineko said:
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
Click to expand...
Click to collapse
Of course it is lol.
»»DARKSIDE««
Thanks for the fix, same thing happened to me. I had the Optimus T before this so I whent flash happy 12 hours after I unboxed this beautiful phone. I've only had this phone a week, you saved my life lol.
this is just now happening to me, this threat is old but very help full lol
Hey all,
not trying to rehash a "solved" thread but Im having this issue and then some.
First, I tried Darksides wipe script and tried to restore the boot and install a new rom, then install the backup, all to no avail. I tried everything. When you get this error, it seems (at least from my experience) that your only hope is to restore from the stock 4.02 google image and then restore from the nandroid. This first happened to me when my phone dropped and off the couch and the battery came out. It seemed to have corrupted the sdcard, or, at least that was my guess.
However, upon redoing everything to stock and restoring the nandroid (even upgrading to the latest ver of clockworkmod recovery), the problem comes back. Im worried about permeneant damage, possibly, but it makes no sense that I would be able to revert to stock and have it working fine. When I reverted and restored from my nandroid, everything worked flawlessly. Then, today, I turned off my phone (which is a rarity, if ever) and it wouldnt boot back up a few minutes later. Bootlooop and the dreaded "error while restoring data!" message. Im going to revert to stock again and start completely from zip, no nandroid. Its possible that the nandroid is corrupted I suppose but i dont believe it would let me restore it than. Any ideas? Could this be from me leaving my phone on practically all the time, without ever turning it off? or the battery coming out while in use? (which makes sense in theory but I've done a battery pull countless times and never had a problem like this). Would there be a way I could determine, for sure if its a hardware problem? Verizon Nexus (hardware ver 9 I believe) now running JB Sourcery 2.0 (from team sourcery...an AWESOME rom, so I dont believe it to be that.)
Cheers!
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Wow thanks so much for this! Just happened to me on my note 2 and after doing some googling I came across this post and it worked perfectly, first try. thanks again!
i had this problem now.. my hearth stopped to work.. but this guide helped me ! thanx ! so it is working in year 2014 too
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
plz help me :crying: i am new to this here is my situation i hav a galaxy s4 i9500 i rooted my device 2 days ago and i backed up during the back up it showed no .android_secure found. skipping backup of applications on external storage andalso root error fix . i google it and found its not a big deal so i factory formatted it but when it restored it and restored it all the applications started showing error msg so i formatted sd card and replaced backup folder and tried to back up it showed md5 mismatch so i editted nanroid.md5 with notepad++ and tried to reboot again now its showing recovery data error . what to do?

[Q] Having a problem I never encountered before

I have used Clockworkmod to backup and restore my Samsung GS4 Many, Many times. I have never had any problems restoring any previous backup before. Today after my phone updated an app from the play store, it started acting funny, so I made a backup, (like I have many times before) and after it was completed (no error messages) I proceeded to recover a previous backup that I restored a few times before, and it ended in a "Error while restoring /system!
I tried rebooting the phone and it just hung in the boot animation so I booted back into the recovery mode and again tried the same restore image, but same error. I then tried one that was done before the one I was having problems with, and got the same error. I have a hard time believing that all these backups have suddenly become bad! They ALL PASS THE MD5 CHECKSUM so they must be good!
UPDATE:
I failed to mention, that the phone was UNLOCKED when I made the backup and tried to restore it...
Not sure if that has any bearing on the result. I can restore an older version that was not unlocked when I made the backup, but it's waaaaay back and I lose so much of my data if I have to use that.
I'm not so sure what to do now. My phone is not too useful if it cannot be restored.....
Any help on what I can do to recover would be much appreciated.
Mahalo! (Thanks!)
Running stock 4.2.2 - Rooted Running another restore again. I wiped all the stuff I dare do and re-running the recovery (it takes a while to do)
Will post results after this one succeeds or bombs. :<(
I had this problem once with my s3.. I couldn't figure out now to fix it but what I ended up doing was reflashing my ROM from a clean state and then just restored the data from the backups in recovery.. All your apps and data will be restored except your system apps or mods
Sent from my SGH-M919 using Tapatalk

Bootloop at green HTC Boot Animation after trying to restore TWRP

Hello,
sorry if this has been mentioned anywhere before, but I wasn't able to find something similar.
So I know why way around with my old Nexus 5 in things backing up the phone with Titanium or TWRP, but since it's wifi module died on me I switchted to the HTC 10, which is kinda intimidating to me when it comes to updating to new OS or backing up. With the NExus 5 it was a walk in the park for me.
First, I don't really understand the concept of S-On and S-Off. Don't know if this is related to my problem, just wanted to mention it.
My HTC 10 is rooted, bootloader unlocked, S-On and runs on 7.0 2.41.401.41.
TWRP is the latest available version.
Before I rooted the phone I made a backup of the stock system image etc like explained in one of those "how to root the htc 10" tutorials (no writing allowed).
To root I had to allow writing onto the system partition of course.
Now, I made an TWRP backup. I backed up everything that was available in TWRP. Userdata, cache, system etc.
Few weeks ago I ran into some problems (I though I did, turned out Google App is just weird) and wanted to restore my TWRP backup.
So I did. Went to TWRP and restored the backup from my SD card.
Got no error messages during the process, but when I wanted to boot up the phone the green HTC boot animation did its thing and then froze at the HTC logo, which would result in a bootloop after ~10 minutes of waiting.
Could force the phone to go into bootloader and from there into TWRP, but that's the best I could do.
Also removed SD and SIM card trays, but that didnt do anything.
Had to factory reset and then do a backup via Titanium backup, which is better than nothing but still a pain in the a** because some things just have to be set up manually, which took me quite a while. I honestly don't want do that again anytime soon
Does anyone have an idea what could went wrong or what I did wrong during the backing up and restoring process?
Except for that, I tried to understand how to update to an upcoming version of the OS when the phone is rooted with S-On and how I could keep my userdata? On the Nexus 5 I just manually installed everything via adb except userdata.img and only had to re-root the phone afterwards. I am afraid this isn't possible with the HTC 10, am I right?
The HTC 10 forces encryption and that has broken TWRP restore for me if I try to switch between ROMs. If I switch ROMs then I have to do a full wipe / format. The one time I tried to go back to my original OS I had a similar issue and I ended up flashing the full RUU to get back to stock.
The only time I am able to restore in TWRP is if I'm returning to the same ROM that I am currently running. Even then I usually just restore the data.

Categories

Resources