Develop Bugs

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.

Simply cannot achieve root

Good evening all. I consider myself an advanced Android user but this one is just absolutely killing me and I know it's something easy. I simply cannot get root following these steps on Chainfire's thread
"- reflash stock boot.img
- fastboot boot /path/to/twrp.img
- TWRP install twrp.zip
- reboot into recovery
- TWRP install supersu.zip"
I have never attempted the version Chainfire released which is CF auto root, boot to root. Since I am interested in obtaining both TWRP and root I decided to go with chainfire's instructions using TWRP's boot image and TWRP zip install. I can fast boot boot the image , I can install TWRP from the zip just fine , I reboot into recovery then install SuperSU zip then reboot into the operating system and it says I have no root ....what am I doing wrong? This is killing me because I know I'm doing something wrong and it's really really easy. I can't really seem to find a good answer in the Q&A forum. Feeling defeated LOL. I would appreciate anybody's guidance

See you using 2.79 SR2?

bash_array said:
Good evening all. I consider myself an advanced Android user but this one is just absolutely killing me and I know it's something easy. I simply cannot get root following these steps on Chainfire's thread
"- reflash stock boot.img
- fastboot boot /path/to/twrp.img
- TWRP install twrp.zip
- reboot into recovery
- TWRP install supersu.zip"
I have never attempted the version Chainfire released which is CF auto root, boot to root. Since I am interested in obtaining both TWRP and root I decided to go with chainfire's instructions using TWRP's boot image and TWRP zip install. I can fast boot boot the image , I can install TWRP from the zip just fine , I reboot into recovery then install SuperSU zip then reboot into the operating system and it says I have no root ....what am I doing wrong? This is killing me because I know I'm doing something wrong and it's really really easy. I can't really seem to find a good answer in the Q&A forum. Feeling defeated LOL. I would appreciate anybody's guidance
Click to expand...
Click to collapse
You did fine until the last step. Go get yourself SU 2.79 SR2 and flash that in twrp RC1 and call it a night. I can think of at least 4 ways of achieving root but twrp RC2 + SU 2.79 SR2 is the latest method.

i think now you booted into the os you need to reboot into twrp then flash SU

quangtran1 said:
You did fine until the last step. Go get yourself SU 2.79 SR2 and flash that in twrp RC1 and call it a night. I can think of at least 4 ways of achieving root but twrp RC2 + SU 2.79 SR2 is the latest method.
Click to expand...
Click to collapse
I've been trying to flash SR4 this whole time... So flash SR2? I'll try it and report back. You guys rock.

bash_array said:
I've been trying to flash SR4 this whole time... So flash SR2? I'll try it and report back. You guys rock.
Click to expand...
Click to collapse
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using? If you use SR4 with TWRP RC1, you'd have to delete the fstab file. That's why you go with 2.79 SR2.

quangtran1 said:
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using?
Click to expand...
Click to collapse
RC1 of the latest TWRP. 3.0.0.2

That's why you couldn't install root.
If TWRP RC1 + SU 2.78 SR4, must delete fstab before flashing SU.
If insist on SU 2.78, then use TWRP Alpha2, not RC1.
If TWRP RC1 + 2.79 SR2, no need to delete fstab.

quangtran1 said:
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using? If you use SR4 with TWRP RC1, you'd have to delete the fstab file. That's why you go with 2.79 SR2.
Click to expand...
Click to collapse
OK everyone in here that helped me out are complete and total bad asses! 2.79 SR2 Version was the ticket. I'm rooted. Shoot guys thanks so much!!! I appreciate it alot

This is what I flashed. Works great. Hopefully this thread helps somebody else out

bash_array said:
OK everyone in here that helped me out are complete and total bad asses! 2.79 SR2 Version was the ticket. I'm rooted. Shoot guys thanks so much!!! I appreciate it alot
Click to expand...
Click to collapse
Awesome, another happy customer.

Updated TWRP, now system only boots back into TWRP

I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks

I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.

facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse

TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse

My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.

alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12

We're can I download v8?
Sent from my Pixel XL using Tapatalk

The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347

So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.

cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.

Slowclap

Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse

Updated guide for TWRP/SuperSU Installations?

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.

Pixel XL will not root

Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.

Flash the stock boot.img to both slots and reroot. Use SR5.

I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)

I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.

https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.

I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...

DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.

I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.