Several days ago I was watching a livestream when my phone froze & suddenly went into bootloop. At this point I've tried all that I know to - I've flashed several different OS versions using the Nexus Root Toolkit, I've manually flashed 6.0.1 & 7.0 (not sure if 7.0 was a good idea to flash tho just because of what's been happening), and at this point I'm not even able to go to the recovery to manually do anything. At one point the phone did work, but it would constantly go back into bootloop for a few minutes before coming back out, but now it is simply stuck in bootloop. I was using Android 6.0.1, stock. The phone was rooted for awhile, but I eventually unrooted and went back to stock. I don't understand what happened, and everything I find on the internet about Nexus 5x bootloop is in relation to the 7.0 update, which I did not bother downloading (luckily lol). Is my phone gone forever? :/
I got my phone replaced some time ago as it also went into a bootloop mid usage. Flashing anything didn't help. My finding was, that the phone worked as long as it was cold. Leaving it off to cool down and putting it on a cooling pad helped for about 10 minutes. From what I understand, it may be a hardware issue.
Gesendet von meinem Nexus 5X mit Tapatalk
See the other threads on here that showed up within the last 1-2 Weeks regarding bootloop, bricked or QHSUSB. Chances are, it might very well be a hardware problem (bad soldering).
My nexus5x suddenly died 5 days ago (with no prior symptoms). Unlocked, no root, stock 7.0 november update.
I was able to turn it on once for ~3hrs after walking outside for 20 minutes, right after it first froze down/bootlooped.
Then it showed up as "QHSUSB_BULK" (8009?) when connected to a pc, but would not even start fastboot anymore.
I tried putting it in the freezer in a plastic bag for ~10 minutes. Fastboot worked, booting freezed inbetween; twrp would not let me enter security pattern.
So I let it rest for two days. Then decided to give it one more try by putting it on my radiator for 20 minutes (just warm, not hot! - please don't panic and make the situation even worse!)
Got it to boot up regularly and keep it on for ~20 minutes. So was able to do one last backup of msgs, imgs, etc. (while still on the radiator). Booted up successfully two more times, but with every decreasing on-time.
RMAing now through Google.
Related
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
I have a early LGG4 from sprint, one of the first. Things have been great, was starting to think I was one of the lucky few.
Yesterday I set my phone down and about 45 mins later when I returned it was at the boot screen, and hot. I pulled the battery and let it cool. Since then I'm in a boot loop for the OS, however I can get to recovery. Sprint is ordering me a new phone, but I have 3 days to wait. I can boot into recovery and it seems to not freeze/reboot there. From time to time I can get my phone booted but it freezes and reboots within minutes.
Yes, same happened to me - H815EU, phone replaced. If you have TWRP there is no prob with backup. If not... maybe thru adb/fastboot.
Phone rebooted on me a couple times yesterday, then started doing it more and more frequently, about every 5 minutes. now, it mostly just sits looping at the HTC splash screen. Usually can't even get to recovery, reboots before it has time to load, or sometimes makes it, but dies before I can select anything. Managed to get it factory reset finally, but no luck. Sometimes it will eventually boot after 10-20 minutes of looping, and stay on for a minute or 2. Everything was bone stock (although bootloader unlocked) before this, had been running fine for months.
Any ideas before I buy a new phone?
lkrasner said:
Phone rebooted on me a couple times yesterday, then started doing it more and more frequently, about every 5 minutes. now, it mostly just sits looping at the HTC splash screen. Usually can't even get to recovery, reboots before it has time to load, or sometimes makes it, but dies before I can select anything. Managed to get it factory reset finally, but no luck. Sometimes it will eventually boot after 10-20 minutes of looping, and stay on for a minute or 2. Everything was bone stock (although bootloader unlocked) before this, had been running fine for months.
Any ideas before I buy a new phone?
Click to expand...
Click to collapse
Try installing a RUU for your version, if it stays on long enough.
If not, take it to warranty.
Good luck!
Hi,
today i had a strange problem with my nexus 5x, I was on WhatsApp and studently my phone freeze and rebooted. After that it was stuck in a bootloop, I first tried to flash the recovery images but after the flash it was still bootlooping.
I tried to use a tool that WugFresh made, I used the “Soft-Bricked/Bootloop” mode to restore it. After 20 minutes of bootlooping it finally booted properly.
BUT after configuring the phone it freezes again and same as before, it bootlooped. This time I let the phone do his business and after a while it rebooted (20 minutes again)
After each reboot, the phone works fine for 20-30 minutes and freeze and reboot again. I tried to film, take pictures, watch videos on YouTube and it worked fine each times (it freezes after I wanted to skip an ad on YouTube).
I tried:
Restore multiple versions of android (the first release and the last one, I didn’t use a older version of Nougat)
Used the WugFresh to flash the images
Erases all the partitions with flashtool commands
I want to discharge completely the phone and charge it back again (I thought that the battery was the problem but because it freezes randomly it might be something else)
Don’t know if someone had the same problem.
Here are the logcat after the phone rebooted : http: // pasted . co / 9296e1ba
I'll try anyting you'll recommand
Thank's in advance
It is easier to write than read, right?
Dunno why everyone thinks that his problem is so special
Im having the same problem as yours. Started 5 days ago, after putting the phone to charge and gone shower. After it my phone was rebooted in the boot-password screen, already gone back to 7.1.1 (was 7.1.2 beta2), flashed O and no solution. Still bootlooping and booting correctly after 10minutes of bootloop. It works for 20-30 minutes or less and freezes again. Sometimes works for hours.
My thread: https://forum.xda-developers.com/nexus-5x/help/nexus-5x-getting-stuck-google-logo-t3580223
My phone is not at warranty time and Google cannot help me.
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.