Related
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.
I was following the guide at:
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I started with a Pixel XL 7.2, unlocked, magisk, etc. I uninstalled magisk, updated all OTA updates, and then began the thread above.
I followed 6 - Extract boot.img from Fcatory Image and fastboot boot.img
The continued with 7 - Root with Magisk
booted to twrp, flashed twrp, no issues.
Rebooted to recovery, flashed elementalX kernel 3.04, and added magisk v16.3
No errors
Rebooted phone, and upon boot, got a message:
"there's an internal problem with your device"
From what I've read, that is not really an issue and has something to do with some things not matching, so, an update to magisk in the future will resolve it. So no big deal.
However, I don't see magisk manager, and have no root.
I reboot back to recovery, uninstall magisk manager, and reboot phone.
Still get the internal problem message, but no big deal.
I reboot back to recovery, and try flashing magisk again.
Still no manager, still no root (from root checker).
I try installing the magisk manager app directly, but, the APK cannot install, and just gives a generic error message of "app not installed".
Reboot to recovery, uninstall magisk again, wipe cache. Reboot, still same internal problem message.
Try to flash magisk 16.0 instead, repeat the above, and still no root, and can't install APK.
So, just kind of stuck at this point. Phone tells me that elementalx installed without an issue though, so, just seems like magisk is the last step. Any help is greatly appreciated. Thank you.
The message you get upon boot is from the kernel, nothing to do with magisk. not that it matters, it doesnt affect anything.
According to EX thread and EX's official websites "How to install" guide, you are supposed to install magisk first. Thats how i do it.
what you need to do is......
Reflash the stock factory boot img and let it boot.
Reboot to bootloader flash or boot twrp, and install magisk.
Reboot let it boot all the way.
Then reboot to bootloader flash/boot twrp and install EX.
Reboot.
---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------
Double post, sorry, butt.......
https://elementalx.org/how-to-install/
Read part one step three.
"3. Root your device (optional)
If you would like root access to your device, install SuperSU or Magisk. This should be done before installing ElementalX. Other root methods are NOT recommended. Root access will give you full control over your device and allow you to change kernel settings and tweak your device. To install SuperSU or Magisk, download to your device, reboot to recovery and install the zip you downloaded. Make sure you reboot into your system after the installation process completes. Ensure that root is correctly installed and working.
At this step, I usually make a backup of the stock rooted kernel. Now that you are rooted, you can do this very easily in EX Kernel Manager by selecting Tools->Kernel backup. This will save the boot.img."
Thank you for the help, will try it when I get a chance. The guide that I was following said for elementalx, flash kernel first. For exnoshadez, to do magisk first, for other kernels, do kernel first. I had read that some kernels need to go first, while others magisk needed to go first, and since that guide was specifically oreo, I thought kernel was first. But, thanks! Will try going back to factory boot image and progressing through.
So, I flashed back to stock boot.img, booted twrp, flashed twrp, and flashed magisk. But, Magisk still did not show up. I tried installing the magisk manager apk, but still get "App not installed" when trying that. At least the "there's an internal problem with your device" message went away.
Any other ideas on what to check when flashing, or why it's not "taking"?
Thanks again for the help.
Found out the problem:
Had to do:
adb uninstall com.topjohnwu.magisk
The key here was that I was upgrading from 7.2 to 8.1, and in the uninstall of magisk, I guess it left some remnant behind which prevented it from installing the new version.
The way I discovered this was trying to use adb to install the magisk manager apk, and that gave me the error:
adb: failed to install MagiskManager-v5.7.0.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match the previously installed version; ignoring!]
Then, I simply uninstalled it, then flashed using twrp again, and it worked fine.
so i installed magisk in a custom rom named Groovy in my Asus zenphone 2 so i installed it without any error un twrp after i rebooted but it takes me back to twrp what can i do i tried magisk unistaller but it says no root enabled something like that.
You need to install the verified boot signer to fix the TWRP boot loop
Hi All 1st new here and just joined.
What I need is some help and advice, looked through but cant really find anything to help me.
I have a Samsung Galaxy S20 which was rooted by a well known online rooting place.
What I need is, I want to update the software but this has been disabled and it is not even showing in the settings. When I search its there but cant do anything with it. The root is oem firmware not custom it has mgdsk on not sure about twrp. Root checker pro and is all green confirming root.
What I want to be able to do is update the software as still on 10 and some of my apps are saying i need to update. I cant do this as the Software Update is Disabled and not actually in the list. Any advice on how and what I can do to update the phone? Or put back on the Software Update as I have looked all day and found nothing to help me.
Rooted Galaxy S20, wanting to update firmware, mgdsk, not sure how to get Software Update back.
TY
I have seen multiple post about people loosing root access after the OTA.. I have jotted down the below the instructions on how to retain root access after OTA updates.
Follow this steps... 1.Magisk Manager → Uninstall → Restore Images). Do not reboot or you will have Magisk uninstalled.
2. Now Update the system and let it install completely. Do not press the reboot button.
3. Now install TWRP A/B Retention Script from Magisk Manger. This module is available on Magisk (if you have twrp as custom recovery) Skip this if you do not have TWRP installed
4. Go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk.
5.Once Magisk installation is done, press the reboot button in Magisk Manager.
Your phone may get into bootloop once, if that happens just restart the phone again.
Voila now you have your OnePlus updated and You also have Magisk installed with root access
WILL THIS WORK PLEASE? EVEN TOUGH I HAVE SOFTWARE UPDATE DISABLED?
Dj-Clubber-UK said:
I have seen multiple post about people loosing root access after the OTA.. I have jotted down the below the instructions on how to retain root access after OTA updates.
Follow this steps... 1.Magisk Manager → Uninstall → Restore Images). Do not reboot or you will have Magisk uninstalled.
2. Now Update the system and let it install completely. Do not press the reboot button.
3. Now install TWRP A/B Retention Script from Magisk Manger. This module is available on Magisk (if you have twrp as custom recovery) Skip this if you do not have TWRP installed
4. Go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk.
5.Once Magisk installation is done, press the reboot button in Magisk Manager.
Your phone may get into bootloop once, if that happens just restart the phone again.
Voila now you have your OnePlus updated and You also have Magisk installed with root access
WILL THIS WORK PLEASE? EVEN TOUGH I HAVE SOFTWARE UPDATE DISABLED?
Click to expand...
Click to collapse
Does the S20 have a/b partitions?
Found the answer - https://www.androidpolice.com/2020/...ung-phones-support-androids-seamless-updates/
No it doesn't
If so then yes it would work if you could download and install updates.
If the phone was rooted with a patched Odin install then you most likely have to wait for the newer version patched and update the same way as last time.
Sent from my ONEPLUS A6010 using Tapatalk
Got the notice there was an OTA. As per instructions I tried uninstalling magisk and restore images. Got a toast notification saying no backups found.
Tried a complete removal of magisk, now stuck at the Bootloader unlocked screen.
Tried flashing the patched boot.img in fast boot and rebooting. Now I'm stuck on the boot animation.
Done with root on this phone, not worth the headaches. (TiBU was the only thing I use it for these days) Get me back to no magisk without loosing data.
[edit]
Ended up having to wipe litterly everything via recovery then it finally booted. :/
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Snaxe123 said:
The patched image you're flashing won't work because you updated to 10.0.14. When updating, you're not supposed to uninstall Magisk, just disable the modules you have downloaded in the "Modules" section.
You need the updated root boot.img. I'll try to upload it later.
Click to expand...
Click to collapse
Thanks. At that point I hadn't installed the OTA update yet. I had just prepped by going into Magisk manager and (mistakenly) hit completely remove magisk. Which it did, then rebooted but left me hanging at the unlocked bootloader warning.
I tried flashing the patched boot.img from fastboot, and reflashing magisk from inside of the temporary twrp, but after a reboot I was left with the boot animation that never went away.
After I wiped it and got back in, I let it download the latest OTA and installed it.
So currently I'm at 10.0.14 now, but without root.