Database Users

Backing up the Atrix and OTA Bootloaders...

Hi Gent's, I have some holes in my Atrix knowledge, that with all the recent developments and new members/devs I'm sure would be helpful for all to discuss and clear up.
The problem is as follows.
How can I, and others, backup their Atrix in safe secure manner that allows us to take advantage of, and remain flexible, for both future updates, either XDA member created, or OTA(which could mess with things, for example blocking our bootloader unlock for those who OTA and haven't unlocked yet, thereby denying them further future flashing freed-up fun roms).
I know we need to backup and save the PDS partition if we want security in flashing the roms regarding touchscreen and device issues, but some things need to be spelled out. First things first, my understanding is a month ago we didn't have a fully functioning CWM, we had tenfar's CWM bootstrap, which was limited in function. I heard something about borked backup/recovery with it, so I played things safe, didn't touch it. Now a couple weeks ago tenfar put out a new version that supports the Atrix post-unlocked bootloader, which allows for greater functionality in CWM. What I need to figure out guys, is what's the protocol for backing up the PDS, making a safe backup of the ENTIRE phone, and then the safe way for wiping the cache's, (IDK which one's, I don't want to trash my touchscreen lower half like some people did?), followed by the currently established procedures for switching from rom to rom.
This is all compounded by the problem that either yesterday or today a new (bootstrap?) item was given Atrix compatibility by the almighty Koush, something called ROM Manager. Should I use this instead of CWM, or should I wait. I'm fine with TiBu for apps and data, but I need to be sure I have everything necessary to restore the phone if necessary because of a bootlooping new rom for example, because I've heard too many nightmare stories about people so far, granted some members have done some stupid stuff, but I think it would be helpful if some of the recent developments in Atrix Backup/Restore could be explained by someone omnipotent in this area.
I'm thinking the correct options are, get Tenfars latest CWM, which REQUIRES bootloader bashing, followed by a Nandroid(?) backup in CWM, then wipe data cache, and dalvik cache, and any other cache's?(IDK!) After the wiping, then install new rom zip from CWM as usual, correct?
The problem with the procedure above, is I think Tenfars latest CWM requires pudding, which presents me and probably others with the following dilemma. I'm assuming, because of Motorola's past history, that when the ATT GB update OTA's, they are going to try to f**k with our current implementation of pudding bootloader unlock, for those who aren't unlocked yet, just how they closed up root with every past update for example. These guys are security nuts, read a post of mine I made last month, they definitely read our forum, at least the Nvidia Tegra guys I've confirmed to. Now I may be wrong, and they may not able to implement this, but I don't want to confuse you guys, I know that those who are unlocked will stay unlocked, but what if they refuse you guys OTA GB official because they check for unlocked BL? That's why me, and I'm sure others haven't unlocked yet. I plan on waiting for the OTA to pop up, pressing install later for 3-4 days denying the update, and checking XDA feverishly to see if those who install the OTA can use CWM, root, Unlock bootloaders, etc. If they lock up the new official GB OTA, then I'll just hit install later one last time, unlock bootloader, and pop in one of the many roms raining down from the sky.
Also this isn't so much a question, as it's a discussion, because I feel like I can't be the only one with these information gaps. If someone can add to the collective knowledge, it will help all of us
/on an unrelated closing note, since it's raining roms, has anyone tried Cherryblur 1.1a, AND Quickrom V1 (7/18), AND Kpenn's GB Beta 4 AND Ninja V 0.4.2 Alpha, AND Dorains Redpill? I'm curious if anyone has been crazy enough or has had the chance to try all of the latest and greatest, I'm sure one of those is more stable than the others, they are all based off of a hodgepodge of unofficial development builds, ha, one's a French 2.3.4 even? Not mention we were goofing around with HKTW earlier, which is MT870 not even Olympus!!! That surely cannot run with much real stablity....

Hi,
Once there is an official OTA for GB, it can be captured and saved. It's a simple edit to remove references to any bootloader. Then it can be flashed using CWM.
Cheers!

Excellent!
Spoken from NF...HIMSELF! Thank you, I was waiting to bite the unlock bullet but I forgot we always steal stuff and repackage it for flashy-goodness.
However, I guess I should just use ROM manager and do a complete NANDROID backup? Does that capture the all important PDS? And by the way, it would seem, that if you stick to legit packages and ROMs and flash with CWM and deal with data the right way, its difficult to brick it would seem?
Dalvik and Clear User Data right, or is there more....
Once again thanks NF, since your such a talented dev for atrix, are you working on cooking a rom?

Will you root given Marshmellow will do app data backup? (Poll included)

I've been rooting devices since my first android device. And using Titanium Backup, to always restore my app data across devices. Or restoring Nandroid backups at times. But it seems with that, upgrades to new OS have become more of a hassle. Since I can not simply let the OTA apply its self.
Having to change to stock recovery depending on the device and in some more recent cases, having to wipe data for the update to go well. It has become a bit of a pain, harder than it used to be.
With Marshmellow doing app data backup. I'm going to try keeping things virgin, no rooting. I may not need to continue with Titanium Backup and since OTAs will work flawlessly, I won't have much personal need to get into the system file area.
So what about you? Respond to the poll and give your take .

I've always done clean install of ROMs, and I always start from scratch with each ROM flash. I'll root as soon as there's a root out.

I mistakenly marked "Yes" to my poll .
Sent from my Nexus 10 using Tapatalk

Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.

rockerrock said:
Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.
Click to expand...
Click to collapse
+1. I got rid of my Verizon S6 because it was way too locked down.

lol asking this on a dev forum... I'd be surprised if anyone says no. It's more than just app back ups. I think phone should ship with root, just enable it/ disable it in the development options. It's like being a standard user on your own laptop instead of administrator... I mean why?

I can see this option on Nexus devices and non-carrier branded devices, but it would never be allowed with a Carrier device. It would be like a work laptop being allowed on that network with software meant to bypass firewalls. Bigger companies will never allow it because of security risks. That being said, I do agree that it should be an option for everyday users.

Can I update with Dec 2016 security patch if my phone is rooted?

Or do I need FlashFire?
I believe that this is the same update as the one in this post
https://forum.xda-developers.com/moto-x-style/general/maintenance-release-dec-2016-security-t3557903

You need full unroot, stock kernel, stock recovery and no system partition modification

lukas77 said:
You need full unroot, stock kernel, stock recovery and no system partition modification
Click to expand...
Click to collapse
could you tell me how I can do this? Is there a general guide?

Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.

acejavelin said:
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
Click to expand...
Click to collapse
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110

ThanuTK said:
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
I hope it helps... Just remember to search around the forums or Google a bit before asking a question. I apologise if I sounded a little snappy, I had just answered some very dumb PM's that frustrated me and then this was the first open thread I saw, sorry if I was a bit abrupt.

This question has been answered a whole lot so it gets a little frustrating sometimes to see a new thread pop up for this issue. That being said and you being new to rooting, I can't stress this enough: please search and read through the threads (and know the XDA rules of course). This device has been out for a while and by now, a large majority of the questions, issues, and whatever else you may have is addressed in these forums. If you do run across anything that there is no answer for, by all means ask away.

Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible

Suri149 said:
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Click to expand...
Click to collapse
Possible? Yes, but it isn't likely and I certainly don't expect it to happen. Lenovo has shown no interest in updating the Pure/Style to support Jio, or even fixing the current VoLTE issues on supported carriers for that matter.

Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?

ThanuTK said:
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
Click to expand...
Click to collapse
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.

My thoughts exactly on the security updates. The only "evidence" I have heard about has been a couple of individuals who do not appear to understand why an app from some unknown source or dodgy websites along with crazy permission requirements might infect their phone. I acknowledge this as a human exploit though and not on the part of Android.

If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:

I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.

roaming4gnome said:
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
Click to expand...
Click to collapse
Dahenjo said:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
Click to expand...
Click to collapse
This is actually a valid way of doing it, but with so many variables to the state of your device prior to doing this the possible outcomes vary a lot.
But @Dahenjo has pretty much the proper procedure... if I was going to try it I'd do it that way... backup, restore stock, take OTA, reroot, reflash Xposed, restore user data... 99% of everything should be intact.

acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
Real good explanation. Good balance of technological and practical
Sent from my iPhone using Tapatalk Pro

acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?

ThanuTK said:
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
Click to expand...
Click to collapse
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.

acejavelin said:
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
Click to expand...
Click to collapse
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451

ThanuTK said:
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
Click to expand...
Click to collapse
The only difference in your links is one is a later build than the other one. Either one should work fine but if I had my choice, I might pick the first update and then use OTA to get to present. NOTE: I had to restore my September 1 backup with TWRP as the December 1 security patch broke my Bluetooth and I use Bluetooth all the time, it is too important to me to lose over a stupid security patch. I have since frozen the updater to avoid being nagged to death install the December 1 update again. When the next "real" OTA comes along, I will thaw the updater so I can take it and *hope* that the Bluetooth issue is solved. I will of course *always* make a TWRP backup prior to doing *any* update so I always have a way to back out of it in the event something is broken over the latest security patch OTA. HTH

Relocking bootloader

Hey guys.
Really sorry for having to post this again :/
Tried posting my issue in this thread but I think that thread's gone cold.
----
I have a Moto G5 Plus US, Model XT1687
Current ROM Info:
Software channel: retus
Build #: NPN 25.137-33
Security patch: Jan, 1 2017
Baseband: M8953_02.03.07.06R POTTER_NA_CUST
On a whim, unlocked the bootloader. Now id like to lock it back.
I haven't updated my phone / installed any OTA's, phone keeps asking to update to NPNS25.137-33-5, haven't done it.
Does this procedure work for me?
Which ROM should I use?
Id like to relock the bootloader and receive OTA updates as normal on my US variant phone!
Many thanks!

I'm pretty sure Motorola hasn't released stock firmware for the retus version.

Cats_PJs said:
I'm pretty sure Motorola hasn't released stock firmware for the retus version.
Click to expand...
Click to collapse
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks

seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..

seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).

Cats_PJs said:
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..
Click to expand...
Click to collapse
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
acejavelin said:
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).
Click to expand...
Click to collapse
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!

seed_87 said:
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!
Click to expand...
Click to collapse
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly

Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.

Cats_PJs said:
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly
Click to expand...
Click to collapse
Oh, wow, I had the (wrong) idea that the SuperSU method was the better one and superseeded magisk. If that works great then awesome I will root using magisk, thanks @Cats_PJs !
easyrider77 said:
Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.
Click to expand...
Click to collapse
Awesome explanation @easyrider77 I will definitely try to root using magisk. Thanks for the warning, don't play Pokemon go and haven't used Snapchat in years so i'm good! I'll try flashing the latest Magisk (v14.0)
One thing tho:
I think I want to (for now anyways) stay stock-ish (stock rom + stock kernel + twrp + magisk).
If I understand it correctly, flashing a custom recovery renders the phone unable to get OTA's (Not that I'd want to apply an OTA update on a modified rooted phone and risk a brick anyways) So, how would one eventually update Android? (Keeping in mind that Motorola hasn't released any retus firmware) Can I flash other non-retus firmwares? (Which wouldn't flash over twrp I think, I would then just loose root and have to flash magisk again, right?)
Thanks a ton guys :good::good::good:
EDIT:
Short xda search pointed me to this official TWRP link, will follow fastboot method to install TWRP.

I'm not sure what exactly stops ota from coming in. I've heard unlocking the bootloader is what causes it, and I've also heard that flashing a custom recovery is what causes it, and I've also heard a custom rom is what does it.
There are options as far as ota goes though, and work the same way, but you'd jsut have to wait. People release flashable ota files all the time, and can be flashed via twrp.
If you want to keep stock, and root that's fine too, but I personally wouldn't worry much about the ota issue at all, because eventually every phone will not get ota as it will lose support, but you can still get the latest and greatest up to date rom with it's features.
Prime examples would be:
Oneplus One,
Oneplus 3
some of the samsung devices like s4
These are just a few, and although they don't receive support officially, they are sporting the brand new android 8 oreo.
Even the samsung s4 has N for it and it came out in 2013 (that's near 5 yrs ago now) and started on Android 4.2.2 (Jelly Bean) and said it was upgradable to 5.0.1 (Lollipop), and now here we are running android 7.1.x.
https://forum.xda-developers.com/galaxy-s4-tmobile/development
(not sure if there were any unlocked variants of that phone at the time as it wasn't a common thing like it is now, that's why I chose the tmobile thread but there are other variants that get it as well)
So when it comes to ota, I personally would not an do not worry about that when I root, that's the last of my worries.
I prefer functionality and customization over ota myself, because most times someone comes out with either an official link to an ota or makes an flashable ota you can flash via twrp, although my semi-educated guess would be if you decide to install the official/stock ota, then it will erase everything you have anyways which can be a pain.
DO keep in mind once you unlock the bootloader, it "officially" voids any warranty and moto does have the option to refuse service if anything goes wrong with the phone, but I have heard some people had no issues and moto took the phone back even when rooted, but that is something you would have to make a choice and live with IF you decided to unlock the bootloader, as there is no way to undo that process.
I have re-locked the bootloader on a moto phone so yes it CAN be re-locked, but........it still gets triggered and moto will know that it's been unlocked even if you re-lock it, because that part is irreversible and cannot be undone, aside from you locking and unlocking it on your side.
As for flashing firmware and all that, make DOUBLY sure you know your phones model number and/or codename, this is key in flashing most anything you do with your phone, because even though a phone may have multiple variants, ie: tmobile, sprint, at&t versions, and even European versions, and the phones are identical in EVERY way hardware wise, you can't just simply pick a rom of choice and use it, it's a matter of knowing what your phones info is.
Example: you cannot take a t-mobile phone rom and flash it's official firmware or it's roms, and updates on a at&t variant, or a metroPCS on a tmobile variant, even though they use the same network, and are the exact same phone and hardware, there are subtle differences and can most likely brick the phone, either hard or soft.
So if I had the US variant of the g5 plus that would be codenamed the same "potter" like the rest, but, the number is different which is XT1687, so I would use that number as my reference, as apposed to the potter name, because there are 3 other variants of that phone which are Amazon Edition and the consumer cellular and of corse the European variants as well, I'm not exactly sure what numbers go with what phones other than the US unlocked variant, but on a quick look the other numbers are XT1684 and XT1685, perhaps someone else with more experience than I have can tell you what those number match up with said phone.
As far as the US variant goes though, I do not want to take a rom or firmware meant for the XT1684 XT1685 and use it on the XT1687 US variant, as it will most likely have bad results, ie: brick of some sort.
That's the main thing you have to worry about, other than that, there isn't much worry. Just do some major research and goggling and read and re-read and read again the directions on the threads at xda as most generally all of them are pretty simple to follow, if you do it step by step.
I recently bought an lg k20 plus phone from metroPCS, have never rooted that phone before and came to xda and followed the rooting thread and rooted it the first time. In a matter of 30 mins I had full root with stock rom (since there are no roms for that phone as of yet) but it is a metroPCS variant, (mp260) and in the case above, this phone is also sold by tmobile, is the exact same phones specs hardware, etc....I could not use the tmobile rom or firmware on this phone.
Hope this helps clear it up some.
Update:
I just bought a 64gb storage/4gb ram US variant of the g5 plus. It brought back some older memories of when I had my other moto, X I think it was, not sure anymore, but I DO remember you can unlock the bootloader as well as re-lock it, but, do keep in mind it still triggers something internally that can't be reveresed, so if moto did decide to check into things, they can tell if it's been bootloader unlocked.
So while you can unlock and lock the bootloader on our side, moto can still tell it's been unlocked, even when re-locked. Just hope if you send it back in they just don't check it and even if they do, hope they don't bother sending it back saying your warranty is void sorry.

Thanks @easyrider77
I used to install custom ROMs on my older phones. Recently though, stock android has gotten pretty good so maybe when this phone loses support I'll try some ROMs. Out of curiosity, what ROM/hacks/kernel do you use?
So, how does this sound:
- Install the OTA my phone's been prompting me to update to (upgrading from NPN25.137-33 to NPNS25.137-33-5 and I think it will then try to update to NPN25.137-83 with an August 1 security patch)
- Install TWRP via fastboot, make a nandroid backup!
- Root with Magisk v14.0
- Looking into maybe changing the boot.img "Your device is not trustworthy" thing
- Adaway! Xposed! Other goodies yay!
- Any other recommendations?
PS: Can Magisk root every firmware released by Motorola for the Moto G5+?

I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.

easyrider77 said:
I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.
Click to expand...
Click to collapse
WIll do, many thanks for all your help guys!
@easyrider77 @Cats_PJs @acejavelin
:good::good::good:

Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck

Cats_PJs said:
Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck
Click to expand...
Click to collapse
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.

easyrider77 said:
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.
Click to expand...
Click to collapse
I really don't have a problem with the sound volume, except when I plug it into my truck. If there's a good song on, and I really want to crank it up, I run out of volume, so I usually turn up the headphone gain in the kernel settings by 3.
I haven't noticed variance between ROM volumes on this phone, but I know on my old note 3 there was definitely fairly large variance between ROMs.

free XZP Pie rooting on Mac, is it possible without CS degree?

At the risk of being barked at by the spirited young hackers on this forum:
After days of searching the interwebs, I am close to resetting to factory settings and returning this thing, even though I really like the phone itself.
Admittedly, I'm a total Android virgin and know only what many hours of googl'ing have left behind (it's all a blur, at this point), but after all of my attempts to use the common rooting suspects (KingoRoot, King Root, iRoot, etc.), I sit here more confused than I can handle.
First attempts at figuring out adb and fastboot made me realise I am in way over my head.
Anyone know of a way to root my XZP running Pie, from my Mac, for free (if at all possible), without first having to get a degree in computer science. I can stumble my way around Terminal, if given clear instructions, but that's where it ends.
hope someone can help.
I really want to get the EU firmware flashed onto this thing, with the modem working as designed for the US market, and hopefully use this thing as a router and many other things that require root access.
But I also read the thread about people like me, who don't know much about Android, ruining their bootloaders and then coming here for help/support...so the question for me arises is: reset to factory settings and return it, before I get myself into quicksand territory, or do whatever it takes to figure it out (with the help of the esteemed community).
It's just such a nice phone, and I miss the iOS jailbreaking days so much, that this would be the perfect antidote.
Anyone care to help?

About the reason, that you are post in this forum thread, I guess you've make your choice of phone. Isn't ir?
In this case, there is a very good manual how to save your TA partition, root the phone and so on...
If you are unsure, which phone you will buy...... Make first of all your choices... Look in xda if the device is supported and following the thread

mad0701 said:
About the reason, that you are post in this forum thread, I guess you've make your choice of phone. Isn't ir?
In this case, there is a very good manual how to save your TA partition, root the phone and so on...
If you are unsure, which phone you will buy...... Make first of all your choices... Look in xda if the device is supported and following the thread
Click to expand...
Click to collapse
thanks for that first heads-up, mad0701.
yeah, I am set on the XZP, as my first Android phone. It serves my primary purpose of being a little presentation device for my 4K video and photography work perfectly, I already enjoy it as a very good Hi-Res music player, it will hopefully serve me as a little portable router/VPN, etc. once I figure out how to root it, and it was a great deal, for a used one, for so much power. But I also want to be able to use its fingerprint sensor, here in the USA, and for that...
So when you say that "a very good manual" is out there, would you be so kind as to share a link? I tried to follow so many methods, at this point, that I am at the end of my wits.

Check this thread... There is a manual available... Step by step... Only give attention, that you flash the TWRP version for your device...
https://r.tapatalk.com/shareLink?ur...share_tid=3795510&share_fid=3793&share_type=t
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented

mad0701 said:
Check this thread... There is a manual available... Step by step... Only give attention, that you flash the TWRP version for your device...
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented
Click to expand...
Click to collapse
thanks again, mad0701...I was out riding all day and just skimmed over that link...first reaction: this is more advanced than I feel confident tackling...I fear that a one wrong action on my part might leave me in a situation where I can't even get the phone back to factory settings, and won't be able to return it anymore (for which I have one week left).
I'll read through the manual in more detail, maybe tomorrow, and if it seems that I can actually do all that, successfully, then maybe I will give it a try. But since I don't even know what the TA is, or the TWRP version, it may be something I may not wanna get into at this time...only so many hours in the day.
but thanks for showing me the manual!

tillkrueger said:
but thanks for showing me the manual!
Click to expand...
Click to collapse
mad0701 said:
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented
Click to expand...
Click to collapse
Lots of people keep pointing at this thread without actually reading it. There still isn't a way to relock your bootloader with your saved TA partition. Yes you can save your individualy encrypted key, but then what?
You still need to unlock your phone to get permanent root, with no way of putting the key back in place, so you still need a 'fixed' kernel
If you want an easy way to root your phone, as you admit yourself your android experience is limited., then I would recomend Xperifix
@sToRm// wrote a one stop shop program that did everything, but then took his work to a private website as he wanted to charge for all the hours that he put into it.
The original thread is here, this would tell you what to do and the drivers you need to install (important). Then the go to the Xperiafix website and pay your $20.
I used it to root my XZ1 compact and it really was as easy as plug it in and follow instructions.
The only probelm with this is that there still isn't a root available for Pie firmware, so his fix is based on Oreo builds.
Lots of people speak badly of Xperiafix 'why pay for a fix when you can get it for free?'
Yea, but free is complicated and I'm happy to pay for easy.
Edit: To answer your original question, I'm not sure there is a Pie root kenel for a stock rom available yet, I know @janjan posted a Pie kernel on the XZ1compact thread, so it's just a matter of time before he updates the XZ premium
You could go with a custom rom to get rooted Pie, read the instructions and decide if you're up for it.

Didgesteve said:
Lots of people keep pointing at this thread without actually reading it. There still isn't a way to relock your bootloader with your saved TA partition. Yes you can save your individualy encrypted key, but then what?
You still need to unlock your phone to get permanent root, with no way of putting the key back in place, so you still need a 'fixed' kernel
If you want an easy way to root your phone, as you admit yourself your android experience is limited., then I would recomend Xperifix
@sToRm// wrote a one stop shop program that did everything, but then took his work to a private website as he wanted to charge for all the hours that he put into it.
The original thread is here, this would tell you what to do and the drivers you need to install (important). Then the go to the Xperiafix website and pay your $20.
I used it to root my XZ1 compact and it really was as easy as plug it in and follow instructions.
The only probelm with this is that there still isn't a root available for Pie firmware, so his fix is based on Oreo builds.
Lots of people speak badly of Xperiafix 'why pay for a fix when you can get it for free?'
Yea, but free is complicated and I'm happy to pay for easy.
Edit: To answer your original question, I'm not sure there is a Pie root kenel available yet, I know @janjan posted a Pie kernel on the XZ1compact thread, so it's just a matter of time before he updates the XZ premium
Click to expand...
Click to collapse
Theres no need for a kernel for pie, flash pie, flash twrp flash magisk. That's it.

Beetle84 said:
Theres no need for a kernel for pie, flash pie, flash twrp flash magisk. That's it.
Click to expand...
Click to collapse
I just realised that Xperiafix is a windows program anyway Doh

Didgesteve said:
I just realised that Xperiafix is a windows program anyway Doh
Click to expand...
Click to collapse
I totally missed the Mac part....

Alright, u need adb and fastboot for mac.
If you will find newer instructions use it, here is the first thing I found.
Unlock ur device here using fastboot, it clearly written there how to do it.
Find latest twrp recovery in this forum.
Use fastboot again.
"fastboot flash recovery your.recovery.img"
Then, using this recovery u need to flash latest magisc.
I've gave u enough information, with minimum efforts u will be able to find everything u need to do it. Plus u will learn something useful.
Goodluck

tillkrueger said:
thanks again, mad0701...I was out riding all day and just skimmed over that link...first reaction: this is more advanced than I feel confident tackling...I fear that a one wrong action on my part might leave me in a situation where I can't even get the phone back to factory settings, and won't be able to return it anymore (for which I have one week left).
I'll read through the manual in more detail, maybe tomorrow, and if it seems that I can actually do all that, successfully, then maybe I will give it a try. But since I don't even know what the TA is, or the TWRP version, it may be something I may not wanna get into at this time...only so many hours in the day.
but thanks for showing me the manual!
Click to expand...
Click to collapse
the manual looking complicated but it only took 2 hours for me, and if u backup and restore your TA partition, u dont need any drm fix for all firmwares, and dont pay for any useless programs like xperifix(the guy on upper comments always advertise this useless windows program)
for rooting, its very easy on pie

I really appreciate all of y'all's input...but, to be honest, I understand too little of it, at the moment, to feel inclined to dive into executing some of those instructions.
I mean, it looks like I was given enough info to have a chance to root and flash my XZP successfully, but I may just hold off for a bit, maybe return this one and wait until I can either score an XZP that's already been rooted and flashed with the mixed EU/US firmware, or wait until I can afford to get a newer device, which has all of the features I am looking for already working: 4K screen, fingerprint sensor, and preferably being a Sony...if such a device exists now.
But truly, thank you all, for now!