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)
Related
UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now
Reverse
Reverse #2
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.
Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock
HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134
Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse
that version...i can´t find it anywere..maybe someone here knows were to find it?
Updated the first MM beta link in OP
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Download full fw.
BUILD REQUEST INFO:
SW Version: cedric-user 7.0 NPPS25.137-72-4 4 release-keysM8937_11.16.02.51R
MBM Version: B8.23
Modem Version: M8937_11.16.02.51R
FSG Version: FSG-8937-02.65.05
Build Fingerprint: motorola/cedric/cedric:7.0/NPPS25.137-72-4/4:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.246.4.cedric.retail.en.US
Model number: Moto G (5)
Android Version: 7.0
Baseband Version: M8937_11.16.02.51R
Build Number: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
Build Date: Fri Aug 4 04:22:37 CDT 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.246.4.cedric.retail.en.US
Version when read from CPV: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What is that?
Sent from my Moto G (5) using Tapatalk
fxdRoiD said:
What is that?
Sent from my Moto G (5) using Tapatalk
Click to expand...
Click to collapse
It's the last available fw for XT1676. NPPS25.137-72-4
https://forum.xda-developers.com/g5/help/stock-rom-moto-g5-xt1676-3-16-dualsim-t3696622
Haven't seen it anywhere untill now when I got a link that was valid for just a few hours, so I thought I should download it and share it.
Is this rom work for moto g5 model XT1677 Indian varient Amazon exclusive ?? If yes voLTE is working or not ??
Anyone have NPPS25.137-79-3 for the XT1670?
Sent from my Moto G5 using Tapatalk
It can relock bootloader?
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
macho_ said:
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
Click to expand...
Click to collapse
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
macho_ said:
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
Click to expand...
Click to collapse
The robot is stock recovery - hold Vol up & press power button I think to access its menu but all you can really do is a factory reset
Can i install this on 1675 variant?
My bootloader is locked
can I flash stock ROM - with the same patch but another channel (from retin to retus) on a device with a locked bootloader?
if yes, how can I do that? from adb fastboot? RSD lite?
TheFixItMan said:
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
rosel11078 said:
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
Click to expand...
Click to collapse
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
OK so, I have to flash latest offcial stock and apply update oreo then???
TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
Do you know what is the lastest flashable firmware for moto g5 cedric 32gb 2ram xt1670 NPP25.137.72????
That will allow me to upgrade Oreo????
CEDRIC_NPPS25.137-93-2-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
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