Google removed the link to the OTA files from their developer preview page and I need the OTA file (not the factory image) for my Nexus 5x. Anyone have this by chance? I think it's bullhead-ota-opp5.170921.005-b05549a0.zip
https://developer.android.com/preview/download.html
Aren't these the factory images? I ask for the OTA because my bootloader is not unlocked and I need to sideload the file. Google had OTA preview files available initially and I'm just hoping someone pulled the OTA for Nexus 5x.
Try enrolling to beta program.
I am enrolled in the beta program, but I loaded an old OTA on accident which is causing my phone to boot loop. I can get it in recovery, so I'm hoping if there is a 8.1 OTA somewhere I can sideload that and solve my problem.
Another attempt at my question:
Did anyone pull the link with an "adb logcat" or something similar to the ota googlezip link? I can find links in the other forums to the Pixel XL and Pixel, but just not Nexus 5x.
Related
Just received an OTA update and was quick to press Install but it was only LMY48T (from LMY48M, never rooted). Tried googling and all I see the 7 (2013) WiFi was suppose to go from LMY48M straight to MRA58K and LMY48T was only a security update for Nexus 6, 9, and 10 which was required before going to M. Should I still try to flash MRA58K manually?
I've just had the same. Odd isn't it?
Trev
tegodwin said:
I've just had the same. Odd isn't it?
Trev
Click to expand...
Click to collapse
Same here.
hampster-colonics said:
Just received an OTA update and was quick to press Install but it was only LMY48T (from LMY48M, never rooted). Tried googling and all I see the 7 (2013) WiFi was suppose to go from LMY48M straight to MRA58K and LMY48T was only a security update for Nexus 6, 9, and 10 which was required before going to M. Should I still try to flash MRA58K manually?
Click to expand...
Click to collapse
Ditto
LMY48T has now appeared on the Google factory image web site. We must have received this OTA update before this was posted. OTA to 6.0 must now be soon.
Trev
Me 2
argh, ditto! I have a notification that an update is available, cool! 9MB only, the LMY48T
Even I received a quick security update for Nexus 7 2013 (LMY48T) and is listed under factory images in Google developers (developers.google.com/android/nexus/images) site now. Seems like Nexus 7 got that security update too. Also Nexus 4 got that security update(LMY48T) too.
So Nexus 4,6,7,9,10 got those updates. Hopefully will get Marshmallow update soon.
My Nexus 4 also got this update. According to the Stagefrigt detector app it fixes all known Stagefright vulnerabilities.
Your Nexus 7 2013 will get Marshmallow. Nexus 4, Nexus 7 2012 and Nexus 10 won't.
So is there a link anywhere for a, OTA link for the Nexus 7 (2013), from this new build number, {OTA update from LMY48T to MRA58K}? Where is the new link? / There seems to be one or more devices' with the LMY48T to Marshmallow, but I do not see one for the Nexus 7 (2013).
Nexus7(2013) said:
So is there a link anywhere for a, OTA link for the Nexus 7 (2013), from this new build number, {OTA update from LMY48T to MRA58K}? Where is the new link? / There seems to be one or more devices' with the LMY48T to Marshmallow, but I do not see one for the Nexus 7 (2013).
Click to expand...
Click to collapse
I too cannot find the appropriate Marshmallow OTA for LMY48T. I tried the update for LMY48M but that did not work.
anyone got a solution for this? cheers
This is so annoying. Is there a way to roll back the security update to sideload the available OTA, because otherwise it's getting a fingerprint mismatch.
Should be out in about a week
Nexusoid said:
This is so annoying. Is there a way to roll back the security update to sideload the available OTA, because otherwise it's getting a fingerprint mismatch.
Click to expand...
Click to collapse
I messaged the Google Dev team on Twitter and they said it should be out in a week or so.
Installing the official Google marshmallow 58k factory image is no more difficult than installing a sideload 48t to 58k image.... Just install the full fresh 58k image and be done. Take control. You can't complain about not having the latest when it's there for the taking. You just have to do it.
Sent from my Nexus 7 using Tapatalk
neyenlives said:
Installing the official Google marshmallow 58k factory image is no more difficult than installing a sideload 48t to 58k image.... Just install the full fresh 58k image and be done. Take control. You can't complain about not having the latest when it's there for the taking. You just have to do it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I thought sideloading the complete image would wipe the device. That is what everyone is trying to avoid.
If that isn't the case, then bonus!!
any news on this?
rassnik said:
any news on this?
Click to expand...
Click to collapse
No I haven't heard or seen anything yet. They said about a week or so, it might be a little longer still.
You can just tweet them yourself. @googledevs and you can also check the hashtag #ghelp as well.
I have the LMY48T trying to get to marshmallow, but surely something is jacked up with my system and adb.. I do i adb restart to recovery, and get no command, so i then i push the buttons to set to install a ota, on my pc says no device when i try to side load. weird cuz it let me reboot using adb.
Finally got OTA update and went straight from LMY48T to MRA58V and apps/games seem to launch so much faster.
Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman
I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?
Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?
As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.
Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman
I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.
I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??
I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
vMAC said:
I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
Click to expand...
Click to collapse
On my phone, the file you are looking for does not exist at this location. Are you rooted and trying to take an OTA? If so the downloaded "incremental" OTA is never going to work. If you are bound and determined to use an OTA image, simply sideload the full OTA from recovery via adb, and if you are rooted why not just flash the full image via fastboot?
v12xke said:
On my phone, the file you are looking for does not exist at this location. Are you rooted and trying to take an OTA? If so the downloaded "incremental" OTA is never going to work. If you are bound and determined to use an OTA image, simply sideload the full OTA from recovery via adb, and if you are rooted why not just flash the full image via fastboot?
Click to expand...
Click to collapse
In the past I have been able to do the incremental OTA while rooted with Magisk without issue. Lately I have been having issues getting it to even acknowledge that an OTA is available. When checking my logcat it showed an attempt to locate that file and that is why I was checking to see if anyone had it.
The problem with doing a full image via fastboot is that I have to be tethered. I travel a lot and don't want to have to worry about getting to my home computer to get everything up to date. The previous ability to do an OTA with Magisk installed for my Pixel was perfect and efficient. Hoping to get back to that point.
vMAC said:
I am trying to diagnose an issue with my Pixel 3XL in which it won't allow me to do the OTA update.
I am looking to see if anyone can verify that they have a file at: /data/system/system-update-info.xml
If you have this file and are on the December 5th security update or the Jan update please send it to me or post here.
Thank you in advance.
Click to expand...
Click to collapse
I am on the December 5th update, rooted, and that file doesn't exist for me. Oddly enough, I don't have a pending update though. When I force it to check it tells me I am up to date.
Did you ever figure this out?
Sorry if this has been discussed elsewhere. I couldn't find anything about it specific to the pixel 3xl.
Has anyone tried Flashfire to install an OTA update?
I have it installed. It recognizes is an A/B partition device. I've seen that there are people that have done it on the pixel 2.
Just curious if anyone has given it a shot. If it was successful, what steps did they take?
Just looking to see if it's possible to take an OTA and maintain root with magisk using Flashfire.
I wouldnt mess with flashfire, it hasnt been updated in ages
I haven't had a chance to try it because my device doesn't get the OTA notifications right away and I get tired of waiting so I download and flash the factory image, but you could try topjonwu's OTA update instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Greetings.
Let's say I accidentally DL'd the OTA from the OEM update screen. Where in my file system might I find the file? I read that it may expire and vanish. It's that true? Kind of afraid to reboot right now. Thanks in advance.
Pixel 2xl, rooted, Magisk, OEM 10, Aug. rev.
Even if the OTA did expire and vanish, and I have never heard that happening, Google makes full OTA images available at https://developers.google.com/android/ota in the Taimen section. As to where they are located, likely in the /data partition, but I have absolutely no clue where exactly they are.
I would simply reboot, as the system has most likely already applied the OTA and simply needs to finish completing the update.
So I had to reboot, now I lost root. Is there an easy way to get it back or do I have to wipe?? Thanks.
Boot - NOT install - TWRP using fastboot on the bootloader screen and flash a copy of Magisk you should have stored on your unit.
If you need detailed instructions we have a rooting guide on the forum that should help. Just make sure not to install TWRP or the unit will end up bootlooping, requiring you to flash the full firmware to fix it.