Related
Marshmallow factory images never a problem flashing. Ever sense Nougat came along I can not flash the system.img in fastboot without getting the dreaded "error: cannot load 'system.img' ". I've tried the trick by adding the extension to flash smaller chucks of data with the command line.
I used flashfire to update with no problem but this takes all the joy of doing it manually.
I know other users have had this problem also. Did anyone come up with a solution for this problem yet? Thanks.
Solved:
Seems that my Platform-Tools program was not updated as I had thought. I had thought it was a "One Button" update type of program but apparently certain parts or updates need to be updated first then other parts can be updated. So long story short for anyone else having this problem make sure the all updates are applied to Platform-Tools.
Thanks for all the help!
Yes this has happened to me and I was stuck almost. I had to load the system image to a otg and flash it in twrp and that's when it would go.
Have you tried flashing using LxMultiTool
Leeum said:
Have you tried flashing using LxMultiTool
Click to expand...
Click to collapse
I have not tried. I will on next update if I can't find any other fix. I also forgot to mention that I updated all the libs and what not in the Google adb program installed on my PC. Also I used Winrar to decompress the factory image if that makes a difference, it hasn't been a issue in the past with marshmallow.
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Pig Vomit said:
I suspect you are not running the latest version of platform tools/adb/fastboot. Find the latest version of platform tools and you should be good.
Click to expand...
Click to collapse
Thanks for the info. I did update to platform tools when nougat was released last month, but will check again. I had the same issue then also. I even installed the 7.0 files. Maybe I'm missing something.
As i said, Download LxMultiTool. It has adb and everything. I flashed latest NRD90U 7.0.0 Stock rom without issues. It also lets you lock/unlock bootloader, sideload files, install recovery
How do you load the system image to otg.?
Sent from my HUAWEI MT7-TL10 using XDA Free mobile app
Solved, thanks guys.
Hi, I am looking for help to get from 6.0.1 to 7.0 on my A2017G. I am currently on B10 with an unlocked bootloader.
This is what I have tried so far:
a. Route via OTAs and zips on sdcard:
a1. B10 with stock recovery. Android works. Got here from B9 with OTA B10 installed via stock recovery from sdcard (downloaded B10 OTA from German ZTE site).
a2. Updated from Android with the Axon7_Nougat-7_0.zip OTA on my sdcard (downloaded from the German ZTE site). Miflash completes without any error message.
a3. Result: phone reboots, after Axon splash screen, phone switches to edl mode (in windows: Qualcomm HS-USB QDLoader 9008).
a4. When I reboot to recovery, I can see that the recovery is 7.0.
b. Route via OTAs and N zip via adb sideload:
b1. B10 with stock recovery.
b2. In stock recovery, "flash from adb".
b3. On windows 10 laptop: adb sideload Axon7_Nougat-7_0.zip. Result: error message "* cannot read 'Axon7_Nougat-7_0.zip' * ".. Zip opens fine on laptop.
c. Route via TWRP and leaked Nougat 7.0:
c1. B10 with TWRP recovery, version 3.1.0-0-ailsa_ii.
c2. Flash ZTE_A2017G.Nougat_leaked_09_03_2017 BootStack and StockSystem by Tron1.
c3. Result: phone reboots to Axon splash and then switches to edl mode, same as a3.
d. Route via TWRP and complete fota update fota_update_A2017GV1.2.0B01_complete.zip
d1. Same result as c.
I have experience flashing with my HTC m7 but on the A7, it seems there are many more ways to make things go wrong and I have no clue where I am going wrong. Any help would be appreciated.
Some strange things:
1) my A2017G (bought in Germany via Amazon, it says A2017G on the back sticker) reports itself as a A2017U to my windows 10 laptop.
2) in stock recovery, when trying to flash from sdcard, I receive an error message that the A7 cannot mount the sdcard.
Replica - sorry
OK, it seems this thread finds lots of readers, so maybe someone can benefit from the solution that I finally found.
These were the steps I took:
a. Starting point was B10 stock (incl recovery) and unlocked bootloader, completely wiped.
b. Only way I could get the 7.0 update (downloaded from ZTE Germany) to work was by putting the .zip on a usb stick and using an OTG cable. Then, 'update' in settings found the zip and started to update. Result was v1.1.0B01
c. As soon as I booted into 7.0, it found the OTA for v1.2.0B02 and started to install that. So, I now finally have 7.1.1 stock with unlocked bootloader.
A big thank you to @raystef66 who provided lots of practical and moral support. Much appreciated.
How can I close the thread?
@piet8stevens Hi, I have a build number ZTE A2017G V1.0.0 B11, MIFavor UI 4.0, Android 6.0.1, Kernel 3.18.20 and I'd like to upgrade to more efficient less limitative version as I have battery drain and can't remove / change google main account with my version. Would you know what's the best version, Is the one you have now better? also do you know when you mess up the upgrade and your phone doesnt work can you still factory reset?
yann360 said:
@piet8stevens Hi, I have a build number ZTE A2017G V1.0.0 B11, MIFavor UI 4.0, Android 6.0.1, Kernel 3.18.20 and I'd like to upgrade to more efficient less limitative version as I have battery drain and can't remove / change google main account with my version. Would you know what's the best version, Is the one you have now better? also do you know when you mess up the upgrade and your phone doesnt work can you still factory reset?
Click to expand...
Click to collapse
AFAIK, you can always do factory reset. There are some good threads with all the files you need such as https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547.
Not sure what you are looking for, but I had good experiences with RR and AEX Nougat. I am currently on RR (unofficial version) N. Am just waiting for O to stabilize a bit to make the switch - see AEX thread https://forum.xda-developers.com/axon-7/development/rom-aospextended-rom-v4-3-t3618950 . I run nanodroid and microG in order to protect my privacy from google. So, no gapps, no google maps etc... .
Hi!
As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.
But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.
1. The official update links from Wileyfox (partially from here, here and myself):
TOS118C (Recovery Image)
TOS163B (Recovery Image) Deleted by Wileyfox
TOS208G (Recovery Image) Deleted by Wileyfox
TOS249H (Recovery Image)
TOS319I (Recovery Image) Deleted by Wileyfox
TOS373J missing
UOS224B missing
UOS273C (Recovery Image)
TOS118C (Fastboot Image) Deleted by Wileyfox
TOS163B (Fastboot Image) Deleted by Wileyfox
TOS208G (Fastboot Image) Deleted by Wileyfox
TOS249H (Fastboot Image)
TOS319I (Fastboot Image)
TOS373J (Fastboot Image)
UOS224B missing
UOS273C missing
TOS089A to TOS118C (OTA Update)
TOS118C to TOS163B (OTA Update)
TOS163B to TOS208G (OTA Update)
TOS208G to TOS249H (OTA Update)
TOS249H to TOS319I (OTA Update)
TOS319I to TOS373J (OTA Update)
TOS373J to UOS224B (OTA Update to OREO 1)
UOS224B to UOS273C (OTA Update)
TOS373J to UOS273C (OTA Update to OREO 2)
2. The instructions how to make the OTA links work (taken from here):
If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
As I just found out: The "User Agent Switcher" for Chrome works just as fine.
3. The instructions how to update a rooted phone (taken from here):
I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.
3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.
3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):
Code:
adb reboot "dm-verity enforcing"
3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).
3.5. Then boot to bootloader and BOOT (not flash) TWRP
Code:
fastboot boot twrp-3.1.1-0-marmite.img
3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there
Code:
adb sideload superuser.zip
3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::
Code:
adb reboot "dm-verity enforcing"
This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...
BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.
Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.
Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?
The images from TOS208G are not available.?
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
(... I dream about Lineage 14.1)
H2Oxide said:
Thanks for this.
(... I dream about Lineage 14.1)
Click to expand...
Click to collapse
We all do, I tried an unofficial build however no WiFi yet :crying:
Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs
I am sure there is some ADB the resolve this for the oneplusone phones.
After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.
I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
quixoticduck said:
Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.
Click to expand...
Click to collapse
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
However like I said at start of post what do you need from your phone/ android version?
image45 said:
It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.
I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.
Click to expand...
Click to collapse
Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
quixoticduck said:
I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.
Click to expand...
Click to collapse
You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.
Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?
Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at
http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/
H2Oxide said:
Thanks for this.
I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?
Click to expand...
Click to collapse
Any thoughts on this? Can I force a sideload or would that be unwise...
der_dkw said:
So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:
Click to expand...
Click to collapse
Sure that's fine.
I really appreciate you collected all the information and created this overview.
Well I finally managed to try the adb sideload and this is what I got.
What's wrong here?
I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G
Any help is much appreciated
Jack3volution said:
What's wrong here?
Click to expand...
Click to collapse
You are using TWRP not stock recovery.
The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).
After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Thanks! my mistake. Yeah I still have stock recovery
Cheers
mdosch said:
Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).
Click to expand...
Click to collapse
What's the actual different between booting TWRP and flashing please?
image45 said:
What's the actual different between booting TWRP and flashing please?
Click to expand...
Click to collapse
Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.
mdosch said:
You are using TWRP not stock recovery.
Click to expand...
Click to collapse
Hmm it didn't work in stock recovery either
Jack3volution said:
Hmm it didn't work in stock recovery either
Click to expand...
Click to collapse
Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?
You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I downloaded the OTA package from the Google page,and dirty flashed over my qq2a with no problems.
Sent from my Pixel 2 XL using Tapatalk
That's what I've always done. And this time it won't take it
Sent from my Pixel 2 XL using Tapatalk
I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.
SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I was having the same issue. I was running a stock rom with the may update . After several tries I desisted and check for updates in the phone and the june ota installed successfully
SuperShadow1021 said:
I must have screwed something up at some point. I figured it out. I upgraded using the factory image and eliminated the -w command from the flash all script so it didn't wipe my phone.
Click to expand...
Click to collapse
I've been removing the -w from the factory images for a few months now. Too much trouble to do a clean flash and I saw no real benefit from the clean flash so I stopped. June update flashed for me just fine.
I was having the same issue. I was running a stock rom with the may update
Check and see that platform tools and all of your driver's are upto date
Solution that work for me
SuperShadow1021 said:
Hello all, today, I tried sideloading the June update QQ3A.200605.001. I get an error message saying"Update package is older than current build, expected a build newer than timestamp 1586927258 but package had timestamp 1586827774 and downgrade not allowed. I am currently on the May build QQ2A.200501.001.B3 with Magisk 20.4 installed and Elemental X Kernel 3.17. I've always done my upgrades this way and is the first time I've ever gotten this error message.
Click to expand...
Click to collapse
I have also face same issue while sideloading June OTA than after lot of searching i found fully working solution.
I am assuming you have not flashed Custom recovery (i usually only boot Custom recovery so that i can sideload ota update using Stock Recovery)
Now connect you phone (USB Debugging: On)
Command: adb devices
Your device must show up in Command prompt
2nd command: adb reboot bootloader
Must be boot into fastboot mode
Now as pixel 2 xl has A/B partition so we have to check active partition first then have to change to another.
To check active slot
3rd command: fastboot getvar current-slot
To change active slot
4th command:
if your active slot is "a"
fastboot --set-active=b
OR
if your active slot is "b"
fastboot --set-active=a
Now reboot to stock recovery (please do not boot into system)
5th Command: fastboot reboot recovery
Now select "apply update from adb"
Once again check for device connection, must show as sideload, then....
Command: adb sideload [filename]
Please replace [filename] with the OTA .zip file you have downloaded.
Ex: adb sideload c:\user\name\Desktop\taimen-ota-qq3a.200605.001-992633c8.zip
Now this should work, as it works for me.
Sorry for detailed instructions, i am pretty sure you already know the basic commands but I just want to post it as guide for everyone.
My First reply on XDA, Happy to help you.