So I have had my phone rooted for over a year now and actually this phone is a 004 hardware phone I got as a replacement a few months ago I had to root too.
I went back to a later CM7 nightly from MIUI two days ago or so and things had been good. I flashed SavagedZen 1.2 and everything was still good. Before i went to bed, I decided to calibrate my battery and wipe my stats. After calibrating my battery i went to go into ClockworkMod 3.0.0.5 and it just went to a blank screen. If i hit Menu while in Clockwork, it will pop up 3/4's the way down "ClockworkMod Recovery v3.0.0.5". It will not let me do anything else, it will just toggle on and off with the Menu key. I have tried hitting Back button or Power, but no go.
I tried pulling the battery many many times, using a different battery and pulling it multiple times, using the power cable with them many times and nothing.
It is also stuck in a White screen bootloop if i try and let it just start up normally. (I let it bootloop all night as i slept)
Anybody have a clue as to what is up?
Thanks
Scratch that, I was able to restore it to a clean CM7 via choosing CLEA STORAGE in the bootloader.
GAH!
Related
My daughter is using a MyTouch Slide which I rooted and put Slidemeroot5 on. She's been using it for a few months now with no issues. Just a bit ago I noticed the CM6 was available and went to grab her phone. The screen wasn't responding so I pulled the battery and restarted. It booted into the standard recovery mode and after that none of the buttons respond. Only option is to pull the battery but then it still boots into recovery.
I placed ESPRIMG.zip on the sdcard and recovery could not find the file. Is this phone bricked? I can't even think of what might have happened for it to do this.
I'd try wiping from HBOOT screen first.
It doesn't give me the opportunity to. Buttons are completely unresponsive. Ended up doing a warranty replacement with T-Mobile.
Hi!
I flashed CM7 (Stable) last night and it was working great. I was using it today when phone froze on me...I don't remember what I was doing...I think I was listening to Pandora. Even though the system was frozen, I was able to hold down the Power button to select Reboot. Phone rebooted but it was stuck on the splash screen for at least 10 minutes. I pulled the battery but it won't get past the splash screen. I tried to get into hboot but the phone vibrated several times and then displayed a blank screen. Now all my phone is doing is flashing the green LED.
Any ideas?
Thanks,
Marc
This could be bad, but don't panic yet.
It has happened to me before and a simple waiting 5-10 min and a battery pull has done the trick.
Do you have a nandroid backup? If so and the battery pull works reboot into hboot and then recovery and restore it. If not boot into hboot and do a full factory reset.
If after waiting a while and you a battery pull still doesn't do the trick try holding down the power button and volume UP. This could possibly reboot it.
If you finally give up I suggest trying this thread.
http://forum.xda-developers.com/archive/index.php/t-958411.html
Thanks! I stopped panicking enough to be able to get into HBoot I still couldnt get past the splash screen so I ended up reflashing CM7. Everything is fine and dandy now. I'm keeping an eye out on it today because it froze when it was running low on battery...I want to see if it does the same thing today. Thanks again for the help!
Good luck...
I've had great luck with the CM7 ROM. Last night I ran my battery down to 1% before charging and didn't experience any issues. Hopefully your issue is resolved for good!!!
Glad I could help! I really like CM7 the battery is great on it. If it freezes again try to reflash it. If it works, Great! haha
Hi Folks,
Was running ZYGOT3 2.0 and Franco #6 for last week or so, with no major issues.
Had a freeze-up after a phone call this morning, figured that maybe I was undervolting too aggressively, and didn't think much of it. Pulled battery, replaced battery, restarted phone, phone hung at Google logo.
Pulled battery again, rebooted to bootloader, entered CWM recovery no problem. Figured I'd reflash the kernel if my phone wasn't booting past the Google logo due to the undervolt settings. When I went to choose zip from SDCARD - the screen went black other than the CWM version and logo, and my folder list never appeared at the top of the screen.
Pulled battery, tried again, same result.
Pulled battery, this time went to advanced menu - wiped dalvik cache no problem.
went back to main screen to try to wipe cache again...and it hung again. Got distracted, came back to phone like 5 minutes later, and CWM had finally responded and was showing me the option to wipe cache.
So I was able to reflash Franco #6 and boot the phone back up. Then I just downloaded Franco #7 kernel - rebooted to CWM Recovery to install - and noticed that the CWM is again very sluggish. It seems that I need to wait anywhere from 30 seconds to over a minute before it responds to even a simple command, such as to show me the list of files & folders.
Any ideas folks?
Thanks!
Justin
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?
Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
if you can get into cwm then try fastboot and flash the factory images from the boot screen
_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.
id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it
I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.
So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.
XCmaster said:
So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.
Click to expand...
Click to collapse
If you can access hboot its not bricked. You need to do the five vibes fix herehttp://pvillecomp.com/?page_id=33, if you can get to hboot to use fastboot. If you cant access hboot you are out of luck.
well an update. what i did was pulled the battery and held down the power button for 10 seconds, then put in the battery and plugged the charger in. and it forced it back into the bootloop. i was then able to access hboot and try and reinstall. well both cm7 and cm9 both started the bootloop. so i went through and factory reset the phone and formatted the sd. and also wiped the dalvik and cache. also formatted system/data/cache, and reinstalled cm7 and it started force closing EVERYTHING. so i completely wiped the phone and reinstalled cm9 and everythijg worked fine, so i went back to cm7 and now everything is working as before. didnt have to enter code in the terminal emulator blahblah.. just an easy fix for me dont think itll work for most but did here so its worth a try i guess.