SuperSU 2.8.x issues - Nexus 6 General

I didn't see this posted here so FYI: As announced here, there are currently some issues with SuperSU 2.80 and 2.81 that are being worked on and Chainfire has recommended staying with SR3-SuperSU-v2.79-SR3-20170114223742.zip for now while he works the issues out.
If you have already flashed 2.80 or 2.81 and lost root it is safe to flash back to SR3-SuperSU-v2.79 using TWRP (according to the thread and it worked fine for me). Hopefully this prevents some from flashing a few different versions trying to get root working again.

You should switch to Magisk, more features and less issues

snowrelyt said:
You should switch to Magisk, more features and less issues
Click to expand...
Click to collapse
Interesting, I'll look through the treads. Thanks for the infos!

Switching from SuperSU to Magisk is pretty easy. I've done it on my N5, N6 & N10.
BACK UP FIRST. Did I need to say that...?
Unroot with Osmosis' Unsu.zip, make sure that you have the original boot image, which in case of doubt you can extract from your ROM and flash (or your preferred kernel - see edit below), then flash Magisk and install the Magisk Manager apk. Note: you must flash Magisk after the boot/kernel, as it does a similar unpack/tweak/repack/install to SuperSU's processing. If you flash the boot/kernel after, you'll lose root.
Just to add to the fun, there are two versions - the stable v12/Manager 4 and a project v13/Manager 5. My N5 & N6 work fine on v12. I couldn't get v12 to work on my N10, but v13 runs perfectly and all three devices pass Safetynet.
I guess you're here because you like tinkering. Magisk is well worth the fun...
Edit: All three devices are on Pure Nexus. The N10 has the stock kernel, and the others have ElementalX. You should be able to use your preferred kernel.
If you do decide to install Magisk, at first sight you may think you haven't achieved root - until you realise (as I did, duh) that you need to check Settings/Magisk Hide.
Once it's up and running, it works as well as SuperSU.
And why did I switch? Only possibly groundless worries about the change of ownership from Chainfire to a company.

I switched to Magisk because of the analytics fiasco, brought about because of inadequate communication from CCMT. As I noted in a now-deleted post, while the analytics may seem a trivial reason to switch, I believe the gatekeeper to the system root must be incorruptible to remain trustworthy. Had CCMT been honest about the analytics in the first place, I might not have switched.

snowrelyt said:
You should switch to Magisk, more features and less issues
Click to expand...
Click to collapse
I agree. That's what I did. I switched from SuperSu to Magisk and it's working fine on Stock 7.1.1.
---------- Post added at 08:53 PM ---------- Previous post was at 08:36 PM ----------
dahawthorne said:
Switching from SuperSU to Magisk is pretty easy.
Once it's up and running, it works as well as SuperSU.
And why did I switch? Only possibly groundless worries about the change of ownership from Chainfire to a company.
Click to expand...
Click to collapse
You are so on point.
I switched from SuperSu to Magisk. Was a little hesitant to do so at first because I've been used to using SuperSu and Magisk was unchartered territory for me. But I decided to make the change and I'm glad I did. Magisk is working very well on my Shamu running Stock 7.1.1. I've installed a few modules, including Viper4Android and wow, what a big difference in sound quality (although those front firing speakers are very good in and of themselves, Viper4Android does indeed make a difference).
All in all, I'm happy to have Magisk installed on my Nexus 6.
Btw, I wasn't too thrilled the way the whole thing went down with SuperSu and CCMT. Not really trusting of that app anymore. To each his own, but I'll stick with Magisk.

For some reason Magisk is gone from play store.

mal13 said:
For some reason Magisk is gone from play store.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=72508849&postcount=21

I moved to magisk, too, thanks for recommendation. I would not even know about magisk that I have not read about it the last days. It seems a much better alternative, I doubt that I will not go back to SuperSU at this situation with CCMT etc. I'm upset with the last supersu's updates, I see, they do not want to do anything that would solve problem as soon as possible. What's the phh's superuser (I guess it's better to stay on magisk for now.)? I have never tried it. [emoji106] [emoji482] [emoji122]
Forgot, use PureNexus, all stock. [emoji122]
Sent from my Nexus 6 using Tapatalk

nemanja066 said:
What's the phh's superuser?
Click to expand...
Click to collapse
It's another open source root solution. MagiskSU is based on phh's superuser which in turn is based on koush's superuser.

Related

Disadvantages of rooting?

Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
qwertyuiop89 said:
Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
Click to expand...
Click to collapse
-OTA are not possible when rooted. You have to flash back stock boot.img and recovery.img to accept an OTA.
-It does not interfere with Nexus Imprint (Fingerprint reader.)
-Does not affect speed or stability
-Warranty is not affected because you can flash stock imgs and relock bootloader.
You can take OTA's if you do the systemless-root. I believe you would have to flash the recovery back to stock, though.
I think you have to flash boot as well since it's modified.
the biggest disadvantage is your device become instantly awesome, so if you are used to being annoyed about the stock OS missing features this is hard to deal with
But honestly the best thing about owning a nexus is you can root and easily go back to stock if you change your mind. The flash images are also easily available for updates (even before the OTA is out). So play with it, and worst case you can always restore back to stock.
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
chaco81 said:
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
Click to expand...
Click to collapse
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
83097markcynt said:
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
Click to expand...
Click to collapse
i have been using systemless root since v 2.61... im using 2.66 now
and android pay didnt work, and even wont pass safetynet test
delete the /su/xbin folder and it passes safetynet and android pay works...
so yes, for me it sucks that i have delete that to make AP to work... which is why for now i am giving up AP since i dont feel comfortable deleting xbin and breaking stuff
Mine passes safetynet test and is just systemless with nothing deleted. No Android Pay in the UK to test it with though.
Not being awesome.
Not living in the exciting XDA fast lane!
Can I use Xposed with systemless root?
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
dimiboy said:
Can I use Xposed with systemless root?
Click to expand...
Click to collapse
Yes mate you can works perfectly well
Sent from my Nexus 6P using Tapatalk
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
lol this seems to happen when you root and install Xposed or pretty much modify anything. Usually I see a decrease in stability and battery life but an increase in performance, and you get to play with new features early.
I'm contemplating rooting just to use the new launcher.
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
You have a couple of things going on.
First root IS as safe as you let it be. If you haven't installed any root applications it should not be any more buggy than stock.
You have installed Xposed. You have not mentioned what modules you have.
I don't have any issues you describe but I don't have a lot of modules installed.
I am stock with Xposed and root.
None
Sent from my angler using XDA Labs

xposed

Can we flash xposed via twrp or flash fire ?
Do it. At your own risk.
If you do it please let us know the results and which version you flashed.
I was also wondering about Viper4Android. I could really use the boost and equalizer.
Can you either nandroid back or flash a stock image if things go south? Can you even flash zips in TWRP yet without issue? You're rolling a big pair if you can't do either.
Is there an xposed for Nougat? Rumor says no. Rumor confirmed.
douger1957 said:
Can you either nandroid back or flash a stock image if things go south? Can you even flash zips in TWRP yet without issue? You're rolling a big pair if you can't do either.
Is there an xposed for Nougat? Rumor says no.
Click to expand...
Click to collapse
What he said....
Surely doesn't seem to be time to try this yet! Too soon and there's no safety net if something goes wrong.
planetbeen said:
What he said....
Surely doesn't seem to be time to try this yet! Too soon and there's no safety net if something goes wrong.
Click to expand...
Click to collapse
To be honest, there's really not much benefit at all to rooting yet. Yet people spend hours upon hours of aggravation trying to do so, with many of them that shouldn't be anywhere near an ADB command.
It's the same story with every new phone. The "root commandos."
Xposed isn't working for Nougat I thought
http://androiding.how/xposed-android-nougat-7-0/
It's Working Now. Don't Use Material Xposed Installer. Use The official Xposed Installer APK which is 3.1.2 Currently. Otherwise None Of The Modules Will Work.
HALOSWORLD said:
It's Working Now. Don't Use Material Xposed Installer. Use The official Xposed Installer APK which is 3.1.2 Currently. Otherwise None Of The Modules Will Work.
Click to expand...
Click to collapse
What ROM r u using?
Do you think it might work on Tilde's ROM? it's a 7.0 ROM
I really dont want screw up, I would not know how to reverse it.
douger1957 said:
To be honest, there's really not much benefit at all to rooting yet. Yet people spend hours upon hours of aggravation trying to do so, with many of them that shouldn't be anywhere near an ADB command.
Click to expand...
Click to collapse
I was just thinking the same thing... i've almost always rooted and modified my phones.. but I think it was usually for a specific purpose or need..
the older phones I had were running touchwiz.. which i HATED to use.. so was so eager to get ROM with more of a stock android..
Or how I would love having some of the features of Cyanogenmod.. like "ScreenShot" or Reboot menu ... but with the V20.. it has screen shot built in beautifully..
I know it was also nice to be able to install titanium backup and be able to delete a lot of the stock bloatware .. but the V20 doesn't have much.. plus I can disable most of them...
I do wish I could find a rom that may run a little faster... I have noticed some Hiccups with this phone.. and 1 or 2 random reboots.. but honestly i'm sure if I went with custom software or modifed with Xposed.. i could see that more..
It would be interesting to see what some of the reasons why people on here have rooted the V20.
netgar said:
What ROM r u using?
Do you think it might work on Tilde's ROM? it's a 7.0 ROM
I really dont want screw up, I would not know how to reverse it.
Click to expand...
Click to collapse
Mega ROM On 7.0 Stock Kernel With SU. If You Have TWRP, Back Up Just In Case. Download Xposed Installer And In Settings There Is An Installation Option, Choose Manual (This Will Save Downloaded Files So You Can Flash Manually From SD) go To The Main Screen And You Can Get Both The Official framework And The Uninstaller. Consider Looking Up How To Unbrick just In Case
Jaws4God said:
I was just thinking the same thing... i've almost always rooted and modified my phones.. but I think it was usually for a specific purpose or need..
the older phones I had were running touchwiz.. which i HATED to use.. so was so eager to get ROM with more of a stock android..
Or how I would love having some of the features of Cyanogenmod.. like "ScreenShot" or Reboot menu ... but with the V20.. it has screen shot built in beautifully..
I know it was also nice to be able to install titanium backup and be able to delete a lot of the stock bloatware .. but the V20 doesn't have much.. plus I can disable most of them...
I do wish I could find a rom that may run a little faster... I have noticed some Hiccups with this phone.. and 1 or 2 random reboots.. but honestly i'm sure if I went with custom software or modifed with Xposed.. i could see that more..
It would be interesting to see what some of the reasons why people on here have rooted the V20.
Click to expand...
Click to collapse
I never did root my V20. I'm on the Note 8 now and can't see any benefit of rooting it, either.
I'm really fond of Android Pay. I'm pretty fond of my phone working as it should all day every day. To one degree or the other, you lose that with root. SystemUI tuner will do quite a bit of Xposed's work, and I'm not so annoyed with ads that I feel a need for Adaway.
HALOSWORLD said:
It's Working Now. Don't Use Material Xposed Installer. Use The official Xposed Installer APK which is 3.1.2 Currently. Otherwise None Of The Modules Will Work.
Click to expand...
Click to collapse
Would u be so kind and post the links where we could find xposed zip and apk, please.
netgar said:
Would u be so kind and post the links where we could find xposed zip and apk, please.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3034811
Dl the APK, sdk24 arm64 version of xposed, and the Uninstaller. Install the APK and allow the app to install xposed through recovery. It will begin install, prompt to reboot in recovery, obviously select okay. Then it's an automatic process. Initial boot up time takes a while so be patient. Everything should be good to go after that. Good luck!
BTW I'm on h918, stock 10q.
I have YouTube adblock, boot manager, xposed torch, and stay awake for now. I feel like a nerd being excited about xposed. This is making the v20 even better!
Lgv20user said:
https://forum.xda-developers.com/showthread.php?t=3034811
Dl the APK, sdk24 arm64 version of xposed, and the Uninstaller. Install the APK and allow the app to install xposed through recovery. It will begin install, prompt to reboot in recovery, obviously select okay. Then it's an automatic process. Initial boot up time takes a while so be patient. Everything should be good to go after that. Good luck!
BTW I'm on h918, stock 10q.
I have YouTube adblock, boot manager, xposed torch, and stay awake for now. I feel like a nerd being excited about xposed. This is making the v20 even better!
Click to expand...
Click to collapse
Thank you...
Lgv20user said:
https://forum.xda-developers.com/showthread.php?t=3034811
Dl the APK, sdk24 arm64 version of xposed, and the Uninstaller. Install the APK and allow the app to install xposed through recovery. It will begin install, prompt to reboot in recovery, obviously select okay. Then it's an automatic process. Initial boot up time takes a while so be patient. Everything should be good to go after that. Good luck!
BTW I'm on h918, stock 10q.
I have YouTube adblock, boot manager, xposed torch, and stay awake for now. I feel like a nerd being excited about xposed. This is making the v20 even better!
Click to expand...
Click to collapse
Did u install 88.1 version?
http://dl-xda.xposed.info/framework/sdk24/arm64/xposed-v88.1-sdk24-arm64.zip
netgar said:
Did u install 88.1 version?
http://dl-xda.xposed.info/framework/sdk24/arm64/xposed-v88.1-sdk24-arm64.zip
Click to expand...
Click to collapse
I installed the original version first. Once it was up and running, I flashed the new version.
Lgv20user said:
https://forum.xda-developers.com/showthread.php?t=3034811
Dl the APK, sdk24 arm64 version of xposed, and the Uninstaller. Install the APK and allow the app to install xposed through recovery. It will begin install, prompt to reboot in recovery, obviously select okay. Then it's an automatic process. Initial boot up time takes a while so be patient. Everything should be good to go after that. Good luck!
BTW I'm on h918, stock 10q.
I have YouTube adblock, boot manager, xposed torch, and stay awake for now. I feel like a nerd being excited about xposed. This is making the v20 even better!
Click to expand...
Click to collapse
Thank you for that I suck at explaining and most of the links I used were external so I can't post them
HALOSWORLD said:
Thank you for that I suck at explaining and most of the links I used were external so I can't post them
Click to expand...
Click to collapse
I'm just glad most, if not all, are able to use xposed on nougat. The little things in life! Even though its just a phone!
Lgv20user said:
I'm just glad most, if not all, are able to use xposed on nougat. The little things in life! Even though its just a phone!
Click to expand...
Click to collapse
Amen :angel:

Guide to root and rom

Hi. is there any basic step by step guides for getting f the latest also extended ROM on my stock oneplus 3t.
Use to do it may y years ago and have lost / forgot everything lol. Also wondered if possible is it able to be rooted and still have access to banking apps using that ROM.
Cheers and apologies in advance
Best guide I've found
https://www.xda-developers.com/unlock-twrp-and-root-the-oneplus-3/
Used this earlier this evening. Simplest guide I've found and works fine for op3t, even though it's written for op3. Also replaced supersu with magisk zip with no difficulties.
Thanks for that. I will look at it tomorrow and attempt it. Did you replace SuperSU during the rooting or after? Read a few ways to do it so just wondered. Is it true that magisk is the way to get android pay and back king aps to still function with root?
Cheers
luke.douthwaite said:
Thanks for that. I will look at it tomorrow and attempt it. Did you replace SuperSU during the rooting or after? Read a few ways to do it so just wondered. Is it true that magisk is the way to get android pay and back king aps to still function with root?
Cheers
Click to expand...
Click to collapse
Didn't flash SuperSU at all. Tried installing magisk at the same time as new rom (vertex - recommended!), but ended up having to uninstall then reinstall later. Magisk v12 wasn't passing safetynet for me, but the Beta v13 magisk seems to be doing the trick for now.

Help, newbie confused!

After 4 1/2 years I finally killed my M8 and am having a HTC 10 with Nougat delivered tomorrow. My M8 was stock rooted with xposed and that's what I would like to do to the 10. When I set up my M8, I unlocked via HTC dev, flashed TWRP, TWRP rooted the device and then I flashed xposed. I would like to do the same to my 10 but am unsure if it's possible or how to do it. I tried googling but a lot of the results were a year old and and I'm not sure that they still apply today. Do I still unlock via HTC dev or should I use sunshine? Will TWRP still install a version of Chainfire's SuperSiu or do I need to use Magisk to root? Is xposed still possible?
me_three said:
After 4 1/2 years I finally killed my M8 and am having a HTC 10 with Nougat delivered tomorrow. My M8 was stock rooted with xposed and that's what I would like to do to the 10. When I set up my M8, I unlocked via HTC dev, flashed TWRP, TWRP rooted the device and then I flashed xposed. I would like to do the same to my 10 but am unsure if it's possible or how to do it. I tried googling but a lot of the results were a year old and and I'm not sure that they still apply today. Do I still unlock via HTC dev or should I use sunshine? Will TWRP still install a version of Chainfire's SuperSiu or do I need to use Magisk to root? Is xposed still possible?
Click to expand...
Click to collapse
You can still unlock via HTC Dev. S-off via Sunshine is also possible and you can leave your bootloader locked, as well. You'll need to use the latest SuperSU, as well as the latest version of TWRP. Can't comment on Magisk versus Xposed because I don't use either one.
Xposed is not possible on Nougat. What were you using it for? I use Magisk for all the mods I used to use (adblocking, YouTube background playback, etc.). Magisk is pretty cool, and Magisk's SU replaces SuperSU for all intents and purposes that I'm aware of.
If you want / need S-OFF, you'll need to pay for Sunshine. If you don't, just unlock via HTCDev, run the latest RUU if necessary (a new update just came out today), install TWRP, boot up into your home screen, install Magisk Manager, use that to download Magisk root, and go about your merry way.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum, and I'm really loving being back on AOSP.
SilverZero said:
Xposed is not possible on Nougat. What were you using it for? I use Magisk for all the mods I used to use (adblocking, YouTube background playback, etc.). Magisk is pretty cool, and Magisk's SU replaces SuperSU for all intents and purposes that I'm aware of.
If you want / need S-OFF, you'll need to pay for Sunshine. If you don't, just unlock via HTCDev, run the latest RUU if necessary (a new update just came out today), install TWRP, boot up into your home screen, install Magisk Manager, use that to download Magisk root, and go about your merry way.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum, and I'm really loving being back on AOSP.
Click to expand...
Click to collapse
There is Xposed for Nougat, albeit recently and it's listed as unofficial.
https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
Magnum_Enforcer said:
There is Xposed for Nougat, albeit recently and it's listed as unofficial.
https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
Click to expand...
Click to collapse
Well how about that? I just skimmed but it looks like the original dev behind Xposed is leery of this implementation, but I don't understand all of that. I guess just the fact that it's possible will be encouraging for a lot of people.
Even so, I'm quite happy with Magisk.
I just jumped from stock (Bad Boyz) to Pure Fusion AOSP from the main HTC 10 forum said:
I'm using Lee's rom at the moment and have thought about the Pure Fusion one, but I keep seeing some issues with wifi and radio signal. Are you having any of these issues?
Click to expand...
Click to collapse
biker57 said:
I'm using Lee's rom at the moment and have thought about the Pure Fusion one, but I keep seeing some issues with wifi and radio signal. Are you having any of these issues?
Click to expand...
Click to collapse
None at all that I've noticed. I mainly use LTE but I switched to wifi for a few hours last night, no problems on my end.
Thank you all for your help, I'll hold out on magisk for a bit to see how the new xposed comes along.
me_three said:
Thank you all for your help, I'll hold out on magisk for a bit to see how the new xposed comes along.
Click to expand...
Click to collapse
I haven't tried it myself but be careful, several people have told me the Sprint HTC10 has more problems being unlocked than other US versions, especially when it comes to flashing the radio to use on different carriers. Specifically I've been told trying to flash the Verizon radio will not only fail but has the potential to permanently disable your radio.

Simple root method with SuperSU.

DISCLAIMER --- I know there are several threads with methods to root the Moto G5+, but I searched for almost 2 hours trying to find one that didn't require Magisk, didn't require another app, didn't require modified kernels or that didn't have several posts from people who were having issues. I finally gave up and went to another source. It was very simple, accomplished in 5 steps from TWRP (once unlocked of course), and mirrored the method used back on my old Moto G2. If this method is somewhere in these forums already I apologize, but searching did not turn it up for me.
I am not going to regurgitate the process since the site covers it well. I did use "twrp-3.2.1-1-potter_persist.img" so as to be able to backup the Persist partition but if that doesn't matter to you the standard TWRP Potter will work just fine. . Here is the link to rooting: https://technewswith.me/unlock-root-moto-g5/
Here is a link to the last version of SuperSU to be released. I already had it in my collection so didn't consider that the link I provided referred to an much older version. https://download.chainfire.eu/1220/S...1001224502.zip.
And once again, I would like to say that I have had absolutely no issues after following this procedure. If you prefer Magisk, that's fine. But this was the fastest and simplest way I found to root my phone.
TBH, I would STONGLY recommend against anyone else doing this from the tutorial linked... This is literally a tutorial from a Moto G2 with the 2 replaced with a 5. Since it is linking SuperSU 1.94 it shouldn't even work on Nougat (2.78 is the minimum I believe). This is a common rehash technique to generate clicks for sites of... ummm... let's just call it "less than exceptional" reputation.
This also has other issues, but they don't effect everyone... You can't hide that the bootloader is unlocked which effects Play Store certification, you can't hide root easily which effects LOTS of financial and gaming apps, and last but not least, ChainFire has left this project, or rather sold it, and it hasn't been updated in well over a year and won't be updated again (ie. it's an abandoned project).
That is why people are using Magisk, because SuperSU is dead, there is no real alternative since SuperUser was abandoned years ago, but besides that it works and works very well. Most people who have issues are not having an issue with Magisk, but with add-ons to it.
Oh, and by the way... SuperSU is still modifying your boot image (kernel) and system partition even though it says it is "systemless" since that is a misnomer.
pastorbob62 said:
DISCLAIMER --- I know there are several threads with methods to root the Moto G5+, but I searched for almost 2 hours trying to find one that didn't require Magisk, didn't require another app, didn't require modified kernels or that didn't have several posts from people who were having issues. I finally gave up and went to another source. It was very simple, accomplished in 5 steps from TWRP (once unlocked of course), and mirrored the method used back on my old Moto G2. If this method is somewhere in these forums already I apologize, but searching did not turn it up for me.
I am not going to regurgitate the process since the site covers it well. I did use "twrp-3.2.1-1-potter_persist.img" so as to be able to backup the Persist partition but if that doesn't matter to you the standard TWRP Potter will work just fine. . Here is the link to rooting: https://technewswith.me/unlock-root-moto-g5/
Click to expand...
Click to collapse
Hmmm. I still use the latest version of supersu to root my G5+, but I also flash the ElementalX kernel. Without the kernel, I just got bootloops.
pastorbob62 said:
DISCLAIMER --- I know there are several threads with methods to root the Moto G5+, but I searched for almost 2 hours trying to find one that didn't require Magisk, didn't require another app, didn't require modified kernels or that didn't have several posts from people who were having issues. I finally gave up and went to another source. It was very simple, accomplished in 5 steps from TWRP (once unlocked of course), and mirrored the method used back on my old Moto G2. If this method is somewhere in these forums already I apologize, but searching did not turn it up for me.
I am not going to regurgitate the process since the site covers it well. I did use "twrp-3.2.1-1-potter_persist.img" so as to be able to backup the Persist partition but if that doesn't matter to you the standard TWRP Potter will work just fine. . Here is the link to rooting: https://technewswith.me/unlock-root-moto-g5/
Click to expand...
Click to collapse
There is in fact a thread about rooting the Moto G5+ with SuperSU here on XDA in the Moto G5+ section: https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
Even this one is outdated like the one you posted, as explained above by @acejavelin is it even more.
Beside the fact that superSU has been sold to some obscure chinese company and isn't supported in any way the linked version is way to old, SuperSU SR5 2.79 is the last fully working build. Also that guide doesn't care about the encryption of the data partition of the Moto G5+ (huge difference to the Moto G2) and the need of something like a no-verity.zip or, better solution magisk which does that job.
I don't know why you think that magisk is a bad solution but it's the actual method (with a lot of features also mentioned above) and it's in active development.
You don't even need a custom kernel.
Because of a kernel bug in some Moto devices the Moto G5+ isn't able to mount images r/w and in combination with the F2FS formatted data partition the effect is you can't use modules with magisk, but root isn't affected.
That's a Moto bug, not a magisk bug.
But even for that there's a easy solution, just flash the F2FS loopback bug module https://forum.xda-developers.com/ap...icial-version-including-t3577875/post71554247 through TWRP and forget it. From now on everything is working well.
So the steps are:
-flash TWRP
-reformat data
-flash magisk 16
-flash F2FS loopback bug module
Easy enough. You're rooted systemless with a root solution which is actively supported.
I owned a Moto G2 too rooted with latest SuperSU and now I'm rooted with the above method on my Moto G5+ and have zero problems.
Sometimes the easiest looking solution isn't the easiest and also not the best.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
There is in fact a thread about rooting the Moto G5+ with SuperSU here on XDA in the Moto G5+ section: https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
Even this one is outdated like the one you posted, as explained above by @acejavelin is it even more.
Beside the fact that superSU has been sold to some obscure chinese company and isn't supported in any way the linked version is way to old, SuperSU SR5 2.79 is the last fully working build. Also that guide doesn't care about the encryption of the data partition of the Moto G5+ (huge difference to the Moto G2) and the need of something like a no-verity.zip or, better solution magisk which does that job.
I don't know why you think that magisk is a bad solution but it's the actual method (with a lot of features also mentioned above) and it's in active development.
You don't even need a custom kernel.
Because of a kernel bug in some Moto devices the Moto G5+ isn't able to mount images r/w and in combination with the F2FS formatted data partition the effect is you can't use modules with magisk, but root isn't affected.
That's a Moto bug, not a magisk bug.
But even for that there's a easy solution, just flash the F2FS loopback bug module https://forum.xda-developers.com/ap...icial-version-including-t3577875/post71554247 through TWRP and forget it. From now on everything is working well.
So the steps are:
-flash TWRP
-reformat data
-flash magisk 16
-flash F2FS loopback bug module
Easy enough. You're rooted systemless with a root solution which is actively supported.
I owned a Moto G2 too rooted with latest SuperSU and now I'm rooted with the above method on my Moto G5+ and have zero problems.
Sometimes the easiest looking solution isn't the easiest and also not the best.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I didn't say Magisk is a bad solution. It's just not my preferred method and it never has been. And actually you are incorrect. The latest version of SuperSU is 2.82 and I use it on both my tablet and my phones without any issues and have since it was released. My mistake was not sharing that info in my post since the link is to an old version. I don't care if it is supported or not - it works and that is all I need. Also I did not have to format my data to get root with the method I shared, nor did I have to install a custom kernel . And as far as being outdated, my 2010 Hyundai is outdated but it still serves my needs, is paid for and gets great mileage so I don't need a different car with a lot of bells and whistles I will never use. The same logic applies for me here. Also the link you provided calls for a modified kernel, a modified TWRP, and a WIFI fix so it is totally different than the method I shared.
If my post is not useful to you, then don't use it. But I thought there might be others who would be interested in the method since it is MUCH simpler with fewer steps and works. The "best" solution is subjective and depends on the users needs and desires. What is "best" for you may not be 'best" for somebody else. FYI - I too am having "zero" problems.
pastorbob62 said:
I didn't say Magisk is a bad solution. It's just not my preferred method and it never has been. And actually you are incorrect. The latest version of SuperSU is 2.82 and I use it on both my tablet and my phones without any issues and have since it was released. My mistake was not sharing that info in my post since the link is to an old version. I don't care if it is supported or not - it works and that is all I need. Also I did not have to format my data to get root with the method I shared, nor did I have to install a custom kernel . And as far as being outdated, my 2010 Hyundai is outdated but it still serves my needs, is paid for and gets great mileage so I don't need a different car with a lot of bells and whistles I will never use. The same logic applies for me here. Also the link you provided calls for a modified kernel, a modified TWRP, and a WIFI fix so it is totally different than the method I shared.
If my post is not useful to you, then don't use it. But I thought there might be others who would be interested in the method since it is MUCH simpler with fewer steps and works. The "best" solution is subjective and depends on the users needs and desires. What is "best" for you may not be 'best" for somebody else. FYI - I too am having "zero" problems.
Click to expand...
Click to collapse
You're right, the last SuperSU version is 2.82 and the latest beta is 2.82 SR5, I apologize for that.
As you wrote the problem is the outdated version of SuperSU in the link you posted.
For sure anyone is free to use SuperSU, it's still a working solution for a lot of devices. I just wanted to explain that there is no more development or support and most probably never will be again, so for future OS it may not work.
Also I wanted to make clear that you don't need a custom kernel or any special zips, as mentioned in the also outdated thread about rooting with SuperSU here on XDA.
Imo, a really good guide is this one:
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post76810574
As posted above, you're good to go with magisk and the loopback bug module and I don't see where this way is more complicated in any way than the one you posted.
Both ways need a custom recovery and for just rooting a flashable zip, magisk or SuperSU. The loopback bug module is only needed if you want to use magisk modules.
I mentioned encryption and the loopback bug as it isn't present in the guide you posted but both things may cause problems for some users, for example you can't backup/restore an encrypted data partition.
But no harm, the guide you posted is usable when it links to an actual version of superSU.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You're right, the last SuperSU version is 2.82 and the latest beta is 2.82 SR5, I apologize for that.
As you wrote the problem is the outdated version of SuperSU in the link you posted.
For sure anyone is free to use SuperSU, it's still a working solution for a lot of devices. I just wanted to explain that there is no more development or support and most probably never will be again, so for future OS it may not work.
Also I wanted to make clear that you don't need a custom kernel or any special zips, as mentioned in the also outdated thread about rooting with SuperSU here on XDA.
Imo, a really good guide is this one:
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post76810574
As posted above, you're good to go with magisk and the loopback bug module and I don't see where this way is more complicated in any way than the one you posted.
Both ways need a custom recovery and for just rooting a flashable zip, magisk or SuperSU. The loopback bug module is only needed if you want to use magisk modules.
I mentioned encryption and the loopback bug as it isn't present in the guide you posted but both things may cause problems for some users, for example you can't backup/restore an encrypted data partition.
But no harm, the guide you posted is usable when it links to an actual version of superSU.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
All good points! I will see if I can find a link with the later version of SuperSU If not, I will put a link to my Google Drive and make it available there. :good:

Categories

Resources