My oneplus 3 was rooted (oxygen 3.2.5 maybe) but I installed the update 3.2.6 today from phone by going into settings. When the phone got updated my root does not work anymore. Please help.
I forgot how I rooted my phone before but it was still on android 6 when I rooted.
When I reboot I still get the black screen saying the device can't be trusted because xxxxxxxxxx Is unlocked, dont remember what.
Usb debugging is on as well as oem unlocked ( these options are still showing unlocked when i went to settings but don't know if they are ACTUALLY unlocked.
Xposed luck patcher, etc not working
Root checker says root not installed properly
Used twrp before.
Also is there any way that I can re-root my phone again without data loss?
Its my first post ever in any form so dont know about posting much.
You can mail me too at [email protected].
Thanks
Try flashing Super su manually from Recovery
Flash latest SuperSU (I think it is 2.78) in twrp. Flash xposed module in twrp too
If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Download twrp
Boot to fastboot
fastboot boot sometwrp.img
Flash supersu from temporary twrp
Hw4ng3r said:
If you did the official update from Settings > System Updates, then you are most likely back to stock recovery as well. You're going to have to re flash twrp before you can flash root and xposed. You will not lose data by performing any of these steps as your bootloader is still unlocked.
Click to expand...
Click to collapse
If you had root and custom recovery (TWRP) then you couldn't have updated by this method as it wouldn't have worked. You need to reflash SuperSU in TWRP as others have stated.
Much simple: from recovery (hope you're having TWRP installed) flash latest SuperSU and Xposed zip file.
Then Wipe Cache/Dalvik, then reboot in System.
If you won't to lose root, you should consider a custom rom like FreedomOS, that provides SuperSU binary by itself (even Xposed, if I'm not wrong).
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.
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Shoruk3n said:
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Click to expand...
Click to collapse
1. If you switch roms, always do a clean install (wipe all partitions) . If you want to get rid off all the mods wipe system and flash the same rom + gapps + root. You won't loose data since you are only modifying the system partition.
2. Stock recovery by Oneplus is as if says stock, you littery can't do anything with it apart from upgrading your OOS, wiping cache partitions and doing a factory reset. I do recommend the TWRP provided by Bluspark since that seems to be the only one I tried without any issues whatsoever.
3. Magisk is the new root method in my opinion, it supports Magisk modules which simply are mods that can be installed and removed with a single click (reboot required tho). You can compare it to xposed but very limited when compared.
4. Boot.img is your kernel, never flash standalone img files apart from TWRP since the kernel modifies more the only the boot img. Always flash the full zip.
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
theburrus1 said:
I have the xt-1952-4 variant. When I first got this phone and tried the various methods to flash and install Magisk, it worked then. Since then for whatever reason, whether it be to fix a soft brick or restore a backup, and having flashed the most recent (March 2020) stock ROM for this phone, never I repeat never have I gotten Magisk to take right. I don't know if it's Magisk or the security updates from Google or Motorola but it's made flashing root nonexistent, even yet while my bootloader is unlocked. Every thread here or on any Google search to install Magisk or root and install TWRP seems obsolete now. Anyone else have this problem And how to perhaps fix it? Am I the only one with such a problem? Thanks.
Click to expand...
Click to collapse
It's only possible to install twrp if you also install a GSI. Twrp will not work on stock. Magisk is also incompatible with twrp, the two can never be installed together no matter what. This is a magisk problem. Magisk uses the recovery partition, so it can use mirrors to make changes (systemless root). Twrp also needs to occupy the same place, because twrp is a custom recovery. Because of this conflict, they can't coexist. Magisk needs you to boot into "recovery" to boot the normal OS with root, and twrp needs you to boot into recovery to operate normally. So it's one or the other.
Unless the developer of Magisk decides to use system root, all newer devices will continue to have this problem. I highly doubt that will change anytime soon. The foundation of Magisk is built on being systemless, and so are all the modules for it.
If you want to use magisk, install the app, and patch your boot.img with it as "recovery", then flash it with fastboot. You must always "reboot recovery" to keep root afterwards.