[ROM] Service ROMs

[5[Strogino]]

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.

 

[Waleedaligomaa]

hw to install

 

[ante0]

hw to install

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!

 

[mataflakitas]

Where L09 ..??

Sent from my MHA-L09 using XDA-Developers Legacy app

 

[justthefacts]

Now my Mate 9 is booting up again!

That was some journey to the dark side. Welcome back.

 

[albertobom]

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

 

[ante0]

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

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.

 

[albertobom]

You need to rebrand to AL00C00 to rollback.

In other words, flash AL00 oeminfo.bin, use AL00 dload.

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

 

[ante0]

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

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.

 

[albertobom]

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.

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?

 

[jaimeguate]

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

Why to rollback?

Enviado desde mi MHA-L29 mediante Tapatalk

 

[albertobom]

Why to rollback?

Enviado desde mi MHA-L29 mediante Tapatalk

Nothing special really just want to know if I can go back if I have to. ?

 

[ante0]

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?

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

 

[mkoijnbhu]

;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.

Hi bro can you send me oeminfo of chinese version of p8 lite 2017/honor 8 lite????


I want to rebrand my phone

 

[seniga1]

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!

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?

 

[ante0]

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?

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.

 

[seniga1]

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.

flash recovery_ramdisk twrp.img

That did the trick, really appreciated, you'r my new hero :highfive:

 

[revjamescarver]

Oreo updates

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?

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.

 

[jaldi]

plz help sir

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.

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.

 

[ante0]

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.

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"