Database Users

Upgrading from Classic Root on Stock 5.1.1 to 6.0 ROM questions

I have a Moto X running the Stock 5.1.1 using whatever root method was out when the phone first became rooted.
I want to ugprade to this ROM http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242 using the "Rooted 60 Deodexed" I haven't flashed a phone since I got this one, so I have a few questions.
1) I'm encrypted but using the custom TWRP from this post http://forum.xda-developers.com/showpost.php?p=65045112&postcount=474. Will that cause any issues?
2) If I want to revert to a Nandroid of my 5.1.1 coming from the 6.0 ROM, do I just restore the Nandroid or are there additional steps to take?
3) Coming from what I assume is a classic system root, but flashing a new ROM, do I need to go back to unrooted stock first, or just flash the ROM for the new fancy systemless root?
4) What is the difference between Odexed and Deodexed?
4a) Will that affect Xposed/XPrivacy at all?
Thanks so much!

If I were you, I would first back everything up, then flash the stock 5.1.1 unrooted file in this thread: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 after doing a factory reset in TWRP. Do a full wipe (this should undo any encryption you've got going on as well). This would be the best way to avoid any issues along the way. (I always do a full wipe when flashing something new out of habit to avoid issues). You may be able to just skip this install if doing a full wipe as well. I'm not too familiar with having encryption on my phone.
After you're booted back up on stock unrooted, flash whichever 6.0 rom you want in TWRP after a factory reset. Systemless root as far as i know is only good if you want to use android pay. Xposed should be fine to use, generally speaking, but you can't use Xposed if you want to use android pay, it breaks it.
If you want to revert to your 5.1.1 nandroid, I would flash that stock file I linked to again and THEN restore your nandroid. I haven't heard of any issues downgrading to lollipop from marshmallow on the 2015 model like there were on the 2014 model between lollipop and kitkat, but to be safe, I'd make sure I was on 5.1.1 before restoring the nandroid.
The difference between odex/deodex is explained here: http://forum.xda-developers.com/showthread.php?t=2200349
Again, these are steps I would take if it were MY phone. Others in the forums may have better solutions or ideas.

@shkmkr Thanks! I'm going to do all that. My main goal is to make sure that at the end of the day, Skvalex's Call Recorder still works as I use that heavily for business calls. I don't really use Android Pay so I don't mind that breaking. I just want to avoid (soft/hard) bricking the phone by downgrading/upgrading around with an unofficial TWRP.
I would like to avoid wiping the encrypted data partition if possible since, encrypting is not the easiest with root. It tends to not encrypt on reboot except under special circumstances which I forget partially. Stock recovery is definitely one of them though and I don't know where to find the stock recovery for 6.0 on this phone as Motorola doesn't have the official 6.0 posted yet.

Could you let me know if this works for you? I made a THREAD a while back and didn't get any help on it. I would like to follow this if it works.
Also I messed up one time and I did infact downgrade back to lollipop and restored my nandroid with no problems. I want to do my 2nd attempt but I want to get it right.

you can get the stock recovery from that first link i mentioned under the 6.0 section.

Second time trying to root phone and I want to make sure I've got this 100%

Alright so I apologize in advance if this thread has been posted a million times and believe me, I've spent the last 4-5 days combing through to make sure I could get every detail of this process done correctly. So I'm not just blindly asking for instructions on how to root my phone. Apologies also if I posted this in the wrong place.
For starters, I'm using Moto G4 Plus XT1641 6.0.1 Build Number MPJ24.139-23.3. My carrier is Koodo in Canada (unsure if that's important but I'll need to being it up again for another point). The files I downloaded were from a youtube tutorial and this includes ADB program, TWRP img 3.0.2.0, supersu zip 2.46 and Motorola Drivers 2.5.4, SOME of which I think may have been outdated versions.
So Saturday night I tried to root my phone with those files. I followed some more guides, I unlocked my bootloader and I think I mostly did everything right except for getting the right supersu version as I've seen up to version 2.82. I think this may have been my first mistake but maybe someone correct me if I'm wrong? My other mistake was not making a backup in TWRP. I'd read about possible wifi problems after rooting so I grabbed the elemental package and possibly even flashed that wrong. I can't even remember the steps of what I did but I'm sure it was all wrong.
Main point, after all that I didn't have ccell service, wifi, etc. The common problems that arise when you do it wrong. I ended up just taking my phone in and getting a new phone. Exact same one, same model. And this brings me to where I am now. I've downloaded some new files and I want to make sure that I've got everything right as to avoid misunderstanding some key parts to the process.
Minimal ADB and Fastboot 1.4.2, twrp-3.1.1-0-athene.img, SuperSU-v2.82-201705271822, Motorola Drivers 2.5.4, and lastly XT1641_ATHENE-TELUS_MPJ24.139-23.3_cid50_subsidy-TELUS_CFC.xml. Notice how that last one says Telus? It's the parent company of Koodo so I'm hoping I can use that as a failsafe.
I think I've covered all the key points so to sum up:
1. Did I use the wrong supersu zip version and could that be a reason why I had no wifi/cell service? Is that also possible because I may have flashed the wrong carrier athene file?
2. Are the files I have downloaded now the correct ones I need and up to date?
3. I'm following this guide. With the files I have downloaded, is it still a correct step by step process? Are there other guides that work better?(thats not a knock on the original guide I'm refering to). https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
I think I've got the right know how and tools to root my phone but I'm just nervous of doing what I did before again and would like some reassurance that I'm doing it right. I've just come from jailbreaks, the world of root is much different. I appreciate any help or tips you guys can throw me!

Hmm, that's odd how you lost radio signal when you rooted, did you obtain radio signal back after you unrooted?
A few things I noted:
1)You may wish to update your device to a newer build, you might get an OTA inviting you to update to MPJ24-139-63 (or 139-64), which was the latest Marshmallow build. Once you've rooted, you will not be able to install OTA updates until you have unrooted and restored the stock recovery (from the same build as you currently have). If you get an OTA notification for any build beginning with NPJ, that's for Nougat.
2)If you plan to stay on Marshmallow, you don't need the ElementalX kernel - a custom kernel like ElementalX is compulsory on Nougat, whereas Marshmallow is not as strict with regards to rooting.
3) I hope the carrier ROM is okay, though from other reports, flashing the incorrect ROM can corrupt device partitions, leaving with no IMEI/no service/no FP. We have possible ways of repairing that though.
The tools you've downloaded seem to be okay and Bender's guide is still okay - even though the tools they've used are out of date - so the general procedure would be (up to you if you've updated MM at this point):
Install adb on your computer.
Boot your device to the bootloader.
Flash TWRP 3.1.1 athene (either the offficial TWRP or an unofficial build from shreps or oadam11) as directed.
Reboot to recovery (to make sure the recovery sticks).
Back up all partitions on your device, make the name descriptive.
Make another backup of the boot partition - this contains your stock kernel, useful for switching root manager.
Once the backups have been made, flash SuperSU v2.82.
Wipe cache/Dalvik
Reboot.

echo92 said:
Hmm, that's odd how you lost radio signal when you rooted, did you obtain radio signal back after you unrooted?
A few things I noted:
1)You may wish to update your device to a newer build, you might get an OTA inviting you to update to MPJ24-139-63 (or 139-64), which was the latest Marshmallow build. Once you've rooted, you will not be able to install OTA updates until you have unrooted and restored the stock recovery (from the same build as you currently have). If you get an OTA notification for any build beginning with NPJ, that's for Nougat.
2)If you plan to stay on Marshmallow, you don't need the ElementalX kernel - a custom kernel like ElementalX is compulsory on Nougat, whereas Marshmallow is not as strict with regards to rooting.
3) I hope the carrier ROM is okay, though from other reports, flashing the incorrect ROM can corrupt device partitions, leaving with no IMEI/no service/no FP. We have possible ways of repairing that though.
The tools you've downloaded seem to be okay and Bender's guide is still okay - even though the tools they've used are out of date - so the general procedure would be (up to you if you've updated MM at this point):
Install adb on your computer.
Boot your device to the bootloader.
Flash TWRP 3.1.1 athene (either the offficial TWRP or an unofficial build from shreps or oadam11) as directed.
Reboot to recovery (to make sure the recovery sticks).
Back up all partitions on your device, make the name descriptive.
Make another backup of the boot partition - this contains your stock kernel, useful for switching root manager.
Once the backups have been made, flash SuperSU v2.82.
Wipe cache/Dalvik
Reboot.
Click to expand...
Click to collapse
Thanks for the reply, it helps me feel a little more confident in what I'm doing. I didn't get my cell service back as I just took my phone into Koodo and they just gave me a new one. A few questions.
Are there some clear guides on how to recover from lost wifi and cell service? I've seen a few but it appears they all have different directions so as a newcomer to Android it does seems a bit confusing to what the right way to do it is. I'm also hoping someone can chime in on the Telus carrier IMG file as that seems to be my backup in case anything goes terribly wrong again. I'd hate to have to bring my phone back again a second time. Also, is it an easy process to make a backup of the kernel in TWRP? I've figured out how to make a backup of the normal partition, just hoping backing up the kernel is just as easy.
I think I'm near ready to take the root plunge in the coming days. It's good to see such a strong community here. Totally different from the jailbreak scene.

lemonlimejones said:
Thanks for the reply, it helps me feel a little more confident in what I'm doing. I didn't get my cell service back as I just took my phone into Koodo and they just gave me a new one. A few questions.
Are there some clear guides on how to recover from lost wifi and cell service? I've seen a few but it appears they all have different directions so as a newcomer to Android it does seems a bit confusing to what the right way to do it is. I'm also hoping someone can chime in on the Telus carrier IMG file as that seems to be my backup in case anything goes terribly wrong again. I'd hate to have to bring my phone back again a second time. Also, is it an easy process to make a backup of the kernel in TWRP? I've figured out how to make a backup of the normal partition, just hoping backing up the kernel is just as easy.
I think I'm near ready to take the root plunge in the coming days. It's good to see such a strong community here. Totally different from the jailbreak scene.
Click to expand...
Click to collapse
Hmm, I'm not aware of any guides specifically dealing with lost Wi-Fi and lost mobile signal. There are a few posts where we've had some success in getting radios back, but it involves either hex editing https://forum.xda-developers.com/showpost.php?p=72340548&postcount=98 or flashing hw, modem or fsg partitions from a working device (in this case, XT1641) The instances I've seen of lost Wi-Fi/mobile signal appear to have occurred during a stock ROM fastboot flash, but hoping someone can chime in as to whether it was just flashing the wrong region firmware or something else.
If you want to back up your kernel in TWRP:
Boot to TWRP
Tap 'Backup' on the main menu
Select only the 'boot' partition - this is the partition that contains your kernel (should be stock and clean if you've not rooted).
Rename the file to remind you it's your kernel.
Swipe to back up.
If you need to revert to this kernel, unroot first (depending on your root manager, you may have to boot and then unroot. I recall SuperSU unroots via the SuperSU app settings), then boot to TWRP.
Tap 'Restore' on the main menu
Navigate to your boot backup
Flash your boot backup
You should now have a clean stock kernel, so if you wish to switch root managers, you should be able to obtain root with your new root manager. We want a clean kernel (no modifications made) since uninstalling the old root may leave traces of root on your existing kernel, and thus may cause issues if you re-root with a different manager.
Good luck in rooting

echo92 said:
Hmm, I'm not aware of any guides specifically dealing with lost Wi-Fi and lost mobile signal. There are a few posts where we've had some success in getting radios back, but it involves either hex editing https://forum.xda-developers.com/showpost.php?p=72340548&postcount=98 or flashing hw, modem or fsg partitions from a working device (in this case, XT1641) The instances I've seen of lost Wi-Fi/mobile signal appear to have occurred during a stock ROM fastboot flash, but hoping someone can chime in as to whether it was just flashing the wrong region firmware or something else.
If you want to back up your kernel in TWRP:
Boot to TWRP
Tap 'Backup' on the main menu
Select only the 'boot' partition - this is the partition that contains your kernel (should be stock and clean if you've not rooted).
Rename the file to remind you it's your kernel.
Swipe to back up.
If you need to revert to this kernel, unroot first (depending on your root manager, you may have to boot and then unroot. I recall SuperSU unroots via the SuperSU app settings), then boot to TWRP.
Tap 'Restore' on the main menu
Navigate to your boot backup
Flash your boot backup
You should now have a clean stock kernel, so if you wish to switch root managers, you should be able to obtain root with your new root manager. We want a clean kernel (no modifications made) since uninstalling the old root may leave traces of root on your existing kernel, and thus may cause issues if you re-root with a different manager.
Good luck in rooting
Click to expand...
Click to collapse
That's perfect thank you so much. Am I right to assume that if I get into a jam then I can just restore/reflash my backups and I'll be back to normal?

To be safe, flash the ElementalX kernel before rooting.

reCoded said:
To be safe, flash the ElementalX kernel before rooting.
Click to expand...
Click to collapse
See this is where I get confused, the guy above you said ElementalX isn't needed on Marshmallow but you say i should use it anyway? I've seen a few differing opinions on what should and shouldn't be done, just not sure which one is the right answer.

lemonlimejones said:
See this is where I get confused, the guy above you said ElementalX isn't needed on Marshmallow but you say i should use it anyway? I've seen a few differing opinions on what should and shouldn't be done, just not sure which one is the right answer.
Click to expand...
Click to collapse
ElementalX v0.07 is not required on Marshmallow (provided you are planning on staying on 6.0.1), you can root the stock ROM kernel. You may wish to flash the ElementalX kernel anyway as this custom kernel gives you more control and tuning options compared to the stock kernel. On stock Nougat, because the anti-rooting kernel security is much stricter and enforced (whereas on Marshmallow I don't think it's enforced), then you need ElementalX or vegito or a custom kernel to bypass the security, by in effect replacing the stock secure kernel with a kernel that doesn't have those restrictions. Without replacing the stock kernel on stock Nougat systems, you can run into a bootloop.
As an MM kernel as mentioned before has weaker security regarding rooting, it's up to you if you choose to root the stock kernel or ElementalX.
I've rooted MM (MPJ24.139-63) in the past with SuperSU (v2.79) and only used TWRP and SuperSU.
In response to your other post, the backups should get you out of a jam, since what you're doing should only affect the partitions you've backed up previously (they in theory shouldn't go anywhere near your modem, bootloader or critical firmware). Bear in mind that the TWRP backup if restored in full will revert your messages and data to that backup. You may wish to use Titanium Backup or other tools to take occasional snapshots of your apps data that you can restore should you have to roll back.

lemonlimejones said:
See this is where I get confused, the guy above you said ElementalX isn't needed on Marshmallow but you say i should use it anyway? I've seen a few differing opinions on what should and shouldn't be done, just not sure which one is the right answer.
Click to expand...
Click to collapse
If you're on Nougat, then you should use ElementalX. If you're on Marshmallow, you don't need it.

echo92 said:
ElementalX v0.07 is not required on Marshmallow (provided you are planning on staying on 6.0.1), you can root the stock ROM kernel. You may wish to flash the ElementalX kernel anyway as this custom kernel gives you more control and tuning options compared to the stock kernel. On stock Nougat, because the anti-rooting kernel security is much stricter and enforced (whereas on Marshmallow I don't think it's enforced), then you need ElementalX or vegito or a custom kernel to bypass the security, by in effect replacing the stock secure kernel with a kernel that doesn't have those restrictions. Without replacing the stock kernel on stock Nougat systems, you can run into a bootloop.
As an MM kernel as mentioned before has weaker security regarding rooting, it's up to you if you choose to root the stock kernel or ElementalX.
I've rooted MM (MPJ24.139-63) in the past with SuperSU (v2.79) and only used TWRP and SuperSU.
In response to your other post, the backups should get you out of a jam, since what you're doing should only affect the partitions you've backed up previously (they in theory shouldn't go anywhere near your modem, bootloader or critical firmware). Bear in mind that the TWRP backup if restored in full will revert your messages and data to that backup. You may wish to use Titanium Backup or other tools to take occasional snapshots of your apps data that you can restore should you have to roll back.
Click to expand...
Click to collapse
Right on, I think I feel comfortable with this now! One more question though, with newer versions of SuperSU is it still necessary to make the command echo systemless=true or was that mostly for older versions? Also if that part is needed, should I run SuperSU from the data folder in TWRP?

lemonlimejones said:
Right on, I think I feel comfortable with this now! One more question though, with newer versions of SuperSU is it still necessary to make the command echo systemless=true or was that mostly for older versions? Also if that part is needed, should I run SuperSU from the data folder in TWRP?
Click to expand...
Click to collapse
The 'echo systemless=true', as I understand it, isn't required on SuperSU 2.79 or newer, so if you're flashing 2.82, you should be able to flash as is without having to run the command too Also makes uninstalling easier!

Please backup first

My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk

riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Click to expand...
Click to collapse
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?

psychopac said:
Can I also flash the same fastboot ROM on which my device was while on stock (considering I was on the latest update and was trying to flash the fastboot ROM of the same version) if I forgot to make a nandroid backup?
Click to expand...
Click to collapse
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
riggerman0421 said:
My only question, why do all these people keep hard bricking their phones? Please, your first step after unlocking your bootloader should be a full Nandroid backup, and download of the stock recovery. That way you have the full stock system, kernel and recovery in case of any mistake, OTA, or any other reason to go back to pure stock. If you need to back to stock, restore your backup, then flash the stock recovery in fastboot. Boom, pure stock, able to accept OTA updates, no issues. Please, for the love of God, make a backup before you make any modifications to your phone. Rant over, thanks for your patients.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.

echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
Click to expand...
Click to collapse
That's absolutely okay with me as I always like to clean flash ROMs and I don't mind the data partition being erased.

echo92 said:
That should be okay, though be aware that doing so may erase your data in the process. If you need to, make a backup of your device as it currently is in nandroid/TWRP and move it off your device. That way, if anything happens, then you may be able to copy the TWRP backup back and restore your device.
---------- Post added at 05:42 AM ---------- Previous post was at 05:26 AM ----------
Unfortunately, in the majority of hard brick cases, a backup won't save your device, as it's not the system side of things that causes headaches, it's the underlying bootloader.
The main reason is, from what I've observed, is users flashing either the wrong firmware for their device (e.g. US firmware on an Indian device or vice versa) or attempting to downgrade their firmware. Either method can leave you with a mismatched bootloader and system. OTA updates check what system you have for installation purposes, but appear to assume the bootloader is the same patch level as your system. (Should they check for bootloader as well? That check would go some way to preventing hard bricks, but appears Motorola assumes you wouldn't flash firmware not intended for your device or downgrade...)
Thus, because you have a mismatched bootloader and system patch level, you can run into hard bricks when users attempt to subsequently take OTA updates, especially with bootloaders updated to May 2017 or newer.
E.g. a user flashed the US retail NPNS25.137-35-5 with May 2017 firmware onto their device, but wanted to revert back to the Indian firmware. They flashed back to NPN25.137-15 (Jan 2017 security patch) without being able to flash the bootloader, since bootloaders do not permit downgrading of bootloaders generally, and especially after the May 2017 patch. So you have a May 2017 bootloader but a Jan 2017 system. The OTA update downloads and begins flashing believing that your system is Jan 2017 and applies updates to your bootloader thinking it too is at the Jan 2017 patch level too. Of course, it's not - it's May 2017 - and thus causes a hard brick.
The current resolution for hard bricks is blankflashes to reset the bootloader. The only other resolution is that users do not downgrade their firmware, and are very careful with what they flash, and only flash the same firmware as they had or newer firmware that is a direct update of their existing firmware. Alternatively, flashing TWRP images of stock ROMs may be preferable, as these images only flash the system side of things (like a TWRP nandroid backup), so do not affect the bootloader.
Click to expand...
Click to collapse
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.

riggerman0421 said:
That is the point of having a backup. You don't have to flash anything in fastboot. You have your OWN firmware backed up on YOUR OWN DEVICE and don't have to worry about any mismatch issues.I have been rooting and flashing custom ROMs for 5 years on 7 different devices( this is the first phone I have not rooted...yet). The first thing I always do after installing a custom recovery is make a full backup. That way if I do something wrong, I always have the stock ROM to go back to. I firmly believe all unlocking and rooting guides should have this step included and not listed as optional but as required. This would help prevent a lot trouble from users flashing the wrong firmware on their phones.
For what it is worth, I have rooted and ROMed: LG Optimus V, Nexus 7 (WIFI tablet), HTC One V, Samsung Galaxy 3, HTC Desire 820, Asus Transformer TF101 (tablet) and Motorola Moto G3. On all these devices I had a full backup of the stock system.
Click to expand...
Click to collapse
I agree with what you wrote, a backup in TWRP and having the same stock ROM is essential to a safe and working device... A stock ROM is always useful in flashing the stock recovery and other stock firmware prior to taking an OTA update. With TWRP backups, you now have to be careful not to allow modifications before you take the backup, else the OTA detects the system partition is no longer readonly, if I recall.
Course, this would be much easier if Motorola/Lenovo released the stock firmware rather than having to depend on leaks, but I'm guessing they don't want to deal with users that flash the incorrect firmware for their device.

I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?

vantastic415 said:
I have never flashed a phone before.
It seems I have a virus/malware that's inserted itself into the ROM on my phone. I perform a factory wipe and reset but the malware is there on the fresh install, redirecting webpages to a pop-up about Amazon or Walmart gift cards. Backing up the stock ROM seems not an option for me. Is it possible to download a stock ROM somehow?
Click to expand...
Click to collapse
We have all the stock firmwares posted here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
And TWRP flashable stock ROMs here...
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616

Noob Questions: Firmware,Bootloader, root.

Hi, i just got the moto g5 plus, i always have phones that from the moment i bought them they wouldn recive any updates, so i realy didnt care if unlocking the bootloader installing new recoverys will affect the OTA updates. So i have a couple of questions.
1- first i want to at least have a stock firmware just in case, but i cant figure out which one should i download from here
firmware.center/firmware/Motorola/Moto%20G5%20Plus/Stock/
Before i always use sammobile.com and it was really easy to found a stock firmware from Argentina. My compilation number is: npns25.137-15-11 this means that i suppose to download that one XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip ?
2- it is possible to unlock the bootloader and root your phone without installing a new recovery? i was reading some post and when you change your recovery or you modify something the OTA update will stop working. they are some methods like the magisk but they seem i little bit too complex for me and i don't want to do it every time that a new update is available.
thanks for the help, and sorry for my English i am from Argentina.

1. yes, but any build will flash and run, so it doesn't really matter that much...
2. Nope. You need to flash TWRP in order to root. This is because the stock recovery will only flash signed images... You can use Magisk, after backing up a stock build. Anytime there is an OTA, just restore to that system image, Flash the original recovery via fastboot, and then take the OTA. Once you have it, flash TWRP again, and restore to your other build. Or just run a custom room like Lineage or RR, and this whole thing isn't really an issue anymore.

Karlinski said:
1. yes, but any build will flash and run, so it doesn't really matter that much...
2. Nope. You need to flash TWRP in order to root. This is because the stock recovery will only flash signed images... You can use Magisk, after backing up a stock build. Anytime there is an OTA, just restore to that system image, Flash the original recovery via fastboot, and then take the OTA. Once you have it, flash TWRP again, and restore to your other build. Or just run a custom room like Lineage or RR, and this whole thing isn't really an issue anymore.
Click to expand...
Click to collapse
yeah i know i had a samsung galaxy s3 until now, and i always have cyanogen, slimrom or now lineage, but this is the first device that i have one that will get updates (at least 1 more :S) and i want to seize that
i will start downloading that file just in case
1- ok so unlocking the bootloader doesn't affect updates only when you modify files? when the update is installing is basically comparing the files that you have with the ones that you suppose to have and if there is something different it will fail? its something like that?
2-dumb question how do you do a full backup in the stock recovery there is no option no do a nandroid backup or it will appear after i just unlock the bootloader?

[Q] XT1768 getting September Security Update

Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?

The way I normally do these type of upgrades is to download the firmware (from here), use fastboot commands to wipe (erase) and flash the needed partitions (everything but data and recovery), boot to TWRP - flash the no-verity-opt-encrypt.zip & root, and then reboot to system - done. It's easy enough for me, but I know some prefer to being able to use a flashable zip in TWRP.
Also, I have to ask - did you get your e4 cheap? It's was replaced by the e5, some other phones seem to be getting replaced like the G6 series (it's gone on clearance at some places), so they can be had cheap.

bast525 said:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
Click to expand...
Click to collapse
Flashing back to stock and taking the updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.

madbat99 said:
Flashing back to stock and taking me updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
Click to expand...
Click to collapse
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.

MotoJunkie01 said:
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
Click to expand...
Click to collapse
This will be for the XT1766, correct? Or will same build work for XT1768 (me thinks not)?

So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?

bast525 said:
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
Click to expand...
Click to collapse
If you're going to slash a firmware package you'll want to wipe everything. Especially data. Make a backup of your data first of course. After you flash TWR P you can try restoring your data and see if everything comes back. but everything in your downloads folder and all of that will be gone once you format data to remove encryption again.