Yesterday was listening to Pandora via headphones, and the phone reboot itself to the "device may be corrupt screen" when bootloader is unlocked. While rebooting, the screen shut off and now the phone is completely unresponsive. The phone was running the latest Pure Nexus Rom with a Substratum theme.
Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.
TwiggieSmalls said:
Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.
Click to expand...
Click to collapse
yea seems strange, unfortunately I'm unable to do anything with fastboot as mine won't even boot into anything.
This happened to me as well. Phone just booted when to the corrupt screen and died. Obviously freaked me out. I held the power button down for a very long time and it booted back up. Please try that. Phone has been fine since then.
Thats scary. It didnt give any warnings (unusually high temps, glitches, random reboots)? Neither of you flashed anything other than PN in the days/hours leading up to the complete shutdown?
Im a bit paranoid since Im running the same rom. But everythings ok here.
Related
I'm running DamageControl 2.07.
I happened to be up in the middle of the night, and I caught my phone randomly restarting. I've seen it happen before but didn't pay it any mind before, but now this is starting to bother me.
Is anyone else experiencing this?
I have this too. Running DC 2.07.2 and when I'm doing something normal (tweeting on Touiteur, texting, etc.) and the phone doesn't actually reboot, it just..... shuts off. This happens at any battery level from 100 to 0. I turn it on and it's fine, but.... it's really annoying.
Yep i experienced this with all the new Rom base on DC. i dont really know how to fix but changing to an other Rom will fix it. The problem is almost all the new 2.1 Roms that came out are base on Dc so i flashed DarchLegend 5.0.5 and its been 3 days and my phone hasn't done that yet
noticed this too when running regaws mod. flashing darch now with the darchstar theme, gunna give it a go.
anyone know of a white taskbar(with 3g) for darchs latest rom?
I've had this happen to me even with stock 1.5, lol.
I don't know what causes it, it's a pain in the ass. It happened a few times after I rooted too. Lately I haven't had this problem anymore.
my phone rebooted on its own last night, second time thats happened. there was talk of this about 2 weeks ago and the thought is this is a battery issue, apparently a couple people bought new batteries and the rebooting didn't happen after.
Alright this is starting to really bother me now. It's rebooting like 3 times a day now. I keep thinking my phone is hacked.
It's happened to me before on 1.5... I was going to charge my phone overnight while I slept, and no matter what I did, I couldn't keep the damn thing to stay off. Everytime I kept plugging it in, it would just turn on again. Eventually I just pulled the battery, put it back in, and plugged it in and stayed off.
this is the first thread i read upon my return from being banned for 7 days. this sh*t scared the living f*ck outta my a**
ahem
sorry
it happened to me right after i installed the latest regawmod
i simple wipe and fresh flash fixed the issue immediatly
i also pulled my battery, and my nandroid was corrupted
i was scared. i was like damn, 7 says and i come back to this?!
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
I'd try just following the steps to update to super clean 2.4. some kernels act up on your version and drop the vibration. It happened to me. 2.4 is running awesome
Sent from my SCH-I500 using XDA App
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Spazguitar306 said:
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Click to expand...
Click to collapse
Try reverting back to stock again and prior to going back up to eb01 and superclean...wipe a few times.
I had a similar issue
Spazguitar306 said:
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
Click to expand...
Click to collapse
I had a similar issue. I actually flashed my phone all the way back to stock. Still no vibrate. I think there could be an issue with the vibrate motor on the fascinate.
I say that because there was nothing I could do to bring vibrate back. All of sudden, it began working again for one day. After that one day vibrate and haptic working, it stopped working for another couple of days. Then, I dropped the phone on accident. Vibrate came back. Eventually, it stopped working again so I took the phone to verizon and they ordered me a new one.. No charge. I bought my phone in Sept 2010.
Good Luck!
Hey guys,
Some how my phone got a virus and I believe the virus has completely wiped the stock rom. Last night, I took it to the AT&T store, they were able to boot into download mode. It gave a warning saying a custom rom could break installed apps or something.
They gave it back to me, and I figured I could just reflash the rom since it was somewhat bootable, so I turned the phone off until I got home.
Once I got home, I tried booting into download and the phone isn't responding at all. I've tried all of the button combinations, tried a different battery, tried charging over night. Nothing has worked. After a while last night, I was able to get a vibrate and the screen would flash a 1px line across the screen and turn back off. This morning however, I am not getting anything.
Not sure if there is anything I could do at this point. Hoping someone has a way to force download through the computer or something. Never had any problems with viruses, always been cautious. Its really frustrating. I know viruses can be really nasty, but can it seriously delete everything including kernal or Samsung's bios?
Thanks for the help, don't think I have any options but hoping someone is a wizard and can help.
Hi all,
My galaxy s5 is stuck in a reboot loop. It started doing this today around 12:18pm and I can't get it to stay on long enough to back up my data. I took it to AT&T and they basically did nothing but tried a different battery and booted into safe mode. Neither of those options worked. I took it to best buy and the tech installed the latest updated and flashed the ROM (I believe). Still didnt work. She believed the issue was with the battery but didnt have any new ones there to test so I went to batteries plus and tested a brand new battery, still is rebooting. I am home now and just wiped the cache in recovery mode, still not working. Is there anyway at all I can get this phone to turn on long enough to backup my data? Any other commands I can try to clear whatever is causing this? I was not using my phone when this happened. It died at 15% which I didnt make too big a deal of because I know the battery has been weakening, but when I charged it up for a bit then turned it on, this problem started. When I turned it on, I had a text message coming through and then it restarted. As I was able to get it on for a bit that same text kept coming in over and over again so I thought maybe something with the messaging app and I disabled that all together but the problem remains. I hope someone can help me out here. Thank you.
SOLVED: Samsung Galaxy S5 Reboot Loop
I figured out a workaround and I take full credit because this creative solution was no where to be found on the internet nor did AT&T, Samsung or Best Buy offer any other alternatives aside from wiping the device. This is what I did:
I booted back into Recovery mode and looked through the logs for any indication of what was happening. My assumption was that it was a driver error and so scrolling through the logs I saw an error that said something like fail psy battery. I immediately think maybe its the drivers for power so I thought I'd see how it would respond if I put it in Ultra Power save mode. Thankfully the phone stayed on just long enough for me to put it ultra power save which did work. The phone stopped the reboot cycle it was stuck in but I still was not able to back anything up since the Ultra power save disabled the USB drivers and port. I let it charge up overnight in ultra power save and said I would try regular power save mode in the morning to see if that would also work but this time allow me mass storage access. Well, that worked! I put it in power save and I am backing everything up now as I type. I've got all my pics and now just letting samsung switch do its thing to perform full backup. YAY! I WIN! Hopefully this helps someone else that may have this problem and have tried everything else that is recommended for solving this issue.
-Natasha
Chicago, South side born and raised
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Aimara said:
Don't really get it, what cause the boot loop in the first place? And you are flashing back to which rom?
Click to expand...
Click to collapse
samsungGs5 said:
I don't know what caused. I wasn't using the phone when it started. I hadn't downloaded any new apps and I wasn't messing around with the OS or system files. The phone battery died at 15%. I plugged in the charger and disconnected when it was at about 28%. I powered the phone on and there were a number of text messages coming through from my friend I was going to lunch with. I opened that message and noticed the text was duplicating itself then it rebooted. Each time I powered it up and got in for a bit that same text was coming through or trying to over and over again. So, I don't know what caused it but I have all of my data backed up and I am going to wipe it now.
Also, the Best Buy tech flashed the ROM so I am not sure which version or anything like that.
Click to expand...
Click to collapse
which os phone on ? lop or MM ?
So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd
Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.
ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.
Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.