Related
While booting a back up of MIUI 1.1.28.1 my phone rebooted went through the process fine, then right after I got past the lock screen it shut off, and I couldn't turn it back on. Just before this I updated to the newest Clockworkmod 3.0.0.7. I thought my phone was done for so i let it sit for the night on the charger in the morning i tried to turn it on using the power and volume down button and it booted into recovery so I went along and tried a normal reboot, same thing got to the lock screen, powered down on it's own again. I've been trying to turn it on again now just to get it into recovery and maybe work with it there but it's not going for it. Any suggestions?
Since you can get to recovery screen it is not bricked. In general you can not brick by flashing a rom, only brick by flashing non-working radio or hboot
Here is how to fix it.
1) Download another ROM to the SD Cards. Pick a stable one, I recommend CM6.1
2) Boot into recovery and enter Clockworkmod
3) Wipe everything (Cache/Data/Dalvik cache)
4) Flash new rom in recovery
I got into recovery once after the initial shut dow, now i'm having the same problem as prior it simply will not turn on i've tried most combinations of the buttons and nothing seems to work any suggestions for getting it into recovery again? I realize that I need to boot another rom now but I need to get the phone on first haha. Thanks again
There's only one combination that should boot into recovery.
Turn it on holding down the volume up arrow. If it doesn't do that then you may have seriously messed up or even bricked your phone.
POQbum said:
There's only one combination that should boot into recovery.
Turn it on holding down the volume up arrow. If it doesn't do that then you may have seriously messed up or even bricked your phone.
Click to expand...
Click to collapse
Volume down* up is qualcomm diagnostics. And that's to get into HBOOT, not recovery lol. Also, holding down on the optical trackpad works just the same as if you're holding volume down.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
slong427 said:
I got into recovery once after the initial shut dow, now i'm having the same problem as prior it simply will not turn on i've tried most combinations of the buttons and nothing seems to work any suggestions for getting it into recovery again? I realize that I need to boot another rom now but I need to get the phone on first haha. Thanks again
Click to expand...
Click to collapse
1) Enter Recovery
a. Pull the battery.. wait 10-30 seconds
b. Re-insert battery
c. Power and Volume DOWN with get you to white Hboot screen.
d. Volume down key to highlight recovery, then use press the power button to enter recovery.
2) You should now be in CWM Recovery. Now it is time to wipe everything.
a. Select "wipe data/factory reset"
b. Select "wipe cache partition"
c. Select "advanced" -> "wipe Dalvik Cache"
3) Now it is time to load a new stable ROM, ensure rom is load onto SD card. Recommend CM6.1
a. Use back button to return to CWM Recovery home
b. Select "install zip from sdcard"
c. Select "choose zip from sdcard"
d. Select the zip file rom you load on the SD card.
That should do it! Let me know if you need anything else.
slong427 said:
While booting a back up of MIUI 1.1.28.1 my phone rebooted went through the process fine, then right after I got past the lock screen it shut off, and I couldn't turn it back on. Just before this I updated to the newest Clockworkmod 3.0.0.7. I thought my phone was done for so i let it sit for the night on the charger in the morning i tried to turn it on using the power and volume down button and it booted into recovery so I went along and tried a normal reboot, same thing got to the lock screen, powered down on it's own again. I've been trying to turn it on again now just to get it into recovery and maybe work with it there but it's not going for it. Any suggestions?
Click to expand...
Click to collapse
This happened to me yesterday, and here is how I eventually fixed it.
Let the phone boot up as far as it would go.
Pluged in my USB to PC
Ran reflash_package.exe from unREVOlked
Booted up normally.
Hope this solves your issue.
John
Thanks everyone got it all figured out it ended up being something really simple I just jumped to thinking my phone was done for, thanks for all your help!
Slong427 could you let me know what your fix was? i have been plagued with this issue for two days now and any rom i try gets to the unlock screen and shuts down. thanks, ian
Hi,
I rooted my DHD today and tried to flash the CyanogenMod-7 for Desire HD & Inspire. It seemed to work but now keeps re-booting every couple of seconds. It won't actually stay on long enough to put another ROM on. Can anyone help? This is the first time I've done something like this and it seemed to be going so well!
Thanks!
Pull the battery for about 10 seconds. Then hold the vol- button down and power your device on. Now you should see a white screen with some text on it. Navigate to recovery and press the power button. Now it should boot into recovery.
In the recovery choose wipe data/factory reset ald let it finish. Once its finished choose wipe cache partition.
Then go to install .zip from sd and then choose zip from sd. Now search for your rom and reinstall it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
This is common. Simply wait for it to boot and power off or use the power button to select reboot. You only have to do it once.
The instructions for installing CM7 all say to install ROM then reboot after first complete start up. Shouldn't need to reinstall anything.
Having been left alone for a few hours it seems to have sorted itself out. Thanks! I just wasn't expecting it to spend quite so long re-booting.
I guess you have enabled wi-fi just after flash cm7. Seems like there is a bug or whatever, all you need is re-boot device after first boot.
And about the re-boot loop, just remove battery to turn off you device then turn it on, enter recovery and flash cm7 again WITHOUT do wipe operation. OK, In this time remember to re-boot after first boot.
I got a bit trigger happy and tried to flash Android Revolution HD 3.3. I did a full wipe from ClockworkMod Recovery and tried to install the zip, exactly like I did for the previous ROM. That kept aborting the installation so I mounted the phone and re-downloaded and copied it onto the SD card again. Same problem. I then tried to re-install cm7 and that also kept aborting.
I now have the message "Back menu button disabled" and if I use the power button to select anything it goes straight to a white triangle with an explanation and the Droid, which I think is stock recovery? I'm getting there from what I think is Clockwork though. Is this recoverable or have I managed to brick it?
I had a similar issue a few days ago - it turned out that the battery stats were screwed up so a fix for me was to boot into recovery and then wiping the battery stats.
Everything was fine after that.
How do I do that? I don't want to reboot out of Clockwork as I'm not 100% sure I actually have a ROM at the moment.
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
mdaigt said:
Can boot into menu. Highlight recovery. Press power button. Powers down, not completely though. Screen stays on slightly. When waiting 5 minutes and press power button boots into loop again.
Click to expand...
Click to collapse
open recovery, goto advanced and wipe battery stats
Going to leave battery out for the night as read in other posts. Fixes the problem of not totally shutting down for some. Thanks.
Well leaving battery out didn't help. Continuous boot loop. Put on charger after turning off orange light came on and didn't go to green after 10 hours. Restarted when I got home and boot loop again. Had CoreDroid ROM installed. Working fine than tried to load Kalagas Mixed Theme and that is where I am now. Looping.
Even a blind squirrel will find a nut now and then. During HTC Hboot menu, noticed it was looking for PD98IMG zip. So I shut phone down. Inserted card with it on it and it restored to original firmware. PHEW. Hope this might help someone else.
So today as i was using my phone my browser crashed on me, followed by all the rest of my apps. Everything started to force close and not sync to anything. Now my phone won't even boot up. It just keeps cycling through the boot screen.
Any help is appreciated. Phone is rooted. Not sure what other info is needed.
Thanks
sounds like a hardware issue like the cpu frying itself... were you overclocking it? was it hot? what charge is was the battery at you said it was rooted what rom/kernel? Do you have insurance on it? if yes then call them up and see if you can talk them into a incredible 2...
Have you tried flashing the RUU?
If you get boot into recovery then do that and wipe everything. Including factory reset then fix permission and if that doesn't work really wipe everything then try reflashing..you can boot into recovery by volume up+power button or volume down+power bottun..that should hopefully work man
Sent from my Dinc
Ok, I rooted my evo and tried some different roms. Couldn't find what I wanted so I wanted to go back to the one I started with on my first try. Long story short, I reflashed it and now I have a lock screen, but nothing else. Evidently fastboot is on, because I canter in to try anything else. Can't get a menu or anything. Just a bunch of force close notifications and an HTC screen. Please help!!!!
Did you try pulling battery and holding both the lower volume button and power until recovery menu(hboot) comes up?
fastboot is on, so it just boots to lock menu. I can receive a call, though.
Yeah, have you tried going to recovery via boot, wiping caches and rebooting? Or if that fails, wipe caches (and data if flashing a different ROM), reflash your ROM and then reboot?
Did this happen on a nand restore, or a ROM flash?
Sent from my PC36100 using xda premium
it was on a rom flash. I think i forgot to wipe everything before flashing. I cant get into the recovery or boot menu. Fastboot is on, so it just boots up. Unless there is another way besides holding vol down and power button.
You need to go to settings -> applications -> development settings and disable the fast boot option in order to let you phone do a full reboot.
Alternately, pull the battery out. Put the battery in. Hold down volume down while pressing the power button. Select recovery from the HBOOT menu.
Alternately, in the rom you should have an option to factory reset the device, which will wipe user data.
Edit: It may be settings -> applications and then disable the fast boot option. It's been a long time since I was on sense.
thats what im getting at, i cant get into anything except power menu to turn off phone. It will redeive a call, but nothing else. When i unlock, all i get is an htc screen with a picture of the evo and a bunch of force clse notifications. I cant turn off fastboot. Anyone have any other ideas.
I think I'm screwed!!!!!!
deleted cuz im an idiot and didnt see you couldnt get into recovery at all
toyotech said:
thats what im getting at, i cant get into anything except power menu to turn off phone. It will redeive a call, but nothing else. When i unlock, all i get is an htc screen with a picture of the evo and a bunch of force clse notifications. I cant turn off fastboot. Anyone have any other ideas.
I think I'm screwed!!!!!!
Click to expand...
Click to collapse
Pull battery out insert battery power button + volume down. Pulling out the battery stops fastboot from letting it boot up normally. Pulling the battery stops the fastboot being on affect
Sent from my PC36100 using XDA
+1, hence post 2.
Ok, well pulling the battery worked. Now, so I don't have another heartattack. Wipe the cache, wipe the dalvik cache, what else before I flash another Rom? Thank you cookbook much.
toyotech said:
Ok, well pulling the battery worked. Now, so I don't have another heartattack. Wipe the cache, wipe the dalvik cache, what else before I flash another Rom? Thank you cookbook much.
Click to expand...
Click to collapse
wipe boot system data cache dalvik cache or you can do all data factory reset then wipe dalvik cache and cache
ok, working on another rom. Will post update in a few minutes.
Go read my guide at the top of this section. Sounds like you can get a lot out of there
working like a charm thank you all soooooooooooo much!
This is the best forum EVER!!!!
Glad ya got it.
Sent from my PC36100 using xda premium
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
justsomedude23 said:
So I rooted my LG Optimus G and wanted to download a new rom to try it out and heard that Cyanogenmod was pretty good. So I downloaded it and extracted it and tried to boot it from recovery on my phone. The problem though is that when it goes to boot up it just shows the cyanogenmod logo and the blue circle spinning. From what I understand it's most likely because I didn't restore to factory settings before hand. So I was wondering whether there's anything that I can do to try and fix it or whether I just got a new paperweight?
Click to expand...
Click to collapse
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM(clockworkmod) is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache(the factory reset in TWRP), but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search.
But if its loading to the CM logo, it is not a paperweight. Worst case scenario you can use LGNPST and a stock bin file to go completely back to stock. But as long as you can get into recovery you shouldn't have to go to those lengths.
Hope this helps.
EDIT: I know it's your phone and if you are like me, it's probably your only phone. But don't panic, real bricks are rare and if you can get back into recovery you are usually fine!
HPTesla said:
Did you wipe data, system, dalvik and cache? Actually what recovery are you using? If it's TWRP, go to wipe and then advanced and wipe everything EXCEPT internal storage(data, system, dalvik, cache) then reinstall the rom and gapps. CWM is different and I haven't used it in awhile, but usually bootloops are because you didnt wipe atleast dalvik and cache, but I usually wipe everything. Just not internal because that is where your files(and rom) reside.
If that doesnt work, you can try a different rom and use adb sideload from a pc. There are plenty of tutorials for that here on xda if you do a search. Hope this helps.
Click to expand...
Click to collapse
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
justsomedude23 said:
No I did not, at the time apparently I wasn't thinking. I was using clockworkmod, but whenever I try and use adb on my pc it doesn't detect my phone anymore either. Rebooting it manually also doesn't work either since it just goes back to the loop cycle, I'll definitely look into sideloading though.
Click to expand...
Click to collapse
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
HPTesla said:
Power your phone off completely, then hold the volume up button while you power it on. Once it loads, hit volume down twice then the power button to get back into recovery. Wipe dalvik and cache and reinstall cm and gapps. You should be ok after that.
I also added some edits to my first post. Again I use TWRP which has an adb sideload option under advanced settings......not sure about CWM. But this guide here is a great resource for our phone and has a lot of helpful links.
Click to expand...
Click to collapse
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
justsomedude23 said:
Whenever I try and turn the power off, it automatically reboots itself back into the loop. That also happens whenever I try and put it into recovery mode so I can't delete anything. Would going through the annoying process of removing my battery potentially help with that?
I also don't know whether LNGPST would be able to help because if the normal manual commands such as the power down function don't work, then I probably won't be able to enter into download mode to use LGNPST.
On a side note, I really appreciate your help, but even if all else fails, I do have another phone I could use but it's old so I'd rather avoid that.
Click to expand...
Click to collapse
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
HPTesla said:
How long have you held the power button in? For me sometimes its 20 seconds but Ive heard as long as a full minute. If you hold the power button down until the screen turns off, and it comes right back on try holding it for a minute straight and let it go. If not, you may have to do the battery pull which is a pain in the a**. But Ive had that power down, turn right back on and into the bootloop myself, holding the power button for a solid 20 count solved it - but again it may be longer. And you're welcome, Im here to help - one thing you will learn about fellow lgog users if you get that phone working again - lots of support!
EDIT: Also, if you do get it to power down and then are able to get into recovery - plug it into the wall. Wait until you get into recovery to do it - but if its been on this whole time your battery might be low and you dont want lithium batteries to drain completely. It shortens their lifespans.
Click to expand...
Click to collapse
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
justsomedude23 said:
Holding it for 20 seconds worked and from there I was able to put it into recovery. Thank you for all the help, if not for you I probably would've tried to remove the back and probably just break it even worse
Click to expand...
Click to collapse
Good stuff man, glad to hear it and you're welcome!