Related
[Solved] I had the l09-c636b191 official version no new ota updates with that version,
Then I did the following:
1.Download l09-c636b210 and install with dload method(works without problem)and download b321 and dload inst..(no problems).
Then I came up with the idea to install nougat beta,downlod l09c636b521:
2.Unlock bootloader and install twrp recovery and doo factory reset...
3.Flash update.zip(only that,it`s mistake,I did not know that need hw update_data.zip ) got errors during flashing after finish restart phone and phone boot with nougat...
4.First no kayboord only google voice,I went through anyway from setup,second many apps missing like clock...settings crashes,and THEMES NOT WORK,MAGAZIN UNLOCK does not exist no wallpapers.In about phone said test kay..
Then I decided to back on b321,then I realized that it was all because I did not flash data.zip(I did not have)
5.Back to b321 with dload and install phone boot and goot with Blinking screen asking for password,I switched off phone and boot in stock recovery doo factory reset after that phone on and setup start(with kayboord)...
6.On home screen the first thing I noticed icons and wallpaper are stock google no emui look,and go to change thames same problem no stock themes(any other not work) and unlock magazine does not exist no wallpapers.But is stable 6.0
I decided to try again to flash android 7.0,just this time with data.zip(download from one xda user)
7.I did everything like at the beginning 2.
Flash update.zip and hw_update.spsceas.zip got errors during installition,after finish installation,it was all the same no kayboord...etc
8.Back to b321 again with dload(this time no password or blinking screen)but is same like latest time themes not work ickons and wallpapers stock android.
Now system is stabile but not 100% have some bugs.
9.Try to register on Malesya beta test progaram for nougat I succeeded in that said got my ota update on december 31. But still no update in settings and notphing in hicare.
Need help for this,would like everything to be like when I bought the phone(system fully functional)
What I doo,any suggestion?
Thanks
Solved problem:
Unlock bootloader+install twpr+root
Go to srk tool,until and install hw_init.
Now themes and magazine unlock work agine,also new notification like sms,viber...tourn screen on when is locked.
interesting. i have L09 C636 (single sim 32GB model) too, in australia.
but not really keen to root yet, can i just unlock bootloader and then install nougat beta,downlod l09c636b521 ????
erwinsie said:
interesting. i have L09 C636 (single sim 32GB model) too, in australia.
but not really keen to root yet, can i just unlock bootloader and then install nougat beta,downlod l09c636b521 ????
Click to expand...
Click to collapse
Yes you cant install nougat without root,need to flash with twrp.Nougat for my not work good.I am nou on android 6.0 b321 emui 4.1
So you are staying away from Nougat ok
Some context:
My MHA-L29C432B138 with TWRP got an OTA update on the phone itself, and I wanted to update (it wanted me to update to B182).
Since I had TWRP replacing the stock recovery I could not flash it through the normal way, so I went ahead to replace TWRP with the stock recovery so I could update.
I was unable to flash the stock recovery since I had no access to flashing in fastboot (FRP Lock, PHONE Unlocked, OEM unlocking option greyed out in developer settings), so I attempted to relock so I could unlock again, hoping that would solve my issue (fastboot oem relock KEY).
By doing this my phone went into a reset, now I'm stuck at FRP Lock, PHONE Relocked, and I can only access the bootloader and eRecovery.
eRecovery is attempting to download updates but fails every time, and I can't use HiSuite to do a system recovery neither (says my device is not supported).
So this is where I'm stuck, any help would be nice!
p3lim said:
Some context:
My MHA-L29C432B138 with TWRP got an OTA update on the phone itself, and I wanted to update (it wanted me to update to B182).
Since I had TWRP replacing the stock recovery I could not flash it through the normal way, so I went ahead to replace TWRP with the stock recovery so I could update.
I was unable to flash the stock recovery since I had no access to flashing in fastboot (FRP Lock, PHONE Unlocked, OEM unlocking option greyed out in developer settings), so I attempted to relock so I could unlock again, hoping that would solve my issue (fastboot oem relock KEY).
By doing this my phone went into a reset, now I'm stuck at FRP Lock, PHONE Relocked, and I can only access the bootloader and eRecovery.
eRecovery is attempting to download updates but fails every time, and I can't use HiSuite to do a system recovery neither (says my device is not supported).
So this is where I'm stuck, any help would be nice!
Click to expand...
Click to collapse
Try to unlock after this.
This does low-level format.
My device: Mate 9 supersu B190 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Everything in fastboot (flashing, locking, unlocking) was unavailable, eRecovery was not working, HiSuite said my device was not supported, and dload didn't work neither (tried 3 different firmware versions).
After spending 1-2 hours on Telegram with others I ended up using funkyhuawei with eRecovery, only thing that worked for me.
Last time I buy a Huawei device for sure, their own services don't even work (eRecovery, HiSuite).
p3lim said:
Everything in fastboot (flashing, locking, unlocking) was unavailable, eRecovery was not working, HiSuite said my device was not supported, and dload didn't work neither (tried 3 different firmware versions).
After spending 1-2 hours on Telegram with others I ended up using funkyhuawei with eRecovery, only thing that worked for me.
Last time I buy a Huawei device for sure, their own services don't even work (eRecovery, HiSuite).
Click to expand...
Click to collapse
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
I'm on the same situation after a ROM installation using HWOTA failed, I don't want to pay $50 to unbrick the phone, could you please give me instructions on how to get this patched hisuite or which file I have to modify?
Thanks!
dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
Hi, am on the same situation, could you plz provide detailed steps to patch hisuite am unable to find any lucx's script.
i got my phone bricked like this
I could fix my phone flashing a factory firmware using DC Phoenix (Yes, I have to pay).
I Flash MHA-AL00 first, then I use eRecovery to install the latest stock firmware and finally HCU Client to repair the empty board (IMEI, S/N, MAC, etc).
I had the same then suddenly it is hardbricked no charging no nothing . It was a 1 month old phone. I didnt do anything other than downloading a c636 oreo and i was c185. But i received it trough the system update using firmware finder and even it authenticated itself. Even installed it with no problem. Then suddenly it broke and after soft brick became hard brick nothing. Now it in service centre i hope they can fix it. It is under warranty. pray for me
help me please
i have the same problem what should i do please help
dealth645 said:
As I said here, for your case the patched HiSuite method would have worked. But it's too late now, you paid, I was in holidays.. I know it's a shame that HiSuite says unsupported or erecovery not working but you could have made your phone compatible by writing some text in a file and using Lucx's script instead of paying funkyhuawei, their service never worked for me.
Click to expand...
Click to collapse
Same problem here with Mate 10, can you teach me how to write some text in a file and using lucx's script instead of funkyhuawei? THANKS!
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.
My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while.
Recently I tried updating to B130 in order to get Android 7 finally, but got problem that the successful update takes no effect at all. I still remain at B120 and keep receiving update notification to B130. I described my steps recently as below:
Try Updater
First of all, I tried using Updater downloading the package and install, it says update failed because the package it not found. I found the reason is the update package is stored in internal storage other than SD card. Then I created dload folder and moved update package to SD card, but Updater cannot detect it and keep telling me to download B130. Therefore, I tried pressing Volume Up, Down and Power button together. Then the package is detected and installing started. It is very fast and I was told install success. However, after rebooting I still have B120 and am told to update to B130 by Updater.
Unlock bootloader and root
Yesterday, I decided to try custom ROM, so I managed to unlock the bootloader, install TWRY and root the phone, though I still cannot make B130 update take effect. I searched for a few custom Rom with Android 7, but I found they still required a higher firmware version than B120, like this ROM, which requires EMUI 5.X.
The help I need
I wonder if I can flash the ROMS that require a higher firmware version when I only got B120 firmware. If I cannot, how can I get my firmware updated, through Updater or any other way (like TWRY possibly) ?
I hope I have stated my problem properly so that you guys can understand. I appreciate any suggestions!
Jlw_ said:
My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3461043
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hello,
Please, i need help. I have problem with my honor 8.
Ill start from begining.
My original fw was frd-l02c432. (Im from eu, czech rep.) But since i wanted oreo update, ive done something wrong. Ive downloaded new update, and ended up with nrd90 test keys. After little play, ive manage to downgrade to frd-l02 c675. Just was unable to upgrade. ive download new sw via FF, install, and now im stuck again on test keys. I cant install twrp. Because, when i unlock bootloader, the oem option will grey out, and cant switch on. Cant install FF, because i have no keyboard. (Also update option is missing in settings) Erecovery is not working - cant find package. And when i download recovery package for c675b130 (or c432) and update via dload, it stuck in 5%- failed.
Is there some way to resurect him back to land of living ? or his only way to live is service center. I know, its almost sure, but i want to try fix it myself. And leave the service as a last resort.
Emui 5.0
Android 7.0
Thanks and have a nice rest of the weekend.
Andy.
EDIT: ok ive solved it (i think ) ive flashed twrp to boot instead of recovery. So phone did not start, but i was able to enter twrp. Then rebranded phone to frd L09 (my region with 432) via TWRP. Instal B380 via FF (with unlocked bootloader and twrp). then reflash TWRP back to normal recovery (because when the phone showed me new update, I was unable to install. ive downloaded the update, then hit install. Phone restarted to twrp and it showed me "error 7" when installing. So Ive uninstaled twrp. then download again. Phone restarted and update installed just fine). i just need to download the "latest package" via update from system everytime, so it will take time Maybe it will help someone. see ya