Database Develop

Thinking about lollipop upgrade

im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!

1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app

thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?

Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.

Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.

Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!

Flash custom rom and enjoy lollipop

pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad

anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.

these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.

Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:

2013 Lollipop update didn't work?

[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.

rickathenrystuff said:
[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.
Click to expand...
Click to collapse
If you were part of the MFN soak test, you do acknowledge and agree to flashing back to 100% stock if you are rooted, when you accept entrance into the test.
Not being 100% stock HAS been an issue in the past. That is why this thread -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and its predecessors existed.

.
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.

rickathenrystuff said:
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Click to expand...
Click to collapse
I wasn't aware it was being sent out to anyone but those who were invited by the MFN yet... then again, I haven't been on as often lately and might have missed it.
rickathenrystuff said:
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Click to expand...
Click to collapse
{bold added by me} And that is the biggest issue we've seen... comparing what happened on other phones to the 2013 X...
I see it happen all too often.
And yes, those posts do say you should expect to lose root... but they also discuss the pre-flash validations, and that returning to stock is required.
rickathenrystuff said:
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.
Click to expand...
Click to collapse
Oh, I completely agree.

Should I downgrade my android version?

Hey, I am currently running 6.0.1 as my android version. Just asking but would it be suggested to downgrade the android version? If yes, than too which version?

Why do you want to downgrade?

The Nexus 6 came out with the 5.0, you can't go further back, even with custom roms. Actually I've head somebody trying to build KitKat for the shamu, but I don't know if he succeeded.
Also why would you like to downgrade, anyway?

Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.

Why not upgrading to android 7 instead of downgrading?

php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
Why don't you try upgrading instead? Android 7.0 factory image has just been released.

Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?

php111 said:
Oh, has it been released? Does it causes those boot loop issues on Motorola branded phones just like it does with LG branded? And could I upgrade using the Wugs tool?
Click to expand...
Click to collapse
If you want to flash the factory image then go here: https://developers.google.com/android/nexus/images#shamu
You will find the factory image for 7.0 there and also the instructions on how to flash it. If you are already on stock 6.0.1, you should bee recieving an OTA update soon. But since you say you have reboots and freezes I would take a backup of what every you need onto your computer and then start of fresh from the link above. That way you won't be haunted by old bugs that might be stuck because of previous versions.

php111 said:
Oh as far as why: I had enough with 6.0.1 freezing/slow/crashing on me. Sometimes it even freezes to the point where I cannot turn off the screen for a few minutes at times. I also have enough with the apps freezing or does not work and Chrome sometimes freezes as well.
Click to expand...
Click to collapse
These freezing/slow/crashing issues look very unique to you. Why didn't you try a factory reset, then add your apps back one by one, and look for those that give you trouble. Also are you rooted, do you use xposed or anything that modifies the basic system? Because I'm runnin 6.0.1 myself, and never had the issues you do.

The instructions on the developer page to flash looks too confusing. Well, it jumps right into it when myself I never done it before.

Everybody on this site once knew nothing about Android. Your safest bet is to just wait for the OTA to be offered (or proactively check for it) and accept it. If you're as novice as your posts suggest, I'm guessing that you're running a pure stock device, so you won't run into any problems with the upgrade. And if you do, you know where we are...

Questions about OTA updates, internet connectivity for unlocked Turbo

Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!

If you have TWRP installed, NEVER take an OTA. You will bootloop or brick your phone. Instead just install the TWRP flashable version from this forum.
This is what you would flash, via TWRP if you want the latest firmware while keeping custom TWRP recovery.
[ROM] MCG24.251-5-5 100% Stock
https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
Perhaps re-flashing your modem might help? It's also at that thread. TWRP flashable version.
By popular demand, here are just the modems: https://www.androidfilehost.com/?fid=745425885120733904
Click to expand...
Click to collapse

Ok, thank you ChazzMatt!

birdgofly said:
Ok, thank you ChazzMatt!
Click to expand...
Click to collapse
As for custom ROMs, for you who is not that experienced I would suggest this one:
Computerfreek274_1.0.8 Update Marshmallow 6.0.1 Global,De-bloated,Root,Volte, 5/29/17
https://forum.xda-developers.com/dr.../computerfreek274mm1-0-android-6-0-1-t3503634
It's actually a tweaked, debloated version of Verizon stock Marshmallow firmware. Everything will still work, including Verizon VoLTE (on Verizon, of course, not other networks). Has slight volume boost, battery optimization, etc.
And of course, lots of experienced users are also running that ROM. I do not mean to criticize it in any way, but you just mentioned that you ran some ROM where some stuff didn't work. This is a ROM built on stock, not CM/LOS based. Nothing much has been changed, just bloatware removed and some tweaks.

No worries, that ROM sounds perfect!
Thank you very much for all of your help!!

birdgofly said:
Hello all!
I've been looking around the forum for answers to my questions, but I'm still pretty unsure, and I'm worried about messing up my phone, so if someone could hold my hand a little bit, I would appreciate it so much!
When the marshmallow update came out, I unlocked my bootloader with Sunshine and installed TWRP and rooted. I'm currently on stock 6.0.1 and September 1, 2016 security patch.
Issue #1: Ever since I unlocked/rooted/updated to marshmallow I've had problems with some of my apps deciding they can't connect to the internet, even though WiFi and 4G are clearly connected. Like I'll be able to browse the internet on Chrome just fine, but the Amazon app won't connect.
From what I've read, it seems like a problem a lot of people have had after upgrading to marshmallow, but I'm still worried it's because I'm unlocked or rooted or have Xposed installed or something.
Restarting the phone seems to be the only thing that really makes the apps work again (temporarily). I read somewhere about clearing the cache from recovery and that seemed to have fixed the problem for a couple of months, but lately I've been having the problem again, and clearing the cache isn't helping beyond having to restart my phone to do it.
Issue #2: I've been scared to take the OTA security updates.. I've generally gathered that they won't relock my bootloader, but I'm unclear on if it's ok to take the updates OTA or if I have to download and install them through TWRP.
Also, do I even need those updates? Call me stupid, but I'm not that worried about security (the only thing I own is a massive amount of student debt, go ahead and take it =P). I'm really just hoping the updates fix the internet thing.. is that a possibility?
So overall I guess I'm asking, will taking the updates OTA wreck my stuff, and is there a chance updating will fix my internet connectivity problem?
Or will using a different ROM possibly fix my internet problem? If so, which ROM would you recommend? I used to have a Razr M with the latest (at the time) CM ROM, but I couldn't use Bluetooth and WiFi at the same time, so it kind of left a bad taste in my mouth about custom ROMs...
Any answers or advice would be greatly appreciated!! Thank you!!
Click to expand...
Click to collapse
There's a complete TWRP flashable update to the latest '5-5' firmware. Saves you the time of putting stock recovery back on and taking it OTA. The TWRP flash won't install the stock recovery, TWRP will stay. There's also a zip to clear/reset the radio/modem. You may not need that due to updating the rom.
Sent from my XT1254 using Tapatalk

So just an update for anyone who might come across this thread later.. I ended up flashing the ComputerFreek ROM suggested by ChazzMatt (didn't clean install, just wiped cache). It worked great, and so far I haven't had any more problems with apps not being able to connect!
Thank you to ChazzMatt, ComputerFreek, Einsteindks, and the wonderful XDA community for all your help

Questions about Pie update issues

What I see re the Pie problem on the Lenovo forum is that several people have tried doing a factory reset to fix things. Some seem to think that works, but others say the improvement is only temporary, and the laggy performance returns after a week or two. Would you expect there to be any difference between doing a factory reset versus flashing what is presumably(?) the same rom using the methods found here on XDA? Seems both should put the phone in the exactly the same state.
I'm still on Oreo, and decline the repeated notifications to update. to Pie. And I've turned off automatic system updates in the Developers menu. Does anyone know if that will prevent the Pie update from being forced through? Is there any way to turn off the update notifications?
Is there any indication that Motorola/Lenovo is doing anything to fix this problem? There's a 43-page thread on their forum on this, which they abandoned as "solved" early on. If I could stop the notifications, I would happily stay on Oreo if they would let me do that.
Thanks for any insights or suggestions.

Peabody424 said:
What I see re the Pie problem on the Lenovo forum is that several people have tried doing a factory reset to fix things. Some seem to think that works, but others say the improvement is only temporary, and the laggy performance returns after a week or two. Would you expect there to be any difference between doing a factory reset versus flashing what is presumably(?) the same rom using the methods found here on XDA? Seems both should put the phone in the exactly the same state.
I'm still on Oreo, and decline the repeated notifications to update. to Pie. And I've turned off automatic system updates in the Developers menu. Does anyone know if that will prevent the Pie update from being forced through? Is there any way to turn off the update notifications?
Is there any indication that Motorola/Lenovo is doing anything to fix this problem? There's a 43-page thread on their forum on this, which they abandoned as "solved" early on. If I could stop the notifications, I would happily stay on Oreo if they would let me do that.
Thanks for any insights or suggestions.
Click to expand...
Click to collapse
Hi, Peabody424...
It's always a bit tricky making recommendations to someone, based on one's own experiences, such as with an OTA update, and particularly when there's such a seemingly wide range of reported user experiences, ranging from the good to the bad to the outright atrocious! And like yourself, I'd also read similar (nightmare) accounts over on the Lenovo forums about the Pie update - so I was similarly cautious when I received the notification towards the end of March that a system update for Pie was awaiting my confirmation to go ahead and install it.
One of the major issues I'd read about Pie, was people's inability to access their device after the update, due to their password/lock-screen pattern not being recognised. And the only solution was to perform a factory reset via the stock recovery - not a good result at all!
This was obviously a significant concern to me, along with other reports of sluggish and poor screen responsiveness, with various solutions being proffered, such as using a custom launcher - I use Nova Prime anyway, so I've never actually used the stock Moto Launcher - and disabling Motorola's own background data collection processes (Android Settings>>System>>Advanced>>
Motorola privacy>>[DISABLE EVERYTHING THERE]), apparently is also reported to have helped make the device more responsive.
Anyhow, I'd prepared in advance of Pie, by ensuring everything on my device was backed up somewhere else, should I need to perform a factory reset in the event of possible problems after the Pie update.
So... after about an hour of downloading and installing Pie... Everything worked perfectly - in fact, Pie managed to resolve some long standing screen glitches I'd been having with Oreo, ever since I bought my G6 back in July of 2018.
Since the March 2019 Pie update, I've subsequently received two further OTA updates - in August and September.
The one in August was a security patch update for 1 June 2019, but it also included Google's Digital Wellbeing App, which for some strange reason had been omitted in the original Pie update back in March. Although this OTA update installed without any noticeable problems, I decided immediately afterwards to perform a factory reset... It just seemed a prudent measure to take - to clear the decks, so to speak, and begin afresh with a clean slate.
---------------------------------------
Here's a list of my Pie/Security patch updates, so far this year...
(Yeah, I know... I'm a bit OCD, keeping a detailed record of such things)
Moto G6 OTA (PPS29.55-24) Android 9.0 Pie Update (from Android 8.0 Oreo) with 1st January security patch. Notified: 01:05, Tue 24 Mar 2019. Downloaded: 01:43 to 02:02 (17 mins to download 1431.2Mb). Commenced installation at 02:02; Completed at 02:37 with no problems.
Moto G6 OTA (PPS29.55-37-4) with 1st June security patch. Notified: 21:41, Mon 5th Aug 2019. Downloaded: 21:42 to 21:54 (12 mins to download 818.6Mb). Commenced installation at 22:00; Completed at 22:28 with no problems.
Performed a factory reset after this OTA, just to clear the decks and begin afresh.
Moto G6 OTA (PPSS29.55-37-4-3) with 1st August security patch. Notified: 04:15, Thu 12th Sept 2019. Downloaded: 04:17 to 04:20 (3 mins to download 155.4Mb). Commenced installation at 04:20; Completed at 04:46 with no problems.
---------------------------------------
In conclusion then, I'm afraid I cannot give any assurances that the Pie update will NOT give you any problems - there are no guarantees here, unfortunately, and whilst my Moto G6 has been improved with Pie, there's no denying that there have been many reports of Pie OTA related problems with this device. I would strongly recommend that if you do take the Pie update, prepare for a possible factory reset, by ensuring everything in the internal storage that is important, is safely backed up elsewhere first.
With regards to possibly reflashing the G6,
maybe back to Oreo, I'm afraid I can't help or advise you there. I haven't reflashed or rooted a device for about two years now - the benefits of doing so seem to me to be fairly marginal these days - so my knowledge about such things is a little out of date. My own Moto G6 will likely be my first device who's bootloader will probably never be unlocked.
As far as Lenovo fixing anything... Well, I wouldn't put money on it! They don't seem to be overly concerned with the kind of problems that I've seen reported on their forums.
---------------------------------------
Apologies for my somewhat non-committal response to your implied question ("Should I update to Pie?"), but as I mentioned at the beginning, my own experiences of Pie may not be reflected by others. Indeed, when reading through the posts on the Lenovo forums about Pie, a few months ago, I was very surprised by the largely negative response that the Pie OTA had engendered, and when the time came for me to update to it, I was even more surprised when everything went perfectly, with none of the problems that had been reported there.
All I can say then, is that Android 9.0 Pie on my Moto G6 has been problem free, and is an improvement over its predecessor, Android 8.0 Oreo.
Hope this helps - and apologies for this rather long post - I do go on a bit sometimes
Kind Rgrds,
Ged.

Thanks very much, Ged. I really appreciate the info on your experience with the Pie update. I guess my first reaction is that you are in the UK, and the updates you received may or may not be at all similar to what's being offered to me in the US (PPS29.118.11.1 to update to Pie). One of the missing pieces of information is whether the problems are only with US phones, or even within the US, what percentage of phones have these problems.
I still wonder about the idea of flashing the latest rom from the archive here. I don't understand how/why that would be different from allowing the OTA update, then doing a factory reset. The latter process has been reported as providing only temporary benefits. And of course I would also like to find a way to turn off the update notifications.

Peabody424 said:
Thanks very much, Ged. I really appreciate the info on your experience with the Pie update. I guess my first reaction is that you are in the UK, and the updates you received may or may not be at all similar to what's being offered to me in the US (PPS29.118.11.1 to update to Pie). One of the missing pieces of information is whether the problems are only with US phones, or even within the US, what percentage of phones have these problems.
I still wonder about the idea of flashing the latest rom from the archive here. I don't understand how/why that would be different from allowing the OTA update, then doing a factory reset. The latter process has been reported as providing only temporary benefits. And of course I would also like to find a way to turn off the update notifications.
Click to expand...
Click to collapse
Hi again, Peabody424...
Appreciate your kind works, and yep, you're correct in your deduction that I'm in the UK. I should have mentioned that in my prior post... My Moto G6 update channel is retgb.
Personally, I would be very hesitant to flash anything, from any archive. I used to flash stuff, frequently, on previous devices, some years ago. But it seems to me, reading here on these Moto G6 forums, that such things have become ever more complicated in recent years, and potentially prone to error, and possibly a device hardbrick.
It's not something you should do lightly, and not without a considerable amount of reading and research beforehand. Now, maybe I'm being a little over cautious, and some longstanding Moto G6 flashing expert will post saying so... But I'd rather be cautious and have a device that works with Oreo, rather than one that doesn't (maybe permanently) with an attempted failed flash of Pie. Or maybe I'm just getting old, and don't much care for the risks anymore...
--------------------------------
Regarding disabling OTA updates... I'm fairly certain you need root for that.
However... If you look in Android Settings>>Apps & notifications>>Advanced>>See all apps, then tap on the 3 dot overflow menu at the upper right hand corner of the screen, and select Show System... then scroll down to locate an app called Motorola Update Services. Tap to enter, and you'll notice that whilst it can be forced-stopped, the disable button is greyed-out, and is thus not available.
But you COULD disable it's notifications as illustrated in my screenshot below... Not sure if that would work in the long term, 'cos the update would still be pending, you just wouldn't be being notified of it - and maybe the update would/might proceed anyway, at some point - I'm just not sure, to be honest.
Hope this helps, and good luck, whatever you choose to do
Rgrds,
Ged.

Thanks, but I turned off notifications for Motorola Update Services in the beginning, and the system update notifications still come through. I suspect it's not possible to turn them off without disabling the Update app.

Peabody424 said:
Thanks, but I turned off notifications for Motorola Update Services in the beginning, and the system update notifications still come through. I suspect it's not possible to turn them off without disabling the Update app.
Click to expand...
Click to collapse
Hi Peabody,
I also saw your post in the other thread, so here is my $.02. I have a US retail unlocked phone that is running PPS29.118-15-11. I updated from 8.0 (OPSS27.104-92-6) to Pie with the PPS29.118-11-1 OTA. My experience was different from GedBlake in that the update almost immediately showed signs of lagginess. For me it seemed that anytime the phone tried to access anything from the network in the background, it would lag the foreground. I uninstalled stuff, played with settings, even reset to factory, to no avail. Then someone recommended that I use RSD Lite to reflash PPS29.118-11-1. The difference is, that unlike the OTA, RSD Lite wiped the phone entirely and gave me a fresh starting point. Why a factory reset did not obtain the same state, I have no idea. But what I can tell you is that my G6 ran like glass after that. I got nervous when I got the notification to update to PPS29.118-15-11 OTA, but I bite the bullet and the upgrade went fine and it still runs like a champ.
-Chris

First to say is to disable the update notification you have to freeze Motorola-Updateservices (com.motorola.ccc.ota)
Code:
pm disable com.motorola.ccc.ota
---------------------------------------------------------------
To Ged Blake:
If your password/lock-screen pattern is not being recognised, you should erase locksttings.db in /data/system via adb/TWRP. It resets your lockscreen pattern and you can access your device.
--------------------------------------------------------------
If you update to Pie you can't downgrade to Oreo without losing your Wifi signal!!!

WoKoschekk said:
First to say is to disable the update notification you have to freeze Motorola-Updateservices (com.motorola.ccc.ota)
---------------------------------------------------------------
To Ged Blake:
If your password/lock-screen pattern is not being recognised, you should erase locksttings.db in /data/system via adb/TWRP. It resets your lockscreen pattern and you can access your device.
--------------------------------------------------------------
If you update to Pie you can't downgrade to Oreo without losing your Wifi signal!!!
Click to expand...
Click to collapse
Hi, WoKoschekk...
Yeah, the password/lockscreen problem was just something I'd read about over on the Lenovo Motorola forums - it was never a problem for me. And your solution of using TWRP, whilst useful to know, likely wouldn't have helped most of the posters there, as most, if not all, are running bootloader locked devices with no TWRP installed. I seem to recall that running unmodified factory stock is a condition of posting there, if you expect a response from a Motorola Service Agent, which I suppose is understandable.
Your solution of disabling Motorola's OTA update app using ADB is something that occurred to me too, but I'm not too enthusiastic about recommending procedures that I've not tried myself... I didn't want to suggest something that might have screwed up the OP's device, however unlikely that may be.
Anyhow, @Peabody424...
This article may be worth reading for more details in how to disable/freeze the OTA app, as suggested by WoKoschekk...
https://www.xda-developers.com/disable-system-app-bloatware-android
Rgrds,
Ged.

You won't have any negative effects by disabling this app. Since it's not possible to deactivate it this might be the only way to turn off the notifications permanently. You can enable the app when ever you want it.

Thanks very much for the responses.
In years past, I have flashed new rom to an old Hisense tablet, but that was a high-anxiety process since I was a total newbie. I'm still basically a civilian here, but understand that it's not entirely impossible that I would be able to do these things successfully. But just so I understand:
Using ADB to disable the update app would (probably) stop the notifications and prevent Motorola from forcing through the update to Pie. But it is not rooting, is reversible, and (if reversed) wouldn't void my warranty. Right?
Using RSD Lite does root the phone, which is not reversible, and does void my warranty. (The rom is factory stock, but you can't un-root.) Also, it's not possible to revert to Oreo after flashing Pie. Right?
Edit: It looks like I was wrong about not being able to un-root. A Youtube video by RootJunkie suggests using RSD Lite restores the phone to stock in every way, and it would become unrooted. So no warranty issues?
Chris, your experience with RSD is really encouraging. From what you said, you did try a factory reset after the OTA update, and it was not successful. But the RSD re-flash of the same rom did work, and continues to work. I just wish I understood why the reset didn't work but RSD did. Anyway, there are now several more updates after 29.118.11.1. Should I let the 11.1 OTA happen, then do RSD LIte, or just do RSD Lite from the existing Oreo, or do RSD Lite from Oreo to the latest rom? I guess we don't know whether any of that matters.
I tried to download RSD Lite from rsdlite.com, but got a 404. Is it available directly from Motorola? Also, I have a Win7/64 computer and an XP computer. Does it matter which one I use for RSD Lite?
Thanks again for everyone's suggestions.

A new post appeared today on the Lenovo forum:
"I did a factory reset on the first of September (2019-09-01). The phone is now back to how it was: lagging, freezing, slow to open apps, slow keyboard, Chrome is laggy and pops up with "app is not responding" prompt.
For me, the factory reset fix lasted a little over a month before the phone got bogged down again."
Chris, I think you did the RSD Lite flash a month earlier than this guy did the factory reset. Have you seen no deterioration in performance? I'm sorry to be so goosey about this, but I don't understand why the RSD Lite flash should leave the phone in a different state than a factory reset of the OTA update, and I just dread doing the Pie flash only to get the same result as the other guy got a month later - as I understand it, I wouldn't be able to go back to Oreo.

Peabody424 said:
Thanks, but I turned off notifications for Motorola Update Services in the beginning, and the system update notifications still come through. I suspect it's not possible to turn them off without disabling the Update app.
Click to expand...
Click to collapse
Peabody424 said:
A new post appeared today on the Lenovo forum:
"I did a factory reset on the first of September (2019-09-01). The phone is now back to how it was: lagging, freezing, slow to open apps, slow keyboard, Chrome is laggy and pops up with "app is not responding" prompt.
For me, the factory reset fix lasted a little over a month before the phone got bogged down again."
Chris, I think you did the RSD Lite flash a month earlier than this guy did the factory reset. Have you seen no deterioration in performance? I'm sorry to be so goosey about this, but I don't understand why the RSD Lite flash should leave the phone in a different state than a factory reset of the OTA update, and I just dread doing the Pie flash only to get the same result as the other guy got a month later - as I understand it, I wouldn't be able to go back to Oreo.
Click to expand...
Click to collapse
I do see slow downs in the phone from time to time, but these can be and usually are explained by external forces, such as wifi strength, and lack of cell service. That said, these are nothing like the lag I experienced after the first OTA to Pie. BTW - RSD Lite does not root the phone, it is only a tool used to flash images to the phone. So if you are flashing an official image, you are not voiding the warranty. Historically, I've been a big fan of rooting phones, however with the G6, I simply haven't found a good enough reason to do it yet. Here is a link for RSD Lite - http://download.canadiancontent.net/RSDLite.html - I used this and downloaded version 6.2.4. I ran it on Windows 10, and ran into a issue with the USB 3.0 port I was connected too. I had to switch to an older port - luckily my system still has a few. I would suggest using the Windows 7 system you have.
-Chris

cdaly1970 said:
I do see slow downs in the phone from time to time, but these can be and usually are explained by external forces, such as wifi strength, and lack of cell service. That said, these are nothing like the lag I experienced after the first OTA to Pie. BTW - RSD Lite does not root the phone, it is only a tool used to flash images to the phone. So if you are flashing an official image, you are not voiding the warranty. Historically, I've been a big fan of rooting phones, however with the G6, I simply haven't found a good enough reason to do it yet. Here is a link for RSD Lite - http://download.canadiancontent.net/RSDLite.html - I used this and downloaded version 6.2.4. I ran it on Windows 10, and ran into a issue with the USB 3.0 port I was connected too. I had to switch to an older port - luckily my system still has a few. I would suggest using the Windows 7 system you have.
-Chris
Click to expand...
Click to collapse
I believe you said in the other thread that you did do a factory reset after the original OTA update, but found that it didn't fix things. If that's the case, then it seems pretty clear that the RSD Lite flash leaves the phone in a different state than the factory reset, although nobody knows why that would be the case since the rom is presumably the same either way.
Thanks for the clarification on rooting. The only reason I would need to root the phone is to be able to hide certain pictures and apps, but I may be able to do that without rooting.
So I have both the 11-1 and 15-11 roms and RSD Lite, and I have the v6.4.0 drivers although I don't think I need them since Win7 already communicates with the G6. If I can muster up the courage, I'll go ahead and give it a try, probably with the 15-11 rom.
A couple more questions: I don't have an SD card installed, but what about the SIM? Is it ok to leave it in the phone when doing RSD Lite? And do I need to set any Developer options, like USB debugging?
Thanks very much for your help on this.

GedBlake said:
Anyhow, @Peabody424...
This article may be worth reading for more details in how to disable/freeze the OTA app, as suggested by WoKoschekk...
https://www.xda-developers.com/disable-system-app-bloatware-android
Rgrds,
Ged.
Click to expand...
Click to collapse
I decided to try this, disabling com.motorola.ccc.ota for user zero as described in that article. And it appears to have worked. Well, normally I would have received the Pie OTA notification immediately on power-up, and after 20 minutes now it hasn't arrived. So while it may be a bit early to count chickens, I'm encouraged. If I decide at the last minute not to risk upgrading to Pie, maybe at least I can continue to run Oreo in peace.
When I go to Settings/Apps&Notifications/AppInfo/ShowSystem/Motorola Update Services, it shows "Not installed for this user". I think that's a good sign.
I did have to install the Motorola ADB driver for this to work. The article doesn't mention that, but I guess it would be obvious to anyone but me.

A question has come up in the Lenovo forum thread as to whether it is necessary to unlock the bootloader in order to run RSD Lite on newer phones like the G6. Chris, or anyone else who knows, can you clarify this? My understanding is that the whole point of RSD Lite was to restore a phone to factory condition, and that flashing stock roms signed by Motorola permitted them to be flashed without unlocking or rooting or anything else.

JimmiH on the Lenovo forum has found "Lenovo Moto Smart Assistant", a new utility from Motorola, which is installed on your PC (Win 7 or 10). Included in the utility is a "rescue" function which appears to do the same thing as RSD Lite - resurrect a phone from any software issues. It downloads the correct official rom and reflashes it to the phone. JimmiH will be reporting back over the next few weeks as to whether the rescue has permanently solved his Pie lagginess issues.
The advantage of this LMSA over RSD Lite is that it runs on Windows 10, and presumably works with USB3 ports, while apparently neither was the case with RSD Lite. And of course you don't have to go hunting for the right rom.
This could potentially be a nice easy fix. Let's hope so.

Curious as to the results of the the "Lenovo Moto Smart Assistant" reflashing method on moto G6. Has anyone had sustained success using this method?
I factory reset my phone in an attempt to cure the Pie lagginess, and had limited success - as other users describe there was a joyful month without lag, then a return to lag over the following months. Within two months you will be back to the same state of constant lag.
I am preparing to move to a Google Pixel 3a but wanted to give the G6 one last chance. I will be attempting the LMSA fix and hope to report back within a few months if this solution is permanent.