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:
Related
The ROMs seem to have bugs so I intend to just use a custom kernel and remove bloat apps. Maybe when I find a ROM updated enough so there aren't any bugs, then I will shift to it.
Also, the updating process for ROMs in general seems very time consuming and frustrating. Plus you have to backup everything before an update to the ROM. This is why I wish to just stay with the stock, until I find something that is less time consuming.
Also - Is there a guide/FAQ for the whole root/rom/kernel/bootloader thing for noobs? If so can you please link it to me?
Thank you.
imda1 said:
The ROMs seem to have bugs so I intend to just use a custom kernel and remove bloat apps. Maybe when I find a ROM updated enough so there aren't any bugs, then I will shift to it.
Also, the updating process for ROMs in general seems very time consuming and frustrating. Plus you have to backup everything before an update to the ROM. This is why I wish to just stay with the stock, until I find something that is less time consuming.
Also - Is there a guide/FAQ for the whole root/rom/kernel/bootloader thing for noobs? If so can you please link it to me?
Thank you.
Click to expand...
Click to collapse
Well, I'll try to clarify some things here. I'm using the Lineage OS Unofficial ROM for this phone. I can't speak for all the other ROMs, but Lineage has been very stable, supports the fingerprint gestures, and if all goes well then we'll see official Lineage OS builds before long. Same thing happened happens with my Moto G3. As for bloat, Lineage doesn't really come with any besides their forked AOSP apps, some of which are replaced by the official Google versions depending on which Open GApps version you choose.
As for updating, Lineage is still unofficial so that means manual flashing, but honestly you can stay on a build for quite some time, there's not a lot of major changes from one nightly to another. Also you can dirty flash updates meaning you don't need to wipe everything, just flash the updates and clear the cache as TWRP suggests after flashing. Once it gets an official build you can update in the System Settings.
A quick look at the Guides forum for this phone would have shown you this collection of guides:
https://forum.xda-developers.com/g5-plus/how-to/howto-ultimate-g5-plus-guide-unlocking-t3593531
Please try to search the forum and look at top and stickied posts in the future. I hope this helped, custom ROMs can do a lot of great things.
Edit: I will say however there's nothing wrong with staying on stock if you choose. I happen to love ROMs but it's personal preference.
That thread and others in the guides section have a ton of useful support whether you're an avid ROM enthusiast or just trying to improve on stock.
To answer your question about updates when staying on stock but using a custom kernel, you won't be able to get them correctly because your /boot (kernel) and /recovery (TWRP) partitions aren't stock anymore which it'll detect and fail.
When updates come you can either return to stock using the tools/guides here, take the OTA then reinstall TWRP and custom kernel (which does take some work to get back where you were), or hopefully a benevolent Dev here will create a flashable zip from the update you can just do in TWRP, which is often the case but we'll have to wait & see. In either case it's still worth it imo for the control you get over the system compared to remaining fully stock.
Can someone make flashable zip of the recent update that fixes the 911 bug?
Hi,
Good question! :angel:
I explain it for another device (Moto G4):
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
Simple explanation:
- You can update with OTAs if you never modify the SYSTEM partition.
- You can install the OTA using any custom recovery (for example TWRP) is you spoof the build thumbprint: you can edit the ZIP of the OTA, or change the data in the recovery.
- The OTA will install a new kernel (it fully overwrite the partition), so you will require to re-root.
That's all!
Use flashfire
zeft64 said:
Use flashfire
Click to expand...
Click to collapse
What's your experience with it so far with G5 Plus, or others using it with our device?
If none, maybe be careful about recommending it without giving further info.
Installed it and on first screen (Actions) it says:
"Motorola devices experimental
While some basic testing has been done for flashing this brand's firmwares, caution is still advised. Please consult with expert users for this brand before performing potentially dangerous actions."
It also says on the Playstore blurb and Chainfire's XDA thread for it that it works "without using a custom recovery", so if we have one is that a problem? I know it is for flashing OTAs otherwise, but does it get around having one if you do?
More generally it also says in both places:
"FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and the XDA discussion thread before doing anything potentially destructive"
Avoid flashfire... I tried to install something and let the device "dead"... I don't know how, but got back to life after some minutes...
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Dahenjo said:
What's your experience with it so far with G5 Plus, or others using it with our device?
If none, maybe be careful about recommending it without giving further info.
Installed it and on first screen (Actions) it says:
"Motorola devices experimental
While some basic testing has been done for flashing this brand's firmwares, caution is still advised. Please consult with expert users for this brand before performing potentially dangerous actions."
It also says on the Playstore blurb and Chainfire's XDA thread for it that it works "without using a custom recovery", so if we have one is that a problem? I know it is for flashing OTAs otherwise, but does it get around having one if you do?
More generally it also says in both places:
"FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and the XDA discussion thread before doing anything potentially destructive"
Click to expand...
Click to collapse
I'm sooooo glad someone else commented on this. I'm sorry man.
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.
The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)
Things we know:
TWRP and LOS-based systems with encryption either don't install correctly or boot correctly afterward. (2 different things perhaps).
Installing Magisk on non-encrypted partition gives boot loop
All LOS-based OS's must be installed on non-encrypted partitions
There is no easily found issue in the Jira issue tracker or TWRP bug tracker about this problem for the OnePlus 5.
I earlier posted this reply in the RR LOS ROM thread in response to another question about LOS-based OS's and encryption. I thought that rather than take a thread off topic, this is a better place for it. (where it can be totally ignored ). I shouldn't have attached this issue to a single ROM's thread since it affects a lot of LOS-based ROMs. There are other little offshoot pieces to this and some may deserve their own threads or questions at least.
TWRP: A number of people using TWRP (official or non) have problems restoring nandroid backups, which pretty much defeats much of the utility of TWRP if you can't do this. Does it have anything to do with Encryption? IT appears to, at least on the encrypted version when using the non-official version. There is a warning about it right in the thread title for non-official TWRP. I've had no problems restoring while encrypted using the official 3.1.1-1 version, but I'm beginning to feel kind of lucky in that regard.
LOS-based systems: These devices that are going to use LOS based systems require decryption of the data partition before installing whichever LOS-based ROM you're interested in. For some people, it's fine. They don't care so I don't see them as having a problem. I actually like encryption and want it, so this problem will keep me from using LOS-based ROMs until it's fixed. I've got a lot of years with Linux and Android experience, have helped with coding and customizing kernels, OSs and recoveries (mostly Philz) in the past, and would be glad to dig into the problem, at least for awhile to see if anything new can come to light but I'm not kidding myself or anyone that I can figure any of this out myself and I'm way out of practice.
Magisk: and non-encrypted partitions are also not happy together, but since I'm not too sure about the nature of that problem, I'll just call it a one-off for the moment.
Things to do: It'd be nice to figure out which area this "blob" of a problem is most likely to be in, and it'd be even nicer if one of the devs that I'll list below already knows where it is and could tell us. I can see some reason for suspecting TWRP and some reason for suspecting a combination of the OP5 FS in combination with the LOS-based ROM (or it's installer). It's not clear yet. I made a quick dirty list of some of the devs either involved with OP5 TWRP or OP5 LOS-based systems and will "mention" them in this thread in case they already know and/or are working on these things.
Another bit of this is that I signed onto Jira bug tracker (Lineage OS) to see if I could find even one sample issue that resembled this on an OP5. I couldn't but I can find some similar ones on other devices with dates only a month old. Part of this would be to try to get this either/both onto the Jira bug tracker or the TWRP bug tracker or both. Another part before that is really deciding whether this issue belongs in those places.
My question:
It's even be helpful to know whether the suspicion of LOS-based ROM and TWRP devs @apascual89, @DarkExistence, @Dees_Troy, @koenkk, @chenxingyu and @xdvs23 is that it is a problem due to TWRP or LOS ROMS or is it the combination of the two? It's be more useful to know what is most suspected to be the actual problem.
Thinking it over: It seems possible that encryption as it exists on the OP5 (in it's native OSs) is not yet available either as a blob or in an API (or in code of course) to LOS. If that's a decent premise, then LOS is just awaiting some nebulous release of either code or prebuilts from OP (not that that's any small thing or can even be counted on).
Personally I'm just curious to know what is thought to be the biggest factor preventing using LOS with encrypted partitions.
Many thanks in advance to anyone that can supply an answer(s). I'm going to do a git on Resurrection Remix to start looking into it. I've got TWRP already and am looking at that. My odds of finding anything are slim alone. If anyone is interested in this, it'd be useful for you to note your interest. If I can think of a unique way (or if you can) to describe this as a LOS-based bug or a TWRP one, then please feel free to either tell me or just open a bug report on Jira or TWRP.
Addition: May as well ask if there's already a link to an issue in Jira. I've scanned it but not found one: https://jira.lineageos.org/browse/BUGBASH-612?filter=-5
Click to expand...
Click to collapse
Clarifications of what I/others would like for the OP5 (TWRP/LOS/MAGISK) spoken of above & below:
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
Click to expand...
Click to collapse
Updates regarding latest encryption fixes in a couple of LOS-based ROMS:
I got multiple reports that CRDROID (Los-based) and Unofficial RR (LOS-based) are both now patched to work with Encryption.
SO: It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
More updates about ROMs and TWRP's:
Here's some updates:
1) ROMs: It's looking like the custom LOS based ROM world is headed for encryption in some cases within a few versions. You can look at the last couple pages of official and unofficial RR to see what's been discussed, but it sounds like a trend is forming that pretty much matches the trend of smartphones in general.
2) TWRP: Even though this discussion (it's about the most recent dozen replies that include me, katinatez and xdvs23) is , I think, in the official twrp thread, it's about some combination of a) official b) unofficial and c) katinatez (Damn, I know I spelled his name wrong , sorry).
Official : Good points: Can do working restores encrypted /// Bad: Can't work with OTG
UnOfficial : Good points : Work's with OTG // Bad :: Can't do working restores usually.
katinatez TWRP: Good points: OTG OK, Restores OK, Encryption/Decrytion OK; But: It's not an official nor has a thread for it and you have to self-mount /system before doing these things.
The idea is to combine the best points of unofficial and katinatez and it sounds like development is back on, and maybe a commit of both katinatez and xdvs23's code can be performed pretty soon.
Some progress seems possible!
Click to expand...
Click to collapse
Looks possible that TWRP (Unofficial) just took a leap forward and is doing a bunch of things right:
Things it's doing well (well via the few reports starting here: https://forum.xda-developers.com/showpost.php?p=73220260&postcount=910)
1) Backup / Restore nandroids (I just asked for some details on encryption states in that thread but I think the restore was to encrypted partition.
2) OTG working
3) TWRP Themes working.
4) I'll try it and check adb access and sideload as well and report back.
Click to expand...
Click to collapse
Thanks for carrying on the battle. So far it seems good to me, so nice work! -- I just installed, plugged in and mounted OTG device and did a full (all partitions) encrypted backup to the usb-stick, then restored it. I saw no red characters, and I may have forgot to save the log (doH!) but will look in the backup folder in a bit.
Currently I'm running noLimits with Elemental 1.06. No problems. Oh yeah, themes working fine as well. Unless something odd crops up, this could be a real recovery.
Good work to you guys for persevering.
Other things tested: Sideload mode OK; Adb shell OK. Installed xXx ROM latest version with another kernel: OK.
-- Probably this will be the last entry since a fully functional TWRP was a big thing on the wish list and it appears to be here. The thread is the "Unofficial TWRP" thread currently, but maybe it'll be renamed.
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
ArkAngel06 said:
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
Click to expand...
Click to collapse
Same with me. I can a step back and sort of see the long view where this thing gets somehow solved in a day or a month or whatever, and the moment it's solved, no one recalls it was such a pain in the butt. IT does keep me from testing LOS-based OS's because encryption won't work with them. It does keep me on my toes whenever I have to restore my phone from a nandroid backup and that stuff seems like where we should focus some energy.
The thing that bugs me as much as anything is that there's no visibility into anyone "doing anything" about this. I keep hearing people saying (devs too) "I don't know" and "Someone will fix it" and that could certainly happen, (or not). I'd feel much better about it if I could at least search up a bug tracker issue in one of the fairly obvious places (Lineage (Jira) bug tracker) or (TWRP bug tracker).
You're right. It's an insane amount of time to waste for something that should be a 10 minute restore from nandroid backup, but the problem is clearly bigger than that even.
Forgot to add this::
Please try to add any ideas you've got no matter how stupid you might think they are. I'm going to start when I return home.
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week.
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
@ArkAngel06
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
Click to expand...
Click to collapse
It's no problem, I thought the video might be like a week old or something, but i figured you wouldn't just now be posting the fix if it was done a week ago.
I hope some people give it a try and it works for them. You'd be a hero. :highfive:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
Click to expand...
Click to collapse
Thanks snowwolf;
I think I replied to some of this in my reply to @ArkAngel06 already and I appreciate it. For Magisk, it seems like we're in a race between Google and the Magisk/SuperSU developers that'll never end. They have to keep leap-frogging each other which I suspect they'll do for a long time yet. It's great to have work-a-rounds and with SuperUser utilities, maybe that's about all we can ever hope for. The emphasis has been thrown on "high security" devices by too many companies and even governments so that the security world will never again look like the beginning of the smartphone era when nearly every phone had an unlocked/able bootloader. I appreciate the reply.
dladz said:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
hachamacha said:
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
Click to expand...
Click to collapse
This is my thread, never got round to making a script but shouldn't be too hard.
Haven't tried this on the OnePlus but the principle should be the same.
https://forum.xda-developers.com/showthread.php?t=3604856
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Another thing to take into account now that may be getting solved with some luck is that the RR official build has had this commit applied today to attempt to fix a LOS-based build to boot encrypted. No one has any idea (I think anyway) whether it works yet, but we should know pretty soon. RR is pretty popular.
Here is the commit(s) I found ::: https://github.com/apascual89/andro...mmit/a13eef258620e0726c6dcd9e83dacc1342080ed6
I'll update the OP if it worked.
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
MrWilsonxD said:
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
Click to expand...
Click to collapse
Thanks. That was my goal I thought maybe we're getting closer on some of these issues that all sort of whirl about one another in the encryption realm. The 'commit' in RR I noted above in some other reply was at least a brief ray of light but I've heard one report that it didn't work so far. I guess we'll see if anyone gets it to work. Cheers.
Quote of someone (and myself asking questions) from the RR Official thread where the commit to try to fix encryption+LOS happened earlier:
Hecke92 said:
Tried encrypted install, but cannot get past boot screen
Thanks anyway
Click to expand...
Click to collapse
Just curious if there's any details you could share about which version TWRP,
which version and type (SuperSU or Magisk) SU and what you had installed prior to this encrypted attempt.
Also which type of encrypted (ext4, f2fs, etc) would be the target?
many thanks for any information either way.
And the reply I got back::
I have the latest tarp by xdvd (as i saw it was newer than official twrp). I am always using magic, but that is of no relevance I think (because I clean flashed RR and no SU is integrated).
Partition is ext4 and before I had OOS (XXX)
so apparently over in the RR unofficial thread there are users reporting that they flashed and booted on an encrypted device.
success.
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
heisenberg33 said:
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
Click to expand...
Click to collapse
Hey cool! That's terrific. I don't have time to scan the source and see if it's any different than the changes I listed from official RR but really this at least halfway satisifies the premise of this thread. I guess I'll keep it going until we're sure that TWRP can backup/restore nandroids no sweat regardless of encryption state and also handle OTG devices. Then I think we're onto a more solid start.
I'll fix this thread up tomorrow in the OP and when it's served a purpose will stop updating it. Shouldn't be long
Thanks to you last two guys for shouting this out for people. I asked a question at the end of official about where their github is located. I don't see it in the OP where official RR lists theirs.
Updates from recent comments in RR ROM LOS-based Unofficial & Official versions::
Since I've not yet found the exact source used in the unofficial version which is now working encrypted on the OP5, I'll have to wait to put up a link to it. @Eliminater is the author so credits to him and whoever did the working commit. If @Eliminater can give us a link to the working github where the changes that made encryption work were committed, it'd be appreciated.
Comments from https://forum.xda-developers.com/oneplus-5/development/los-resurrection-remix-n-t3632856 (unofficial RR) seem to indicate that although they managed to get encryption working OK with RR unofficial that they "may" have lost the ability (at this point) to run non encrypted. I'm not certain of this but that's how the comments/replies look. I'm sure it'll settle out soon. I'm also pretty sure that every LOS-based developer for the OP5 knows where the source is where this change occurred and that's more important than me knowing where it is. (so good job!)
Comments from Official RR: https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578 where I found and posted the commit that was supposed to fix encryption, indicate that they're not yet quite there. Comments say that encrypted official RR is not yet working and still boot-loops. Shouldn't take long for them to get these two synced up, but that's just my take. On Official RR, decrypted works.
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
gershee said:
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
Click to expand...
Click to collapse
Thanks for the report. It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
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.
Hi,
Phone: Moto G4 Plus(32GB)
TWRP + Magisk + Xposed + Elementalx : Is this a gud idea?
Is Magisk Hide effective enough to use Banking apps in rooted phones?
Whats safetynet exactly. What does it mean that its pass?
Its expected that Moto G4 Plus will get Oreo Update.
Will the Update be available if device is rooted with Magisk?
Is there a blog that any body has used to do this on their Moto G4 plus and has successfully worked with everything working without any issues?
can you give me the link to that step by step blog/forum which you used?
There were too many blogs/forums about this and there is a reply in each one them saying that their phone is bricked now. Dont want to take that risk.
Does anybody have a perfect/absolutely amazing blog with step by step guide.
This is my primary phone.
Your help will be much appreciated.
eighty9sid said:
TWRP + Magisk + Xposed + Elementalx : Is this a gud idea?
Click to expand...
Click to collapse
Not good idea,
Correct order,
TWRP > Custom kernel > Magisk . (Done.)
Don't flash Xposed if you want to use banking apps, it will break safetynet.
Is Magisk Hide effective enough to use Banking apps in rooted phones?
Click to expand...
Click to collapse
Personally, i don't use banking apps, but Magisk Hide works fine on other similar apps. So, it will be fine there..
Whats safetynet exactly. What does it mean that its pass?
Click to expand...
Click to collapse
Safetynet is term that is related to safety,
If your device passes safetynet then it's secure, banking apps and others will work fine,
But if safetynet fails, then your device is unsecured, banking and related apps may not work..
Its expected that Moto G4 Plus will get Oreo Update.
Will the Update be available if device is rooted with Magisk?
Click to expand...
Click to collapse
Even Lenovo/Motorola don't know when OREO will be there for Moto G4 Plus. No other comments
EDIT: If update available in future, you will have to be on stock unmodified ROM, that meams it will fail if magisk or any mod installed..
can you give me the link to that step by step blog/forum which you used?
Click to expand...
Click to collapse
Check Guides section for Unlocking and flashing TWRP,
And follow LATEST guide for rooting (older thread/information for rooting can brick your device)
And if you are finding XPOSED + Safetynet Pass + Banking apps, then not possible..
Hello there,
I too am using Moto G4 32GB Dual SIM (XT1643) as a daily driver and I am using a Custom ROM i.e. HAVOC which is an Android 8.1.0 Oreo based ROM. I am using Magisk and TWRP and banking apps like SBI anywhere, Kotak App are working flawlessly. I have not tested Google Tez though.
Even when I had the stock ROM, I rooted it using Magisk and Installed ElementalX Kernel via TWRP. I followed steps from XDA itself, used this link:
https://forum.xda-developers.com/moto-g4-plus/themes/g4-g4-plus-how-to-install-magisk-pass-t3551896
And as per your question on SafetyNet, it is basically a security check for android developers so that they can verify that the phone is not rigged or rooted or modified. In order for every developer to write their own code to go through various checks to check the integrity of the phone, google provided SafetyNet an easy to implement feature for developers. For more on SafetyNet, visit this website.:
https://www.nowsecure.com/blog/2017/08/03/android-apps-google-safetynet-attestation-api/
And as far as Magisk is concerned, I personally prefer Magisk over any other rooting solution, there are more than one reasons for that. Mainly I that I play Pokemon Go, so Magisk does it's job very well hiding my device status from Pokemon Go.
For difference between Magisk and SuperSu, here is the link:
https://www.xda-developers.com/magisk-vs-supersu/
You can install OTA updates with MAGISK easily, just need to install STOCK kernel and Uninstall Magisk.
I've never used XPOSED on my device, so I cannot help you with that.
And you may know this already, but I will tell you just in case you don't, In order to root your phone or install custom recovery, you need to unlock bootloader and then install custom recovery like TWRP.
To unlock your bootloader, visit:
Motorola - Unlock Bootloader
And Finally, I hope you know what you're doing. Follow the steps carefully and always read comments and user reviews before doing anything at all.
Happy Rooting
Maybe Wait till OREO OTA comes
I asked this because these two links kind of suggested that it was possible.
https://www.reddit.com/r/nexus5x/comments/5wdb27/does_elementalx_kernel_break_safety_net/
https://www.xda-developers.com/systemless-xposed-android-oreo-available-pass-safetynet/
I may be wrong.
Maybe i should wait for Oreo OTA to come and then decide.
Magisk Xposed is not working, I tried both the version of Xposed but phone doesn't boot at all. So in short, Root with Magisk + banking apps is possible, but root with Magisk+Xposed (even Magisk xposed)+banking apps is not possible as of now.
I tried Sandhook and Yahfa, both are not working.