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.
Related
So I wont say I tried everything but have been reading and trying solutions and they havent worked for me. Maybe someone can point me in a different right direction. So far I clean installed 3.2.8(twice btw), I'm fastbooting into twrp 3.0.2-1, flashed supersu 2.78 SR4 and flashed xposed framework v87.
Sometimes xposed framework v87 flashes in twrp and when I open xposed installer it says xposed framework is not installed. I attempt to then unintstall and try again and sometimes it fails in twrp with this message "cp: cant create '/system/xposed.prop':Read-only file system". I attached a screenshot. I'm also running xposed installer 3.1.1, also tried 3.0.1 by dvdandroid. Any suggestions?
Have you tried Magisk and Systemless Xposed?
mznk said:
Have you tried Magisk and Systemless Xposed?
Click to expand...
Click to collapse
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
SysAdmNj said:
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
Click to expand...
Click to collapse
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
Thanks it all worked and went green except when I tried to download the systeless arm64 sdk23 from within magisk manager. I ended using a test1 version and it went through. Now I wasnt even planning on using magisk but how are you using magisk? When I used it before it was for android pay but I thought that all broke.
Installing xposed breaks SafetyNet anyways and I have no use of Android pay or Pokemon Go etc.
But, with magisk I can install and mod system files without making changes in the system partition like dpi, Viper, SystemUI mods etc. I really like it for the ease of that.
I have installed Xposed on 3.2.8 with a success from the beginning. Steps I've taken:
1. Dirty flashing full zip OOS 3.2.8.
2. Flashing systemless SuperSU from Chainfire (you have to:
Code:
echo SYSTEMLESS=true >> /data/.supersu
for systemless).
3. Flashing Xposed v87-test version, which now disappeared from dl-xda.xposed.info/framework/sdk23/arm64/
4. Flashing ElementalX 0.28.
I was upgrading from 3.2.6.
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
OxygenOS 3.2.7 with v87.1 Magisk version installed. Got stuck at boot animation when dirty flashing to oos 3.2.8. Any ideas? Is there compatibility problem with xposed modules?
I would use a newer recovery, twrp-3.0.2-23-oneplus3 is the latest and I've had zero issues with it. I uploaded it to drive vs searching for it. Next, as stated, install Xposed via the app, version 3.0.1 by dvdandroid is what I'm using and after selecting arm64 api23 , granting root, it installs, reboot and done.
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
After several failed attempts to root my Galaxy S6 Edge+ (SM-G928T) with the latest firmware update to 6.0.1, G928TUVU4DPK6, this is what I had to do to get a working root solution. At no time did I ever have a problem installing TWRP with Odin. Ive been using Odin 3.12.3 but I had the same issues with Odin 3.10.7.
I started with a clean slate and performed a fresh install of the stock firmware which I downloaded from here:
http://forum.xda-developers.com/tmo...al/sm-g928t-stock-odin-g928tuvu4dpk6-t3516310
After flashing the stock firmware with Odin 3.12.3 I did the basic setup on my device to make sure I could boot and everything was working. Next, I shut down my device and booted to Download Mode by using the key combination of Volume Down + Home + Power. Once booted into Download Mode I used Odin again to flash TWRP 3.0.2-0, which is available here:
https://dl.twrp.me/zenltetmo/
After the flash was complete I booted to recovery using Volume Up + Home + Power. When TWRP starts it will ask you if you want to swipe to allow system modification. If you swipe to allow system modifications you will trigger DM-Verity and you will not be able to boot normally unless you flash a custom kernel that has DM-Verity disabled in the fstab or you can flash the no-verity-opt-encrypt.zip that I dowloaded from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
The newest version available is 5.0
So, I swiped to allow system modifications. Next, I transferred the no-verity-opt-encrypt.zip from my PC to my device and installed the zip in TWRP. Once this was completed, I transferred my root zip from my PC to my device. I used the PHH Superuser to root my device which is available here:
https://superuser.phh.me/superuser.zip
I installed the root zip in TWRP, wiped cache/dalvik cache and then selected Reboot System. I didnt know if I would be able to boot or not. I could never get past the T-Mobile boot animation each time I attempted to root this damn thing but low and behold everything went as planned and I was fully booted up and running. I went through the setup wizard and everything was working as it should.
I am using PHH Superuser instead of Chainfires SuperSU. Its a personal choice for me as I have been using PHH Superuser since the hand off of SuperSU to a new company, CCMT, LLC.
Once I was finally able to boot normally I downloaded PHH's app in the Play Store from here:
https://play.google.com/store/apps/details?id=me.phh.superuser
This is just my experience of what I had to do to get root working on my S6 Edge+. All of my root apps are working as designed. I cant remember the last time I didnt have a rooted device and it was starting to bother me. I was having root withdrawals. If anyone decides to upgrade to the latest firmware from T-Mobile and wants a working root solution, here is what worked for me. I have not tried to use Chainfires SuperSU again. If you dont want to use PHH Superuser and wanted to use SuperSU instead, try to insert SuperSU in place of PHH Superuser and see what happens. Do this at your own risk because I have not tested it with this solution that I found. Good luck. Happy Rooting!!
fast69mopar said:
Has anyone upgraded their firmware to PK6 and attempted to root? I don't have any issues flashing TWRP with Odin. None whatsoever. When I flash a SuperSU zip or a PHH Superuser zip, I cannot get past the T-Mobile boot animation. It freezes every time. Once this happens I cannot boot to recovery. I can only boot to Download Mode. Hell, I can't even power down my device after I flash a root zip. Just curios if anyone has dealt with this issue. I have attempted to flash SuperSu zips starting with the 2.71 Beta up to the 2.78 SR5 with zero luck. I've also tried with PHH Superuser and I get the same results. Can anyone shed and light on the subject?
Sent from my SM-G928T using XDA-Developers mobile app
Click to expand...
Click to collapse
Here is the one I used. works great
Venal_System said:
Here is the one I used. works great
Click to expand...
Click to collapse
I tried that version too and I ended up with the same problem each time. I figured it out last night though. Im going to update my OP with the steps I had to take to get it working and that way if anyone upgrades to the latest PK6 firmware for their G928T and has this problem my thread is available with a solution.
It's been awhile since I've used a custom recovery. Since I've had this phone I've used systemless root and flashfire to install OTA's and that has worked fairly well. Recently my phone bootlooped and google sent me a new one.
I just unlocked it, installed TWRP and Magisk, but was wondering what the best way to upgrade the phone would be.
1I've heard flashfire works with Magisk, but I never had much luck with custom recovery's and updating with flashfire.
If flashfire doesn't work, what would be the best way to update?
When 7.1.2 is released, could I just flash the system, radios, etc. from fastboot and then reflash magisk from TWRP and be upgraded?
I had to uninstall magisk, reboot, download the ota via the system menu and install it, then re-flash twrp, then boot recovery and flash magisk, then re-add my modules and re-enable systemless adblock
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
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Very strange, but it just worked, after the 20th time of doing the same thing. Who knows why
Hey, my issue with Magisk is a bit different. I've upgraded my Pixel 2 XL every month and flashed Magisk afterwords. What I keep running into for the past couple of months is that after I'm all done, I will get a notification that there's an update to Magisk, but it's the same version I already have. I've tried different versions from 16.7 to the beta 17.3 and I would always seem to lose root after a while and be prompted to download the update to Magisk. Any help is greatly appreciated! Thanks in advance.
I am having the same issue with magisk after updating to nov update. Did the flashall then booted twrp and flash magisk Not sure why
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Run the Magisk uninstaller first
run 17.1 or the uninstaller. i've had better luck with 17.1
I guess the issue is linked to the Active Edge Module!
Download "uninmod_magisk", install it via TWRP, execute it via Terminal in TWRP, delete the Active Edge Module.
Now you can boot and reinstall that module.