I was using KangORama and loving it but decided to give Rodriguezstyle a chance. I had done a nandroid backup and flashed the Rodgriguezstyle ROM. I didn't particularly care for it so I went into recovery and tried to do a nandroid restore. It went through the motions and got to "as is" then froze. For at least 15 minutes. I had to remove the battery and now when I reboot, it stays on the Google colored "X" screen. What do I do to fix this??
I rebooted into recovery and reflashed Rodriguezstlye (only ROM I had on sd card) and the phone is back. I'll move back to Kang-O-Rama now. Why would nandroid backup cause this?
Related
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
Hi all,
I just installed ClockworkMod Recover using ROM Manager on my G1, replacing Amon_RA. Immediately before replacing, I did a Nandroid backup using Amon_RA. No problems, lots of dots and then it returned. After I installed ClockworkMod, I tried creating another Nandroid backup, first from the recovery screen and then from the ROM Manager app. Both times the backup hung on the message "Backing up .android_secure..." and required a battery pull to get back. The last time I let it go for over an hour before giving up. I'm running CM6 stable, if that matters.
Any idea? I'm about to put Amon_RA back on, so I can get good Nandroid backups again.
I know this is an old post but I am getting the same thing. Going to continue researching.
hmmm last time i had an issue kinda like this it was the recovery... need to re flash it somehow.. maybe the sd ext has something to do with it also...? im not sure but i would try to re flash recovery or maybe switch back to amon-ra if all else fails can always re-root
Mine took over 20 minutes today. Just when I was about to pull the battery, it moved on. Probably down the amount of stuff you have on your phone I guess.
I'm running a 32GB card stuffed with apps
havent used clockworkmod in a long time, i stick with amonra -- but if i remember right with clockwork isnt there an option to have a status bar so you can see how things are moving along? maybe not...
hey everyone, i'm new here. Sorry if this has been posted before, but i'm having a bit of a problem right now.. I rooted my CDMA hero last night. I made a nandroid backup of my phone before i flashed any roms. I flashed a rom and did something wrong, so i tried to restore my nandroid backup... and i got stuck at the "htc - quietly brilliant" screen. i then found out i'm supposed to wipe all data, so i did, and flashed the nandroid backup again.. same problem. so i flashed a different ROM and it loaded up.. so, again, i wiped all data and tried to restore my stock ROM (google didn't back up contacts when it said they were, so i'm trying to restore to get them back)... and i'm STILL getting the quietly brilliant screen. Any help? Thanks!
When you restore - it does take a while to boot up. How much time did you wait on the white screen? Also, did you get any errors during the nand restore?
no, no errors.. and i waited a pretty long time. Enough to allow the "Quietly Brilliant" screen to flash black, then come back up a few times... i'll do another nandroid restore though and watch for errors. But when i did it before, I didn't see any.
this can happen if you don't have enough space on your sd card during the backup. it has been my experience that nand will not give you an error when it runs out of space, everything appears to have completed as it should, but when you go to restore not everything is there, thus causing the phone not to boot.
also as someone else stated the first boot after a wipe can take a very very long time. 10-15+ mins. (this is not always the case)
my advice (for what it is worth) try a full wipe, and load a new rom. another thing to consider is that most (should be all) roms do not come with gapps built in. once you flash the new rom, before you try and boot it, you should also flash gapps. for instance aospCMod will not load without it.
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
daveishere911 said:
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
Click to expand...
Click to collapse
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
aqualls said:
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
no
Sent from my HERO200 using XDA Premium App
I've tried repeatedly to install CM7.2 and keep getting stuck on a blank screen. I'll see a "CyanogenMod" then "loading..." right below that. Then it goes blank and nothing ever happens after that.
Some background info. I've had CM7 installed on this in the past without problems. Months ago I went back to a rooted stock. Then yesterday I decided to try CM9 alpha. That installed perfectly. But it was too slow, so I decided to try CM7.2.
I used the same CWM 1GB boot SD, copied "encore_CM72-MiRaGe-02012012.zip" along with the Gingerbread Gapps and CWM. Installed in the same order and wipe data/factory reset.
So I got stuck on that blank screen after the CyanogenMod loading... message. I then decided restore to stock. Installed the 1.01 stock image. It also wouldn't boot up, but I powered it on and off 8 times and it did a factory reinstall and then it booted up normally.
Once back at a factory fresh system. I powered it off and tried installing CM7.2 again. Unfortunately I'm having the same problem again. Ugh, why won't it load now.
Hang on... I might be in the process of making a newb mistake. MD5 didn't match on my SD card, probably the ROM.ZIP is corrupted. Trying again with a good copy.
That was it. It's working now. Please disregard my idiot on the Internet moment. Thank you.
You always figure it out five minutes after you finally give up and post for help/venting.
Been there.
Been using the Toolkit 1.9.8 to root and unlock my att nexus 6. Seemed to work fine and have been running well for the past few days, however after a backup attempt (nandroid) the phone is stuck in a boot loop (spinning dots). Any tips to help me get it unstuck? I've rebooted into recovery and wiped the caches. I did successfully create a backup before it started looping so I'm trying to restore from that at the moment.
I just went and did a Nandroid too after running a few days fine after having unlocked and rooted. Now on my first boot I cant get the OS to load, stuck at the spinning dots splash screen too. I left it for about 20 minutes just to make absolutely sure it was stuck. I thought maybe it had to re-compile things or something with ART. IDK, it was a theory anyway.It seemed stuck for sure so I held down all buttons to force a turn off. I then booted into TWRP and restored my nandroid I just made, which I know shouldnt make a difference cause it is the same thing and I didnt wipe anything before anyway, just made a backup. Anyway, I restored the nandroid and tried to boot and it worked fine. Odd, but worth a try for you.