Develop Bugs

[Q] Stuck at Unlock Bootloader screen

My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?

i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?

Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?

molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?

herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!

OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"

[q] hard bricked

OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman

I can't help... but am in the same boat as of last night with the 5.0 update.

Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.

Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!

im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?

When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.

ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.

tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.

When i boot to recovery i get the TWRP startup screen but stays stuck.

Bump
bump.. any ideas?

i have the same :/

kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."

tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?

NO success because I cannot unlock the bootloader.

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:

Bricked?!?

Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.

Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again

And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.

if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all

Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.

So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?

Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked

If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.

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.