Database Develop

Cheesecake

I believe its time more people check moto servers. http://db.tt/rTv1HLJc this app will find updates off of motos server. Do not install them. Upload to a file sharing service and send me a link thru email. Im not responsible for anything that may happen. My email is [email protected] and yes its [email protected]
Sent from my DROID4 using Tapatalk 2

I would be willing to give it a shot. I downloaded and installed the apk but I don't know what I am doing with it. Do you know where I can find a guide on how to use it?

I installed the Cheesecake app before, and noticed that even though I changed the servers, it doesn't change from what it looks like in the app and from the testing page. Also each time I do it and have done it, I got "Motorola Service Account" needed. Am I doing it wrong?

I believe you need to wipe data/cache prior to running. That is, according to this post:
[Project Cheesecake] Need YOUR help!
Background:
Yes it's true, Motorola has every OTA, every non-accepted OTA, and every non-release OTA and sbf sitting on a sever. Special Motorola employees get access to these, even on their phones through the access of the blur cloud. There are 19 servers.
The Goal:
Project Cheesecake was a success on finding a few dev builds for the Defy, Atrix, and Photon which lead to an unlocked bootloader on these devices. There is bound to be something on ONE of these servers, and eventually we'll strike gold and find an unlock. Just takes checking everyday.
How you can help:
Check the servers every change you get! Every phone is a little different, plus keep in mind these are ftp servers, so you might get lucky when you do your scan and you might catch something someone else didn't see before; or you might find something that was uploaded, and then later deleted. Wifi is recommended (but not required) when scanning the servers.
Prerequisites:
You need to use Root Explorer or another file manager with root permissions, because when you find an update, it's going to put it in /cache and you need to copy it from there to the sd card.
Please be on stock 2.3.5 (1.3.412) or 2.3.4 OTA. If you have deleted stuff or are running a custom rom or something, you will need to sbf for this to work.
Getting Started:
1)You need to be on stock latest OTA!!
2) WIPE DATA AND CACHE!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1226664
This comes from the droid x2 forums

Cool. Will try that.
---------- Post added at 02:10 PM ---------- Previous post was at 01:37 PM ----------
Factory Wiped Data and Cache, and same issue, not changing and moto account needed . Guess I get to wait to see if anyone else gets the similar issue.

After you do the first step you have to reboot and never click that button again
Sent from my DROID4 using Tapatalk 2

When you check for updates, and get the Motorola account required prompt, just select Setup, it will load for a few moments and you will get one of two screens
1. You could get the device is up to date screen or an update available, which means you successfully checked the server
2. It might say Connection failed: in order to complete setup, yo need a data connection... which just means that server is currently down
So, don't worry, you are doing it right. The Motorola account required is bogus.
P.S. Sorry for the late reply, I had not actually had a chance to try it myself yet

Hey guys just noticed... Motocast no longer works once I started messing around with cheesecake. I get the same message as I do for a down server in cheesecake. I tried changing the server to the production one, but it will not recognize my account. the, I tried creating a new motocast ID and I hang on verifying Motocast on your computer. My next step is a data/cache wipe and not messing with cheesecake, but anyone have any ideas how to get my connection to Motocast back?

I did a titanium restore w/ system data (backup was prior to cheesecake install). So Motocast works again.... but im guessing motocast uses the update servers to validate connection with ur PC or something like tht.
Does anyone else have problems with Motocast after using cheesecake? im wondering if its worth trying again?
Sent from my DROID4 using XDA

Revert back to stock ota server?
Good Evening!
I apologize if I'm stepping out of line by asking but I was curious,
are Droid 4 users able to revert back to the stock Verizon OTA update server after using Cheesecake to modify it?
I've been searching around a bit and came up empty handed to see if there was a way to do that. Obviously not a big deal if I can't (especially since I didn't make a system backup /w Titanium beforehand).
I've just been trying different things to see what I come up with really.
Thanks again!

Yes you can. A reboot reverts it.
Sent from my DROID4 using Tapatalk 2

I've had no luck with this at all. It wipes out all of the Motorola service settings; I always have to do a full data restore to get them back.
And seriously, a full factory reset / wipe data/cache before running this app? I'm not going to do that every day...

I couldn't get it to work either the first time. I did a FDR, then installed cheesecake just after signing in to my google account. Worked just fine then. I just don't find any files. Just get "your device is up to date" or "no connection". Reinstalled all my other apps and it still works just fine. Just no files to download.

Motorola Account Required
I dont get it why it's not working. I've done evertything. I am rooted with Safestrap.
I cleared cache, installed cheesecake, then cleared again after install. then rebooted.
Cleared cache, hit first button, cleared cache, rebooted again.
Cleared cache, hit second button, same story
Hit third buton, "Motorola Account required"
No matter how I do it, I can't get passed it. "Setup Now" puts me into an infinate wait od "Communicating with server" for all servers.
I havent done FDR because its honestly not worth the hassle if I have to do that everytime. Suggestions? or perhaps a little more clarity or a fix would be extremely helpful.

This is kinda where I was headed when I asked if it could be reverted. I've since moved on to the Eclipse ROM but I was wondering, do we necessarily have to change the system files to check the Motorola servers, or would it be acceptable to just skip to step #2 and check the servers that way?
I don't know if that would provide any kind of benefit.

Well, I have it set in my little head that, much like the Droid RAZR, there is an ICS update chillin somewhere on the servers for our Droid 4. And being that there seems to be many who have problems with Cheesecake on the D4, I wonder if there are many people who are actually able to check consistently, or if it is being ignored. Is someone continuously checking? The D4 doesn't seem to have nearly as much action on it as the Bionic or the RAZR.

VS910ZVB: "LG Revolution gets bloat-removing OTA update"

From Android Central: "Updates, patches, and bug fixes are included in version VS910ZVB."
I don't have enough posts yet to link, so replace the " [dot] ":
androidcentral [dot] com/lg-revolution-gets-bloat-removing-ota-update

I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.

Haxcid said:
I have remove clock work so I can get the update. Been so long since I connected my phone to my pc to this, I will have to start from scratch. Time to search for all the how to's in here.
Click to expand...
Click to collapse
I'm rooted but without CWM (still have stock recovery). Can I simply defrost (freezing is all I've done) and get the update? Or do I have to do a hard reset to get back to full stock?
If hard reset to stock is required, any tips or techniques that you use to save time to get back to where you were? Thx.

Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...

Haxcid said:
Well I am updated and while I notice that all the extra Verizon apps are gone here is what I see...
1. Kindle, bing, slacker, tunewiki, and Verizon tones are all still installed and no option to remove them.
2, After I installed a dozen apps of my own, I still have 1gig of app space available.
3. The phone is remarkable faster and smoother.
I am going to see if they fixed the Exchange email client issue I was having...
Click to expand...
Click to collapse
Did you need to unroot? If yes how did you do it?
Thx
Mendel

mmp17 said:
Did you need to unroot? If yes how did you do it?
Thx
Mendel
Click to expand...
Click to collapse
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.

Haxcid said:
Rooted should be ok, you may likely lose your root. It does not install with clockwork. I used lgnpst and imaged my phone, I then did a factory reset, felt like starting from scratch.
Verizon only removed a handful of apps. I am not sure it was worth the trouble. I have to root again so I can go back in and freeze or uninstall all the crap they left.
Id say in the de-bloat department they were a epic fail.
Click to expand...
Click to collapse
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel

mmp17 said:
I tried to do the update and it fails. I unrooted and it still failed if it is not worth it I'll leave it as it is. let us know if this update can be rooted.
Thx
Mendel
Click to expand...
Click to collapse
yeah I returned my phone to stock with the lg tool and tot file, then did a factory reset, updated, rooted again, used titanium back up to uninstall the rest of the bloat Verizon missed.

While I do not know if the update breaks root or not, you can use the root tool in the dev section (esteem root v2) to root your phone. It works like a charm.

So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app

me too. I am running zv9 with root. And uninstalled lots of useless apps for me. I tried update, but failed.
wslguy said:
So was anything else updated? Trying to decide if it's worth my time to bother with. I am already running a zv9 that I seriously debloated and tweaked to where it's useable.
Sent from my VS910 4G using xda app-developers app
Click to expand...
Click to collapse

It will rebloat your phone. While they did patch some things, my phone did actually run smoother. I did have to root it again and un-install all the bloat they left, vzw tones, navigator, city id, kindle, slacker, etc...
No better battery life and not much of a performance increase. Id wait if you are happy.

keeps trying to update
I was planning on rooting & putting BrokenOut ROM on my revo when my contract ended. Then this OTA update came out, and I was worried that it would prevent that. So, I rooted the phone and put CWM recovery on and did a backup. As expected, the OTA update failed.
But, it hasn't given up. It tries and tries, about once a day. I hear my phone chirp, and it has rebooted and drained the battery, and shows at various times either the "update failed" screen, or the "updating in 2 minutes" screen, or recovery. When I get prompted to run the update, I defer it - but the deferal time doesn't correspond to when the reboot happens.
It's possible that the rooting and recovery are behind the problem, and not the update - but I suspect the update has something to do with it.
So, what I'd like to know is:
1) if I get the update, can I still use ROM Manager to change the recovery back to CWM, and still be able to flash BO on it?
2) to get the update, is it safe to just use ROM Manager to put the stock recovery on it, then run the update? I haven't done any debloating or other rooty stuff not mentioned above. I'd rather not lose data by reset, tot, etc.
3) can I fix my problem without getting the update? Maybe one of the options on the "update failed" screen? I'm not sure if I've selected only "OK" or only "Cancel" so far - or what those are supposed to mean.
4) do the security updates make zvb better than BO? (Does anyone here no what the security updates are?)
Thanks...

Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.

I.M.famous XMAN said:
Broken out is based off of V9, so unless there are updates to the radio, you will most likely over-write most, if not all, of the updates.
As posted earlier, someone has rooted and installed cwm. But, someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) I will try my best to update BO. Also, if someone can do a backup of the new update and post it up, (not the blob crap, the other one ) I'll rip the kernel and post a flashable zip. Maybe they did fix something. We will see.
Click to expand...
Click to collapse
Yeah, I figured current BO would undo zvb, that's why I was wondering which I should go with. The update downloaded several times, but I don't see anything in /data/local/tmp. Don't know if the download failed or just didn't persist. It hasn't tried to update for the last 30 hours or so. I'm not eager to encourage it at the moment.
I see that haxcid re-rooted, but nothing about re-cwm-ing.

can't find update file(s)
I.M.famous XMAN said:
...someone wants to post up the update (you can rip it from the /data/local/tmp directory, iirc) ...
Click to expand...
Click to collapse
I rebooted my phone, and once again it prompted me to install the update. I selected "defer" and then checked settings / about phone / software update / status which says "Package downloaded successfully".
However, /data/local/tmp is still an empty directory, according to ES File Explorer.

That's where the file was stored for v7, v8, and v9. Maybe they changed it for this update. IDK. I'll look into it. No worries. It's all good.

I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
Click to expand...
Click to collapse
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB

OrangeJoe said:
I think it gets downloaded to /cache/fota, but deleted once the process finishes failing. I will try to trigger it again and copy it before the phone reboots. I was not given the defer option this time.
---------- Post added at 01:31 PM ---------- Previous post was at 01:09 PM ----------
Ok, I got it, I think. It's called ipth_package.bin
For now, I'm going to skip trying to attach it, and just give the link from which it seems to download:
https : / / pvzwmdmcdn.vzw.motive.com/firmware/LG_VS910_ZV9_TO_ZVB.bin
~47 MB
Click to expand...
Click to collapse
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9

dbeauch said:
Is it weird that my phone never prompted me for the OTA? I am on BO 2.0.1 with ZV9
Click to expand...
Click to collapse
Not really. I believe MT disabled the update feature from BO; hence the 'super fast' FC's at boot.

[Q] Checking for OTA Update Error

Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).

mikestrong19 said:
Just got the Verizon Moto X and now I am attempting to update it to the latest version (Android 4.4.2). I am currently on Android 4.2.2, which came with the phone out of the box. Whenever I go to About Phone > System Updates, it says "Checking for an available update" for a second and then the error message "An unexpected error has occured. Please try again later." pops up. I tried talking to Verizon (they redirected me to Motorola) and Motorola, where I was sent through the standard troubleshooting steps by someone who clearly didn't know anything about the phone. I tried restarting the phone, wiping the phone's cache, and looking for updates through the Motorola Device Manager on my computer (which said that my phone was up to date, even though it clearly isn't). Is there anything else I can do before I try a factory reset? I would prefer to download the OTA, but I have experience with rooting and installing custom ROMs, so if I have to install the update manually, I will (if it gets to that step, I will probably end up installing the 4.4.4 update which got sent out to soak testers).
Click to expand...
Click to collapse
Do NOT upgrade until you've read another 24 hours on this board!!!!! I think you should take a second look at your status and see if you misread 4.4.2 as 4.2.2

If I may ask, why not update?

mikestrong19 said:
If I may ask, why not update?
Click to expand...
Click to collapse
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.

doitinthedirt said:
If you dont mind having an unrootable phone than update.
4.2.2 and 4.4 is fully rootable and able to disable write protection, 4.4.2 and newer is not. once you upgrade past 4.4 you lose ability to gain write and root.
Click to expand...
Click to collapse
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.

mikestrong19 said:
Oh OK, that makes sense. Thanks for the info. I have another phone that I use for rooting, ROMs, etc. The Moto X is currently my daily phone, and I need it to be stable, so I am not worried about rooting or anything like that. Just want the latest stock Android version on there.
I just talked to Motorola on the phone again, and they went through the same standard checklist (restart, wipe cache, factory reset -- none of which worked). At this point, they are going to exchange my current phone for a new one, which works out for me. The Moto X I bought was used, so I am getting a new phone for a used price in a convoluted way.
Click to expand...
Click to collapse
Wow, what a waste. You could have just flashed the entire STOCK SBF as per the Return to Stock thread, and avoided costing Moto money, and hence raising the prices for everybody... :/
This would have repaired any filesystem corruption/damage, which is the only conceivable thing that might have caused your issue.

Your new one will probably have 4.4.2....which means no write protection disabling.
D'oh!
---------- Post added at 07:17 PM ---------- Previous post was at 07:17 PM ----------
You could have had FULL root on 4.2.2.

Root 5.1.1 or 6.0.1?

I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!

ota then root

I OTA'ed, now the phone randomly reboots several times a day, and some apps don't work correctly. Great.

factory reset.

*sigh* I was afraid you were going to say that. Now the problem is backing it up. I have a Titanium Backup Pro license, but I only use it on my old rooted GS2. The Note 4 is not rooted so TB won't run on it. All the rooting tutorials say "back up your phone before you root" but you need root to run TB. Chicken or egg? I guess I could try Samsung Kies, don't know if it will back up everything. My photos are backed up to Google Photos, I guess everything else is replaceable, but I would really rather not have to reinstall all my apps one by one after a factory reset.
That brings up another question: when you to go Settings/Backup and Reset, I have "Backup my data" set to On and linked to my Google account, but nowhere can I find documentation of exactly WHAT gets backed up or to WHERE (it says to "Google servers" but what the heck does that mean? I can't find it on my Google Drive or anywhere else on my Google account dashboard.)
I do greatly appreciate your help, by the way.

You could try reinstalling through kies or smart switch. Make sure to clear caches before and after. And see if that works. If it doesnt help, you could flash recovery, root, try to backup as much as you can between reboots and then factory reset. Your apps should automatically download from play store. But without the titbackup files you'll lose settings and data in a lot of apps that Google doesn't backup.
I unlocked your mum's bootloader.

kydar said:
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
Click to expand...
Click to collapse
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.

Shad0wsabr3 said:
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Click to expand...
Click to collapse
There aren't that many problems with MM. Just superficial stuff like not having mobile data toggle. The problems you are hearing about a factory reset will fix. Like lag, jankyness, apps loading, phone freezing temporarily. You won't be able to do OTA. It will fail because of root. You need to titanium backup or whatever method you prefer of backing up data and flash through kies, odin or smart switch. Probably easier to go that route unless you only did minor things with root like just block ads, then you can probably get away with flashing stock recovery and then OTA. You still might have to factory reset like I had to even though I flashed whole rom through smart switch. If you have xposed or modified something like swapping recent apps and back key like me, then you'll need to flash marshmallow whole and start over after backing up.
Afaik, you can't downgrade to 5.1.1 unless somebody figured out a workaround or you only flashed everything except bootloader.
I unlocked your mum's bootloader.

@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.

kydar said:
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
Click to expand...
Click to collapse
Iv never backed up an unrooted device so I wouldn't know. Glad you nrought that up as Iv been meaning to look into that.
Would you happen to know where the downloaded ota file location is? My phone downloaded it and I keep postponing it.

Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.

Where are the root instructions for completely stock 910T with MM update?

vernj123 said:
Where are the root instructions for completely stock 910T with MM update?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...overy-n910t-t3-marshmallow-pe3-guide-t3406870

kydar said:
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Click to expand...
Click to collapse
I'm still researching what your dealing with. As for me I found the ota file. For those looking for it this is how and where I found it....
With RomToolbox I went to root browser. Then to data folder and a folder named fota. Within the fota folder is the ota update named update.zip. I erased that and then went into Titanium Backup and chose to freeze both software update files. So far no constant reminders that I have an update ready to be installed.
Hope this may help.

OTA update endless fail loop PPWS29.69-39-6-4 on Magisk (un)rooted X4

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.