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.
Related
Hey all, first time poster. I wrote a real nice explanation of my problem, but i lost it so anyways, i'll keep it short(ish).
The EVO is less than 3 weeks old, running the latest OTA, recently rooted using UnrEVOked 3, nothing fancy. I ran the battery down completely last night (first time since i got the phone) and once i got to a power source, it wouldn't boot correctly. It hangs at the white splash screen, and then finally boots up but won't respond to any touch input.
Also the phone seems to be running exceedingly slow, the boot process takes substantially long than normal once it gets past the splash screen and my live background is freezing and seems to be stuttering.
I launched into the bootloader and i get a "Touch Panel - Fail". LAME!
I'm not sure what to do at this point, whether i should wipe it or go back to stock or what. Any advice would be much appreciated.
UPDATE:
I managed to get the phone into the recovery console, make a back up (i was planning on going back to the stock image) and wipe the dalvik cache and fix permissions. I rebooted and voila! fixed. Hopes this helps any one else who has this problem.
Moral of this story: Travel with a charger.
Another update. It froze up again in the middle of sending a text. I rebooted by battery removal, and it did the same thing again. Super long splash screen and sluggish boot up, no touch response when it finally came up. I booted into recovery and cleared the dalvik cache again. Seems to be working again now. We'll see if it does it again.....
Well, the screen locked up again. I tried going through the whole process again. I wiped the caches and battery stats, nothing. I wiped all the storage and data, booted into a clean stock interface, nothing. Restored the backup image, and then at some point, through all the rebooting and whatnot, it just shut down completely. I can't even get it to the bootloader. I'm really feeling like it's a hardware problem, and i've made peace with sending it back for TEP, but i have no way to unroot it.
Any suggestions? Please......
Theres unroot processes out there. I cant remember where but ive seen them. Mine gets sluggish too, but after a reboot its ok. You cant even get into the bootloader tho. I'm not even close to an expert but.......uh I'd 'lose' it and call the insurance co....
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 NOTE 4 that was just sent to me as a replacement from Sprint. It came with Lollipop loaded. I rooted using Chainfire autoroot. When I loaded the phone it told me that I didn't have root.
I think used the battery pull method to try and get TWRP to load. So I ran CF-Auto (I know I used the correct one). This time I unchecked auto reset or restart. I pulled the battery and went into TWRP manually
Once there I flashed the BOBv2 and Noterized Rom as well.
Each time I reboot with either of them it just HANGS and the yellow Sprint spark screen. I have tried to wipe cache, I did the factory reset with TWRP. I reflashed them...still NOTHING. Just hangs at that screen regardless of what ROM it is. Please help.
Are you giving it time to load? Maybe like fifteen minutes.
Yeah, got to give it at least 15 minutes to boot up after that. Hell I've gone up to 25 minutes.
It takes a super long time not like pre lolipop days. It make me hate flasing as much . Everyone phone takes super long to boot . It will just be patient. I wasted my time thinking it wouldn't boot to. Then i listened to everyone and they was right takes a long time. Let us know how things go
ART, known as Android Run Time can be a pain when loading your applications and optimizing the device. But once it's all loaded, your device will fly.
Thank u guys. I was just being impatient
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!
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.