So I have an lg g2x originally running gingerbread 2.3.3 and I went through this procedure -> http://forum.xda-developers.com/showthread.php?t=1259852&highlight=linux+g2x+root
Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down and tries to boot again.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
I am running linux and do *not* have access to windows at all.
Which LG screen are you getting? The static one or the one with a moving green bar underneath it? Can you still boot into Clockworkmod Recovery or was that a no go? You need to give more detailed information so people can figure out at what point in the boot process your phone is rebooting.
I get that initial booting LG screen with the face and the letters LG, there is no green bar. It sits in that screen for 15 or 20 seconds then attempts to reboot. Well, thats what I assume happens. The screen goes black, the buttons along the bottom flash and then after a few seconds that white LG screen comes back and it does it all again. It never gets past that and never into CWM. I can still put it in the flash mode that allows nvflash to connect and do its thing, but thats about it.
If you have successfully nvflashed cwm. Then you should be able to get into cwm by holding volume down+power until it goes to a blueish LG screen. Then flash a rooted rom from there.
That is the easiest/safest way of rooting a g2x. If you haven't done this you can Google "nvflash g2x Linux" and find guides on how to do it.
Sent from my LG-P999 using xda premium
Right, thats exactly what should happen. Unfortunately, its not what actually happens. During bootup I a can hold power + volume down all day long and get the exact same behavior. Its a bit disconcerting.
[solved]
Guys, I found the problem and figured I would post it here for future folks.
I was unable to start my phone plugged into the charge (both to the computer and to the wall). I had to have the battery in for this to get to a good place. I guess initial startup just took too much power.
So if you do this, after using the restore script. Press the power button and volume down hold both, then *put in the battery*. Thats what worked for me.
thanks!
Related
I have the stock 'v10c' ROM on a 'Rogers' LG Optimus 3D.
This morning I was using the Google+ Android client and - without closing the app - pushed the power button to put the phone to sleep and put it in my pocket.
About 15 mins later I pulled the phone out of my pocket and it was dark, but the touch countrols were all lit up. I know that usually isn't good news. The phone was unresponsive.
I pulled the battery and tried to re-boot. It gets to the Rogers screen and then boot-loops, with a flash of the Rogers screen each time it restarts a cycle. Roughly 15 seconds apart.
I did vol+down+Power (guessing based on other phones) and it booted into a recovery (3e) menu that only offered me the chance to wipe all user data. Ok. I moved the cursor down using vol+down and sletected "yes" with Home. The phone then presented a triangle logo and the green android and sat there.
Meanwhile...I Googled. After about 10 mins I pulled the battery again and did the Vol+down+3D button+Power boot to the REAL recovery menu.
I then did a wipe / factory reset from the recovery menu. I have assumed the Home button is the enter button (BTW).
Again the triangle and the green android appear. They are still there 10 mins later.
Not sure what to do now...the phone won't boot and the factory reset won't fix it. But it isn't dead. I can still get to recovery, so in theory this is fixable. I just don't have time for it right now. :-/
I was wondering if maybe the phone had updated OTA in my pocket and I didn't realise it and I may have messed up the process. But I have never seen a phone do an OTA update without first notifying the user and seeking confirmation...so I that probably isn't the case.
Very annoying.
I'm posting this here in case anyone else has the same experience.
Anyone have any advice?
[Update: The Menu button is the enter button...not Home. So I did a real factory reset and the phone now boots to the "Welcome to your new phone" screen. *WHEW!*]
Uhmm... if Menu button is home button that means u have problem with build.prop. I never met with this kind of problem, however I think u just should turn on usb mode in cwm, put a ROM on phone, flash it and see how this will be. Don't forget to backup ur rom.
Sent from my LG-P920 using XDA Premium App
Hi there,
I've got the same problem with my LG P920.
Then I read your thread and now I can tell you how to fix...
The recovery is the right way to fix, but the homebutton is not the menu button.
You have use the Options Button the first from the left side or the 3d-button.
Than you came to factory default and you can restart youre device.
best regreads
Morphix
Anyone know the glitch that is causing this?
Sent from my LG-P925 using xda premium
If've got the boot-loop for the first time and it happend after a reboot comand on the comand app...
I have the same problem and no idea why it happens ..
I had this 2 times in one week! very anoying..
Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
why not change the volume button, at gsm service.
It's a good phone.
compul said:
Hi,
long story short: while trying to install CM on my old one s I first flashed the boot.img as described here: h t t p : / / wiki.cyanogenmod.org/w/Install_CM_for_ville. It appears that the firmware overwrote the custom recovery on a reboot, and when I entered recovery to install CM I got a screen saying "entering recovery..." in pink at the top, htc logo in the middle, and "This build is only intended for development, to not leak from HTC" (something like that) in red at the bottom. Nothing happened.
I shut it down and started it back up, and it went to boot with the same htc logo and red message at the bottom -- and froze there. Only 10+ sec power button restarts it, nothing else helps. Weird enough I noticed that if it's on a cable it won't restart but just stay off, and if it's not connected it will restart immediately, no chance to switch it off.
Here's my biggest problem: my volume rocker is brocken. Up works somewhat, but down is 95% dead. I entered the bootloader through adb before, but since I can't boot the phone anymore I can't get in anymore.
It seems to me like the best solution would be to somehow fix the volume rocker. It's not 100% dead, occasionally I could get a keypress through, so I would just suppose the contacts are a little bad and I could just polish it a little? But the phone seems a pain to take apart.
What would you suggest? Is it too easy to break the whole thing while trying to clean the contacts of the rocker?
Thanks for any help / comments!
compul
Click to expand...
Click to collapse
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
null0seven said:
why not change the volume button, at gsm service.
It's a good phone.
Click to expand...
Click to collapse
While that is my last resort, I'd like to avoid it. I do have a working Nexus 5 after all.
TiTAN-O-One said:
Taking it apart is smth you can do. Ik its hard, i tried but if you're confident its your power button then do it. After you reveal the back of our phone, you can access the buttons
CM11 Powered G-Wonder
Click to expand...
Click to collapse
It's the volume rocker, not the power button; and it's been broken for a long time. I'm a little afraid I might rip things apart, but this makes it look outright easy: youtube.com/watch?v=6j25jajIq3g. I'll give it a try.
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
rexsis13 said:
So, yesterday I decided to reboot my phone since it was very sluggish for whatever reason. I think it shut down properly but when it came back on, there was a very interesting problem that had come up - it didn't boot any further than the logo screen, which didn't even play its standard animation; it just stood there with the LED on the home button changing colors (like normal). I left it on overnight hoping the problem would be gone, but to no avail. It still hadn't booted when I woke up. If it matters, the only thing I can boot to is download mode. It doesn't let me get to safe mode or however it's called (the menu you navigate with volume up/down and the power button). Needless to say, I was very puzzled. Then I went on and tried to flash the latest kdz since I thought that would fix the problem. I hoped that would easily fix the problem. But no, it decided to be funny and give me more headache. I tried using this guide: http://forum.xda-developers.com/showthread.php?t=2409308 but after step 20 the LG Mobile Support Tool crashes and I can't continue. Sure thing, I will try the Upgrade Recovery that the tool has built in. It properly detects my phone, the software download and extraction goes smoothly. Then I reach the S/W Upgrade part of the process. The few first seconds everything is fine, but then the bar reaches 5% and just stops. Just like that. Now it's been 8 hours since I began the recovery and no progress has been made.
Can anybody help me? I'm lost here...
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please post your question here:
http://forum.xda-developers.com/showthread.php?t=2257421
The experts in that thread will be able to help.
Good luck!
Thread closed.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.