Related
So Blu finally released the Marshmallow update for the Vivo XL... and it kind of sucks. It's only 6.0 and not 6.0.1. The Gionee model of this phone has been running 6.0.1 since June. Updating via the OTA was a nightmare. It failed 3 times before it finally worked. Then I performed a factory reset, as always when performing a major update. It seems that you cannot format the memory card to use it as internal storage. It gives you the option but it ALWAYS fails. Also, the battery life blows. I lost 20% battery overnight while the phone was inactive and supposed to be dozing. Very disappointing so far. Anyone else have any problems?
My update failed several times but that was about he only problems I've faced. After a factory reset everything seems to be working fine. I am able to use my micro SD as internal as well. No other problems at all with what you mentioned. Everything seems to run smoother than it did on lollipop (but that could be as a result of the factory reset).
I'd love the upgrade if it didn't break compatibility with one crucial app. Until the issue of false root positives is addressed, I'm sticking to lollipop.
my wife's phone updated first try, didn't even feel the need to factory reset it after it came up, so far buttery smooth and better battery life, i think like 1 % over night sitting there and moderate use she got a few days out of her phone. so far i'm happy
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
weatherdude35 said:
My Vivo XL updated with no problems. However, i have noticed that it runs slower than before when viewing Netflix or listening to music, even though i only have 2 or 3 other apps opened at the same time. I usually have to free up more RAM to get it to work properly but i never had this problem when the phone was running Lollipop. Can be irritating at times because even some websites will lag or typing text messages can be slow because the lag time is ridiculous.
Click to expand...
Click to collapse
Back up your things and try a factory reset. Had the same problems but this fixed it.
This was a good updated for me
WiddleyScudds said:
This was a good updated for me
Click to expand...
Click to collapse
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
xphyle1971 said:
Yeah. I'm the OP. After a couple days, the update settled in. Battery life went back to normal, which is to say, stellar. So basically, all good here.
Click to expand...
Click to collapse
Extreme mode is also impressive don't know if you've seen it. Do you know if there is root yet? I've attempted king root but it fails and I don't want to brick this phone trying to F with other methods
I'm also running 6.0 and it seems to be working great. Much smoother and better battery life. Does anyone know of a method to root the Vivo XL running 6.0 yet?
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
I also have this issue. probably because of being rooted. However even I restored original ROM backup and original recovery, I still got such information and cannot do OTA update.
it works correctly , the system is smooth and everything is fine , maybe You a have a rooted device try reflashing and redownload the update
adaeda said:
Good afternoon guys, I have a problem, to update mi Blu vivo XL to Marshmallow the official BLU site says that my version number should be : BLU_V0030UU_V10. I am a little confused about this version number. That is the number in the Wireless update? I have this Current number in Wireless update BLU_V0030UU_V07_GENERIC_5.1_20160126-1033, but when I have tried to check for updates I can't install nothing, this message appears " Your system was damaged, wireless update is disabled". I don't know what to do, I can't install the update via Wireless update, Is there any other method like manually transfer a file? If it is possible, where can I find the file and what is the file name?
Click to expand...
Click to collapse
Same here, my android 6.0 version was v07. Oddly enough, the first OTA update is v10. But then the next OTA update took the label back to V07. I reverted back to android 5.1 stock rom, since that was the only way I could get TWRP to load.
How can I go back to the lollipop update ???
Pls I need you guys to help me
I'm using BLU vivo XL, I flashed my phone through stock recovery and I wiped cache & format the phone then rebooted the phone, ever since then its been writing invalid imei, I checked the baseband and it's not showing anymore, I've tried to fix this but no way, I later downloaded the stock ROM and reflashed the phone still its showing invalid imei, I wanted to download Gionee S plus stock firmware but dunno if it's gonna fix the problem, pls I need guys to guide me on how best to fix this issue, its been two weeks + now, God bless.
someone share marshmallow for vivo xl (blu vivo xl v0030uu)
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
Hello, I have seen a mixed bag of opinions about Oreo, some saying is excellent, others stating that only marginal improvements, and, a bunch reporting problems af all kinds, even regretting that they updated, many did not receive Ota, but installed the firmware via Odin, I would really like to hear about your experiences about OTA Oreo, in Mexico oreo is not yet available, and maybe I would not accept it, depending on your opinions, but only about OTA Oreo, thanks in advance for your useful inputs
So, you already heard a lot of opinions, but now you want to hear even more opinions. Interesting !
Many have downgraded. So, once you get it and if you don't like it...
I like it. No problems. Few changes in phone settings. Slightly better battery.
Sent from my Galaxy Note 8 using XDA Labs
It's been great. No issues and very good performance.
Dejan Sathanas said:
So, you already heard a lot of opinions, but now you want to hear even more opinions. Interesting !
Many have downgraded. So, once you get it and if you don't like it...
I like it. No problems. Few changes in phone settings. Slightly better battery.
Sent from my Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Yes, because in most cases the opinions I read do not tell how oreo was installed, that is why I ask to those who received OTA
You should just update for the security, if nothing else. I flashed Oreo via Odin, once booted I factory reset. 0 problems for me. Feels snappier for sure.
winol said:
Yes, because in most cases the opinions I read does not tell how oreo was installed, that is why I ask to those who received OTA
Click to expand...
Click to collapse
Do you think it matters how you install it ? I think it doesn't matter. If you install it either way and then do a factory reset, which in my opinion is a must, you're good to go. But that's just my opinion.
Sent from my Galaxy Note 8 using XDA Labs
stonedpsycho said:
You should just update for the security, if nothing else. I flashed Oreo via Odin, once booted I factory reset. 0 problems for me. Feels snappier for sure.
Click to expand...
Click to collapse
So, you recommend to hard reset after the OTA?, This would be the first time I update via OTA, As I rooted all my devices before this one
winol said:
So, you recommend to hard reset after the OTA?, This would be the first time I update via OTA, As I rooted all my devices before this one
Click to expand...
Click to collapse
It is just something I have always done. The amount of times I have seen a bug or issues fixed by a factory reset, sod setting the phone up, get all your apps on then find a bug. I am sure it would be fine by OTA but if that fails you always have Odin as a backup. Even if you decide you do not like it you can go back to N.
If you are rooted and have custom recovery the OTA will fail anyway. If so just flash with Odin.
stonedpsycho said:
It is just something I have always done. The amount of times I have seen a bug or issues fixed by a factory reset, sod setting the phone up, get all your apps on then find a bug. I am sure it would be fine by OTA but if that fails you always have Odin as a backup. Even if you decide you do not like it you can go back to N.
If you are rooted and have custom recovery the OTA will fail anyway. If so just flash with Odin.
Click to expand...
Click to collapse
Ok, it is reassuring to know that I can downgrade, as I remember from my older dvices that downgrading was not possible at least not easily
winol said:
Hello, I have seen a mixed bag of opinions about Oreo, some saying is excellent, others stating that only marginal improvements, and, a bunch reporting problems af all kinds, even regretting that they updated, many did not receive Ota, but installed the firmware via Odin, I would really like to hear about your experiences about OTA Oreo, in Mexico oreo is not yet available, and maybe I would not accept it, depending on your opinions, but only about OTA Oreo, thanks in advance for your useful inputs
Click to expand...
Click to collapse
I've got an exynos with oreo i received OTA, in my opinion everything is a bit faster, and the whole interface has been refined just a bit. Better battery life by just a little. Definitely update for the new emoji style though! ?
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.
I have two (identical) X4 1900-1 Android One phones , both were rooted with Magisk patched boot image on PPWS29.69-39-6-2. I was able to restore boot image with Magisk Manager on one and the January 1 PPWS29.69-39-6-4 OTA update completed successfully, I reinstalled Magisk per tutorial, root is present and Safetynet passed. The other one became stuck in a kind of updating loop for this OTA prior to restoring the image with Magisk, the update failed on "Step 3 of 6", then starts all over again, ad infinitum, causing battery drain and slowdown. It started this before I restored the boot image with Magisk but fail is continuing since doing so and after a reboot. Automatic updates were turned off in Developer Options, but it still tried to install the update before notifying me that it was available. One difference after restoring boot image with Magisk is that the phone is no longer showing the update progress page--when you tap System Updates the CHecking for Updates flashes briefly and then a toast says Software Update Unsuccessful. That message comes up every few seconds.
My past experience with failed OTA updates on other devices has been the update process stops with one failed update, never tries again and I had to flash manually. Wondering about the best way to address this issue is. One of these phones is my "backup" device, so I have some wiggle room on what to do. Should I (a) flash stock back on the problem phone and let it go through the several security updates, or could I possibly restore a TWRP backup from the updated phone on the problem one? I did a similar restore years ago from one Moto XT926 to another and it worked, but I believe the restored phone might have acquired the serial # of the donor.
I took logcats before and after unrooting, but had trouble uploading one of them. I'll try again.
I spoke a little too soon on the one that "successfully" updated. It is unable to complete phone calls with the same SIM that works in the one that keeps giving the failed update message. Calls just end as soon as send is pressed, or hang trying to connect. In Settings it shows the correct phone number etc., network settings are same as the working phone and this one worked with this SIM a few weeks ago. Some problems connecting to computer visa wifi as well. Beginning to wonder if this is a bad update? Could really use some help here as I don't have a fully functional phone now.
Turns out the "successfully" updated phone is pretty borked. Lots of strange behavior and black screen freezes. The modem/radio seem to have major problems. With no sim card in the phone, the LTE icon shows and indicates signal, but no connectivity. Freezes and blank screens when I hop around in Settings. Wifi connect is wonky. And no phone connectivity with SIM. Looking like I'm gonna have to go back to stock with PPWS29.69-39-6-2, the latest full FW I have.
Has anyone out there had problems with this OTA?
Where can I find the log file from the OTA update, to try and see what went bad?
On the "failed" phone, I was able to find the url for the OTA update (Blur_Version.29.461.4-29.481.10.payton_fi.google_fi.en.US.zip -- PPWS29.69-39-6-4) on the logcat and download it. I've uploaded it to Drive and here is the link is below if anyone needs it. There are lot of error and suspicious messages in one of the logcats from the failed one but interpreting them meaningfully is above my paygrade. I've attached another log to this post. Can someone tell me how to stop the endless updater loop until I can fix the other phone? I am unsure what app/service to disable. I read somewhere there is a way to delay updates on Pie, but it doesn't appear to be a toggle anywhere in Settings.
This is the Android One/Google Fi variant XT1900-1. Flash at own risk!
https://drive.google.com/open?id=151TRLKfmlROCT6f--U4PWRPqmkFyD0T9
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Force Updates
KrisM22 said:
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Click to expand...
Click to collapse
Thanks , however that option was turned OFF in Developer Options. Update still forced itself on both phones.
Oh well! It's all google's fault!
Back to stock working so far
KrisM22 said:
Oh well! It's all google's fault!
Click to expand...
Click to collapse
Appears so. Keep reading.
I flashed stock PPWS29.69-39-6-2 and so far things seem to be working--phone, data, wifi.
I'll give a full update on functionality and de-borking when the thing's finished its updates and app installs.
I did notice that in device setup, in the Google Terms the last item "Install updates and apps", states "This device may automatically download and install updates and apps from Google and your device manufacturer...." and there is no on/off toggle!!!! You are forced to accept this "setting", the only option is "Accept"!
Thanks again Google.
I suppose this means that the Developer Options setting is moot.
I would be interested to know if this "(it's not a bug it's a) Feature" is present in Oreo builds?
Remember that google doesn't write android so we can modify it - in fact, google goes WAY out of its way to prevent that - that is why there are so many releases of things like Majisk - google keeps blocking them.
Only a tiny tiny fraction of Moto X4 users attempt any modification of their phones.
You might succeed because you have not yet flashed a custom ROM and thus changed the bootloader and file system from the stock OTA'ed Pie setup. Those that have cannot return. Apparently ever.
KrisM22, would you say that the X4 is a less suitable device than others for rooting? And BTW appreciate your noob warnings, only wish they had appeared sooner. I had already rooted these earlier.
As a matter of practice, I never flash custom ROM or recovery on devices until after they've reached end of OEM support. Actually with the ability to boot TWRP via fastboot I don't see any advantage to installing it but numerous disadvantages. I have unlocked and rooted all my (unlockable) devices, but I may rethink that in light of these recent Android changes. For my next phone I would probably choose a more mod-friendly OEM, if such exists. One+ maybe?
a) you're welcome
b) don't mod this X4 in any way if you are OTA upgraded to Pie.
You might have been able to modify it if it was still on 7 or 8 but I have no idea what the devs are using for
1) bootloader
2)file structiure.
I think, if you have to root, go back to something like a G3, where the bootloader didn't change and the file structure didn't change. Even the Z play had probs around the Oreo bootloader change, but we still could use rsdlite to get back from most disasters.
iow, think pre/pre Treble in any form. It may be, in a couple more years, when Treble has stabilized, that we can get away with modifying things, but on a current phone I would avoid it, UNLESS others have already successfully/repeatedly done it.
I also feel that most of the reason for flashing a custom ROM are gone. People get there, spend a lot of time playing with updates and releases, and eventually go back to stock. There are always a few exceptions, but... As to the various reasons for "needing" root, I feel there are always alternatives. I use Block This! to keep ads out of Brave, BBC app, and APNews app. While there are occasions like can't-edit-build prop, I find I can live without it. It is an adjustment of attitude/expectation. Yes, I have had tons of fun and wasted tons of hours playing with my past phones, it happens I haven't missed it with this one, especially since the sec updates are so recent - I don't worry until it's a year or 2 past.
Once the X4 is on Pie stock, do not modify it in any way.
As to other phones, yes, if you really have to modify it, search the wealth of info that is XDA until you have found a phone that folks have been able to repeatedly get back to stock - be on the lookout for a trail of endless posts about bricked phones and blank flash stuff - a sure sign to avoid it. - This forum is littered with them!
If you have modified a phone: BEFORE taking an OTA, flash phone with latest stock, then let it take the OTA. I had to modify that - I have no idea if you can flash this thing once it is on Pie.
I also feel that most of the reason for flashing a custom ROM are gone.
Click to expand...
Click to collapse
I agree, especially for current devices that are still supported. I'll leave these stock at least until that ends. I actually though it had already reached EOS, so I was caught with my pants down. That said, these phones ran just as well stock/rooted as all of their predecessors I have owned, and as well as when unrooted--until the update fail happened. I may root one if I decide to keep using it beyond EOS. And it's true that most custom ROMs are rarely as smooth and reliable as factory.
Yes, I have had tons of fun and wasted tons of hours playing with my past phones
Click to expand...
Click to collapse
True Dat! But, a hobby is a hobby, and not everything hobbyists do in any field turns out stellar. One reason I always try to have have a decent running backup phone if I mess with a daily driver.
With an EOS device, the risk of a bad outcome is to a large degree mitgated by the greatly diminished value of the device. I have a Moto X 2015 Clark that I've been playing with Randomblame's LOS16 builds on, and it is very usable. Too bad that phone never had good battery life, I liked everything else about it. Might as well keep it rather than sell it for the maybe 50 bucks it might bring. Hell, I only cut my last XT926 loose early last year!
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
redwoodie said:
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
Click to expand...
Click to collapse
EXCELLENT!!! Great to hear!
Yes, always have a backup!!!
EOS: I was surprised by this update and am now guessing that we might even get one in Mar or Apr. We'll just have to see if that includes 10. But to me a phone is not really "EOS" until maybe a year or 2 after it stops getting updates. I haven't heard of anyone getting hacked. On any phone.
Great!!!
If you are willing, could you do a couple things:
Go to first post edit, go advanced and mark thread as SOLVED.
add a post about how you did it:
1) disclaimer: "Do at your own risk. I am not responsible for anything." or some such!
2. a sentence or 2 about how you did the flash.
3. attach a copy of the bat file you used for the flash.
I think only works if you haven't changed bootloader or file system - NO custom ROM.
Thanks!
Post issue solved etc.
I will happily do that once I've gotten the second X4 straightened out, at that point I'll feel confident it is really "solved".. Probably next week at soonest, I have a minor medical procedure today. I didn't use a .bat file, I fastboot flashed each .img, erase and sparsechunk the old school way. There was a flashall.bat I found on XDA but it was for Oreo builds, had a couple lines in it I was unsure about, and wasn't comfortable modifying it.
Many thanks! Hope all goes well with that today!
If you could provide a log, or list of commands used, that would help!
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
redwoodie said:
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
Click to expand...
Click to collapse
Thanks. modem problems? Dunno... Keep us posted! Thanks!
Are your two One fi, or regular - I bet the motherboards on the two are different, thus the different result.
Both One/Fi. Same baseband versionon both.
Just re-flashed NON-HLOS.bin ad fsg.mbn, same results.
I'm a little baffled by the script commands that follow these flashes to "erase modemst1/t2". One user on this thread claimed omitting (commenting out) those erase commands cured the problem https://forum.xda-developers.com/moto-x4/how-to/android-one-xt1900-1-wifi-sim-stock-t3941837.
I tried the modem flash mentioned above with out the erase commands. No change.
Another suggests:
My XT1900-7 had lost its IMEIs and Wifi connections, even after factory reset.
The solution:
Get XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet
if you are booting from slot _b, then go to fastboot and flash modem from this FI ROM:
Code:
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
Thinking about flashing back to original stock Pie 29.69-26, or the latest 29.69-39-6-4.