Develop Bugs

Nexus 5x stuck in boot loop after OTA downgrade from N Preview to 6.01

The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Edit: When I try to run "fastboot flashing unlock" I get "FAILED (remote: oem unlock is not allowed)"

Pattond said:
The wife got a refurbished 5x from the Best Buy Sales this week, it was already on N. We went and opted out of the preview and it downloaded and installed 6.01. Since then it has gone into boot loop where it shows the Google Logo, then beginning on the animation, then starts over.
I am able to get into recovery mode, I tried a reset and that didn't work. I can get into adb, and the device is seen, but when I try to sideload, I get a E:footer error.
I also tried Nexus Root Kit, but its wants me to turn on developer mode for USB debugging, and the phone cant get me there.
Frustrated enough to call Best Buy, they sent me to the store Geek Squad. He said they could only exchange, and since they are out of phones, I am SOL for getting a working unit. Money back only.
Click to expand...
Click to collapse
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.

PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options.
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Returned with
FAILED (remote: oem unlock is not allowed)
PiousInquisitor said:
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Click to expand...
Click to collapse
SHA256 Checksums on bullhead-ota-mtc19t-4ea6522b.zip match. When sideloading, at about 50% the phone says
"Warning: no file contextsThis package is for "bullhead" devices: this is a " ".
"E:Error in /sideload/package.zip
(Status 7)
Installation Aborted"
PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
I'm going to try that now.

You can use the Nexus root toolkit, manually put the phone in bootloader and click OK to get past the "enable debugging window". It's asking you to do that so it can reboot the phone itself into bootloader.

PiousInquisitor said:
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.

Pattond said:
The LG reset software got me going, but after it loaded, I did get an internal error message. I hit OK, it seem to be running fine. Will reload apps and see what happens.
Click to expand...
Click to collapse
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
If I were you I'd unlock the bootloader, flash the latest factory images then relock the bootloader. Check the build number and date. I'm sure it's pretty old.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.

Pattond said:
it is an old copy, 6.0. I started the update process, and got an update failed notice. I used the LG software again and it is getting it running, but I am still getting the internal error message (see attached)
.
Click to expand...
Click to collapse
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
The vendor image is out of date. When you boot up. Enable developer options. In developer options there is a toggle to allow OEM unlocking. Tick it. Then use fastboot to unlock the bootloader. Download and flash the latest images. You won't have any more problems.
Click to expand...
Click to collapse
All good, got it to 6.01, no internal error message on boot. I did the OEM unlock as you suggested, then let WugFresh's Nexus Root Toolkit take it from there. Thanks!

Damn I'm in the same situation but it will actually boot all the way to the lock screen and as soon as I put in my password it reboots. It actually will reboot regardless after sitting on the lock screen for about 10 seconds.
I really really don't want to lose everything on the phone. I have the factory image and can unzip it and manually install parts. I just don't want to wipe the data. Bootloader is still unlocked and I had oem unlock option enabled prior.

PiousInquisitor said:
I would be irritated too. Lets figure out where you are.
Lets boot into fastboot mode and see your bootloader is locked... Power off the phone then hold the power button and volume down button simultaneously. A few seconds later you will boot into fastboot mode. The bottom half of the screen should be information about your device. The last line should say DEVICE STATE = unlocked/locked. If it says locked you are in good shape. Just flash the latest factory images. If it is still locked, you need to figure out what path you want to get it running again.
Path 1. See if the bastard that had the phone before you flipped the "allow oem unlocking" in developer options. Reboot to fastboot mode as described above. Connect the phone to your computer. Then open a terminal (or command prompt) in the directory where your fastboot file is located and issue the following command:
Code:
fastboot oem unlock
If by some miracle it allows you to unlock, do it. You are in very good shape if you can. If you get to that point someone will help you fastboot the factory images. If not continue to path 2 below.
Path 2. Try and sideload the latest OTA. You are having trouble doing that, I see. You have a bad download. Also, I suggest using the developer preview OTA for reasons I cant explain. Let us know how it goes with another download and another try.
Path 3. You can use a tool made by LG to completely reflash your phone. Instructions for that are HERE.
Click to expand...
Click to collapse
Ok, i feel really stupid asking this.....WHAT ARE YOU TALKING ABOUT WHEN YOU SAY "FLASH" THE LATEST FACTORY IMAGE????
Ive been stuck in a boot loop for 3 days now. it only gets as far as the "google" logo before rebooting agin and again and again and again....:crying::crying::crying::crying:

BOOTLOADER is LOCKED and Usb debugging is not enabled

My phone is gone into LOOPMODE only showing GOOGLE , and no OEM enabled , no USB debugging Enabled also DEVICE state is LOCKED...
please help me to restore my set.
how to Unlock the bootloader or how to enable USB debugging ?

From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.

First off , thankyou for replying
sconno said:
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
Click to expand...
Click to collapse
yeah sure, i m on HOLD , i have tried all things such as adb, nexus toolkit and all adb commands .
Reply soon bro !

Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!

r3act said:
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
Click to expand...
Click to collapse
but how to unlock bootloader , thats the problem bro ! i have done evrytthing to do so !

OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.

sconno said:
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
Click to expand...
Click to collapse
but i think my Android is corrupt , it showing only google when i press and hold the power button.
give me another solution bro !
And anyone from MUMBAI (BORIVALI WEST)

Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/

harihacker said:
Try this. It worked for me on 2 devices.]
Thanks for this, I am going to give this a go with a heat gun later on today.
Click to expand...
Click to collapse

harihacker said:
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
Click to expand...
Click to collapse
lol , I think my Phone is dead RIP .

pls help me! The system has been Destroyed

hi there
i made a huge mistake!
I flashed the PE Extended Rom. All went well, system was booting, and hell yeah, its awesome. but then, i mad ethe mistake. I LOCKED the bootloader Damn, how stupid i was, and this just i wanna see if a payment app for my wife will work when bootloader is locked. And, immediatly after fastboot oem lock system was bricked. now i can access only fastboot and when i start up, just see that the system has been destroyed so i can not access recovery!
Anyone could help me?

Use Fastboot (Then "Fastboot OEM edl" in adb) To go to edl mode
If you can't enter it.. Test point (Need to open back cover)
Then download Global ROM
Select Flash all(Dont lock)
Hope this help

AlishaSama said:
Use Fastboot (Then "Fastboot OEM edl" in adb) To go to edl mode
If you can't enter it.. Test point (Need to open back cover)
Then download Global ROM
Select Flash all(Dont lock)
Hope this help
Click to expand...
Click to collapse
Thx for ur reply. Sadly i can't enter it Will wait a bit and hope someone else have another idea. but if not, i need to open it

DarkLord8580 said:
hi there
i made a huge mistake!
I flashed the PE Extended Rom. All went well, system was booting, and hell yeah, its awesome. but then, i mad ethe mistake. I LOCKED the bootloader Damn, how stupid i was, and this just i wanna see if a payment app for my wife will work when bootloader is locked. And, immediatly after fastboot oem lock system was bricked. now i can access only fastboot and when i start up, just see that the system has been destroyed so i can not access recovery!
Anyone could help me?
Click to expand...
Click to collapse
Best way to do this would be to go back to miunlock exe and unlocking your bootloader again.... this would then restart your phone in recovery mode... flash the ROM available and the device would be fine as before..... True story... I did the same with my redmi note 6 pro..... none of the other things worked for me but this did...

Any way to fix Bootloader ?

Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ

elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
Is there are any way to fix that with out change motherboard ?
Click to expand...
Click to collapse
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)

andybones said:
wait why did you run fastboot oem lock??
if you were wanting to lock you need to run an RUU first (for future reference)
by the "phone can't boot anymore" do you mean like nothing. completely dead? (Bricked)
you can't get to bootloader or download mode? Try holding volume up, volume power and power for a few minutes, see if does anything.
does it show charging light?
I am not experienced enough to give more details, esp about motherboard, but if can get to download or bootloader try RUU that matches the firmware on it.
(gotta be very sure about what you're doing when running commands esp. once the device is unlocked. once unlocked it's on you what you flash and run..)
Click to expand...
Click to collapse
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ

elween07 said:
Because there is a damn app only can run when the bootloader is locked... so I did that -.-. Now when I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
which app?
also why were you trying to lock?
I can't say but it seems like it could be a pain, but I hope not!

elween07 said:
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
Click to expand...
Click to collapse
and some people say natural selection doesn't exist

Oh dear!
I dont like to tell you this, but you have hard bricked your phone and it cannot be fixed using software.
Locking the bootloader is ONLY for when you are on pure stock. Even having a custom recovery (like TWRP) isnt allowed even if the ROM is stock.
In locking it, you have hard-bricked it, and there isnt ANY way to recover this using software. Nobody on XDA has EVER been able to sort this one out.
Your best bet is one of two options:
1. Buy a new phone. Yeah, pain I know, but the HTC 10 is now 3.5 years old and it might be cheaper to just buy a new phone than try to fix it.
2. Get it fixed at a repair shop. I can imagine that a few local places might not be able to do it, but maybe somewhere can. It's worth an ask?
I seem to recall that using a JAVA card or something like that you might be able to fix it, but if you have locked the bootloader with a custom rom on it, then the chances are it is over for you.
Hey, don't beat yourself up too much about it; we've all done stupid things in the past. I reversed my car into a concrete post last month and it cost me a fortune to fix it!
Such is life.....

elween07 said:
Dear
I unlock my HTC10 then flash TWRP recovery and PE ROM
after that I do "fastboot oem lock" ..............
now my phone can't boot anymore >.<
When I power up my phone it only show "HTC" for half second then power off automatic. If I plug the power cable, it will keep turning on and off.
Is there are any way to fix that with out change motherboard ?
Following video
https://www.youtube.com/watch?v=qh9u7v-VoiQ
Click to expand...
Click to collapse
Bro, never relock the bootloader. That's just a bad idea. You most likely hard bricked your phone and there is no way back. That's not 100% for sure but if u flashed any non-htc images the bootloader will not boot it. Thats why you keep it unlocked, so it can boot unsigned images. That's why it keeps shutting off.

Question Help, Bootloader locked phone bricked

So I just received the phone today and as I always like to do with my new phones I downloaded the latest full ota, installed it through local upgrade and when I pressed reboot the phone rebooted normally.
I went an pressed reboot to recovery and boom the phone just died, no recovery it goes to QUALCOMM crash dump and I am able to boot into bootloader but OEM unlock is still off in the developers options, cant unlock boot loader, cant flash anything in fastboot and there are no MSM tools.
Anyone have any ideas??
Be careful I was on stock rom flashed with stock latest rom with locked bootloader and no funny business and the phone just dead.

I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.

Will check that now

Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.

speakeasy2 said:
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
Click to expand...
Click to collapse
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)

awsan said:
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
Click to expand...
Click to collapse
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.

speakeasy2 said:
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
Click to expand...
Click to collapse
Tried that, tried flashing and booting from a boot.img and both returned with failed locked

What model do you have? I don't see why your OEM unlock option would be greyed out...

i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?

i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?

Wrssmithjr04 said:
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Click to expand...
Click to collapse
Thanks it worked, they contacted me and started a remote session and fixed the phone
craznazn said:
What model do you have? I don't see why your OEM unlock option would be greyed out...
Click to expand...
Click to collapse
It was not greyed out I just didnt press it before the phone was corrupted
jammin6996 said:
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Click to expand...
Click to collapse
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me

awsan said:
Thanks it worked, they contacted me and started a remote session and fixed the phone
It was not greyed out I just didnt press it before the phone was corrupted
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
Click to expand...
Click to collapse
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.

jammin6996 said:
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
Click to expand...
Click to collapse
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot

i did something similar (hello, im an idiot) and oneplus just had me send my phone to a licensed repair place and have them send me a brand new one.
3 days later, sure enough, it was just a new phone. coming form op6, i didnt realize the state of rooting since OP8. Since google handles OPs OTA updates, its a lot harder and op8t was only able to root thanks to a generous insider who leaked the code needed to make MSMdownloadTool work.

purpleman2k said:
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
Click to expand...
Click to collapse
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.

jammin6996 said:
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
Click to expand...
Click to collapse
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?

schmeggy929 said:
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
Click to expand...
Click to collapse
No I'm not blaming then for that. I'm blaming then for there lack of communication and the fact that they have me a run around for 16 hours and being transferred between 2 remote technicians, because "we apologize but Agnes is new here and wasn't sure what she was doing" just for the 2nd technician, Olivia, to attempt to flash the wrong files, and then says "we will try again this time tomorrow" that shows me how incompetent they are. They ask for a list of information before hand so that they make sure they have the right device and files.
And to further my reason for return, when I placed my pre-order it was listed as Dual-SIM, just to receive a single sim version. And the phone gets much hotter then most, and the battery life is no where near what it should be. With all that they want nearly the same price as all other flagship devices..

Finally got OnePlus to fix my phone using the MSM tool, and was able to keep an unprotected copy of it. what is the best place to upload and host a 3.5gb file so i can share it here?

Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!

Faizanbutt907 said:
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Click to expand...
Click to collapse
odin is for samsung. you are on OP9 Pro section.