Any B126 force update solution? - Huawei Mate 9 Questions & Answers

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

Related

rooting doogee dg100

Hi all im just looking at a cheap phone for my mom that will pretty much just be used for phone calls and texts but I was wondering if anyone has got one of these phones and if you can root them so I can delete some rubbish off it so she has got some more room for apps as they only have 4g I believe if anyone could help id be really grateful
Jxt. said:
I didn't see any sites that talks about rooting, but you should check out the one click rooting application to see if your device is supported.
Click to expand...
Click to collapse
Thanks I'll give it a try when it comes through
Has anyone got a link to this app please and also is this the only way that may be possible thanks
Rooting DG100
galaxys3_newbie said:
Thanks I'll give it a try when it comes through
Click to expand...
Click to collapse
I'm also contemplating rooting one of these and would appreciate if you could comment on the success of One Click Rooting.
Thanks
I will do just waiting for it to come through what do you thonk of the phone
Sent from my GT-I9300 using xda app-developers app
galaxys3_newbie said:
I will do just waiting for it to come through what do you thonk of the phone
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Try Shuame
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
the flash tool
serafis said:
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
Click to expand...
Click to collapse
Hi,
I don't know if it's because it's all written in Chinese when I get to the page with the actual zip on it or if it's because I'm blind and am missing some important visual cue on the page, but I can't figure out how to download the firmware or how to get the tools. Any advice on this? I even tried looking at the source code to see if there is a direct link to the file, but it's all full of JavaScript.
Incidentally, is there any indication on the site as to whether we might expect a newer version of Android on this phone in the future?
problem with dg100
Hi, i need your help to fix my DG100, i tried to upgrade following the instructions in the website of Doogee and now the phone is not working at all. when i click in UPGRADE&FIRMWARE and connect the phone i got an error: SP FLASH TOOL ERROR: (8045) NO VALID PARTITION MANAGEMENT TABLE (PMT) FOR STORAGE DEVICE and when i click in DOWNLOAD and connect the phone i got : BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). Please, can you tell what i must do for fix this problem?. Thank you for your help.
Firmware 0926
tuxedo116 said:
Hi, i need your help to fix my DG100, i tried to upgrade following the instructions in the website of Doogee and now the phone is not working at all. when i click in UPGRADE&FIRMWARE and connect the phone i got an error: SP FLASH TOOL ERROR: (8045) NO VALID PARTITION MANAGEMENT TABLE (PMT) FOR STORAGE DEVICE and when i click in DOWNLOAD and connect the phone i got : BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). Please, can you tell what i must do for fix this problem?. Thank you for your help.
Click to expand...
Click to collapse
If you use the SP_Flash_Tool_v3.1320.0.174, you will manage to overcome that problem, but then you'll face the real one. The real problem is that your,phone like mine too, has a different version LCD display, that needs firmware 0926 to work right. If you use 0917, phone will flash, reboot, but show garbage on screen. I am asking Doogee to provide me the 0926 firmware (the one that my phone had installed when it arrived 5 days ago), but they don't reply to my mails. It also seems that the new display is not IPS as the earlier versions, as it greys while on angle and shows color shifting (obvious even with garbage on screen...).
I am waiting for a second DG100 within next week, so if anyone can share a way about extracting 0926 firmware from it, i would be obliged...
Asterisd said:
If you use the SP_Flash_Tool_v3.1320.0.174, you will manage to overcome that problem, but then you'll face the real one. The real problem is that your,phone like mine too, has a different version LCD display, that needs firmware 0926 to work right. If you use 0917, phone will flash, reboot, but show garbage on screen. I am asking Doogee to provide me the 0926 firmware (the one that my phone had installed when it arrived 5 days ago), but they don't reply to my mails. It also seems that the new display is not IPS as the earlier versions, as it greys while on angle and shows color shifting (obvious even with garbage on screen...).
I am waiting for a second DG100 within next week, so if anyone can share a way about extracting 0926 firmware from it, i would be obliged...
Click to expand...
Click to collapse
Hi, thank you for your answer, i am using SP_Flash_Tool_v3.1320.0.174 but nothing happen, could you please tell me, how can i do to overcome the problem?, thank you.
tuxedo116 said:
Hi, thank you for your answer, i am using SP_Flash_Tool_v3.1320.0.174 but nothing happen, could you please tell me, how can i do to overcome the problem?, thank you.
Click to expand...
Click to collapse
Ok, i managed to get my phone working again, by using an extracted rom from a phone with 0926 firmware.
h**ps://docs.google.com/file/d/0B2JMI3yL-RxZWHdYaFYycDhsdUE/edit?usp=sharing
Download this files, extract them in folder with firmware 0917 and then flash them to the phone. This will work until we get the firmware from the factory (if it ever publishes it). Doogee no more for me, by the way, their customer support sucks...
Files from 0926
Asterisd said:
Ok, i managed to get my phone working again, by using an extracted rom from a phone with 0926 firmware.
h**ps://docs.google.com/file/d/0B2JMI3yL-RxZWHdYaFYycDhsdUE/edit?usp=sharing
Download this files, extract them in folder with firmware 0917 and then flash them to the phone. This will work until we get the firmware from the factory (if it ever publishes it). Doogee no more for me, by the way, their customer support sucks...
Click to expand...
Click to collapse
Yo, i tried using the files you uploaded to flash. however, i am still faced with the BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). btw, i also used the SP_Flash_Tool_v3.1320.0.174
dealer12 said:
Yo, i tried using the files you uploaded to flash. however, i am still faced with the BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). btw, i also used the SP_Flash_Tool_v3.1320.0.174
Click to expand...
Click to collapse
Doogee announced new firmwares, 0926 and 1101 for DG100 at their site. Try 1101 first and then the 0926.
Solution
I solved the problem of the error 4032, steps:
1) i used windows xp, i don't know if it will work in windows 7.
2) i did use firmware 9_26 and flashtools v3.1328.
3) select the scatter of the firmware 9_26, leave marked only PRE-LOADER and click in DOWNLOAD.
4) Keep pushed (power) + (volume -) and connect the cable to the pc. You must see the red line, then purple and finally the green circle, then disconnect the cable.
5) Now unmark PRE-LOADER and mark the rest of the options and click in DOWNLOAD; then connect the cable keeping the buttons (power) + (volume -) pushed; now you must see the red line, then the yellow line and the green circle.
Thanks to Asterisd for your advice.
serafis said:
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
Click to expand...
Click to collapse
I've done the extact same thing however I am not able to download twitter, whatsapp, skype or facebook after uninstalling and reinstalling in Play Store. The message I receive is the software is not digitally signed. The camera sucks really bad after doing the latest firmware upgrade. Is it me or am I missing something in the process ?
Doogee Collo Dg100 boot problem
I have a Doogee Collo DG100.
I have tried to flash a new ROM but at the middle of the process I got an error from SP Flash Tool "BROM ERROR:S_NOT_ENOUGH_STORAGE_SPACE(1011)". Now the phone does not start.
Can you please tell me what to do?
psild said:
I have a Doogee Collo DG100.
I have tried to flash a new ROM but at the middle of the process I got an error from SP Flash Tool "BROM ERROR:S_NOT_ENOUGH_STORAGE_SPACE(1011)". Now the phone does not start.
Can you please tell me what to do?
Click to expand...
Click to collapse
I get an error at wi-fi settings NVRAM WARNING: Err = 0x10.
Can anyone tell me what it is?
Tony Speaks said:
Hi,
I don't know if it's because it's all written in Chinese when I get to the page with the actual zip on it or if it's because I'm blind and am missing some important visual cue on the page, but I can't figure out how to download the firmware or how to get the tools. Any advice on this? I even tried looking at the source code to see if there is a direct link to the file, but it's all full of JavaScript.
Incidentally, is there any indication on the site as to whether we might expect a newer version of Android on this phone in the future?
Click to expand...
Click to collapse
I use Chrome which seems to auto-translate and gives me a Chinglish version of the screens, which makes it a lot easier.
I assume you got to the pan.baidu download site? If so, in the middle of the screen there is an icon that looks a bit like a suitcase. Above and to the right there are two rectangular buttons, one blue and the other unfilled. Click the unfilled one. A popup window will appear with another two rectangular buttons at the top, one blue and one unfilled. Again click the unfilled one. That should start the download.
This site has a list of the latest downloads: http://www.doogee.cc/en/gb/xiazai.asp - I'm currently running DG100-0917 and about to try DG100-1101
Hope that helps.
---------- Post added at 01:16 PM ---------- Previous post was at 01:03 PM ----------
rci_canada said:
I've done the extact same thing however I am not able to download twitter, whatsapp, skype or facebook after uninstalling and reinstalling in Play Store. The message I receive is the software is not digitally signed. The camera sucks really bad after doing the latest firmware upgrade. Is it me or am I missing something in the process ?
Click to expand...
Click to collapse
What's the exact wording of the message(s) you get? I recall I had some difficulty with this and googled how to overcome it, including deleting incorrect application IDs and certificates from one of the Android files - sorry, I can't now remember exactly what steps I followed but if you can post the exact message I'll try to help.
I don't think I was able to get Facebook to update from Play, no matter what I did. I think I read somewhere that this might be to do with one of the themes that Doogee / Mediatek use being incompatible with later versions of Facebook.
Anyway, please post the message(s) and I'll see what I can do.
Cheers.
DG100-1101 breaks WiFi
I installed the latest firmware, DG100-1101 but unfortunately Wi Fi and Bluetooth don't work, and when I reverted to DG100-0927 I get an odd entry in WiFi settings NVRAM WARNING Err = 0x10. Everything else seems OK though.
I would advise NOT upgrading to this version and if anyone finds a fix for the Wi Fi issue' please post here, thanks

ROOTING Note 10

Hi all,
Someone know How can I Root my device?
You can not yet...
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
mudnightoil said:
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
Click to expand...
Click to collapse
As a fresh owner of Honor Note 10 I was curious if it's possible to have the bootloader unlocked. Just finished chatting to the admin from the website and he claims that YES, they offer this service for 30EUR. But then I asked him if there's an actual way to root the device and he wouldn't know. My point here is: there's not much of a point to have an unlocked bootloader if you can't get the root on the phone. I think we will have to wait a bit longer till someone gets a working root method. I wouldn't mind to pay for having the bootloader unlocked (for reasonable amount of moneyh) as long as it works...
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
mudnightoil said:
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
Click to expand...
Click to collapse
Given Huawei's recent dull attitude that reads something like "LOCKED BOOTLOADER is for your safety only" (BLAH BLAH BLAH), reasonable doubt of a commonly available ROOT for this magnificent device is more than imminent...
But hope is all there's left, right
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
Hmmm... there seems to be some work in progress alright regarding a custom TRWP for Note 10, if the google translator works fine, that is:
https://translate.google.com/transl...m/thread-17327282-1-1.html&edit-text=&act=url
And the bootloader unlock code might get somewhat cheaper, too:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Let's wait and see, I guess
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
7gismo said:
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
Click to expand...
Click to collapse
i have downloaded but you need to have unlocked bootloader. i had also registered for that xda huawei unlocker thread, but stll waiting for unlock key.
Here : https://1drv.ms/u/s!AizwhfImY2xzgadtepfbKJ1BQqxMvg
---------- Post added at 02:08 PM ---------- Previous post was at 01:57 PM ----------
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
7gismo said:
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
Click to expand...
Click to collapse
How did you got it unlocked?
i know there are many pid sources but was waiting for someone to confirm they really work for note 10. Can you please share where you got it from?
Sure, I've posted the link already:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
I chose the fast 1-20min option and it was done that way, indeed. You must pay upfront, of course. They generated the unlock code for me and all I did was a few lines in cmd powershell while phone was in fastboot mode.
There's an ugly message coming up everytime I boot saying that my device has an unlocked bootloader?
But we need a custom CWM or TWRP image now?
I wonder if there's a stock boot image of Note 10 floating around online, perhaps in Huawei Chinese forums?
---------- Post added at 04:28 PM ---------- Previous post was at 03:35 PM ----------
bark1234 said:
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Click to expand...
Click to collapse
Just did some digging there and actually, you can find a working firmware file 125 for Note 10 online. Chances are even the latest 132 build is there somewhere on Chinese forums...
I'd recommended you to get the bootloader unlocked from the link above, if you have a good idea how to proceed with root? My skills are way too limited, I'm afraid?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Thanks for your reports.
TWRP image file is included in K-RecTools_8e.apk.
Rename apk to zip and decompress it, you can get the twrp.img.
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
trd_jzx100 said:
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
Click to expand...
Click to collapse
OK now. I managed to flash TWRP on the phone successfully. However after i tried to flash Magisk, the phone remains unrooted So it's a no for me. Any idea why?
There's a red error stating coming up twice: failed to unmount '/system' (Device or resource busy). But the Magisk zip get installed anyway. So what am I doing wrong?
EDIT: the bloody TWRP is password protected. My pin password doesn't do the trick...
EDIT 2: OK, just removed my lock screen in phone settings, no errors in TWRP anymore. But after I flashed Magisk (no erros again), phone still remains unrooted? What the hell?
What version magisk are you using
trd_jzx100 said:
What version magisk are you using
Click to expand...
Click to collapse
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway?.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation ?. But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
7gismo said:
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation . But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Click to expand...
Click to collapse
bark1234 said:
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
Click to expand...
Click to collapse
I'll see what I can do. The least I can do is to create a brief tutorial how to root this beauty of a phone?.
Thanks again for your tremendous help

Any USA Mate 9 users on EMUI 9 / Pie 9?

Wondering if we will still see the 9.1 update here in the US....
Thanks. Upgrading to 9.1 is what I am thinking about. But after many failed tries, I gave up, for now.
Still on 8.x, and no sign of 9.x.
No help from query made to Huawei USA.
Same here, Oreo 8.0 with B377. Nothing in FF either
Had Live Chat with Huawei USA re this, and in summary the answer was ..."if and when the update is released, it will be uploaded to your phone automatically.".
The operative phrase being "...if and when...".
Sadly, I don't see it happening. With each day, the tension between Huawei and the U.S., now the rest of the world, I don't see anything further from them, for the 9, which is why I went with a different phone in November. After the Mate2, 8, 9 I was looking forward to more Huawei phones, but, with dropped support for the U.S. (rightly so), I had to move on.
Great phones, but without DIRECT OEM support for a U.S. model, I'm just not into the whole root, unlock, flash stuff anymore.
If it doesn't come from the OEM, I don't bother with it. Just gettin' too old....now get off my lawn!
I pretty much agree, except Google and Android bowing to the ban pressure, causes me to rethink not only future Huawei products ( “...if, and when they become available in the USA”), but also Android and Google. I have avoided the dark side (Apple) till now, but am rethinking that..
OnePlus has a good reputation. But in older models I read about higher radiation emissions than other peer phones at that time.
I am thinking of having it once my mate 9 dies...
Sent from my MHA-L29 using Tapatalk
Zalophus said:
I pretty much agree, except Google and Android bowing to the ban pressure, causes me to rethink not only future Huawei products ( “...if, and when they become available in the USA”), but also Android and Google. I have avoided the dark side (Apple) till now, but am rethinking that..
Click to expand...
Click to collapse
I won't go *that* dark, as I can't ever imagine owning Apple. It's tricky because I want this phone, just upgraded. I'm all in on Google, just can't find a great phone at a decent (sub $500) price...
EMUI 9 Pie 9 available according to firmware finder
MHA-LGRP2-OVS 9.1.0.252 FullOTA-MF dated 7/17/2019 available according to FF for MHA-L29C567
I just bought a OnePlus 6t and it's has 8gb ram yada yada and really zippy. I like the mate 9 more. The screen on the mate is nice and bright and the sound quality from the headphones blows away the 1+. I even rooted the 1+ and increased the headphones to 90 but still quality is not as good. I like the volume and power on the same side of the mate. I'm desperately trying to figure out how to get pie on it. I'm going to post a question about what files are out there I can flash. I've tried and failed so far.
It's been a while since anyone asked: is there any way to get C567 to 9.0/9.1?
I'm at MHA-L29 8.0.0.360(C567) --never bothered to get to the latest Oreo 377 (doubt that has an effect as I've been going for the FullOTA-MF).
Today I tried firmware finder erecovery and patched hisuite on numerous 9.0 and 9.1 firmwares that were supposedly approved for my IMEI. I haven't tried rebranding, dload method (don't even know if that exists for C567 Pie), or emuiflasher.
Anyone been able to do it?
(I confess I've posted this same question two a couple of other threads here on XDA).
I also keep trying and ran across this article and says to use flashy to manually flash the 2 beta files for 9.0 way back in january. I wonder if I can use the flashy tool to flash the current 9.0 432 files for now and let those update to 9.1 when it happens. Had I seen this article way back in January I would have tried it. You can use the second link to download any version of android for the mate 9. Type "mha-L29" into the search field where it says "enter model" and press enter. Then just left click on the "filelist" and a second later it will pop up. The cut and past the url into a new window and press enter and it will start downloading. If the beta files will work with flashy then why not the actual files. In xda the p20 forum has similar instruction for beta pie back in 2018.
https://www.getdroidtips.com/huawei-mate-9-android-9-0-pie-update/
https://pro-teammt.ru/online-firmware-database-ru/
Edit: Someone did the exact thing I was thinking about with the p10. He used ff to download the actual files and used flashy. Maybe I'll give it a shot earlier tomorrow. I'm not sure how to use flashy yet though. It says unzip the update files into the unzipped flashy folder but not sure where in the folder. I guess I can try and see.
https://forum.xda-developers.com/mate-10/help/pie-upate-t3891577
jeffrimerman said:
I also keep trying and ran across this article and says to use flashy to manually flash the 2 beta files for 9.0 way back in january. I wonder if I can use the flashy tool to flash the current 9.0 432 files for now and let those update to 9.1 when it happens. Had I seen this article way back in January I would have tried it. You can use the second link to download any version of android for the mate 9. Type "mha-L29" into the search field where it says "enter model" and press enter. Then just left click on the "filelist" and a second later it will pop up. The cut and past the url into a new window and press enter and it will start downloading. If the beta files will work with flashy then why not the actual files. In xda the p20 forum has similar instruction for beta pie back in 2018.
https://www.getdroidtips.com/huawei-mate-9-android-9-0-pie-update/
https://pro-teammt.ru/online-firmware-database-ru/
Edit: Someone did the exact thing I was thinking about with the p10. He used ff to download the actual files and used flashy. Maybe I'll give it a shot earlier tomorrow. I'm not sure how to use flashy yet though. It says unzip the update files into the unzipped flashy folder but not sure where in the folder. I guess I can try and see.
https://forum.xda-developers.com/mate-10/help/pie-upate-t3891577
Click to expand...
Click to collapse
Nice find jeffrimerman! Looking around, I found the original developer of the beta flashy tool is @a1Pha, who designed it for the P20 Pro. Here's his OP on the method:
https://forum.xda-developers.com/hu...uide-how-to-install-emui-9-android-9-t3839316
I read thru the 45 pages of comments in that thread and saw a couple of folks that had successfully used the tool to upgrade from Oreo to Pie and rebrand at the same time. Also a couple of folks who used it on other Huawei models. The tool requires two zip files, so I think you're right about needing to upgrade to 9.0 first (as 9.1 has a single zip file).
Quite a bit of discussion in the thread relates to maintaining bootloader and FRP open. It seems we might end up with those locked, making it difficult to change/upgrade ROMs other than by OTA. That would mean that under the worst scenario (other than some unexpected bootloop), we might get stuck on that 9.0 ROM if for some reason Huawei checks IMEI and not region for upgrades. The thread also has a post (linked in the OP) that has a modified FLASH.txt file to use to upgrade from "Beta to Beta" and another for getting back to Oreo, so even this scenario might be avoided.
As for where to put the zip files, the beta-flash_0.2.zip, once unpacked, has a folder conveniently labeled "ZIPS-HERE"!
I'm currently downloading MHA-L29 9.0.1.191(C432E7R1P8) from FF, and will wait to hear from your test to give it a shot! Good luck, and I'll help anyway I can if something goes south. :good:
---------- Post added at 09:52 AM ---------- Previous post was at 09:19 AM ----------
Opening the FLASH.bat in beta-flashy, I noticed it installs a custom "No Check" recovery. It probably has a "secret sauce" in it, so it's probably required to use the one for the P20 Pro that's in the original tool. For a moment I thought of replacing it with the "No Check" recovery for MHA specifically in the HWOTA8 tool (also by @mankindtw but slightly different file size), but best not to tinker too much?
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
https://www.dropbox.com/s/11ghma7pqkbq32h/MHA_RECOVERY8_NoCheck.img?dl=0
Oh wow, I actually PM'd him last night asking about exactly how to use the tool. I tried downloading from his link on that post but it didn't work. I did see the zips here so I'm sure you're right on that. The article I posted here mentioned unzipping the updates so that's what confused me. I'll have to read that guys post and see if he mentions it. Maybe he'll respond to my pm before I attempt it. He also flashed a beta 9.0 and wasn't sure if updates would come ota after that so maybe he'll know by now since it's been months. If I don't get a response then I'll ask in his thread. Has 9.0 been able to be rooted? I have my unlock code still so I can redo that from adb if I need to.
I didn't have any trouble downloading the beta flashy, but just in case, here's a copy:
https://www.dropbox.com/s/te9fcilkphi7n7i/beta-flashy_0.2.zip?dl=0
I'm not that concerned about further updates once we're on 9.0 C432, for example to 9.1. There seem to be multiple options in case OTA doesn't work: using the beta-flashy with the "beta to beta" modified script, using the EMUIFlasher_1.2.apk (intended for OpenKirin, but apparently useful for rom changes within Oreo or within Pie--but not between them), the FF eRecovery method, modified HiSuite (probably the best option as I believe it doesn't require root, unlocked bootloader or data wipe), or perhaps HWOTA9:
https://forum.xda-developers.com/mate-9/how-to/emui-9-0-beta-t3857239/page18
Let me know if you decide to pull the trigger! I'm tempted to give it a shot too.
---------- Post added at 01:08 PM ---------- Previous post was at 12:27 PM ----------
Regarding root on 9.0/9.1, it seems patching recovery with Magisk is working, although with some hiccups especially in 9.1 (stock phone app crashes):
9.0: https://forum.xda-developers.com/mate-10/how-to/guide-magisk-root-mate-10-pro-t3886967
9.1: https://forum.xda-developers.com/hu...nt/guide-magisk-root-p30-pro-bl-code-t3938285
Note that having bootloader unlock is indispensable for root. Glad I got it back in the day!
I've got the files, same ones you downloaded. The guy that updated with flashy on his mate 10 back in Jan couldn't remember exactly what he did.
"Download the firmware and extract it inside the same flashing tool extracted area" - This is from the article so it sounds like extract them into the "zips here" but then they technically wouldn't be zips so makes me wonder.
"Extract the firmware bundle, you'll get two ZIPs and some XMLs." - Tool creator says something similar but he said you end up with 2 zips but he was talking about 1 beta file which might have bundled the 2 updates together which makes me think I just put "update" and "update full yada yada" into the zips here folder.
I'm noticing if I unzip both files they both have a "META-INF" folder which could cause some confusion so it makes me think do not unzip the updates. I think tonight I'll end up trying it with the updates being zipped.
I think I'm on page 10 of the post of the p20 with the tool and one guy mentioned renaming the zips. I'll have to read and see if we need to rename them. Did you notice anything?
This was some instructions I read in a "flash.txt" file I read for using the tool to downgrade so I imagine we need to do the same to upgrade. Same name for the HuRupdater also. I think I have all the info I need
echo.
echo Put the update.zip into the "ZIPS-HERE" folder.
echo.
pause
echo.
echo Now rename the update_full_XXXXXX_hw_eu.zip to update_all_hw.zip and put it in the ZIPS-HERE folder.
echo.
pause
echo.
I assumed you would rename the zips and put them in the folder "ZIPS-HERE" without extracting the contents.
I was thinking the same thing but since both literally said extract I didn't want a brick =( hehe. I did it!!! I put the whole folder and ran it from the C root of the drive just to be safe. I thought someone mentioned it not seeing files. I followed the instructions that show on the pc in cmd promt since it pops up a cmd window and guides you through. It seem to do it smoothly then the phone boots and you have EMUI with the circle loading the file to 100%. When I hit 100% it said "update failed" and gave me one uption to reboot. I was worried I had a brick. When it rebooted a different Huawei logo came up and said "optimizing apps" and got up to 100% and booted up fine. Phone looked exactly the same which worried me. I never did a factory reset so it literally did a normal update and kept all my settings and icons the same and I never had to input anything. I checked phone info and it's build number is 9.0.1.191(C432E7), with emui verson 9.01. Success!!!!! Security patch says May 5 2019. I imagine we'll get a regular update when 9.1 rolls out to us or you can probably put resurrection remix if you want. I put that on my Xiaomi Mi 8 Lite and it's pretty nice. So far so good. My bootloader must still be unlocked since it gave me that warning. Even developer options is still there. Enable OEM unlock is checked but not greyed out so I can still lock maybe. Let me know if you have any questions.
Edit: This helped get hotspot working again
Connection your phone to the computer (may need to enable developer settings)
adb shell settings get global tether_dun_required
If the result is "null" or "1"
adb shell settings put global tether_dun_required 0
Reboot phone
So, I gave it a shot as well. All went as you described, except I didn't get to the "optimizing apps". Instead it bootlooped about 3 times and then told me there had been a problem and that it suggested a factory reset. Must have been some root app or setting after all these years that tripped the process. Anyway, I was able to then get back to a clean 9.0.1 C432 and luckily I had done a full backup to external storage with the Huawei app. I restored, had to tinker with some apps that didn't get all their settings updated and reenter my Google password, etc. but am back in business in Pie!
I did try to go ahead and update to 9.1 via FF eRecovery and modded HiSuite to no avail. Also, the phone keeps wanting to "update" me to the same firmware by installing a 20kb OTA claiming I have some unauthorized apps (even right after factory reset). So I'm a bit suspicious that I won't be getting OTA to 9.1.
Next step will be to root (I've got several apps that require it), and perhaps try the 9.1 update via EMUIFlasher or some other method in a couple of weeks if I don't get an OTA push.
Thanks for getting my courage up and working on this together. Let's keep this thread active with any updates from either of us. Hopefully this will also help other C567 Mate 9 users get to Pie.
---------- Post added at 08:22 AM ---------- Previous post was at 07:44 AM ----------
Succeeded in rooting with Magisk:
Magisk Manager apk in OP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Instructions for EMUI 9: https://topjohnwu.github.io/Magisk/install.html
That's great news, we're 2 for 2. I had Viper4Android which I never got working, magisk, root checker but not really that many root apps so maybe that helped. I wonder if we can use this same method to get to 9.1 or is that just 1 file now. I think this tool is written for 2 files, not 3 and not 1. I wonder if the "dload" method would work. I could never get the big update.app file onto my sd card. It would always fail but maybe I need to reformat it from exfat to ntfs or something. Welcome to PIE =)

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.

Categories

Resources