Hi Everyone
I was rooting My op7 pro after updating to open beta android 11. While i was booting twrp it shows Fastboot Mode screen And stuck on that
Hope i ll find possible solution from the community
Regards
ali_hamza
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
benjaminries said:
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
Click to expand...
Click to collapse
You should just be able to run direct install after you boot to A11 with the patched boot image.
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
calripkenturner said:
You should just be able to run direct install after you boot to A11 with the patched boot image.
Click to expand...
Click to collapse
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
benjaminries said:
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
Click to expand...
Click to collapse
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
calripkenturner said:
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
Click to expand...
Click to collapse
Got it. Yeah my Magisk Manager was still installed from previous beta, but it took away the "direct install" option when I lost root from flashing the unpatched boot.img. Personally I would always rather patch my own boot.img file than rely on something from a filesharing service, especially when trying to get out of brick...
But I can see how until proper TWRP support comes, we can just use Magisk to patch alternate boot slot before rebooting but immediately after flashing the latest OOS beta using the regular system update process. Hindsight...
benjaminries said:
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
Click to expand...
Click to collapse
need to use orangfox recovery
esi2121 said:
need to use orangfox recovery
Click to expand...
Click to collapse
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
benjaminries said:
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
Click to expand...
Click to collapse
Check the orangefox ,it's only recovery support a11 for now
esi2121 said:
Check the orangefox ,it's only recovery support a11 for now
Click to expand...
Click to collapse
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Yesterday i download and tried to flash Pitch Black Recovery Project but results were same.
I think there should be some changes regarding A11 in any recovery so the best is that we should wait for their( Devs) further response
benjaminries said:
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Click to expand...
Click to collapse
yup thats it , but in orangefox git said official support A11
esi2121 said:
yup thats it , but in orangefox git said official support A11
Click to expand...
Click to collapse
Check out this (now locked) thread though: it seems like there's no working port of OrangeFox for guacamole that supports OOS11 yet... lots of people bricking and boot-looping on the hope that there might have been!
[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1] | XDA Developers Forums (xda-developers.com)
Related
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Same problem here. Already tried to boot every version of TWRP without success.
abrahammurciano said:
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
But there's no button to flash, I open the app, select flash recovery, select device, but theres no button to flash it.
See screenshot
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Denkai said:
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Click to expand...
Click to collapse
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
super odd. maybe your boot image is corrupt? still doesn't explain why fastboot boot isn't working though... Try bluSpark's TWRP image. it's a solid build and I am not having issues with it.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page17
or you can also try swapping to the other partition by typing 'fastboot --set-active=_a' (or fastboot --set-active=_b) and booting to that recovery.
if that doesn't work for ya, try and restore stock via fastboot is my only suggestion:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
[/COLOR]
abrahammurciano said:
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
Click to expand...
Click to collapse
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Does it work for Android 10?
oneplus 6 running oxygen os beta 30 with magisk 20.1 without twrp
Borat38 said:
[/COLOR]
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Click to expand...
Click to collapse
Please I need TWRP for Blackview BV9600 pro please share with me if you have a link to a webpage I may find it
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
Hello I'm having magisk root access and official TWRP app but can't use it for NAndroid backup, how can I use the app for backup and fishing custom ROM?
We have stock factory boot images, I'm only posting the latest builds.
The rooted android 10 images are rooted with latest Magisk 20.4
The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e
You will still need to install the Magisk Manager to use root. Root will not work without it.
You HAVE to be bootloader unlocked in order to flash a boot image, meaning these Verizon images are likely useless but google does say it covers extra carriers too. The 11 images seem to be unified in terms of Verizon and other carriers, but do NOT cover
Make sure to match the boot image build number to your own build number. (Settings/about/android version/build number)
-
Android 11 - RP1A - NOV - Stock Factory Boot
Stock Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Stock Boot Versions
Android 11 - RP1A - Oct - Stock Factory Boot
Stock Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Stock Factory Boot
Stock Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Stock Factory Boot
Stock Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Stock Factory Boot
Stock Boot Image - Global - QD4A.200805.003
AFH
Stock Boot Image - VZW/JP - QD4A.200805.001
AFH
--
Android 11 - RP1A - Nov - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201105.002 - All carriers except EMEA, SG, and IN
AFH
Old Rooted Boot Versions
Android 11 - RP1A - Oct - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.201005.006 - All carriers except EMEA, SG, and IN
AFH
Android 11 - RP1A - Sept - Rooted Factory Boot
Rooted Boot Image - Global - rp1a.200720.011 - All carriers except EMEA, SG, and IN
AFH
Android 11 Beta R3 - RPB3 - Rooted Factory Boot - Thanks to @Xenanthropy !
Rooted Boot Image - Global - rpb3.200720.005
AFH
Android 10 - QD4A - Aug - Rooted Factory Boot
Rooted Boot Image - Global - QD4A.200805.003
AFH
Rooted Boot Image - VZW/JP - QD4A.200805.001
AFH
--
For root on Android 11, you need the latest Magisk Canary that can be found here
Steps to proceed:Unlock Bootloader
Ensure you are on latest android version
Ensure you have the latest versions of adb/fastboot tools
Download the desired boot image and place where adb tools have access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
On the phone:
Go to Settings/About and scroll to the bottom
tap 'Build Number' 7 times
type password/pincode if you have it otherwise don't worry
Go to Settings/System/Developer Options
Enable OEM Unlocking
Enable USB Debugging
Accept USB Debugging prompt on phone - If this doesn't pop-up by itself, unplug phone and plug back in to pc and then it should pop-up, HAVE to allow access..
On pc type:
adb reboot bootloader
fastboot flashing unlock
On phone:
Volume up/down to YES and press power button to proceed with bootloader unlock and wiping data partition
fastboot reboot
--
Flash Boot Image on Bootloader Unlocked Device
Ensure you are on an android version matching the boot image you want to download(Check Settings/About - Click on Android Version - Look at 'Build Number')
Download desired boot image on pc and place it where somewhere you have adb/fastboot access
Connect phone to pc and open terminal/cmd prompt to where you put that desired boot image
Reboot phone to bootloader
on pc type:
fastboot flash boot desired-bootimage-name.img
fastboot reboot
--
To Pass CTS w/root- Courtesy of @quangtran1
After flashing rooted kernel:
In Magisk Manager, install the MagiskHide Props Config module;
Execute command 'su -c props' using a terminal app on the phone;
Choose 'Force BASIC key attestation' option from menu;
Choose from fingerprints list, it should default to Pixel 4a, just Confirm
Reboot
?????
Profit
--
If you want or need to make your own rooted boot image
You need the latest Magisk Manager installed.
Stable Magisk for Android 10, maybe 11 | Canary Magisk for Android 11 for sure.
Download the desired Stock Boot Image from here or extract it yourself from Google's Factory Image zip.
Copy to sdcard of your device.
Open Magisk Manager, click the first 'Install' button next to 'Magisk is up to date'.
Click 'Install'.
Click 'Select and Patch a File'
Find and select the desired Stock Boot Image.
You will find the magisk patched, Rooted Boot Image in the sdcard/Download folder titled 'magisk_patched.img'
Copy that to your pc and flash your pixel 4a from fastboot or copy to the phone and flash with exkm/fkm/etc.
Reboot
Install Magisk Manager
Enjoy being rooted.
XDA:DevDB Information
[Stock/Rooted Boot Images] Pixel 4a [NOV 02], Tool/Utility for the Google Pixel 4a
Contributors
HolyAngel
Source Code: https://developers.google.com/android/images#sunfish
Version Information
Status: Snapshot
Created 2020-08-24
Last Updated 2020-11-02
thank you very much good man. if you can do that also for the beta version it would be great.
https://developer.android.com/preview/download#
@dark8899
Ah I had forgotten about the beta, thanks! And added!
Before I mess up my phone, Do I just run "adb reboot bootloader" then "fastboot flashing unlock" then "fastboot flash boot [Android11RootPatch].img" then "fastboot reboot", set up the phone, install magisk?
I haven't rooted in a while and I'm also just a user not a developer.
@DJesri13
Yep that would pretty much do it exactly.
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Xenanthropy said:
Hmm, not seeming to work on mine... I tried both flashing my own acquired (and patched with magisk) boot.img as well as your patched boot, and neither seem to want to boot when I reboot, it just boots back into fastboot and says "reason: no valid slots to boot" (or something to that effect, i've already patched the original boot.img back) Tried flashing the patched img to both slot A and B, nothing seemed to work. Got the furthest with my own patched image, the google logo would turn to the G and act like it was loading but it continued to "load" for a good 10 minutes so I just gave up.
Click to expand...
Click to collapse
It also isn't working for me. It won't let me flash the boot image. I also tried my own image patched with magisk.
Edit: I all my attempts to flash the boot partition failed so I can still boot the OS
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
HolyAngel said:
@DJesri13
@Xenanthropy
Sounds like possibly not flashing correctly or you weren't already on the latest firmware. You need to be on the firmware matching the boot.img. This is pulled directly from the factory image. Try flashing that first and then this image and see what happens.
For flashing this after flashing same firmware on android 10 for instance:
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
make sure you're flashing to 'boot', the 3rd word in the command. if you don't put that it won't flash or if you put something other than 'boot' you could have other issues.. Should still be fixable by flashing the factory images.
Click to expand...
Click to collapse
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Xenanthropy said:
I just checked my build version (i'd upgraded to android 11 beta via the ota update by signing up for the beta) and it matches the boot img, RPB3.200720.005.
When I run "fastboot flash boot root.boot.sunfish-rpb3.200720.005.img" it flashes it properly, but upon rebooting it just reboots back into fastboot stating that there was an error. It wouldn't boot on my custom patched boot.img either so i'm not sure what the issue is here.
My current steps were:
1. get phone, immediately unlock bootloader
2. opt-in to android 11 beta, check for updates and upgrade to the beta (rpb3.200720.005)
3. extracted boot.img from the Android 11 beta OTA update, patch it with magisk and attempt to flash (doesn't work, google logo just loads indefinitely)
4. Try flashing your patched boot.img, which results in the phone immediately rebooting and stating an error with the boot slot
If i'm doing something wrong, i'm not sure what it is. I can provide more details if necessary
Click to expand...
Click to collapse
Ah ok gotcha. it sounds like you did everything right too. Might need a magisk update or something else for that then. May remove the beta root image then..
Are you currently running the Android 11 beta? It would be nice to know if someone was able to get the beta rooted properly so we could see what steps they took.
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
DJesri13 said:
When I try to flash the boot img I get
FAILED (remote: Failed to write to partition Not Found)
Should I try to flash to the boot slot?
EDIT: I flashed and it went through but now it just boots to the bootloader, flashing the stock boot img doesn't fix it. Ill reflash the factory image and again later maybe
Click to expand...
Click to collapse
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
xxTECRAxx said:
i am also in the same boat here. unlocked and then fastboot flash boot root.boot.sunfish-qd4a.200805.003.img (to slot a)
it booted to Google logo then restarted into bootloader fastboot mode.
it says no valid slot to boot. see attached image
Click to expand...
Click to collapse
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
i relfashed the factory image, then dropped magisk into phone with windows explorer. installed magisk then redid the fastboot flash boot root.boot.sunfish-qd4a.200805.003.img and she just booted up. unsure if i have root though
EDIT: i have root!
---------- Post added at 11:23 PM ---------- Previous post was at 11:03 PM ----------
DJesri13 said:
Yep, I was getting the same results using the beta firmware and boot img provided and my own as well as the Augusta firmware with the provided images and my own that I pulled from the factory image and ones I patched.
Anyone know if it is possible to sideload magisk as a zip?
Click to expand...
Click to collapse
if you're stuck inside fastboot, then reflash the factory image from this file sunfish-qd4a.200805.003-factory-fac7c08d.zip using the included "flash-all.bat". once that completes, boot phone back up and go to settings to enable developer options. then enable USB debugging and finally transfer the magisk.apk into the phone using windows explorer. once all this is done, start over at the top:
adb reboot bootloader
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
xxTECRAxx said:
i relfashed the factory image, then ....
.....
fastboot flash boot root.boot.sunfish-qd4a.200805.003.img
fastboot reboot
get paid
Click to expand...
Click to collapse
This is for android 10 or 11 beta?
Zlatty said:
This is for android 10 or 11 beta?
Click to expand...
Click to collapse
10
Can anyone confirm if Rooted 10 + Magisk passes SafetyNet on the 4a?
You need to patch boot-s by latest canary magisk, especially if it`s BETA 11.
https://github.com/topjohnwu/magisk_files/raw/canary/app-debug.apk
Can someone help me out, I don't understand why I can't boot up after flashing the stock or the batched boot image. My bootloader says slot a and that's the one I flashed to. I tried the beta but right now I'm back on Android 10 and neither will let me boot up.
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
adb devices
adb reboot bootloader
fastboot flash boot "D:\Downloads\boot_patched.img"
fastboot reboot
Click to expand...
Click to collapse
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
fastboot flash boot_a "D:\Downloads\boot_patched.img"
fastboot flash boot_b "D:\Downloads\boot_patched.img"
Click to expand...
Click to collapse
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
iamMG said:
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
Click to expand...
Click to collapse
I had an issue before, with the Canary APK. Try installing the v23 app and repatch your boot IMG with it. Worth a shot.
I tried, again, with v23. Same bootloop occuring.
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
@soka said:
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
Click to expand...
Click to collapse
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
iamMG said:
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
Click to expand...
Click to collapse
True, sorry just trying to help you narrow it down.
@soka said:
True, sorry just trying to help you narrow it down.
Click to expand...
Click to collapse
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
iamMG said:
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
Click to expand...
Click to collapse
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
BillGoss said:
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
Click to expand...
Click to collapse
Thanks, I will try this method and report back.
Btw, after you booted using this method, for how much time did the boot animation showed up (the two circling white dots around bigger red dot)?
Edit: I tried this method. No luck. The boot animation goes on 5-10 minutes, at which point I reboot into bootloader and flash the stock boot image.
Anyway, I ended up downgrading to OxygenOS 10.3.8.
Starting to give up as well... Never had any issues before (on Android 10) to flash root on O7Pro, but ever since Android 11, I keep having "boot loop" issues. Aka, the boot logo keeps loading and never boots into the OS. Only works again if I re-patch the original boot.img file.
This is starting to get.. VERY, VERY annoying. Why isn't there any proper method of getting this to work?
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
hkdoublecat said:
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Click to expand...
Click to collapse
I am too afraid to upgrade to OOS 11, only to find out root doesn't work for me. The restore function of this unofficial TWRP version is buggy so can't really depend on it to restore OOS 10.3.8. So, I have decided to stay on the latter until Team Recovery releases a proper update for Android 11.
altwu said:
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
Click to expand...
Click to collapse
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Mangtas_666 said:
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Click to expand...
Click to collapse
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
altwu said:
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
Click to expand...
Click to collapse
i tried attaching the images to the post but they're not showing up. i tried editing the post to attach the images, but they're still not showing up. sorry.
What's this?This is a stock oxygen os fastboot Rom for OnePlus9 adapted from https://forum.xda-developers.com/t/...xygenos-a-04-a-07-for-mt2110-devices.4404719/ .I really appreciate @Valdem for his flashing script for OnePlus 9RT.And I modified his script according to OnePlus 9 partitions and changed some flashing order in script.
Note that this is only for the device which is unlocked bootloader.And internal storge may be cleaned if you downgrade from higher oxygen rom or come from other rom like custom rom.
The ROM's image is extracted from oos11.2.10.10BA and oos12(LE2113_C47) ota package.Note that the ROM is only for ONEPLUS9(LEMONADE).
For full package oxygen os:
Flashing instructions:
- On your PC, install bootloader drivers for OP9 and check if device is recognized in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode.
- Connect the OP9 to your PC
- On your PC open command line window in the uncompressed folder,
- double click flash-all.bat
- wait till PC shows "pause" on terminal.
-Whether to format data is depend on which rom you stayed before. If upgrade from older oxygen os or on the same version oxygen os,no need to format data.Otherwise format data and reboot phone.
For firmware package:
Firmware package is used for whom wants to install custom ROM.And flashing firmware package by using this instead of MSM can streamline the procedure.After the PC shows "pause"on termianl,firmware package has been installed completely.Then following the custom rom install procedure-flash boot boot.img.If not boot into recovery,replace phone into bootloader mode,flashing dtbo and vendor_boot partitions will work.
The using procedure is same as full package.
NOTE:Before using this fastboot ROM and Firmware,you must have a compatible boot.img which can flashing images in fastbootd mode.Oherwise,install the "boot.img","dtbo.img"and"vendor_boot.img"by using "fastboot flash boot boot.img","fastboot flash dtbo dtbo.img"and"fastboot flash vendor_boot vendor_boot.img"in phone's bootloader mode.If phone don't boot into recovery or fastbootd mode,flashing firmware(If target is OOS11,then flashing oos11.2.10.10 firmware;If target is OOS12,then flashing firmware OOS12C47).After this,reflashing boot,dtbo and vendor_boot.
Download link:
Oxygen os 11.2.10.10:OOS11.2.10.10(FULL PACKAGE)
Oxygen os 12(LE2113_C47):OOS12(LE2113_C47)(FULL PACKAGE)
Firmware package:
Oxygen os 11.2.10.10 firmware:OOS11.2.10.10firmware package
Oxygen os 12(LE2113_C47) firmware:OOS12(LE2113_C47)firmware package
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
jmadiaga said:
in A12, which recovery do you use.
bec. twrp does not survive an Android 12 upgrade.
TWRP no compatible with A12
Click to expand...
Click to collapse
This script uses fastboot, not recovery. Custom ROMs typically post the recovery image to use for flashing them in the thread if you're asking about that.
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
cbrown666 said:
Any one success in flashing OOS11.2.10.10 or OOS12(C47) by using this script?
Click to expand...
Click to collapse
Fastboot scripts are the quickest path to bricking and having to use MSM in my experience so I'm not trying it. If you do, make sure you switch to slot A first because for some reason, slot B really doesn't like to cooperate on this device.
Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
Unlock The Bootloader;
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;
To unroot simply flash the stock boot.img.
Relock Bootloader;
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out
Thank you so much
Thanks so much. Going to try this weekend with my daughter phone.
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?
I received the update but refusing to apply it
jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.
Rooted my Nord 2T successfully. Thanks once again
Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used
Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today
nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable
Stock Boot for Indian variant CPH2401_11_A.13 added to OP
can u post the latest update boot.img for indian unit CPH2401_11_A.14
Stock boot for Indian CPH2401_11_A.14 added to OP
Stock boot for Global CPH2399_11_A.14 added to OP