Database Users

Beta Nougat stuck Solution (rollback)

I was stucked on nougat and cant rollback, also fastboot was not responding. I follow this steps to fix it
1) Download DC Phoenix https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix (You will need some credits)
Download a B320 rom (Example L29C432B320) and extract it (we are going to use update.app on step 3 and step 6)
2) Connect your phone on your computer on fastboot
3) On DC phoenix, select your update.app and flash it to your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Restart your phone (i recommend use "fastboot reboot")
5) Repeat steps 3 and 4 three times.
At this time DC phoenix should flash everything (including system, cust, recovery and boot) without any error.
6) Now you should be able to dload your update.app without any issue.
I hope this help you to get ride of nougat.
PSI: my english isnt good

Mod Edit

Writing XLOADER partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
20.11.2016 15:18:47 Writing device finished OK
Click to expand...
Click to collapse
At 38% is the end?
"Software install failed"
Before was ended at 5%
bluheart said:
When free solutions are working, why pay for DcPhoenix
So.many threads for one simple solution.
Lazy Mate 8 users wasting threads of xda
Click to expand...
Click to collapse
I have already tried everything,
Nougat does not get rid of it.

bluheart said:
When free solutions are working, why pay for DcPhoenix
So.many threads for one simple solution.
Lazy Mate 8 users wasting threads of xda
Click to expand...
Click to collapse
It's not about laziness, I do not want to pay for my error in installing 7.0. But I know what I'm talking about, I just can not seem to get back to Android 6.0 in any way and I'm not a beginner. I do not condemn the initiative of anyone who is trying other means.

the way we have played with our android devices over years, we know few basic things.
To recover Huawei, all you need is the latest recovery which I have uploaded in one thread.
There's no need to.play with other partitions.
Put your region firmware UPDDATE.APP in dload folder
Flash latest nougat recovery.
Boot into recovery, if it doenst flash try again.
If it goes into recovery.menu, wipe cache, off the phone.
Flash recovery again and reboot into recovery.
Thats all.
Keep flashing recovery and rebooting into it whole dload folder contains the needed file

Current version: NextL09C999B100EMUI41
Extracting partitions
Cannot create extract directory: C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\tmp\20161120_160200_UPDATE\
Extract files to directory: C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: QHC0xxxxxxxxxxxx
IMEI: 868xxxxxxxxxxxx
Build number: :NXT-L29C900B500
Product model: NXT-L29
Writing BOOT partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
ERASE partition CUST ...FAILED
Writing CUST partition with file C:\Users\tEsTeR\Desktop\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Software written
20.11.2016 16:04:37 Writing device finished OK

Reboot the device

Reboot -> Boot Logo -> Restart -> eRecovery

Hen Ry said:
Reboot -> Boot Logo -> Restart -> eRecovery
Click to expand...
Click to collapse
Do it three times. Flash the whole rom. Fastboot reboot every time. Then dload.

bluheart said:
When free solutions are working, why pay for DcPhoenix
So.many threads for one simple solution.
Lazy Mate 8 users wasting threads of xda
Click to expand...
Click to collapse
Like I said nothing worked for me and maybe this can help some users.
Your posts aren't really helpful .

B180:
by 99% demolition , bootanimation, encrypting, bootanimation, setup , :good:
With B320 no chance, but with B180 then the success.

I successfully downgraded to Kangvip b368. The procedure was as follows
First of all make sure you have nougat stock recovery .
Then download stock B320 , extract the update.app and put in the dload folder on the sd card.
Next do the dload update by pressing the 3 buttons.
Hopefully it will complete to 100%
After that do a factory reset. U may find that your bootloader is locked again. So unlock it, flash twrp and u r good to go. Flash Kangvip b368 through twrp and that's it. Try it and let us know.

Astra1 said:
I successfully downgraded to Kangvip b368. The procedure was as follows ...
Click to expand...
Click to collapse
I can attest to this. I used Huawei Update Extractor to pull the stock recovery from the nougat update.
placed the update.app from NXT-AL10C00B323 into a dload folder, turned the device off, held down all three buttons and waited for it to finish reverting, unlocked my bootloader and installed TWRP for EMUI 4.1.
Currently restoring my KangVIP NANDROID.
Thank you Astra1, enjoy your ad-free!

P9lite Bricked

Good evening everyone,
Hope to find the answer here.
I have a p9 lite vns-l33 I wanted to install Android 7 on and it has, of course, bricked!!
Since I am stuck on the screen that warns that the device is unlock and the message "your device is booting now ...."
http://www.hostingpics.net/viewer.php?id=862217IMG20161217001029.jpg
Nothing happens is the screen stays on I can not even turn off such.
I have access to fastboot, my phone is unlock. So I tried to put twrp nothing to do, to restart boot, recovery, system and believed from an official image in b100. But nothing to do comes back to the same screen.
I tried to boost fastboot on twrp but nothing to do
The I'm blocked would you have an idea?

This stuck should cause by trying trying to boot mm twrt in nougat.
Don't have dload in scard,just press volume+,volume-,and power, boot into eRecovery flash process then restart is okey
Otherwise, you can also flash stock nougat recovery , put update .app on sd card and have a dload flashing. like:
Code:
fastboot flash recovery recovery.img
If flash recovery failed/ command not allowed, unlock first
Code:
fastboot oem unlock your former_unlock_code

thank you for your reply
I do not have the update.app on the sd card because my erecovery does not allow me to install it. It just allows me to reinstall by wifi but it crashes.
For Fastboot is what I need to extract from recovery.img update.app or it does it all by itself?
Thank you for your help

You'll have to go the hard route. You'll find all the required files in the ROM section.
Download any Nougat.zip (329 worked for me, 336 did not). Unzip. You'll get the update.app.
Download the second file with all the missing apps. Do not unzip. Maybe rename to something shorter like data.zip.
Download Revolution Recovery for Nougat. Unzip. You get the recovery.img. RENAME to something like revolution.img.
Open update.app in Huawei Update Extracor. Extract recovery.img, boot.img and system.img to wherever your fastboot.exe is. It's practical to put it all in one directory so you don't have to type long paths.
Now, careful...
Go into Fastboot. If Vol- + Power doesn't work, let it boot into eRecovery, press Vol- and tap Reboot. There you are.
Open a command window in the dir with fastboot.exe and the .img files (right click, Open Command Window)
fastboot flash boot boot.img
.... OK
fastboot flash system system.img
.... sparse 1/5 or something, this takes a bit of time.
fastboot flash revolution.img
.... OK
Now DO NOT REBOOT into System. Hold Vol+ + Power while still in Fastboot. It'll boot into Revolution eventually. Tap Advanced, ADB Sideload. Swipe.
Back in your command window, type:
adb sideload second_file.zip
... working... this'll take a bit. There might be an error message like 'could not mount /data'. Doesn't matter at this point.
When done, type
fastboot flash recovery recovery.img (this is the stock recovery you extracted from update.app)
... OK
Reboot to recovery from Revolution.
Do factory reset. Note: If you don't do this last step, there will be a bootloop.
Reboot. The system should now boot up normally. At least it did for me... good luck.

THX !!!! i can boot !!!
But :
dancress said:
fastboot flash revolution.img
.... OK
.
Click to expand...
Click to collapse
when i try this , it's not work. Fastboot say :
unknown partition 'revolution.img'
error: cannot determine image filename for 'revolution.img'
I'm try : fastboot flash recovery revolution.img and after i reboot my phone with Hold Vol+/- + Power and only after my phone boot into Revolution eventually.
After this work :
dancress said:
Back in your command window, type:
adb sideload second_file.zip
... working... this'll take a bit. There might be an error message like 'could not mount /data'. Doesn't matter at this point.
.
Click to expand...
Click to collapse
But
dancress said:
When done, type
fastboot flash recovery recovery.img (this is the stock recovery you extracted from update.app)
... OK
.
Click to expand...
Click to collapse
don't work.
Finally
dancress said:
Reboot to recovery from Revolution.
Do factory reset
.
Click to expand...
Click to collapse
I don't find factory reset in Revolution ....
I'm one question why, in parametes, my android model is ?????

Ok after want to format phone with Revolution now when i'm a black screen???? why?

BenouLM said:
THX !!!! i can boot !!!
But :
when i try this , it's not work. Fastboot say :
unknown partition 'revolution.img'
error: cannot determine image filename for 'revolution.img'
I'm try : fastboot flash recovery revolution.img and after i reboot my phone with Hold Vol+/- + Power and only after my phone boot into Revolution eventually.
After this work :
But
don't work.
Finally
I don't find factory reset in Revolution ....
I'm one question why, in parametes, my android model is ?????
Click to expand...
Click to collapse
1. fastboot flash recovery revolution.img in Fastboot - sorry, mistyped. Was in a hurry.
2. Fu**ed up there too. You need to reboot directly into Fastboot from Revolution, then flash the stock recovery. Then boot into it (Vol+ + Power) before anything else and do the factory reset.
SORRY. One should not type such relatively sensitive things while already late for something

dancress said:
Then boot into it (Vol+ + Power) before anything else and do the factory reset.
Click to expand...
Click to collapse
Thx but now i can open eRecovery ....
I managed to do everything you said but now I have nothing more ....
I have at all erased and my such does not boot anymore.
I can not reinstall android with Revolution ....
I do not know what to do

Then I succeeded to have eRecovery but it does not install anything and I can not do a reset
I would like to go back to the original configuration with android 6 .0

Ok I summarize:
- I made a data format I have nothing on my phone
- I just have recovery Revolution and fastboot that works
- I can not install anything by eRecovery and Revolution crash
- I would like to reinstall original when I installed N.
Thank you for your help

plz help
Current version: VNS-L31C900B058
Extracting partitions
Cannot create extract directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\tmp\20161217_221104_UPDATE\
Extract files to directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Software written
17/12/2016 22:18:50 Writing device finished OK
AND :
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing VENDOR partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\VENDOR.img
VENDOR partition UPDATE ...FAILED
Writing PRODUCT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\PRODUCT.img
PRODUCT partition UPDATE ...FAILED
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Software written
17/12/2016 22:42:08 Writing device finished - INCOMPLETE

BenouLM said:
plz help
Current version: VNS-L31C900B058
Extracting partitions
Cannot create extract directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\tmp\20161217_221104_UPDATE\
Extract files to directory: C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM_FW OK
Extracting partition: CACHE OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CUST.img
CUST partition UPDATE ...OK
Software written
17/12/2016 22:18:50 Writing device finished OK
AND :
Device found: FUH0216B19000859
Build number: :NRD90M test-keys
Product model: HUAWEI VNS-L31
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing MODEMNVM_UPDATE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing SENSORHUB partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\BOOT.img
BOOT partition UPDATE ...OK
Writing DTS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\DTS.img
DTS partition UPDATE ...OK
Writing MODEM_FW partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\MODEM_FW.img
MODEM_FW partition UPDATE ...OK
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\CACHE.img
CACHE partition UPDATE ...OK
Writing VENDOR partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\VENDOR.img
VENDOR partition UPDATE ...FAILED
Writing PRODUCT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\PRODUCT.img
PRODUCT partition UPDATE ...FAILED
Writing SYSTEM partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\SYSTEM.img
SYSTEM partition UPDATE ...OK
Writing XLOADER partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FASTBOOT partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing FW_LPM3 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing TEEOS partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing RECOVERY partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file C:\Users\benou\Desktop\Nouveau dossier\DC_Phoenix_v22\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Software written
17/12/2016 22:42:08 Writing device finished - INCOMPLETE
Click to expand...
Click to collapse
Why did you use dc-phoenix ?!
Dc Phoenix may break your phone !
After that you have done your phone booted up right ? But he falls on a bootllop
So download b336 version, with your computer using huawei update extractor , extract recovery
After in fastboot command type :
fastboot flash recovery RECOVERY.img
After boot to recovery, do a Factory reset and wipe cache

simo255 said:
Why did you use dc-phoenix ?!
Dc Phoenix may break your phone !
After that you have done your phone booted up right ? But he falls on a bootllop
So download b336 version, with your computer using huawei update extractor , extract recovery
After in fastboot command type :
fastboot flash recovery RECOVERY.img
After boot to recovery, do a Factory reset and wipe cache
Click to expand...
Click to collapse
I use Dc_Phenix because I read in another post that it had worked for some people.
I take the B336 http://www.gizrom.com/b336-huawei-p9-lite-android-6-0-ota/ or http://forum.xda-developers.com/huawei-p9lite/development/android-7-emui-5-0-vns-l31-l21-l23-t3513816 but I do not get anything. Either the wipe does not work as it does not give me the ability to do it ...
I'm really stuck ...

simo255 said:
After boot to recovery, do a Factory reset and wipe cache
Click to expand...
Click to collapse
After boot to Recovery the phone stay to installing update 5% :
http://hpics.li/63a6275
A few minutes after the phone restarts and nothing has changed.

If youre Still on MM because the Nougat Update failed, even the Revolution Recovery wont work, in this case you need Meticulus Recovery. it even may get flashed by revolution rec, but i dont know if it uses the exactly same partition paths.
It even May help to Root your phone if your bootloader is open and you got a working recovery. The SuperSU patches the boot.img with the required ramdisk etc and reflashes it.
Your Stucking between the Unlocked message and the Logo ( Which would be shown next ) is a signal for an incompatible boot.img, otherwise ( if it is the right but broken it would get stuck in after the Huawei Logo. )
even regard that you have unplugged the phone from your Computer when you try to flash the update.app via Vol Up+ Down + Power, otherwise it aborts at around 5% or shows an error that its not possible. I Worked on the Same problem for 16 Hours till i got it fixed.
For me the following Chain worked : Installed the nougat recovery for file manager Access, created the dload folder on the external sd, and putted the b150 Update.app to it, flashed the Recovery from "vovler de nougat a MM p9 lite.zip" and flashed the oeminfo "C432OemInfo-DUALSIM-P9LITE.zip" ( relocks the bootloader ). After this the Stock Hardflashing worked, rebooted to erecovery and wiped data and cache. Unlocked the Bootloader again, flashed meticulus twrp and rooted the phone ( Systemless, to path the boot.img ) Then i flashed the flashable Firmware ( For me it was CM13 but it should work with MEDROM too )
Just think about if you flashed CM13 anytime your dataencrypten will get lost ( Then The recovery tells you its unable to Mount /data ) then the whole intern storage needs a wipe.
Some of this May work for you, but some may not. But i guess a Softbrick cant even get much worser and i dont know a hardbricked huawei, so its up to you to give it a try or not, otherwise the Huawei Support May Help you for a little Donation ( at least i think they do, ive never spoken to one of them )

WieserZ1C said:
If youre Still on MM because the Nougat Update failed, even the Revolution Recovery wont work, in this case you need Meticulus Recovery. it even may get flashed by revolution rec, but i dont know if it uses the exactly same partition paths.
It even May help to Root your phone if your bootloader is open and you got a working recovery. The SuperSU patches the boot.img with the required ramdisk etc and reflashes it.
Your Stucking between the Unlocked message and the Logo ( Which would be shown next ) is a signal for an incompatible boot.img, otherwise ( if it is the right but broken it would get stuck in after the Huawei Logo. )
even regard that you have unplugged the phone from your Computer when you try to flash the update.app via Vol Up+ Down + Power, otherwise it aborts at around 5% or shows an error that its not possible. I Worked on the Same problem for 16 Hours till i got it fixed.
For me the following Chain worked : Installed the nougat recovery for file manager Access, created the dload folder on the external sd, and putted the b150 Update.app to it, flashed the Recovery from "vovler de nougat a MM p9 lite.zip" and flashed the oeminfo "C432OemInfo-DUALSIM-P9LITE.zip" ( relocks the bootloader ). After this the Stock Hardflashing worked, rebooted to erecovery and wiped data and cache. Unlocked the Bootloader again, flashed meticulus twrp and rooted the phone ( Systemless, to path the boot.img ) Then i flashed the flashable Firmware ( For me it was CM13 but it should work with MEDROM too )
Just think about if you flashed CM13 anytime your dataencrypten will get lost ( Then The recovery tells you its unable to Mount /data ) then the whole intern storage needs a wipe.
Some of this May work for you, but some may not. But i guess a Softbrick cant even get much worser and i dont know a hardbricked huawei, so its up to you to give it a try or not, otherwise the Huawei Support May Help you for a little Donation ( at least i think they do, ive never spoken to one of them )
Click to expand...
Click to collapse
I LOVE YOU
i get stuck the last night trying to put nougat, but i downgrade to mm and get stuck in huawei logo and no led,
only flash supersu and all worked good again :$

spadyrus said:
I LOVE YOU
i get stuck the last night trying to put nougat, but i downgrade to mm and get stuck in huawei logo and no led,
only flash supersu and all worked good again :$
Click to expand...
Click to collapse
I have the same issue..but the problem with my device it's worse..when I connect my phone to PC it says: Fastboot2.0, and it's stucked on a blackscreen 4ever.. any ideas what can I do? Thanks!

I'm also on the sh** with my phone. Stuck on your device is booting now...
Can't get erecovery or fast boot or anything. Can't even turn off the phone.
Sent from my ONEPLUS A3003 using Tapatalk

I am in the same situation, bootloop, and i was able to enter bootloader and unlock it, but now can't enter anymore. Phone wasn't turning off then i managed to drain battery, but I still can't enter bootloader. when i press volume - and power the yellow menu appears and if i press volume up to enter eRecovery it freezes. If try to boot normal the yellow screen with the unlock message appears and then the mobile hangs. How were you able to solve this?
thanks

Hello,
When you pressed Vol- you plugged your phone on the computer or not?
Because to access fastboot it is compulsory to do the manipulation Vol- with the telephone connected to the PC

How to get OTA update with my tablet rooted? My tablet is yoga tab 3 plus.

My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?

zkn1021 said:
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
Click to expand...
Click to collapse
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version

matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.

I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.

zkn1021 said:
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
Click to expand...
Click to collapse
zkn1021 said:
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
Click to expand...
Click to collapse
Well first unroot by flashing boot and system, then install update in Lenovo recovery. Yes it's possible to do that. Then when the update installed successfully you can root again with TWRP and SuperSU.

brothers, I skipped system verifying by editing updater-script, but the OTA still failed because signature verifying failed.
Anyone knows how to skip signature verifying?
If we can skip that, we may install ota update package manually while the device is rooted.

matshias said:
the easiest way is to restore the boot and system partition .
...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat

DGolovin said:
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
Click to expand...
Click to collapse
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.

matshias said:
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
Click to expand...
Click to collapse
Thanks for eхplain. I have downloaded your backups of 734th firmware for Lenovo Yoga 3 Plus F already but new knowlege will not be redundant

Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you

Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs

NtahX said:
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Click to expand...
Click to collapse
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
dasinflames said:
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
Click to expand...
Click to collapse
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.

matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash system system_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.626s]
sending sparse 'system' (516880 KB)...
OKAY [ 18.443s]
writing 'system'...
OKAY [ 7.726s]
sending sparse 'system' (507198 KB)...
OKAY [ 18.163s]
writing 'system'...
OKAY [ 7.812s]
sending sparse 'system' (511833 KB)...
OKAY [ 18.332s]
writing 'system'...
OKAY [ 7.876s]
sending sparse 'system' (514911 KB)...
OKAY [ 18.410s]
writing 'system'...
OKAY [ 7.345s]
sending sparse 'system' (514937 KB)...
OKAY [ 18.282s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (511997 KB)...
OKAY [ 18.328s]
writing 'system'...
OKAY [ 22.033s]
sending sparse 'system' (156572 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 17.717s]
finished. total time: 194.195s
c:\adb>fastboot flash recovery recovery_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 2.907s
Since I already flashed boot.img yesterday, continue with system & recovery. I didn't know that Download mode will only shows Lenovo logo. Normally it will shows what running on the background. Did as told and manage to recover. Sadly I've wiped cache & data in Recovery yesterday, now back to square 1. But at least better than bricked device. Thank you.

matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
the only way that my tablet can to be recognized in my computer is with sideload. I'll try with that method.
thxs!!
PS: I used at the end the Multiflashtool and now my tablet works perfectly
if someone has the parallel problem, here is the solution: http://www.mediafire.com/download/58upc51o93ux2f4/Archivo+StargetDawn.rar
just install and execute the multiflash program.
greetings

matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!

zkn1021 said:
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
Click to expand...
Click to collapse
Well it seems you have to request the backup again. system.ext4 is a file based backup. This will not restore to a 100% original system image. The person who provided this for you has to run it again and select "system image" instead of "system" when creating the backup. This will then be a binary copy of the system partition.
Once you have that you should create a backup using TWRP on your own device with boot and system image selected onto an external SD card. Don't forget to boot TWRP with system left read only. Then you replace the *.win* files (also the .md5 files) on you SD card with ones you get from this person files. Then reinsert the SD card into the tablet and select restore in TWRP. Then the two partitions should be original if the person you got them from didn't modify it somehow.
I am not sure which format TWRP uses to store these partition images but if the above doesn't work we'll figure out how to extract it.

matshias said:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
hello iam on s000689 and i have a hard time trying to find that recovery image... can i just you S000725 and then not have OTA updates?

HELP! MLA-TL10 bricked/bootlooped?!

I tried to update stock phone via Firmware Finder from B170 to B360. Downloaded fine and asked for restart. Phone said it was updating but froze at 5% and restarted by itself and bootlooping.
Holding Vol+ and power on leads to "EMUI installing update..." screen, then "Software install failed!" with only option to
Reboot system now
Rebooting takes phone to Huawei eRecovery with options
Download latest version and recovery
Reboot
Shutdown
Download and recovery ends with "Getting package info from server" which eventually fails
I can enter Fastboot & Rescue Mode, but phone is LOCKED (in green text) so cannot flash
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 532676608 bytes
sending 'recovery' (41787 KB)...
OKAY [ 1.471s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.487s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 532676608 bytes
sending 'boot' (33249 KB)...
OKAY [ 1.166s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.197s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 532676608 bytes
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Also, the phone is not being recognized by HiSuite latest version (8.0.1.302), and not supported by HiSuite System Recovery!
I've been reading through these forums and Googling but nothing is helping! :crying: Phone is out of warranty as it's a hand-me-down. Are paid options like DC unlocker the only way?

Anyone? Or is this phone too outdated now?

I managed to get microSD card for phone but still having troubles. I put UPDATE.APP into dload folder on root of microSD and boot with three button press but installation gets stuck and fails at 42%. I've tried with all FullOTA-MF roms from Firmware Finder, no success.

if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2

zaabolla said:
if your bootloader is unlocked see this post: https://forum.xda-developers.com/showpost.php?p=74624117&postcount=2
Click to expand...
Click to collapse
It was locked (getting the 14 day message before) but I tried to unlock again through the EMUI website and it worked!
So I successfully flashed TWRP 3.0.3.0. but I cannot install zips, encountering this error for all versions B360, B358, B356, and B170.
Code:
Installing zip file '/external_sd/dload/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: No such file or directory
Removing unneeded files...
Patching system files...
Removing empty directorys...
Unpacking new files...
add link type file...
write radio image...
error:oemsbl version write error!
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from zip failed
[COLOR="red"]Updater process ended with ERROR: 7
Error installing zip file 'external_sd/dload/update.zip[/COLOR]
Updating partition details...
...done
I tried the steps in that post above but there are issues when copying the contents to the device as process hangs at file system.ext4.win000, saying 3 minutes remaining forever, eventually stopping the process itself.
Any further steps? I feel like I am one step closer to unbricking this device though.

i don't know what are you doing like that
flashing official rom is with original recovery not with TWRP recovery
with TWRP you can flash only custom roms like lineage, or restore backup rom
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
and copy backup files to an sdcard with PC, and try the new TWRP

Oh, hmm, silly me then
Anyway, the restore worked fine when put on microSD card. Reboot failed stating an error in Chinese text (don't know what it says), and keeps rebooting into TWRP.
System not booting anyway so flashed LineageOS.zip but during the process, log showed "failed to mount /product (invalid argument)". Reboot phone and it's stuck on Lineage OS boot animation for over 30 minutes
Updated TWRP to latest 3.1.1-0

Changed the filesystem to f2fs and the TWRP backup in that post booted! Everything seems to be working except the phone is branded as CAN.
Flashing any version of stock MLA-TL10 firmware with stock recovery still fails at 42% just like before though. And flashing Lineage OS still hangs on boot animation like before as well.
I think I'll just leave the phone as is in stock Android 6.0, at least it's useable now

Flashed TWRP 3.1.1-0. The log says Failed to mount /product (invalid argument). Never had this error before but everything seems to be working fine.
Just got an idea, if anyone can kindly provide a TWRP backup I can try restoring to that.

i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked
---------- Post added at 05:32 PM ---------- Previous post was at 05:32 PM ----------
i am trying to restore twrp backup but there's a problem
Failed to mount /product (invalid argument).
Failed to mount /cust (invalid argument).
and there's no file name cust and product in offical firmware update.app and any other i had try 3 or 4 firmware's but didnt find any file name in update.app using huawei firmware extractor can you guys please help me out? my phone is stuck on bootloader unlocked option power button for continue col up button for ercovery
my bootloaders are unlocked

accidentaly formatted partition system H870 FASTBOOT only

hi guys, can you help me, please?
I accidentally formatted the system partition from fastboot.
->fastboot format system
I'm trying to flash it again. I downloaded the original ROM, extracted it into system.img and when i try to flash it I get:
->fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
How is that possible? Can i fix that?
Additional info: unlocked bootloader, when i reboot the phone is always in the fastboot mode.
Thanks in advance to everybody

Solved
Just enter in download mode and install kdz with LGUP! Solved!