yashsingh1/xdaforums huggingface dataset:
[Moto X4 Questions & Answers] redwoodie:
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.
[Moto X4 Questions & Answers] redwoodie:
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
[Moto X4 Questions & Answers] KrisM22:
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.
[Moto X4 Questions & Answers] redwoodie:
Force Updates

Thanks , however that option was turned OFF in Developer Options. Update still forced itself on both phones.
[Moto X4 Questions & Answers] KrisM22:
Oh well! It's all google's fault!
[Moto X4 Questions & Answers] redwoodie:
Back to stock working so far

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?
[Moto X4 Questions & Answers] KrisM22:
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.
[Moto X4 Questions & Answers] redwoodie:
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?
[Moto X4 Questions & Answers] KrisM22:
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.
[Moto X4 Questions & Answers] redwoodie:
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.

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!
[Moto X4 Questions & Answers] redwoodie:
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.
[Moto X4 Questions & Answers] KrisM22:
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!!!
[Moto X4 Questions & Answers] KrisM22:
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!
[Moto X4 Questions & Answers] redwoodie:
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.
[Moto X4 Questions & Answers] KrisM22:
Many thanks! Hope all goes well with that today!

If you could provide a log, or list of commands used, that would help!
[Moto X4 Questions & Answers] redwoodie:
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.
[Moto X4 Questions & Answers] KrisM22:
Thanks. modem problems? Dunno... Keep us posted! Thanks!
[Moto X4 Questions & Answers] KrisM22:
Are your two One fi, or regular - I bet the motherboards on the two are different, thus the different result.
[Moto X4 Questions & Answers] redwoodie:
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://xdaforums.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:

Thinking about flashing back to original stock Pie 29.69-26, or the latest 29.69-39-6-4.
[Moto X4 Questions & Answers] redwoodie:
I'll try -2 again to see if I can even get spotty wifi back, then try some of these test codes and see what I can find.

https://safetricks.org/android-secret-codes/

https://www.xda-developers.com/codes-hidden-android/

There's a thread on Lenovo about the wifi issue on Moto Z, but nothing about the mobile fail.
[Moto X4 Questions & Answers] KrisM22:
hope you have some success!
[Moto X4 Questions & Answers] redwoodie:
Secret codes etc.

I'm on -5 now with wifi cutting out and no mobile.

A number of those "secret codes" do nothing at all...some that relate to mobile signal do nothing if you don't have connectivity.

I was looking at

*2767*3855#

The description is:

The question is, exactly what firmware, and where from? Would it take all the deep stuff like modems, GPS, etc. back to stock? Renew all partitions? Is it installing firmware from some hidden backup partition (maybe FSG?) and....would it be taking it back to the firmware the device originally shipped with (yikes! Marshmallow?).

KrisM22, since you were able to install custom ROMs and then get back to stock, is that worth a try on this ?

I saw something on a Moto page I cruised by that said the X4 won't get another version upgrade. So maybe another security patch or 2 and that's it.
[Moto X4 Questions & Answers] KrisM22:
XDA went belly up immediately after you sent that - thus the delay...

My sense on those secret codes is that they appeared maybe 10-15 years ago and have been since attributed to every phone on the planet by folks who wish to appear knowledgeable. but aren't. Most will not work on your or any phone. I believe that factory reset is one of them, and, no, I have no idea what it originally meant. I think Nokia was one of the phones they originally worked on. some of those codes were carrier specific so would only work if you had a specific carrier. It's almost anyone's guess. I have never played with any other than the **61 which (sometimes, on some phones) changed the delay for the (ATT) carrier to go to voicemail. Long time ago I think I tried one that was supposed to allow you to choose your speed(like lte), but I was afraid and never selected anything. whether they work or do anything is mostly hearsay by inexperienced folk. If someone pipes up and claims to have knowledge on this, take it with a grain of salt until it actually does something on your phone.

I did install 3 custom ROMs and got back to stock ONLY because I had backed up EFS, Persist, etc.

I figure I was lucky.

I did at one point wind up with a situation where it wouldn't take 6 (or whichever one it was) until I went back to -2. I doubt it would change anything for you but you might try that with the latest majisk and see, before you put it under the truck's tires. More and more I am thinking that one is simply gone and we will never discover why.

no more updates... - yeah, you are probably right. Oh well, it was a nice ride! I'll use it until it breaks and then get something else (used, a few years old, probably Moto, not too expensive.).

Had it out yesterday testing the camera and had to laugh - after all the tons of work folks have done on researching camera apps, stock camera is still by far the best. better than my (old) little Canon Elph SD780. Very suitable for a trip abroad. or anywhere.

Wish I knew more. Gives one pause about modifying a phone in the future.
[Moto X4 Questions & Answers] johnjingle:
IF you are unlocked, it would probably be easiest to just backup the stuff on the phone and then re-install the firmware via fastboot you probably do not even have to erase everything if you are already stock. There are tutorials on this site.

firmware: https://mirrors.lolinet.com/firmware/moto/payton/official/

https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
[Moto X4 Questions & Answers] KrisM22:
Read the thread before commenting, please.
[Moto X4 Questions & Answers] redwoodie:
KrisM22, which (EFS, Persist etc.) partitions did you restore going back to stock after custom?
[Moto X4 Questions & Answers] KrisM22:
I think at one point I restored dsp, efs1, efs2, fsg, persist, and vendor. vendor, as I recall, failed and was never restored. persist and fsg come from rom flash zip anyway, so did nothing. dsp would have nothing to do with it. Subsequently when I had the refusal to successfully OTA update, I restored efs and went back to -2 and all was well. If I recall correctly, and it was a while ago. I suspect it was -2 that cured it, though. For you, one thing you might try is to backup efs on bad phone, copy all 70 or so partitions from the working phone to the bad phone, and then restore the correct efs, flash -2 and see what happens. I have never researched it so wouldn't have the faintest idea how to copy all partitions and both slots, phone to phone. EDIT you could destroy the phone by doing that since you would have to delete and create all those partitions, I think... beware.
[Moto X4 Questions & Answers] redwoodie:
Well, guess what. I restored EFS (only, no other partitions) from the 04/06 (-4) TWRP backup taken before I flashed -5 (that started my problems), and wifi and mobile are working. But software update continues to fail.

I had tried restoring the entire TWRP backup earlier but it failed, I think error 255 tar fork.

So we know for sure that an EFS backup is critical before any modding.

Now, if I could just get the effin thing to take an update!
[Moto X4 Questions & Answers] KrisM22:
Okay, lets see if it holds. If it starts again, please get me a 2 minute Matlog of communications cutting out. I don't think you need root to do that.

Yeah I remember you teling me about that tar error before.

Yes, EFS for sure, but I would take all of the non-standard stuff offered in twrp.

As to it not updating just flash -6 next time. If you have a phone that works except for updating, I would take it and run. Or I quess you could try -2 plus the efs restore....
[Moto X4 Questions & Answers] redwoodie:
How do I do that?

Flashing -6 (and any subsequent) sounds like a plan. One thing, the EFS I restored was from -4, phone is on -5. Maybe version mismatch is blocking update?
[Moto X4 Questions & Answers] KrisM22:
could be...

I'm working on it. should have it in a few minutes.
[Moto X4 Questions & Answers] KrisM22:
logcat for Moto X4 One fi at stock Pie Mar 1 2020:

on phone install Matlog

press desktop and choose widgets and put the Matlog widget on the desktop.

Allow access - no need for root:

Be dev (tap build)

USB Debug on.

USB cable connected to computer.

(Motorola drivers run or repair)

Tap pulldown and set to transfer files.(else it won't find device)

adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS

In Matlog app/settings(3 dots)/settings

log buffers - change to all 3 - Main, Events, Radio.

Omit sensitive info to ON <- don't trust this - check for email and phone # before attaching txt file.

When you are experiencing the problem, tap the widget to start recording. click OK.

run for 2 minutes or enough to catch a couple cycles of the problem

tap the widget to stop recording.

You may have to rescan media to see it - it will be in

internal storage/matlog/saved logs/

attach it to a post.

I probably won't be able to see anything but it occurred to me while I was out walking (avoiding the many folks not wearing masks) that we should do this. If you can, tell me the time frame of when it cuts out and when it comes back.

I may edit this - it's been a VERY long time since I've looked at a log!

I look at it with notepad++
[Moto X4 Questions & Answers] redwoodie:
OK, thanks!

What parta the planet you at? Lotta people here not wearing masks in town but I live out in the woods....I can walk for miles and see no one! Going to stores is very stressful.
[Moto X4 Questions & Answers] KrisM22:
Boston. Lots of people. And our daily caseload is still pretty high. But a lot of people seem not to care. Oh well!
[Moto X4 Questions & Answers] redwoodie:
If I'm not having connectivity problems after flashing -6 or -2 and EFS, but still not updating, would the Matlog be any use sussing that issue?
[Moto X4 Questions & Answers] KrisM22:
No. I suppose somebody from google/android could but I sure couldn't.

Interesting - solved the connectivity. Does it repeatedly try to update? or just sit there?
[Moto X4 Questions & Answers] redwoodie:
Yeah, endlessly. Quits at 21%. Remember the title of this thread? The more things change, the more they stay the same.
[Moto X4 Questions & Answers] KrisM22:
okay, if you can, get me a short matlog around the time that it quits and I'll see if it says anything. Let me know the time that it quit.
[Moto X4 Questions & Answers] redwoodie:
I downloaded Matlog and got it working, but I think I'll flash -2 and restore EFS again and see if it will update. Working on a project at home so I'll get to it in a few days. Need a rest from flashing phones, I think I have flashed these two at least 40 times.
[Moto X4 Questions & Answers] KrisM22:
cool. alternately you could flash 6 and no more updates until the next one.
[Moto X4 Questions & Answers] KrisM22:
There's another update out there but mine is doing what it did on the last one - just looping on unsuccessful. I'll deal with it tonight. edit: this is ppws29.69-39-6-8 security May 1.

Did -2 and then took 4,5,6,8

couldn't boot said data may be corrupt.

try factory reset.

I just realized I didn't format data before flash - I will go re-do.

No it failed again. I'm going to try to get a usable system with a factory reset.

You know, I am beginning to think about dumping the x4 and getting something else. I certainly will never modify/flash a phone again. I have wasted 4 hours on a beautiful sunshiney day.
[Moto X4 Questions & Answers] hugehead83:
Same!

Same happened to me today on my XT1900-1.

I selected "Try again" a few times, and eventually it worked. Then I tried the OTA again, and the problem came back.

Then I held VOL- for close to a minute and was able to get it to a fastboot state.

I ran the flash-all.bat for XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-6 and it booted ok.

I re-applied latest TWRP/Magisk, and I'll probably wait until there's a full image of this release before trying again, or just skip all together :/

Edit: This is the first time I've had this issue, and I have applied every monthly update since this phone was released.
[Moto X4 Questions & Answers] KrisM22:
Yeah, I think -8 is a bit more fussy. I thought it might be my google backup but if you had the same prob, then not.

At the moment, because I was having trouble with google assistant, I (format data and wipe stuff and) flashed -6, which then immediately took 8,- wait for my google backup stuff to restore - reboot - retry 4 times and then did factory reset. pita. it's almost enough to make me switch to apple. ;)
[Moto X4 Questions & Answers] akillenb:
OK, saw that -8 was available, and checked my (now relegated to backup device) X4. It showed -8 was ready to install, and would be rebooted by June ? to install if not done prior. So I rebooted.

And it failed to boot.

Twice!

Factory data reset the only other option, and the phone rebooted to be setup as new, yet again. Now I have to wait while it downloads 3-4GB of apps and data. Already switched to apple for my daily driver, as this "stuff" has gotten ridiculous.
[Moto X4 Questions & Answers] KrisM22:
Yes, I quite agree. Each time an update comes out I have to do a full install from scratch.

No more modifying phones for me.
[Moto X4 Questions & Answers] Redx508:
is there not a way to disable all OTA updates on stock?

i was on stock 9.0 rooted and it kept trying to update to the may OTA
[Moto X4 Questions & Answers] KrisM22:
Nope. There is a setting down in system/advanced/Developer options, but it doesn't work.
[Moto X4 Questions & Answers] Redx508:
wow this sucks

i just want to stop messing with custom roms for now lol
[Moto X4 Questions & Answers] johnjingle:
Considering this thread:

1. Don't unlock and root your phone and expect automatic updates to work correctly, it just doesn't sometimes on almost any phone.

2. Jailbreak(root) iPhones and you can and will run into similar problems.

3. I have 3 different phones with separate numbers (2 Android and 1 iPhone). The android phone that I leave stock never has issues with updates. I mess with the other android(unlocked and rooted) and iPhone (jailbroken) and very often end up with issues I need to troubleshoot regarding updates, recovery, etc.

4. I find it fun to fix problems with those other two phones and consider it a challenge.
[Moto X4 Questions & Answers] johnjingle:
That being said, just use fastboot to run the script to install the previous build (make sure you don't have erase user date in the script) and when it still says data may be corrupt, restart and it should work. Then use Titanium Backup to stop Motorola Update Services until you can get the update off of lolinet.
[Moto X4 Questions & Answers] KrisM22:
Okay. Enough. take this discussion elsewhere. Only on topic for redwoodie's thread here please.