Database Develop

is my nandroid restore frozen?

This is my first time to restore a nandroid backup i recently made. The load bar isnt animated any longer and its sitting on:
"restoring data...
[email protected]"
the first time i pulled the battery after about 5 minutes and rebooted into what appeared to be a partial restore, but the home button didnt work and i powered down before it finished synching my settings. Im on my second attempt, sitting at the same place and its been close to 10 minutes, is this normal or should i just try pulling the battery again and reflashing the rom altogether? I wiped the first time even though my searching said it wasnt necessary, no wipe the second time. here are my unhelpful search results:
http://www.google.com/search?source...s+nandroid+restore+take+on+nexus+one?&qscrl=1
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=did+my+nandroid+restore+freeze?&qscrl=1

Doesn't sound too good i'm afraid & I am of little help either as I too am new to Android ROM flashing - but rather, as a help to others, can you state what type & version of recovery you are using (ClockWorkMod / amon_ra), what Nexus you have (AMOLED / SLCD), whether you have the phone connected over USB when backing up / restoring, android version backed up, what charge level you had etc.
I believe all of these elements can affect your results in one way or another.
e.g, I believe for SLCD, you require amon_ra v1.8.0.1 & some people have reported issues if performing the operations while connected to USB.
Good luck & let us know how you get on.
Steve.

thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery

AndroidPerson said:
thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery
Click to expand...
Click to collapse
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine

cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
thanks im going to remember this, the more things i have to try when something goes bad, the better

cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
I've run into a similar hangup before running Clockwork, and fixed it pretty much the same way you did. I've since gone back to Amon's recovery, as its nandroid functions seem to be more reliable.

[Q] I9000 Crash and Failure to Boot

I had my phone randomly soft brick today and I was wondering if someone might be able to shed some light on what happened to me.
So, my phone is a Samsung Galaxy S GT-I9000M on Bell Canada. Rooted, ADW, Clockword Recovery, *No* Lagfix (I removed it), GPS Update. Today I went to open an app and the phone froze and subsequently rebooted. Upon restart the boot animation displayed for a while and then went to a black screen. Phone did not respond to any input. Force restarting led to the same effect. Tried a battery pull, no dice. Wiped the cache partition, no dice. Booted into recovery then clockwork recovery. Restored to my last nandroid backup. Phone restarted, displayed boot animation for a long time then went to the black screen and accepted no input. Restored to my nandroid before that, no luck. Wiped dalvik cache, no luck. Connected the usb, booted into recovery, opened android commander, and pulled down a copy of everything on the internal sd card. Finally, while walking to the Bell Canada store to get a replacement, I did a factory reset... The phone booted.
So what has me extremely curious is what did a factory reset do, that restoring from a nandroid backup didn't? And what the hell happened to the phone that an app crash trigged a quasi soft brick. Let me know if anyone has any ideas.
Thanks!

I had the same thing happen to me all the time on the XXJPC TOM after having installed the TaskManager update (it was 1.4 back then) from Samsung Apps. Everything seemed fine until I rebooted. After the boot animation played, there was the "I'm crashing" vibration (vibrating once, then three times shorty after) at which point the phone went off. I had this happen four times in a row before I figured out (by accident) that it's the TaskManager update that did this to me. Only a factory reset could revive the phone. Did you, by any chance, install the TaskManager update, too, on a Froyo ROM?
Hope this helps a bit. It was rather frustrating to me.

I'm just running a rooted stock i9000 rom (android 2.1). No task manager update.
I did manage to recover. The process ended up being this:
Backup data on internal sd card while in recovery mode
Factory reset
Wipe cache partition
Boot
Install rom manger
Copy data back to internal sd card
Restore from most recent nandroid backup
The only thing I can think of is somehow I suffered a corruption of my data partition, so the factory reset fixed it by wiping the partition. Not sure if that's a possible explanation.
Sent from my GT-I9000M using XDA App

[Q] Recovery mode not working - Please help!!!

Hi,
I have tried to upgrade the ROM on my Samsung Galaxy S i9000.
The upgrade was successful but the phone was not running well, so I tried to restore the previous ROM by using ROM Manager app.
For some reason the restore did not take place when the phone was rebooted.
After this, the phone will not boot.
When I press the power button, only the welcome screen comes on, but nothing happens.
I tried to enter recovery mode, by pressing volume-up+home+power, but nothing happens (the welcome screen comes on and that's about it).
Download mode is working.
When I try to connect the phone to the PC in download mode the PC recognizes it, but in other modes, the USB is not recognized.
What should I do to restore my phone to its previous state?
Is there another way to enter recovery mode?
Thanks,
Dubi

Use odin to flash another firmware to it, I have links below in my sig.
Instructions should be within the threads, but its essentially put the files in the matching names, and click repartition (this wipes the phone) and click start

Thanks for your quick reply.
I am not sure that I understand the difference between recovering the old ROM and flashing a new one, as you suggested.
If I use the Odin with the download mode, will it erase the contents of my internal sd-card as well and contact information or will this information still be available and I can use it to restore my phone (for example I used Titanium backup to backup the contents of my applications etc.)?
In other words, what are the differences between the two methods?
Thanks again,
Dubi

Odin is usually considered a fresh install, it usually deletes everything on your phone, (sometimes internal sd card, but not always). When you do flash through odin its like a factory reset so you will loose all contact info and app info etc. If you saved your backup on internal sd then you will loose that if you internal sd is wiped.
Going through recovery it depends on the rom and contents of the zip. Sometimes it will factory reset your phone, sometimes it wont. Usually it is advised to wipe if you are changing to a different rom, but as you said it was only an update and so it probably wouldn't require a wipe.
In your case yes everything will be wiped via Odin, and possibly your internal sd card will remain.
Titanium backup will allow you to restore the apps and data you have backed up.
Unless you can get back into recovery it may not be possible to save everything that was on there previously. The only way that I think may work is by using adb, and typing adb reboot recovery. If that works then you should maybe try the update again, or try another zip
Solve it? lemme know

[Q] Galaxy Ace: stuck in bootloop for unknown reason?

Reposting this here…
Hi, all!
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
I have tried a suggestion a user here made and made a nandroid backup, did a full wipe, reinstalled the ROM (which allowed me to get out of the bootloop) and then restored the data from the backup (which stuck me back in a bootloop). Still no idea and I really don't want to lose this data. If it's too much effort to fix the loop, is it possible to extract the data from the backups on a PC and manage to restore it to a clean wipe?
Thanks in advance!

Fixed my problem by doing a clean installation, and using Titanium Backup to extract the data from my nandroid backup. It was quite a simple solution, really. No idea why no one seemed to suggest it, though.
Oh well, my problem is solved.

HTC One stuck at recovery screen, Can't Reset

HTC One M7 stuck at Android recovery
Did a factory reset for no reason and my phone died while it was resetting. Ever since it's been stuck at the android recovery, Factory reset isn't
working, gives me the error : Failed to mount data, pretty much tried everything, with no luck
what's hapenning, anyone know how to help me, i'm almost giving up on it.
Tried wiping cache, connecting to pc shows me a blank usb drive that's inacessable, can't find phone on htc sync, tried to adb shell: No devices found.
P.s - The phone had no problems prior to the needless reset, the phone wasn't rooted.

I seem to be having the same issue. Mine soft bricked and the Factory Reset failed.
Mine shows:
-- Wiping data...
Formatting /data...
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting\/cache
Data Wipe Complete.
Write host_mode:0 done
Then it gives me the same system recovery menu. Rebooting just put it right back into the same loop.