Develop Bugs

My M8 might be bricked and I can't find a soloution anywhere :(

I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead

raphi809 said:
After many attempts of turning off and doing the power+vol up I got the bootloader to come up
Click to expand...
Click to collapse
Bootloader is power+vol down
raphi809 said:
since everything at this point had failed I picked the factory reset option from the bootloader.
Click to expand...
Click to collapse
I think this is your main problem. Factory reset in bootloader on a modded phone corrupts the internal memory. Use Windows explorer or Device Manager to find the phone's internal memory and format it.

Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.

raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
AFAIK, if you can boot into the bootloader, you can still fix it with a full RUU or .zip with all the partitions. (unless you have hardware damage), because if you have corrupt partitions your phone will have a black screen and can be flashed by directly communicating with Qualcomm chip with linux(tried it once on my HTC One X, didnt work as my partition table itself was corrupt)

raphi809 said:
I need help you guys or I'm really screwed . My phone had been working perfectly fine on a rom that I had been running for a month, when out of nowhere I had a random reboot, don't know what could have caused it because I was just checking my messages on the facebook app, but ever since then my phone would not get past the boot screen, to make matters worse I could not get the phone to go to recovery doing the whole power+vol up. Don't know what happened to twrp but it would only show up when I would turn off the phone and plug it to charge. When the charging battery pops up with the percentage if I tapped the screen and hit the power button it would flash the twrp main menu for a quick second and it would disapear. I could not interact with twrp at all. After many attempts of turning off and doing the power+vol up I got the bootloader to come up and since everything at this point had failed I picked the factory reset option from the bootloader. Now my phone will only load straight to the bootloader and nothing else. To make matters worse no fastboot commands are working aside from getvar and show devices. I can't erase cache,flash a recovery or relock the bootloader or go back to S-On which means I cant use the warranty. Tried the RUU and it say's it can't communicate with the phone. So basically i'm looking at a paper weight with a bootloader that won't take any commands and no system image. I've been looking everywhere for a solution and the closest thing I could find is flashing the expanded 1.57 firmware in http://forum.xda-developers.com/showthread.php?t=2754063 from my sdcard but the link is dead
Click to expand...
Click to collapse
Don't try to s-on if your s-off. Just get phone in fastboot bootloader mode and run ruu. I've done it several times so it will connect. Just go through the ruu setup and watch it work. If u can't find ruu for latest firmware then try a older one your s-off so u shouldn't have to do anything but plug the phone in fastboot bootloader mode and run ruu.
I never even relock the bootloader when I flash ruu. And I allways flash in fastboot bootloader mode.
I hope this helps. If not I will try to help u figure it out.

Sneakyghost said:
Internal Memory cannot be mounted as USB on the M8 and hence it cannot be formatted from within Windows. Also, no TTY solution talks to the chip afaik. So this way is closed too.
The symptoms described sound like not only the System/Data/Recovery partitions got corrupted but also bootloader to some extend.
Something has happened while your phone was booted that corrupted large portions of your NAND. This does sound like a real hardware failure like a broken RAM to me. But then again RAM would not cause (corrupted) writes to bootloader. That partition only gets overwritten during a flash process. Not from within the phone so i would have no clue how that could get corrupted.
Are you dead sure the drivers on your PC are alright? Are you 101% sure the communication doesnt work because of the phone having an issue?
I would make totally sure drivers for fastboot are ok and then try to run (just any) RUU and try to rewrite the partitions. If you can't get that done, you will have to swallow that bitter pill and send it in. Well i would anyway. No idea what else you could try.
Click to expand...
Click to collapse
Where in Germany do you live, SneakyGhost? My M8 has been giving me nightmares, It is S-Off and today I changed the CID/MID to that of developer edition and installed the relevant Android Marshmallow firmware.zip and then ran the MM RUU from HTC Dev page. No matter what ROM I tried on SuperCID or even on this new MM software, many apps keep on crashing. Unfortunately this has stopped working, unfortunately that has stopped working. I have 3 other friends with M8, never has their phone seen an app crash. I have to restart the phone many times daily to get it to work for some time, while another app randomly crashes. Can you help me?
Thanks

Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.

Sneakyghost said:
Well if it's crashing a lot after flashing a complete RUU I'm sure the device is faulty. Maybe bad NAND or bad ram. Send it in to HTC. Don't bother setting it back S-ON cuz a.) They'll know anyway and b.) Going back S-ON is dangerous and locks you out from most repair methods you could try in case HTC won't service your device. Just saying because a lot of people seem to be thinking that going back S-ON is increasing their warranty claim chances.
Click to expand...
Click to collapse
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.

harri2cool said:
My phone is out of warranty, will HTC entertain me? How much will thay charge for repairs? I think out of warranty repairs cost more than getting a used working phone.
Click to expand...
Click to collapse
Super different from country to country. HTC Germany service is worse than it ever was. They contract Regenersis since January 2015 here, same company as in the UK.
You have to keep in mind that HTC's contractors do the checking and validating of your warranty and they go by very tight rules. You can argue and escalate as much as you want, they will charge you if your local HTC is in any way similar.
Globally, HTC has worsened their service approach a lot. I'm waiting for a service/warranty decision regarding an old M7 since half a year. A mate from our team waited six months too, but for HTC to find his M9 which they lost and refused to replace. He only just got it back, unrepaired despite full warranty eligibility.
To sum it up, if your device is older than six months, don't bother. Not worth the hassle and not worth the money. HTC won't do sh!t after six months usually. And the prices, like you guessed, are a nightmare too.
If your NAND turns out to be faulty like I assume, it'll be a mainboard replacement, which equals a new phone. And THAT can be had a lot cheaper on eBay or craigslist.

Motherboard replacement is 200 USD give or take 25 on model (DNA/butterfly was $150 and a m7wlv motherboard was $175. I priced my AT&T m8 and it was $215) for the HTC service centers here in the US. I assume the EU ones are similar in price.
Before blaming hardware, have you changed mid/cid back to stock and ran an ruu to be sure it wasn't a bad flash or compatibility?

[Q] 5x boot loop / soft brick

EDIT: solved. Thanks!
My 5x seems to be in a boot loop / soft brick type of situation. I had the N preview 3 installed, but no unlock, root, etc. I just got it recently and wanted to see how it performed stock (other than N).
I did install CameraX to use slowmo, stabilization, etc. That's actually what I was using when the device rebooted randomly. No big deal, I expected a reboot every once in a while. But now, it's stuck on the "4 dot" animation and won't go any further. Even left it overnight. Finally, after a few manual power-offs with no change, I entered recovery to do a factory reset. That seemed to work, but it still won't boot past the animation.
I would just push a factory image, but I never checked the box in developer options to unlock bootloader. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?

the john said:
My 5x seems to be in a boot loop / soft brick type of situation. I had the N preview 3 installed, but no unlock, root, etc. I just got it recently and wanted to see how it performed stock (other than N).
I did install CameraX to use slowmo, stabilization, etc. That's actually what I was using when the device rebooted randomly. No big deal, I expected a reboot every once in a while. But now, it's stuck on the "4 dot" animation and won't go any further. Even left it overnight. Finally, after a few manual power-offs with no change, I entered recovery to do a factory reset. That seemed to work, but it still won't boot past the animation.
I would just push a factory image, but I never checked the box in developer options to allow ADB. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?
Click to expand...
Click to collapse
Boot into bootloader, ADB works in there.

the john said:
I would just push a factory image, but I never checked the box in developer options to allow ADB. Is there any way to override that and push the image anyway? I've had several Nexus devices, and have rooted/flashed other brands as well, which is why this is so frustrating. I (mostly) know what I'm doing!
And if not, I guess I'll look at warranty. The guy I got it from on Swappa got it from Project Fi, so do I go to them? I have it activated on a standard carrier, but it's within the year. Or is it LG?
Click to expand...
Click to collapse
It wasn't clear what you were saying, I think you meant you didn't check the box to allow bootloader to be unlocked.
If that is the case, download the full (as opposed to differential) OTA from here
https://developers.google.com/android/nexus/ota
then boot into recovery and flash using adb sideload.
If you actually can unlock the bootloader, then use these images
https://developers.google.com/android/nexus/images
If you get an error during flash, then probably your EMMC is dying.

sfhub said:
It wasn't clear what you were saying, I think you meant you didn't check the box to allow bootloader to be unlocked.
Click to expand...
Click to collapse
Right, that's what I meant -- sorry! I actually did ADB the OTA and it didnt boot. So I used LGUP and refurbished it. Didn't take then, either. As a last resort I did ADB OTA again, and it worked.
Thanks for the response. :good:

Darke5tShad0w said:
Boot into bootloader, ADB works in there.
Click to expand...
Click to collapse
I actually did that, but it didn't work the first time. After trying a couple more times, and on a different computer, it finally worked.
Thanks for the reply.

Bootloop. Recovery doesn't work, bootloader locked

Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.

Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app

Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk

I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?

I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.

Have you found any solution?

vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.

Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers

Bootloop, soft brick?

I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked

shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.

Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...

enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?

UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...

shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.

Mine is @ LG as I haven't bought from Google... Let's see...

talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.

Nexus are impossible to brick, unless you flash stock factory image...

I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus

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.