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!
Ok. So i have completely screwed up my phone. I have rooted my phone and installed a few different ROMs on it. I have clockwork recovery installed on my phone and I was using it to clear my data to install a new ROM. I cleared my /system and then did a "reset data/factory reset" and I believe the factory reset is what messed everything up. Now when I boot up my phone it shows "Google" and has a little progress bar that gets to 100% and does nothing after that. My phone will show up on my computer as an ADB device but nothing more. When I boot into my bootloader, it freezes up completely. The volume keys and power button don't do anything.
I have clockwork mod installed but I can not get into it. My last ROM installed was Slim ICS from slimroms[DOT]com (I can't post links yet ) I'm not sure if that is needed but I thought I might throw that in.
Any help would be much appreciated. I am without a phone right now because of my toying around with it.
EDIT: I have solved my issue. I just came back to tell what I did in case someone else hits this problem. Every time I took the battery out and put it back in, my phone would instantly turn on. After about a million times of taking my battery and putting it back in, I noticed that every so often it wouldn't boot up (either because I put the battery in weird and readjusted it or left the battery out for a long time). Whenever my phone would not boot up on its own and I booted into the bootloader, everything would work great. Once I realized this, I left my battery out for about half an hour, put it back in, and everything worked out great. I installed a new ROM and my phone is back to the way it was.
I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.
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.
I just downloaded the update for Cyanogen Mod 13 and I clicked install then my phone powers on (no matter what buttons I press; power, power and volume up and home) it has the Samsung S5 logo and the text "Recovery booting..." (as well as the other warranty text stuff). It then quickly flashes the screen with the Android and cog logo with the text "Installing system update" for the shortest time (making it almost impossible to read the text) it then flashes this screen on and off every 5-10s for the rest of the time. I thought that the screen maybe just a little glitchy but the "update has been running for almost an hour now. How can I fix this problem if my phone doesn't allow me to put it into recovery mode .
So I spent about 3 hours trying to fix this problem trying every combination of buttons to press on boot as well as trying to make my phone detectable or something like that. Let my Mum try fiddling with it (she has no idea what she doing with new tech) some how she managed to press the buttons just right. It went into download mode and I was able to flash it with an update of TWRP using ODIN and it rebooted and started up. If you haven't already try putting it into download mode, I've heard getting the timing right can be tricky when your phone is doing unusual things. Now I'm unsure whether to try updating again but I might try wiping and going back to a stable 12.1.
Mod Edit:
Thread closed as ODIN fixed it