Database Users

official update after root - possible?

hi all. Maybe is a stupid questions but I want to know if I root my phone do I will get any official update? (see attachment)

No, you wont be able to get the over-the-air updates anymore if you root.
However, if you flash a custom rom like cyanogenmod the devs usualy incorporate the ota update into their roms. So either way you'd still get the patches

so that mean in order to get the updates over-the-air, i have to role back to unroot nandroid backup, do the updates, than root again.. is that correct?

I thought I read in a recent thread that if you rooted, but kept the stock Tom
You would still get OTA update. Can anyone clarify?

if you have stock bootloader and stock rom but are rooted you will still receive OTA updates, if you flash amons boodloader, and custom roms you will not receive updates.
just remeber that once you update you will lose root and will have to re-apply the root, when it has been released. for that update!

No i mean flash a custom rom (like cyanogenmod) and each time there is an OTA update cyanogen will patch it to his rom. So pretty much flash a custom rom and keep it updated because they will include any OTA updates that are out already

r8zer said:
if you have stock bootloader and stock rom but are rooted you will still receive OTA updates, if you flash amons boodloader, and custom roms you will not receive updates.
just remeber that once you update you will lose root and will have to re-apply the root, when it has been released. for that update!
Click to expand...
Click to collapse
ok, so, can you give me one root information, in order to keep my updates over the air, please?

what do you mean give you one root information, if u unlock bootloader, via fastboot, then use pauls root over at modaco, u will still have stock boot loader and custom rom, all root does is give u superuser, as long as you do not flash a custom recovery or custom rom you will be fine.

r8zer said:
what do you mean give you one root information, if u unlock bootloader, via fastboot, then use pauls root over at modaco, u will still have stock boot loader and custom rom, all root does is give u superuser, as long as you do not flash a custom recovery or custom rom you will be fine.
Click to expand...
Click to collapse
take a look at my fist post: I unlock bootloader via fastboot, I applied root but I did not used Paul root, and also I don't have a custom rom. I have the attachment on top of the page..... everybody get me confused.... can somebody clarified me?

all you show in top post is a pic of the update 1, ERE 27 which to date is the newest one google has released,
right, u got stock bootloader and stock rom, but u r rooted u will still get OTA updates as only custom roms block OTA updates!.

r8zer said:
all you show in top post is a pic of the update 1, ERE 27 which to date is the newest one google has released,
right, u got stock bootloader and stock rom, but u r rooted u will still get OTA updates as only custom roms block OTA updates!.
Click to expand...
Click to collapse
which means 'm still able to get OTA updates, correct?

This conversation was very frustrating to read.
Yes you will get OTA updates, but you will get the same updates much sooner by using Cyanogen's ROM.
I have no idea what motivation you would have to root your N1 and void the warranty if you are just going to get OTA updates and not take advantage of any of the benefits that root enables... (The most desirable of which is a custom recovery allowing the application of a custom ROM)

Diceman4 said:
This conversation was very frustrating to read.
Yes you will get OTA updates, but you will get the same updates much sooner by using Cyanogen's ROM.
I have no idea what motivation you would have to root your N1 and void the warranty if you are just going to get OTA updates and not take advantage of any of the benefits that root enables... (The most desirable of which is a custom recovery allowing the application of a custom ROM)
Click to expand...
Click to collapse
I feel sorry if these conversation it becomes frustrating, but look my reason:
1. no warranty, in my country is not available yet, it sales on black market
2. before to root, I did not made a nandroid backup, I done after root
3. I'm running Alpha 10 Desire Rom for N1, and I want to make sure if I'm going to roll back to my nandroid backup, I will be able to get OTA updates
one more time I do apologize.

WARNING: Android 5.0 Bootloader and KitKat Compatibility

Android 5.0 (Lollipop) Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.​
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.​Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.

That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.

You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.

nice info

lost101 said:
Android 5.0 Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.

juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!

Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:

As always, very informative thread @lost101.

lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules

MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.

Is stock recovery and stock firmware same? If not how do i get stock recovery back?

S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039

Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884

[Discussion] Moto G XT1032 - GPE Converted Lollipop

So yeah, I've successfully converted my XT1032 to GPE and updated it to Lollipop. In fact I didn't have to spend a lot of time in Fastboot as a lot of those guides out there would have you do. Just flashed the 4.4.4 GPE and then once it loaded it asked if I wanted to upgrade. So I don't know about other XT1032 users but I thought it was fairly painless.
One thing of note if your planning to root, this is the method I did it. http://autoroot.chainfire.eu/. Now just so you know that list doesn't have the new Lollipop versions I used Google and to find the post with them. Just make sure you turn off, "Mount namespace separation". I found it was giving me some trouble. I also ended up installing SuperUser into /system and after that my root issue disappeared.
During the whole thing I had my SIM out (I have to pay for data, I'm with Koodo Mobile). Once it was done installing the updates (software and everything) I put it back in and the phone asked to reboot. Everything seems to be working and I turned data off so I wouldn't use it.
Anyone else with a XT1032, having any difficulties with this?

akasaka said:
In fact I didn't have to spend a lot of time in Fastboot as a lot of those guides out there would have you do. Just flashed the 4.4.4 GPE and then once it loaded it asked if I wanted to upgrade. So I don't know about other XT1032 users but I thought it was fairly painless.
Click to expand...
Click to collapse
So, u might now want to explain a li'l?
How/What did u flash GPe 4.4.4? The complete firmware image, using fastboot? As in this thread [http://forum.xda-developers.com/showthread.php?p=47820707]??
And then, u say it asked to update.. So, u got the official OTA, on a converted device??

prakharkmr27 said:
So, u might now want to explain a li'l?
How/What did u flash GPe 4.4.4? The complete firmware image, using fastboot? As in this thread [http://forum.xda-developers.com/showthread.php?p=47820707]??
And then, u say it asked to update.. So, u got the official OTA, on a converted device??
Click to expand...
Click to collapse
If you convert your XT1032 to GPe it practically becomes the GPe device. Regular XT1032 and GPe are identical,just the software is different. And you can convert GPe to regular XT1032 also.

Hey OP do you have a link to the stock firmware file that you used to flash the 4.4.4 GPE ROM?
---------- Post added at 04:51 PM ---------- Previous post was at 03:59 PM ----------
I just installed this 4.4.4 GPE firmware on my XT1032:
https://mega.co.nz/#!lUJCFICJ!19k6_7Zsd5_FB47ydrs2ECHF6wWOEd1oUlEmvr_p75Y
I was not offered the OTA update to Lollipop. Also, when I flashed the firmware using mfastboot, it said "failed" for the GPT partition.

prakharkmr27 said:
So, u might now want to explain a li'l?
How/What did u flash GPe 4.4.4?
Click to expand...
Click to collapse
+1. Just want to know if there is a less painful way to do it. I guess, unlocked bootloader is needed for sure. Also, there is Motorola All-in-one tool which can convert Moto G to GPE. Anyone knows if this is safe?

Guys, you should be very careful doing this. It appears that the GPE and the Retail US 4.4.4 firmwares each have a different bootloader, which is why it failed for me when I tried to flash the GPT.bin partition. I'm pretty sure that if you get this error and then try to install the OTA you will brick your phone.
Someone claims to have solved this issue, but I would not trust it until it has been verified by more people.
http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842

so, dear @akasaka plz reply!!

How is battery life compare to CM12 ?

Sorry Guys,
Hey let me get back to you. Making food. (Like half hourish)

I'm used the Stock for GPE 4.4.4. The file name is (GPE_XT1032_KTU84P.M003_CFC.xml.zip). I believe it's the same as the link SickBeast posted above. As for battery life, like I mentioned I went to bed so I just work up with a full charge but here is the battery usage so far. I'll post another later.
Update: Also I just used adb & mfastboot do it all. Didn't use any other software.

What ROM were you on before flashing the 4.4.4 GPE firmware? Did you get an error when flashing the GPT.bin partition?

Wasn't using a ROM. I have in the past but I was on my stock firmware hoping that OTA would be coming in a couple of days for Koodo but then I decided not to wait and no errors. Just warnings when it came to the system images but it all flash successfully.

akasaka said:
Wasn't using a ROM. I have in the past but I was on my stock firmware hoping that OTA would be coming in a couple of days for Koodo but then I decided not to wait.
Click to expand...
Click to collapse
That's probably why you did not have a problem then. You had the older bootloader which you were able to upgrade using the 4.4.4 GPE ROM. I had flashed the 4.4.4 Retail US ROM which has a newer bootloader than the 4.4.4 GPE ROM. There is probably a way to downgrade but I'm staying with the retail ROM until an OTA or a full GPE 5.0.1 image is released.
Thanks for the info though, it's good to know that this type of upgrade worked for you. I hope you are enjoying Lollipop.

I am. One thing of note... Netflix finally works on Lollipop!

Can I convert to GPe (4.4.4) my XT 1032 with Android 4.4.4 Stock ROM ?

As some one mentioned. XT1032 uses the same hardware as GPE and vice versus. Only thing I'd watch out for is what SickBeast said is if your using the US 4.4.4 bootloader.

Eurofighter_ty said:
Can I convert to GPe (4.4.4) my XT 1032 with Android 4.4.4 Stock ROM ?
Click to expand...
Click to collapse
As I have explained, you will have an error flashing the GPT.bin partition, which I believe will cause you to brick your phone when you install the OTA update to Lollipop. We need someone to figure out how to fix this for us. Read this thread, I linked to another thread where someone claims to have solved a similar problem.
IMO it's not safe to do this type of update to Lollipop yet. We need a factory image. IMO you should be patient and do it that way. We should probably have an image within a week or so.

Ok, then I will wait. Thanks for your reply

You're welcome.

akasaka said:
So yeah, I've successfully converted my XT1032 to GPE and updated it to Lollipop. In fact I didn't have to spend a lot of time in Fastboot as a lot of those guides out there would have you do. Just flashed the 4.4.4 GPE and then once it loaded it asked if I wanted to upgrade. So I don't know about other XT1032 users but I thought it was fairly painless.
One thing of note if your planning to root, this is the method I did it. http://autoroot.chainfire.eu/. Now just so you know that list doesn't have the new Lollipop versions I used Google and to find the post with them. Just make sure you turn off, "Mount namespace separation". I found it was giving me some trouble. I also ended up installing SuperUser into /system and after that my root issue disappeared.
During the whole thing I had my SIM out (I have to pay for data, I'm with Koodo Mobile). Once it was done installing the updates (software and everything) I put it back in and the phone asked to reboot. Everything seems to be working and I turned data off so I wouldn't use it.
Anyone else with a XT1032, having any difficulties with this?
Click to expand...
Click to collapse
So that simple you got root?? because i really want to get lollipop but i need a lot some root apps on my work
en

Bricking by OTA update after re-flashing stock ROM

I've read many posts that if we, re - flash the stock ROM, and then perform an OTA update, then it might brick the device, due to the bootloader incompatibility.
So, here I'm not sure, what type of bricking(soft brick or hard brick).
And, can someone explain in detail, what's actually happens, in this case?
As in, if I install a custom ROM, and then reflash the stock ROM, and perform an OTA update, would it brick the device?
~ Thanks

Nope, you won't. Custom roms don't touch the bootloader.
Sent from my Moto G⁴ Plus using Tapatalk

Silesh.Nair said:
Nope, you won't. Custom roms don't touch the bootloader.
Click to expand...
Click to collapse
Okay,
my confusion is, what if I manually flash an old bootloader(not sure if the version of the bootloader changes with the official updates) , while flashing an older stock ROM, and then I update that old stock ROM installation, via OTA update, does it brick the device?
And if it doesn't, what are the other circumstances, wherein official OTA updates can brick the device.

You cannot flash an old bootloader over a new one. It will error out.
Sent from my Moto G (4) using Tapatalk

Silesh.Nair said:
You cannot flash an old bootloader over a new one. It will error out.
Click to expand...
Click to collapse
Okay, so it means basically an official update can never brick the device.
Thanks for clearing it

OTA update when rooted

My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.

mongoose96 said:
My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.
Click to expand...
Click to collapse
You must be PURE stock to take an OTA update, or it will fail and bootloop... Flash a rom if you wish.

What i did was make a back up of everything just incase and then look up the ota version on your phone and get it in the rom section and look up twrp flashable OTAs and just flash it. you might lose root but its easy to get back if you flash magisk again.

You can found the right guide here:
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

does anyone have fastboot stock rom?

siddhesh9146 said:
does anyone have fastboot stock rom?
Click to expand...
Click to collapse
Of the current version? lol, no, we wish... we are averaging 3-6 months behind OTA releases for full ROM images, if we get them at all. Moto does not officially provide them, so they have to be leaked somehow, and sources are completely dried up yet, but it's getting there. :/

Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.

mortadelax said:
Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.
Click to expand...
Click to collapse
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?

mortadelax said:
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?
Click to expand...
Click to collapse
Oreo ist absolutely fine, no problems with it.
I haven't heard of any issues like increased battery drain, for me nothing changed at all regarding battery and the rest is also working flawlessly.
It would be a lot of action to unlock and root the device just to stop the updater service.
If you don't have any other plans that need root privileges I recommend just taking the OTA (s).
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Click to expand...
Click to collapse
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?

mortadelax said:
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?
Click to expand...
Click to collapse
Yes I am.
Just check some of the custom ROM threads, there are some that need stock Nougat as base but the most of them need Oreo. For custom ROMs there are no up/downgrading problems, that's only the case for stock firmwares.
And as said above, there are TWRP flashable stock builds that doesn't have these problems too and will bring you to whatever stock firmware you want, not just pseudo. (Here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482 )
So if you're on stock Oreo after unlocking the bootloader and flashing TWRP all options are open for you. Just don't forget to make a full nandroid backup incl. EFS and persist before you flash anything.
Sent from my Moto G5 Plus using XDA Labs