Related
Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?
Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0
Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.
Anyone able to help?
If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.
It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.
Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....
I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!
StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky
I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app
Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.
ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.
No worries bud
capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B
Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..
I have never done an OTA update as when I first got into Android I was flashing ROMs nearly every week and never waited for updates just flashed a new ROM, however when I got my Nexus 6 I decided to just root and stick with stock.
I woke this morning and the 5.1 update was available but when I download it and select install and reboot it boots into recovery (TWRP) and I can't see where the download is - I presume I am having to flash it myself? So I have to reboot and it says I am up-to-date with 5.0.1 and then an hour later the download is available again and I go through the same process.
Can anyone help, tell me where i am going wrong.
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
DebianDog said:
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
Click to expand...
Click to collapse
Well OK stock except for the recovery. I presumed you would know what I meant. I will ensure my posts are word prefect next time.
md1008 said:
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
Click to expand...
Click to collapse
Thanks I'll give it a go
Same issue here. Let us know how you make out.
Hate to do a "me too" post, but I've had the exact same experience.
I'll wait to see whether the fastboot -w method works before I do anything else.
I did try to find the (410.4Mb) download on my N6, but I suspect that the failed update must have deleted it, as it's asking me to download it again.
fastboot -w just wiped userdata so needed to do a fresh install and was still at 5.0.1. So just had to install my backup again to get back to where I was this morning.
Ouch! Sorry to hear it (though glad that you had a backup) - thanks for saving the rest of us from trying that particular route.
I'm still looking for a way to get to 5.1.
You can't do an OTA update with a NON-STOCK recovery.
You can however, if your bootloader is unlocked, download the factory image, extract it, and flash the system.img, bootloader.img, radio.img, cache.img etc...use fastboot to flash those.
Or you can fastboot flash the stock recovery, and take the OTA again.
Thanks.
I assume that I can also use Nexus Root Toolkit to "Flash Stock + Unroot" (without wiping the device), then take the OTA update to 5.1, and then use NRT to Root again?
Just doing a full backup at the moment before I start playing!
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Since doing the method recommended in the second post the OTA update hasn't been available on my device?
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Philip said:
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Click to expand...
Click to collapse
yes and yes done that too
Philip said:
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Click to expand...
Click to collapse
Why did you take the scenic route? This is by far the longest method to do that.
Instead of flashing stock with nrt, why not just flash stock normally? That way you could have just flashed 5.1 without having to take any OTA...
And further, if you wanted to keep recovery, why not just flash the system and boot image keeping everything else as it is? Then just flash SuperSU from twrp?
2 commands
fastboot flash system system.img
fastboot flash boot boot.img
Boot into recovery and flash root.
Much quicker than the method you used.
rootSU said:
Why did you take the scenic route? This is by far the longest method to do that.
Click to expand...
Click to collapse
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Philip said:
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Click to expand...
Click to collapse
It took you loads longer haha.
rootSU said:
It took you loads longer haha.
Click to expand...
Click to collapse
And that bothered you so much that you had to tell the whole world about it? Wow!
Philip said:
And that bothered you so much that you had to tell the whole world about it? Wow!
Click to expand...
Click to collapse
To be honest no. The route you took was so long that I thought you just didn't have a clue about what you were doing so I thought I'd help out and let you know the quicker version... And if anyone reads your post and thinks its the best way to do it, well now they have some contrast.
What bothers me is your attitude however. But I don't care enough to get into an argument with people who would rather waste their time and the people they try to help than listen to constructive criticism.
But yeah, your way is needlessly long so I hope people don't take your lead.
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.
KDZ V40 V409N10l
https://drive.google.com/file/d/1abM4BFQXdW2YzEdLPDcKqeMINfwGohLl/view?usp=sharing :good::good::good:
PjLyTam said:
KDZ V40 V409N10l
http://pkg02.lime.gdms.lge.com/dn/d...2JCA1I61965CIN/V409N10l_00_LGU_KR_OP_1015.kdz :good::good::good:
Click to expand...
Click to collapse
Link broken!
nyttliv7 said:
Link broken!
Click to expand...
Click to collapse
fix
Is that the international model?
guytano86 said:
Is that the international model?
Click to expand...
Click to collapse
https://www.getdroidtips.com/download-v409n10l-lg-v40-thinq/
More info on this download.
So it updates that version to 8.1.0?
This phone comes with 8.1.0 out of the box
guytano86 said:
This phone comes with 8.1.0 out of the box
Click to expand...
Click to collapse
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Ainz_Ooal_Gown said:
the link above says it's 8.0 oreo update....which didn't make sense since mine says 8.1.0 .-.
Click to expand...
Click to collapse
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
guytano86 said:
Yea its probably a typo. I got this update last month. More interested in the November security patch with the camera update
Click to expand...
Click to collapse
Same tbh
Is it work lg g6att us997 converted verson??
munna1123 said:
Is it work lg g6att us997 converted verson??
Click to expand...
Click to collapse
An LG G6 from AT&T converted to a LG V20 US version?????
Guys this is for the LG v40, other devices are highly likely to result in a brick
LG V40 Recovery/Bootloader
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
EBRJR said:
Has anyone else had the following experience with the LG V40: I obtained mine about a three weeks ago. It does have the latest Android already loaded. It's from AT&T. While i am no expert, I always root and am usually pretty successful at it and rooting does provide functionality that I have now come to almost need. It gave me comfort that there were already "How to" explanations all over the web on recovery, root, obtain the unlock code, flashing using Fastboot in bootloader mode, etc., specific for the V40. It gave me even more comfort that various explanations were more or less consistent. Other than the fact that the Developers are not yet releasing the .bin to unlock the Bootloader (which, in time, they probably will do), it seemed like the road to rooting would go fairly smoothly.
However, when I decided to perform some very simple tasks which would be necessary to install a TWRP or some other recovery in anticipation of eventually rooting, I discovered that with my version of the V40, there is no “recovery” at all. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a "factory reset" of the phone or back into the system. Again, I am no expert, but for someone at my intermediate level, I do know that I do need to be able to get into a usable recovery and, more importantly, bootloader mode in order to flash a custom recovery and, eventually, to root the phone. All of my efforts lead me to conclude that there is no way of getting the phone into anything but a "factory reset". Forget about bootloader or Fastboot mode. The "factory reset" recovery gives you two choices -- reset or reboot back into the system. There is no other avenue. When I used the ADB tools while in this particular "factory reset" recovery mode, and tried to reboot into bootloader mode from there, the phone would simply boot back into the system. So, that route ended in a place where I could never install TWRP or anything else, for that matter – including the inability to apply an unlocking code if one were available. Next, I tried get into recovery mode using the ADB tools, not the physical buttons. I was able to achieve something that looked more like a “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this particular problem with other phones before and sometimes, using the physical buttons at that stage, I was able to reveal commands. However, with the V40, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, I tried to use the ADB tools to boot into bootloader mode from that more "conventional" recovery. This merely brought me back to the system again! I played around with this for quite some time before contacting the Developer website. Evidently, they aware of it but cannot understand it. I really like the phone but, without a recovery, it's not marketable. Unless someone here has any ideas, I think I and the phone will be paying a little visit to AT&T soon!
Click to expand...
Click to collapse
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
The option is there for certain models but no official unlock support yet.
LameMonster82 said:
Yeah, the new phones don't have "recovery". Whatever LG uses to factory reset it's not really a "recovery". However there is still hope because TWRP can still be added as a "recovery". That's the case with the. LG G7 and it's being accessed through "factory reset" but it's not resetting. As far as I know there's still no way to unlock the v40.
Click to expand...
Click to collapse
Without being able to get into bootloader, how do you add TWRP?
EBRJR said:
Without being able to get into bootloader, how do you add TWRP?
Click to expand...
Click to collapse
You're able to access the bootloader without any trouble.
LameMonster82 said:
You're able to access the bootloader without any trouble.
Click to expand...
Click to collapse
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
EBRJR said:
I cannot..i cannot get to a place where Fastboot can be used. Only a recovery with no commands. Please tell me how you did it. Thanks!
Click to expand...
Click to collapse
There are 2 ways
1.) Adb reboot bootloader
2.) USB plugged in.
While restarting holding down vol- key
(It works for the g7 bitte not sure for the v40)
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.