Related
hi all
after re brand my mate 9 from AL00 to Al29 using this method (link below) everything goes well but the problem now i cant get OTA ! i dont know why
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
now i want to install another firmware maybe ( c185, Al00 or maybe keeping same Al29 with new update 182)
i want your help to give me advice which method is good to get OTA without problem
1- https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
2- https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
thank u
Hi
I want to install the LH29C185B182 ota on my mate 9 and I tried the dload folder method but it always gives me a fail message. please guys if you know any way to install the OTA zip files kindly inform me. :highfive:
the ota is in the team mt site but not listed yet in the mobile app !
Currently, the only ways are:
Firmware Finder
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Or Funky Huawei.
The linked thread cannot install OTA as far as I know.
Firmware finder can only install updates which are approved by Huawei (your imei must be approved, else they fail).
Funky should be able to do both but cost. money to use
thank you ante0 that was very informative. Then I guess I have to wait until it appears on firmware finder...
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
Hi everybody!
A friend of mine gave me a Honor 8, model FRD-AL10, so is the Chinese version.
I would like to install the european version of the Firmware, but i read that it can be dangerous if i dont follow the correct instructions.
I tried to check on the forum, but I did not find any guide that could help me.
Can somebody help me?
Also, if the device crashes, would it be possible to restore it?
And after I install the firmware, can I update it normally, or do I have to flash the new firmware every time?
Thanks
What is the instruction? Tell me about it. btw if phone crashed you can restore via hisuite on your computer.
Hi all,
I got my new Huawei Honor V10 Saturday and it's an excellent phone! The phone updated itself to the latest firmware as soon as it connected to WiFi.
So now I have BKL - L09 8.0.0. 163(C636)
This is an important question that might help all new V10 people....
Would it be possible to use funky Huawei to downgrade the firmware to before the July patch /update and then use DC unlocker or HCU client to unlock the bootloader??
What's your thoughts on this?
Thanks for your help
D.
Do you have a code?
If you have a code.. You don't have to downgrade
If you don't have a code.... Sorry about your bad luck
br54 said:
Do you have a code?
If you have a code.. You don't have to downgrade
If you don't have a code.... Sorry about your bad luck
Click to expand...
Click to collapse
He does not have one.
We were thinking, as DC/HCU used to work with Honor V10 (though on their site it only lists AL models, but I have seen someone use it to remove FRP lock), downgrading might be a solution. Sadly there are no dload packages for C636, but they exist for both C432 and C00 on androidhost.ru.
The thing is, if someone has already tried this and it failed OP wouldn't have to waste $45$.
So if someone on C432 who doesn't have an unlock code they could test downgrading to a May patch firmware or earlier.
I can provide instructions if you want to test.
This works fine on Mate 10/Pro as long as you haven't updated to a 02 xloader, then downgrading won't work as recovery will check xloader to prevent the brick that occurs when you flash a 01 xloader firmware on one with 02
I have a c675 on b161...I have a unlock code.. But am unwilling to root the finiky honor..
While I could.. It's not as easy or simple as my old Samsung.. Plus a lot of the features break upon flashing of other ROMs
While I would debloat tweak..I think the phone is fine as it is
Good luck...
ante0 said:
He does not have one.
We were thinking, as DC/HCU used to work with Honor V10 (though on their site it only lists AL models, but I have seen someone use it to remove FRP lock), downgrading might be a solution. Sadly there are no dload packages for C636, but they exist for both C432 and C00 on androidhost.ru.
The thing is, if someone has already tried this and it failed OP wouldn't have to waste $45$.
So if someone on C432 who doesn't have an unlock code they could test downgrading to a May patch firmware or earlier.
I can provide instructions if you want to test.
This works fine on Mate 10/Pro as long as you haven't updated to a 02 xloader, then downgrading won't work as recovery will check xloader to prevent the brick that occurs when you flash a 01 xloader firmware on one with 02
Click to expand...
Click to collapse
br54 said:
I have a c675 on b161...I have a unlock code.. But am unwilling to root the finiky honor..
While I could.. It's not as easy or simple as my old Samsung.. Plus a lot of the features break upon flashing of other ROMs
While I would debloat tweak..I think the phone is fine as it is
Good luck...
Click to expand...
Click to collapse
OP doesn't have an unlock code. OP is asking if it would be possible to downgrade using FunkyHuawei to an earlier fw, and then to use DC/HCU to get unlock code.
Same way can be done on Mate 10/Pro, I downgraded (Though through DLOAD) from C432B148-SP1 to B142 and DC was working fine. On C432B145+ (June+) it is not working at all.
But I cant find any real proof that DC/HCU was working for global Honor View 10 prior to June firmware.
And as for debloating, there's not much bloat to begin with (thankfully). And preinstalled apps, including some of Huaweis own, can be uninstalled/disabled.
I couldn't live without root But I guess I like tinkering with my phone more than actually using it as a phone, lol
Good luck
ante0 said:
I couldn't live without root But I guess I like tinkering with my phone more than actually using it as a phone, lol
Click to expand...
Click to collapse
I am the exact same here and that's why I want to root this beast lol lol!
Downgrade Honor 9 stf-l09 from 8.0.0.378(c432)
ante0 said:
He does not have one.
We were thinking, as DC/HCU used to work with Honor V10 (though on their site it only lists AL models, but I have seen someone use it to remove FRP lock), downgrading might be a solution. Sadly there are no dload packages for C636, but they exist for both C432 and C00 on androidhost.ru.
The thing is, if someone has already tried this and it failed OP wouldn't have to waste $45$.
So if someone on C432 who doesn't have an unlock code they could test downgrading to a May patch firmware or earlier.
I can provide instructions if you want to test.
This works fine on Mate 10/Pro as long as you haven't updated to a 02 xloader, then downgrading won't work as recovery will check xloader to prevent the brick that occurs when you flash a 01 xloader firmware on one with 02
Click to expand...
Click to collapse
Hi,
I have Honor 9 STF-L09 that was previously unlocked officially but when I upgraded to 8.0.0.378(c432) bootloader get locked and now I am unable to unlock it with dc unlocker it get error 375. Can you provide me with instructions how to downgrade it. Thanks
romanp_ua said:
Hi,
I have Honor 9 STF-L09 that was previously unlocked officially but when I upgraded to 8.0.0.378(c432) bootloader get locked and now I am unable to unlock it with dc unlocker it get error 375. Can you provide me with instructions how to downgrade it. Thanks
Click to expand...
Click to collapse
You would have to use service firmware from androidhost.ru. I would downgrade to the version which is GPU Turbo. That one might work with DC.
You get instructions with the firmware, but basically just you unzip the file, copy the 'dload' folder from 'Software' to microsd and start dload mode (Vol up + down + power).
ante0 said:
You would have to use service firmware from androidhost.ru. I would downgrade to the version which is GPU Turbo. That one might work with DC.
You get instructions with the firmware, but basically just you unzip the file, copy the 'dload' folder from 'Software' to microsd and start dload mode (Vol up + down + power).
Click to expand...
Click to collapse
HI,
Thanks for quick reply. I will try your method later on but I would like to say that
I did try to downgrade to STF-L09_C432B130 from 4pda.ru/forum via SD card method in *#*#2846579#*#* but it failed at 5%
Any Idea what could be wrong? Also can you tell me how do I know that firmware is GPU Turbo? Thanks
romanp_ua said:
HI,
Thanks for quick reply. I will try your method later on but I would like to say that
I did try to downgrade to STF-L09_C432B130 from 4pda.ru/forum via SD card method in *#*#2846579#*#* but it failed at 5%
Any Idea what could be wrong? Also can you tell me how do I know that firmware is GPU Turbo? Thanks
Click to expand...
Click to collapse
B376 is the build that added GPUTurbo so you should be able to downgrade to that.
They added a new bootloader in that so you can't downgrade past it.
(You can technically but your device will hardbrick and you need to flash with TWRP or NoCheck recovery).
It may be possible because huawei started preventing downgrades in Pie, and I'm not sure if they've done so in later builds of Oreo too...
ante0 said:
He does not have one.
We were thinking, as DC/HCU used to work with Honor V10 (though on their site it only lists AL models, but I have seen someone use it to remove FRP lock), downgrading might be a solution. Sadly there are no dload packages for C636, but they exist for both C432 and C00 on androidhost.ru.
The thing is, if someone has already tried this and it failed OP wouldn't have to waste $45$.
So if someone on C432 who doesn't have an unlock code they could test downgrading to a May patch firmware or earlier.
I can provide instructions if you want to test.
This works fine on Mate 10/Pro as long as you haven't updated to a 02 xloader, then downgrading won't work as recovery will check xloader to prevent the brick that occurs when you flash a 01 xloader firmware on one with 02
Click to expand...
Click to collapse
I have. A question It's possible to unpack update.app with xloader2.Img replace for xloader1.img from update before July pacht and repack and this shloud work? Or not I'm so noob I'm. Sorry for the question anybody tried?
ante0 said:
B376 is the build that added GPUTurbo so you should be able to downgrade to that.
They added a new bootloader in that so you can't downgrade past it.
(You can technically but your device will hardbrick and you need to flash with TWRP or NoCheck recovery).
It may be possible because huawei started preventing downgrades in Pie, and I'm not sure if they've done so in later builds of Oreo too...
Click to expand...
Click to collapse
Yes, thanks I did managed to downgrade to 376 and tried to use dc again with same error 375. I did notice that my phone is not in device manager modem section as required by DC May this be a reason? Also what is downgrading in Pie ?
romanp_ua said:
Yes, thanks I did managed to downgrade to 376 and tried to use dc again with same error 375. I did notice that my phone is not in device manager modem section as required by DC May this be a reason? Also what is downgrading in Pie ?
Click to expand...
Click to collapse
Downgrade to a previous build. Like B197 to B179. Can't be done in Pie.
You could try with the Handset ProductLine drivers found in DCs download section, but if it can read phone it means it should work if it's not patched in B376. So chances are they added it in B376, and you can't downgrade past it.
You didn't save unlock code last time you got it?
ante0 said:
He does not have one.
We were thinking, as DC/HCU used to work with Honor V10 (though on their site it only lists AL models, but I have seen someone use it to remove FRP lock), downgrading might be a solution. Sadly there are no dload packages for C636, but they exist for both C432 and C00 on androidhost.ru.
The thing is, if someone has already tried this and it failed OP wouldn't have to waste $45$.
So if someone on C432 who doesn't have an unlock code they could test downgrading to a May patch firmware or earlier.
I can provide instructions if you want to test.
This works fine on Mate 10/Pro as long as you haven't updated to a 02 xloader, then downgrading won't work as recovery will check xloader to prevent the brick that occurs when you flash a 01 xloader firmware on one with 02
Click to expand...
Click to collapse
You're the master!
ante0 said:
Downgrade to a previous build. Like B197 to B179. Can't be done in Pie.
You could try with the Handset ProductLine drivers found in DCs download section, but if it can read phone it means it should work if it's not patched in B376. So chances are they added it in B376, and you can't downgrade past it.
You didn't save unlock code last time you got it?
Click to expand...
Click to collapse
Unfortunately I could not find the code I was given before.
DC does not identify my phone by name and model it is just saying Found Applications port
Also in DC app on my phone there is no option for code by IMEI ???
I could not find a specific drivers for my phone in download section of Dc site. There is two files for Huawei Android phone drivers but I do not know how to instal them.