Database Info

Can't exit bootloader after trying to reinstall TWRP on android 10

I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.

It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.

USB Debugging has nothing to do with fastboot.... Just flash stock boot img or a patched with twrp/magisk and boot your phone usually

mercenaryhmster said:
It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.
Click to expand...
Click to collapse
Where do I find the patched boot image?

TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
If nothing helps, try to reflash with MsmDownloadTool.

TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045

GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
Was able to get past the bootloader, but once I swipe up to load the device, it blacks out

GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
I can't find the menue in magisk manager where I can install TWRP

TheEndernaut said:
I can't find the menue in magisk manager where I can install TWRP
Click to expand...
Click to collapse
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.

TheEndernaut said:
I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.
Click to expand...
Click to collapse
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.

johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules page

johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules menu

tech_head said:
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.
Click to expand...
Click to collapse
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!

The command is "fastboot boot recoveryfilaneme.img" using the .img file

TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
No, no, no.
TWRP can only be flashed from either TWRP or Magisk.
On this device, you can only boot the image file. You can only flash the zip while running a booted TWRP or from the Magisk Manager.

TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
Hope I can explain myself. You are using a command you shouldn't be using: fastboot FLASH boot, you shouldn't flash the image from fastboot, you need to use that image to boot into recovery and then flash recovery itself from INSIDE recovery, then you NEED to flash Magisk from inside recovery too.
The command is: fastboot boot recovery.img
Btw, you can't see the "modules" option in Magisk because I think you flashed stock boot.img. Try flashing Magisk patched boot img and then flash recovery in Magisk as it was said before.

Did you click all the 3 buttons at once?

TheEndernaut said:
After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img)
Click to expand...
Click to collapse
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).

redpoint73 said:
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).
Click to expand...
Click to collapse
How do you install TWRP from Magisk?

blade35 said:
How do you install TWRP from Magisk?
Click to expand...
Click to collapse
Magisk/Modules/+/Select TWRP installer.zip

OnePlus 7 pro root problem

Hello.yesterday i tried to root my OnePlus 7 pro.i unlocked the bootloader first and then I have installed the twrp on slot a and slot b.then I have installed magisk,from this moment the WiFi on my phone stopped working.(when I am turning them on the automatically turned off)I tried again to flash stock ROM and twrp but when I install magisk I had the same problem.Then somehow I accidentally bricked the phone and today I have the stock ROM with unlocked bootloader and I need your help to root.

You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.

Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?

The phone now is stock and unrooted

panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
20.3 is the latest version and works perfectly fine on mine
o.o
How is it not stable?

I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"

panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
Can you Share a screen capture of your twrp file and your fastboot command

I will try again later and post screenshots

Dont understand.
HermitDash said:
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Click to expand...
Click to collapse
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.

Can you explain this easier method you said here to try it as i am a noob?

panagiwtis90 said:
Can you explain this easier method you said here to try it as i am a noob?
Click to expand...
Click to collapse
Okay, new to this thread. Where are you at right now? Booting? Which OS, TWRP, Magisk versions?

I am at 10.3 stock rom without root and twrp(just unlocked bootloader)

panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
I am on the same version what I did was find the patched boot image with magisk for Android 10 flashed it using adb then installed magisk manager and I had root.
https://forum.xda-developers.com/on...atched-boot-image-oneplus-7-pro-t3964345/amp/

panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Follow this guide and you won't need to use the patched boot,img file. I've never liked using the patched boot img.

Thank you GeekMcLeod your method worked

amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Click to expand...
Click to collapse
It's just easier than having to manually extract the boot.img
fastboot boot twrp is just to get twrp up and running then flashing the script actually installs it.
Yes it does say that it'll unroot you but for those that are unrooted already this step doesn't do anything.
After flashing you reboot TWRP so it works fresh post-script.
Then install magisk as usual and reboot to system done.
This is if you want both TWRP and Magisk all done at the same time vs booting the boot.img installing Magisk then installing TWRP where I can have it all done within TWRP which is the usual route people take to get to root.

My comment below in red font:
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same.
Fastboot boot twrp just remotely boots a "temporary" (one time) instance of TWRP, but does not install TWRP to the device. Flashing the TWRP installer zip is for installing TWRP on the device. This is optional and a matter of personal preference, and not needed to achieve root. What the installer zip does, is extract the boot.img and injects TWRP, then installs that modified boot.img back to the phone.
And when you do flash the twrp.zip it says your now unrooted flash magisk.
Correct. When the installer zip patches the boot.img to install TWRP (as described above), root is removed.
And when you flash magisk it actually then unroots magisk.
Not correct. Magisk roots the phone. If you flashed Magisk and did not have root, what may be happened, is that you may have flashed Magisk to one slot, then somehow booted to the other (unrooted) slot.
The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Manually patching the boot.img is certainly a valid way to achieve root, and maybe more reliable. I'd hesitate to say it is "easier".
Also, if you flash TWRP as a Magisk module, you will still need to flash Magisk again to have root. Flashing TWRP by that method will still unroot the phone, same as the other method (as I described above).
Click to expand...
Click to collapse
---------- Post added at 08:56 AM ---------- Previous post was at 08:44 AM ----------
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
You did it wrong. Those two command do completely different things. So the difference in commands is a big one.
As I mentioned above, fastboot boot TWRP.img just remotely boots a temporary (one time) instance of a boot.img that has been patched to include TWRP. Then the correct way to install TWRP to the phone is (from the temporary booted TWRP) flash the TWRP installer zip, which properly extracts your phone's boot.img partition, patches it to install TWRP, then installs the modified boot.img back to the phone.
Fastboot flash boot TWRP.img does something completely different. It flashes the img to the boot partition. "Flash" is the action in this case, and "boot" is the location (not the action). The TWRP img is not meant to be installed to the phone. Don't know for sure, but I highly suspect that boot.img has some differences depending on your 7 Pro model. So when folks incorrectly flash TWRP.img, they are replacing the phone's kernel and breaking WiFi, and sometimes cell network and/or Bluetooth. Again, the correct way to install TWRP is to use the installer zip (as described in the previous paragraph) which properly takes your phones specific boot.img and patches it.
What folks should understand, is that A/B partition devices (like the 7 Pro) do not have a discrete recovery partition. Recovery is part of the boot partition, which also contains the kernel. So by doing "flash boot" you are messing with the kernel in ways you should not, and therefore results like broken WiFi is not surprising.
---------- Post added at 09:06 AM ---------- Previous post was at 08:56 AM ----------
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
Magisk if fine. Your issues are due to pilot error, as I've described above.

Question Proper Rooting for OnePlus 9?

Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused

You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11

I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help

xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link

How to install root?

I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?

doveman said:
I've created a patched boot.img with Magisk and flashed that with Fastboot but after rebooting Magisk still shows that it's not rooted. So I tried flashing the boot.img in Recovery but again after rebooting it's not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").

NOSS8 said:
The boot.img to patch must be the same as the rom you are using.
Try renaming magisk.apk and magisk.zip and flashing it with Twrp. (You may need to flash vbmeta and use "fastboot flash --disable-verity --disable-verification vbmeta images\vbmeta.img").
Click to expand...
Click to collapse
Yeah, I downloaded the correct ROM (miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip) and extracted the boot.img from that.
Renaming magisk.apk to magisk.zip and flashing it just installs the app doesn't it, it doesn't root the phone as far as I'm aware.
I followed the instructions here, which say that you should only tick the "Patch vbmeta in boot image” option when patching the boot.img in Magisk if the device does NOT have a separate vbmeta partition. The Poco X3 does have a separate vbmeta partition,, so I didn't tick that option.
Installation
The Magic Mask for Android
topjohnwu.github.io
I've tried the "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img" command with four different versions of fastboot that I've got, dating from 2016 to 2020, and they all reject the "--disable" switches as an "unknown option".
I tried it without those options, so I flashed the patched boot.img and then did "fastboot flash vbmeta vbmeta.img" but after rebooting Magisk still shows that root is not installed.

https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot​
Size: 5.3 GB​
Release Date: 2021-11-09​
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz​

NOSS8 said:
https://xiaomifirmwareupdater.com/miui/surya/stable/V12.5.4.0.RJGEUXM/
Type: Fastboot​
Size: 5.3 GB​
Release Date: 2021-11-09​
Package Name: surya_eea_global_images_V12.5.4.0.RJGEUXM_20211109.0000.00_11.0_eea_e9805977c3.tgz​
Click to expand...
Click to collapse
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?

doveman said:
OK, I see that the one I downloaded was the 2.7GB recovery version rather than the 5.3GB fastboot version, but isn't the boot.img the same in both?
Click to expand...
Click to collapse
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Check:
https://forum.xda-developers.com/t/...n-vendor-dynamic-partition-enable-rw.4238807/
https://forum.xda-developers.com/t/q-h-safety-way-to-unlock-bootloader-flash-recovery-root.4198719/

NOSS8 said:
Yep, normally, in the current recovery there is only a "payload.bin" file but maybe on old phones the boot.img is present (I don't remember).
Maybe download it and check the imgs in the img folder.
Have you tried with an older or beta version of Magisk?
In case the cmd posted above is generic, the real cmd is:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!

doveman said:
Yeah, in the "miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" recovery version, there's a boot.img in the root folder and vbmeta.img (and vbmeta_system.img) in the firmware-update folder.
In the fastboot version, the boot.img is in the images folder but it's the same size (134,217,728) as is vbmeta.img (4,096).
I realised I made a stupid mistake as I was trying to do it in Powershell and it was saying "unknown option -- disable-verity" so it was adding a phantom space between -- and disable-verity. I reflashed the patched boot.img and vbmeta.img using those switches from a command prompt and it flashed them OK, but after rebooting Magisk still says it's not rooted!
Click to expand...
Click to collapse
What happens if you try to root from the Magisk app?

NOSS8 said:
What happens if you try to root from the Magisk app?
Click to expand...
Click to collapse
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.

doveman said:
The only option in the Magisk app is to root by patching the boot.img, which you then have to flash in fastboot.
I know it used to have an option to root in situ but I think that was removed some time ago.
Click to expand...
Click to collapse
No functional TWRP for this device.?

NOSS8 said:
No functional TWRP for this device.?
Click to expand...
Click to collapse
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.

doveman said:
Yeah, I've got TWRP installed. I tried booting into that after flashing in fastboot, as I recall there was an issue once (probably on a different device) where the root wouldn't "stick" if you didn't do that, but it didn't help.
Click to expand...
Click to collapse
Strange case as strange as the number of threads has this subject for this device.

NOSS8 said:
Strange case as strange as the number of threads has this subject for this device.
Click to expand...
Click to collapse
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.

doveman said:
I tried flashing the patched boot.img in TWRP, followed by the vbmeta.img, then I went to Advanced and did the "Fix AVB (vbmeta)". Now the System can't boot at all and it just boots into TWRP every time, so I guess that "Fix AVB (vbmeta)" has screwed something up.
Click to expand...
Click to collapse
This phone is rootable, surely an oversight or an error somewhere.

NOSS8 said:
This phone is rootable, surely an oversight or an error somewhere.
Click to expand...
Click to collapse
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!

doveman said:
I've tried reflashing the patched and the original boot.img and vbmeta.img but it still says "System is destroyed" if I try to boot to System. I don't know what the "Fix AVB" did but it's not good!
Click to expand...
Click to collapse
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/

NOSS8 said:
In case you can always flash a recovery or use Miflash to recover the phone.
To see:
https://www.gizmochina.com/2020/10/13/how-to-unlock-bootloader-and-root-poco-x3-nfc/
Click to expand...
Click to collapse
I've already got TWRP recovery flashed. I guess I'll have to flash the ROM again and start from scratch.

I tried flashing super.img but that didn't fix it. In the end, going into ADB Sideload mode in TWRP and flashing the 2.7GB recovery version of the ROM with
"adb sideload miui_SURYAEEAGlobal_V12.5.4.0.RJGEUXM_0deb1eaf6f_11.0.zip" fixed it without losing any data.
I still can't root it though. I've tried the "install Magisk (root)" option in TWRP and renaming magisk.apk to magisk.zip and installing that in TWRP, but it still shows "Installed N/A" in Magisk and Root Verifier says "Root permission not granted or Superuser App Missing" but then it says "Superuser App: 25.25:MAGISKSU", so it's the root permission that isn't granted.

Surely that is the problem.
https://techshift.net/what-is-disable-verity/

NOSS8 said:
Surely that is the problem.
https://techshift.net/what-is-disable-verity/
Click to expand...
Click to collapse
I thought so but I've reflashed the patched boot.img and done
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
and
"fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img"
in case it needed that too, but Magisk still shiows "Installed N/A"
I tried installed SR5-SuperSU-2.82 zip from TWRP to see if that would get it rooted,, but it couldn't even install that, it just gave some error.

Question Anyone have Oxygen OS 2115_F20 Full rom or patched boot image?

Has the full rom been released yet?

arsalturtle891 said:
Has the full rom been released yet?
Click to expand...
Click to collapse
No, at least on Oxygen Updater. Are you on F20 and you want to root?

TheNewHEROBRINE said:
No, at least on Oxygen Updater. Are you on F20 and you want to root?
Click to expand...
Click to collapse
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being

arsalturtle891 said:
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
Click to expand...
Click to collapse
When you rooted did you do fastboot flash or fastboot boot and then direct install in Magisk app?

I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img

arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
Then you can't restore your original boot image from Magisk. You should only ever do fastboot boot and then use direct install in Magisk. Unfortunately the latest full rom available for your device is LE2115_11_F.17, so I think your only chance is that someone share a stock F18 boot image so that you can flash it and then update.

arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.

shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
Appreciate it!

shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
I'm not seeing the attachment

Here is the stock unrooted F.18 boot.img. Make sure to extract it first.

So I was able to remove root by first following the same commands I used to root in the first place with the boot image you provided. However, I cannot update to F20 using the system update. It keeps failing

Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.

shadabkiani said:
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
Click to expand...
Click to collapse
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?

arsalturtle891 said:
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
Click to expand...
Click to collapse
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?

shadabkiani said:
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
Click to expand...
Click to collapse
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"

arsalturtle891 said:
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
Click to expand...
Click to collapse
Why do you always "fastboot boot......" and then "fastboot flash boot...."?
Generally, fastboot boot.... will make you phone boot up the given image temporarily (whether it's a boot image or a bootable recovery image). Whereas, fastboot flash boot.... will permanently flash the given image. Normally, you only have to go with one of these methods depending on your task/goal.
Anyway, since you have flashed the stock unrooted boot.img and OTA is still failing, I suggest you just back up your personal data (photos, stuff) to PC or whatever, and then go with the MSM tool method. It will wipe all your data on phone, and revert your phone to OOS11 with locked bootloader. From there, you can take OTA updates all the way upto OOS13 F.20. This seems to be the simpler way to get out of your current predicament.

How to use MSM tool:
1. Download the package according to your device/variant, and extract it.
2. Power off your phone and keep it aside. DO NOT connect your phone to PC for now.
3. Run the MSM tool exe. It will take a couple of minutes to load.
4. Click on Target drop-down menu and choose O2 if you are on Global.
5. Click Start. It will go to Waiting for Device mode.
6. Now on your phone (which should already be powered off), press & hold both the vol+ and vol- buttons (NOT the power button) and connect the data cable from PC to your phone. Your phone's screen will still stay black and it will enter EDL mode.
7. The MSM tool will start flashing as soon as the connection is successful.
Note: You need to have OnePlus device drivers on PC.

I appreciate the support. Can you also provide me with the F20 boot image by any chance.

Sure. Stock unrooted F.20 boot.img attached. Make sure to unzip it.
By the way, if you have MSM tool, you can get your current boot.img from its readback feature. Super simple. Launch MSM tool. Press F8. Select the desired boot image (boot_a or boot_b). Enter the password as: oneplus. Click read. Power off phone, and get it into EDL mode by pressing holding vol- vol+ buttons then connecting data cable from PC. The desired boot.img will be dumped in C: drive.
Also, F.21 has just been released, so you better update to that. I haven't yet as I am currently on crDroid.
Anyway, F.20 boot has been attached.

Hello sir Can I get F.21 boot
vendor boot
dtbo
there're no FULL package out there for Global variant
Just only incremental update
How can I get that Full Image?
Or Should I extract it from India Variant Full Image F.21
will It work normally?