So I used msm tool to go back to 9.5.3 to unbrick my OP7 Pro and then updated the firmware to 9.5.4 because apparently TWRP fails on adb unless you go to firmware 9.5.4 or above I believe. So I did adb commands and did the TWRP I'm file and booted into TWRP just fine. Then adb sideloaded and flashed TWRP zip file and TWRP sticks fine until I go back into recovery and flashed the magisk beta 20 version and 19 does the same thing. After I flashed magisk zip hell breaks loose. Literally TWRP won't stick unless I go back to adb and do fast boot then twrp.img file and force it to show up even then if I were to adb sideloaded it again and flash the TWRP zip again and see if it sticks without flashing magisk it still will not hold. I don't understand what is happening. I just want to get my OnePlus 7 pro with magisk and working g TWRP without any troubles at all. Should I update it to a different firmware or is the magisk or TWRP files I downloaded wrong what is the deal???? TWRP is the 3.3.4 or whatever and so is the img file and magisk is 20 version please let me know the solution it makes no sense to me. I have to keep msm unbricking back to 9.5.3 and it's pissing me off.
You got two ways:
- flash TWRP
- Boot to TWRP
- flash Magisk (DO NOT REBOOT)
- flash TWRP again (use the TWRP installer zip always)
Or...
- Flash TWRP
- Flash Magisk
- Boot device
- Flash TWRP installer as a module in Magisk
Didn't work
I tried all methods stated above and none of them are confirmed working on 9.5.4 Could you confirm it working on that firmware please? I just flashed twrp zip 3.3.4 file through magisk no luck and magisk is no longer rooted now with twrp... I'd have to run adb command and fastboot boot twrp.img to get twrp to come back and reflash magisk now... However that means twrp will still not stick at all. Which doesn't make sense. If you get it working on this firmware please let me know because I've been trying to get both to stick for awhile now. I did get it to work on another firmware but I couldn't remember which one... But technically it should work on firmware 9.5.4 because that is the firmware that supports adb commands where as 9.5.3 does not. This is gm-1917 model global/US 9.5.3 is the first firmware it comes with.
Want to chime in here and add I have the GM1915 and I have the same issue even after following the above steps. I've updated and used the MSM tool multiple times but TWRP never stays on the recovery, in fact, I usually find the OEM recovery to be gone completely after flashing so if I attempt to boot to recovery it just sends me to my bootloader.
Bump
Has anyone rooted F2 pro on android 11 version global miui 12.2.4?
I need help ,bootloader is unlocked.Kindly help
What's the problem?
I just rooted my F2 pro with android 11 version RJKEUXM 12.2.3.0, everything is working.
My steps:
Install Magisk Manager
Copy original boot.img to Phone
Patch original boot.image via Install Magisk
Copy patched boot-image to PC
Phone Fastboot-Mode:
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
Tiemichael said:
What's the problem?
I just rooted my F2 pro with android 11 version RJKEUXM 12.2.3.0, everything is working.
My steps:
Install Magisk Manager
Copy original boot.img to Phone
Patch original boot.image via Install Magisk
Copy patched boot-image to PC
Phone Fastboot-Mode:
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
what about fingerprint? is it working fine?
Yes, everything is fine (safety net, fingerprint, banking apps). I don't use Google Pay ...
For Safety Net: follow here, and here (only needed since yesterday!)
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
stoigeboiii said:
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
Click to expand...
Click to collapse
Try patching boot image with magisk 19. Boot it first. If booting okay then flash magisk patched image to boot a & b. Plz let me know if any luck.
stoigeboiii said:
I got a Pixel 3 that I've been trying to root for a while. I've got the bootloader unlocked (OEM unlocking). I noticed that my Factory image is 9.0.0 (PD1A.180720.031, Sep 2018, Verizon) and I'm not sure if the Verizon is the reason it's not working. That is definitely my current build though. I've tried making the image with both the stable build (Magisk v23.0) and the current canary build.
I was able to boot it again by flashing the main boot.img in Fastboot. I've tried installing it on both boot_a and boot_b together and separate and it still doesn't work. I've been using fastboot flash boot boot.img not twrp
Does anyone have any idea of what I can try or what I'm doing wrong?
Click to expand...
Click to collapse
Did you do the "fastboot flashing unlock" step (this will wipe your phone) to unlock your bootloader? OEM unlocking does not unlock the bootloader, it only allows it to be unlocked with fastboot.
Generally speaking, Verizon phones cannot be bootloader unlocked. However a few people have successfully unlocked new phones, fresh out of the box, that have never been connected to Verizon. It appears the bootloader is not permanently locked until the initial connection to Verizon.
dcarvil said:
"fastboot flashing unlock"
Click to expand...
Click to collapse
When i typed that it said already unlocked
Device already unlocked
I don't think I have a verizon Model but I actually have no clue
ashish_jha said:
magisk 19
Click to expand...
Click to collapse
I tried to do this with Version 19.4 but no luck
Any other ideas?
stoigeboiii said:
I tried to do this with Version 19.4 but no luck
Any other ideas?
Click to expand...
Click to collapse
But did u patch it with magisk before booting?
stoigeboiii said:
I tried to do this with Version 19.4 but no luck
Any other ideas?
Click to expand...
Click to collapse
There are several things you can try:
How are you transferring the the images between your phone and PC? MTP can corrupt files, so use adb push/pull or SFTP.
Since you are on Android 9, you should be able to boot TWRP without installing it. Copy magisk.zip to your phone, do "fastboot boot trwp.img", then Install from TWRP. If you use Magisk 23, rename magisk.apk to magisk.zip. If you use 19.4 or 20.4, just download the zip file.
Search the Magisk support forum at https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382 for similar problems and solutions.
If all else fails, give me the md5sum of your patched boot image. I'll patch that image, and compare the md5sums to see if I get the same result.
Newbie here trying to root Vivo Y21 (Android 11) using Magisk. I am using a bootloader unlocked Vivo Y21.
Magisk 23 (stable): Stuck at Fastboot on using a patched boot.img
Magisk Canary: flashed and rebooted successfully, but shows not installed and no root
About the phone :
Android 11
Ramdisk: Yes
A/B: No
Zygisk: No
Custom Recovery does not seem to be available for Vivo Y21. Flashed from Fastboot mode:
>>fastboot flash boot <patched_boot.img>
>>fastboot reboot
Any ideas on what I did wrong or could try would be really helpful.
Me too.... I too have the same problem. Someone help.
undapri said:
Me too.... I too have the same problem. Someone help.
Click to expand...
Click to collapse
have you unlocked bootloader?
Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?
even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!
OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?
Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.
Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.