Database Info

Fastboot Mode Not Working in Windows 10

I cannot get fastboot mode to work under Windows 10. I see lots of posts regarding this issue but none of the suggestions have worked for me.
I am seeing my OPO with adb and can maipulate it and reboot it:
Code:
C:\adb>adb devices
List of devices attached
15b00da9 device
But when I reboot into fastboot, "fastboot devices" gives me nothing. The phone shows fastboot mode.
Some things I have tried:
Currently using Samsung drivers
Have manually switched USB driver in device manager to Samsung ADB
Have tried 15-second usb drivers and UniversalADBDriverSetup. Neither help. Same problem.
Have followed several suggestions on installing Google USB drivers. They don't seem to show up when manually switching USB drivers. Only the Samsung ADB drivers show up.
Currently have driver signing turned off.
Does anyone have any other suggestions?

Have you tired installing the drivers while in "Test mode" ? I currently have Windows 10 insider build 14965 and I have no issue, both adb and fastboot work.
I always use this installer on all PCs I need fastboot/adb. https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
It's an all-in-one pack of the drivers and fastboot+adb. Never had problems with it and always worked for me, it gets installed in system so you can run them from any CMD

Yup I tried adb-setup.1.4.3 with driver signing disabled. I tried uninstalling what I could find and then reinstalling.
The Google drivers are confusing. Selecting update driver and then navigating to the driver location yields "No drivers for your device could be found."

Just tried it again. These are the 15-second drivers I mentioned. I say yes to "install drivers". But attempting to change USB driver either gives the error mentioned in my last post. Or if I try to choose from drivers already installed, all I see are the Samsung drivers. I cannot see Google USB drivers.

This is kinda the summary of what I've tried:
http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opo
But I can't get the Google drivers to install. Again, Windows says no software found for your hardware.

Seems more of a Windows problem at this point, I usually install that, plug the phone and that's it, never had problems (on multiple computers and OS) I can only suggest you to refresh windows installation, either from the settings "Update and recovery" (you can chose between keeping data or full wipe) or from the CD if you have it.

Okay that was weird. I tried completely removing the Samsung drivers through Add/Remove Software then I reinstalled the 15-second drivers and rebooted. I happened to leave my phone in fastboot mode. When I went into device manager I saw "Kedacom USB Device | Android Bootloader Interface" but fastboot still gave nothing.
I manually changed that driver to "Marshall London Bootloader Interface" and viola:
Code:
C:\adb>fastboot devices
15b00da9 fastboot
Now adb isn't working but I'll try manually changing that driver too.

So ADB has now stopped working. Still manually selecting the Google drivers folder yields no software for your hardware. I will now try re-adding the Samsung drivers and see if the fastboot interface remains intact.

Before I get to the Samsung driver, with the phone in normal booting and PTP mode I now see that same Kedacom USB Device with three models listed:
#recovery
Android Bootloader Interface
Kedacom KDB Interface
None of them work with ADB.

[SOLVED] Fastboot Mode
I think I figured it out. All the help postings talk about manually selecting the driver. What I found out was that I had to do this *twice*: once for regular ADB mode and once for Fastboot mode. I set the ADB mode to the Samsung ADB drivers. To change the Fastboot driver I needed to boot the phone into Fastboot. I could then change that driver to the Marshall London Bootloader Interface.
I was then able to unlock the bootloader (remember to set the OEM Unlock option under Developer Options) and then install TWRP.
What a pain.
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.

kbocek said:
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.
Click to expand...
Click to collapse
https://dl.twrp.me/bacon/
You got the last image from here?
Code:
fastboot oem unlock
Then
Code:
fastboot flash recovery twrp-xxxxx.img

Yes, it's unlocked.
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ -0.000s]
finished. total time: -0.000s
Full disclosure time. I'm actually doing this on a OnePlus X. I was also testing with a OPO and so started posting here.
Two things I think were important. 1. I didn't rename the recovery file to recovery.img. Second, I didn't issue the fastboot boot command. However:
Code:
C:\adb>fastboot flash recovery twrp-3.0.2-0-onyx-OnePlusX.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.750s
I also tried renaming the file to recovery.img. TWRP still doesn't show up. So I tried the boot command after installing:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.516s
I've tried several versions of TWRP, 3.0.2.0, 2.8.7.0 and some other ones supposedly for the OnePlus X. The fastboot boot command does not reboot the phone. Still can't figure out the "dtb not found" message.

This thread describes my problem exactly. It mentions a custom bootloader that's supposed to work from eng.stk. Trying to find it.
http://forum.xda-developers.com/oneplus-x/help/users-twrp-t3258756

Finally. I installed the custom bootloader from here:
http://forum.xda-developers.com/devdb/project/dl/?id=20236
Bluespark V41. *Now* the bootloader is replaced and works. So, yes, there is a problem with the standard Onyx TWRP images.
Edit:
I misspoke. It's the *recovery* image that is being replaced.

thanks
thank u so much...now its working

[SOLVED] No boot in TWRP possible. Under no circumstances...

I have a strange problem with my brand new Mi Mix 2s.
My procedure from the beginning:
Unlook using tool from Xiaomi. For this I had to wait 72h.
Subsequently, the unlooking was considered successful.
For this I used my notebook with Windows7 (no VM).
Now I got the needed files and want to start with the installation of TWRP.
I also use my notebook but with Linux, my everyday operating system.
I have set the phone to fastboot mode (vol-down + power).
With fastboot devices you can find the phone. But commands like flash or boot end in a frozen console.
Unusual. Now I try it again in Windows7 (dualboot). The same problem.
Then I try the Windows10 game computer of my son.
The commands are confirmed as successful.
But in fact nothing happens. Nothing is flashed and I am not in the TWRP to boot.
Here the console output:
Code:
#[twrp.ing = twrp-3.2.3-0-polaris.img]
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.914s]
booting OKAY [ 0.071s]
Finished. Total time: 1.051s
#[black screen]
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (42368 KB) OKAY [ 0.951s]
Writing 'recovery' OKAY [ 0.201s]
Finished. Total time: 1.165s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot boot twrp.img
creating boot image...
creating boot image - 43386880 bytes
Downloading 'boot.img' OKAY [ 0.910s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 1.009s
F:\platform-tools>fastboot devices
19cf4510 fastboot
F:\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.004s
#[reboot]
Unfortunately, I am not aware of any possibilities to solve the problem further.
Does anyone have suggestions or ideas?

Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.

malimukk said:
Which TWRP are you flashing? Are you sure that it is the proper file for mix 2s?
What happens when you reboot the phone after flashing recovery with vol+ and power?
Flash twrp then restart manually holding vol+ and power buttons.
Click to expand...
Click to collapse
Yes. It is this version: https://eu.dl.twrp.me/polaris/
I have tried your tip. Does not work either.

Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?

yabow said:
Can it be helpful to close the bootloader and perform unloocking again?
How is the usual way to lock the device again? Using fastboot, or are there other solutions?
Can I really reopen the bootloader afterwards?
Can someone confirm that multiple opening is possible with the MIunlock tool?
Click to expand...
Click to collapse
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly

malimukk said:
Yes you can unlock again. I've done it myself.
I am not sure what is happening in your situation. Which MIUI version are you running?
I'd suggest you to flash a more recent version of MIUI with the Mi Flash tool.
Perhaps MIUI developer 8.12.27 version.
Let it boot to system after flashing
Then turn off, flash twrp, disconnect cable,
reboot from fastboot with Power and Vol+
No other ideas honestly
Click to expand...
Click to collapse
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?

yabow said:
I have
MIUI-Version 10.2.1.0 GLOBAL
Model M1803D5XA
and using
fastboot version 28.0.1-4986621
on Windows10
I have tried with Linux, but here the comandline hangs and nothing happends...
Do you think i have to use a developer ROM? This can be a problem?
Click to expand...
Click to collapse
For me sometimes fastboot just does not want to work on my laptop, then I switch usb ports and it magically works again. It is usually an issue on the PC. try abother cable as well. You cab also try to uninstall your adb/fastboot drivers and install these: https://forum.xda-developers.com/showthread.php?t=2588979
Preferably on the Windows10 machine you have, as it seems closest to working.
Miui version should not be relevant, but it might be that yours is somehow messed up. I would suggest you to avoid using the mi flash tool for now as it uses fastboot to flash the different images and it might cause other issues as clearly fastboot is somehow broken. You can try to update to a dev rom thorough the phone update app?
Btw when you do fastboot boot twrp.img you have to keep the cable plugged in

Didn't change anything. Damn it.

check this
read this page (need a translater)
in MiMix2s_Xiaomi.eu_Firmware yoo find a install_TWRP.bat in folder 02_TWRP
exchange and rename your new twrp to the name in the folder
https://tradingshenzhen.com/de/cont...sh-tutorial-global-firmware-xiaomieu-firmware

So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.

yabow said:
So, I tried some TWRP versions (v15, v14, and others) to get the black-screen error again and again. Version v8 finally allowed me to boot into TWRP. Yeah!
Before I closed the bootloader,
got a message about a destroyed device,
reloaded the stock-ROM with MI-flash,
booted TWRP v8 from this thread,
only saw cryptic files and just used an OTG adapter to install more *imgs and *zips.
Not everything works as it should yet, but it will...
Thanks for your help.
Click to expand...
Click to collapse
Your storage is encrypted, that's why you have the "cryptic files".
TWRP v8 can not decrypt your storage, the latest version can though

My OnePlus 7 Pro is bricked.

My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.

You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.

I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.

Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.

How can I get things done back, all I've is fastboot.
It's a New set, please help (

dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.

It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>

dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?

Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.

dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro

LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?

dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.

tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img

SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro

joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks

In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.

dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.

Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.

Htc bootloader unlocked but Not Allowed on Production Device

I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.

hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
hassanulhaq said:
I am currently running android 9.0 on htc dual sim model. i have unlocked my bootloader but whenever i tried to flash twrp or any other fastboot command after sending it says not allowed on production device.
target reported max download size of 536870912 bytes
sending 'recovery' (46340 KB)...
OKAY [ 1.320s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.355s
i have tried both commands
fastboot flash recovery
htc_fastboot flash recovery (through different folder heaving related files)
Help me Solve that issue.
Click to expand...
Click to collapse
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.

Download mode
CiroConsentino said:
I recently unlocked bootloader to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
I recently unlocked bootloader on my HTC U11 to flash Magisk so I could have root access. I was getting the same error and found out that you must do the flashing in "download mode", not in fastboot or bootloader mode.
Click to expand...
Click to collapse
How to do that in download mode?

hassanulhaq said:
How to do that in download mode?
Click to expand...
Click to collapse
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here:
https://www.getdroidtips.com/unlock-bootloader-htc-u11/
Click to expand...
Click to collapse
.
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
https://savegyd.com/magisk-root-tutorial/
Click to expand...
Click to collapse
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).

issue resolved
CiroConsentino said:
hi, sorry for the late reply, my brother "borrowed" my phone for a couple weeks and he did a factory reset. I don't have my phone yet, hopefully I won't have to unlock the phone again or flash Magisk into the bootloader again either...
To unlock the bootloader, I followed this nice and detailed tutorial here: .
Then I followed Magisk's official tutorial on how to flash it without a custom recovery... here
... just go to the "How to install Magisk with ADB and Fastboot (without custom recovery)" section and read it carefully, but instead of rebooting the phone into fastboot mode, I had to do it all in download mode.
I I did not install TWRP custom recovery, I manually patched the stock "boot.img" file with Magisk and then flashed the patched boot with this command with the ADB tool in Windows (phone in download mode):
fastboot flash boot patched_boot.img. I wanted to keep HTC's stock recovery.
Then I rebooted the phone into Android, and opened "Magisk" app in Android to make sure the root was working...
I didn't have internet connection in my phone (data connection or wifi), I did it all offline.
If you don't have the locked "boot.img" you must check the exact version of your installed Android OS and download the correct RUU file. Then you can extract the boot.img from it, patch it with Magisk, then flash it into the phone.
I did it in download mode as it was failing in fastboot mode. Make sure to enter download mode when you restart your phone, not fastboot mode. I'm not responsible if you brick your phone. My phone is the "Global" version from India (6GB RAM, 128GB internal storage).
Click to expand...
Click to collapse
Issue was resolved. My phone's bootloader was unlocked and and top of all it got pie update on unlocked bootloader with rooted phone and updated to android pie, then it started creating random issues like phone booting time was around 10 to 15 mins and i was getting above mentioned error. whenever i was booting to download mode my system was not detecting my phone but in fastboot mode it was detecting (kind of strange issue)... which turns out to be a cable issue. Once i changed my cable my phone was detected in download mode. So i re-locked the bootloader and then again flashed the firmware everything came to normal. Phone is up and working fine and thanks for help again.