I'm trying to update my phone from MiFavor 4.0 Current version: A2017UV1.0.0B17 to the B19 update posted on the ZTE support page:
Code:
America AXON 7 SD card software package(326200B1901A2017UV1.1.0B19).zip
When I try to update from Android Recovery menu with update.zip on sdcard I keep getting the same error:
Code:
Installing Update package...
assert failed: getprop("ro.product.name") == "P996A01_N"
E:Error in /sideload/package.zip
(Status 8)
The Android Recovery header shows my device as:
Code:
ZTE/P996A01/ailsa_ii
6.0.1/MMB29M/20160616.175016
Any idea how to get the update to go through? I searched for my current version A2017UV1.0.0B17 and only found a thread here about security patches, and one on ZTE community: community.zteusa.com/forums/discussion/12586/cant-get-updates-help?
trapezoidalrutebega said:
I'm trying to update my phone from MiFavor 4.0 Current version: A2017UV1.0.0B17 to the B19 update posted on the ZTE support page:
Code:
America AXON 7 SD card software package(326200B1901A2017UV1.1.0B19).zip
When I try to update from Android Recovery menu with update.zip on sdcard I keep getting the same error:
Code:
Installing Update package...
assert failed: getprop("ro.product.name") == "P996A01_N"
E:Error in /sideload/package.zip
(Status 8)
The Android Recovery header shows my device as:
Code:
ZTE/P996A01/ailsa_ii
6.0.1/MMB29M/20160616.175016
Any idea how to get the update to go through? I searched for my current version A2017UV1.0.0B17 and only found a thread here about security patches, and one on ZTE community: community.zteusa.com/forums/discussion/12586/cant-get-updates-help?
Click to expand...
Click to collapse
You need to OTA upgrade to B15 (7.0.0) from 6.0.1 before you can upgrade to B19 (7.1.1). I was getting the same error when trying to go from B29 (6.0.1) straight to B19 (7.1.1). You may be able to find an SD card zip of B15 if you are not able to get the OTA.
Hello, trapezoidalrutebega ! Are you perhaps located within the US attempting to perform the update?
ZTEUSA Support
ZTEUSA Support said:
Hello, trapezoidalrutebega ! Are you perhaps located within the US attempting to perform the update?
ZTEUSA Support
Click to expand...
Click to collapse
Yes I'm in the USA. My understanding is that I have a US version of the phone.
I can't do OTA updates - the update utility just says I'm up to date. I'll have to look for the SD Card image of B15 and try that.
People have been saying that my system version is not one of the normal versions. I got the phone used on Swappa a couple months ago. I don't think the previous owner did anything to the phone because the bootloader is still locked. In the bootloader screen I see the following:
Code:
FASTBOOT MODE
PRODUCT_NAME - AILSA_II
VARIANT- MTP eMMC
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - 3aa0b0d7
SECURE BOOT - enabled
DEVICE STATE - locked
So hopefully DEVICE STATE - locked means that the bootloader is locked.
jdgesmlls said:
You need to OTA upgrade to B15 (7.0.0) from 6.0.1 before you can upgrade to B19 (7.1.1). I was getting the same error when trying to go from B29 (6.0.1) straight to B19 (7.1.1). You may be able to find an SD card zip of B15 if you are not able to get the OTA.
Click to expand...
Click to collapse
jdgesmlls - thanks for the tip! It worked.
I did the following:
SD card update to B15 (7.0.0)
OTA updates were available after I successfully updated to B15, but since I already had B19 downloaded I decided to update via SD card.
SD card update to B19 (7.1.1)
OTA update to B25 (7.1.1) Security Patch Level: March 1, 2017
Related
Hi all
I have a rooted Nexus 6P running on MMB29Q build, 6.0.1.
When trying to flash the March Patch update I get ERROR: 7, as well as the following message:
Source: google/angler/angler:6.0.1/MMB29Q/2480792:user/release keys
Target: google/angler/angler:6.0.1/MHC19I/2590160:user/release keys
Verifying current sytem...
Package expects build fingerprint of google/angler/angler:6.0.1/MMB29Q/2480792:user/release keys or google/angler/angler:6.0.1/MHC19I/2590160:user/release keys; this device has Huawei/omni_angler/angler:6.0/MRA58K/dees_troy02060822:eng/test-keys.
I can guarantee I am running 6.0.1 on MMB29Q, so what is the error message about?
Many thanks
How did you flash MMB29Q, through fastboot?
Edit: Are you coming from a Custom ROM?
Flicker20 said:
Hi all
I have a rooted Nexus 6P running on MMB29Q build, 6.0.1.
When trying to flash the March Patch update I get ERROR: 7, as well as the following message:
Source: google/angler/angler:6.0.1/MMB29Q/2480792:user/release keys
Target: google/angler/angler:6.0.1/MHC19I/2590160:user/release keys
Verifying current sytem...
Package expects build fingerprint of google/angler/angler:6.0.1/MMB29Q/2480792:user/release keys or google/angler/angler:6.0.1/MHC19I/2590160:user/release keys; this device has Huawei/omni_angler/angler:6.0/MRA58K/dees_troy02060822:eng/test-keys.
I can guarantee I am running 6.0.1 on MMB29Q, so what is the error message about?
Many thanks
Click to expand...
Click to collapse
Sounds to me like you're trying to adopt an OTA on a rooted phone which you can't do. Flash the factory images to update. Guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
Started the day with firmware 763
Took a backup with TWRP
Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Took one more backup with TWRP
Attempted update to MM using download from ASUS, manually initiating from recovery, got the error below
Attempted update to MM again using the notification prompt after booting phone with update file on SD card (per ASUS' instructions), got the same result, below.
The error text is this:
Code:
Can't install this M package (Tue May 17 23:05:50 CST 2016)
L less than 20160426 build (Tue Dec 1 17:16:17 CST 2015)
E:Error in /sideload/package.zip
(Status 7)
E: fota_return_code 409
It seems this error typically means that the current Lollipop version is old and needs to be updated to the latest before trying to update to MM. I've validated in the About screen that my firmware version is indeed 1531 so I'm not sure what else I need to do.
I apologize if this question has been answered elsewhere. I hunted around for a while on this forum and using Google and didn't find anyone that seemed to be in this same situation.
Thank you for the help!
did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
murat124 said:
did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
Click to expand...
Click to collapse
Well I never actually flashed TWRP, I just booted it using fastboot each time I needed it. Does flashing the OTA updates update the recovery or do I have to do that manually?
I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.
murat124 said:
I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.
Click to expand...
Click to collapse
Does back2stock require a full wipe? I was hoping not to have to do that...
bennettj1087 said:
Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
[*]Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Click to expand...
Click to collapse
Worked in my case when I updated to latest lollipop firmware available.
(Actually I never installed the complete firmware, just flashed
Code:
boot.img
and
Code:
recovery.img
for the latest lollipop firmware available and marshmallow FW installed like a charm, though I'd suggest you install the complete lollipop framework)
I went to work successfully unrooting my phone earlier this year.
I kept the bootloader unlocked because I didn't see it as a problem.
I began working on locking the bootloader this November after my phone could not successfully install the Nougat update.
I've flashed the stock Marshmallow image from Motorola's website but was never given the Nougat update :{
I've read in some places that image is outdated, so i tried some other "official" images I could find that were supposed to be more up to date.
I had the same problem with them so I successfully flashed a Nougat image from: firmware.center/firmware/Motorola/Moto%20X%20Pure%20%28XT1575%29/Stock/
I've now been hit a security update for nougat (version 25.201.1) and I get this error upon the first reboot
E3005 "/modem/image/adsp.b01" has unexpected contents.
E: Error in /cache/BLur_Version.25.11.22.clarck_retus.retus.en.US.zip
(Status 7)
I don't care if my bootloader is locked or not I just want my phone successfully install these updates
Any ideas?
Thanks
I think you had some errors with last flashing.
You should flash the same stock Nougat one more time.
Each fastboot command should ends with OK. @tijuanagenius
tijuanagenius said:
I went to work successfully unrooting my phone earlier this year.
I kept the bootloader unlocked because I didn't see it as a problem.
I began working on locking the bootloader this November after my phone could not successfully install the Nougat update.
I've flashed the stock Marshmallow image from Motorola's website but was never given the Nougat update :{
I've read in some places that image is outdated, so i tried some other "official" images I could find that were supposed to be more up to date.
I had the same problem with them so I successfully flashed a Nougat image from: firmware.center/firmware/Motorola/Moto%20X%20Pure%20%28XT1575%29/Stock/
I've now been hit a security update for nougat (version 25.201.1) and I get this error upon the first reboot
E3005 "/modem/image/adsp.b01" has unexpected contents.
E: Error in /cache/BLur_Version.25.11.22.clarck_retus.retus.en.US.zip
(Status 7)
I don't care if my bootloader is locked or not I just want my phone successfully install these updates
Any ideas?
Thanks
Click to expand...
Click to collapse
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
acejavelin said:
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
Click to expand...
Click to collapse
How would I properly update my modem firmware? Can i just flash the new modem firmware or do I have to re-flash my entire phone again :{
tijuanagenius said:
How would I properly update my modem firmware? Can i just flash the new modem firmware or do I have to re-flash my entire phone again :{
Click to expand...
Click to collapse
Ignore this^
acejavelin said:
Your modem firmware is incorrect, it is not what is expected by the update script (see bold highlight above)... The bootloader being locked or unlocked by itself will not effect being able to successfully take an OTA update.
Click to expand...
Click to collapse
Thanks! I simply tried flashing the NON_HLOS.bin file again and the update completed successfully!
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..
Hey guys,
I try to update my mothers old phone so hopefully some apps are still compatible. I am using the lastest Lollipop firmware (Version WW-1.15.40.1582 ). The problem is I get a error message trying sideload the next firmware version (Version WW_21.40.0.1692 ) which is Marshmellow. As you can also see on the screenshots attached:
Can't install this M package (Tue May 17 23:05:50 CST 2016)
L less than 20160426 build (Tue Dec 1 17:16:17 CST 2015)
E:Error in /sideload/package.zip
(Status 7)
E: fota_return_code 409
Click to expand...
Click to collapse
I found a similar problem here:
Issue upgrading ZE551KL to Marshmallow
Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting: Started the day with firmware 763 Took a backup with TWRP Updated FW to 1106, 1234 and 1531 in...
forum.xda-developers.com
but I did not manage to flash TWRP, the phone just reboots if I try to boot into it and I have to get back to my old recovery image. Also I could not find any updated recovery image in the internet. The ASUS firmware.zips don't contain it somehow. Can somebody help/guide me how I could get the phone on Marshmellow? I know it is an old phone but we are ppor here in Brasil .
Best,
Choceur