Database Users

PHH's Root Disappeared

Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.

apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me

SuperSU randomly losing root?

I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode

I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.

I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?

Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.

Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.

Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.

On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su

Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD

No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...

G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)

I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.

highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?

sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here

Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.

Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.

So, according to you... Which is better? SuperSU or Magisk?

SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.

Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.

[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?

Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.

Magisk on Stock (rooted) Nougat?

Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?

Flapjack said:
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Click to expand...
Click to collapse
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk

Choose an username... said:
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Click to expand...
Click to collapse
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.

So install just boot.img from twrp and flash magisk.

Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
Either do what WesTD says or find a SuperSU uninstaller zip (i think there's one around), or wipe system and reflash the ROM

Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5

marcdw said:
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Click to expand...
Click to collapse
Good stuff. Thank you!

I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.

AnonVendetta said:
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
Click to expand...
Click to collapse
Could you say which problems you had with Magisk?
If you had f2fs then of course. But usually Magisk works as it should and has the module system which is very useful too.

Rooting OREO (41.3.A.2.24)

I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?

Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?

deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!

Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148

D802 any root methods are not working!

hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance

1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.

zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.

so any advice anout that problem?

you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable

Screenshot https://i.imgur.com/6IcIvJx.jpg

slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9

zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?

Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.

zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro