Updated guide for TWRP/SuperSU Installations? - Google Pixel XL Questions & Answers

Got a replacement Pixel XL for my bad 6P, Wanting to install twrp and root right away.
Does anyone have a decent guide for installing TWRP and SuperSU? I've seen different (outdated) methods and want to clarify that I'm doing it right the first time. I'm no spring chicken when it comes to this stuff but it seems every new device is different.
From what I've found this is the process:
Unlock bootloader using fastboot
-Fastboot flashing unlock
-Fastboot oem unlock
Fastboot boot path/to/twrp.img
Within TWRP, install the twrp RC2 zip file.
**Do I need to install the verified boot signer zip? I'm not sure if this is needed with newer versions of SU?
**I've read RC2 doesn't handle nandroid backups well. Is it better to stick with RC1?
**If I need the verified boot signer zip, which verisons do I use with which versions of TWRP?
Here's where I'm a little confused. Do I just go into TWRP and flash SuperSU 2.82? What version of SuperSU should I flash? Do I need to flash anything else along with it? I'm sticking with Nougat until more Android O ROMs are available. Because of this I believe I'm safe installing 2.82 Stable instead of the beta.
I plan on using Magisk as I prefer that over SuperSU, is there anything I need to know before I install Magisk over SuperSU after I reboot and verify everything works with SuperSU?
Any input would be greatly appreciated.

Related

Help with Suhide in Zenfone2

Hello guys, somebody can help me install Suhide on Zenfone 2? I've tried the guides around, everything went fine thru the install in temporary TWRP, but when I relock the bootloader I end up in a bootloop.
My steps:
1-Unlocked phone with the unlock.bat
2-Turn off Cellphone
3-Started in Bootloader
4-Flashed Temporary TWRP
5-Go into Recovery
6-Flashed Magisk, SuperSu for magisk (2.76), dropped command in terminal echo "SYSTEMLESS=true" > /data/.supersu, flashed SuperSu (2.78)
7-Reboot into Bootloader
8-Relock phone with restore.bat
Even if I just flash SuperSu for Magisk (2.76) and doesn't update to 2.78 my phone ends in Bootloop.
Are I missing something?
Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
so, I'm supposing that the fifth option in this tool is SuHide instead of PHH?
Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I was using Magisk+PHH, I want to use Suhide to test, because I used to use SuperSU.
I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.
Abex, thank you, I will try tomorrow when I arrive on my Job, there is my PC with all the stuff to do, I will post news if everything went fine or goes bad
abex181 said:
I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.
Click to expand...
Click to collapse
thanks. I was searching this for a long time.
is there a place where to find @shakalaca's contributions to Zenfone?
Abex, when I flash SuperSu 2.76 or 2.78-R1, even the version you've posted I got stuck into loading screen.
Hi all.
I am currently having the exact same issue with my Zenfone 2 ZE551ML. Things I have learned (Which may be very obvious to some)
The device cannot boot with the bootloader unlocked.
Locking the Bootloader with any kind of custom recovery installed causes the device to only boot into the bootloader. Recovery or stock ROM cannot be accessed.
The only way around this is to unlock the bootloader, flash the stock recovery and then relock the bootloader.
Steps I have taken:
1) Unlock the bootloader
2) Boot into the bootloader and flash latest TWRP recovery for ZF2 (twrp-3.0.2-0-Z00A.img)
3) Reboot into TWRP recovery
4) Flash the Xposed Uninstaller (latest version)
5) Flash the Magisk Uninstaller (latest version)
6) Flash Magisk-v6_repack_for_zf2_601.zip
7) Flash SuperSU-v2.76-magisk.zip
8) Enter TWRP Terminal, issue command - echo "SYSTEMLESS=true" > /data/.supersu
**Note at this point, I get no response from the terminal, just the next command line. I think I should be expecting one? And therefore something is failing at this step?**
9) Flash SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip
10) Flash xposed-v86.2-sdk23-topjohnwu.zip (I am lead to believe that this is the only version that won't trip Safetynet, even later versions like 86.5 do)
11) Flash suhide-0.53.zip
12) Reboot to Bootloader
13) Flash the stock recovery
14) Lock Bootloader and reboot
This causes a bootloop on the splashscreen (White on black, so bootloader is locked) and on one attempt, a notification before the splashscreen informing me the device failed verification. The only solution I have found for this is to re-unlock the bootloader, enter recovery (stock) and sideload UL-Z00A-WW-4.21.40.134-user.zip
Then reboot to bootloader, lock bootloader again and reboot. No data missing or anything, but the phone is not rooted.
I'm wondering if suhide or superSU require the bootloader to be unlocked permanently- in which case, we need a solution for that. Could this be the case?
Or is it that we need a superSU v2.76 fix for Zf2 version, much like the v2.78 graciously posted by abex?
Perhaps it makes sense to sideload the Stock Marshmallow ROM at some point via TWRP, BEFORE returning to stock recovery? But even then, I think flashing it before superSU v2.76 seems pointless, as there are issues there- and does flashing it after simply wipe out all the hard work?
@kemp7, @Alterius:
If, after flashing a zip, you are getting stuck on boot or find that you can only boot to recovery, you can try flashing the boot.img from UL-Z00A-WW-4.21.40.134-user.zip in fastboot. This should get rid of any modifications to the boot image made by the various systemless mods you may have flashed previously. Any files added to the filesystem will still be present, but there should be no hook to load any systemless scripts like su.d or magisk. If you were using a custom kernel, it will no longer be installed. Of course, if you reflash the MM update zip in its entirety, this will be included, though I thought I should mention this to save you some time.
Before flashing any zip, you should try to get a general idea of what it will modify. If you've been flashing many zips and getting errors, it's a good idea to go back to a clean slate before trying something new. In fact, every time you flash a recent SuperSU zip, the script actually restores the boot image to a backup that was made the first time you flashed a recent SuperSU zip. This behaviour may be desirable, or it may unwittingly uninstall a custom kernel....
I also have to reiterate that its probably a bad idea to mix Magisk-based systemless mods with ones based on SuperSU's su.d.
Regarding the zip of SuperSU v2.78-SR1 that I posted, I'm not sure if it will work if you re-lock your bootloader afterwards. I can only report what I've tested and I keep my phone unlocked. That being said, the ZF2 can definitely boot with an unlocked bootloader, modified recovery, root, kernel, etc. Note that for MM rom, you will need to flash a modified TWRP in order to boot in to android (3.0.2-M1).
In this thread, I've reported a working instance of SuperSU v2.78-SR1, systemless xposed v86.2, and suhide v0.53 on my ZF2 with unlocked bootloader and TWRP-3.0.2 installed. To get there, I've only just followed the instructions on the suhide thread, except with the zips replaced with the ones patched for our ZF2 that I posted in that thread.
If you are having trouble, go back to stock MM rom. You can do this by flashing the stock recovery.img from the 4.21 zip in fastboot, then ADB sideload the whole zip. I think you should be able to do this with unlocked bootloader. Reboot into android to make sure all your data is still there.
Then, you can flash TWRP 3.0.2 for MM roms using fastboot. Your bootloader will need to be unlocked for permanent custom recovery. You might be able to dothe following with temporary TWRP (fastboot boot TWRP.img), but I haven't tested this.
From there you can follow the instructions in the suhide thread: flash SuperSU v2.78-SR1, (optionally reboot first, there will be a couple boot cycles before android starts up), flash suhide v0.53, (optional reboot), optionally flash systemless xposed v86.2, wipe dalvik cache, reboot.
Abex, thank for all the support again!
I've downloaded all the modified files for zenfone 2 from your posts ( SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip and xposed-v86.2-sdk23-topjohnwu_repack_for_zf2.zip ), except the suhide installer (suhide-0.53.zip) that is the original file from suhide thread.
For Unlock & reLock Bootloader I was using one tool I found here on XDA that comes with two files (unlock.bat & restore.bat from this thread) but it makes my phone unbootable if I just unlock it if I remember correctly.
Theres any good and safe tool that do you recommend for just Unlock the bootloader so I can give I try?
Today I did a mess on my phone while trying to figure out the things, so I reflashed a RAW imagem from LL .196 and did the upgrade with the MM zip on Internal Card, then did a factory reset afterwards, so I'm basically "starting fresh" , so I believe that theres no trace from my old messy tries.

How do I root my phone (SuperSU)?

I read the post about it. I'm new to this, it just looked like a lot of jargon. From what I can tell though I can't just downloaded supersu then flash it in TWRP. I tried it, it doesn't work. Can anyone explain in layman's terms how to root my phone? I have the pixel XL. Any help would be much appreciated. Thanks.
Thats exactly what you can do. If your bootloader is unlocked and you have TWRP RC1 installed you simply flash SuperSU v2.79 SR3 and all is well.
As noted, you will need to unlock the bootloader before using TWRP to flash the SuperSU zip. At that point the standard warning is: DO NOT LOCK THE BOOTLOADER. Items 1 and 8 from the following have more information.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
alluringreality said:
As noted, you will need to unlock the bootloader before using TWRP to flash the SuperSU zip. At that point the standard warning is: DO NOT LOCK THE BOOTLOADER. Items 1 and 8 from the following have more information.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
I did this, and it didn't work. I downloaded the SuperSU app and it said there aren't any SuperSU binaries. I tried flashing multiple times.
BDogg718 said:
Thats exactly what you can do. If your bootloader is unlocked and you have TWRP RC1 installed you simply flash SuperSU v2.79 SR3 and all is well.
Click to expand...
Click to collapse
I did exactly this, and it didn't work.
The latest beta SuperSU zip is at:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
The latest stable SuperSU zip is at:
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you are using TWRP RC1, it should come up with a message when it starts. Sometimes TWRP RC1 doesn't start with the message, and if that happens, I'm not sure if it will install a zip without following the additional instructions from Dees_Troy. Personally I installed the SuperSU v2.79 SR3 zip this past weekend just by booting TWRP RC1, and for a second install I used TWRP Alpha 2. Assuming your Pixel XL indicates it's unlocked, my suggestion would be just to boot the TWRP Alpha 2 image, don't install the TWRP zip, and then install whichever of the above SuperSU zips you want to use.

Twrp and flashing a Rom

So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.

Can't root Oreo (Magisk) or flash TWRP

I just changed from Android Nougat to Oreo flashing the latest build from Google (8.1.0, OPM3.171019.013, Jan 2018).
I used Nexus Root Toolkit for that, including Wipe.
All is fine with that, but I want Root access, prefering Magisk.
For that I'd need TWRP, but I seem unable to flash it with NRT (doesnt' update, TWRP 3.0.0.2, version to old?).
Well, it boots into that TWRP but it doesn't stick.
I also tried to flash the Magisk.zip via NRT directly, but didnt't work either.
As it seems I need Root to flash TWRP (using TWRP Manager) but I apparently also need TWRP to flash Root?
Please help me out here, I now fear to make a mistake with "me trying stuff".
(Like using that temporary older TWRP and installing latest Magisk, if that works, hoping it sticks, installing TWRP after that via TWRP Offical App)
Forget NRT (Nexus Root Toolkit) and just manually flash the recovery...
Download the current version here: https://dl.twrp.me/bullhead/twrp-3.2.1-0-bullhead.img.html
Boot the phone to the bootloader by holding Volume down while booting, or using ADB while the phone is running "adb reboot-bootloader"
Flash recovery with Fastboot: "fastboot flash recovery twrp-3.2.1-0-bullhead.img"
Easy peasy.....
fronten said:
I just changed from Android Nougat to Oreo flashing the latest build from Google (8.1.0, OPM3.171019.013, Jan 2018).
I used Nexus Root Toolkit for that, including Wipe.
All is fine with that, but I want Root access, prefering Magisk.
For that I'd need TWRP, but I seem unable to flash it with NRT (doesnt' update, TWRP 3.0.0.2, version to old?).
Well, it boots into that TWRP but it doesn't stick.
I also tried to flash the Magisk.zip via NRT directly, but didnt't work either.
As it seems I need Root to flash TWRP (using TWRP Manager) but I apparently also need TWRP to flash Root?
Please help me out here, I now fear to make a mistake with "me trying stuff".
(Like using that temporary older TWRP and installing latest Magisk, if that works, hoping it sticks, installing TWRP after that via TWRP Offical App)
Click to expand...
Click to collapse
Adding onto the above comment, make sure to use Magisk 14.0 or newer on Android 8.1.
Sent from my Nexus 5X using Tapatalk
Thank you, that was really quick and also worked quickly.
Magisk root now also functions, I am happy so far.

How to upgrade O+5T to OxygenOS 5.1.0 when rooted with stock recovery?

Greetings. I received the OTA update (which I did not install!) on my OnePlus 5T today. I'm on OxygenOS 5.0.4 with magisk installed, phone is rooted, bootloader unlocked, stock recovery (no TWRP).
What's the right path to upgrade to 5.1.0?
I'm experienced with the command line and have no problems with it.
Based on my ideas, I think the path should be:
- Download full Oxygen OS 5.1.0 Full Zip
- Start TWRP using adb
Code:
fastboot boot
(which TWRP version?)
- Wipe dalvik and cache
- Flash the downloaded file
- Wipe dalvik and cache
- Flash magisk
That's it. Am I missing something? Do I need to reinstall magisk as specified as last step? Which TWRP version should I use (from the official website?)?
Thanks for your help :good:
Please go through the dedicated update thread that ive made for the update
https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
The thread has all the instructions and files needed to update. As far as twrp is concerned i recommend latest codeworkx or or bluspark recovery. The links are available on the thread.
Feel free to post on the thread if you have any further doubts.
Thanks @Funk Wizard , I read that thread (I linked it in my post) but it mentions "For Stock Non Rooted Users with Stock Recovery" and "For Rooted Users with TWRP Recovery" while in my case I'm rooted with STOCK recovery, which doesn't fit any of those 2 sentences. Which one should I follow?
As you are rooted you can flash the full zip from stock recovery that would remove root or you need follow and flash via twrp. If rooted stock recovery is no good TBH and i recommend staying on TWRP.
You can flash twrp from fastboot and then follow the instructions on the flashing post.
In case you dont need root anymore you can just flash the full zip from stock recovery. It will remove root and you will stay on stock recovery. In both the cases, use the full zip to flash via twrp or stock recovery.
No good? Please be more specific, why it's no good? From my understanding keeping stock recovery with magisk installed and bootloader unlocked allows me to pass all SafetyNet checks, which is very helpful if you don't want to deal with apps complaining that you are rooted. I can easily boot to TWRP as long as I can plug my phone into my computer by just using the fastboot command. The only downside I could see is if I brick my phone and have usb debugging disabled, I can't fastboot from adb.
Flashing TWRP would make me fail SafetyNet checks, which I'm not interested into.
After I flash the full zip, do I also need to flash the OTA update?
Thanks by the way, basically the only real "special" thing I need to do is install Magisk again after flashing.
Flashing twrp doesn't break safety net. So it's upto you if you want to stay on stock recovery with no additional benefits or on twrp.
Also, if have full time zip then you don't need to flash ota zip again.
That's good! I'll definitely flash twrp in that case.
@sshivampp Sorry to resurrect this thread, but looks like it's important. On TWRP website itself it's stated that installing TWRP would break dm-verity. What's the consequence of this? https://twrp.me/oneplus/oneplus5t.html

Categories

Resources