I have been trying to root my device several times now using the patched img method, and all of the time it has ended up soft bricking my device.
I would really like to know how to install Magisk the proper way with TWRP installed.
Please help me out
Thank you
Install Magisk from the zip file in TWRP - you have to do tethered TWRP boot ("fastboot boot twrp.img" - the UEFI bootloader on OxygenOS 10.3.0 and later are fixed so Fastboot tethered boot works correctly now), then install TWRP the usual way from zip installer, and finally reboot back into recovery then install Magisk (also from zip installer).
Sent from my OnePlus 6T using Tapatalk
Dr. Mario said:
Install Magisk from the zip file in TWRP - you have to do tethered TWRP boot ("fastboot boot twrp.img" - the UEFI bootloader on OxygenOS 10.3.0 and later are fixed so Fastboot tethered boot works correctly now), then install TWRP the usual way from zip installer, and finally reboot back into recovery then install Magisk (also from zip installer).
Sent from my OnePlus 6T using Tapatalk
Click to expand...
Click to collapse
Does using official TWRP work?
You may want to use unofficial version as it works better than official ones (the one at twrp.me is already way outdated).
Sent from my OnePlus 6T using Tapatalk
Related
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
I have been using many custom ROMs in the past months on my phone. I flashed stock Oreo just for fun. Now I lost my TWRP. It got replaced with Stock recovery. The main problem is I am unable to flash a recovery on my phone since then. I set my phone on USB debugging and open powershell & run the command " adb fastboot reboot"
Things get weird here. After flashing the TWRP image using fastboot flash recovery "mytwrpname.img" . Recovery shows a pattern(3×3) and asks me to decrypt. I do it and flash magisk but CTS/ Safety Net keeps failing. I wanted to reflash and again TWRP is gone.
What should I do. Sorry for the long story. Rules wanted me to be descriptive.
Help me out!!
Yeshu_bablu said:
I have been using many custom ROMs in the past months on my phone. I flashed stock Oreo just for fun. Now I lost my TWRP. It got replaced with Stock recovery. The main problem is I am unable to flash a recovery on my phone since then. I set my phone on USB debugging and open powershell & run the command " adb fastboot reboot"
Things get weird here. After flashing the TWRP image using fastboot flash recovery "mytwrpname.img" . Recovery shows a pattern(3×3) and asks me to decrypt. I do it and flash magisk but CTS/ Safety Net keeps failing. I wanted to reflash and again TWRP is gone.
What should I do. Sorry for the long story. Rules wanted me to be descriptive.
Help me out!!
Click to expand...
Click to collapse
Same problem happend to me , what i did
1. After decrypting , i flashed masgisk and lazyflasher
2. Booted to system , opened magisk manager and got root
3. Downloaded official twrp app from playstore
4. Opened official twrp app ,granted the supersu permissions
5. Downloaded and flashed the same twrp recovery from which i decrypted the device(very important to download and flash the same recovery version )
6. Boom you have twrp recovery forever :good:
shibbu18111997 said:
Same problem happend to me , what i did
1. After decrypting , i flashed masgisk and lazyflasher
2. Booted to system , opened magisk manager and got root
3. Downloaded official twrp app from playstore
4. Opened official twrp app ,granted the supersu permissions
5. Downloaded and flashed the same twrp recovery from which i decrypted the device(very important to download and flash the same recovery version )
6. Boom you have twrp recovery forever :good:
Click to expand...
Click to collapse
Is it important to flash lazy flasher?
Yeshu_bablu said:
Is it important to flash lazy flasher?
Click to expand...
Click to collapse
I don't think so. I'm on latest TWRP 3.2.3.1 by just decrypting and flashing Magisk 16.
Sent from my Moto G5 Plus using XDA Labs
I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/oneplus-6t/development/recovery-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Looks okay
However, the flash of the OS in TWRP is not clearly defined. Everyone is waiting for new update to try it in the TWRP... So, basically if you wanna flash it that way, you'll probably be the first.... This could put you in the risk of bricking the device though.
I have just done this. Yes you can boot the unofficial 6T recovery and then flash the installer no problem. However if you were running a OP6 ROM the 6T will not decrypt it, unless Im soing something wrong. On my phone once Im on a OP6 rom like LOS16 I can only use the Blu TWRP, if I go back to stock 6T OOS I have to use the 6T TWRP to decrypt. On either system I can bounce between TWRP versions without issue doing as you said, boot the img, then flash the zip, but I cant view anything. Going back to thr correct TWRP restores data access, no bricking worries that Ive run into personally.
There is no official TWRP yet...
Sent from my OnePlus 6T using Tapatalk
celtic426 said:
I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Click to expand...
Click to collapse
I did a post below for the update to Unofficial version with decryption working
https://forum.xda-developers.com/showpost.php?p=78267079&postcount=299
Sent from my OnePlus6T using XDA Labs
Thanks for the replies.
I successfully went from blu_spark TWRP to the newer faijta TWRP which has the option for decrypting.
That allowed me to use the recovery to flash the new OTA OxeygenOS update which I downloaded from oneplus.com.
Hi, I'm interesed on android beta 11 but I have a lot of customizations root related in Android 10, (includes soli radar use and GSM doze, for example).
The question is Magisk Canary version works on 11? Or the better is wait for a update or android stable version?
Hi, root is working with the canary version of magisk. Most of the apps who needs root are working....( Titanium Backup,Adaway) The only app that isn t working for me is Swift installer for theming.....
Greetz
Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!
bjonkheer said:
Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!
Click to expand...
Click to collapse
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020
caballero221 said:
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020
Click to expand...
Click to collapse
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.
caballon said:
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.
Click to expand...
Click to collapse
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Sent from my Pixel 4 using XDA Labs
caballero221 said:
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Click to expand...
Click to collapse
In the bootloader or fastboot mode.
caballon said:
In the bootloader or fastboot mode.
Click to expand...
Click to collapse
In the bootloader, via fastboot commands
Sent from my Pixel 4 using XDA Labs
I get the problem when I try to flash patched boot img, I end up in the bootload with status 'no valid boot slot to boot'. Any hints?
Can anybody upload patched magisk boot img for pixel 4 .020 ?
I get the same error in beta2, I think must flash the same boot.img of the zip (patched, obviously) but this means clean flash (flash-all) every update and lost the data
Sent from my Pixel 4 using XDA Labs
Has anyone managed to root android 11 beta3? when I try to flash patched boot img, I end up in the bootload with status "no valid boot slot to boot".
Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs
caballero221 said:
Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs
Click to expand...
Click to collapse
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.
grigiotitan said:
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.
Click to expand...
Click to collapse
I don't know why, but since beta 2 the method don't work. My pixel 4 fall in bootloop in the same way, and only fix flashing the OTA. Before, I think only work with full whipped beta installation and patch specific the boot.img of the full beta img flashed, but not tested yet
Sent from my Pixel 4 using XDA Labs
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..