Database Info

Correct versions of TWRP and Magisk

Hello folks,
I have a Pixel sailfish and I am on Nougat 7.1.2. I would like to just root it via Magisk. Bootloader is unlocked and i tried the latest version of TWRP 3.2.1.2 and latest Magisk 16.0, Magisk Manager is 5.7. Heres the problem, if I tried to flash TWRP and then reboot into recovery (to check if TWRP sticks) I could not access my files because they are all encrypted. I did removed all pass codes, fingerprint etc. Is there a specific version of TWRP, Magisk that I need to install on Nougat 7.1.2? My process is as follow (assume fresh Nougat is onboard):
1. Boot into bootloader
2. Fastboot twrp zip
3. In twrp, flash twrp .zip
4. Reboot into recovery to see if twrp sticks
5. If 4 passes, then flash Magisk zip (version 16)
6. Reboot into system
7. Install Magisk manager apk file
8. Open Magisk manager.
Please let me know,
Thank you very much

I would like to point out that my main goals are: run stock 7.1.2 and root. That's it, no fancy kernels or anything. 8.1 and 8.0 stock are killing my battery so i would like to do some tests on 7.1.2.

You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp

Thanks for this but i still have the same problem. Setting pin in Nougat, then reboot into bootloader, fastboot the .img file works. When in TWRP, it asks for my pin, i enter and manage to decrypt my data. Then I proceed to flash install tpwrp.zip. Process ends well but then when I reboot the phone, then reboot into TWRP (already installed). TWRP is there which means that the installation process is ok. However, this time, it does not ask for my PIN, there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted. Obviously, I cannot flash install Magisk.zip here. So I tried the following:
1. Fastboot the twrp.img to get into TWRP
2. Do not install TWRP but go to file manager and flash the Magisk.zip
3. The process ended well. I rebooted
4. Phone booted fine. I then installed Magisk Manager v5.7 (latest from XDA) via apk.
5. Installation ended ok.
6. I opened up Magisk Manager and got stuck at the Boot Logo.
I hope these are detailed, please let me know if you can help me.
Thank you very much
TENN3R said:
You can try set a pin, twrp in nougat worked perfectly.
So when you go in twrp with a pin set, it will 100% ask you the pin for decrypt.
Also, not sure if you made a writing mistake, but you have to fastboot the img, not the zip of twrp
Click to expand...
Click to collapse

maxwell0312 said:
... there is only a slide bar to "Swipe to allow modifications". I did so and my file manager only has a bunch of files with weird letters. I assume these are encrypted...
Click to expand...
Click to collapse
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.

TENN3R said:
Looks like some kinda problem with this twrp version.
Have you tried an older one, just to be sure? From what I remember, latest version made for nougat was 3.1.1 (?) but I'm not sure.
Maybe just try a 3.2.0, for example. Just boot it to avoid problems, don't flash the zip since you are not sure.
Otherwise, you can always try the manual boot.img patch method for magisk, so you don't have to use a recovery (official magisk thread -> installation instructions -> Via magisk manager)
These are only my ideas, not sure if they're gonna work or not.
Click to expand...
Click to collapse
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you

maxwell0312 said:
...
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
...
Click to expand...
Click to collapse
I think for this you better ask in magisk forums. Stable version of magisk also installs the manager apk, I noticed that beta versions don't.
You can find better support in official magisk thread :good:

Hey
maxwell0312 said:
Thank you very much for your help, I managed to fix and make TWRP stick, so no problem there. Problem now is Magisk doesnt work. Is there a problem with my order:
Flash Magisk.zip in TWRP.
Reboot. Install Magisk Manager then open it. I got stuck at this step. Magisk Manager is frozen upon open.
If anyone has any ideas, please let me know.
Thank you
Click to expand...
Click to collapse
What version of TWRP did you use..More like what did you do..I am having the same problem.

I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom

Fixed (update)
hardhead808 said:
What version of TWRP did you use..More like what did you do..I am having the same problem.
Click to expand...
Click to collapse
I flashed TWRP 3.1.1-1 then of course went in a recovery bootloop...Just flash SU..... PROFIT

maxwell0312 said:
I used TWRP 3.1.2.0 and 3.2.1.0. All failed. I figured that after flashing TWRP.zip via TWRP Recovery (which you get to after you do fastboot boot twrp.img from PC) , you would need to pick the correct Slot to reboot. Once you boot into the correct slot, then flashing Magisk.zip would work, I think. I kept messing around with reboot into A and B and got tired of it. Now I switched to Resurrection OS for sailfish, got all I want: theming and rootless support. I actually tried to go back to stock 7.1.2 myself to test if batteries improved. It turned out that it didnt really matter much. Also, if you are into Substratum theming like I do, its better to use an OMS rom
Click to expand...
Click to collapse
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck

fiverings said:
I found that when I use the uninstall magisk then flash magisk zip, if you watch closely, magisk will install some files to slot b also. Most of the time it will automatically download magisk manager. As far as battery life, my pixel XL was never better on 8.1. I installed the app is 9 preview 2 and my battery life is even better. You should move forward not back.
Good luck
Click to expand...
Click to collapse
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?

maxwell0312 said:
What is your SOT when go back with root? Also, what are the versions of TWRP and magisk that you use?
Click to expand...
Click to collapse
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck

fiverings said:
TWRP version is 3.2.1-2
Magisk is 16.0 version
Magisk is 16.4 installed version
Magisk Manager is 5.7.0
I read somewhere that I should be on 16.2 or 16.3 I read that after I installed 16.4 it didn't work at first, but about 4 or more hours later it started working. I'm certified and pass all tests. After installing Magisk, I always clear cache & data from play store app, then clear just cache from play store services.
Sot, I usually can get around 8 with 15-20% left
Good Luck
Click to expand...
Click to collapse
Thanks. I am on the smaller OG Pixel with 2770 mAh battery. I got 6h15 mins of SOT with 5% left. Not sure if this is normal

Was this problem ever resolved? I've been having problems that seem similar. I'm trying to use TWRP with Magisk and the stock google 9.0 for my Pixel, but I keep getting stuck. Wonder if someone has complete set of steps with specific versions of each of the necessary components.

bad post

Magisk Root without TWRP for OnePlus 6 Oxygen OS Android 10 Open Beta 5 | OOS 10.3.1

Latest TWRP doesn't support Android Pie 9.0 for OnePlus 6, or at least for me it didn't.
So, I've made a Magisk patched boot image for Android P that we can flash it in fastboot bootloader.
Note: This is not Oxygen OS ROM, this is just a patched boot img for Oxygen OS to make root work. You need to unlock the bootloader before proceeding with anything.
Note 2: Please disable Magisk modules in the Magisk Manager before flashing the patched boot, because some modules might not support the latest OOS and your device will bootloop. If the modules has been updated by the devs to support the latest OOS you can install the modules after that.
Note 3: Sorry guys, I haven't tested the Android Q Developer Previews. Even though Magisk is supported on Q, please flash it at your own risk.
For older versions download from here: Google Drive
Folder updated with Stock boot images as well.
OOS 10 Open Beta 5 Patched Boot
OOS 10 Open Beta 5 Stock Boot
OOS 10.3.1 Patched Boot
OOS 10.3.1 Stock Boot
Flashing instructions:
Code:
fastboot boot (patched_boot_filename_here).img
or
fastboot flash boot (patched_boot_filename_here).img
Thanks @vlaf
reboot to system (if you make another reboot the root won't stick, so continue with the following steps)
Open Magisk (in settings select beta channel) and click install and install Magisk again with Direct Install (recommended)
reboot again and the root will stick even after the reboot.
The thread I followed for the instructions is here. Thanks for @b1czu
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Even easier way to root without TWRP:
1. Install OTA update (Don't reboot).
2. Open Magisk Manager, install Magisk and choose "Install to Inactive Slot (After OTA)" (Now reboot).
3. Now you are rooted without TWRP and without any boot img hassles as well.

wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！

Not work here. Bootloop, only see Bootanimation not more.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
If you are I can give you the stock boot image for reverting it.

ManikandanGuru said:
I've tried it again and it worked for me
Are you using Android P Developer Preview 3?
Click to expand...
Click to collapse
Yes lol.

It works for me. That's a great help. Thank you.

SpectraFun said:
Yes lol.
Click to expand...
Click to collapse
I've updated the Google drive folder with the stock boot image for DP3.
Download and flash it to revert the bootloop.
I'm not really sure why it didn't work for you. Sorry about that.

Raymond.William said:
wow dude that's useful. I don't need TWRP that bad but I need root to use Titanium backups.
Thanks man！
Click to expand...
Click to collapse
Yeah TiBu is the main reason for me as well.

Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.

geoff5093 said:
Worked great for me, thanks! Only issue is I can't get Pokemon Go to work anymore, I'll play around with it.
Click to expand...
Click to collapse
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.

Yeah I did, but I rebooted an additional time and everything works now!
ManikandanGuru said:
Did you try hiding Pokemon Go in Magisk hide? Because the latest update addressed the Pokemon Go issue as far as I know.
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk

Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.

geoff5093 said:
Yeah I did, but I rebooted an additional time and everything works now!
Click to expand...
Click to collapse
That's great.

What about safety net?

G0dofWar said:
What about safety net?
Click to expand...
Click to collapse
The first one, ctsProfile, fails. But the second one basicintegrity passes. I believe the only app I use that checks safetynet is PokemonGo and that works for me.

SpectraFun said:
Not work here. Bootloop, only see Bootanimation not more.
Click to expand...
Click to collapse
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first

toastyp said:
Did you unlock your bootloader? Don't think you can boot rooted/unsigned images without unlocking first
Click to expand...
Click to collapse
Lol sure is unlock.

MrSteelX said:
Easy way to install twrp is to fastboot boot twrp. From there, you must turn on adb sideload and push twrp to phone because it will not decrypt storage. After install, reboot to recover and it will ask for password to decrypt. Then just flash magisk to have root with working twrp. Also, you have to use twrp 3.2.2 or it will crash.
Click to expand...
Click to collapse
Yes. This worked. A simple workaround to get twrp working with encrypted Android P

Download link updated with Beta 1 patched image.

[OOS 5.1.11] Pre-Rooted Bootimage

Hi there,
OnePlus is rolling out the OxygenOS 5.1.11 update! According to this thread, I made a pre-rooted bootimage for you to flash
I used the guide on the mentioned thread and used Magisk Manager 5.8.3 (129) with Magisk 16.7
For those who'd rather like to do it on their own, I'll also attach the original bootimage of OOS 5.1.11.
Downloads:
- patched bootimage [MD5: 5EC7C328AEE0D38B43A2727BCD767378]
- original bootimage (5.1.11) [MD5: B6790A9D38F41E0EBC6830D1076FAFF0]
Video instructions:
The awesome @GizmoFreak made a nice step-by-step video for you! :good:
Special thanks for his guide at @b1czu, [MENTION=4470081 ]TopJohnWu[/MENTION] and @GizmoFreak! Please also give him a "thanks" :good:
UPDATE: Magisk 17.1 was released by @topjohnwu ! Many fixes and most important: "Install to inactive Slot (After OTA)" is back! Upgrading our ROM should now be much easier again since already rooted users don't need to use the whole fastboot thing again. However, for new 'unrooted' users, I'll still provide here the always latest patched bootimages.
Cheers,
T.Bear

thanks do we still need to do the direct install from magisk manager?

czerdrill said:
thanks do we still need to do the direct install from magisk manager?
Click to expand...
Click to collapse
Yes, if you whish to keep root. Otherwise your device would take the stock bootimage for the next boot again. This patched one is only for booting with 'temp' root privileges so that you can use magisk Manager to direct install the root stuff to the original bootimage.

does this pass the safety checks?

It's the same procedure as in the thread I mentioned! This is not a standalone 'project', just the missing bootimage for the latest OxygenOS update.
But to answer your question, yes if you follow the instructions on the mentioned thread it passes all checks.
Only if you install things like Xposed framework it won't pass.

RiTCHiE007 said:
does this pass the safety checks?
Click to expand...
Click to collapse
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
fastboot boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
EDIT 1: Added 3rd command which I used but forgot to mention it here ?. Thanks GizmoFreak !

amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
SafetyNet will show the response is invalid because Google recently updated the SafetyNet API. Now developers need to use an API key to access SafetyNet. We need to wait for Magisk to be updated.
---------- Post added at 11:03 PM ---------- Previous post was at 10:56 PM ----------
amihir said:
I followed these steps -
1. Downloaded and installed 5.1.11
2. Downloaded patched 5.1.11 boot image
3. Rebooted phone to fastboot mode
4. Installed the patched boot image using this command -
Code:
fastboot devices
fastboot flash boot boot.img
5. Phone booted.
6. Opened Magisk Manager>Install>Direct Install (recommended)
7. Rebooted phone
8. Opened Magisk again, checked safety net, failed.
Then I used root checker, even that showed Safety net fail.
But I was able to Play Pokemon Go which relies on safety net
Click to expand...
Click to collapse
And the second command should be fastboot boot boot.img

Plz make for H2OS OB 1

Thanks

Do I need to install 5.1.11 first?

williamcll said:
Do I need to install 5.1.11 first?
Click to expand...
Click to collapse
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Created a video. I hope it will make things easy for others.

Depressed T.Bear said:
Here's how I update:
- install update
- reboot to fastboot mode
- boot using the patched bootimage
- install Magisk 'direct'
- reboot & done
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Will I lose my data in the process?

no, all are retained

GizmoFreak said:
Created a video. I hope it will make things easy for others.
Click to expand...
Click to collapse
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Sent from my OnePlus 6 using XDA Labs

Depressed T.Bear said:
Thank you very much for this nice and helpful video! With your permission, I'll link it here on my post when I'm back home!
Again, thank you!
Click to expand...
Click to collapse
Yes feel free to add it to OP.

ed-gonzo said:
no, all are retained
Click to expand...
Click to collapse
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)

Brother, your download link is not working?

williamcll said:
which version of magisk should I get? I see everything from 16.0 to 16.4 (which I am using right now on my 5.1.9)
Click to expand...
Click to collapse
Magisk 16.7 is up to date

What's the benefit of keeping stock recovery and not rooting via twrp?

Can't install Magisk 17.1 on OxygenOS Pie Open Beta 2

Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
UPDATE (09/12) : Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx to exelinguy.

Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.

Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.

Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Will upgrading reset the phone or will just upgrade with the same data?

sanu26661 said:
Will upgrading reset the phone or will just upgrade with the same data?
Click to expand...
Click to collapse
it depends on the situation. If you're on the Open beta updating to a newer build, the data will still be there, but if you're on the open beta downgrading a build or downgrading to oreo, your data will be lost.

whizeguy said:
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Click to expand...
Click to collapse
I already tried, still nothing

try to change slot A / B

dum143 said:
try to change slot A / B
Click to expand...
Click to collapse
When you install rom, install twrp and reboot to twrp it changes slot. If he has done it 2 times both slots are tested.

exelinguy said:
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Click to expand...
Click to collapse
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop

Azhar_Fahry said:
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Click to expand...
Click to collapse
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post

exelinguy said:
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
Click to expand...
Click to collapse
Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx for helping me bro. appreciate it.

I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.

whymista said:
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
Click to expand...
Click to collapse
have u tried to flash the open beta rom zip? I got that problem too, it's shows random folder and it contains nothing. but after I flashed the open beta rom and re flash the twrp from fastboot, it's fixed.

Flash TWRP Via Magisk?

I rooted my phone using the Magisk patch boot image feature, and was wondering if you can flash the TWRP zip file via magisk to install it? Thanks!

Sparrowhawk120 said:
I rooted my phone using the Magisk patch boot image feature, and was wondering if you can flash the TWRP zip file via magisk to install it? Thanks!
Click to expand...
Click to collapse
Hi,
yes you can. Grab the latest installer zip and install like any module. Reboot into recovery and flash magisk again.
Reboot into system , and done.

Yeah this is it.

@soka said:
Hi,
yes you can. Grab the latest installer zip and install like any module. Reboot into recovery and flash magisk again.
Reboot into system , and done.
Click to expand...
Click to collapse
awesome, thanks!

What? I thought the OP asked if it is possible to flash TWRP via the Magisk app? But @soka replied as if to answer how to flash magisk itself? Or am I getting this wrong? How can you flash anything besides official Google signed .zips with stock recovery?

Magnufire2 said:
What? I thought the OP asked if it is possible to flash TWRP via the Magisk app? But @soka replied as if to answer how to flash magisk itself? Or am I getting this wrong? How can you flash anything besides official Google signed .zips with stock recovery?
Click to expand...
Click to collapse
@soka replied :
Grab the latest installer zip and install like any module. (@soka was talking about TWRP zip file)
Reboot into recovery and flash magisk again.
(This is the Magisk zip file you should already have flashed from rebooting into TWRP now)
Reboot into system , and done.
I have to try this... This seems just way too easy...