My phone no longer sees OTA updates so I have been stuck using the factory images for the last few months. This month when I run flash-all.bat I end up with:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
< waiting for any device >
Sending 'bootloader' (8361 KB) OKAY [ 0.214s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
and the update fails. I am currently using the 4/27/2020 copy of platform-tools and validated that bootloader bootloader-sargo-b4s4-0.2-6355063.img is in the local directory so Im a bit stumped.
I ended up having to sideload the OTA update.
Dunno if you've tried this yet, but you can factory reset your device and backup, then see if OTA works.
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Different-But-Similar Issue
darkmeridian said:
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Click to expand...
Click to collapse
In my case, I uploaded the wrong boot image via flash.android.com; what I thought was beta 1 of Android 11 was a pre-Developer Preview of Android 12 (S). Since I still had the last full image of Android 10, I went back and flashed that (to scrub my flub). The OTA of 11 beta 1 came in on schedule once I had done that. Tomorrow, I'll hopefully (barring heat) take the new Google Camera for a drive - looking at changes since 7.2 - which shook things up merely on the NightSight/Astrophotography end. I seriously doubt that this will be 7.4 (which was unique to the Pixel 4), as I had seen nothing indicating that even Google was going to cross-port any of 7.4's feature set to the rest of the Land of Pixel.
I tried using flash-all for the first time for the June update and also got errors and an unbootable phone. So I went back to the sideloading method that has always worked fine for me and that fixed the problem. My phone is also rooted with magisk.
Related
I didnt see any mentions of it, but when i did my usual download the ota file, adb sideload and it has always served the package and rebooted fine. Feb update failed to sideload it gave a diff error code 1 and then 0 the second time i tried it. Redownloaded it , switched usb ports and again sideload failed. I ended up just letting google install it from the os , which i normally dont like to do but it worked. I noticed that ota was only 100+ meg versus 1.6 gigs using the recovery method. Im on a verizon locked bootloader stock setup. Could a older version of adb or fastboot suspect? But thats usually shows other oddball errors.
Sounds like a bad download to me. My ota was much larger than 100 megs and I had no problems sideloading.
Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*
KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.
If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!
I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.
That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.
If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.
Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1
No idea why this posted twice.
Thanks!
The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.
39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...
Was sideloading my Pixel 4a to the december update, was getting the common failed to read command (closest I got was 94%) and decided to reboot. I expected to get stuck booting or reboot into bootloader, but surprisingly I booted into the new update. Never saw this before so just wanted to ask if this is something I should be warry of (e.g potential crashes and bootloops because I haven't re-rooted yet).
Thanks!
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Spell out the adb tools used.. version #
Steps used to "downgrade" your mentioning many different roms, especially confusing because you must flash (all ?) partitions to downgrade especially bootloader and such.
If you used factory web flasher or not. Or another all in one tool. Even just adb tools and double click flash-all.
I thinking you need to use factory flasher, wipe all, flash all partitions. Keep bootloader UNLOCKED.
The statement of trying to transfer data makes no sense since you likely can't get past system installation to get to transfer data.
So post steps please of your methods to get to your post question.
Maybe a better spot to post question, lots of great people in this thread!
June 7, 2023 - Beta 3 UPB3.230519.008 Global - Android 14 "Upside Down Cake" - Pixel 7 Pro [Cheetah]
Android 14 Beta program for the Pixel 7 Pro [Cheetah] Download links in the middle of the OP. Welcome to the Android 14 Developer Preview! This first release is for developers only, to help with early development, testing, and feedback...
forum.xda-developers.com
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
simplepinoi177 said:
Yeah...even after you downgraded successfully enough to get to the setup page/stage, maybe it was not downgraded successfully 100%.
I suggest using Google's official Android Flash Tool to reflash the full factory image to all partitions to try and get everything properly set up.
A couple of things to be sure of: best to use platform-tools r33.0.3 (in case flashing in fastbootd is necessary), make sure to check "force flash all partitions" and make sure not to check "skip secondary".
If for some reason you think flashing to both slots would be best, it hasn't been confirmed that the Android Flash Tool does this, so then you should try badabing2003's PixelFlasher to flash to both slots....
Hope this helps...
Click to expand...
Click to collapse
Have got it all sorted now. Went back to 05 May beta and that's working fine. Was using the official flashing tool and flashing all partitions and wiping butbthar was where I was getting the issue.. But now if I just wipe it works all ok.
SAMVREMIX said:
So downgraded from Beta 2 of A14 to A13 and now cant get past the stage of the setup to transfer datat from an old device. It either says setting has stopped working or if i click on dont copy, it will then go to the checking info page then back again to transfer data. Have tried different A13 builds and different roms, all with the same build. Thanks.
Click to expand...
Click to collapse
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
shivdubey said:
Same issue with me as well but the problem is I can't use android flash tool because oem unlocking and usb devugging was not enabled tried sideloading the OTA zip of android 13 may patch but still the same error stucked on initial screen setup please provide any leads Thanks
Click to expand...
Click to collapse
i have the same problem, any help?
Had the same issue, I sideloaded latest Android 14 beta 2 OTA image for my pixel 5 and that fixed the problem.
OTA images for Google Pixel | Android Developers
Instructions for downloading and appying preview OTA images for Pixel devices.
developer.android.com
A14 Beta 2.1 was just released and includes the following fix aimed at addressing this issue:
Fixed an issue that prevented users from completing device setup after opting a device running an Android 14 beta build out of the beta program. However, this fix is not backward compatible, so users that want to opt out of the beta program should take the following steps beforeopting out:
Update the device to Android 14 Beta 2.1, either through the over-the-air (OTA) update prompt, or by downloading an OTA image and then applying the update manually.
Reset the pin, pattern, or password that's used on the device by navigating to Settings > Security & privacy > Screen lock. You can use the same pin, pattern, or password that was used previously, but you need to go through the setup flow.
Opt out of the beta program by following the instructions listed for the "How can I opt out and return to a public Android release" question in the FAQ section of the Android Beta Program page.