Database Info

[A700] Booting failed

Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !

grimnnir said:
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
Click to expand...
Click to collapse
make sure you have the a700 and not the a701 or a510 etc etc....
also, you could try booting directly into fastboot:
1. power off
2. hold power and volume down, while you're doing that, constantly change the rotation switch from lock unlock lock unlock.... keep doing it for about 5 seconds
try flashing from here... it might give you the same result but worth a try.
other possible problems:
1. the recovery you downloaded is corrupt
2. the recovery you downloaded was not a working version
3. you might not have the right usb drivers installed
4. you might have used the wrong recovery commands
5. command (sometimes) needs to be Run as Administrator on Windows (right click)
6. you might have waited too long to reboot to recovery, or used the wrong method to do it
it might make it easier for you if you just rename recovery on computer to recovery.img (so you can just type fastboot flash recovery recovery.img)
also, I have uploaded a copy of the recovery I'm using (it's newer)

you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...

Shreps said:
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Click to expand...
Click to collapse
it might be fine but personally I would not try that... recovery and boot are not to be confused and bootloaders are not to be messed with

The stock recovery comes up instead of flashed twrp

Hello,
When I try to reboot to recovery the stock recovery comes up instead of twrp.
I have flashed multiple versions (through adb) of compatible twrp recoveries, but the issue was the same with all of them.
I am on android oreo with the latest update.
I just want to access twrp.
Did anyone experienced the same, or does anyone know hot solve this problem?

How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'

ante0 said:
How are you booting to TWRP?
Which command are you using to flash TWRP?
Unplug usb + power + vol up, release pwr when phone vibrates/huawei logo is seen.
Or use 'adb reboot recovery'
Click to expand...
Click to collapse
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up

MLGarlic said:
Im using fastboot flash recovery_ramdisk recovery.img through adb
And im using power+volume up
Click to expand...
Click to collapse
Post output from command prompt when flashing.

ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
I cannot access it but as i remember its output was successful. Nothing failed.
But somewhere it wrote that 31 version doesnt match 39 killing. But i could still flash the recovery afterwards successfully

ante0 said:
Post output from command prompt when flashing.
Click to expand...
Click to collapse
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?

i am using this recovery for my Mate 9 (L29) at https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993. Works fine. I suggest when you flash it via fastboot, please don't use command to reboot phone. Instead, just unplug phone and manually shut it off. Then, hold vol up + power buttons, it should load TWRP. I experienced that the reboot command loads eRecovery than TWRP.

martinhinge said:
Hi
I have the same problem... Let me just round up the facts:
I have a Huawei Mate 9 Pro
The phone is unlocked, when i boot in to bootloader (adb reboot bootloader) it says PHONE Unlocked + FRP Unlock
When I flash twrp I get:
fastboot flash recovery_ramdisk twrp-3.1.1-0-hi3660.img
Sending 'recovery_ramdisk' (27944 KB) OKAY [ 0.658s]
Writing 'recovery_ramdisk' OKAY [ 0.268s]
Finished. Total time: 0.943s
When I afterwards try to boot into recovery (adb reboot recovery)
Error
Please update your system
Error
Func NO 11 (Recovery image)
Func NO 2 (Load failed)
I currently have build no LON-L29 8.0.0.323(C432LOG)
All I want to do is flash a newer image, can I do it with adb/fastboot directly?
Click to expand...
Click to collapse
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353

ante0 said:
Only reason it would do this is because you're flashing an image meant for Nougat.
Try this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
Click to expand...
Click to collapse
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help

martinhinge said:
And when you say image, you mean the twrp image, right? Which one of the four download links should I use? the one for mate 10 pro?
Thanks for your help
Click to expand...
Click to collapse
What?
The thread I linked is for Mate 9, only one download link is in there.
Direct link: https://mega.nz/#!tgd2BIRS!NOk3XkSaBX8PC5xjyrZNyIIz52aSoPZFphQNauhTKGQ

[Help!]ADB devices not listed

Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??

zappomax said:
Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??
Click to expand...
Click to collapse
I don't get it. The TWRP site you posted said to fastboot into TWRP image, then flash recovery from TWRP itself. It seems like you tried to flash the image directly. As the TWRP site you posted explains, this is not how it works anymore.
Just follow the instructions from the site.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
Click to expand...
Click to collapse

Command is "fastboot boot recovery.img" and when you're in twrp flash twrp zip
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?

akxak said:
After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?
Click to expand...
Click to collapse
Sure

zappomax said:
Sure
Click to expand...
Click to collapse
Sounds like your usb drivers are faulty. Try a different computer. Happened to me before with a Pixel XL.

Sometimes it helps just to reconnect the phone.

Sorry to all...
I just needed to read the instructions carefully on TWRP site...
So stupid and hasty

There's no recovery on this device, it's included in the boot partition. So fastboot boot the image, and then flash the installer zip.

I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.

ashish_jha said:
I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.
Click to expand...
Click to collapse

ADB Driver Installer v6.0 for Windows 10 64 Bit (2023)
ADB Driver Installer v6.0 Latest for Windows 10> It helps you to connect Android Smartphones and Tablets to Windows 7/ 8/ 10/ XP/Vista x64/ x86
www.driversforum.net

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.