So I came across a Nexus 5x where the previous owner has not rooted or unlocked the bootloader and it has stock recovery. It is on constant bootloop. As it's bootloader locked and stock recovery is there any way to resolve the issue or am I toast?
Be advised I have not purchased this phone yet. Merely communicating with the current owner.
Any advice would be greatly appreciated. Thank you in advance
Edit. Owner says it does not get past Google logo and he guessed it bootloop a around every 10-15 seconds. He does state it can go to stock recovery but will not stay....It bootloops from that after a minute or so.
Is this phone completely screwed?
Sent from my Nexus 6 using XDA-Developers Legacy app
ozzmanj1 said:
So I came across a Nexus 5x where the previous owner has not rooted or unlocked the bootloader and it has stock recovery. It is on constant bootloop. As it's bootloader locked and stock recovery is there any way to resolve the issue or am I toast?
Be advised I have not purchased this phone yet. Merely communicating with the current owner.
Any advice would be greatly appreciated. Thank you in advance
Edit. Owner says it does not get past Google logo and he guessed it bootloop a around every 10-15 seconds. He does state it can go to stock recovery but will not stay....It bootloops from that after a minute or so.
Is this phone completely screwed?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'd ask the owner if he boots into fastboot, if it still t reboots on its own. They are known to have a defect that causes this though. So if he's done no modding to have soft bricked it, chances are it's a broken device you can't fix
Sent from my Nexus 5X using Tapatalk
Related
Yesterday my completely stock Nexus started a constant boot loop. I have tried doing a factory reset and cache wipe via the recovery menu out of the bootloader, but each time it does nothing and reverts back to the settings it was using. I have tried using the Galaxy Nexus toolkit and Nexus root toolkit, but neither will work because the bootloader will not stay unlocked. It will unlock initially, but after the required restart it reverts back to locked again (it also does not clear user data at all). I have called Samsung about it and the lady assured me it was a software issue and wanted to charge me $70 for it to be fixed (over the phone mind you), so I figure if it is a software issue (personally I think it is a hardware issue), you guys could help me much better than she could. Thanks.
Have you tried Wugfresh Toolkit? Use the unroot option and it should take everything back to stock.
From there, unroot again, see if that works since its a one-step thing (you don't have to do anything with your phone except plug it in)
I have tried to use it, but the phone will not stay on long enough to go through the root process, and even if it does, the bootloader does not stay unlocked through the initial load.
It's an hw issue, most likely.
Sent from my Nexus
bk201doesntexist said:
It's an hw issue, most likely.
Sent from my Nexus
Click to expand...
Click to collapse
I have contacted Samsung again and the reps refuse to believe it is hardware "because it is still turning on" and want to charge me $70 to talk to a technician. Does anyone know of a way to directly contact someone who knows what they are talking about.
Get logs (logcat, kmsg) and show them
Sent from my Nexus
Have you tried using fast boot commands to unlock bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
Hello friends!
I've found several threads on various forums with this problem, but no viable solutions so far.
I decided to give my 2013 N7 to my wife so I performed a factory data reset. It began the process then became stuck while erasing the userdata. After a couple hours it gave me the dead Android. I restarted and it was bootlooped. I then booted into bootloader mode to just flash the stock image files. While in fastboot, the first step I took was to unlock the bootloader. I was prompted with the "Yes" or "No" options. I choose yes then it hung at 'erasing userdata'. I left out overnight hoping it would eventually continue. No luck. I have never been rooted or ROM'd on this tablet. All stock. Has anyone found a fix for this issue? Thanks in advance!
I am in the exact same boat and have spent a number of hours over the last week or so trying to get it going again. Mine was actually running Android L since the day it dropped and got stuck in a bootloop after a dead battery. Something is definitely corrupt, because it fails to erase, format or flash any partitions.
I had left the bootloader unlocked after flashing L. In a fit of desperation, I tried fastboot oem lock, and of course it locked. Now I can't get it unlocked again.
What reading I have done doesn't look promising.
Yeah. I have found zero solutions on ecru forum out there. My wife's first gen N7 will bootloop out of nowhere about every three months. I loved Nexus tablets until this nonsense. I think I'm done with them.
I have the same problem.
Any solutions?
Sent from my Nexus 5 using XDA Free mobile app
mo123456789 said:
I have the same problem.
Any solutions?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The only solution I ever found was to buy a broken screen tablet from eBay for it's motherboard. I spent hours and hours over a couple weeks trying to revive it. The replacement has been rock solid ever since.
Good luck
Any updates on how to fix this? I also encountered this problem. I was going to give my Nexus 7 away, so decided to do a factory reset. It took forever and just wound up showing a dead Android with an X on his chest. I turned it off and it said it was erasing, only to get the same results. I had never messed around by rooting or unlocking the bootloader, but I decided to try and unlock the bootloader, but the same thing basically happened. It hung up on erasing userdata and it never managed to unlock the bootloader. Do I have any options? My Nexus seems to be forever stuck on a screen with an Android saying it's erasing data, but it never manages to complete that task.
Thanks for any help guys.
I've had roughly the same happen to me on my Huawei P1 LTE. I can't do anything with my system partition......
From what I've seen on forums is that it can happen on any device. i.e. once your internal memory becomes corrupt, your F*cked.
As the Nexus 7 (2013) is now getting on a bit, the prices are so cheap that I would suggest just picking up another.
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.
Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...
enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.
Mine is @ LG as I haven't bought from Google... Let's see...
talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.
Nexus are impossible to brick, unless you flash stock factory image...
I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus
Hi all,
TLDR: 5x stuck in bootloop; Should I lock bootloader / do anything else in recovery before sending back? And can this be undone if they refuse to repair the phone?
After having it for just over a year my Nexus 5x (rooted, custom rom, recovery and kernel) got the dreaded bootloop issue. (Had been running same rom/kernel/... for many months when one day it just got in a bootloop)
I tried these steps but with no succes.
When I tried starting the phone again a few days after the bootloop started it was suddenly working again but after using it for a few hours the phone once again got in the bootloop pattern so I'm going to assume it's a hardware problem.
I have already contacted the shop where I purchased (Europe, so always 2 years warranty) and can send it back, but would like some advice. Should I lock the bootloader / flash anything else before sending it back to get rid of the bootloader unlocked warning?
My 5x has some minor damage around the edges (nothing bad) but I'm a bit afraid they will use this as an excuse not to repair it. If I lock the bootloader again and they send it back unrepaired is there anything I still can do to unlock it again or will I basically just have a brick?
Thanks in advance.
I join up the conversation too. Same problem as you mate. BLOD, rooted and bootloader unlocked. Can someone please give us some advice?
If you can boot into the uploaded I'd try to lock it, fastboot oem lock. It wouldn't hurt. If they send it back just unlock it again.
Sent from my [device_name] using XDA-Developers Legacy app
I've joined the club too - mine is over 2 years, bought on release and lasted until around Christmas...
I will try to re-lock bootloader before it goes in to get repaired as upon boot it shows the screen that shouts warning, not secure! Etc. (Can't remember the wording...)
One good thing out of this is i went and bought a Pixel 2 [emoji41] i had a great excuse to tell myself!
Sent from my Pixel 2 using Tapatalk
I flashed stock and locked bootloader before I sent it in.
Got it back after 1.5 weeks => mainboard preplaced. No problems.
Hmm, phone isn't booting up at all now-charged overnight and tried... nothing. No lights, held power for a minute, tried everything.
Would the content bootlooping have killed the battery somehow?
Thanks
Sent from my Pixel 2 using Tapatalk
When my 5X started bootlooping I went into fastboot mode where there is a power off option, this way the phone turned off without constantly trying to boot and killing the battery.
rG- said:
I flashed stock and locked bootloader before I sent it in.
Got it back after 1.5 weeks => mainboard preplaced. No problems.
Click to expand...
Click to collapse
Same story here. I had my 5x over 1,5 years when it started bootlooping.
I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
mrafee113 said:
I have a nexus 5x which got into a boot-loop when I applied android 8 beta.
this is for like about 10 months ago, so I barely remember what happened.
I do not remember how I managed to get the device locked again. :|
but I heard from my friend that the boot-loop fix image is out and I wanted to fix the phone because my current phone is killing me.
as I got it up and running I saw the locked text in the bootloader. I user fastboot flashing unlock but got an error that stated that it could not be done.
I tried enabling usb-debugging from adb but I had/have no clue what went on. the only thing I know is that I'm seriously stuck with a phone that I need.
So, PLEASE help me. I absolutely have no idea what to do. as far as I'm concerned I only need to get past the usb-debugging and therefore the locked state. after that I'm all good and able to flash the boot-loop fix.
so, what should do guys? (desperately asks)
Click to expand...
Click to collapse
Can you boot into the stock recovery? Try sideloading the latest Oreo update zip. I'm not sure that will do anything, but worth a try.
Sent from my [device_name] using XDA-Developers Legacy app
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
mrafee113 said:
I can boot into bootloader and stock recovery, but doesn't that action require usb-debugging to be enabled?
Click to expand...
Click to collapse
No, it shouldn't.
Sent from my [device_name] using XDA-Developers Legacy app