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

[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?

[ROOT] and [Solve] every issue in oxgyen os open beta {1/2/3} (Android pie 9.0)

I've managed to solve all problem by rooting and installing magisk
1. Some apps may not work properly
I have tried every app I used in oreo and each app works fine (I know this is not a solution )
2. Google pay not works
Solution-Google pay works by using a magisk module called
*tezhider4magisk*
https://androidfilehost.com/?fid=5862345805528042557
3. Google play shows device not certified
Solution - Google play shows device is certified using magisk module called
*ClearPlayStoreWithServiesData4Magisk*
https://androidfilehost.com/?fid=890278863836289937
4. Safety net not passed in magisk on open beta 1/2/3
Solution - for safety net to pass in magisk we need to edit a line in build.prop (have to some file explore like es file explorer or root explorer to edit build.prop)
Replace
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
Click to expand...
Click to collapse
With
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Click to expand...
Click to collapse
5. For rooting oxgyen os open beta 1/2/3
Follow guide from developer [Manikandanguru] (all thanks to him?)
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

Is there a fix yet for aod/ambient display yet?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/

For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Doesn't work, crashes display settings.

sahu.prashant said:
Try this maybe? It worked for me on OOS Oreo at least. Didn't try it on P yet but should work I think...
https://www.google.co.in/amp/s/www....always-on-display-oneplus-6-oneplus-5-5t/amp/
Click to expand...
Click to collapse
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?

Gmos24 said:
Is there a fix yet for aod/ambient display yet?
Click to expand...
Click to collapse
For me aod/ambient display works perfectly
Have you dirty flashed new beta
Try doing a factory reset I hope that will fix it

BossNexusS said:
For me my nfc is not working for some reason, the option in settings is greyed out and it's causing so many wakelocks that it's also killing my battery.
Click to expand...
Click to collapse
Try clearing cache from recovery that solves a lot of issues

Gmos24 said:
Edited message to fix the quote to the correct person.
I had to uninstall it on oos ob1 because it was making the display settings crash. I just reinstalled it on hydrogen os beta 4 and it works again however the status bar doesn't turn black. Any idea on how this could be fixed or if it's an easy fix?
Click to expand...
Click to collapse
Woah! Sorry about that, I guess I should have tested it first on P. I'll flash OOS Open Beta 2 today and then try this mod. Will update if it works.
And status bar issue is a strange one, no idea about that!

Can we get incremental ota update even when unlocked and magisk installed (no twrp)?

I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now

droid-devz,
Flash Oos ob02, then twrp blu spark.
Reboot to twrp to check if it's working. Flash Magisk 17.1.
Reboot to system.

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Yess i just updated from beta 1 to beta 2 no problem
You'll just lose root everytime you update and have to install just magisk again
Don't install custom recovery that causes problems I guess use the above method (in the thread)

droid-devz said:
I cant boot once I flash Magisk 17.1
Every time I flash magisk, I get in boot loop. I have used official and Blue TWRP both to flash magisk every time I am in boot loop.
I have to reflash everything to get booting. How to root OB 2 now
Click to expand...
Click to collapse
Official twrp doesn't work only blue star twrp works

Veestaai said:
Can we get incremental ota update even when unlocked and magisk installed (no twrp)?
Click to expand...
Click to collapse
Probably not..magisk root rewrites the boot image..safest bet would be to use update manager to flash whole rom updates, then reinstall magisk.

CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?

JRevenge said:
CAUTION:
With the latest update of the BETA 2, once you give the command in fastboot "fastboot boot twrp.img" the phone goes into softbrick with a Qualcomm screen. Has anyone found an alternative method?
Click to expand...
Click to collapse
does not happen with me !!!

Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?

digidude512 said:
Sadly the build.prop fix for SafetyNet only worked on Open Beta 1.
Anyone got SafetyNet passing on Open Beta 2?
Click to expand...
Click to collapse
safety net passes with current canary build of magisk
plug this into the custom section in the magisk settings under update channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json

sorry, hit send before it finished uploading

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Android 10 - Root

Hey guys!
I have a rooted pixel 3. I want to upgrade to Android 10 if they release in the next day or so as reported. I've read they made some progress with magisk...
What is my best bet here?
I would love to keep root, but most importantly I want to keep my data and upgrade to Android 10.
I do really want to keep root too.
Is there a guide?
Thanks!

I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.

kkjb said:
I had Q beta 6 working with current process. Canary channel still only works by patching your boot.IMG. So with twrp still not working on beta 6. All instructions say image flash not possible upgrade path. So until 10 is stable + twrp stable I don't know either. I will just flash 10 and see also. But I really don't expect data to retain, will try though.
Click to expand...
Click to collapse
This is a build of blueline TWRP-3.3.1 from the crosshatch tree that is supposedly working from a follow-up post.
https://forum.xda-developers.com/pi...pixel-3-xl-t3861623/post79995400#post79995400

So is there no way to root just now?
I upgraded from a rooted Android 9 by downloading the factory image for 10 and removing -w from the bat file. All okay, data retained.
But there is no TWRP that works and I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.

Audioboxer said:
I tried to fastboot boot a magisk patched boot image from the factory image zip file and it didn't work.
Click to expand...
Click to collapse
That works, did it myself. Make sure you are on the latest canary build of Magisk.

TonikJDK said:
That works, did it myself. Make sure you are on the latest canary build of Magisk.
Click to expand...
Click to collapse
Thanks, I was on beta.

Does edxposed work with android 10?

Bubbler4343 said:
Does edxposed work with android 10?
Click to expand...
Click to collapse
It did not work on Android Q Beta 6... just bootlooped. So I am assuming it still does not work for 10.

It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?

stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
Did you try the twrp version in post #3?

Just got a notification for upgrading to android 10 , date Tuesday 10.19 pm.
Since there is no xposed available for Android 10, i' ll stick to android 9

Looks like TWRP won't decrypt. Has anyone ADB sideloaded the Canary version of Magisk through TWRP? That was the old workaround when decryption didn't work.

stilltli said:
It does not work for me, guess I should have removed my magisk modules before updating :crying:
TWRP also seems not to work so I see no way to remove these modules now...
Does anyone have a suggestion besides wiping the device?
Click to expand...
Click to collapse
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.

jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I assumed it was for 3XL only, glad you pointed that out! It does boot, however TWRP is not able to mount anything (system, data etc.), so I guess this is a dead end.
sliding_billy said:
I was under the impression that fastboot of twrp-3.3.1-0-blueline could be used for certain things in 10 (possibly flashing Magisk uninstaller). Also, be sure you have the canary uninstaller.
Click to expand...
Click to collapse
As stated above I am unable to access any partitions, so I guess I'm also unable to run the uninstaller :crying:
Thank you both for your suggestions :good:

jd1639 said:
Did you try the twrp version in post #3?
Click to expand...
Click to collapse
I have tried, and it doesn't decrypt from what I see (booted into TWRP, but no file access)

Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not

Edemilorhea said:
Uhh,so now, android 10 can root or not!?
My English isn't good....
So hope someone tell me root is work or not
Click to expand...
Click to collapse
I rooted 10 with no issues.

sliding_billy said:
I rooted 10 with no issues.
Click to expand...
Click to collapse
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?

Edemilorhea said:
Oh cool！！
So just fellow android 9 root step on android 10?
It's worked?
Click to expand...
Click to collapse
No, you have to use a Magisk patched boot with canary magisk. Not even close to the old way. No TWRP. Lot of info on here. You might want to start reading before jumping in.

Manually patching the boot image with the canary build "works" - as in - it shows Magisk installed in Magisk Manager and can grant Superuser to apps --- BUT, you can't write to system, so things like Adaway don't work, also Google Pay doesn't work. I'm not sure what you use root for, but this makes it fairly useless to me for now.