Below are a list of all known Nexus 5 OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file on my website, http://randomphantasmagoria.com, in case Google pulls it down in the future.
OTA Updates - hammerhead
Current firmware: Android Android 6.0, Build MRA58N
MRA58N from MRA58K - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip
------------------------------------------------
MRA58K from LMY48M - https://android.googleapis.com/pack...402b.signed-hammerhead-MRA58K-from-LMY48M.zip
------------------------------------------------
LMY48M from LMY48I - https://android.googleapis.com/pack...ed-hammerhead-LMY48M-from-LMY48I.79fa6114.zip
------------------------------------------------
LMY48I from LMY48B - https://android.googleapis.com/pack...ed-hammerhead-LMY48I-from-LMY48B.1207c77d.zip
------------------------------------------------
LMY48B from LMY47D - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47D-restricted-radio.zip
LMY48B from LMY47D - https://android.googleapis.com/pack...d-hammerhead-LMY48B-from-LMY47D-fullradio.zip (Use this if the one above won't flash)
LMY48B from LMY47I - https://android.googleapis.com/pack...rhead-LMY48B-from-LMY47I-restricted-radio.zip
-------------------------------------------------
LMY47I from LRX21O - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX21O-radio-restricted.zip
LMY47I from LRX21O - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX21O-fullradio.zip (Use this if the one above won't flash)
LMY47I from LRX22C - http://android.clients.google.com/p...d-ota-LMY47I-from-LRX22C-radio-restricted.zip
LMY47I from LRX22C - http://android.clients.google.com/p...mmerhead-ota-LMY47I-from-LRX22C-fullradio.zip (Use this if the one above won't flash)
-------------------------------------------------
LMY47D from LRX21O - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
LMY47D from LRX22C - http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
-------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
LRX22C from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84Q.a7e2eebf.zip
LRX22C from LRX21O - http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip (Original, may not flash for most people)
LRX22C from LRX21O - http://android.clients.google.com/p...rhead-LRX22C-from-LRX21O.radio-restricted.zip (Attempt to fix #1, may or may not flash.)
LRX22C from LRX21O - http://android.clients.google.com/p...d-hammerhead-LRX22C-from-LRX21O-fullradio.zip (This should flash for everyone)
-------------------------------------------------
LRX21O from KTU84P - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
LRX21O from KTU84Q - http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
-------------------------------------------------
KTU84Q from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KOT49H.9cad7d26.zip
KTU84Q from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84M.21e068a8.zip
KTU84Q from KTU84P - http://android.clients.google.com/p...ed-hammerhead-KTU84Q-from-KTU84P.a32b2f45.zip
-------------------------------------------------
KTU84P from KTU84M - http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip
-------------------------------------------------
KTU84M from KOT49H - http://android.clients.google.com/p...ed-hammerhead-KTU84M-from-KOT49H.d173d546.zip
-----------------------------------------------
KOT49H from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KFS78N.2a79b8f6.zip
KOT49H from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KQS81M.f3dc7925.zip
KOT49H from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KRT16M.b3d1f307.zip
KOT49H from KOT49E - http://android.clients.google.com/p...ed-hammerhead-KOT49H-from-KOT49E.537367d5.zip
----------------------------------------------
KOT49E from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KFS78N.777bedc5.zip
KOT49E from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KQS81M.79448efe.zip
KOT49E from KRT16M - http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
----------------------------------------------
KRT16M from KFS78N - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KFS78N.c6defefd.zip
KRT16M from KQS81M - http://android.clients.google.com/p...ed-hammerhead-KRT16M-from-KQS81M.ea9d0ad5.zip
SPECIAL THANKS
Nevvty
fevan
El Daddy
TheManii
switch85
xdatastic
GabrielGPP
emuneee
kvidli
EthanFirst
HackerWolf
mazsuper
msinkovich
zero_x3
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Thank you, added you to the index.
subscribing. nice to see oldblue here as well
oldblue910 said:
As with so many Nexus devices in the past, I'm going to be tracking OTA update URLs for the Nexus 5 both in this thread and on randomphantasmagoria.com. The first post will be updated with each OTA and if you get an OTA update on your Nexus 5 that I don't have listed here, please get the URL and post it here for the community!
VERY IMPORTANT
When the Nexus 5 launches, it will most likely have an immediate OTA update available the first time you turn it on. Please DO NOT accept this OTA update without getting some information for me first! Too often, people get excited when they turn on their device for the first time and see an update. They accept the update and before we know it, we end up losing all data on the firmware that the device ships with.
When you get your Nexus 5 and turn it on for the first time, please gather the following info before applying that out-of-the-box OTA update:
1. The values of ro.build.fingerprint and ro.build.date.utc from /system/build.prop.
2. The baseband version (can be found in Settings | About Phone)
3. The bootloader version (can be found by booting into fastboot mode, the bootloader version will be displayed on screen).
4. The filename for the out-of-the-box OTA ZIP file (if any). This file can be found in /cache or you can check logcat for the full URL. Either one works.
If you need help with any of this, I'll be more than happy to assist! After we have this information locked down, feel free to apply the OTA update out of the box and enjoy your new device!!
Click to expand...
Click to collapse
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Any reason your not just requesting a system dump of the out of the box firmware?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. Basically it comes down to the fact that system dumps aren't official and you can never be guaranteed that what you're getting is pure and unmodified. Because of that, they're pretty much useless for me.
For a shipping firmware that just gets updated upon first boot, I just want the info. It's much faster for someone to just type out the info I need rather than dumping the system, zipping it, uploading it, downloading it and hitting a hex editor to get the bootloader and baseband versions from the dumps.
I'm sure someone will post a system dump, but unless it's an OTA or a set of official fastboot images from Google, I don't really have any use for them.
Sent from my GT-I9505G using Tapatalk
Gotcha
Sent from my XT1080 using XDA Premium 4 mobile app
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
oldblue910 said:
Alright guys, the Nexus 5 order pages are live. If anyone buys one, PLEASE get the info I need (listed in the first post) before applying the out-of-the-box OTA update. Thank you!!
Click to expand...
Click to collapse
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
wvcadle said:
Will do. Just ordered my white 32GB with 2 day shipping. I live in WV and know from the N4 release that they have a facility in Lexington, KY where it will most likely ship from.
*subscribing*
Click to expand...
Click to collapse
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
oldblue910 said:
Thank you very much. Much appreciated. Also, once you get that info, apply the out-of-the-box OTA update and then get the same info for the updated firmware as well, please!
Click to expand...
Click to collapse
Will do.
wvcadle said:
Will do.
Click to expand...
Click to collapse
You're the man. Thanks, dude!
https://support.google.com/nexus/answer/3507867?hl=en&ref_topic=3415518 said:
The new Nexus 5 comes with Android 4.4 pre-installed. Note that you will be prompted to install a small update when you set up your device.
Click to expand...
Click to collapse
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Same here
Sent from my Nexus 10 using Tapatalk 4
efrant said:
Unless you are like me, who doesn't boot into Android the first time until after I unlock the bootloader, dump all the partitions and get root...
Click to expand...
Click to collapse
Well that would require waiting a custom rec to be released first, generally people here are so impatient they'll flash a rom and when they realize it's a dos 4.0 image they'll just come and complain because no factory images are available
---------- Post added at 04:09 PM ---------- Previous post was at 03:36 PM ----------
https://groups.google.com/forum/?fromgroups#!topic/android-building/JVLaFRoJxFk said:
the kitkat release build (KRT16M) for the Nexus 5--which will be tagged with android-4.4_r1
Click to expand...
Click to collapse
Whatever the initial rom is, it will likely OTA to KRT16M
TheManii said:
We can more or less expect that the initial rom wont ever be dumped, as SETTING UP THE DEVICE WILL FORCE AN OTA.
This is what happened for the 2013 N7 and for the GE S4.
If you are willing to try and get the initial ota, you will likely need wireshark/fiddler/<your preferred network sniffer> to get the url.
Click to expand...
Click to collapse
Is it possible to set up the device with no network connection and avoid any initial OTA update?
I'm thinking not, first post states it could be pre-downloaded and in the cache folder...
koriflame said:
Is it possible to set up the device with no network connection and avoid any initial OTA update?
Click to expand...
Click to collapse
Possibly...you can definitely try. :good:
Sent from my Galaxy S4 Google Play Edition using Tapatalk
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
El Daddy said:
My N5 will be showing up Monday afternoon. I'll pull the OTA link if it hasn't been posted by then.
Click to expand...
Click to collapse
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
oldblue910 said:
And all the info on the shipping firmware!! Keep in mind that, like the N7 2013 WiFi, there may be two OTAs out of the box. The first one will be forced during the setup screen. That one will convert the ROM from dev-keys to release-keys, then once that one is in and you set up your device, it'll probably get a normal OTA to KRT16M.
I hope there's a custom recovery available by Monday. Otherwise we may lose that initial devkeys->releasekeys OTA because it's forced.
If there is a custom recovery, make sure you don't boot the system normally the first time. Instead, the first time you turn it on, boot it into fastboot mode (power + volume down). Note the bootloader and baseband versions on screen. At that point, unlock the bootloader, boot the custom recovery (use fastboot boot recovery.img so you don't overwrite the stock recovery), and do a nandroid. Provide that Nandroid backup, please!
Once that's done, stay in the custom recovery and do an adb shell. Dump the radio if you can. I can help you with that if you don't know how.
After that, boot her up normally, accept the forced OTA and after it applies, DO NOT let it boot up again. Once it reboots, hold down volume down as it reboots so it'll go back into fastboot mode. Note if the bootloader version changed. Boot your custom recovery again (use fastboot boot) and this time do an adb pull on the log files in /cache/recovery. The devkeys->release keys OTA filename should be in there. Post that.
After that, boot her up, set her up, and get the OTA link to the KRT16M OTA, and then tell us the new baseband and bootloader versions for KRT16M. Thanks everyone for offering to help. If there is a custom recovery by Monday that'll be awesome. If not, we may lose the devkeys->releasekeys OTA file. :/
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Hmm, I didn't know about the forced OTA during setup. Does it reboot the device or somehow just switch the keys?
Anyway, I'll do what I can. Hopefully, I can keep my excitement in check and remember to do all these things!
So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?
EYEramid said:
So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?
Click to expand...
Click to collapse
Same thing happened here.
colarosen said:
Same thing happened here.
Click to expand...
Click to collapse
Im gonna try reflashing back to stock again, in a couple of days. If you figure it out let me know
Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.
colarosen said:
Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.
Click to expand...
Click to collapse
That's exactly what I did too
ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).
colarosen said:
ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).
Click to expand...
Click to collapse
Cool, I'll try this tonight, thanks
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....
I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.
I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!
I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?
Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.
batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016
Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.
I made the mistake of installing TWRP and Magisk before updating, and all I get is the "update unsucessful" screen, so now I'm stuck with 7.1.1 on my Android One Moto X4.
I found a factory image of Oreo on firmware.center (can't link it here because new user, but the filename was PAYTON_FI_8.0.0_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) for my device, and would like to know if it's safe to use and how to install it (sites seem to give conflicting information). This thing is brand new, so I'm a bit nervous about messing it up.
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
sleeptab said:
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
And use this ROM as it is current Oreo with March Security patch: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
Click to expand...
Click to collapse
One last thing, that guide mentions using mfastboot, where do I get it? Is it any different from the regular fastboot?
No it's just normal fastboot.
Flashed it, works great! Thank you! (However, Android File Host was having issues and it took multiple times before a successful download)
Hello, last time I updated my P7 was in January, I want to flash the May Update, but the last image factory uploaded in google's page is February Update. I only can see May 23 OTA. Why they stopped uploading full image factory? Is there a new workflow to update a rooted device? (I prefer not to flash otas)
Thanks
alsansan said:
Hello, last time I updated my P7 was in January, I want to flash the May Update, but the last image factory uploaded in google's page is February Update. I only can see May 23 OTA. Why they stopped uploading full image factory? Is there a new workflow to update a rooted device? (I prefer not to flash otas)
Thanks
Click to expand...
Click to collapse
Change the language on the download page to English and they should all show up.
Lughnasadh said:
Change the language on the download page to English and they should all show up.
Click to expand...
Click to collapse
Had that problem once too, viewing the page here in Germany. Then someone told me to change the language. Sometimes I wonder how such a big billion dollar company can mess up stuff so bad.
thank you so much