I didn't found here something for rooting Nexus 5x with Oreo 8.1 Security Patch February 2018 just with SuperSU and Magisk isn't always an option(for me).
Required: unlocked bootloader, TWRP 3.2.1-0 installed
Go to Playstore and install Chainfires SuperSU v2.82. Download the attached file and put it to your internal storage. Reboot to TWRP and install SR5-SuperSU-v2.82-SR5-20171001224502.zip. Reboot to system. After two reboots you will be back in system and SuperSU is working. If you don't install the app first through Playstore, you won't find any SuperSU in your app list. I don't know why, but this way worked for me and i tried it several times, because i didn' want to have Magisk on this phone. Viper4android is also working without any problems. Hope this helps anybody with the same problem.
Coredown said:
I didn't found here something for rooting Nexus 5x with Oreo 8.1 Security Patch February 2018 just with SuperSU and Magisk isn't always an option(for me).
Required: unlocked bootloader, TWRP 3.2.1-0 installed
Go to Playstore and install Chainfires SuperSU v2.82. Download the attached file and put it to your internal storage. Reboot to TWRP and install SR5-SuperSU-v2.82-SR5-20171001224502.zip. Reboot to system. After two reboots you will be back in system and SuperSU is working. If you don't install the app first through Playstore, you won't find any SuperSU in your app list. I don't know why, but this way worked for me and i tried it several times, because i didn' want to have Magisk on this phone. Viper4android is also working without any problems. Hope this helps anybody with the same problem.
Click to expand...
Click to collapse
Thank you for your post.
I've tried several times to root the Nexus 5x only flashing the SuperSU by fastboot but I never rooted the phone.
I followed your suggestions and now it works.
Also the version of SuperSu to flash was different. I kept flashing an S3 while the one published by you was an S5.
Thank you.
bluemarine57 said:
Thank you for your post.
I've tried several times to root the Nexus 5x only flashing the SuperSU by fastboot but I never rooted the phone.
I followed your suggestions and now it works.
Also the version of SuperSu to flash was different. I kept flashing an S3 while the one published by you was an S5.
Thank you.
Click to expand...
Click to collapse
Your very welcome. Nice to see that I could help you
It works like a charm, thanks so much!!
I failed in the past because I installed SR5-SuperSU-v2.82-SR5-20171001224502.zip first, then install SuperSU app. SuperSU app then needs to update binary, then the phone stuck.
Funciono en mi Moto G4 con AOSP Extended 5.6/Oreo 8.1, no crei que me fuera a funcionar y probe con el root checker
mod edit - translation added
I run on my Moto G4 with AOSP Extended 5.6 / Oreo 8.1, I did not think it would work and probe with the root checker
Excellent! Thank you!
Related
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
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
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.
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
mundodroid said:
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
Click to expand...
Click to collapse
I aslo had that problem on two occasions.
The first was with the Stock ROM 7.0 and the resolution was simply reboot and wait with an app that needed SuperUser to run. After a while the SuperUser request flashed up. In my case I used Titanium BackUp as the app.
In the second instance I had loaded the Lineage 15 (Android Oreo ROM) and had to install Magisk to get the root. I may have been using the wrong SuperUser though.
Some ROM's, however have a setting that you can change to get the root if you want to.
mundodroid said:
I did all the installation procedures the twrp was installed plus the superSu does the installed all right, when I look at the device does not have root
I wear
Stock ROM 7.0
TWRP 3.1.1
Click to expand...
Click to collapse
Why don't you try Magisk instead of SuperSU. I also had a lot of problems with SuperSU like App Quarantine, Titanium backup not detecting root, or taking a long time for SuperSU prompt. I have no problems with Magisk.
Not sure it will help you because in my case, SuperSU did appear in the app drawer.
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