Database Users

P9 Lite bricked (L31)

Hi, my problem is with the L31,
I've trying to downgrade from Nougat to MM. I saw on the thread this steps and i followed:
"Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Then I flashed badwolfs recovery b2 as that one lets me transfer files from pc to phone and followed instructions from htcmania from here".
The problem is that i didn't reach to downgrade and when i try to reinstall Nougat by TWRP i get this error messages:
" E: Unknow comand (errno) update_huawei-pkg_from_ota_zip: update package from zip failed"
"Updater process ended with error: 7
Error installing zip file '/external_sd/DLoad/Update.zip'
Updating partition details...
...done"
Now my phone stays freeze on the huawei logo and the flashtool doesn't even recognize my device.
Can someone help me with this matter, please?

try to flash stock recovery and do a factory reset

simo255 said:
try to flash stock recovery and do a factory reset
Click to expand...
Click to collapse
Problem solved.:good:

aalmeida1972 said:
Problem solved.:good:
Click to expand...
Click to collapse
how did you flash a stock recovery please ???

darth_us37 said:
how did you flash a stock recovery please ???
Click to expand...
Click to collapse
I followed the steps that someone advice me. Like above.
"I had to first extract the nougat firmware with huawei firmare extractor and flash everything by fastboot
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Booth files you can find it in this page.
http://forum.xda-developers.com/huawei-p9lite/development/android-nougat-dev-build-huawei-t3488360/page33"
To flash img. i used the file that i attached.
Good luck

so now i restored twrp , i put the update app in sd card and it doesn't want to flash , i'm still trapped in bootloop but i have access to twrp now what to do now ?

I found the old twrp is okey for downgrade,
Just put b161 update.app into sdcard/dload and press volume down + power key.
but flash badwolf's twrp will get stuck in fastboot, though It's not really bricked.

hi, maybe you also have a solution for my problem.
i installed a wrong update via sd card (dload etc.), now my phone is just black no signal nothing. and it seems like a fastboot loop always when i plug into the pc im in fastboot without doing anything
when i try to unlock the bootloader i get "failed command not allowed")
and also when i try to flash the extracted files from update.zip i get the same error ("failed command not allowed")
by the way i didnt active usb debuggin or oem unlocking
please help thank you

A2017G How to relock Bootloader to original mode.

Hi,
is it possible to relock the bootloader to original factory mode.

fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.

After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?

I am interested in a tutorial about going back to stock for G model

The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.

Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.

Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse

dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.

i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?

Any help for the G modell ?

dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.

LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"

peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.

Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.

@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.

how can i flash my original recovery. what is the command for cmd ?

Please help restoring back original recovery.

dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.

I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?

I soft bricked my phone

I wanted to unlock the bootloader and flash a custom rom, but I followed the wrong guide. I am or was running A2017U build 27 but I followed a guide for A2017G, here https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379.
My phone is stuck at the ZTE logo screen and will not proceed despite using TWRP to flash the backup image. Am I screwed?

project_86 said:
I wanted to unlock the bootloader and flash a custom rom, but I followed the wrong guide. I am or was running A2017U build 27 but I followed a guide for A2017G, here https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379.
My phone is stuck at the ZTE logo screen and will not proceed despite using TWRP to flash the backup image. Am I screwed?
Click to expand...
Click to collapse
If you still able to boot to TWRP, I recommend you flashing my B29 Bootstack + StockSystem from here : B29 Files Click Here , then you can flah Stock Recovery you'll be up and running again, i'll be uploading TWRP Flashable B29 recovery Here is the Stock Recovery Flashable Zip CLICK HERE ... YOU CAN UNLOCK using B20 Official ZIP + B20fastboot.zip (Official).
So here Steps:
1- Flash B29 Bootstack + StockSystem
2- Flash Stock Recovery
3- You'll have you device back and running

DrakenFX, thank you. Flashing the bootstack and stocksystem got me in working order. $20 coming your way as promised. Don't drink and flash folks. Lesson learned.

project_86 said:
DrakenFX, thank you. Flashing the bootstack and stocksystem got me in working order. $20 coming your way as promised. Don't drink and flash folks. Lesson learned.
Click to expand...
Click to collapse
you don't have to man, i'm just glad i'm here to help other. send me you hangouts via PM , i'll help you getting Unlock Bootloader before N get here,

Thanks I appreciate that.

***EDIT*** This was caused by the fastboot I had on my PC. Rebooting into Linux and using that fastboot worked fine.
I was able to downgrade to B20, however, flashing your P996A01B20Fastboot_ssl.zip file did not allow me to unlock the bootloader. After rebooting, going into the bootloader menu, and running "fastboot oem unlock" does nothing nor does "fastboot devices" see any device. Do you have any ideas why it is not working?
To be clear, when I ran the P996A01B20Fastboot_ssl.zip from stock recovery it said,
"script succeeded: result was [1.0000000] Install from SD card complete."

Brick (error mode) after update_command: only fastboot works.

Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?

please help I can't buy another phone it's urgent...

p181153 said:
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
Click to expand...
Click to collapse
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.

@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?

haky 86 said:
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
Click to expand...
Click to collapse
Tell me where I said you are responsible of bricks ? I followed the steps you described, If you don't want to help just don't say anything

neondragon1909 said:
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
Click to expand...
Click to collapse
This is I want to know. He don't said it but I tried to flash oreotwrp from nougat and it said partition error using recovery_ramdisk. And the nocheck didn't work, so I took another nocheck for this TWRP and put the update_package command and then this

I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.

haky 86 said:
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
Click to expand...
Click to collapse
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update

p181153 said:
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
Click to expand...
Click to collapse
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater

neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
Thanks any detailled guides for that so I'll not make the things worst ?

neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead

p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use fastboot flash recovery recovery.img not recovery_ramdisk

neondragon1909 said:
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Use fastboot flash recovery recovery.img not recovery_ramdisk
Click to expand...
Click to collapse

I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything

p181153 said:
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
Click to expand...
Click to collapse
Try unlocking bootloader again

neondragon1909 said:
Try unlocking bootloader again
Click to expand...
Click to collapse
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...

p181153 said:
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
Click to expand...
Click to collapse
please help me can't restore my phone when I want to flash boot of a nougat firmware it say partition length error.....
when I want to flash recovery same...
I can't do anything I need my phone it's 3 days already I miss important calls...

This forum is called xda-developers but there are no developers or someone who really know how android works. I can't found anyone who can help me even on other forums. I have access to something which can save my phone but NOBODY know how to use it. How disapointing.

why

Stock rom npns25.137-93-14 for xt1685

Does anyone have stock rom npns25.137-93-14 for xt1685 for fastboot flash ???
I am trying to get oreo OTA update to work, and i had twrp installed, tried to flash stock recovery.img "not sure i got the right version" but update to oreo failed for some reason....
Think i maybe must flash the stock rom again and lock bootloader....

There is no image leak for 137-93-14, however using this tool on your pc you can download and flash the latest system images for your device. Install it, connect, select rescue and reboot your phone to fastboot. It will format the phone so make sure you have backups of your files.