[Huawei Mate 10  Guides, News, & Discussion] Rstment ^m^:
Heyo ! I tried using the tool that you provided but it ended up in hard brick. Phone is black, led doesnt respond and no buzz when holding power button - brick as it only shows up as bootloader device in device manager. Why tho? I tried going 02 to 02 , moving from 9.1 to 8 in couple tries . First was 9.1.300 to 9.0.259 or smthing with emui 9 to 9.1 tool as I figured it might work due to no check script. It worked , all is welland i tried flashing kangvip only for it to get stuck on ur device is unlocked messsage forcing me to flash system and ramdisk since it didnt look like its gonna get any firther into booting os. From 9.0.259 stock I used the tool you brought up to go to 8.0.0.156 from december or something like that. It all went succesfull :

*** WELCOME TO EMUI DOWNGRADER 0.1 by Vorion ***

Thanks to @Ante0, @Atarii, @dkionline, @frantm, @last****ingdroid, @Mankindtw, @Pretoriano80, @shimp208, @zanooda123
... and of course to support@huawei.com

Press any key to continue . . .

PLEASE READ EVERYTHING THIS TOOLS TELLS YOU TO DO!

Press any key to continue . . .

BEFORE STARTING, PLEASE ENSURE YOU REMOVED ALL KIND OF SCHEMA, PIN OR FINGERPRINT SECURITY.
TWRP DOES NOT SUPPORT DATA DECRYPTION, AND NO ROOT IS POSSIBLE ATM, SO IT WILL END UP WITH AN ERROR IF YOU DON'T.

Press any key to continue . . .

Put the update.zip into the "ZIPS-HERE" folder.

Press any key to continue . . .

Now rename the update_full_XXXXXX_hw_eu.zip to update_all_hw.zip and put it in the ZIPS-HERE folder.

Press any key to continue . . .

Now rename the update_data_full_public.zip, rename it to update_data_public.zip and put it in the ZIPS-HERE folder.

Press any key to continue . . .

- Rebooting to fastboot, confirm with enter when in fastboot screen

* daemon not running; starting now at tcp:5037
* daemon started successfully

Press any key to continue . . .

- Flashing TWRP recovery

target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.600s]
writing 'recovery_ramdisk'...
OKAY [ 0.141s]
finished. total time: 0.742s

- Rebooting..
- AFTER PRESSING A KEY, PLEASE UNPLUG YOUR PHONE AND HOLD PRESS THE VOLUME UP BUTTON UNTIL PHONE BOOTS IN TWRP.
- OTHERWISE THE SYSTEM WILL BOOT AND YOU WILL NEED TO START THE SCRIPT AGAIN.
- IF YOU MISSED THIS STEP, JUST CLOSE THIS SCRIPT USING THE RED CROSS AND OPEN IT AGAIN.

Press any key to continue . . .

rebooting...

finished. total time: 0.009s

Wait for device to boot in TWRP. The touch screen may not work, do not care about it.
PLEASE PLUG YOUR PHONE BACK BEFORE CONTINUING.
Confirm with enter when your phone will be in TWRP.

Press any key to continue . . .

- Decrypting data partition. Should work if you removed phone's password.

command is: 'decrypt' and there is no value
No password provided.
Done processing script file

Press any key to continue . . .

- Uploading update files

ZIPS-HERE/update.zip: 1 file pushed. 25.1 MB/s (2262451577 bytes in 85.852s)
ZIPS-HERE/update_all_hw.zip: 1 file pushed. 25.3 MB/s (661424448 bytes in 24.884s)
ZIPS-HERE/update_data_public.zip: 1 file pushed. 25.1 MB/s (200463426 bytes in 7.604s)
images/nocheck.img: 1 file pushed. 25.8 MB/s (26247168 bytes in 0.969s)

- Writing recovery commands. Wait.

UPDATE.ZIP - OK.

UPDATE_ALL_HW.ZIP - OK..

UPDATE_DATA_PUBLIC.ZIP - OK..

DONE.

Press any key to continue . . .

- NoCheck recovery is going to be flashed.

51264+0 records in
51264+0 records out
26247168 bytes (25.0MB) copied, 1.207457 seconds, 20.7MB/s

Press any key to continue . . .

++++ Rebooting. Enjoy!

Press any key to continue . . .

But it reported failed to flash system img error when it left fastboot and asked me to reboot or boot into erecovery to rescue device . I chose erecovery wanting to do factory reset like its written in the script but the moment I pressed that button all went black and I couldnt do shet from there on. Is it doomed ? lol I tried dc phoenix guide only to have it not want to log in to my account reporting wrong pass username even tho I copied what I got from gmail as credentials.... Then I realised that having it as android phone > bootloader interface in device manager prolly means fastboot and Im screwed anyways even if dc works or doesnt. Phone is on service now I hope they dont notice twrp or unlocked bl >.< Was there anything I shouldve done differently ?

At first I didnt check xloader so I remembered mass brick thread and was pissed lol , downloaded the tool put the update through it and nit reports 02? idk now , was the original 03 or smhting ? Ill try modifing the tool to accept already extracted file so I can check.

Extracting UPDATE.APP, FULLOTA takes a bit. Please wait
Extracting XLOADER from UPDATE.APP
Checking XLOADER
02 - Safe when going 02 to 02

You can flash 02 XLOADER ontop of 01 XLOADER, but you can't flash 01 XLOADER ontop of 02 XLOADER.
01 to 01, 01 to 02 and 02 to 02 is safe. 02 to 01 is not!

Cleaning up
All done!
Press ENTER key to continue...

---------- Post added at 11:14 AM ---------- Previous post was at 10:35 AM ----------

Heyo ! I tried using the tool that you provided but it ended up in hard brick. Phone is black, led doesnt respond and no buzz when holding power button - brick as it only shows up as bootloader device in device manager. Why tho? I tried going 02 to 02 , moving from 9.1 to 8 in couple tries . First was 9.1.300 to 9.0.259 or smthing with emui 9 to 9.1 tool as I figured it might work due to no check script. It worked , all is welland i tried flashing kangvip only for it to get stuck on ur device is unlocked messsage forcing me to flash system and ramdisk since it didnt look like its gonna get any firther into booting os. From 9.0.259 stock I used the tool you brought up to go to 8.0.0.156 from december or something like that. It all went succesfull :

*** WELCOME TO EMUI DOWNGRADER 0.1 by Vorion ***

Thanks to @Ante0, @Atarii, @dkionline, @frantm, @last****ingdroid, @Mankindtw, @Pretoriano80, @shimp208, @zanooda123
... and of course to support@huawei.com

Press any key to continue . . .

PLEASE READ EVERYTHING THIS TOOLS TELLS YOU TO DO!

Press any key to continue . . .

BEFORE STARTING, PLEASE ENSURE YOU REMOVED ALL KIND OF SCHEMA, PIN OR FINGERPRINT SECURITY.
TWRP DOES NOT SUPPORT DATA DECRYPTION, AND NO ROOT IS POSSIBLE ATM, SO IT WILL END UP WITH AN ERROR IF YOU DON'T.

Press any key to continue . . .

Put the update.zip into the "ZIPS-HERE" folder.

Press any key to continue . . .

Now rename the update_full_XXXXXX_hw_eu.zip to update_all_hw.zip and put it in the ZIPS-HERE folder.

Press any key to continue . . .

Now rename the update_data_full_public.zip, rename it to update_data_public.zip and put it in the ZIPS-HERE folder.

Press any key to continue . . .

- Rebooting to fastboot, confirm with enter when in fastboot screen

* daemon not running; starting now at tcp:5037
* daemon started successfully

Press any key to continue . . .

- Flashing TWRP recovery

target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.600s]
writing 'recovery_ramdisk'...
OKAY [ 0.141s]
finished. total time: 0.742s

- Rebooting..
- AFTER PRESSING A KEY, PLEASE UNPLUG YOUR PHONE AND HOLD PRESS THE VOLUME UP BUTTON UNTIL PHONE BOOTS IN TWRP.
- OTHERWISE THE SYSTEM WILL BOOT AND YOU WILL NEED TO START THE SCRIPT AGAIN.
- IF YOU MISSED THIS STEP, JUST CLOSE THIS SCRIPT USING THE RED CROSS AND OPEN IT AGAIN.

Press any key to continue . . .

rebooting...

finished. total time: 0.009s

Wait for device to boot in TWRP. The touch screen may not work, do not care about it.
PLEASE PLUG YOUR PHONE BACK BEFORE CONTINUING.
Confirm with enter when your phone will be in TWRP.

Press any key to continue . . .

- Decrypting data partition. Should work if you removed phone's password.

command is: 'decrypt' and there is no value
No password provided.
Done processing script file

Press any key to continue . . .

- Uploading update files

ZIPS-HERE/update.zip: 1 file pushed. 25.1 MB/s (2262451577 bytes in 85.852s)
ZIPS-HERE/update_all_hw.zip: 1 file pushed. 25.3 MB/s (661424448 bytes in 24.884s)
ZIPS-HERE/update_data_public.zip: 1 file pushed. 25.1 MB/s (200463426 bytes in 7.604s)
images/nocheck.img: 1 file pushed. 25.8 MB/s (26247168 bytes in 0.969s)

- Writing recovery commands. Wait.

UPDATE.ZIP - OK.

UPDATE_ALL_HW.ZIP - OK..

UPDATE_DATA_PUBLIC.ZIP - OK..

DONE.

Press any key to continue . . .

- NoCheck recovery is going to be flashed.

51264+0 records in
51264+0 records out
26247168 bytes (25.0MB) copied, 1.207457 seconds, 20.7MB/s

Press any key to continue . . .

++++ Rebooting. Enjoy!

Press any key to continue . . .

But it reported failed to flash system img error when it left fastboot and asked me to reboot or boot into erecovery to rescue device . I chose erecovery wanting to do factory reset like its written in the script but the moment I pressed that button all went black and I couldnt do shet from there on. Is it doomed ? lol I tried dc phoenix guide only to have it not want to log in to my account reporting wrong pass username even tho I copied what I got from gmail as credentials.... Then I realised that having it as android phone > bootloader interface in device manager prolly means fastboot and Im screwed anyways even if dc works or doesnt. Phone is on service now I hope they dont notice twrp or unlocked bl >.< Was there anything I shouldve done differently ?

At first I didnt check xloader so I remembered mass brick thread and was pissed lol , downloaded the tool put the update through it and nit reports 02? idk now , was the original 03 or smhting ? Ill try modifing the tool to accept already extracted file so I can check.

Extracting UPDATE.APP, FULLOTA takes a bit. Please wait
Extracting XLOADER from UPDATE.APP
Checking XLOADER
02 - Safe when going 02 to 02

You can flash 02 XLOADER ontop of 01 XLOADER, but you can't flash 01 XLOADER ontop of 02 XLOADER.
01 to 01, 01 to 02 and 02 to 02 is safe. 02 to 01 is not!

Cleaning up
All done!
Press ENTER key to continue...

It was 02 on 9.0.259 firmware as well , so the downgrade would be 02 to 02 , idk why it failed then... One thing to note tho , erecovery broke in 9.1.300 after using dd command from ante0 to flash erecovery as ramdisk so I dont have to flash stock ramdisk to remove magisk root. I did flash stock ramdisk when I downgraded tho , but erecovery was still broken failing to get package info when trying to download stock firmware. If u can help shed some light in any way please do , ty !