Develop Bugs

[Q] What the hell just happened??

So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)

zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.

Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...

i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%

It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.

Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...

I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal

May I ask what rom are you currently on?

datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel

It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...

I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.

zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness

Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...

http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app

datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.

Verizon G4 crashed

My G4 seemed to be running hot yesterday and I had to charge it several times more than normal. All of a sudden it shut down would not boot back up. I tried everything but it will not go in to recovery or download mode. No lights come on at all when charger is connected either. One time I was able to get the MEIE number to flash and it said press power to reboot before it blanked out again. I called Verizon and they said it sounded like a complete system/software crash. I am rooted but haven't made any changes to my phone in several weeks. Verizon overnighted a replacement to me and it should be at my house when I get home. I wonder if this is the same issue that has been happening to the Sprint version that was recalled? Possibly the phone was just mad at me because it happened an hour after I ordered my Nexus 6p......lol

Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.

Colchiro said:
Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.
Click to expand...
Click to collapse
No it still doesn't boot up. I can get to the LG screen for maybe a second and it shuts back down. When I first noticed that it was hot I could reboot it. I let it cool off before restarting it but the problem persisted. What ever was causing it to overheat was also draining the battery. I had to charge the phone up twice by 2:00 pm. My "certified like new replacement" arrived on Friday and initially everything was good. On Saturday the Wifi disconnected and would not turn back on. The icon just sits there and blinks at me. If I go in the settings menu it is grayed out and doesn't give me the option to turn it on. I just got off the phone with Verizon and they are sending me another G4. Hopefully I will have better luck with this one. I would like to have a working phone that I can sell when my Nexus 6p arrives.

Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?

sefirosu0522 said:
Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?
Click to expand...
Click to collapse
No I didn't. It was Warranty replacement so it didn't have to go through insurance.

I had a similar issue last week, no root, running 12a. Phone shut itself off during normal usage (checking football scores). Running a little hot so let cool. Never booted past Verizon splash screen. Tried fresh battery, factory reset, safe mode. Nothing. Got my "certified like new" model. So far so good, but 6P here I come.
Sent from my VS986 using Tapatalk

Hmmm well good timing if you ordered a Nexus 6P. You can sell it like new.
Haha I was just watching "The Nexus 6P will bend in half if you try to bend it in half" video. I'd be interested in a size comparison between the 2.

So this exact thing happened to me, just several days after I got it (same thing, also rooted, nothing much done to the phone).
I had figured the battery ran dead (because I knew it was low), but it just wouldn't power on. Chargers wouldn't light it up. I put it on the charger for hours, and nothing happened. Lost all hope.
Then, randomly, I decided to see if Download Mode would work on my phone. I don't know why I tried it.
I pulled battery, and put it back. I held on Volume (up?) on the phone, and plugged it into the computer.
OH MY GOD -- IT CAME TO LIFE -- ! DOWNLOAD MODE!
I shut it down from download mode, then turned it back on (I think a battery pull) and it worked again.
I was completely relieved.
This happened to me a second time, weeks later.
The same solution worked.
I hope that this helps someone.
TL;DR: Try Download Mode (pull battery and put it back in -- then, while holding the volume Up key on the phone, plug USB into your computer)

Nexus 5X randomly dies and then I can turn it on again only when its battery hits 0%

I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.

I have had the exact same problem, mine only occurs when the phone is ran down to 0% and powered off. I never let that happen but I have a 3 year old son who repeatedly does it, and every time i hold my breath, praying it will come back on. Well i am holding my breath and praying once again this morning,hoping it will power back on. Do you think it could be some kind of "protected mode"to keep the battery or something else from overheating or whatever?

alezmoroni said:
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
Click to expand...
Click to collapse
If you need the phone and are confident, try unlocking the bootloader, reflashing stock factory image and relocking the bootloader again. You will lose all the data, though.
If you can live without a phone for a while, just send it to Google/LG. Nothing else one can do imho.

When my phone was in the last steps of dying (eventual bootloop), I could disconnect the battery and it'd get farther through the boot cycle, or even once booted. Basically, after it wouldn't react to any buttons or combos, I would disconnected and reconnected the battery. Then I could give things another shot. So I'd start it, it'd make it to the colored circles, or I could boot to the recovery menu, and try some things, but at some point it would go black. Then it would not react to anything unless I disconnected the battery. Then it would react to the buttons again and eventually one of the steps would make it go black. And then take a disconnect to get another try.
It sounds like your phone may be close to dying.
By the way, I only opened it up since I was past the warranty expiration date, and LG extending the warranty to about 18 months wasn't a known thing at the time. It is actually easy to get everything apart, but hard not to make dings in the plastic cover even using plastic tools.
I would say, back up everything you can from it and expect it is going to get worse. Redoing the OS didn't save mine.

Nexus 5x won't turn on

My nexus 5x just doesn't boot up.

I had the same problem twice, last tine a few weeks ago.. A solution by a friend; Put the device in a plastic sack, close it very good. Then put the (enveloped) device in afreezer for a least 8 hours. After this time the batteryis absoltely empty. Now close it to yor USB-Lader and it takes only a few mitutes that in runs again. It worked for me twice, nd in worket with other deviceslike Samsung and Huawei.

I had it also some days ago but I had no time to put it in the fridge or just wait to fix it by itself.
My trick was to open the back cover and remove the battery connection for some seconds. After re-connecting it started up right away.

I have the same problem. I just want to turn it on to download some of my data. I have tried putting it in the freezer though only for about half an hour to an hour. I'm afraid the condensation may damage it too much.
Someone advised me to put it in the oven for a bit (lol), not sure if this is actually gonna do anything.

I tried that heat gun multiple times, put into freezer for about 4 hours, removed battery, charged it 5 days in a row.
I only managed to get the red light flashing, but it still wont turn on.
Is there anything more to try?
I personally think the battery is completely dead, but I dont have another battery to try it out.

I know this is an old thread but thought I'd post this anyway in case anyone is still trying to fix their Nexus 5x. I've tried everything to get a sign of life out of this phone, nothing worked. I was messing around with it and without even paying attention to what I was doing, I was holding just the Power button down for somewhere between 1 and 2 minutes and out of nowhere the phone vibrated. Looked at the screen and sure enough it booted up just fine! Can't believe it! If anyone reads this and gives it a try, let me know if you have any success.

Replaced screen and battery, now in (another) bootloop!

Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?

Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.

bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.

I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated

I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good