Database Info

Any B126 force update solution?

So, ive been checking around here literally every 2 hours, trying to see if someone found a solution to force the update, rather than waiting and waiting.. Talking about the international version of the mate 9 of course..
Thought opening this might gather great minds here to find a solution.
So everyone, your help is much appreciated by all of us..

I've been testing all day with someone who has an affected phone. We have been successful in flashing B115 onto a European Mate 9 by hijacking eRecovery or using a trick to flash via USB in HiSuite, but B126 refuses to flash with either of these methods. There is something about the B126 package which the phones don't want to flash.
When a ROM is flashed on a Mate 9, it must have an internet connection. eRecovery (or HiSuite) sends a request for a code based on the serial number of the phone, its IMEI, an update token, and the version number of the update. Huawei's server returns an encrypted hash. This hash is then checked by the phone and for whatever reason, this check fails with the B126 package (it works fine with B115.) I have been looking into ways of getting around this, but the only way I can come up with (overwriting the hard disk area an update.app file is stored while Hisuite is doing the live flash) is extremely dangerous and could result in a brick. So it's better to wait for a new version to come out, which might be flashable via eRecovery or HiSuite.

So annoying! I'm also desperately waiting for the update because I really like the phone but some annoying bugs are just making the whole experience so annoying. It was quite silly of Huawei to actually release the phone with this half baked ROM.
Any way, now I'm not just going to check for update every hour but also this thread
Cheers,

Many thanks for your efforts @duraaraa, hopefully you'll find a way in the end.

I just found the exact reason why it doesn't work, and am working on a remedy. If it's successful, I will make it public tomorrow. Afterall, Huawei is not authenticating these versions for installation. OTA authentication is different so I can't say anything about that, but the authentication for eRecovery/HiSuite full version flash is not there.

duraaraa said:
I've been testing all day with someone who has an affected phone. We have been successful in flashing B115 onto a European Mate 9 by hijacking eRecovery or using a trick to flash via USB in HiSuite, but B126 refuses to flash with either of these methods. There is something about the B126 package which the phones don't want to flash.
When a ROM is flashed on a Mate 9, it must have an internet connection. eRecovery (or HiSuite) sends a request for a code based on the serial number of the phone, its IMEI, an update token, and the version number of the update. Huawei's server returns an encrypted hash. This hash is then checked by the phone and for whatever reason, this check fails with the B126 package (it works fine with B115.) I have been looking into ways of getting around this, but the only way I can come up with (overwriting the hard disk area an update.app file is stored while Hisuite is doing the live flash) is extremely dangerous and could result in a brick. So it's better to wait for a new version to come out, which might be flashable via eRecovery or HiSuite.
Click to expand...
Click to collapse
Thats tbe spirit i was looking for.. Mate9 gang around.. This way we all try to share updates

malikons said:
So annoying! I'm also desperately waiting for the update because I really like the phone but some annoying bugs are just making the whole experience so annoying. It was quite silly of Huawei to actually release the phone with this half baked ROM.
Any way, now I'm not just going to check for update every hour but also this thread
Cheers,
Click to expand...
Click to collapse
Join the club..

duraaraa said:
I just found the exact reason why it doesn't work, and am working on a remedy. If it's successful, I will make it public tomorrow. Afterall, Huawei is not authenticating these versions for installation. OTA authentication is different so I can't say anything about that, but the authentication for eRecovery/HiSuite full version flash is not there.
Click to expand...
Click to collapse
We all can't wait.. So keep us updated here..

I'm in....
Inviato dal mio MHA-L29 utilizzando Tapatalk

Ok, so. Here is what I have. I've been up all night, it's 7AM, and I'm tired, so I'm not going to be working on this any more until tomorrow. If any of you can find the solution to this, I can very likely let you flash whatever version you want onto your phone. This will be a long explanation, but if anyone is knowledgeable about openssl, they can help me hack at this.
Here is a response from a request to huawei's authorization server for B115, which can be flashed.
Code:
data=eyJ1cGRhdGVUb2tlbiI6Ijc1M0Q4QUYwMDAwNzFBQkMiLCJkZXZpY2VJZCI6IjU5OTg0RUJBQ0U5MkI3REJBQkQxMzUwQTk4NDgzQzlDM0U3MTYyRjMxMDExNDk0QjQ2REFFNkU4MjJEMkM0OEIiLCJhcHByb3ZlZFZlcnNpb25MaXN0IjpbeyJ2ZXJzaW9uSWQiOiI2NjcxMSIsInN0YXR1cyI6IjAiLCJ2ZXJzaW9uTnVtYmVyIjoiTUhBLUwyOUM5MDBCMTE1In1dfQ==&sign=MEUCIF1DGCXm0VPxuBa2qdBfGr98haEasb3yMcCVr+lYbHrBAiEAyZn3Wi1vlD9ZeWQDWeTt9kE7a9YJhFR2b01nG/FDlWI=&cert=MIIDJzCCAsygAwIBAgIJALWcScNmfs+NMAoGCCqGSM49BAMCMIHXMQswCQYDVQQGEwJDTjEQMA4GA1UECAwHSmlhbmdzdTEQMA4GA1UEBwwHTmFuamluZzEsMCoGA1UECgwjSHVhd2VpIFNvZnR3YXJlIFRlY2hub2xvZ2llcyBDTy5MdGQxQTA/BgNVBAsMOERldmllIFJlZ2lvbiBEZWxpdmVyeSAmIFNlcnZpY2UgUXVhbGl0eSAmIE9wZXJhdGlvbiBEZXB0MRQwEgYDVQQDDAtPVEEgUm9vdCBDQTEdMBsGCSqGSIb3DQEJARYOb3RhQGh1YXdlaS5jb20wHhcNMTYwNzEyMDgxOTU5WhcNMTcwNzEyMDgxOTU5WjCB2zELMAkGA1UEBhMCQ04xEDAOBgNVBAgMB0ppYW5nc3UxEDAOBgNVBAcMB05hbmppbmcxLDAqBgNVBAoMI0h1YXdlaSBTb2Z0d2FyZSBUZWNobm9sb2dpZXMgQ08uTHRkMUEwPwYDVQQLDDhEZXZpZSBSZWdpb24gRGVsaXZlcnkgJiBTZXJ2aWNlIFF1YWxpdHkgJiBPcGVyYXRpb24gRGVwdDEYMBYGA1UEAwwPT1RBIEF1dGggU2VydmVyMR0wGwYJKoZIhvcNAQkBFg5vdGFAaHVhd2VpLmNvbTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABGeDtAUO4uTY5yWwS54sk030WOdHYoaaO0dufn4jvul22Ytogvua1W0qY+ABblhA3eB49YXYPnpLvGhjr+73oZ6jezB5MAkGA1UdEwQCMAAwLAYJYIZIAYb4QgENBB8WHU9wZW5TU0wgR2VuZXJhdGVkIENlcnRpZmljYXRlMB0GA1UdDgQWBBTGCe/51LIS2ZT9nAj06RaAFcQa4jAfBgNVHSMEGDAWgBTH3T3aib5XZtlRccAInw7VjXJS0jAKBggqhkjOPQQDAgNJADBGAiEAjyic8z59ws8PvB2Q7apf69yFLM7ByICD8RBXxmz1WtUCIQChb2PYP5BzGRFxKV9ow9DesWt4bakIgdNFsUuT4NwMlQ==
We can split this up into three parts. All of them are base64. so the first part, from data= to &sign= can be translated to plain text, which gives us this json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"66711","status":"0","versionNumber":"MHA-L29C900B115"}]}
The sign= portion is a signature, and the cert= portion is an openssl certificate.
I have determined that all or part of the data= portion is signed with the certificate in the cert= portion. But I don't know in what shape the data is signed. If I convert everything and check with openssl, verification fails. I hope that someone can run some experiments and figure out exactly what it is in that data which is signed. If you can find this, I can help you get whatever version loaded you want.
By the way, here's what happens when we try to request B126:
Code:
data=eyJ1cGRhdGVUb2tlbiI6Ijc1M0Q4QUYwMDAwNzFBQkMiLCJkZXZpY2VJZCI6IjU5OTg0RUJBQ0U5MkI3REJBQkQxMzUwQTk4NDgzQzlDM0U3MTYyRjMxMDExNDk0QjQ2REFFNkU4MjJEMkM0OEIiLCJhcHByb3ZlZFZlcnNpb25MaXN0IjpbeyJ2ZXJzaW9uSWQiOiI2ODE2NSIsInN0YXR1cyI6IjEifV19&sign=MEUCIBrO1Y0ko3+fb12yXewessLbe3lfg5XPoPoqL30G5XMtAiEA9WniyB0vNRZWREk2vYT3Dfq9hPUJMNC8miAdlkULCe0=&cert=MIIDJzCCAsygAwIBAgIJALWcScNmfs+NMAoGCCqGSM49BAMCMIHXMQswCQYDVQQGEwJDTjEQMA4GA1UECAwHSmlhbmdzdTEQMA4GA1UEBwwHTmFuamluZzEsMCoGA1UECgwjSHVhd2VpIFNvZnR3YXJlIFRlY2hub2xvZ2llcyBDTy5MdGQxQTA/BgNVBAsMOERldmllIFJlZ2lvbiBEZWxpdmVyeSAmIFNlcnZpY2UgUXVhbGl0eSAmIE9wZXJhdGlvbiBEZXB0MRQwEgYDVQQDDAtPVEEgUm9vdCBDQTEdMBsGCSqGSIb3DQEJARYOb3RhQGh1YXdlaS5jb20wHhcNMTYwNzEyMDgxOTU5WhcNMTcwNzEyMDgxOTU5WjCB2zELMAkGA1UEBhMCQ04xEDAOBgNVBAgMB0ppYW5nc3UxEDAOBgNVBAcMB05hbmppbmcxLDAqBgNVBAoMI0h1YXdlaSBTb2Z0d2FyZSBUZWNobm9sb2dpZXMgQ08uTHRkMUEwPwYDVQQLDDhEZXZpZSBSZWdpb24gRGVsaXZlcnkgJiBTZXJ2aWNlIFF1YWxpdHkgJiBPcGVyYXRpb24gRGVwdDEYMBYGA1UEAwwPT1RBIEF1dGggU2VydmVyMR0wGwYJKoZIhvcNAQkBFg5vdGFAaHVhd2VpLmNvbTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABGeDtAUO4uTY5yWwS54sk030WOdHYoaaO0dufn4jvul22Ytogvua1W0qY+ABblhA3eB49YXYPnpLvGhjr+73oZ6jezB5MAkGA1UdEwQCMAAwLAYJYIZIAYb4QgENBB8WHU9wZW5TU0wgR2VuZXJhdGVkIENlcnRpZmljYXRlMB0GA1UdDgQWBBTGCe/51LIS2ZT9nAj06RaAFcQa4jAfBgNVHSMEGDAWgBTH3T3aib5XZtlRccAInw7VjXJS0jAKBggqhkjOPQQDAgNJADBGAiEAjyic8z59ws8PvB2Q7apf69yFLM7ByICD8RBXxmz1WtUCIQChb2PYP5BzGRFxKV9ow9DesWt4bakIgdNFsUuT4NwMlQ==
The data portion translates to the following json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"68165","status":"1"}]}
You will notice that the status in the working update was 0. It also gave a version. In this case, we get status 1 and no version. Ergo, authentication fails and it will not install through eRecovery or HiSuite, while version B115 will.
So if you can find out what is signed and how, I might be able to re-sign this stuff and just provide/generate the certificate/key via my DNS server so that the installations no longer fail.
That is where I'm at. If anyone can crack the code, please post it here.

@duraaraa, just wanted to say you're a beast. Thanks for all your contribution and hard work thus far to the Mate 9 forum. I think I speak for everyone when I say we're lucky to have you here. I hope more developers start chiming in soon to help. I know it can be quite a task doing all of this by yourself, so we appreciate the time/effort you've spent for everyone. Cheers brother :highfive:

duraaraa said:
Ok, so. Here is what I have. I've been up all night, it's 7AM, and I'm tired, so I'm not going to be working on this any more until tomorrow. If any of you can find the solution to this, I can very likely let you flash whatever version you want onto your phone. This will be a long explanation, but if anyone is knowledgeable about openssl, they can help me hack at this.
Here is a response from a request to huawei's authorization server for B115, which can be flashed.
We can split this up into three parts. All of them are base64. so the first part, from data= to &sign= can be translated to plain text, which gives us this json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"66711","status":"0","versionNumber":"MHA-L29C900B115"}]}
The sign= portion is a signature, and the cert= portion is an openssl certificate.
I have determined that all or part of the data= portion is signed with the certificate in the cert= portion. But I don't know in what shape the data is signed. If I convert everything and check with openssl, verification fails. I hope that someone can run some experiments and figure out exactly what it is in that data which is signed. If you can find this, I can help you get whatever version loaded you want.
By the way, here's what happens when we try to request B126:
The data portion translates to the following json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"68165","status":"1"}]}
You will notice that the status in the working update was 0. It also gave a version. In this case, we get status 1 and no version. Ergo, authentication fails and it will not install through eRecovery or HiSuite, while version B115 will.
So if you can find out what is signed and how, I might be able to re-sign this stuff and just provide/generate the certificate/key via my DNS server so that the installations no longer fail.
That is where I'm at. If anyone can crack the code, please post it here.
Click to expand...
Click to collapse
Your help is much much appreciated.. I have friends expert in telecommunications security, will share this with them and see what they can do.. If they can..
Regardless, you are a big asset to all of us mate9 users.. Thank you again..

opasha said:
@duraaraa, just wanted to say you're a beast. Thanks for all your contribution and hard work thus far to the Mate 9 forum. I think I speak for everyone when I say we're lucky to have you here. I hope more developers start chiming in soon to help. I know it can be quite a task doing all of this by yourself, so we appreciate the time/effort you've spent for everyone. Cheers brother :highfive:
Click to expand...
Click to collapse
Thank you for that! I feel less like a beast and more like a slug right now to be honest!

duraaraa said:
Thank you for that! I feel less like a beast and more like a slug right now to be honest!
Click to expand...
Click to collapse
Haha, you're welcome, bro. To me, progress, no matter how slow, is still progress .

OK guys. Here is the final outcome.
Basically, updates are either approved by Huawei to be installed, or not approved.
B126 is actually a beta version, and it's only available to SOME IMEIs. I got a hold of someone who got the update and used his information to confirm.
Anyway, you will NOT be able to side load it. In order to install a regular update through eRecovery or HiSuite, the update must be authorized as an update which can be installed by Huawei. As of right now, the only non-Chinese update authorized to be installed by Huawei is B115. There are several Chinese updates which you could install on your phone, however, if modified correctly, but I don't think you would want to do this, as there are negative side effects.
So why do I declare it to be impossible? B126 is only installable as an OTA by people whose IMEIs are on Huawei's beta list. Here's how an OTA works.
1. The phone goes to query.hicloud.com to check for the version to get. (This step can be overridden by me, and I can make the phone find any version.)
2. The phone downloads the update and verifies that the files are correct. (This step also works fine.)
3. The phone then says it will restart to install in 10 seconds.
4. Right before the phone restarts to install, it connects over HTTPS to https://query.hicloud.com to confirm. Because it uses a certificate and I can't fudge the certificate, this is the step we cannot bypass. So the install stops here unless your IMEI is on Huawei's approved list, and the update is found to be invalid.
The only chance we will have at installing updates Huawei doesn't want us to install will be either unlocking the bootloader, rooting, or finding a way to install without any internet connectivity. I'm sorry to have to say this, but it's not going to happen this time
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135

duraaraa said:
OK guys. Here is the final outcome.
Basically, updates are either approved by Huawei to be installed, or not approved.
B126 is actually a beta version, and it's only available to SOME IMEIs. I got a hold of someone who got the update and used his information to confirm.
Anyway, you will NOT be able to side load it. In order to install a regular update through eRecovery or HiSuite, the update must be authorized as an update which can be installed by Huawei. As of right now, the only non-Chinese update authorized to be installed by Huawei is B115. There are several Chinese updates which you could install on your phone, however, if modified correctly, but I don't think you would want to do this, as there are negative side effects.
So why do I declare it to be impossible? B126 is only installable as an OTA by people whose IMEIs are on Huawei's beta list. Here's how an OTA works.
1. The phone goes to query.hicloud.com to check for the version to get. (This step can be overridden by me, and I can make the phone find any version.)
2. The phone downloads the update and verifies that the files are correct. (This step also works fine.)
3. The phone then says it will restart to install in 10 seconds.
4. Right before the phone restarts to install, it connects over HTTPS to https://query.hicloud.com to confirm. Because it uses a certificate and I can't fudge the certificate, this is the step we cannot bypass. So the install stops here unless your IMEI is on Huawei's approved list, and the update is found to be invalid.
The only chance we will have at installing updates Huawei doesn't want us to install will be either unlocking the bootloader, rooting, or finding a way to install without any internet connectivity. I'm sorry to have to say this, but it's not going to happen this time
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
Click to expand...
Click to collapse
I agree with u about it being impossible, i even checked with my security experts friends, and they said " only by hacking Huawei servers Hahaha"..
But am so so so excited and waiting for this update, really the device needs the update badly to complete the experience, feels like i have the fastest horse ever, but am missing one of his legs..
I wonder how fast Huawei will roll out the final version.. Maybe those who have history with Huawei devices can tell, as am new to Huawei and ive always been a Samsung guy (not anymore with the impressive mate9)

duraaraa said:
...
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
Click to expand...
Click to collapse
Some people in the Netherlands that had MHA-L29C432B109SP2 also got the update to b126.
Not me unfortunately.

@duraaraa, did u changed the public key to any from an updated phone?

dkionline said:
@duraaraa, did u changed the public key to any from an updated phone?
Click to expand...
Click to collapse
Sorry, I don't understand your question.

I am on B110 with my C636 model. Nothing new yet
Sent from my FRD-L09 using Tapatalk

[Help]: problem downgrading from Nougat to MM

So I tried to downgrade from B137 Nougat to MM doing a roll back following
https://forum.xda-developers.com/honor-8/how-to/software-rollback-guideline-frd-lo2-t3538016
I copied the UPDATE.APP in SD card on my L04 with B317.
I did press and hold volume + _ and power and just got a user reset. Now the phone starts but it is asking me to insert my google account but I can't insert it because there is no keyboard working only google voice.
Not sure what I can do but clearly I messed up.
:crying:

you gotta find a rollback package.. and flash it first , and then flash marshmallow

find downgrade pakage and firmware in honor fourms

I've also had the identical problem. These ^^ people are right. You have the same model as I do , Frd-l04, so this is the link I used to get the rollback pkg:
http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098
And read the doc that you can get there, but it's pretty basic: Like they said, first install something called the intermediate rollback.app (or maybe it's update.app) and then the b162 one. First is about 100K and 2nd is about 2G . It doesn't really make a bit of sense or seem right until you've done it (like many things).
Just so you know: The way I found that was by googling .. "Honor 8 frd-l04 rollback" (or something much like that and the hit was on the first page of hits).
Other trivia: For me, I had to hold the combo up/down/power until I saw the screen saying "rolling back" (or whatever it said). You don't enter anything, it's just happening and then you can let go the keys. First one is pretty quick, 2nd is a little longer. (probably the intermediate/setup is 1/20th the size of the target 162 package).

{Solved}
Thank you guys, I guess I didn't download the right B162 firmware.
I couldn't find it in the Huawei website for some reason and today downloaded it from here
https://www.androidfilehost.com/?w=files&flid=129430
This solved my problem

hachamacha said:
I've also had the identical problem. These ^^ people are right. You have the same model as I do , Frd-l04, so this is the link I used to get the rollback pkg:
http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098
And read the doc that you can get there, but it's pretty basic: Like they said, first install something called the intermediate rollback.app (or maybe it's update.app) and then the b162 one. First is about 100K and 2nd is about 2G . It doesn't really make a bit of sense or seem right until you've done it (like many things).
Just so you know: The way I found that was by googling .. "Honor 8 frd-l04 rollback" (or something much like that and the hit was on the first page of hits).
Other trivia: For me, I had to hold the combo up/down/power until I saw the screen saying "rolling back" (or whatever it said). You don't enter anything, it's just happening and then you can let go the keys. First one is pretty quick, 2nd is a little longer. (probably the intermediate/setup is 1/20th the size of the target 162 package).
Click to expand...
Click to collapse
Does it matter if the bootloader is locked/unlocked?

DroidMau5 said:
Does it matter if the bootloader is locked/unlocked?
Click to expand...
Click to collapse
No. On the Honor 8 applying the rollback package also re-locks the bootloader. (Yes, seems crazy).

hachamacha said:
No. On the Honor 8 applying the rollback package also re-locks the bootloader. (Yes, seems crazy).
Click to expand...
Click to collapse
Thanks so much dude, I've been stuck on a messed up B360 and I wasnt able to relock my bootloader, root, or even use my smart key for 2 weeks. Following this I successfully rolled back and its 100% functional :laugh:

Honor 6x OTA update bln24 B365 to B376-Full

What I don't understand is there are all these talented people out there, finding ways to do virtually anything to their phones, but there doesn't seem to be any normal solution to receiving an OTA update on a phone that has twrp and rooted and just install the update. The phone is obviously getting the right update, it restarts to install and twrp fails with error 7. There are all kinds of people saying "unpack the zip, remove the asserts line, which doesn't work, at least for this update. Also try using the dload method, but really the ultimate question is, why hasn't a simple solution to just installing this ever have been found? Is the way that all this stuff works in the background just so difficult that a legit update cannot be installed because the stock recovery isn't present? and if so, why can't a way around this obstacle be found.
I would just like to install updates as they come down (i assume by now this phone is trying to work its way up to android 8, or oreo) but i am stuck just ignoring it. I don't mind a little messing around to get things to work, i just haven't found any that actually do and don't involve wiping out the phone and installing everything again. Any answers are appreciated.

Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.

Mannan Qamar said:
Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.
Click to expand...
Click to collapse
Ok, I'll give it a shot and respond later. Like I said, I don't mind jumping through a few hoops. One question, how can I make sure whatever latest full OTA is doesn't have emui 8 in it? will that firmware finder point out what is in it?

If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB

Mannan Qamar said:
If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB
Click to expand...
Click to collapse
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?

jackmeat said:
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?
Click to expand...
Click to collapse
Ouch...this locks the bootloader....so can't get twrp or SU back on without losing my data (well, i have a backup, but would have to restore everything, at least i assume) if i unlock the bootloader

If it's stock firmware it will. Forget that download from firmware Finder

Mannan Qamar said:
If it's stock firmware it will. Forget that download from firmware Finder
Click to expand...
Click to collapse
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.

jackmeat said:
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.
Click to expand...
Click to collapse
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.

Mannan Qamar said:
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.
Click to expand...
Click to collapse
Well, I am still on EMUI 5 right now. I was kind of hoping not to go through flashing a custom ROM since I went through doing that on my LG nexus 5, and yes, it was great once it worked, it was a real pain to get to that working part. I was hoping the standard OTAs were going to get me up to android 8, and then just be happy with that. So I am unsure how I can flash TWRP again since my bootloader is locked again. Basically if I am going to be stuck wiping my phone out again, then I suppose I would be inclined to going the route of a custom ROM. So I guess it is just a matter of if I can get twrp on here again without wiping my phone again (unlocking the bootloader)

Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.

Mannan Qamar said:
Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.
Click to expand...
Click to collapse
so in essence what you are saying is that I can't go any further at all right now without wiping my phone again so i can unlock the bootloader? As of right now, I don't even know Huawei is going to release Oreo for this phone OTA, and even if it does, right now I can't get it. So since you have been so helpful (and very much appreciate it btw) what do you think is my best course? I don't think unlocking the bootloader will be an issue. i have the code saved somewhere around here. I wasn't all dead set on EMUI, it was just kind of nice staying somewhat in the realm of legit. And no, I have no qualms about straying outside of that. I just didn't want the nightmare I had with my nexus occurring again and not having use of my phone as a phone for the longest time. I'll await to see what you think I should do. Thanx again

Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15

Mannan Qamar said:
Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15
Click to expand...
Click to collapse
Looks like I will be stuck either way with wiping the phone, so I may as well go the custom ROM road. Don't really need to bother with the HwOTA then I wouldn't think. Unless I am missing something here. So who are the players for custom these days? still cyanogen? I saw on a search thay had android oreo 8.1. I used their custom ROM on my nexus as well. I most likely won't be getting to this now until tomorrow. I'll backup my phone...oh ****, titanium isn't gonna work. no more root....ok, i'll unlock bootloader, get twrp and root back on my phone and backup so definitely not until tomorrow. Only question for tonight is do I still need that HwOTA? I think I am a bit confused on what exactly I am trying to achieve. is it EMUI 8 with custom ROM of android 8? or nixing EMUI completely. Pardon my ignorance, but I really am just a bit hazy here on how this all works. all this for some stupid security update only because I thought it would open my phone back up to getting the OTAs and Huawei would release 8.....

Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.

Mannan Qamar said:
Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.
Click to expand...
Click to collapse
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.

jackmeat said:
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.
Click to expand...
Click to collapse
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on?
2. Do you have TWRP recovery? Or stock?
3. Lastly is your phone rooted?
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.

Mannan Qamar said:
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on? Yes the bootloader is locked now. And no, I do NOT get that warning screen anymore
2. Do you have TWRP recovery? Or stock? NO, I don't have TWRP anymore
3. Lastly is your phone rooted? No, I removed root to perform theinstall of B376-FULL and was obviously not able to root it after due to the previous
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.
Click to expand...
Click to collapse
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen

jackmeat said:
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen
Click to expand...
Click to collapse
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.

Mannan Qamar said:
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.
Click to expand...
Click to collapse
I am not trying to do anything. The phone has received an OTA update, B377, and after it downloads, it says install. click to restart now. After restarting to do the install (the everyday, normal OTA update method, nothing fancy) then it goes to that error. Only option from that black EMUI screen is "reboot now"

Bootloader Unlocking through Downgrade possible?

Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )

no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.

Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.

no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.

well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).

"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).

GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.

Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.

Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help

Resolved - L29C567B190->Build NRD90M Test-keys-> DLOAD fix fails -> Now Boot Looping

Resolved - L29C567B190->Build NRD90M Test-keys-> DLOAD fix fails -> Now Boot Looping
I've been working on the path to have my Mate 9 unlocked, rebranded, and to Pie.
I followed this guide. Not sure why, but I ended up with this:
TWRP Recovery (expected thisi)
Not upgraded to Oreo (unexpected)
Build: NRD90M Test-keys (unexpected and problematic)
I've read that I need to re-install the MHA-L29C567B190 again.
So, I attempted 2-3 times with different downloaded (supposedly MHA-L29C567B190) firmwares to just use TWRP to upgrade. All failed. So, I decided to put a DLOAD directory with the files required onto my SD card and upgrade from the Project Menu.
Of course, I had to reinstall the default recovery to do that. I did that using fastboot.
So at this point, I'm thinking I can do the reinstall of MHA-L29C567B190. So, I did this:
Launched Project Menu (*#*#2846579#*#*)
Select 4. Software Update
1. SDCard Upgrade
Phone restarts and starts the upgrade
I get this message
Software install failed!
Incompatibility with current version. Please download the correct update package.
Click to expand...
Click to collapse
So I presume I get that error because NRD90M Test-keys doesn't even have any compatible versions. I am certain I downloaded the files for MHA-L29C567B190.
Anyone have any suggestions how I can reinstall the Nouget MHA-L29C567B190 over NRD90M Test-keys?
If I can get that fixed, I can struggle again with rebranding.
Any help appreciated.

So, I went out and studied the rebrand instructions, and finally found that I misspelled the HWOTA directory on the SD Card. So I ran that again.
This time it appeared to be working on the install of the 432 software at the end of the process. But it failed for some reason.
Now I'm in a boot loop. My very first. Should I celebrate my first?
So, now on a search to find how to get out of the boot loop. I've tried the various options I do have from the boots into recovery. Exact naming of process I list below may not be accurate, but you'll probably get the idea:
Tried the option to download latest version and image...failed
Tried doing a factory reset...failed
Tried following the rebrand process once more. same results.

Update on attempt to fix bootloop...
I followed this article to repair. I downloaded a fresh c567b190 file, and copied the update.app into dload. Did a force install per the instructions...it failed.
I had another one from a different download site. It failed.
I tried a 432 file from what I was trying to rebrand to. It failed. I do find it interesting that supposedly same files downloaded from different sites are different sizes. As well, some instructions say to only copy update.app to dload, and others say to copy entire set of files/folders that are in the file that update.app is in.
Beginning to worry this phone is toast.
I'm going to search out other 'remedies'.
[EDIT]
I'm pretty sure that the build showing as NRD90M is causing my problems. I suspect the bootloader is checking against the version and "nothing is compatible" with it. So being in a bootloop with the additional problem of wrong build identification is making this difficult.

I don't know if anyone after weekend will see this and/or have any suggestions, but I'll keep updating as I learn things or stumble onto new obstacles.
I do have some success to express.
I used this thread and it got me booted, into Oreo, and a good build.
BUT...(as always)
The instructions on that thread are to unbrick, and install the rebrand files at the same time. However, during the TWRP Install process (after getting Oreo 8.0.0.046(0409) installed. It was supposed to boot into TWRP after installing it, and do that update.
But, yet another error: during TWRP install attempt, got an error about partition size (don't recall if it was too long or short or what. If anyone needs to know to help me get past this I can run it again).
So, the batch file was waiting at a prompt for me to load TWRP so it could continue. But no TWRP. So I found a TWRP for Oreo, and installed it. I then hit the ENTER key for it to continue, but it didn't.
I loaded Firmware Finder on the phone, and it found nothing to work with it. I have no idea what Oreo 8.0.0.046(0409) is even for, or what region it would be from. Can't find it even with Google.
So, here's what I need help with
What's the best way to get to MHA-L29 C432(Europe). Would it be as simple as adding my l29 model in FF, downloading c432, and installing via TWRP? Another way better?
I think I'm off of the keyboards and phone for a while. It's been quite a chase.
Hopefully I'll get some feedback early next week on how to progress.

u need find oem with hw eu region with l29, then phone can accept update

kikson112 said:
u need find oem with hw eu region with l29, then phone can accept update
Click to expand...
Click to collapse
I as thinking I had the right firmware, MHA-L29C432B194. But as I think about it, I didn't get that from FF. When I add a model of MHA-L29C432B194 in FF, and search, I find it, but I'm not sure which one I need. I understand I need FullOTA-MF-PV for dload. What is there is FULLOTA-MF, and OTA-MF . I suspect it depends on which method of install I use.
I"m thinking about trying booting to TWRP, and 'install' the ZIPS for the firmware. But I haven't seen confirmation that will work. I don't want to end up in another bootloop.

at the end what u want to do ? tell me ?

kikson112 said:
u need find oem with hw eu region with l29, then phone can accept update
Click to expand...
Click to collapse
kikson112 said:
at the end what u want to do ? tell me ?
Click to expand...
Click to collapse
I have fixed the bootloop problem from a search that I found a tutorial. The problem now is that it left me on an Orea that oeminfo (cust) is lost. It's not recognized as a valid rom.
I have another thread that has migrated to this topic. I think someone there is gathering tools for me.
I apparently need to downgrade to Nouget, and start over my efforts to migrate to c432, which then will auto upgrade me to Pie. Problem so far at this point is finding a good HWOTA8 file. All searches I find that have links are dead links.

if someone gather it let him work. give me what exacly rom u need, full name

Sorry. I am not getting the email notifications of updates. Apparently sometime in the past, I opened a different account here with my current email. It won't let me update my email address here as it is used in that other account. I've tried the Forgot password thing, but the reCAPTCHA just circles and circles and never lets me make the request.
Back on topic: I got it all worked out. I had another thread on topic of the beginning of my process that was pretty much done. But conversation struck back up, and it continued on to a fix for this problem. It's a bit lengthy, and I learned a lot there, thanks to @zgfg.
If anyone wants to see how this was resolved, you can start at Post # 60 at this thread.
Thanks folks for your input here.