Database Develop

[GUIDE - L31] How to change C432 to C636 in order to get B361 Nougat

Hi, everyone.
I did this to my device and succeeded, so I thought I'd share the procedure with you, if you want to do so, too.
IMPORTANT: I am NOT responsible if you damage your device by following this guide; I am an XDA member like you and I am just sharing a guide that worked for me.
I am assuming you have all the Huawei and ADB drivers installed on your computer and know some basics on how to do these things; if you have no clue where to start, don't risk.
First of all, you need to be in C432B161.
You need to download:
1. This toolkit https://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873 and relative package for C432;
2. OEMinfo for C636 you can attached to this post (thank you to the creator);
3. B170 update.app from C636 you can find in this package (1) http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66846/f1/full/update.zip
4. the firmware package and data files (B361) you can find here
(1) http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1258/g104/v77171/f1/full/update.zip (2)http://update.hicloud.com:8180/TDS/...cseas/update_data_full_VNS-L31_hw_spcseas.zip
Procedure
1. Back up all your data because this is going to erase everything from your phone;
2. Open the toolkit, and after installing the package for your device, unlock your bootloader, install TWRP and root your device which you can also do directly from the recovery (the tool is very easy to use and I am not going to be extremely detailed on this one);
3. In the toolkit, change the OEMinfo of your device by selecting the custom.bin and OEMinfo you find in the package attached to this post;
4. Reboot your device by entering the Huawei recovery and do a hard reset/cache clean from there;
5. Insert the update.app file you find in the C636 update package (which is B170) in a folder on your SD you rename "dload" (obviously without the brackets);
6. SD in your device, press the volume keys and power button to upgrade your phone to C636B170... I got an error during this process, but the phone booted and I proceeded regardless;
7. Do the same procedure as before: this time only unlock bootloader and install TWRP recovery by using the toolkit, and in the meantime put the two files to upgrade to B361 in your SD and put it back in the device;
8. Enter TWRP by pressing volume up + power button, install the update package first and then the data files;
9. Do a hard reset from the Huawei recovery you now have, and clean the cache. Reboot;
You are now in C636B360, the Nougat update I find the most stable.
If you want to get rid of the initial booting warning, you can relock your bootloader by doing so:
1. Connect your device to you PC, and from the ADB drivers folder on your hard disk, you open a CMD command (right click on your mouse while holding Shift, then "open command in here" or something similar)
2. Switch off your device, then connect it to USB and immediately switch it on while holding volume down button;
3. In the CMD window, type "fastboot devices" and then Enter to make sure your PC detects the phone;
4. Type oem relock + your bootloader code;
5. The phone will ask you if you want to relock the bootloader;
Done!

Hello
Tuto perfect :good:
thank you

My dude.

Happy to hear it's well done/it helped somebody

On step 7. Can i update has in step 5. Put firmware update.app and then the Data update.app (with eRecovery - Vol+Vol-POWER)? (like that i dont need to unlock bootloarder again and flash TWRP)

so what's the difference between c432 and 636?

FOSI17 said:
On step 7. Can i update has in step 5. Put firmware update.app and then the Data update.app (with eRecovery - Vol+Vol-POWER)? (like that i dont need to unlock bootloarder again and flash TWRP)
Click to expand...
Click to collapse
No, you need to install it from the recovery because there is not just one update.app file, it's a package with many files in it. You need to do it from TWRP please

mjz2cool said:
so what's the difference between c432 and 636?
Click to expand...
Click to collapse
The localization. C432 is Europe, C636 is from another country. In terms of features and performance, there is no difference except C636 has been upgraded to a pretty stable version of Nougat and you can have it on your device..

SALVO9 said:
The localization. C432 is Europe, C636 is from another country. In terms of features and performance, there is no difference except C636 has been upgraded to a pretty stable version of Nougat and you can have it on your device..
Click to expand...
Click to collapse
yeah i knew about localization, so that's the only difference. but can i set the language to dutch in 636?

Hi, I have previously converted my p9 lite to C432 dual sim , and now if I convert to C636 , will I loose dual sim? Thanks

lazeintera said:
Hi, I have previously converted my p9 lite to C432 dual sim , and now if I convert to C636 , will I loose dual sim? Thanks
Click to expand...
Click to collapse
No you shouldn't lose it

I have a problem. After installing B361 on select wifi, normal keyboard doens't show, only voice. And it seems it can't skip forward.

FOSI17 said:
I have a problem. After installing B361 on select wifi, normal keyboard doens't show, only voice. And it seems it can't skip forward.
Click to expand...
Click to collapse
You did not flash the additional data package, so you don't have all the files. You have to unlock the bootloader, flash revolution recovery for nougat since you don't have TWRP anymore (it's been replaced by stock nougat one) and try to flash those files manually. I cannot guarantee the results because I find that recovery really unuseful to say the least (my opinion). If you don't succeed, flash the oeminfo for MM you find on htcmania, and revert to MM with stock firmware and 3 buttons method

SALVO9 said:
You did not flash the additional data package, so you don't have all the files. You have to unlock the bootloader, flash revolution recovery for nougat since you don't have TWRP anymore (it's been replaced by stock nougat one) and try to flash those files manually. I cannot guarantee the results because I find that recovery really unuseful to say the least (my opinion). If you don't succeed, flash the oeminfo for MM you find on htcmania, and revert to MM with stock firmware and 3 buttons method
Click to expand...
Click to collapse
When i flash update.zip, it gives 2 errors at end of flash:
failed to mount '/cust' (invalid argument)
failed to mount '/system' (invalid argument)
When i flash update_full_VNS-L31_kw_spcseas.zip, it gives 2 errors at end of flash:
failed to mount '/cust' (invalid argument)
failed to mount '/system' (invalid argument)
---------- Post added at 04:07 PM ---------- Previous post was at 03:59 PM ----------
OK, i Have downloaded all files again and restarted from clean C636B170.
And now everything is ok

Does the camera work?
Sent from my HUAWEI VNS-L31 using Tapatalk

slaughta8868 said:
Does the camera work?
Sent from my HUAWEI VNS-L31 using Tapatalk[/QUOT
Hello
Yes, everything works on L31 :good:
Simply change the region and you can install the latest update.
Click to expand...
Click to collapse

Everything works, and very well.

So, as it's working well on european devices, which are the differences between c432 and c636? If they are quite similar, why didn't Huawei release a c432b361 version?
I'm not understanding Huawei's approach...

teacher77 said:
So, as it's working well on european devices, which are the differences between c432 and c636? If they are quite similar, why didn't Huawei release a c432b361 version?
I'm not understanding Huawei's approach...
Click to expand...
Click to collapse
Nobody is. I personally believe it's all marketing strategies. They want us to buy new phones and there are plenty on their way.

SALVO9 said:
Nobody is. I personally believe it's all marketing strategies. They want us to buy new phones and there are plenty on their way.
Click to expand...
Click to collapse
I think the same things. Disappointing, if true...

AL10 Can't get OTA to work

I have an AL10 with Chinese firmware. I used SRK Tool for Huawei and did the following
1. unlocked booloader
2. install twrp
3. Flash L19C646B190 from twrp
4. root
5. update oeminfo to C636
- After this step I had issues that when I boot the phone kept on asking for a password to decrypt the storage. I booted into twrp and tried to change the /data partition to ext4 from f2fs, but couldn't
6. Tried to flash L19C646B190 using UPDATE.APP and volume up + volume down + power, but couldn't. Phone complained that the firmware was incompatible
7. Used SRK Tool to update ro.build.display.id to EVA-L19C900B00. It was #ro.build.display.id=disabled
8. Flashed L19C646B190 using UPDATE.APP and volume up + volume down + power
9. Bootloader was locked again and twrp replaced with stock recovery after flashing
All in all the phone seems to be working find, but OTA is not working.
How do I go about getting OTA to work again?

za_fluffybunny said:
I have an AL10 with Chinese firmware. I used SRK Tool for Huawei and did the following
1. unlocked booloader
2. install twrp
3. Flash L19C646B190 from twrp
4. root
5. update oeminfo to C636
- After this step I had issues that when I boot the phone kept on asking for a password to decrypt the storage. I booted into twrp and tried to change the /data partition to ext4 from f2fs, but couldn't
6. Tried to flash L19C646B190 using UPDATE.APP and volume up + volume down + power, but couldn't. Phone complained that the firmware was incompatible
7. Used SRK Tool to update ro.build.display.id to EVA-L19C900B00. It was #ro.build.display.id=disabled
8. Flashed L19C646B190 using UPDATE.APP and volume up + volume down + power
9. Bootloader was locked again and twrp replaced with stock recovery after flashing
All in all the phone seems to be working find, but OTA is not working.
How do I go about getting OTA to work again?
Click to expand...
Click to collapse
Try change oeminfo to C432 or C185. I also try to use c636 but never get ota update. My device al00

rhodondendron said:
Try change oeminfo to C432 or C185. I also try to use c636 but never get ota update. My device al00
Click to expand...
Click to collapse
Worked like a charm, thanks I changed my oeminfo to hw / meanaf for c185 and flashed an offical L19C185 from Huawei. Immediately got all the OTAs and the device is working great.
For anybody with an AL10, don't bother looking for a L29 ROM, just Flash n L19, it works perfectly. The OS sees all the RAM and storage space

I flashed L09 rom to my AL-10 and everything is working fine too

I also have an al-10 and I'm tired of the Chinese rom.Can I change it to another rom？

Dirrin said:
I also have an al-10 and I'm tired of the Chinese rom.Can I change it to another rom？
Click to expand...
Click to collapse
Dude! Are you really asking that? OP create this thread because he change his chinesse phone rom to international rom

[ROM] Service ROMs

MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.

hw to install

Waleedaligomaa said:
hw to install
Click to expand...
Click to collapse
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!

Where L09 ..??
Sent from my MHA-L09 using XDA-Developers Legacy app

ante0 said:
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
That was some journey to the dark side. Welcome back.

So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432

albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload. Then rebrand back to L29C432 using Hwota. It's currently the only free way of rolling back to Nougat.

ante0 said:
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload.
Click to expand...
Click to collapse
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right

albertobom said:
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
Click to expand...
Click to collapse
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.

ante0 said:
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
Click to expand...
Click to collapse
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?

albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk

jaimeguate said:
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Nothing special really just want to know if I can go back if I have to. ?

albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
Oeminfo in this thread: https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 can be restored as a backup. That's probably the easiest way.
Alternative, copy and flash using dd.
cp /external_sd/MHA-AL00C00. bin /tmp/oeminfo.bin
dd if=/tmp/oeminfo.bin of=/dev/block/sdd5

5[Strogino said:
;74268268]MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
Click to expand...
Click to collapse
Hi bro can you send me oeminfo of chinese version of p8 lite 2017/honor 8 lite????
I want to rebrand my phone

ante0 said:
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?

seniga1 said:
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
Click to expand...
Click to collapse
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.

ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
flash recovery_ramdisk twrp.img
That did the trick, really appreciated, you'r my new hero :highfive:

Oreo updates
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
You should be able to get updates if you are on the Oreo beta, update checks for stock recovery and won't update if you are on a custom or patched recovery, system update would just see you as updating from beta to release version, beta and release versions are both official ROMs so I don't think you would have any issues with updating as long as the device brand is the same.

plz help sir
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.

jaldi said:
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
Click to expand...
Click to collapse
You do have Oreo, right?
TWRP should fail to install if you don't have Oreo (unless you're flashing it to recovery and not recovery_ramdisk).
But it sounds to me like it's not installing at all, since you're ending up in stock recovery.
Make sure you use "fastboot flash" , not "fastboot boot"

[Guide] Mate 10 Magisk Root

Steps:
Prepare and Notice
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Important! Remove Huawei "HiSuite" application if it's already installed. It may interfere script running.
C. Only tested ALP-AL00C00 same brand upgrade and downgrade packages.
D. Backup data, it might be restore factory default setting especially using downgrade ROM version.
E. Update package will be put in the internal /data partition.
F. Unlock bootloader before flash steps, use unlock.bat in "HWOTA8_Mate10" lock directory.
G. After update successfully, device might be locked again.
H. Get HWOTA8_Mate10 Package (HWOTA8_Mate10_2018052301_Remove_ota_rebrand.zip)
I. Windows10 can't recognize mate 10 fastboot device, see dc-unlocker free registry patch to fix it. (Link)
J. Mate 10 has imei in oeminfo, which is used for unlock bootloder not for system. Run lock/info.bat to see oeminfo IMEI.
Magisk (Thanks to @topjohnwu)
A. Install Magisk by running magisk/magisk.bat and follow instructions.
B. Install Huawei Wifi Fix module (Huawei-Wifi-Fix_v1.0_1500_2018041201.zip), if wifi is not working. [Not Must]
C. Join or dig more information from Magisk forum.
Change Log:
2018052301: Remove ota function, it bricks phone with recent new ROMs.
2018051001: Remove rebrand function, it bricks phone with recent new ROMs.
2018042501: Add BLA-AL00C786 porsche/cn (Not tested).
2018042401: Repack use full compress if update zip failure. Support ALP-L29C636B134 and BLA-L29C636B137 repack.
2018041201: New Magisk v16.3 and WiFi Fix module use 1500 template.
2018031301: Add new brand (no test), ALP: C69, BLA: C55 C109 C771 C782
2018021601: Replace with new Magisk 15.4, add huawei wifi fix module.
2018020601: Support BLA-L29C432B130-log repack.
2018012201: Port Magisk to Mate 10, only test ALP-L29C636B129 pass safetynet.
2018011401: Add new brand (no test), ALP: C02 C40 C109 C212 C346 C432 C605, BLA: C25 C33 C34 C45 C316 C521
2018011301: Support new update-binary
2018010501: Repack add lock bootloader selection, rebrand use huawei function which is more safe.

Nice, glad to see its very similar to the p10/mate 9.

Can this work on mate 10 Pro?

mankindtw said:
Steps:
Prepare and Notice
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Only tested ALP-AL00C00 same brand upgrade and downgrade packages.
C. Backup data, it might be restore factory default setting especially using downgrade ROM version.
D. Update package will be put in SD card.
E. Unlock bootloader before flash steps.
F. After update successfully, device might be locked again.
G. HWOTA8_Mate10 Package (HWOTA8_Mate10_2017120901.zip)
Flash Update
A. Put three huawei update files (update.zip, update_data_public.zip, and update_all_hw.zip) into "HWOTA8_Mate10" repack directory.
B. Run repack.bat to patch three zip files.
C. Use Vol-Dn + USB cable to boot into fastboot mode.
D. Run Replace_Recovery.bat in HWOTA8_Mate10 and follow message instructions.
E. It will reboot and install update automatically.
Click to expand...
Click to collapse
Wow, will give it a try
---------- Post added at 05:29 AM ---------- Previous post was at 04:45 AM ----------
Hope there might be some one who will elaborate Rebranding of Mate 10

k4fari said:
Hope there might be some one who will elaborate Rebranding of Mate 10
Click to expand...
Click to collapse
I'm going to try rebrand.

Its for the first time ever i am unable to unlock the boot loader, i obtained the boot loader unlock code by the following method for my mate 10. Don't know whats went wrong , when i try to unlock the boot loader in fastboot its giving an error. anyone can guide me on this?
Edit: I logout the Huawei Id and also set the usb debugging to Manufacture Mode by using *#*#2846579#*#* and then tried to unlock the boot loader and it worked as a charm.

mankindtw said:
I'm going to try rebrand.
Click to expand...
Click to collapse
Best of luck then.
I have tried the above method and after replace kernel and replace recovery successful i am still unable to boot in twrp mode by using volume + and button mode. Instead of Twrp i get a screen "reboot system, wipe data / factory , wipe cache"

k4fari said:
I have tried the above method and after replace kernel and replace recovery successful i am still unable to boot in twrp mode by using volume + and button mode. Instead of Twrp i get a screen "reboot system, wipe data / factory , wipe cache"
Click to expand...
Click to collapse
There is no TWRP at this moment, I modified stock recovery which can accept adb command.
Your screen is already in "Recovery" and follow message instructions for the next step.

mankindtw said:
There is no TWRP at this moment, I modified stock recovery which can accept adb command.
Your screen is already in "Recovery" and follow message instructions for the next step.
Click to expand...
Click to collapse
Mm You can not even work on the mate 10 pro?

mankindtw said:
There is no TWRP at this moment, I modified stock recovery which can accept adb command.
Your screen is already in "Recovery" and follow message instructions for the next step.
Click to expand...
Click to collapse
Ok got it, now it started to update to 8.0.0.126(c185) the latest one available on ff, i'll post the results after a while.
Regards
it started and the update failed on the phone at 54% whats wrong with me

k4fari said:
it started and the update failed on the phone at 54% whats wrong with me
Click to expand...
Click to collapse
Did you download "FullOTA-MF" ROM and your original brand is "ALP-L29 C185" ?

mankindtw said:
Did you download "FullOTA-MF" ROM and your original brand is "ALP-L29 C185" ?
Click to expand...
Click to collapse
Yes i have downloaded the full ota 8.0.0.126 of 2.68 gb of c185 , currently i am on 8.0.0.119(c185)

This one is have downloaded , is it because i skipped 8.0.0.125(c185) ?

k4fari said:
Yes i have downloaded the full ota 8.0.0.126 of 2.57gb of c185 , currently i am on 8.0.0.119(c185)
Click to expand...
Click to collapse
Try other version of c185 ROM to see if it makes any difference.

mankindtw said:
Try other version of c185 ROM to see if it makes any difference.
Click to expand...
Click to collapse
having slow internet connection, but i will try, can i try simple ota of 500 mb? or this method needs full ota mf?

k4fari said:
having slow internet connection, but i will try, can i try simple ota of 500 mb? or this method needs full ota mf?
Click to expand...
Click to collapse
Don't try, I'll give you another "update_binary" to patch zips.

mankindtw said:
Don't try, I'll give you another "update_binary" to patch zips.
Click to expand...
Click to collapse
Now update stops at 6% in the phone and shows software insatll fails , i have tried many times with the new update_binary file as well, but no luck :crying:
---------- Post added at 08:28 PM ---------- Previous post was at 08:18 PM ----------
mankindtw said:
Don't try, I'll give you another "update_binary" to patch zips.
Click to expand...
Click to collapse
will the small ota brick the phone by this method?

k4fari said:
will the small ota brick the phone by this method?
Click to expand...
Click to collapse
Don't use OTA-MF, you should use FullOTA-MF zips.

mankindtw said:
Don't use OTA-MF, you should use FullOTA-MF zips.
Click to expand...
Click to collapse
i was using full ota mf 8.0.0.126(c185). but was not able to get any success, i am continuously trying since the last 7 to 8 hours:crying:

check the repack.bat plz

Go back to stock rom

Hi,
I've installed a custom rom, but now i can´t install updates, Pie for example.
How can i unroot and go back to stock rom?
Thanks

aalmeida1972 said:
Hi,
I've installed a custom rom, but now i can´t install updates, Pie for example.
How can i unroot and go back to stock rom?
Thanks
Click to expand...
Click to collapse
I'd suggest HurUpdater: https://forum.xda-developers.com/ho...h-official-firmware-recovery-t3769279/page111
OTAs do work with an unlocked bootloader, but not with root or custom kernels.

Does this works with the P10? In the post i ddin´t found the P10.
And if it works, wich zip file i have to choose? And i have root
Thanks

Try my guide (Tutorial #2, Oreo to Oreo)
After that do a factory reset with eRecovery (boot with Vol+ and connected USB).
What also should work is flashing the system.img manually via fastboot.
For this extract the system.img from the correct firmware version with Huawei Update Extractor.
Connect your phone to your PC, boot into fastboot and flash with "fastboot flash system PATH\TO\SYSTEM.IMG".
After that do a factory reset with eRecovery (boot with Vol+ and connected USB).
Note for the next time: backup your system partition via TWRP before flashing the custom rom.
Also note that a factory reset is needed, without your phone won't boot, so backup your personal data before doing it.

aalmeida1972 said:
Does this works with the P10? In the post i ddin´t found the P10.
And if it works, wich zip file i have to choose? And i have root
Thanks
Click to expand...
Click to collapse
Yes, it works on the P10. You can download the files with the firmware finder app. I'd recommend the newest oreo version for your customisation (e.g. B382 for C432).
But Jannomag's solution should work equally well.

Wich Jannomag´s thread?
Do you have the link, please?
Thanks

aalmeida1972 said:
Wich Jannomag´s thread?
Do you have the link, please?
Thanks
Click to expand...
Click to collapse
The fourth message in this thread

I am sorry, maybe i am just dumb but i can't find it

I followed the guide but know i am i an bootloop. I get the message "your device has failed verification and may not work properly"

It restarded, but as D188-L29!!! I download the VTR-L29 on https://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29C432&firmware_page=0
Now i can't update or nothing

aalmeida1972 said:
It restarded, but as D188-L29!!! I download the VTR-L29 on https://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29C432&firmware_page=0
Now i can't update or nothing
Click to expand...
Click to collapse
Possibly you renamed the wrong customisation file (i did it once for the 09 while I needed the 29).

Which one did you download? And did you flash manually or did you use my script?
Download my oeminfo, it's from VTR-L29C432 Version 8.0.0.380, while the version doesn't really matter.
Flash it via TWRP using "Install" and "Use Image". Flash it to oeminfo partition. Then do my update script again.

I followed the guide to do Oreo to Oreo - basically wanting to get from custom Rom (fRomFuture B370) back to stock, so I chose the same firmware version to extract. Flashed everything with the script and it went fine and it boots and works.. but
The resolution seems to be off, too low and the right side of the screen is unresponsive to touch (about 1cm )
EDIT- Rolled back to fRomFuture B370 for now - need to find a way to get back to stock, as want to move on to Openkirin ROM instead

HI, i have a vtr-l29 root, i want to unroot(version oreo), how do i do it? what do i need to flash?. thank you Alex