Related
Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
tchabalie said:
Please help! My rooted LG Revolution won't turn on. When I unplugged it from the charger this morning I powered it off. when I went to power it back up all it does is flash the LG logo and do a little vibrate like it is force closing! I have 2 days left before I can no longer return it. I did several battery pulls also with no luck. thanks in advance!
Click to expand...
Click to collapse
Did you install Clockwork on it, or just rooted?
If you only rooted it, try performing a factory reset.
This can be accomplished by holding volume down and power until you see the screen change to "Clear data and factory reset?".
Press power to confirm.
You will lose your data, but your phone should return to normal.
Just rooted, no clockwork. I will give it a try! thanks!
Tried your suggestion...just keeps flashing and vibrating. Any other suggestions?
Did you ever see the factory reset screen?
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
tchabalie said:
No I didn't. just the LG logo flashing and the force close vibrate. the only way I can get it to stop is to take the battery out and put it back in. Then when I hold the voume down and the power button it just starts doing it all over again.
Click to expand...
Click to collapse
make sure you are holding it long enough. You have to continue to hold the power and vol button for sometime before you get the recovery screen.
As rooting will generally not brick a phone (it is the recovery mod that generally bricks), if you cannot get it, take it back tell them you woke up and it was on the charger like this. They should exchange it with out issue. (Do not mention that you rooted the phone)
It sounds to me like your phone is defective, it happens.
Another option is here: http://forum.xda-developers.com/showthread.php?t=1120062 .
I can walk you through it on IRC tonight if you're on around 12PM Pacific Time...
If not, there are guides for using LGNPST on the internet.
Good luck!
Thanks! Held the buttons down for a full 3 minutes and nothing. Is that long enough? Read through the other info you posted and boy does that look scary! LOL! I will try tomorrow when I have more time. Or maybe I should just return it since I have only had it for 12 days
try pulling the battery and holding the power key for about 30 seconds. my original droid use to do this from time to time and it always worked for me.
Thanks. Tried but it did not work. Ended up just returning it and getting a new one. Now I can start over! LOL Just came from the Samsung Fascinate and was pretty proficient in flashing roms and kernels. But I have to admit that I am a little confused with the process on the Revolution.
Not sure boot problem is related to root
I've had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen in the morning.
It seems a number of non-root users have this problem.
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
This morning is the first time, however, that I have this exact problem. For a few times this morning I was able to get to clockwork and restore different ROMs, but always to the same blank loop during boot. Now not even able to get to Clockwork or Factory Reset. I'm headed in to Verizon to try for a replacement. I'll let you know if they make any noises about rooting.
Getting back into Clockwork
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.
Returning Rooted Phone to Verizon
FYI, I returned a rooted, stuck in boot loop phone to Verizon yesterday. In the store they arranged the return and did not ask about or look for rooting in any way.
They did try a factory reset, which was not working in any case, so no signs of Clockwork.
Same problem, different results.
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
timus5 said:
I have a ROOTED LG Revo, but the first one I owned had the same problem. That one was NOT rooted, so must just be an LG thing. First phone had stock android 2.2, and this one has STOCK 2.3.4 ( after OTA ), and is just rooted with simple memory management and font tools. I WAS able to Hard Factory Reset, but the same problem still existed after reset. ADB cannot even recognize the handset. Boots with animation, stops halfway through, reboots into blank screen and freezes. RETARDED!!! This will be the second handset being sent back in as little as a month. I bought the REVO the DAY it came out, and loved it. But now I don't. No love left. I'm getting the Droid Razr!
Click to expand...
Click to collapse
Please don't necro threads....
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app
timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?
timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?
timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device
timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q
KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?
Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,
It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/
Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.
Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8
mashk said:
Have you tried a factory reset?
On boot, bottom down n power will take u to fastboot.
You can do a factory reset from there.
HTC sync can save your stuff.
Sent from my HTC One_M8
Click to expand...
Click to collapse
As I mentioned above, I can hardly do anything from that fastboot screen. Up, down and power button is not working as I cannot navigate to recovery or factory reset. Even pushing power button wont do.
When I connect the phone to PC, nothing happen. It is because the phone is out of battery i suppose?
The problem is when I start to charge the phone, it will keep looping. But if I dont, the phone is death and I cant do anything.
I honestly dont know. I suspect you have
Fast boot selected under Settings>power.
You've got to try till you can get into fastboot otherwise send it for repairs.
Sent from my HTC One_M8
evelucife said:
Hey guys,
So I have had my One more than a year, never root, never install any mod in it, just simple, daily use. It worked well till last night when some weird thing happened:
- At first, the Back, Home and HTC buttons keep flashing along with the screen. When I unlock my screen pass lock and go to the home screen, it showed a notification like "To restart the phone, keep pushing the power button for (x) second" with x is the count down number. After that, the phone is automatically rebooting, then the problem happen again.
- After a few times, I manage to shut it down properly then turn the phone up. As I notice, as long as I doing something with the phone such as calling somebody or checking facebook or simply sliding the home screen, thing is normal. But as I stopped using it, that weird notification pop up again
- The phone keep restarting after that, again and again. Sometime it boot successful, but when Im go to the home screen, the notification shows up and my phone restarts again. As I couldnt turn off my phone, it is drained and out of battery.
- This morning, I put the cable in and try to charge it, and My One now stuck at the first HTC logo screen then restarting and then stuck again. That looping process is drive me crazy. As I try to pull out the cable, the phone is not working (Obviously) since it is out of battery.
- As I hold down Power and Volume down, I can enter bootloader screen. I saw a "locked" banner and cannot navigate through the menu and can not press Fastboot or anything. After 2-3 seconds, the phone is shut down and keep looping.
Long story shot, can anybody tell me how to fix this. As I have a lot of pictures that havent been backed up, I really appreciate if I can keep everything without doing a factory reset. Oddly enough, I cant even do a factory reset since the bootloader is not working.
Please help.
Click to expand...
Click to collapse
looks like an hardware defect, maybe your power button is stuck?
alray said:
looks like an hardware defect, maybe your power button is stuck?
Click to expand...
Click to collapse
I dont think so man. It seems working normal for me. But thanks anyway
evelucife said:
I dont think so man. It seems working normal for me. But thanks anyway
Click to expand...
Click to collapse
"To restart the phone, keep pushing the power button for (x) second" with x is the count down number.
Click to expand...
Click to collapse
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.
alray said:
Because this is exactly the message we usually get when holding the power button for more then 5 sec...
and that would explain the reboot issue
looks like the "power" key is always active
definitively sounds like an hardware issue imo
and your issue is even present in bootloader what confirm that this is an hardware defect.
Click to expand...
Click to collapse
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.
evelucife said:
Yeah u has a point. Any idea how to fix that? Or I have to bring it to someone else to fix it.
Click to expand...
Click to collapse
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...
alray said:
You'll probably have to send it for repair. Better to contact HTC and see how much it will cost...
Click to expand...
Click to collapse
Thanks man. I will see if i can do.
So. My Moto G is completely un modded, not rooted, and is exactly stock how I bought it and haven't changed any of the software. My Moto G has been getting slower in the past couple of months with everything going slower than usual. I bought my phone in February 2014.
Yesterday while I was at school, in my pocket I had my phone. I felt random vibrations in timed cycles. So I pulled out my phone and had a lol at it randomly rebooted but came back to the home screen. As I started to use it just to send a couple of messages it rebooted again but this time after the reboot animations they just went on and on, what I've found out to be called a boot loop.
So I went home did some research and figured I would have to factory reset. I couldn't get into the phone therefore I had to do it externally. I got the the menu thing ( I think it's called fast boot menu ) and I wanted to select newer bootup or power up just to see if that would possibly stop the boot loop. I selected it and got into my phone, into setting and factory erased my phone.
Well I factory erased my phone and re installed the apps I on,y essentially use or NEED such a social media, within this time there was no unusual activity. Shortly after my phone randomly rebooted ( after downloading the apps ) and turned off, and then went in to the former boot loop! I was furious!
Well here I am, left it overnight for charge and it's been looping for 10 hours. I tried going back into the fast boot menu, the first time I got into it this morning I selected recovery in hope to reset it, however the screen said no command with the android and the exclamation point. The second time I got into the menu I tried 'Factory' and it just rebooted and back into the cycle.
At one point I did get into my phone however shortly after that guess what happened, it turned off and rebooted. And back into the vicious cycle.
I am led to believe it's the power button that's causing the problem ( correct me if I am wrong ) as when I did manage to get I to the phone I did try pressing the power button to investigate this and on some occasions in did lock the phone but in several others it displayed the power off popup and then turned off shortly after indicating that I was holding the button down which I definitely wasn't doing.
So where would I go from this? Do I call Motorola, try flashing a stock ROM ( it's completely stock ATM , I don't know how to do this so if I have to do this can you please explain briefly ) or try going back into the fast boot and go into recovery and try and get rid of no command ( if I can, and how ? ).
Please any help would be very appreciated!
Thanks in advance.
PS you don't think it's the back cover that's doing it because it took that off last night '
kevlarpatel said:
Do I call Motorola, try flashing a stock ROM
Click to expand...
Click to collapse
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
doppelhelix said:
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
Click to expand...
Click to collapse
Hi, I had a look online and came across a forum post saying it was a jammed or sticky power button and the poster stated to hit the power button side of the phone on a desk a couple times and it will go back to normal. I'm glad to say it did work after I hit it a couple times, as fast as ever now due to the reset!
I was wondering if I call Motorola would they give me a free new moto g out of it, as I see it as an opportunity to do so, or will they just prompt me to send it so they can repair it under warranty? Is it worth calling ?