Develop Bugs

[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.

HTC One m8 doesn't boot

So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16

ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).

Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:

ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.

So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.

Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse

It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it

ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.

Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?

Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

It now says Relocked then underneath security warning. Is that good?

ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.

Will i have to re unlock the boot-loader for the RUU.exe to work?

ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.

Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one

ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.

Yeah it says updating 0 out of 7 sending ........................

ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.

This is what comes up

It send that 1 had been sent then it said error

How to install Android in Download Mode

Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot

http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.

peltus said:
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.
Click to expand...
Click to collapse
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Edit: I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

Light_Ben said:
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Click to expand...
Click to collapse
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.

peltus said:
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.
Click to expand...
Click to collapse
I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?

OK I did a lot of research and I think I'm stuck.
fastboot recognized my device, I had to connect the phone on USB 2 instead of USB 3 port.
ADB shows an error on the phone, and fastboot says OEM is forbidden. And because OEM can be activated only from the phone... I'm doomed I suppose.
LG said my warranty expired. And anyway, I would have to pay for shipping and all.
:'(
Thanks for everything. If you find anything, answer here.

I think someone has already started a thread on unbricking bootloader locked phones. You might search for that.
But to me, it just sounds like the hardware has gone belly up just as many others. You might search for that problem also.

Thank you, I contacted the author of the topic!
Just in case for people, here is the topic: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 ([REQ] Need help. Unbrick phones with locked bootloader, oem unlock disabled)

Light_Ben said:
Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot
Click to expand...
Click to collapse
just sent it to lg ...I iam paying 130 euros for new bootlader because mine stucked on bootloop but I can acces the recovery mode and I tried to flash stock but nothing if you never locked the bootloader try to sent it to lg and say to them you never unlock the bootloader ....sorry for my bad engilsh

I have a big problem and I did not find any solution at xda.
I flashed a custom rom and now after entering pin my phone bootloops. I am not able to enter recovery or download mode.
It feels like the phone is ignoring volume up and volume down buttons. I also tried to press the buttons directly on the motherboard. I cannot immagine that the buttons are broken. Has anybody an advice or me?

Restarting reboots to bootloader

Hey guys. Stepped away from the forums for a while and I'm back lurking the forums again with a question.
My device is the TMO Moto Z2 Force XT1789-04 and I am running the stock ROM, 8.0.0,
OCXS27.1.5 with the January 2019 security patch. I am rooted with Magisk V19.0 on the stock kernel.
I'm almost certain I have seen my issue discussed before but I was unable to find it. Here's what happens...
When I perform a normal reboot by pressing the home button, my device reboots to the bootloader. Once I am in the bootloader I can press the power button to select "start" and my device boots normally into the OS.
This issue started when I recently switched from Magisk V17 to V18. I have returned to stock a few times to diagnose the issue with no luck. When my device is completely stock I do not have the issue. When rooted with any version of Magisk, I do.
Can anyone provide some insight for me please?

fast69mopar said:
Hey guys. Stepped away from the forums for a while and I'm back lurking the forums again with a question.
My device is the TMO Moto Z2 Force XT1789-04 and I am running the stock ROM, 8.0.0,
OCXS27.1.5 with the January 2019 security patch. I am rooted with Magisk V19.0 on the stock kernel.
I'm almost certain I have seen my issue discussed before but I was unable to find it. Here's what happens...
When I perform a normal reboot by pressing the home button, my device reboots to the bootloader. Once I am in the bootloader I can press the power button to select "start" and my device boots normally into the OS.
This issue started when I recently switched from Magisk V17 to V18. I have returned to stock a few times to diagnose the issue with no luck. When my device is completely stock I do not have the issue. When rooted with any version of Magisk, I do.
Can anyone provide some insight for me please?
Click to expand...
Click to collapse
I think the fb_mode is still set on, just issue 'fastboot oem fb_mode_clear' w/o quotes and that should solve it.

41rw4lk said:
I think the fb_mode is still set on, just issue 'fastboot oem fb_mode_clear' w/o quotes and that should solve it.
Click to expand...
Click to collapse
Lemme give it a shot and I'll report back shortly with the results.
Do you know what would cause the change?

fast69mopar said:
Lemme give it a shot and I'll report back shortly with the results.
Do you know what would cause the change?
Click to expand...
Click to collapse
Usually when you flash a stock firmware the 1st thing the flashall does is set fb_mode so that it can keep bootloader mode while flashing. Most likely the command to clear it was either not present, missed, or just didn't execute properly. It happens, but it's a simple remedy.

first attempt at fastboot fb mode
41rw4lk said:
Usually when you flash a stock firmware the 1st thing the flashall does is set fb_mode so that it can keep bootloader mode while flashing. Most likely the command to clear it was either not present, missed, or just didn't execute properly. It happens, but it's a simple remedy.
Click to expand...
Click to collapse
I booted to fastboot and entered the command. Command went good. First reboot from fastboot with the fastboot reboot command sent me right back to the bootloader. I hit the power button to boot into the OS and let it boot up as usual. Next, I performed a reboot just using the power button and it rebooted normally. 2nd reboot with the power button took me back into the bootloader. I hit the power button to boot to the OS and it booted normally again. Im going to fastboot flash the command again to see if anything changes.

fast69mopar said:
I booted to fastboot and entered the command. Command went good. First reboot from fastboot with the fastboot reboot command sent me right back to the bootloader. I hit the power button to boot into the OS and let it boot up as usual. Next, I performed a reboot just using the power button and it rebooted normally. 2nd reboot with the power button took me back into the bootloader. I hit the power button to boot to the OS and it booted normally again. Im going to fastboot flash the command again to see if anything changes.
Click to expand...
Click to collapse
That's a little odd, maybe a vol btn is sticking? Issue the clear command again, then 'fastboot reboot bootloader', issue the clear command again, then reboot normally. All of that shouldn't be necessary, but if you still get pulled into booloader mode after all that then I'd inspect the buttons.

I have been having this exact same issue for so long now.... I've tried everything I could ever possibly think of with no luck. I can fastboot boot into twrp. Ive tried every firmware as a flashall including other providers firmware just to take a shot at it. At this point I dont even care if I never get baseband back, I just want to have my moto Z2 back to play with lol.
PLEASE, let me know if you find a solution. Also Im on XT1789-04

H411UCIN093NIC said:
I have been having this exact same issue for so long now.... I've tried everything I could ever possibly think of with no luck. I can fastboot boot into twrp. Ive tried every firmware as a flashall including other providers firmware just to take a shot at it. At this point I dont even care if I never get baseband back, I just want to have my moto Z2 back to play with lol.
PLEASE, let me know if you find a solution. Also Im on XT1789-04
Click to expand...
Click to collapse
The solution is above, you have a whole other problem entirely. You've apparently (as you said) flashed every firmware you could find and borked your baseband and most likely your system. So long as you haven't done anything silly like lock your bootloader (I assume you haven't since you can boot twrp), you should be able to blankflash back to a clean slate and flash the appropriate firmware for your variant. TMO or ATT, whichever one you had originally.

41rw4lk said:
The solution is above, you have a whole other problem entirely. You've apparently (as you said) flashed every firmware you could find and borked your baseband and most likely your system. So long as you haven't done anything silly like lock your bootloader (I assume you haven't since you can boot twrp), you should be able to blankflash back to a clean slate and flash the appropriate firmware for your variant. TMO or ATT, whichever one you had originally.
Click to expand...
Click to collapse
Ive been trying to how do I get into EDM?
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
41rw4lk said:
The solution is above, you have a whole other problem entirely. You've apparently (as you said) flashed every firmware you could find and borked your baseband and most likely your system. So long as you haven't done anything silly like lock your bootloader (I assume you haven't since you can boot twrp), you should be able to blankflash back to a clean slate and flash the appropriate firmware for your variant. TMO or ATT, whichever one you had originally.
Click to expand...
Click to collapse
How do I get it in the mode to do a blankflash if the phone boots to fastboot or just bootloops? Thanksss

H411UCIN093NIC said:
Ive been trying to how do I get into EDM?
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
How do I get it in the mode to do a blankflash if the phone boots to fastboot or just bootloops? Thanksss
Click to expand...
Click to collapse
'fastboot oem blankflash' w/o quotes.

all remaining attempts to reboot...
41rw4lk said:
'fastboot oem blankflash' w/o quotes.
Click to expand...
Click to collapse
So far so good after issuing the fastboot commands for a 2nd time. fastboot oem fb_mode_clear has worked for me and it stuck. I have rebooted more than 40 times in the last 2 days to verify and all is working as it should. Thanks for the info bro!

I'll totally give that a shot. I tried the modified fastboot exe with the added reboot edl command with no luck. I'll let you know if what you suggested works.

H411UCIN093NIC said:
I'll totally give that a shot. I tried the modified fastboot exe with the added reboot edl command with no luck. I'll let you know if what you suggested works.
Click to expand...
Click to collapse
Don't use the modified fastboot, just regular fastboot is all you need. Make sure you also have the blankflash.zip, most up-to-date firmware for your variant, and the qualcomm diag drivers. They're all around here, just search for them.

41rw4lk said:
Don't use the modified fastboot, just regular fastboot is all you need. Make sure you also have the blankflash.zip, most up-to-date firmware for your variant, and the qualcomm diag drivers. They're all around here, just search for them.
Click to expand...
Click to collapse
cant use the command given. it says
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.016s

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.