[SOLVED] Fastboot Flash failes after firmware update - Huawei P9 Lite Questions & Answers

Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
EDIT: The solutionwas to re-unlock the bootloader (just perform "fastboot oem unlock PERSONAL UNLOCK KEY). Thanks to AndreaEl for suggesting the solution.

i have had the same problem some days ago.
Re unlock bootloader and try again

Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset

opal06 said:
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
Click to expand...
Click to collapse
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
opal06 said:
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
Click to expand...
Click to collapse
Have u tried using the method on this thread?
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302

Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse

Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it

AndreaEl said:
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Tried that, it doesn't work. And I'm at B381 by the way. See when I try to send the firmware update to the updater app and install it, nothing changes. The installation completes and after reboot, when I check from about phone I see that I'm still in B381(at least according to it )
---------- Post added at 12:39 AM ---------- Previous post was at 12:32 AM ----------
opal06 said:
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
Click to expand...
Click to collapse
My boatloader is already locked and I'm not rooted.
Click to expand...
Click to collapse

Related

[METHODS][Getting Back] to STOCK ROM after flashing Custom roms

This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
Method 1 :
Make a twrp backup soon after unlocking boot loader .
Am not going to explain how to unlock bootloader and also twrp flashing ,you can search different threads available in the same section .
Soon after unlocking bootloader , Just boot twrp before flashing it .
This can be done this way , Once you unlocked bootloader .
Upon firstboot ,just goto developer options and enable USB debugging and then Open the folder where you had setup minimal fastboot (Mfastboot v2 google for it) . You should have it as you can't unlock bootloader without minimal fastboot .
In any empty space in minimal fastboot exrracted folder , just press shift+right click and select "Open command prompt here" .
Now copy twrp recovery to Mfastboot folder .
Connect your phone to PC.
In command prompt type the below command
adb reboot bootloader
Hit enter ,
Now your phone reboots to bootloader .
Now type this command .
mfastboot.exe boot twrp.img
(Just rename the recovery to twrp.img before flashing )
Now just take a backup and keep it safe somewhere to access when required .
This is easy , but many may loose their twrp backup for some reasons or forgot to take a backup before stepping to custom ROMs , move to Method 2 if your in such group .
Method 2:
Download update.app from official site .
Extract and put dload folder in root of sdcard .
Power off the phone and press vol up+ vol down and power .
It will now fully flash stock ROM with all stock files .
(This method requires stock recovery so keep in mind to flash stock recovery before trying to update as twrp can't perform these tasks )
Method 3:
Its not hard and not easy too but you required to download some tools .
Huawei update extractor tool (google for it)
Once downloaded open the tool and choose the path where you placed update.app in your PC .
Now the tool opens update.app .
Extract system.IMG and boot.IMG from update.app
Put them in the minimal fastboot folder.
Boot your phn to fastboot using command adb reboot bootloader .
Now connecting your phone to PC in bootloader mode , type the below commands
mfastboot.exe flash system system.img
mfastboot.exe flash boot boot.img
mfastboot.exe reboot
That's it you are on stock ROM.
Method 4:
Flash the stock rom flashable zip posted by devs in your device specific threads and flash it .
Fully for noobs : METHOD 5:
Download the twrp backup posted in device specific threads and put it in sdcard and restore it. Its easy though .
Now your device is ready for flashing official updates "if you get them"[emoji14].
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
yddek971 said:
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
Click to expand...
Click to collapse
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
flibblesan said:
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
Click to expand...
Click to collapse
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
yddek971 said:
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
Click to expand...
Click to collapse
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
flibblesan said:
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
Click to expand...
Click to collapse
thanks a lot !
gopinaidu77 said:
This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
.
Click to expand...
Click to collapse
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
clsA said:
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
Click to expand...
Click to collapse
Yeah , thats what i mean device specifix threads .
And thanks for your repository , all the stuff in one place :cheers:
Hi Gopi,
Please help me getting back to stock on my L-22.
I am planning to go back to stock of L-24 available as (KIW-L24-B151-Stock (Boot.img - System - System/Priv-App Only)) posted by clsA.
1. Which method to follow????
2. Do I need to go back to stock Recovery???? If yes, then how??? where is stock recovery of L-22 posted?????
Please guide me I can cook it.
3. otherwise B140.debloated version -2. I tried to install through TWRP. NO success but a bootloop. is it ok this way???
Thanks in advance.
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
gopinaidu77 said:
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks man,
It worked. Now on stock with update 150 installed.
Sent from my KIW-L22 using XDA-Developers mobile app
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
faisalsiddiqui said:
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Click to expand...
Click to collapse
newic2001 said:
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
Click to expand...
Click to collapse
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
good work bro, helps a lot of ppl @gopinaidu77
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
s4h1k0 said:
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
Click to expand...
Click to collapse
try restoring though twrp
clsA said:
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Click to expand...
Click to collapse
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
NAROUTO said:
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
Click to expand...
Click to collapse
Of course unlocked one.
gopinaidu77 said:
Of course unlocked one.
Click to expand...
Click to collapse
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
NAROUTO said:
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
Click to expand...
Click to collapse
Your update.app fail to flash at 5% right ?
Its easy .. Goto settings/storage and set sdcard as default .
And then try dload method .it will get flashed now

[GUIDE][ROOT][UNIVERSAL] FORCE INSTALLING STOCK OTA UPDATES WITH SToCK RECOVERY

Since lollipop there is no manual update option in huawei updater and even the huawei stock recovery has no or less interface which has no adb sideload option. This became a crunch to flash the update which your friend got and which u dont.
This Method is Universal for all huawei devices
In order to apply ota update using this method , root access is a major requirement so be sure your device is rooted.
If u had twrp recovery , at first flash SuperSu package to root your device (Try systemless root only) .
After successfull root ,flash stock recovery from twrp and reboot system.
Step 1:
In my case b370 is the last ota i found for kiw-l22 which vsriram92 posted here . Thanks to him for posting the update before 99% users got their update :good:
Download the relevant update package (ota) which you need a relevant base package to install it on . Ex: b360 as base for b370 update
step 2:
just remember the path where u downloaded the package . Install Flashify from playstore or From Here
Select Zip file which is the third option in flashify .
step 3 :
Navigate to the path where u downloaded ota package select the update.zip (ota package).
flashify starts downloading the package to its path asks you for root access .
Grand Su permissions , Select Cwm recovery if flashify asks as the next option.
Now the phone reboots to recovery and starts flashing.
After the ota update , your device will be unrooted . so take a backup of your stock recovery by following below guide.
Enable Usb debugging and connect ur phone to pc.
navigate to adb folder and place twrp.img or recovery.img in adb folder ,open command window from the same folder and type
Code:
adb reboot bootloader
Now type
Code:
fastboot boot recovery.img
or what_ever_its_name.img
now it temporarily boots twrp , take a backup of your stock recovery and then flash twrp for permanent install and then reroot ur device.
Happy flashing :laugh::good:​
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
rbtrai said:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
Click to expand...
Click to collapse
You might have installed a zip which is not stock ota update . i haven't posted this without trying . I installed b370 with this method and made this live here .
i downloaded from the link provided above which vsriram92 posted...
rbtrai said:
i downloaded from the link provided above which vsriram92 posted...
Click to expand...
Click to collapse
Were you in b360 before doing this ?
Thanks again Gopi. Another great contribution.
vsriram92 said:
Were you in b360 before doing this ?
Click to expand...
Click to collapse
yes ofcourse
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Ajith san said:
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Click to expand...
Click to collapse
Nope. It was there in EMUI 3 previously. Now, we can't unless it has only update.app.
so b370 is only for the ones who gave root access to their phones?
Like your contribution. Perfectly updated to B370.
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
great
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Zacki06 said:
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Click to expand...
Click to collapse
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
ShadySquirrel said:
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
Click to expand...
Click to collapse
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Zacki06 said:
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Click to expand...
Click to collapse
TBH, I'm on a verge to start building LOS or PAC/Slim/whatever is properly maintained and fast for my own needs and ditch EMUI completely....
I'm searching for other firmwares now via FirmwareFinder, there is a probability that one is a leaked test or something like that, because it simply doesn't want to flash. If I find out something, I'll continue on thread you've linked, to avoid flooding this one.
Hi. Thanks for your guide.
I need to update my phone with several ota updates. I just need to repeat this guide's procedure until updated to the last ota or there is a better way to do that?
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
How to update step by step.. Mention it plz
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just because you can't do it, that doesn't mean it's fake.
Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just follow the procedure and you will be done

[REQUEST] XT1700 Original Firmware

Hi there, recently just bricked my XT1700. I installed the XT1706 original rom uploaded by dr.faramroze (very thank you) but I can't install OTA updates, and i don't feel confortable with the secondary sim useless menu.
Somebody can do a backup from his XT1700? Or just a link to download it, because I can't find anything but XT1706...
Sorry my bad english and thank you.
From this page you can download Moto XT1700 stock firmware use SP flash tools to install.
http://motorolastockrom.com/motorola-moto-e3-xt1700
---------- Post added at 08:45 PM ---------- Previous post was at 08:38 PM ----------
Also I'm need here so I want to ask you something I like you erase system and backup XT1706 from recovery. I found that site and downloaded the last software version (S503) I installed and everything goes well. But when I tried to unlock bootloader again the adb window said: This operation is not allowed and I wasn't able to unlock boot loader. Then I downloaded version S116 and I tried to unlock bootloader again and surprised It works. But I tried to install OTA updates and y get no notification of updates. It says system has the last version when is not. Some idea of what can be happening here?
sfreddy15 said:
From this page you can download Moto XT1700 stock firmware use SP flash tools to install.
http://motorolastockrom.com/motorola-moto-e3-xt1700
Click to expand...
Click to collapse
Just a warning - those firmwares (at least the 2 latest versions S503 and S302) have locked boot loaders, you will not be able to unlock the bootloader with fastboot, or install TWRP/SuperSU if you install them.
Would appreciate it if anyone knows where to get either S503 or S302 with unlocked bootloader.
Use S124. It allows bootloader unlock!
k-ninja said:
Just a warning - those firmwares (at least the 2 latest versions S503 and S302) have locked boot loaders, you will not be able to unlock the bootloader with fastboot, or install TWRP/SuperSU if you install them.
Would appreciate it if anyone knows where to get either S503 or S302 with unlocked bootloader.
Click to expand...
Click to collapse
Use S124. It allows bootloader unlock!
jmak117 said:
Use S124. It allows bootloader unlock!
Click to expand...
Click to collapse
In the end I went with the S131 firmware for the XT1706... allows unlock, but isn't any newer than the XT1700 firmware I originally started with :-/
Is this thread still alive?
If so i need help. The links arent working (they work but they dont bring me to the download page, instead to another website) , so does anybody have the stock firmware with them?
It would really help. Im getting so close to rooting my phone!
Here friend, hope you find useful
http://givemerom.com/moto-e3-xt1700

A2017U Stuck on ZTE screen, cannot boot into system even after factory reset

So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Install supersu or dm-verity to bypass the security checks.
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
romeoh said:
I think this is B29 stock image DrakenFX has uploaded it on sharing website, give it a try.
https://www.androidfilehost.com/?fid=312968873555009511
Click to expand...
Click to collapse
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
gpz1100 said:
Install supersu or dm-verity to bypass the security checks.
Click to expand...
Click to collapse
Doesn't that require unlocked bootloader? I want to avoid voiding the warranty.
tupurl said:
Thanks for the link!
Will this work via the update from sd card option on the stock recovery? Or would you recommend flashing from TWRP? Or via MiFlash in EDL mode?
Click to expand...
Click to collapse
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
romeoh said:
This is the zte official B29 package and the only way to used it from the stock recovery from the SD card. It won't work with twrp because it requires the stock recovery. You can also use this method and you don't have to have unlcked bootloader http://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514/page26
Click to expand...
Click to collapse
So, I just now tried to apply the package you linked to (Draken FX stock Marshmallow) and it gave me the same errors :/
E: footer is wrong and E: signature verification failed. Should I try something else?
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
I can't boot into system. Is there a way to enable OEM unlock from recovery, EDL, or factory test mode?
Did you check the zip? You could always use miflash b15 full.
lafester said:
Did you check the zip? You could always use miflash b15 full.
Click to expand...
Click to collapse
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
axon7tool uses different drivers. install the correct drivers for miflash.
tupurl said:
I've been trying to use MiFlash to flash the B29 stock zip by DrakenFX that the romeroh linked to but I can't see my device in MiFlash :/. I know EDL works cuz the axon7tool is able to detect it and write or read recovery and boot properly. Ideas on how to get MiFlash to detect my phone?
Click to expand...
Click to collapse
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
romeoh said:
Ok, I think there was a little misunderstanding about the B29 link that I sent to you bro. That file can only be flashed in Stock recovery you can't flash it with MiFlash. If you want to use MiFlash the only version that's available to flash in EDL mode is Nougat B15. Just reread the OP of the the link I've sent to you before and If you didn't understand anything let us know there is always someone here will help you.
Click to expand...
Click to collapse
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Fazedyrus said:
I'm having sort of the same problem except I'm stuck on the bootloader unlocked screen and any rom I flash gets stuck on "patching system image unconditionally"
Click to expand...
Click to collapse
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
romeoh said:
Have you tried to use the EDL method?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
It should work on fixing this issue even if you are with Unlocked Bootloader, but you'll end up on Nougat B15 because this is the only full EDL mode package available.
Click to expand...
Click to collapse
Flashing supersu and dmverity zip doesn't work either
Fazedyrus said:
Did that, the flash is successful but I still have the same problem in that the system won't boot. Should I just relock and rma at this point?
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
Flashing supersu and dmverity zip doesn't work either
Click to expand...
Click to collapse
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
lafester said:
You doing a full wipe before flashing? Flashing b15 full (no twrp)? Also try format data instead of wipe.
I've gone through this a few times and always manage to get booting.
Click to expand...
Click to collapse
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
Click to expand...
Click to collapse
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
---------- Post added at 05:32 PM ---------- Previous post was at 04:45 PM ----------
Fazedyrus said:
I've done that several times already with no success. I think somehow my device just doesn't work
---------- Post added at 04:14 PM ---------- Previous post was at 04:12 PM ----------
also tried flashing DrakenFX's B29 Stock images but still can't boot into system
---------- Post added at 04:21 PM ---------- Previous post was at 04:14 PM ----------
I've tried many things over the past 3 days for over 10 hours so I think I'm gonna return this phone and just get a OP3T
---------- Post added at 04:45 PM ---------- Previous post was at 04:21 PM ----------
also, not being able to flash any rom with a working twrp makes it look like only I have this problem
Click to expand...
Click to collapse
yep, everything is stock yet I am still not able to boot into system
lafester said:
Enable OEM unlock and flash zte zip from external SD. Sometimes they zip it twice so check the file.
Click to expand...
Click to collapse
tupurl said:
So, while trying to follow the steps given to me to gain root access for data recovery, I stupidly swiped allow system modifications on the signed TWRP. The phone has been unable to boot into system ever since and only gets stuck on ZTE screen. I am able to boot into recovery, bootloader, FTM, and EDL but not system. This suggests that the system image has been corrupted somehow. I downloaded the B15 zip from ZTE's support page and tried to do update via SD card from stock recovery.
After selecting the zip file the phone screen showed the following (I tried with and without renaming the zip to update.zip):
supported api: 3
Install /sdcard/<"filename>".zip
finding update package, opening update package, verifying update package
E: footer is wrong
Update package verification took 1.0 s (result 1).
E: signature verification failed
Installation aborted
This entails that perhaps the official zip is faulty in some way. I chatted with ZTE support, he told me to wipe cache, try redownloading the zip file and retry without renaming, But no dice. Then he suggested a factory reset. I had read that for some others a factory reset had fixed the problem, so with some qualms, I went through with it. Lo and behold, even after 30 min the phone was still stuck on ZTE screen. ZTE support no longer has a B29 zip for downgrading and does not offer a B19 zip. So according to the support guy my last option is sending my phone in for repairs where they'll reformat the phone and reflash Stock ROM free of charge.
While that's all well and dandy, I am still desperately attempting data recovery (all efforts have been futile and I am well aware that I will likely be wholly unsuccessful). So, I was wondering if any of you guys had a backup of the fully stock system image, or had a zip file, or solution that would allow me to boot into system successfully without rooting or unlocking bootloader. A fully stock OS is preferred but am open to alternates such as DrakenFX's fastboot enabled EDL zip if there's absolutely no way to go back to fully stock OS. I am ok with downgrading and then updating later. Just don't want to get the phone reformatted. Thanks in advance.
TLDR: Phone stuck on ZTE screen; factory reset did not help; need to flash fully stock system image and maybe can boot successfully into system; if all else fails will probably submit warranty claim.
Click to expand...
Click to collapse
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Howie Dub said:
lafester is correct, the B15 file from downloaded from ZTE is zipped twice. There is an actual update.zip inside a folder inside the "America A2017U SD card software package(A2017UV1.1.0B15)SD_W" zip. When I bricked my phone, I extracted the update.zip and I was able to flash it from the SD with the stock recovery. Hope that helps.
Click to expand...
Click to collapse
where can I find this zip

EDL Tool vs TulipTool

I have a new (to me) Axon 7 Mini. i hIve had an A7U from a couple of years.
This phone came via eBay, but w/o user PW from previous owner.
Using TulipTool I was able to unlock the Bootloader, wiping all previous User Data, but the Google FRP blocks re setup (it hasn't been 48 hours tho).
Meanwhile I was going to flash a new bootlaoader and ROM, but the EDL tool does not find the phone in FTM or EDL. Surprising since the TulipTool worked fine.
And when attempting to flash TWRP 7.1r1 via TulipTool Recovery just reboots to a blank acreen. Verity restores Stock Recovery after a reboot to system. Unfortunately there is no FactoryReset or Flash ROM choice in the Mi Stock Recovery.
Any ideas? Thanks.
To use EDL tool you need to remove the old driver (he works with TulipTool only), and install stock driver(It should install automatically).
bius88 said:
To use EDL tool you need to remove the old driver (he works with TulipTool only), and install stock driver(It should install automatically).
Click to expand...
Click to collapse
I removed and reinstalled all drivers and moved the EDL tool to C: root.
It now finds the ADB interface, but still receives no phone response in EDL or FTM. No message is seen on the phone asking for USB Debugging.
It has not yet been 48 hours since I removed all user data after unlocking the bootloader, so Google still has me locked out from completing registration, so we will see what happens by tomorrow.
I was hoping to flash a ROM and setthis up for my wife.
I successfully set the phone up as a new user, then Factory Reset which also restored the complete compliment of Android Recovery options. Now to (again) begin the EDL flashing experiments.
Any latest recomendations for Bootloader, ROM and Kernel?
amphi66 said:
I successfully set the phone up as a new user, then Factory Reset which also restored the complete compliment of Android Recovery options. Now to (again) begin the EDL flashing experiments.
Any latest recomendations for Bootloader, ROM and Kernel?
Click to expand...
Click to collapse
First you need read about Bootloader
---------- Post added at 09:35 AM ---------- Previous post was at 09:23 AM ----------
About Edl Tool using
bius88 said:
First you need read about Bootloader
---------- Post added at 09:35 AM ---------- Previous post was at 09:23 AM ----------
About Edl Tool using
Click to expand...
Click to collapse
Thanks. I have been working with the A2017U since Nov 2016 so am a bit familiar. I bought the B2017G as an experiment and am quite impressed with "little brother", so far.
EdIt: For kicks I tried "Check for Updates" and surprisingly received an OTA update from.6.0.1 B14 to 6.0.1 B21. That no sooner had installed when I was notified again that the B21 to 7.1.1 B12 update was available (glad to see ZTE is consistent with their confusing id scheme across the platforms) It also downloaded and installed w/o issue (a whopping 1.8 GB). We'll see where to go next.

Resources