Database Develop

[ROM/GUIDE] Full Updates / Back to Stock Files via TWRP (A2017U, A2017G, A2017)

READ, READ BEFORE PROCEEDING
YOU'VE BEEN WARNED​
Ok, I wasn't going to create a new Thread for this but is really needed to keep this a little separate but in the same thread, so here i'll be updating base on current updates for each variant this Thread will contain Current Updates and as for now current updates are :
REQUIREMENTS :
- Plain and simple, you just need TWRP. Either via @tenfar or @tennear Tools or happens that you already have TWRP install.
ROOT:
If you are UNLOCK BOOTLOADER proceed with STEP 7, if not you'll need to use @tenfar Modded boot image base on your system update to get root access.
Each steps will contain 2 files which are:
1- BootStack
2- System+Boot
Q: Why 2 Flashable Zip Files?
A: Well cuz a lot of us know you CAN use / try other variant system image , i have separate what is just needed to for that purpose, meaning if A2017U want to give a shot to A2017G or A2017 software you will just need to Wipe Cache -Dalvik - Data and Flash the A2017G or A2017 Flashable system file or vice-versa.
The Bootstack just need to be flash ONCE per variant, the A2017G CAN'T use A2017U Bootstack (well you probably can but IS NOT RECOMMENDED) .
- A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)
- A2017.B10 (Post # 4 or Click Here)
- A2017G.B08 (Post # 3 or Click Here)
- A2017G Flashable Stock Recoveries (Post # 5 or Click Here)
-------------------------------------------------------------------------------------------------------------------------------
I'll be Updating this thread base on current Updates and please let's keep this thread clean and on-topic
-------------------------------------------------------------------------------------------------------------------------------

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017UV1.1.0B35 NOUGAT Update
-----------------------​
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N) / B19(N) / B25(N) / B32(N)
-----------------------------------------------------
Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important
1- Download the following zip files
- A2017UV1.1.0B35_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B35_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (Wipe Data if you aren't updating from B29-MM or B15-N)
5- Flash A2017UV1.1.0B35_bootstack_by_DrakenFX.zip( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- FlashA2017UV1.1.0B35_systemstock_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT AND KEEP TWRP after flashing Stock System, download SuperSU v2.79 (Or your preferable Root method)
WARNING - WARNING​NOTE : YOU MUST FLASH SUPERSU OR VM-VERITY ZIP, IF YOU WANT TO KEEP TWRP, THE B32 UPDATE HAVE STRIP BOOLODER
8- REBOOT and Enjoy Nougat B35 Rooted or Just Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
.
.​

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017G.B09 Update ( Files Provided by @tron1 )
-----------------------​
-----------------------------------------------------
UPDATING FROM B01, B02, B03, B05 , B06 or B08 Rooted or Stock
-----------------------------------------------------
1- Download the following zip files ( Thanks @tron1 for making the files )
- ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
- ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B09 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
. Here's the B08 Files in case are needed
. TWRP_A2017G.B08.BootStack_By_DrakenFX.zip
.
. TWRP_A2017G.B08.FStockSystem_By_DrakenFX.zip
.
..................................................................................................................................................................................................
.
. Here's the B06 Files in case are needed
. ZTE_A2017GV1.0.0B06_BootStack_by_DrakenFX.zip
. md5 : fa64983faaf4d37a26772dab53a61ff2
.
. ZTE_A2017GV1.0.0B06_StockSystem_by_DrakenFX.zip
. md5 : 3b34ac0d1c81248454666b9ae644da16
.
.................................................................................................................................................................................................
.
. Here's the B03 FIles in case are needed
. ZTE_A2017G.B03_BootStack_by_DrakenFX.zip
. md5 : ae0f260a9bd7ee486704842bc9efa202
.
. ZTE_A2017G.B03_StockSystem_by_DrakenFX.zip
. md5 : 5086d5a0d73e07a257b9f4cb4b7c7631
.
..................................................................................................................................................................................................
.
.
. Here's the TWRP B06 Flashable Stock Recovery
. TWRP_B06_StockRecovery.zip
.
. Here's the TWRP B08 Flashable Stock Recovery
. TWRP_B08_StockRecovery.zip
.
..................................................................................................................................................................................................

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017.B10 Update
-----------------------​
-----------------------------------------------------
UPDATING FROM B09 or Below Rooted B20
-----------------------------------------------------
1- Download the following zip files
- ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip
- ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B10 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
.B10 & B11 Flashable TWRP Files can be found here also :
https://www.androidfilehost.com/?w=files&flid=118419
.
.

----------------------------------------------
A2017G
Flashable Stock Recoveries
----------------------------------------------
Folder with A2017G Stock Recoveries B06 , B08 and B09
TWRP Stock Recoveries Flashable Zips
----------------------------------------------​

Last Reserve for something else thread related

:good:

@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.

TheRoyalSeeker said:
@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.
Click to expand...
Click to collapse
System Dump for which variant? i know A2017G and A2017 are .dat but that can be converted to .img very easily, if you have windows you can use this Android DAT/IMG File Unpack and Repack V 2.0 , that's what i use to convert .dat to .img.
If you need more info just PM.

Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.

AllAboutAndroids said:
Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.
Click to expand...
Click to collapse
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Let me try that now and will let you know asap!

AllAboutAndroids said:
Let me try that now and will let you know asap!
Click to expand...
Click to collapse
Let's us know I'm mins away from doing this but NEED root!!

S8ntsHaz3 said:
Let's us know I'm mins away from doing this but NEED root!!
Click to expand...
Click to collapse
Noooooope. I went back to Stock Recovery somehow...even though I had TWRP all along.

Sad days

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Trying this again!
S8ntsHaz3 said:
Sad days
Click to expand...
Click to collapse
Got TWRP back. I'm going to attempt the method above and let you know!

AllAboutAndroids said:
Trying this again!
Got TWRP back. I'm going to attempt the method above and let you know!
Click to expand...
Click to collapse
Awesome thanks !!!!

S8ntsHaz3 said:
Awesome thanks !!!!
Click to expand...
Click to collapse
Hmmm stuck at "Please Wait..."

Which method did you use to obtain root/TWRP?

S8ntsHaz3 said:
Which method did you use to obtain root/TWRP?
Click to expand...
Click to collapse
Using:
D:\Downloads\axon7root-us-b27>axon7root.exe -p 3 -r
That only gave me TWRP. I still can't get Root to work on the B27 Update.

Update p9 lite nougat ota "s ​​no officials

I was given a link. cronociclope Senior Member
I tested it. 100 for 100 on :cyclops:
It is necessary to return or to be emu 4. (MM).
Have the unlock code. (Bootloader).
Have downloaded the full firmware (2 files) Full-ota-mf-pv that twrp can install.
And have downloaded the firmware update, full full-ota-mf (no pv). (3 files).
pc+ winzip+ twrp (chinois), carteSD,
regard
https://www.youtube.com/watch?v=oTBvz71l4s0&t=1s
So on the pc, with winzip. Because with winrar for me it does not want to transfer large volumes. :
_ Downloaded a firmware emui 5. Full-ota-mf-pv for your device (it's a firmware in two files, which twrp for MM can install).
_______ update.zip and datafull hw-eu.zip
Uploaded emui update 5. Full-ota-mf not written pv and that does not share ota. But we want it. : (this is a firmware in three files).
________update.zip, public file and data hw-eu.zip
_ Open the update file of the pv version and delete the update.app, then open the update of the no pv version, and transfer update.app in the pv version.
Do the same thing with the datafull file hw-eu and data hw-eu.
In the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init :cyclops:
_copy your two new .zip files onto the SD card.
_start the phone in recovery twrp MM.
_ Go to wipe, advanced wipe, check all except well-sure sd card, and wipe to wipe.
_allez to install, installed both zip, it will show you two errors ignore them.
_allez to reboot, reboot system.

Hello
in the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init

regard
2017.09.20 VNS-L21C432B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/filelist.xml

B383 was released on Firmware Finder.
Install the OTA one (mb version).

Johnny TDN said:
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Click to expand...
Click to collapse
yes, full-ota-mf
2017.09.21 VNS-L21C432B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/filelist.xml
and
your pkg install full-ota-mf-pv vns-l21c432b371
2017.03.21 VNS-L21C432B371 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/filelist.xml

got an ota update b383.
failed at 32%
gg huawei

Johnny TDN said:
got an ota update b383.
failed at 32%
gg huawei
Click to expand...
Click to collapse
strange 32%
with this method, I can even install p10 lite.
can be checked, the update.app that is the good you place in the update.zip
go to wipe before installing update.zip edit this seems important.

2017.08.30 VNS-L31C432B390 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip

If I am rooted and I have TWRP, can I install the update?

I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version misc) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
Reboot
It's ok
http://oi63.tinypic.com/29cncx4.jpg

Paolo83 said:
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
It's ok
Click to expand...
Click to collapse
Hello
Hello
ALSO Product.img of update.zip?
Because, he does not want, that's why, I always go to MM.
bad reading sorry,

Chisetdel31260 said:
Hello
ALSO Product?
Click to expand...
Click to collapse
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder

Paolo83 said:
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Click to expand...
Click to collapse
I've already asked him to hassan and he added to install twrp product image, but its not working.
I tried to copy pasted already with a file explorer, but every time, things break. (either with force close parameters, or force close camera, or boot-animation disappears and becomes android).
there is always something wrong.
Yes, we leave from MM everything is ok, clean.

You have to use solid Explorer It works!! With this procedure In five minutes I upgrade to last version

Managed to update to b382.
Seems stable and somehow, the battery is much better o^o

go
time to download, c432b390.
And to transfer everything in the b370 zip, then to go back to c432b160, I installed it correctly.
so this version is emu 5.0.1, patch September 1, version kernel 25 aug and baseband 286.
as you can see.

Updated to b382 vns-l21.
Problem : No notifications on Hangouts. I must go to my friend's chat in order to see the notification.

I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:

Doble_f said:
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Click to expand...
Click to collapse
Hello
yes, I add it.
you just have to open the folder data / hw_init /
sorry,
for my bad English.
yet I do a great deal of effort.
for that google translator, does not blow up the planet.

Hi Chisetdel, I share this video, which includes the files OEMinfo.zip, Update.zip and Update_data_full.zip modified and ready to install via TWRP directly from EMUI 4.1 for the L21 (C432B382/EMUI 5.0.1) and L23 (C605B372/EMUI 5.0.1): here
Greetings

[How to Root] [TWRP] Huawei P smart - FIG-LX1

[How To Root] Huawei P smart - Android 8 - EMUI 8.0.0
The Rooting was tested by me on this device:
Model: FIG-LX1
Board: FIG-L31
Build No.: 8.0.0.128(C432)
EMUI 8 - Android 8
"free device"
Whether the following instructions are based on provider-branding is applicable, I could not test
and therefore advise against it.
Warning: Rooting will void the device warranty. Be careful with the newly acquired root rights.
I recommend this only to users who are fit in handling a custom recovery.
This TWRP is not yet perfect and should be used with caution.
Make sure to backup all data on the SD card. (PC, stick, or HD)
Create a backup with the Huawei Backup App.​
Make sure the bootloader is open.
OEM and FRP unlocked,
in the device settings, OEM unlock and USB debugging enabled.
The stock kernel is mandatory.
This is flashed in fast boot mode/ bootloader:
If the device is unroot, it does not need to be done.
fastboot flash kernel kernel.img
(KERNEL.img.header must also be in the adb folder.)
This steps must be followed exactly:
Factoryreset in recovery.
Flashing TWRP in the bootloader: fastboot flash recovery_ramdisk FIGO.img
Boot to TWRP and change the file system of the external SD card:
Wipe> Advanced Wipe> Micro SD card> Repair or Change File System> Change File System> FAT:
Execute with "Swipe to Change".
This change deletes all data on the SD card.
Switch to the Mount menu and unmount all partitions. (remove all hooks)
On the internal and external memory.
Then create a backup:
Backup> Select Storage> Micro SD card> select all partitions,
except cache. Then reboot the device into the system and copy the Magisk Zip to the SD card.
Then install in TWRP: Install> Select Storage> Micro SD card> Magisk-v16(1600).zip> Swipe to confirm Flash.
Is there an error message, installing this Zip via MagiskManager App.
Reboot and if not available, install the MagiskManager App and check the root.
The routing is now complete.
Install Magisk modules only with the app; never with TWRP.
Important:
Never wipe the cache or perform a factoryreset.
[*]Please do not experiment with Xposed. This leads to the bootloop and the Firmware must be completely reinstalled.
[*]Please with each backup, make sure to unmount all partitions again. (internal and external)
Update via Firmwarefinder:
Start Firmwarefinder App and select the appropriate update.
Then on GET AN UPDATE THROUGH DNA.
Then on WITHOUT IMEI.
Availability is displayed.
Now click on REGISTER UPDATE and the registration is displayed.
Then click IN-APP PROXY.
Now activate DNS in the router, enter 81.177.139.39 as addresses and save.
Now go to the WLAN settings on the phone, touch and hold the active connection.
Then change to Network in the menu.
Under Proxy-manual, enter localhost and port 8080 as host names for extended options.
Now only set the IP setting to DHCP. Now start the eRecovery.
Vol.+ and Power with PC connection
There on "Download latest version and recovery".
Then click on "Download and recovery" and register there under Select WIFI.
Now the update is displayed and can be started.
When rebooting, the device lands in the bootloop,
execute a factoryreset in the recovery.
After the update reboot and all changed WLAN settings, also in the router
and reboot it again. If you don't, it'll be over by the time
next OTA update is displayed again and again, since the authorization remains in memory.
Themes-Fix, How to Unbrick, FRP-Unlocking and Bootloader Unlocking I described here. Or follow this thread.
https://www.android-hilfe.de/forum/...t-how-to-root-twrp-root-anleitung.866625.html
It is easy to translate with: https://www.deepl.com/translator
All downloads are here: http://www.mediafire.com/folder/7qdu5je08caya/FIGO
Attention: Changing the oem.info can
cause the phone to lock. OEM/FRP=LOCK
Thread Update 2017-03-28:
A new TWRP is now available. It is version 3.2.1-0.
Original Chinese developer version.
Instructions:
First perform the Huawei data backup.
Flash TWRP per Adb as usual.
Then switch from Chinese to English.
Then assign write and read rights by removing the hook in wipe menu.
Now for security, create a backup without data.
Then Format Data.
Create a new full backup including data. This is possible now that the
formatting is the size of Data = 0.
Now reboot the device and set it up completely new.
Now there is a new and configured data partition.
Then turn OEM and USB back on and boot to TWRP.
Then create a new full backup.
TWRP is now fully functional. Only the MTP mode does not work.
http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img
Good luck!
My special thanks for this original Chinese TWRP for free use,
goes to: "weibo.com/xinkid520", FIRE Team(Developer) and "Team Win Recovery Project".
​Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.
Many thanks to: funkyhuawei.club, Jrummy, Chainfire, Stephen (Stericson) +
Jmz Software, TWRP, osmOsis,Topjohnwu and Huawei Technologies Co., Ltd 华为技术有限公司

it's alive!!! FIGO-LX1C10B120
Men I love you!!!

Thank you monster!!!! [emoji8]

thanks !! are we getting a Huawei P smart forum here soon ??

Themes
I cannot apply themes after Root ?

Hello,
could you also provide the vendor.img?
Would be really nice.
Thx in advance

@enjac
Forum habe ich beantragt.
I have applied for a new forum.
@JahSound77
Flash the cust.img. Then it works.
@Destroyer706
Vendor kannst Du nicht mit adb flashen.
You cannot flash Vendor with adb.
Hey, guys, I got a brick. Can someone save/extract the "kernel. img"
from the 122. Or can someone from the sources compose a kernel. img? I don't have a linux pc.
:crying:

I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img

Themes
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .

Destroyer706 said:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Click to expand...
Click to collapse
I uploaded it now. :good:
https://mega.nz/#F!EplhBBzS!UUgXBRC9DRaExP9HY57FKQ

JahSound77 said:
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Click to expand...
Click to collapse
You must be logged in to the google account and huawei id. Outside Asia. If it doesn't work, wait one or two days. It'll probably work then. It was like that with me.

Thx. I am already compiling the kernel from source

Destroyer706 said:
Thx. I am already compiling the kernel from source
Click to expand...
Click to collapse
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....

ChinHon said:
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
Click to expand...
Click to collapse
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.

Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).

Destroyer706 said:
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Click to expand...
Click to collapse
There is no boot. img in the 121 firmware anymore. Only the kernel. img. I flashed that. So I have the bootloop and need the img from 122, so I thought you might be able to extract it from your device.

steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
Not included in the UPDATE. APP anymore.
See filelist:

Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8

steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
I found another update in the net. Here the oeminfo as a self-extracting archive.
https://mega.nz/#!5gcygYLL!Wdlvg5jUo2hv6L7DBtAVT1-0z_WRmSBLuBin7iUGjig

Destroyer706 said:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
Click to expand...
Click to collapse
Hey bro, FIGO's alive again. Thanks a million. You're the best.
:good::good:

custom [P9Lite] C636 base P10Lite

custom rom Just for C636 SDN BHD
Malaysia,Indonesia,Thailand,Philippin,Cambodia,srilangka,Australia, other n specific C636 about
=====================
A= required:
=Enable oem unlock.
=Unlock bootloader .
=====================
Warning:
= after device unlock bootloader do not factory reset in setting advance. Mybe device bootloop after use custom..if not..developer options oem hide disable..n frp locked
Repair: run cmd ..(fastboot oem relock type ur password unlock) enter..go developer show enable oem then unlock bootloader again ..
====================================
B= unroot ur mobile
= supersu: https://forum.xda-developers.com/showpost.php?p=63615067
= magisk :https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
= flash use twrp n then format data
=========================
C= change data f2fs.
=Use twrp made by OldDroid
https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
= how to f2fs? Go twrp wipe format data, type yes. N thn reboot recovery.. n check data file system ready f2fs is good. but if not changed f2fs! U need change manual from ext4 to f2fs.
After change data, recommend reboot recovery again and check data..
=================
D= flash custom
= select root one only n kernel.
= welocom
===================
E= ur mobile home menu screen
=Login play story n then go twrp wipe dalvik/ ART cache, cache only..reboot.
=magisk safety net..check safety then usb debugging developer options enable ,touch button right , open magisk settings disable magisk hide n enable again..then check safety.
= but if you want permanent magisk safety..
Try it extract my custom zip, look folder
Go twrp install :
magisk Huawei propfix.zip
Magisk permissive.zip
Busybox.zip.
=======================
Bugs: sometimes,,, after installed app not show menu..restart device showing, it's a small matter.
will be fixed soon
==============
if you have a problem!? please comment.
===============
Extra = Go back data defaults ext4!?
Format data twrp by oldroid
Then flash twrp: https://www.youtube.com/redirect?q=...3MzQ1OUAxNTI1MTg3MDU5&event=video_description
Use pc lunch batch file. Or extract zip put img file external sd .twrp find img .select install img, select recovery flash , n reboot recovery format data again data is change ext4
= back to official : https://forum.xda-developers.com/hu...ota-p9-lite-upgrade-rebrand-tools-pc-t3778839
Information: Stable n faster
=======================
approximate mount custom:
vendor: 60% base p10 lite n Vulkan
Production: 80% base p10 lite ,high quality camare n bokeh .but apps mate 9 camera
System : 100% base p10 lite
Cust: 100% base p10 lite
Version: 100% base p10 lite
=======================
manufacturer 12 April/ 2018
Solved 1 may/ 2018
Download: https://mega.nz/#!oD5z2Bpa!2b4XWfsQk7odih4vR3ToI-H8Xg5iCP8Xc9rRzzfnSRk
=====================

Huawei P9 potentally bricked?

Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool. I succesfully flashed it without complications. But then my luck went out and i maybe have softbricked my phone. Here's how it happened.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix. After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot. So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery. After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted. It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking. I did go to sleep. Now its day 2 and i am writing here with my phone at the side in eRecovery. This time i didnt wipe anything else than data and the cache, also i did a factory reset. I easely can go in the OS again, but then i still would get the false directory without any files and couldnt load OpenGapps and the network fix or the BASE ROM, because i know now that it isnt a problem with base rom. I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it!
Many regards!

Since you have followed the re-branding guide by @Tecalote, why didn't you follow also his instructions for going back to stock (Oreo or even Nougat)
https://forum.xda-developers.com/showpost.php?p=77161314&postcount=3
Same things have also been asked in the Open Kirin thread, see e.g.
https://forum.xda-developers.com/showpost.php?p=77589852&postcount=79
Good luck, as long as you have Fastboot and eRecovery, your phone is not dead

Restore your phone and try to be not confused
Bumo Gaming said:
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix.
After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot.
Click to expand...
Click to collapse
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Bumo Gaming said:
So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery.
Click to expand...
Click to collapse
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
Bumo Gaming said:
After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted.
It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking.
Click to expand...
Click to collapse
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
Bumo Gaming said:
I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it! Many regards!
Click to expand...
Click to collapse
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.

Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem

zgfg said:
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
Click to expand...
Click to collapse
SD Card is easier, but HuRUpdater works also from internal storage → and it works also from USB (with OTG cable)
Only problem, TWRP hasn't support for encrypted data yet - but the steps with format data and then copy with PC in Windows Explorer the required files to internal storage, should solve this. ( for this case)

Tecalote said:
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Click to expand...
Click to collapse
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
Click to expand...
Click to collapse
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
Click to expand...
Click to collapse
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
Click to expand...
Click to collapse
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards

Bumo Gaming said:
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Click to expand...
Click to collapse
Many thanks for your detailed feedback! :good:

slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine.. what i did in end is that i changed oem info via hwota to EVA-L09C636 and put again chinese EVA-AL10 oreo.. now my android system have lots of problem, no aps, keyboard was gone (only chinese kb and somehow i managed to put en). Everything is messed. Now problem gets bigger: OEM unlock is grayed in developer options, so i cant unlock bootloader (and in fastboot mode, bootloader and FRP are locked), so there is no way to put TWRP and everything look bricked (( Also dload update always fail at 5% with any room i try... Pls help me, i just want to go back to original nougat, like when i bought and forget chinese brand and oreo... Thanx in advance
droid info app:
Model: EVA-L09 (EVA-L09)
Manufacturer: HUAWEI
Baseband Version: 21.258.09.00.030
RIL Version: android infineon balong-ril 1.0
Build Number: System 8.0.0.046(0EET)
Build Fingerprint: Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07111806:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: O (8.0.0)
SDK: 26
Click to expand...
Click to collapse
zgfg said:
First and most important for any further analysis, please clearly write on which exact build name/number you are
Can you post a screenshot of Setting/About
Click to expand...
Click to collapse
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine..
Click to expand...
Click to collapse
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl

Tecalote said:
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Click to expand...
Click to collapse
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?

slayernn said:
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
Click to expand...
Click to collapse
Yes, this is really a slow download, but no - it's the only place where you can get Firmware, which is installable with dload method!
If you create a User on this Site, download is faster, but needs even some hours....

@slayernn
When your Download is ready → you have: Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0 EMUI8.0.0 05014GSG androidhost.ru.zip
Rename it to: Huawei P9 EVA-AL10 8.0.0.528.zip
→ unpack/extract zip, then you have the folder: Huawei P9 EVA-AL10 8.0.0.528 - the folder contains:
ReleaseDoc
Software - go inside this folder, there is: SDupdate_Package.tar.gz → unzip/extract it, then you have the folder: SDupdate_Package.tar - this folder contains:
SDupdate_Package.tar - unzip/extract it, then you get finally the folder: SDupdate_Package - and this folder contains, what we need, the folder:
dload
Inside this folder you find the UPDATE.APP - and probably one or two additional folders with another UPDATE.APP (for the location, example: update_EVA-AL10_all_cn.app)
Now you have two possibilites
A)
1) Flash first the UPDATE.APP with dload method → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
2) reject SD-Card, delete the previous update.app and copy the second update.app (update_EVA-AL10....) into dload folder → rename it to: UPDATE.APP
3) In EMUI-Recovery go to Reboot and during restart press Vol+ and Vol- to force update:
4) now second UPDATE.APP will be flashed → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
5) delete second Update.app in dload folder and copy the first UPDATE.APP again into dload folder and flash it once again with dload → once you have done this and phone reboot automatically, press again VOL+ to enter EMUI-Recovery
6) Make Wipe Cache and Factoryreset
7) Phone should boot → and be able to enable OEM-Unlock → then a downgrade to Nougat and rebranding would be possible (ask me for the steps, before doing)
B) Second possibility (costs about 15 EUR, but it is easier and probably better)
Buy from DC 15 Credits (=15 EUR) from here: https://www.dc-unlocker.com/buy
Download DCPhoenix Software v63 - extract it and open DCPhoenix, log-in to your Account
In the first field above choose the big, first UPDATE.APP
on Customation field select the second UPDATE.APP (no need to rename for DC)
Flash it → additional you can change oeminfo on second tab....
Wish you success

@slayernn
I answered your PM → forgot to ask: Can you please tell me each exately name of the second two folders (with the two other update.app)
Thx

@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9

Tecalote said:
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Click to expand...
Click to collapse
First of all, thank you Tecalote on all your tutorials and support in every step, without you restoring phone to original stock state would be imposible.
In short, i will explain what problem i had and how it is fixed.
History:
My P9 EVA-L09 was changed to EVA-AL10 and oreo, after few stupid mistakes in a rush, i changed oem info to EVA-L09c63.. and re-update AL-10 files in final step from hwota7. After that i got semi bricked device, oreo with damaged build number, oem info, and most important bootloader/frp was locked and couldnt change oem unlock (it was grayed). After that i tried many different fw/roms via dload method without success until Tecalote suggest downloading Huawei P9 EVA-AL10 8.0.0.528. UPDATE.app of that pack always worked and it was crucial later, but next dload EVA-AL10_all_cn didnt work, so i was at beginning again, with damaged oreo.
What i did later and steps that restore my device to stock nougat:
Next thing i did is taking DC-Phoenix + HCU timed license after which i tried to change oem info, but in dc-phoenix there was no EVA-L09 so i used EVA-L29 and tried some appropriate files to upload. It ended with errors and phone was dead bricked.. cant power on/dload/recovery but dc-phoenix still recognise it in fastboot so then i tried to upload EVA-AL10 8.0.0.528 again and it worked, during period of update device was unlocked and i realised i could use hwota7 tool during that time, just to unlock bootloader with code, so i did and it was successful, was it clever? dont know! What i got now is old oreo with f****d oem info / build etc but unlocked. Next thing i did is to use HCU program and in repair cdma tab, i changed model/vendor/country to EVA-L09/hw/eu! Right after that uploaded EVA-L09_C432B390_Firmware_France_Ger... and update_EVA-L09_C432B390_hw_eu from dc-phoenix and it was successful! Now i got nougat (poor without camera and so) and original EVA-L09 model name. Next, Tecalote send me HWOTA download link and steps to take https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3 and after that, phone was fully restored to original state and everything is working perfecto. It took me 2-3 days of work, many errors.. in a moments i was thinking that device is completely bricked and want it to throw in trash can. Never give up..thats point Best regards!