Database Info

Trying to flash custom Rom ends up in clockworkmod to reboot...

Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????

xtrg said:
Hi all,
I have the att one xl, carrier unlocked. I used it for a month now in my country with no problems, I had it rooted,bootloader unlocked etc.
I used clockworkMod to backup everything and to try to flash this ROM
http://forum.xda-developers.com/showthread.php?t=2075783
I followed the instructions on this page
http://www.teamandroid.com/2013/04/09/update-htc-one-xl-hatka-android-411-jelly-bean-custom-rom/2/
I got to the final step and rebboted phone. After that, problems began. It runs again the clockworkmod recovery and it says it cannot mount the sdcard. I read that i have to flash the stock ROM. I tried that getting the recovery.img from the clockworkmod backup folder nad now when phone reboots,it starts the clockworkmod but when i make i choice on this it goes for rebooting...
Any help please????
Click to expand...
Click to collapse
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?

Hey my friend thnks for the reply. I'll try all of these right now. If u can please follow the thread, I might have more questions...Thnks again!

I've reache the point where i mount again my sd card and making all thw wipe things...
I' ve installed the rom but after it says that is succesfully installed and rebooting it shows the htc logo and after that...nothing!
The device turns off(or at least i think it is)black screen, no charge little orange light...But when it comes to this mode, I can hear the soun of the pc like when u do connect a device!
What am I doing wrong?
And yes I have hboot 1.14. What is the correct sequence in the actions????

Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app

exad said:
First off, I'd use TWRP since it's compatible with all ROMs and CWM has very little compatibility with our phone.
To do that, download TWRP 2.3.3.1 Check MD5
boot to bootloader/fastboot
then fastboot flash recovery twrpfilename.zip
then wipe cache, dalvik, system, factory reset in TWRP
Flash rom.
If you are on hboot 1.14, you then need to extrract the boot.img from the ROM's zip and fastboot flash boot boot.img
As for the not able to mount SDCard, did you factory reset in the bootloader?
Click to expand...
Click to collapse
exad said:
Did you extract the boot.img from the rom and then flash it using fastboot?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...

xtrg said:
Yes I did.
Booting in bootloader
going to fastboot and it changes to fastboot usb
typing in command prompt
>fastboot flash boot boot.img
I get
sending 'boot' (6076 KB)...
OKAY [ 0.901s]
writing 'boot'...
OKAY [ 1.528s]
finished. total time: 2.430s
from the bootloader options i choose recovery
phone restarts on twrp
I swipe everything out
I go to install and choose the zip file from the sd card which contains the rom
installation starts ok and it finishes saying all ok
I choose reboot in system from the twrp
(In this point i get a question on fixing root permissions and i choose yes)
after rebboting, htc logo comes up and after that...nothing...
Please help...
Click to expand...
Click to collapse
You're wiping after flashing the boot.img... so you need to reflash the boot.img don't wipe anything, just fastboot flash boot boot.img and then reboot the phone.

HELP! Nvidia Shield OEM 6.0 NO RECOVERY! NO ROOT!

Hi, everybody, I am having problems with my nvidia shield tablet, it seems that after I had updated to android 6.0 I lost my custom recovery, and the original recovery is not there. Therefore I cannot update to 6.0.1, i cannot root, and my computer does not recognize the tablet when i go into the bootloader. Please help!

Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sent from my Nexus 6 using XDA-Developers mobile app

Are you able to turn off the tablet and use the volume keys to get into bootloader/fastboot mode? You can fastboot flash recovery from there.
Sorry it took so long to reply, yes, I can get into the boot loader. I can even fastboot, but my computer can't seem to communicate to my tablet once its in Fastboot/bootloader so every time I try to do as you said. My computer can't send the commands because it doesn't recognize the tablet.

Update drivers

I also lost twrp and root after the full OTA update. I tried to fastboot flash recovery back, but when I reboot into recovery it says "no command". How can I fix this? Its seems as if the recovery partition is gone? Thanks for any help.

That is stock recovery

lafester said:
That is stock recovery
Click to expand...
Click to collapse
How can I get TWRP to flash then? I am getting this:
Code:
sudo ./fastboot flash recovery recovery.img
[sudo] password:
target reported max download size of 100663296 bytes
sending 'recovery' (7228 KB)...
OKAY [ 0.353s]
writing 'recovery'...
OKAY [ 0.334s]
finished. total time: 0.687s
It finishes too fast to actually do anything. I have tried both 3.0.0 and 3.0.2 twrp for MM. I would appreciate any suggestions on how to fix this. Thanks.

You renamed twrp to recovery? If so you did flash it. Do you reboot directly into recovery?
Sent from my SHIELD Tablet using Tapatalk

Yes I renamed it to recovery.img and rebooted. When I reboot to recovery, it still just says no command.

Are you unlocked?

Yes boot loader shows unlocked

Latest twrp?

TWRP-3.2.0-0-sailfish.img Installing.

I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
I also tried this method from https://twrp.me/google/googlepixel.html
Installation:
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
this all seemed to go ok.... but i still dont have root ?????
any help to what i'm doing wrong ?
Click to expand...
Click to collapse
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

phaino00 said:
TWRP does not provide root privileges. You need to use Magisk 14.5 for root privileges on the Pixel. Link for Magisk:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Try a fresh install of the complete firmware, letting it wipe everything including data. Magisk v14.5 build 1456 works fine for me with the final 8.1.

daddylonglegs said:
Is there a guide anywhere on installing Magisk on the OG Pixel? I got TWRP installed and I have no password set so everything is decrypted. But whenever I boot my phone, I get errors about system stuff crashing and can't use my phone.
Do I need to install ElementalX as well? What could I be doing wrong?
Click to expand...
Click to collapse
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.

phaino00 said:
Just as @roirraW "edor" ehT mentioned, do a completely fresh install of the December Factory Image. Boot into system and set up. Reboot into bootloader and install TWRP 3.2.0.0 via fastboot. Install Magisk 14.5 and reboot system. (In TWRP, you will want to hit cancel when prompted for pin/password, then select read only and install Magisk 14.5 via usb-otg). All should be good.
Hope this helps.
Click to expand...
Click to collapse
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?

daddylonglegs said:
Thanks but I have my phone set up so perfectly that the idea of losing all the data on my apps, their locations on my home screens, my widgets and how they are set up, etc. is something I don't think I can bring myself to do
I did install the complete factory image; the only thing I changed was I removed the -w command. Why is completely wiping the phone necessary to install Magisk anyway?
Click to expand...
Click to collapse
Wiping the phone completely is not necessary to install Magisk, just recommended if issues persist.

be sure you have the right magisk version: 14.5 if you have the latest 8.1

smudge100 said:
I followed the instructions on https://www.xda-developers.com/how-to-install-twrp/
when i run -- fastboot flash recovery twrp-2.8.x.x-xxx.img
(in my case -- fastboot flash recovery twrp-3.2.0-0-sailfish.img)
target reported max download size of 536870912 bytes
sending 'recovery' (26520 KB)...
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED ((remote: partition [recovery] doesn't exist
finished. total time 1.000s
Click to expand...
Click to collapse
Make sure you've got the latest platform-tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
I was getting the same error until I updated the platform tools. Maybe it's a new version of fastboot? Regardless, fastboot boot [TWRPnamehere].img worked for me with the new tools/fastboot.

[Guide] Unlock Bootloader, Get Root and Flash TWRP Recovery

Warning: This guide is a WiP and is NOT complete. DO NOT FOLLOW THIS GUIDE UNTIL THIS MESSAGE IS REMOVED.
You will require ADB and Fastboot installed on your computer.
First you will need to send a private message to the_lazer with your IMEI and Serial Number and they will give you a key to unlock the bootloader.
Wherever you see KEY in this guide replace that with the key you got given.
Second you will need to download Magisk from here, rename that file to
Code:
magisk.zip
Then download the TWRP.img from here.
If the touch screen doesn't work on TWRP then press the power button so the screen sleeps and then press it again so it wakes up and it should work.
Make sure your device has "Enable OEM Bootloader Unlocking" enabled in settings.
Plug your device into your computer and turn the device off.
Hold the power and volume up buttons, if it has a menu where reboot to bootloader or fastboot is a option then do that.
Once in fastboot mode on your computer run:
Code:
fastboot oem key KEY
fastboot oem unlock
Press the volume up button on the phone and it should unlock successfuly.
Once that is done you will need to run:
Code:
fastboot boot TWRP.img
Note that you should NOT flash twrp yet as it will give "red state" error and prevent your device from booting.
Then once in TWRP if it asks for a password then click cancel. If that doesn't work then press the power button and then press it again so the screen sleeps and wakes up then swipe to unlock and click cancel again.
Swipe to allow modifications then click Advanced and then ADB Sideload and swipe.
Next run
Code:
adb sideload magisk.zip
and it will flash magisk.
Magisk will provide root and patch the bootloader so it will still boot past the "orange state" screen.
Next go back twice and click Reboot and then Bootloader.
Then on your computer run
Code:
fastboot flash recovery TWRP.img
That will now flash TWRP.
The reason you need to flash TWRP after you have flashed magisk is because magisk is required to patch the bootloader so that it will actualy boot.
Then run
Code:
fastboot reboot
and you should eventualy reboot to android, give it about 30mins to boot just to be safe.
Then install Magisk Manager from
Code:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
.
You should now have a working rooted Nokia 3 which uses Magisk.
TODO: Add troubleshooting section and steps to follow if something goes wrong.

Any feedback? Does anyone want to pm me and try it safely?

JakesDen said:
Any feedback? Does anyone want to pm me and try it safely?
Click to expand...
Click to collapse
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates

redweaver said:
Don't worry, then next time someone asks about rooting their Nokia 3 I will be sure to point them to this thread, and I like how you described the process. It's very easy to understand. I already have my phone rooted and i'm sticking with my stock recovery because of updates
Click to expand...
Click to collapse
Thanks :3

nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
Runs flawlessly and doesn't crash or bootloop.
However if you enable a magisk module which causes a bootloop then you would have to factory reset the device unless /data is decrypted in which case you can just delete the folder the magisk module is located in. I will add to the guide instructions on how to have a decrypted /data partitionlater.

SkaboXD said:
nice guide, did you encounter any crashes like SuperSU or it runs normal without errors?
Click to expand...
Click to collapse
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo

virenhp said:
QUOTE=virenhp;75052054]I have Unlocked bootloader in Nokia 3 TA 1032
I flashed Trwp Successfully but Still Getting Stock Recovery when entered to Recovery Mode. Please Help Me .. How Can I get Twrp Recovery. Thank Yo
Click to expand...
Click to collapse
if flashing doesn't work, use this command: fastboot boot recovery.img
You will boot to twrp successfully but you need to do this every time when you want twrp.

I followed your guide step by step but when rebooting after TWRP flash, the phone does not boot into system. No matter how i try to reboot the android logo pop up with orange state and the next thing is TWRP loading. I can boot into bootloader, so i tried flashing magisk and TWRP again, but no success. Any help would be appreciated

I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed

I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
I recommend not using SuperSu.
You can however install magisk and then use magisk manager to install a systemless xposed.
Just don't use the official regular xposed or your device won't boot.

Please make sure to quote me so I get notified if you respond.

it's good and easy guide, i got my nokia 3 rooted in 30mins

Send me the adress where i'm sending private messege

Tayyabmadina said:
Send me the adress where i'm sending private messege
Click to expand...
Click to collapse
Just click "New Private Message" and enter "the_lazer" in the "Recipient Username" field.
Or message them from https://forum.xda-developers.com/member.php?u=3665957

Thank you

i did everything like on tutorial but when i finish it. it boot to TWRP

redweaver said:
I will try this method the next time I get an ota update. Wasn't sure if it was the superSU or the xposed that was causing the errors. After this update i've confirmed it's the SU.
I've never used magisk before. Hope it won't conflict with xposed
Click to expand...
Click to collapse
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.

JBData said:
My Nokia3 roadacts:
- Developper mode OK
- Unlocked OK
- Install magisk & TWRP
fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.047s]
finished. total time: 0.484s
adb sideload magisk.zip
Total xfer: 1.59x
fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (13916 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.734s]
finished. total time: 1.188s
- Install SuperSU
fastboot reboot
rebooting...
finished. total time: 0.016s
fastboot reboot
adb sideload SuperSU-v2.82-201705271822.zip
That's the only way I found to install SuperSU, cause I don't succed to put the zip in my phone: All mounts in TWRP failed : USB (a R1 warning PC appears), internal... I had transfert the zip in the Nokia before doing all but I don't know where it's located when I browse in TWRP.
According to the trace I saw on the phone when I did the adb sideload, SuperSU install and config seems to be OK, but I'm no sure.
When I open a term on the phone, navigate in the filesystem, I can't do su but see a SuperSU path with an install shell that failed...
My 2 problems:
1/ is SuperSU OK ?
2/ I'm block : how to go back to Andoid to execute root checker or SuperSU, always boot on TWRP ?
Need Help.
Click to expand...
Click to collapse
I haven't used magisk before, but I was under the opinion that you didn't need to sideload or flash supersu once you've sideloaded magisk. Maybe you need to read up on activating root with magisk

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