Download Mode : DISABLED in fast boot mode - Nexus 6P Q&A, Help & Troubleshooting

Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:

amandeepparmar said:
Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:
Click to expand...
Click to collapse
If you have an unlocked bootloader and can boot into it, does it not recognize your phone or simply not allow you to run commands? My download mode reads as DISABLED in my bootloader and I can run fastboot commands. I think you're a little confused on terminology, too. You'd sideload software via ADB with TWRP or for an OTA, your stock recovery. You'd fastboot flash partitions via the bootloader.

ultyrunner said:
If you have an unlocked bootloader and can boot into it, does it not recognize your phone or simply not allow you to run commands? My download mode reads as DISABLED in my bootloader and I can run fastboot commands.
Click to expand...
Click to collapse
I can boot into fast boot mode by hardware button combo pressed but its not recognising any fast boot or ADB commands when I connect it on my laptop

When connected by USB and in your bootloader, run 'fastboot devices' and if it doesn't show your serial # then it isn't recognizing your phone, likely a driver issue.
Sent from my Nexus 6P using Tapatalk

amandeepparmar said:
Hello Devs
I want to roll back from Android Nougat to Marshmallow by installing TWRP.... I have my bootloader unlocked on my Nexus 6P but since I have the error of Download Mode DISABLED in fast boot mode Im unable to flash the firmware through ADB.
Kindly help.:crying:
Click to expand...
Click to collapse
Do not try to do that. We have a lot of bricked devices (Including Mine) after we tried rolling back to Marshmallow. Just a warning. If you still want to take a risk, go ahead by all means.

Driver issue....resolved.....Working now!!...Thank you

amandeepparmar said:
Driver issue....resolved.....Working now!!...Thank you
Click to expand...
Click to collapse
No problem. I would listen to Indian84 and stay on Nougat until you can flash full factory images.
Sent from my Nexus 6P using Tapatalk

Related

Bootlooping Nexus

My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.
Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk
Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?
No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.
colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk

Stuck in bootloop after failed update.

Please help!!!
I tried to update my rooted Nexus 6P to 8.0.0 (OPR5.170623.011, Nov 2017) using the Flashfire app and something went wrong!!! The phone is now stuck in bootloop and will not get past the 4 google coloured dots. I can boot the phone into the bootloader and then get into TWRP recovery from there but thats pretty much it.
I hoped I would be able to fix it by flashing the system image, bootloader etc using adb and fastboot but have had no luck. I have tried on both a PC and a Mac and neither seem to recognize the device. When using the commands "adb devices" or "fastboot devices" nothing shows up and when I try to flash anything it says "waiting for any device" yet when the phone is off it signals that it is charging from the laptop.
I have updated my rooted 6P multiple times before using both Flashfire and adb/fastboot from both a PC and a Mac and have never had problems before this. I have run out of ideas to try so any help would be greatly appreciated but I fear I might have bricked my beloved Nexus 6P.
MilkyOolong said:
Please help!!!
Click to expand...
Click to collapse
Weird. You should at least have fastboot when in bootloader mode, and MTP with TWRP. In bootloader mode, plug the device into your PC. The device is not detected at all? Have you tried wiping cache/dalvik? MTP not working in TWRP?
If you can boot into recovery then your device is not bricked. Make sure the adb and fastboot binaries on your computer are completely up to date. I'm pretty sure Google updated them for Oreo. You will need to flash the full stock image with flash-all.bat command when you get your computer to recognize your phone. Updating from Nougat to Oreo using Flashfire or Flashify is a bad idea because you are dealing with something way more extensive than an OTA update.

Help please can't see my phone in adb

I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now 
videodave1 said:
just trying to get back to stock now 
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.

OnePlus 8 Pro Fastboot Bootloop

My OnePlus 8 Pro is stuck in a fastboot boot loop, can't even power the phone down at this point, fastboot just comes back up again. There is no ROM on the phone somehow (after attempting to downgrade from the beta program) The bootloader is also locked as well, and can't flash any fastboot images. I have attempted to use the MsmDownloadTool, but can't get out of fastboot to use it.
What can I do at this point?
UPDATE: After letting the phone sit and drain the battery completely, I was able to get it into EDL mode, and use the MSM tool, it flashed everything, but still no boot. Any suggestions?
Make sure that you are not connected to USB and select power off from the fastboot menu. You should be able to put it into EDL mode after that and connect back to USB so that you can use the msm tool.
rmiles7721 said:
Make sure that you are not connected to USB and select power off from the fastboot menu. You should be able to put it into EDL mode after that and connect back to USB so that you can use the msm tool.
Click to expand...
Click to collapse
Power off would immediately power back on and to fastboot. I let the phone die and was able to get it to go into EDL mode after, and was able to use the MSM tool, but still no boot.
Any suggestions?
Only time I have had that happen is when I still had the USB cable connected. If it let you use the msm tool and still no boot there may be something wrong with the phone and need an RMA.
Can you access fastboot from the command line? Try downloading the fastboot rom and flash it using the flash-all bat. I had an issue after doing an ota where it wouldn't boot anything but the bootloader. Had to manually change slots to B and then run flash-all and was good after that.
Sent from my ONEPLUS IN2023 using Tapatalk
rmiles7721 said:
Only time I have had that happen is when I still had the USB cable connected. If it let you use the msm tool and still no boot there may be something wrong with the phone and need an RMA.
Can you access fastboot from the command line? Try downloading the fastboot rom and flash it using the flash-all bat. I had an issue after doing an ota where it wouldn't boot anything but the bootloader. Had to manually change slots to B and then run flash-all and was good after that.
Sent from my ONEPLUS IN2023 using Tapatalk
Click to expand...
Click to collapse
Fastboot does boot, but it is locked so there is no flashing anything through that.
Recovery can now boot as well, but still no boot to OS.
hole896 said:
Fastboot does boot, but it is locked so there is no flashing anything through that.
Recovery can now boot as well, but still no boot to OS.
Click to expand...
Click to collapse
So unlock it?
c_86 said:
So unlock it?
Click to expand...
Click to collapse
"but it is locked so there is no flashing anything through that."
Cannot unlock as I can't boot into an OS to enable the unlock. Tried flashing through fastboot but gives error that it has to be unlocked. I have attempted unlocking it through fastboot but it gives an error that it can't be unlocked.
hole896 said:
"but it is locked so there is no flashing anything through that."
Cannot unlock as I can't boot into an OS to enable the unlock. Tried flashing through fastboot but gives error that it has to be unlocked. I have attempted unlocking it through fastboot but it gives an error that it can't be unlocked.
Click to expand...
Click to collapse
Rough. I was thinking since it didn't have a os loaded it would bypass that switch in dev options
c_86 said:
Rough. I was thinking since it didn't have a os loaded it would bypass that switch in dev options
Click to expand...
Click to collapse
Yep, already contacted OnePlus the other day and they are supposed to be setting up a remote session, but I haven't heard from them yet...

Categories

Resources