Here at last ?
Got this morning the ota message too.
While writing this post, I can say factory image are still not uploaded, so just to avoid problems I'll wait the factory images release. I heard some people complain on the 4 xl forums about soft bricks and bootloops
I got update now - no problem..
Can't get it because I'm rooted. Waiting for a flashable version.
Spookymyo said:
Can't get it because I'm rooted. Waiting for a flashable version.
Click to expand...
Click to collapse
Uhhhh?
Sideload the OTA bro. https://developers.google.com/android/ota -- Or dirty flash the factory image.
Alcolawl said:
Uhhhh?
Sideload the OTA bro. https://developers.google.com/android/ota -- Or dirty flash the factory image.
Click to expand...
Click to collapse
There's a better way I found.
https://topjohnwu.github.io/Magisk/tutorials.html
Which december OTA file is for the unlocked pixel 4? My current build number is QD1A.190821.007
10.0.0 (QQ1B.191205.011, Dec 2019
10.0.0 (QQ1B.191205.012.A1, Dec 2019)
10.0.0 (QQ1C.191205.016.A1, Dec 2019
Edit: Figured it out. It's .012.A1
Related
THis got pushed to my phone today, and I have it deferred for now, is there any way I can grab it for someone? Does anyone have a Verizon MotoX anymore?
is just a security update
I had the same file pushed to my phone yesterday. I cant install it. Since I'm using TWRP as my recovery, I end up in a recovery boot loop. It would be nice if there were a version I could flash.
Here is the official OTA update pulled from my XT1096. It's the security update (August 1, 2016).
You need to be on the latest official software which you can download here:
https://mirrors.lolinet.com/firmwar...VERIZON_5.1_LPES23.32-25-5-2_cid2_CFC.xml.zip
Flash back to "official" status using the guide below (this will wipe your device so make sure to backup your data):
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Then you can take the OTA.
ssmcd said:
Here is the official OTA update pulled from my XT1096. It's the security update (August 1, 2016).
You need to be on the latest official software which you can download here:
https://mirrors.lolinet.com/firmwar...VERIZON_5.1_LPES23.32-25-5-2_cid2_CFC.xml.zip
Flash back to "official" status using the guide below (this will wipe your device so make sure to backup your data):
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Then you can take the OTA.
Click to expand...
Click to collapse
Thanks that worked great!
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Mae7 said:
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Click to expand...
Click to collapse
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Mae7 said:
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Click to expand...
Click to collapse
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Jakets said:
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Click to expand...
Click to collapse
Not sure. It's probably disabled for a custom ROM.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Fat Rat Bastard said:
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Click to expand...
Click to collapse
Yeah I actually ended up going with a V17 firmware.
So, when I go to try and check for system update, it says I'm already up to date. I have the stock 7.1.1 (RETUS/Non-Fi) Retail XT1900-1, (re)locked bootloader. Has there been no official OTA after November? (I did try to manually flash other builds/Oreo/Fi ROM/etc. but flashed back to 7.1.1 stock/Nov 2017 since Android Pay is something I use and other ROMs didn't let me use that). Did I miss something while flashing back to stock that's borked OTAs? [Tried wiping through stock recovery, through TWRP, etc. no difference) Any answers would be great! TIA!
Answer: Looks like it was just me.
Update: Fixed it! Reimaged stock from September 2017 and OTAs began to work! Right now OTA updating to 8.0. So happy!
smmankad said:
Answer: Looks like it was just me.
Update: Fixed it! Reimaged stock from September 2017 and OTAs began to work! Right now OTA updating to 8.0. So happy!
Click to expand...
Click to collapse
Your OTA worked with TWRP installed?
Neffy27 said:
Your OTA worked with TWRP installed?
Click to expand...
Click to collapse
Nope. Still on stock recovery. Since the stock recovery is nowhere to be found for this device, I have refrained from flashing TWRP (I had only fastbooted TWRP, never installed it on here).
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?
If you side loaded the December ota image, can you downgrade to November and receive December's ota? I think the Google image on their site for December is buggy on my device. I am hoping they didn't have the images mix matched since they renamed them twice.
splink7007 said:
If you side loaded the December ota image, can you downgrade to November and receive December's ota? I think the Google image on their site for December is buggy on my device. I am hoping they didn't have the images mix matched since they renamed them twice.
Click to expand...
Click to collapse
Pretty sure you would have to re-flash the entire November image through adb. Then accept the ota before rooting.
I do know that others have faced issued when flashing the wrong December image, like face unlock not working for example.
itylermartin said:
Pretty sure you would have to re-flash the entire November image through adb. Then accept the ota before rooting.
I do know that others have faced issued when flashing the wrong December image, like face unlock not working for example.
Click to expand...
Click to collapse
So I couldn't side load the November ota, I would have to flash the entire full image? Then accept the December ota?
splink7007 said:
So I couldn't side load the November ota, I would have to flash the entire full image? Then accept the December ota?
Click to expand...
Click to collapse
Anytime you downgrade, you have to do a full wipe, and then fastboot the factory image. If your bootloader is unlocked, I would first try fastbooting the December factory image to both slots to see if that fixes your problems, rather than have to wipe your device. You could also try side loading the December OTA to see if that fixes your issues as well.
Badger50 said:
Anytime you downgrade, you have to do a full wipe, and then fastboot the factory image. If your bootloader is unlocked, I would first try fastbooting the December factory image to both slots to see if that fixes your problems, rather than have to wipe your device. You could also try side loading the December OTA to see if that fixes your issues as well.
Click to expand...
Click to collapse
Looking at Google factory image page, it looks like flashing the full factory image requires unlocked bootloader? I'm as factory as they come lol.
splink7007 said:
Looking at Google factory image page, it looks like flashing the full factory image requires unlocked bootloader? I'm as factory as they come lol.
Click to expand...
Click to collapse
Yep. Like I stated in my post. I'm afraid all you can do is side load the OTA again for December to see if that helps your problem.