Related
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
cgrimm9 said:
I installed twrp on my pixel on 7.1.1 it reboots to tarp again I got it to boot to the p.s. by clicking reboot / a on bottom left option but get error codes and can't open a lot of apps. I tried to install a tom and clear device cache and cause fails. Anyone know how I can fix this. I thought I used all the latest files
Click to expand...
Click to collapse
Did you fastboot boot into TWRP, then flash twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip? Were you stock prior?
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
cgrimm9 said:
Installed img through pc then installed the zip file with twrp. I found a article here stating I need to flash stock ing to get back to normal
Click to expand...
Click to collapse
Yes, you are not supposed to install twrp, just boot into it. If you install it by mistake, you go back, flash stock boot.img, and do it again.
This is from Dees_Troy's post located here
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Tulsadiver said:
Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
Click to expand...
Click to collapse
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
alienjon said:
@Tulsadiver First off, thanks for the post on this. I installed TWRP to slot A by accident and am finding myself in this same predicament (though I found that I can boot by switching to slot B). I found another post online that mentioned what you commented on, specifically:
Having previously downloaded Oreo 8.1 and setup root, I had loaded into TWRP, went to install, selected the TWRP zip, and installed (as per what you had suggested and what I read earlier). This is what led me to the current problem, making me realize that I'm missing something in the description. Now, I likely don't need to flash TWRP (I don't develop and used flashfire to do upgrades) but my last upgrade left me rootless and I felt having it installed would make life a little easier. I was hoping to ask for a clarification on the TWRP install.
Also, you mentioned flashing the stock img. Do you mean from the android OTA downloads? I was getting a corrupt file error when I tried flashing that to slot a...
Click to expand...
Click to collapse
Things have changed with 8.1. you have to root with magisk. From slot b you cannot fastboot flash boot_a boot.img?
I believe the instructions now are to boot to TWRP, install TWRP pixel installer zip, then flash Magisk zip
Here is where TWRP files are here
https://dl.twrp.me/sailfish/
Tulsadiver said:
From slot b you cannot fastboot flash boot_a boot.img?
Click to expand...
Click to collapse
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
alienjon said:
I hadn't tried yet. I was worried about messing things up further without asking for help online first. I'll give this a shot later. Does boot.img refer to the android image file? (ie: what I'd download from the OTA site?)
Click to expand...
Click to collapse
Yes, the zip file that is located where the flash-all.bat is. Unzip it and flash the boot.img.
I bought a Pixel 2 on swappa. It had different bootloader's on slot a and slot b. I couldn't flash updates when on slot a. I thought I was hosed but from slot b I could flash to slot a so now I'm fine. Slot a had a preview bootloader.
Hi all,
I tried to uninstall Magisk yesterday and ended up stuck in bootloop. I tried wiping the data using twrp, not working, then i tried factory reset using twrp, also not working and worse for some reason my TWRP is not opening anymore after that
Hence i was looking around for the firmware, i found one, extract the update.app and get the boot.img, system.img, cust.img and recovery.img. I flashed it directly using ADB. And it got worse! Only then I realised from the forum that the firmware did not work! Sob2....
Now i'm stuck with a phone where the whole system, boot img, etc is wrong. Can anyone please share with me their firmware? Especially the four img that i messed up....
Really appreciate it...
If you can find the original boot.img which is backed up by magisk, then you can flash it and update to b120 through TWRP
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
joke19 said:
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
Click to expand...
Click to collapse
That is only for the Magisk app, not to root the phone. Rooting the phone is a totally different procedure.
Number ome was the last zip with I root my phone with simple flash and number 2 is the new one.
Look inside.
Here the how to from magisk for a customer recovery.
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
Patching the images does not work. But installing the magisk.zip (the latest version) through TWRP or OrangeFox does work (tested and confirmed)! I don't get why it works when installing the zip and does not when patching a recovery.img but this is what we got...
Fun Fact, the instruction manual states you have to hold the HW key to enter recovery until the boot logo shows up, for me now the device is rooted on every boot without any issues, without the need to hold down any buttons.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
pawn_broker004 said:
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
Click to expand...
Click to collapse
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the good old days?
insetta said:
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the goof old days?
Click to expand...
Click to collapse
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
pawn_broker004 said:
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
Click to expand...
Click to collapse
So I'll have wait at boot for about 15 min? I'm afraid of screen burn-in.
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
mdalarian said:
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
Click to expand...
Click to collapse
Can you see your files while your phone is booted into OS?
Chances are, the encryption type changed from FDE to FBE, meaning the master key no longer works.
I suggest you backup everything now to a computer, because you can end up like me, and lose access to any file on the phone.
If you saved everything you deem precious from your phone, you need to do a wipe, and then FORMAT /data in recovery.
This will factory reset your phone, but it will work proper with the recovery.
i was on 12.2.5.0 rooted with magisk (by patching boot image pulled from zip firmware).
Phone will no longer boot (stuck at MIUI logo) after i upgraded to 12.2.6.0 with magisk patched 12.2.6.0 boot image. I don't understand why. My steps for updating as follow:
1) flash stock 12.2.5.0 boot image to phone via fastboot before upgrade
2) downloaded 12.2.6.0 full receovery zip file, extracted the boot image and patched it via magisk; copied the patched file to PC
3) copied 12.2.6.0 rom to downloaded_rom folder in phone, upgraded phone with it via Settings
4) phone rebooted to 12.2.6.0 normally after upgrade
5) rebooted to fastboot and flashed 12.2.6.0 magisk patched boot image
6) phone will not boot (stuck at MIUI logo)
7) phone again boots normally if I flashed back stock 12.2.6.0 boot image to it
Any enlightenment to what i did wrong and how to rectify deeply appreciated. Thank you.
(I have used the above method to upgrade rooted LG phones previously and it always went uneventfully; unsure what other steps are need for Xiaomi.)
potatohead said:
i was on 12.2.5.0 rooted with magisk (by patching boot image pulled from zip firmware).
Phone will no longer boot (stuck at MIUI logo) after i upgraded to 12.2.6.0 with magisk patched 12.2.6.0 boot image. I don't understand why. My steps for updating as follow:
1) flash stock 12.2.5.0 boot image to phone via fastboot before upgrade
2) downloaded 12.2.6.0 full receovery zip file, extracted the boot image and patched it via magisk; copied the patched file to PC
3) copied 12.2.6.0 rom to downloaded_rom folder in phone, upgraded phone with it via Settings
4) phone rebooted to 12.2.6.0 normally after upgrade
5) rebooted to fastboot and flashed 12.2.6.0 magisk patched boot image
6) phone will not boot (stuck at MIUI logo)
7) phone again boots normally if I flashed back stock 12.2.6.0 boot image to it
Any enlightenment to what i did wrong and how to rectify deeply appreciated. Thank you.
(I have used the above method to upgrade rooted LG phones previously and it always went uneventfully; unsure what other steps are need for Xiaomi.)
Click to expand...
Click to collapse
steps are good what u tried, at least i root mine every time with patched boot.img same like u. But im on Indonesian rom. didn't try 12.2.6.0 global or eu. But for sure steps u using is good. U can try older magisk manager app (maybe problem is new magisk)
Dadovvv said:
steps are good what u tried, at least i root mine every time with patched boot.img same like u. But im on Indonesian rom. didn't try 12.2.6.0 global or eu. But for sure steps u using is good. U can try older magisk manager app (maybe problem is new magisk)
Click to expand...
Click to collapse
After troubleshooting, I realized issue lies with Magisk modules. I neither deactivate nor remove the modules before updating the rom. It didn't occur to me this is necessary in the first place as previous experiences (on LG phones) did not call for it. After removing them, I am able to root the update via the patched boot image method.
For those facing the same problem, you can remove Magisk modules the following way (downgrading to the previous rom will not work as data partition will be corrupted):
1) grab a copy of the latest TWRP from MB
MBROMS - Browse /TWRPLMI at SourceForge.net
sourceforge.net
2) fastboot boot the twrp img file
3) decrypt your data partition using your phone's lockscreen PIN
4) download Magisk uninstaller from Github and install it
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
5) go to File Manager /data/adb/ folder and check whether there are any leftover traces of Magisk, manually delete any magisk, modules folder or files if they exist
6) reboot the phone into system and root it using the latest Magisk app (for patching of the previously extracted boot image)
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
wugga3 said:
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
Click to expand...
Click to collapse
Hello, thanks for the reply, I wanna get a few things straight before doing anything that have the potential to brick my phone.
1. My phone rn isn't rooted, so I cant uninstall or disable Magisk modules, I CAN root my device but it is very unstable and im not sure doing it is a good idea, maybe there's another way to disable them?
2. What do you mean by dirty flash? Using the device update section and selecting the official OOS version I downloaded from OnePlus.com?
1) may be forget about root for now as that's probably not the priority at this time. Getting a stable operating system is the priority. And skip TWRP (don't see the point of if being needed at this step either).
2) my best guess is that I've used oxygen updater from the play store to download the full update (not incremental update) that exactly matches the one you have installed now - or search here and find the match to download or used the OnePlus cite to get the file. Then once that is downloaded to your device - go to settings/system/system updates/local update and install and reboot. That's the dirty Flash as in don't wipe/reset your device either before/after the installation. I'm hoping that this method will clean up both the recovery and boot images to stock and hopefully restore stability to your device without the wipe/reset.
Hope that helps and restore the device stability without TWRP nor root.
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
NitayMa'ah said:
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
Click to expand...
Click to collapse
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
hammered58 said:
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
Click to expand...
Click to collapse
Ill try it now thank you
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's a image file you can flash in fastboot. It's
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Fixed!
Thanks so much for the suggestions, which I might didn't fully consider in a rush...
The solution was to root my phone, reboot it all shaky and try to disable all Magisk modules (took me 2 tries because of the crashes and stuff), then flash again the original boot image, rebooting, creating a rooted boot.img using Magisk and flashing it.
Littlemether said:
Here's a image file you can flash in fastboot. It's
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Click to expand...
Click to collapse
First of all thanks for the help but I ended up fixing it in another way.
Second of all, not really related but do you know if I can use this recovery on OP7Pro A12 custom Rom? (and flash it)