Develop Bugs

[x Force] Installing Magisk Root & Universal Systemless Interface

Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased

JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.

sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.

For this procedure is necesary unlock the bootloader?

Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.

Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.

Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.

Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!

And how are we gonna unlock the bootloader?
Is there a way to do that?

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.

DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers

jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).

DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?

humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct

I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?

the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol

j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.

Check out this post, it works like a charm.

Project Treble & S10+

So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:

I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.

Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.

Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....

Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.

NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.

uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's

NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.

uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho

Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]

thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.

sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.

NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value

thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:

uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename

NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting

vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.

In the meantime, is someone running GSI as a daily driver?

sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.

Issues Rooting Pixel XL with TWRP/Magisk

I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.

ookami007 said:
I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.
Click to expand...
Click to collapse
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Need to try this soon, glad to see it's working ?
Sent from my Pixel XL using XDA Labs

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.

tyler.durden said:
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.
Click to expand...
Click to collapse
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.

tyler.durden said:
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.
Click to expand...
Click to collapse
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU

Tulsadiver said:
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU
Click to expand...
Click to collapse
Thank you! Magisk finally installed using the boot.img patching method, and now I have root access.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?

smithilberry said:
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?
Click to expand...
Click to collapse
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.

Tulsadiver said:
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.
Click to expand...
Click to collapse
Yes, that's what I meant. I also got it working. I used TWRP 3.3.0 and it worked. Not sure what the reason would be.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently. ?
Sent from my marlin using XDA Labs

flash713 said:
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
You rock! Appreciate you telling me this! I believe I understand more now that I've read about the A/B partition for a few weeks.. Pixel XL forums actually has the most detailed information of A/B that I've seen yet. Cheers.
Sent from my marlin using XDA Labs

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs

flash713 said:
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
To roll back you not only have to flash the entire image but you'll have to wipe your phone.

TWRP boot looping?
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?

SeekMocha said:
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?
Click to expand...
Click to collapse
NEVER MIND: I was using wrong version of TWRP.

SeekMocha said:
NEVER MIND: I was using wrong version of TWRP.
Click to expand...
Click to collapse
What TWRP version did you use?

[GUIDE] How to Root OnePlus 7T without TWRP

So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi

Flashed and working flawless.
Really thanks for this.
Awesome work bro.

Can you please upload the patched boot.img please? I dont see it in the above folder at all.

nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder

Working, thanks a lot @mauronofrio

I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.

jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene

I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.

@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.

RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.

nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?

jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it

Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.

Thanks, rooted successfully

?
To be honest need video tutorial asap?

mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.