Related
So i was trying to flash hacker kernel
It bootlooped.
So i reflashed renegade and tried reflashing.
it rebooted
now everytime i try and flash anything it reboots
super su is missing.
I installed super su from play store
when i go to flash binaries it reboots.
I updated TWRP
still same thing.
If i flash anything it just boots back to recovery.
Any thoughts?
Flashed back to stock and rerooted.
Did the trick.
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
koop1955 said:
Would you consider editing the topic to add the word "solved" please? The might help give others direction.
So when you started out from stock, you used Odin to install TWRP, but then thought you could get rooted by installing SuperSu from the Play store, which did not work.
Proper steps are to install TWRP using Odin with SuperSU on your phone. After TWRP is installed, instead or rebooting completely, reboot to Recovery and flash SuperSU that way.
Is that about right, @phelony?
Click to expand...
Click to collapse
No I had previously been rooted fine and dandy. for some reason TWRP started just rebooting on any flash.
so is it not going into bootloop mode anymore? because i've been having this problem for the last 6 months. i thought i'd try again and still doing the same, it'll get to the setup at the beginning and then reboot back to twrp????
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.
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section, whereas experts there might be able to assist you.
Regards
Vatsal,
Forum Moderator.
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
ShaDisNX255 said:
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
Click to expand...
Click to collapse
Thank you for your help. I did all the clear instructions from the thread. I couldn't get the CF auto root to stick. Also couldn't find a surfboard for TWRP 2.8.7, they only have 2.8.0 on the TWRP site, or TWRP 3.0. Ultimately I've got my original factory stock lollipop back. I'm no longer rooted. I had rooted before through KingRoot. I tried again and it says that I'm out on a list for root for my phone. So my phone works again. I guess I should be happy with that.
If you want to root, you could try flashing cfautoroot with Odin.
audit13 said:
If you want to root, you could try flashing cfautoroot with Odin.
Click to expand...
Click to collapse
I did try to flash CF auto root with Odin after I flashed back to the stock ROM. But it didn't work. It stayed stuck on the T mobile screen for a very long time. So I just gave up trying to root again and stayed with the stock ROM without root. Thanks. Maybe I'll try again and see if it'll work next time.
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
audit13 said:
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
Click to expand...
Click to collapse
Will that root my device?
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
audit13 said:
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
Click to expand...
Click to collapse
OK. Thanks. Also, which version of TWRP? I can't seem to find a download for 2.8.7.0, only for 2.8.0.0 and 3.0 on the official TWRP site. Also where can I find SuperSu? Do I flash SuperSU with TWRP once TWRP is on phone? I read somewhere that the best version for TWRP is 2.8.7.0, but I can't find it anywhere.
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
audit13 said:
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Click to expand...
Click to collapse
OK. Thank you. I will get to this next time my friend is available with the computer.
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.
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!
You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk
Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!