HELP!! S20 Ultra stuck in boot loop during REGULAR USE, Wont go in Recovery Mode!! - Samsung Galaxy S20 / S20+ / S20 Ultra Questions &

Hello all,
I need some serious help here. I was using my Samsung Galaxy S20 Ultra when DURING USAGE, the phone decided to reboot. It is rare but it happens. But the problem escalated when it refused to reboot again. It has constantly been in a boot loop ever since. It did fully RESTART TWICE in the middle but before I could unlock the phone it slipped back into its boot loop coma.
Everything on the phone is stock, updated to the latest versions for all I know. No combination of power and volume buttons help. What it only does it switch it from boot loops to a static boot screen.
ANY HELP OR EXPLAINATION WILL BE APPRECIATED !!
Sincerely,
SRV

These phones should never spontaneously reboot. That indicates a potentially severe problem; always take any sign of system instability seriously. Often it's the only warning you get before a boot loop.
You need to get into safe mode or the boot menu to do a factory reset. Make sure you're using the proper sequence and timing matters. Try holding the power button down for at least 30 seconds.
Poorly written apps can do this. It may be the firmware was corrupted (possibly a single event upset) or a hardware failure. Play with it...

@blackhawk
I have tried:
power button hold for long
power button + volume up
power button + volume down
all three
The current situation is:
It is stuck on boot screen for 5~10 random minutes then starts cycling again. What do you figure could be the reason for it to have fully restarted (then gone back bootlooping) when the situation was fresh ?
Do you think i should let it drain out ? (How long would it take lol)
Perhaps try unplugging the battery/ removing SD card WHILE its still booting ?

Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?

My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.

planeinmountain said:
My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.
Click to expand...
Click to collapse
You weren't able to get it in recovery at all right ? and how much did it end up costing you ?

blackhawk said:
Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?
Click to expand...
Click to collapse
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.

panzer27 said:
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.
Click to expand...
Click to collapse
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.

My wife and I also experienced a similar issue with our S20 Ultra 5G. Except ours was an update that literally just killed the device. We tried every combination of buttons to get into recovery or bootloader mode with no success. Ultimately we had to send the device to a Samsung service center to have the LCD, battery and motherboard switched out.

blackhawk said:
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.
Click to expand...
Click to collapse
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?

panzer27 said:
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?
Click to expand...
Click to collapse
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.

blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
I am dead sure it is Malware.
I got it up and running and looping a few times now. The battery draining probably cleared some flags that prevented a normal reboot.
Phone has survived a minute in safe mode. Let's see

blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?

panzer27 said:
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?
Click to expand...
Click to collapse
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.

blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping

blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?

panzer27 said:
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping
Click to expand...
Click to collapse
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.

panzer27 said:
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?
Click to expand...
Click to collapse
As long as you flash the correct stock rom. Make sure it's the right one!!!
Not sure about the best method. Make sure you find out what is the best shot as you could hard brick the phone if you goof this up.
Throw it to Samsung if in doubt.
I've been fortunate and never had to do this. One reason I leave the Android firmware alone, avoiding even upgrades and updates. Android firmware flashing is the most complicated I've seen. A PC bios or a Canon Pro shooter, router are a snap to do by comparison.

blackhawk said:
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.
Click to expand...
Click to collapse
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.

panzer27 said:
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.
Click to expand...
Click to collapse
Update or reflashing the stock rom?
You should never interrupt when it's flashing. Yeah it could definitely at least soft brick it.

Related

a very strange hard brick

Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )

[Q] SPH-L710 reboots in recovery Battery, power button issues possible

I have read the other posts regarding the rebooting issues of the Sprint Galaxy S3 variant, but I seem to have a touch more difficult problem. My phone constantly resets and seems to be getting worse. It now will reset in the middle of recovery. I was able to wipe the cache and dalvik and then it started resetting even more frequently in recovery and made reloading the rom impossible. It even resets in the download screen. So it makes it impossible to use Odin and other applications. If anyone has any ideas let me know. I have a few possible options that I am pondering. The following is what led up to this if you need some background:
A week ago, I noticed that my battery suddenly was not charging when wifi was on. I turned it off thinking it was some glitch and reset the phone and plugged it in to charge. It said it was at 100 % some hours later. then I turned it back on again and within a couple minutes, it said it was at 22%. So I hard reset and then plugged it into the wall, but it was still not charging. I had go somewhere,so I plugged it into the car charger and enabled fast charge. I turned on my data and all the sudden it rebooted, lost my wifi password, but when it came back on, it was charging properly. So I thought it was just some odd glitch. Charged properly for days.
Then I noticed the phone starting to randomly reset maybe once very other day when texting. I was actually going to put on a new rom tomorrow thinking maybe my old one had become corrupt. Then it suddenly increased drastically tonight to where it was starting to reset constantly. I thought maybe the button was stuck, and pulled off my otter case to make sure it wasnt being pressed down oddly, but it continued. Then I went into recovery and was able to wipe the cache and dalvik before it got really bad and now it won't even let me stay in recovery for any length of time. I almost got a rom loaded when it reset and its been resetting faster than ever. Becoming unresponsive to button presses as well. Even when I could get into the recovery, it would keep showing "swipe screen to open," as the power button was apparently continuing to activate or the phone was trying to reset itself. And yes, I have tried a battery pull several times and then tried to get into recovery, only to be booted out right as I see the recovery screen if I get there.
So that is my problem. I can't flash odin or anything else as the phone just keeps resetting. Part of me thinks to get a new battery and try to see if that doesn't solve my issue, as maybe the battery is causing the phone to reset? But part me is also thinking maybe the power button has gone sticky suddenly? It won't charge it seems as the red light will not come on and it keeps resetting before the battery charging icon can even come up. Any help or advice would be appreciated. I am leaning towards the battery going bad suddenly and shorting out the phone. I now have the battery, which last I saw was at 48% (It was charging when this happened), out of the phone and am waiting till morning to hopefully pick up a new battery. But I would appreciate any insights into this issue.
Thank you very much
Same issue
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
I just had my phone replaced for same reason ( Thank god for insurance) Download mode would last about 5 seconds, Recovery would do the same. I managed to get a stock restore with flash counter reset to boot as i was walking into the Sprint store for the techs to look at this lol.. Same exact thing happened on my S2. Power button is done. If you have INS call and get it replaced (Took me about a week for new phone)
I read some post on possibly using Samsung Kies to flash a new ROM, but that was for the international version. I would be curious if anyone has ever tried this or if its possible to replace the power button with a part replacement? I have ordered an S4 but this time I will make sure to use the home and left touch pad more often to unlock the phone and save wear on the power button. I wold still be interested f anyone has found a fix for this.
mawamd said:
I'm having the same issue described above with the S3 constantly rebooting. I can get into download mode but it restarts a few seconds into the flash. I have tried a different battery but that did not solve the problem - I am also thinking it's a power button issue... any suggestions?
Click to expand...
Click to collapse
So after looking around, I am pretty convinced this the power button,as people describe on this question. If you don't have insurance, I see there are selling replacements or you can pay someone to replace and fix the power button fairly affordably on ebay. I might go the second route, as I want it fine right and the man had a 100 percent rating positive, and I dont really know what I am doing lol. Thanks everyone for your answers.

Boot Looped

Hello,
Today, while I was using my phone, it restarted itself and has been stuck at a boot loop almost entirely since then. It has successfully booted up 2-3 times but will usually restart itself within 30-45 seconds of booting and then will be stuck in a boot loop again. When it has started up its usually after it has been bootlooping for a while. I have an H811 , I'm rooted and using xTreme Rom v2.0. I have had occasional random reboots here and there before but the phone always booted right up again without any issues. I haven't done anything with root/recovery since early September.
I've tried doing a factory hard reset without any luck. My phone booted up after I tried the hard reset and it was like the reset didn't happen. I can't boot into TWRP. I can boot into download mode and I tried to reset using kdz. It got to 100% but the the phone restarts and is back in the boot loop (then the lg flash tool gets an error and force quits). I've tried removing my sd and sim cards, I've tried swapping to a different battery, I've tried leaving the battyer out and letting the phone cool down. Nothing is working. I have noticed that when the phone is going to boot up correctly the full LG animation plays. When the phone is going to boot loop I only get a static LG Powered by android image.
Since I tried and failed to reset to stock using kdz, the phone no longer boots up past the LG screen. I've redownloaded the kdz file and tried to reset again with the same results. When I have it in download mode Windows recognizes the phone but it says there's an issue with the MTP driver. I've reinstalled the drivers and I still get that the MTP function isn't working correctly.
Any suggestions?
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Yah mine was also on charge while it happened. But it was on LG provided charger.
nipun1110 said:
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
HappyPessimist said:
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
Click to expand...
Click to collapse
They will give u a replacement. that's all. but noone will say what's causing it.
Sent from my LG-H815 using Tapatalk
HappyPessimist said:
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
Click to expand...
Click to collapse
Exactly what happened to me. now after CSE flash of KDZ, it won't start at all. just boot looping. also after hard reset.

Corrupted hard drive= dead Pixel C

Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
xm0is3sx said:
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
Click to expand...
Click to collapse
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
Tell us please, how the replacement device. Because I am from Russia and I detail it is important to find out how things are going.
dkryder said:
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
Click to expand...
Click to collapse
im guessing the battery was around 80% when it decided to mess up so i think it got stuck formatting the hard drive and just died from there
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
any guess why this happened to yours? im thinking it might have to do with the magnets inside the pixel C i did stick it on the fridge to see if it was pretty strong (dumb yeah i know) lol it did work fine while stuck to fridge but messed up a few hours after that
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
thats the same message i got also after turning on the display I also have a keyboard and took it off to put the tablet on the fridge and put it back on the keyboard afterwards and it still worked fine until i turned the screen off and tried to turn it on later
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
yup, this has happened to mine several times but except for one time, i just pressed vol dn & power to get to the options screen and rebooted. so i did not have to reset but one time. but mine has not died yet. i also think the magnets might be causing this and some other issues
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
You guys could always try to unlock your bootloader from fastboot and reflash the stock images.
PriyanPhoenix said:
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
Click to expand...
Click to collapse
God I hate dealing with non-technical customer service reps, the devs from Dolphin Browser didn't understand portrait vs landscape, I ended up stopping the conversation because I'd rather beat my head against the wall. Same thing goes for Wizards of the Coast and Magic 2015, I asked then why all my data on my tablet didn't sync to the cloud since it was using Google Play games so I could continue the game on my phone and they just kept on saying "It's not meant for phones so that's why it doesn't work" even though it actually worked perfectly on my phone, they also kept calling me by the wrong name, even after multiple corrections.
Sent from my Pixel C using Tapatalk
I have the EXACT same problem on my 32GB pĂ­xel c, i am returning it.
Enviado desde mi XT1039 mediante Tapatalk
Same here
Okay, same boat here. Just received my Pixel C two days ago. Pretty neat to use, put always fully charged. Several unresponsive(freeze) occurs to me, especially when I tried Lens Blur feature in Google Camera. But overall I'm pretty satisifed with the experience and design.
Today I got onboard of a airplane. I guess it's after X ray security check machine... then I opened the tablet it prompted me with password. And the following with sort of "your drive is corrupt but we can restore it from Google backup" things. I clicked next (it's fully charged by now) and the looping restart begins. I can't even turn it off until I find the vol down + power trick to enter the recovery menu. But right now it's completely unusable. I think I'll request a order returning when I'm back...
I've just had the same experience on a third Pixel C, this time after about a week. I think this time I'm just going to demand a refund. They've failed to send me a single working device and don't seem to have any fix for this. I can't go through a continual process of RMA-ing and losing any data not yet backed up indefinitely.
What country are you guys from for those of you having issues? I'm in the USA and bought mine as soon as it launched and haven't had a single issue with it, meanwhile I see a bunch of people are having random QA issues which seems to be pretty odd.
Sent from my Nexus 6 using Tapatalk
I'm in the UK. I bought at launch so I'm well outside the 30-day window, but I've gone through three different units. On the plus side, they agreed to a refund with no hassle at all so I assume this isn't an isolated issue. Thanks to Amazon Prime I'm already setting up a Sony Xperia Z4 and, whilst I'd still prefer stock Android and the Pixel C 's aspect ratio, I'm actually pretty impressed with it so far...
Same thing here.
Did your replacement function?
Some premium tablet
Screw Google for not sending a USB C to USB A 3.0 cable so I could at least attempt a ADB factory flash.
God I hate dealing with non-technical customer service reps,
Click to expand...
Click to collapse
You know "boot loop" isn't a technical term right??

Is my phone lost?

So i have had my zenfone for awhile now. i unlocked the bootloader and was able to root it with a temp CWM. it was going fine for a long time.
Then one day my phone started to act up. wouldn't read texts right, false notifications, and app crashing. i thought maybe i had a virus so i ran a cleaning app (Clean Master and Lookout) but they found nothing. so i thought why not restarting the phone? seems to work for some.... *sigh*
Upon restarting the phone i am now stuck on the ZenPhone flip case thing... with the info on the circle. i thought maybe i dropped my phone sometime or somewhere and the case got stuck. okay simple fix, i tried using a magnet to open the case... and it did nothing.
Then I tired going into recovery mode by going through fast boot. but selecting anything in fast boot causes the phone to "freeze" and endlessly vibrate. It can't even detect when its plugged into the computer so i cant do commands on it from fast boot. i cant even do it from the OS as i think when its in the flip thing it doesn't allow PC access (at least i think). but the strange part about being on the OS, is that when phone goes to sleep (screen turns off), it "freezes".
What i'm asking here is there a way to fix this or is this phone lost. i made this account just for this... please help!
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Chocketbear said:
Good luck, I wish I had never bought this phone. I've sent it back to A-Sucks two damn times and it's still nothing more than a phone that always has some kind of an issue.
Click to expand...
Click to collapse
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Sonrio224 said:
Well i'm not one for giving up so easily. tho i am stumped on this, i would like it if i didnt have to send this back to asus... plus i think i voided my warranty.
Click to expand...
Click to collapse
You have a different issue, yeah don't send it back.
Maybe you can try twrp manager app to flash recovery if you can boot the system
titou4488 said:
Maybe you can try twrp manager app to flash recovery if you can boot the system
Click to expand...
Click to collapse
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Sonrio224 said:
I tried that. my computer, or any other computer i tried, doesn't detect its connected when in fast boot nor in the OS.
when trying to use the normal recovery on the phone. it gets stuck in an endless vibration until i turn it off.
Booting into anything (i.e. Normal boot, recovery) from fast boot causes the vibration hang
Click to expand...
Click to collapse
Re-read that, nothing was said about the PC...
ultramag69 said:
Re-read that, nothing was said about the PC...
Click to expand...
Click to collapse
my bad... either way, i still cant get into the OS as its stuck on the ZenPhone flip case thing as i stated above. it wont let me do anything from there.
if the phone cannot be saved. i might as well sell it for parts.
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
ultramag69 said:
Before that, have you tried totally discharging the battery, leaving for a day or 2 to get rid of any last traces of power from the RAM then recharging and starting up again?
Might be something screwy going on with the phones hardware but these things are literally PC's and sometimes they need to have a good shutdown to get rid of all the quirks stuck in ram.
If you don't want to wait, you could just open up and disconnect the battery. You were only going to sell as parts anyway....
Click to expand...
Click to collapse
haven't tried that. ill fully drain the battery and see where i get
Okay so good news. that actually worked... i think. i took the battery out for a bit and let it sit, then i put it back in and it booted up just fine!
but now i have a new issue, i can no longer talk on phone calls. speaker isn't working for some reason. might have put it back together wrong.
all things considered, thank you so much for the help!
No worries, good luck on the speaker issue...

Categories

Resources