Last night I power cycled my phone and put it on my charger. When I woke up this morning and looked at my phone there were a ton of force close screens. I have no phone (cannot make calls) and not data.
I power cycled the phone over and over and have been searching the net all day but cannot get it to work. The only thing that I had done prior to the initial power cycle was a few updates from the market, so I uninstalled those apps, but it appears that was not the problem.
I have root access and was running gumbo's rom (now MaDoCo...thought that would help) and I really don't wanna do a factory reset. Is there anything I can do?
Factory reset is most likely gonna be your only option. If you dont wanna do that, do you still have the .zip for your rom on your mem card? If so, why not just reflash the zip? Might take care of the issue without having to do a hard reset. I am assumingm, though, that if you are rooted you would have created a nandroid backup? Why not just restore?
Tried reflashing the rom and that didn't work. Gonna do a Factory reset now. Lets see
tried factory reset and now i'm stuck on boot screen
Did you ever make a Nandroid backup?? I would suggest you run the Sprint RUU and bring your phone back to Stock, reroot, install recovery, and then a custom ROM. That looks like your best option.
But, just for the hell of it -- take out of your battery and then insert it back in and reboot, see if that does anything.
What kind of factory reset did you do? Wipe from recovery, go through setting, the home>back>power one, or what? And are you stuck at the HTC screen? That happened to me once, but it was because I flashed a GSM rom my first try. Boot into recovery, wipe the phone, and if that doenst do it, I agree with pseodo, time to RUU.
Well I tried resetting from the recovery and wiping, but it will not boot up. Then I tried the RUU, but it wont get past the boot screen in order for me to to connect it to the USB. I tried connecting the USB through recovery and although I can access my SD card via my PC, going through the steps for the RUU says its not connected.
I took my phone over to sprint and although they know I have a custom rom on there (which voided my warranty), they are still gonna give me a brand new one and send mine back through manufacture warranty. It'll be in on Tuesday. Luckily for me I have an online back up through by MyBackUpPro, so I should be good on restoring settings, apps, contacts and all other important stuff. (Minus Root and Custom Rom )
Thanks for all the suggestions, I appreciate it.
I flashed a new set of icons last week and had a bunch of force closes, restored a nandroid and everything was fine.
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?
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,
I think I´ve got a little problem.
I wanted to restore a backup with the Recovery (RA v. 1.7x) but since about 45min my phone does nothing... only the full stops are going to be more and more and now my screen is full of them...
So as a conclusion: Since 45min my phone tries to restore my backup.
So what shoukd I do?
I´m afraid to brick my phone if I remove the battery or do sth. during restore...
EDIT: Problem solved...
Noticed that adb commands are working during restore and so it was possbile to reboot my phone...
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.