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?
https://www.xda-developers.com/motorola-one-power-moto-z3-play-twrp/
Support Status: Current
Maintainer: kaneawk, erfanoabdi
Code Name: beckham
Device Tree / files
NOTE: Monthly security updates may break
decryption of /data in TWRP. MTP does not
work at this time, but you can use adb to transfer files.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoz3play.html
The new twrp works fine
Hopefully this means more support in the future. Did you flash or boot? Curious if it will bootloop if I flash the img
Installation:
If you do not already have TWRP installed: Download twrp img. 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 twrp.img
This will temporarily boot TWRP on your device.
I'm aware of how to boot TWRP on my device. I was wondering if it would be possible to *flash* it though. As I understand it you need the TWRP zip compiled and was wondering if you got that working or not for this device.
Booting is fine for now but I need to have TWRP as recovery for bootloops when I don't have my PC available
Edit for spelling
what works
I have downloaded the twrp.img
I ran fastboot boot twrp.img
I have downloaded magisk 17.1 and flashed it via twrp
Installed Magisk Modules: AdgaurdDNS, Greenify4Magisk, and Viper4Android FX
what doesn't work
installed xposed framework via magisk -> caused bootloop
Pretty sure it's an Xposed bug because Xposed bootloops on any device that's got 8.1 with latest patches
So if we can unlock the bootloader, and boot to twrp, can we not install supersu from there? Or am I understanding this wrong?
Magisk is superior in about every way. Also super su isn't being developed anymore
Ah, I'll look into it more. My last phone was forever old, and my only option was SuperSU. Thanks!
please any help update the download TWRP file, because in github the developers say mount vendor is working, but the file in twrp webpage its old.
Has anyone tried booting this on the Sprint version
Help me plz
hello, Im trying to install the twrp recovery but i cant, its happing a error
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.999s
and i dont know how to solve, please help me
Trwp can't be installed on this device as far as I know. Available twrp is for booting purposes only.
Fastboot boot twrp.img
Click to expand...
Click to collapse
Whenever I use the command fastboot boot twrp.img, it boots just fine but if I try to use fastboot flash recovery twrp.img, it gives me an invalid partition name recovery error. I am trying to root the device. To my understanding, if you just boot into TWP, its only temporary. I guess my question is, is flashing the .img necessary and if so, why is it giving me this error? I got the .img from the offical website, its in the same folder as fastboot, and even boots right up if using the boot command so the image isnt corrupt. Any suggestions?
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
?
darkdaemon32 said:
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
Click to expand...
Click to collapse
So can I root this device without installing TWRP? I want to continue using my mods (which I believe TWRP will break) and I don't really care about the custom recovery at this point but want root access for a few select items like AdAway.
There isn't even a way to currently INSTALL TWRP on the z3. The only way to use twrp is with fastboot boot. And you use this to temporarily boot to twrp and flash the magisk installer zip for root. Magisk is systemless and doesn't modify system so you should be able to use all apps that detect system modifications such as gpay etc.
Would anyone help me? I saved the Magisk file to internal memory, but when I try to install TWRP (fastboot boot twrp.img) the internal memory files are encrypted.
How do I decrypt these files so I can do the Root?
Hello everyone,
I found a working recovery for our phone
here
All credits go to
@yshalsager for developing and uploading
and
@yukimaru2215 for first linking
Bugs: Encryption not working - but stock rom boots up without encryption with a trick...
Attention: You will need to format data - all your data will be lost! Backup first!
How to install:
Tempearily root your device and modify fstab.qcom - this is needed to enable decryption
a) install fastboot and adb from hereb) load a prerooted kernel (patched bootimage) from here and copy it to your adb fastboot folderc) boot to bootloader -> reboot and keep holding vol+ until you see "FASTBOOT"d) Open command prompt, navigate to your adb fastboot folder and type in command prompt:
Code:
fastboot boot patched_boot.img
e) Go to apps, upgrade magisk manager, install any root explorer, grant root permissions and navigate to /vendor/etc/fstab.qcomf) open fstab.qcom with texteditor and change "forceencryption=footer" to "encryptable=footer" and save
[*]Install TWRP and wipe data backup everything first - this will wipe all your data
a) Download recovery form link aboveb) copy extracted TWRP-3.2.3-daisy-1808.img to adb fastboot folder and type in command prompt
Code:
fastboot flash boot TWRP-3.2.3-daisy-1808.img
c) Type in command prompt
Code:
fastboot reboot
before hitting enter keep holding vol+d) In TWRP you will get the message can´t read data -> skip decryption and go to "wipe" and "format data"e) if you want to root your device you need now need to boot to bootlaoder (reboot -> bootloader) - if not, you done here. Reboot to system and setup your device
[*]Root your device
a) You are in your bootloader... download patched_twrp from here and copy it to your adb fastboot folderb) Type in command prompt
Code:
fastboot boot patched_twrp.img
c) Boot up, upgrade Magisk manager and install magisk via manager -> choose "direct install"
If you flash back a stock boot.img, you will loose your wifi functionality!
Enjoy!
thanks man
You can make a video soon
Noob dude.... And with this method, how is the steps for can update via ota the next updates?
Thx for this hard word and sorry my bad english!
Enviado desde mi Mi A2 Lite mediante Tapatalk
Testing official TWRP tonight. Some issues with decryption but will be resolved soon hopefully. Stay tuned!
d1ngh said:
Testing official TWRP tonight. Some issues with decryption but will be resolved soon hopefully. Stay tuned!
Click to expand...
Click to collapse
When will it be available?
dannyzamora said:
Noob dude.... And with this method, how is the steps for can update via ota the next updates?
Thx for this hard word and sorry my bad english!
Enviado desde mi Mi A2 Lite mediante Tapatalk
Click to expand...
Click to collapse
If you using Havoc 2.0, linke me, it's everything,you need! This twrp lets you boot up all treble GSI Roms....
And otas should be installed normal.
1. Uninstall magisk
2. Install ota, not reboot
3. install magisk
4. Flash twrp and boot up with patched twrp via fastboot
You never boot up without root... So everything's fine with modules and otas doesn't touch vendor and encryption...
brunoliveh said:
When will it be available?
Click to expand...
Click to collapse
When it's ready :silly: just be a little more patient won't be long now.
brunoliveh said:
When will it be available?
Click to expand...
Click to collapse
Hopefully by end of week, maybe earlier
i did every step here but after all the phone stuck on bootloop.
any idea why?
Voodoojonny said:
Hello everyone,
I found a working recovery for our phone
here
All credits go to
@yshalsager for developing and uploading
and
@yukimaru2215 for first linking
Bugs: Encryption not working - but stock rom boots up without encryption with a trick...
Attention: You will need to format data - all your data will be lost! Backup first!
How to install:
Tempearily root your device and modify fstab.qcom - this is needed to enable decryption
a) install fastboot and adb from hereb) load a prerooted kernel (patched bootimage) from here and copy it to your adb fastboot folderc) boot to bootloader -> reboot and keep holding vol+ until you see "FASTBOOT"d) Open command prompt, navigate to your adb fastboot folder and type in command prompt:
Code:
fastboot boot patched_boot.img
e) Go to apps, upgrade magisk manager, install any root explorer, grant root permissions and navigate to /vendor/etc/fstab.qcomf) open fstab.qcom with texteditor and change "forceencryption=footer" to "encryptable=footer" and save
[*]Install TWRP and wipe data backup everything first - this will wipe all your data
a) Download recovery form link aboveb) copy extracted TWRP-3.2.3-daisy-1808.img to adb fastboot folder and type in command prompt
Code:
fastboot flash boot TWRP-3.2.3-daisy-1808.img
c) Type in command prompt
Code:
fastboot reboot
before hitting enter keep holding vol+d) In TWRP you will get the message can´t read data -> skip decryption and go to "wipe" and "format data"e) if you want to root your device you need now need to boot to bootlaoder (reboot -> bootloader) - if not, you done here. Reboot to system and setup your device
[*]Root your device
a) You are in your bootloader... download patched_twrp from here and copy it to your adb fastboot folderb) Type in command prompt
Code:
fastboot boot patched_twrp.img
c) Boot up, upgrade Magisk manager and install magisk via manager -> choose "direct install"
If you flash back a stock boot.img, you will loose your wifi functionality!
Enjoy!
Click to expand...
Click to collapse
hay bro i'm now unlock boot loader and flash boot twrp.img its boot to recovery
i flash DisableForceEncryption_Treble.zip via twrp then flash patched boot.img to root via magisk good till now
i reboot to system and root my device and every thing is good now
but when try to enter twrp its go to stock recovery ok.
what i can to do now to get twrp and keep phone rooted too?
and what is different between twrp.img and twrp patched.img
elkhshap said:
hay bro i'm now unlock boot loader and flash boot twrp.img its boot to recovery
i flash DisableForceEncryption_Treble.zip via twrp then flash patched boot.img to root via magisk good till now
i reboot to system and root my device and every thing is good now
but when try to enter twrp its go to stock recovery ok.
what i can to do now to get twrp and keep phone rooted too?
and what is different between twrp.img and twrp patched.img
Click to expand...
Click to collapse
Hey, it's written above! You need to root with patched twrp linked above... Else you will loose twrp or wifi
Voodoojonny said:
Hey, it's written above! You need to root with patched twrp linked above... Else you will loose twrp or wifi
Click to expand...
Click to collapse
sorry let me step by step going
now i;m rooted what do second ?
Official is here:
https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
Voodoojonny said:
If you using Havoc 2.0, linke me, it's everything,you need! This twrp lets you boot up all treble GSI Roms....
And otas should be installed normal.
1. Uninstall magisk
2. Install ota, not reboot
3. install magisk
4. Flash twrp and boot up with patched twrp via fastboot
You never boot up without root... So everything's fine with modules and otas doesn't touch vendor and encryption...
Click to expand...
Click to collapse
Please explain by video
maorhag said:
i did every step here but after all the phone stuck on bootloop.
any idea why?
Click to expand...
Click to collapse
Sorry for responding so late... I had a bit of full calendar...
I just did this with another phone (I use these phones for my employies)... Idk, why it´s not working for you sorry. But meanwhile there´s a official twrp - this should do the trick!
Sorry for inconvinience
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
You will have to msm flash
anupsnair said:
You will have to msm flash
Click to expand...
Click to collapse
That is what i did - twice already... Still no Boot into twrp...
martinforum said:
Hello,
I have bricked and unbricked my op6 with msm download tool.
Now i tried to install lineage and followed the instructions.
I tried following:
- with twrp standard
- with blu
- with twrp in Boot_a and b
In all cases the reboot lead to a dark screen.
Any idea?
BR Martin
Click to expand...
Click to collapse
From what firmware are you from?
Hitman478™ said:
From what firmware are you from?
Click to expand...
Click to collapse
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
martinforum said:
MSM included OOS 5.1.5
Update required to which version to make twrp bootable?
Click to expand...
Click to collapse
Thank you. Yes this was the reason why! I can boot in twrp again.
There are different howto's out there. What is the right order to install following packages - do I have to reboot after each package?
Twrp
Lineage rom
Openapps Pico
Su
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Hitman478™ said:
I did not fully understand the problem but i can see one thing: oos 5.1.5 as a base firmware for lineage is not correct because oreo firmware is not supported, so in order
if you want only TWRP
Update to the latest firmware (oos 10)
follow this guide: https://forum.xda-developers.com/oneplus-6/how-to/guide-installing-bluspark-twrp-magisk-t3997765
If you want lineage 16/17
Update to the latest open beta pie (28)
reboot to fastboot
download TWRP img and zip (9.101)
open windows prompt and type "fastboot boot twrp.img" (make sure to insert the correct name file instead of twrp.img and check if is .img and not the .zip)
device will automatic reboots in TWRP
now from here flash the TWRP .zip file and reboot to recovery to make sure it's there
now you can update recovery to 9.107 if you want (and it's highly reccomended) by flashing the proper 9.107 .zip
don't forget to use blue_spark TWRP
Now everytime you flash a rom you need to flash TWRP after that otherwise it will not stay there
hope it's all clear and that i've not forgot anything
Click to expand...
Click to collapse
Thank you. Blue_spark twrp is working.
Now i have installed lineage and without reboot oppengapps pico but I do get an error message.
To ensure twrp, i reinstalled as you said bstwrp. But the reboot brings me back to a black screen.
Any tips for the right order to install and reboot?
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)