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.
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.
Anyone know how to root if I'm already on 9.5.6?
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.
The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk
larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions
OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you
With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk
skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi
Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.
I just purchased a new OnePlus 7 Pro yesterday and immediately set about rooting it. This is the process I followed:
fastboot oem unlock
fastboot flash boot twrp-3.3.1-4-guacamole.img
TWRP: Install > Select Storage > Internal Storage > Magisk-v20.3.zip
TWRP: Wipe > Format Data
I rebooted and was confused when I wasn't rooted. It seemed the last step had undone my root, so I went back into TWRP and installed Magisk again this time without formatting data. When I rebooted I had root and all was well.
However, there was an OEM update available that warned me it would remove root if I installed it. I found this guide to install an OEM update without losing root, which basically says to download the update via Oxygen Updater and then install it from TWRP. On step 6 is says to select the "Inject TWRP after install" option, but this didn't exist in my TWRP. I went ahead without it, thinking maybe it was enabled by default in my newer version of TWRP. The installation seemed to go without a hitch, but when I rebooted after I was stuck in fastboot. I couldn't boot my phone, nor could I get back into TWRP or regular recovery, only fastboot.
I tried flashing TWRP again using fastboot, but to no avail. I also tried running fastboot -w, but was still stuck in fastboot. I did some more research and found this comment which made it seem like all I had to do was download 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT from here and then run flash-all.bat. Once I did so I ended up stuck on the following screen:
Code:
QUALCOMM CrashDump Mode
--------------------------
dm-verify device corrupted Force Dump
kernel_restart
I can't seem to do anything at all with my device; not even turn it off. I tried holding the power button down for nearly a minute and no response from the phone. Is there any hope at all for my phone or have I properly destroyed it?
https://forum.xda-developers.com/oneplus-7-pro/help/mistake-kernel-error-t4029743
Same thing happened to me and I searched around a bit and found resolution. You can try what I did or try msm tool but search first as crashdump error is becoming common issue it seems
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Thank you so much! I thought I'd corrupted fastboot and permanently bricked the phone.
Once I was in fastboot I used tool all in one to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip onto my phone by picking Flash Factory Images, and now it's back up and running.
jasons1004 said:
I held both volume buttons until restart and let go of one of them to get into recovery and then boot to boot loader if needed
Click to expand...
Click to collapse
This was the magic trick I needed to know. Holding both volume buttons didn't quite work for me. I held them both down for over a minute and nothing happened. Then I tried holding down the power button and that seemed to work after several seconds. I didn't hold down volume down quickly enough the first time, so I had to do it again. I held both volume buttons and the power button for over a minute, but again, nothing. I tried a couple more times and got it to work. Haven't been able to figure out exactly what causes it to exit the CrashDump mode, but the volume buttons together seems to be the important part.
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
Just use tool to flash 9 then after first boot fasboot flash whatever 10 build you can find. Then after first boot of 10 try boot twrp and install twrp.
Honestly I just used the tool to root and flash recovery. There is a button for that and just pick your files. Good luck
altayh said:
This time I tried doing the OEM updates first, thinking that attempting to install them manually is what caused my problem. First I installed the 10.0.3.GM21AA update, then after rebooting I installed the 10.3.0.GM21AA update. At this point it said my system was up to date, so I want ahead and booted into fastboot and ran fastboot flash boot twrp-3.3.1-4-guacamole.img. No errors, but no TWRP either. My phone was stuck in fastboot again.
Is it necessary to stick with 9.5.13 if I want root? Is there some way to get TWRP to work with 10?
Click to expand...
Click to collapse
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
redpoint73 said:
You need to use a more recent versions of TWRP with Android 10. Current unofficial version -74 should work. So in your current condition, you should be able to simply boot TWRP (using the correct version), flash TWRP installer zip (if you want TWRP installed), flash Magisk (current version is 20.3) and reboot and you should have root again.
Click to expand...
Click to collapse
Ah, I was using the Official TWRP App to get the images so I was under the impression that twrp-3.3.1-4-guacamole.img was the latest. I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
redpoint73 said:
Easiest way I've found to install the OTA updates, is to simply install the update through the phone settings, do NOT reboot immediately after the update, go into Magisk Manager, flash TWRP installer zip as if it were a Magisk module (optional, if you want TWRP installed), then install Magisk picking the option "Install to inactive slot (after OTA)". Than just reboot, and you should be updated and with root.
Click to expand...
Click to collapse
This is good to know. Thanks.
Just to follow up, I applied the available OTAs through the phone settings (up to bulid 10.3.0.GM21AA) and then followed the More articulated but fully functional instructions to install TWRP 3.3.1-74 Unified Unofficial Q. Everything went well and I'm now up to date and rooted. Thanks again to both of you!
altayh said:
I assume you're saying I should use TWRP 3.3.1-74 Unified Unofficial Q by mauronofrio from over here instead.
Click to expand...
Click to collapse
That is the correct TWRP to use ("Unofficial" version -74), as it appears you have already determined.
I don't know why the "official" versions have fallen so far behind. It's been months stuck on version -4, so it seems that they have stopped going "official" for some reason. No matter, the unofficial versions are working fine (and in fact required for Android 10 as you now know), so the "official" tag seems like a technicality.
On these OnePlus phones I don't know why they love Qualcomm Crashdump mode. I fixed it sort of like you, but this worked 100%. You hold all 3 buttons (power, vol up, vol down) and you bypass the crashdump (takes several seconds 5 maybe 10), just quickly let go so you'll be in fastboot mode and can work your magic to fix the damn thing....
I even contacted OnePlus on an 8 they had no idea what to do...
Fastboot flash boot recovery.img <-- bad idea
Fastboot boot recovery.img <-- provit
Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!
99mike199 said:
Hey,
I updated already rooted phone with Oxygen updater (forgot that he will remove TWRP in auto install) and now can't get it to fastboot into TWRP with ADB. I tried several .img files but non worked. Every time it goes to Crash dump.
Did someone successfully fastbooted into one? Or the only solution is to go back and do it manually from OOS 10?
Thank you!
Click to expand...
Click to collapse
If you are on OOS 11 then use the attached file and try the below steps.
1. Reboot to Fastboot mode.
2. Use command : Fastboot boot boot.img (use attached TWRP alone)
3. Once rebooted to recovery mode Install recovery by Advanced -> Install Current TWRP . This should install the image automatically to your device.
Reboot your phone to system mode and then reboot it back to recovery mode later.
Hope the above helps.
TWRP is wonky on A11, for now.
If I'm not mistaken the TWRP provided by other poster will have issues with making and restoring backups.
If you are still rooted and looking for a backup/restore method, you might as well leave TWRP alone for now and simply maintain root through the Magisk app. If root was lost, then you can use the version provided here: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4306803/ which is likely what other user posted, to restore root and then wait for Google to release the full deets on A11 to hobby developers who can then make a new TWRP.
This worked for me to get back TWRP and root after upgrading. Thank you very much!
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)