Related
Hi all,
I bought a H60-L12, but the manufacturer had installed the H60-L02 rom (version H60-L02V100R001CHNC00B611).
How can I install the H60-L12 version?
I've already tried to install these 5 ROMS:
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B307
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B611
H60-L12-4-4-V100R001CHNC00B118-unicom-32g
H60-L12-4-4-V100R001CHNC00B119-High-unicom
H60-L12-V100R001CHNC00B121
But I always get the error "Software Install Failed!" with the volume + & - & power method.
Also tried with the *#*#2846579#*#* and didn't worked as well.
Tried to install different stock versions and nothing.
What should I do more?
Regards,
Luis
Check INDEX
"For L12 Users ONLY" Sections you might need to restore correct version stock local.prop and build.prop
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Julsen1985 said:
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Click to expand...
Click to collapse
hi have you succeded to install L12? i found that you may need to install the L12 recovery image first and then you can flsh back to your L12 firmware have you tried?
henr721 said:
hi have you succeded to install L12? i found that you may need to install the L12 recovery image first and then you can flsh back to your L12 firmware have you tried?
Click to expand...
Click to collapse
Hi, yes I did. I wrote the way here (in german)
http://www.iphone24.org/blog/howtos...ielle-firmware-zurueck-flashen-full-restore-1
An thermalboyz included it into his collection here: http://forum.xda-developers.com/honor-6/general/huawei-honor-6-index-t2963209
Scroll down to: 3 Button Restore not working (If you change between variant example L02>L12) Or Partition been changes and cannot restore back Stock version. Use this steps below : -
From huawei club forum, which posted by Chinese, they provided a "middle package" for H60-L02/L12, L01/L03/L11/L21:
Link for refer: http://club.huawei.com/thread-4744481-1-1.html
中转包地址如下：
荣耀6移动版（H60-L01/L03/L11/L21）
荣耀6联通版（H60-L02/L12）
We have to download it, then do upgrade it first before upgrade ROM version.
P/S: If you cannot extract it, may need rename it from chinese name to latin letter.
If need assist in Chinese word, let me know.
Hope this help.
lmpcruz said:
Hi all,
I bought a H60-L12, but the manufacturer had installed the H60-L02 rom (version H60-L02V100R001CHNC00B611).
How can I install the H60-L12 version?
I've already tried to install these 5 ROMS:
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B307
H60-L12_EMUI3.0_Android4.4_V100R001CHNC00B611
H60-L12-4-4-V100R001CHNC00B118-unicom-32g
H60-L12-4-4-V100R001CHNC00B119-High-unicom
H60-L12-V100R001CHNC00B121
But I always get the error "Software Install Failed!" with the volume + & - & power method.
Also tried with the *#*#2846579#*#* and didn't worked as well.
Tried to install different stock versions and nothing.
What should I do more?
Regards,
Luis
Click to expand...
Click to collapse
Julsen1985 said:
I have the same problem but I am on version L04 at the moment and can not got back to L12. My phone is not rooted nor unlocked. I asked the support of Huawei via mail but till now no reaction from their side...
Click to expand...
Click to collapse
Julsen1985 said:
Hi, yes I did. I wrote the way here (in german)
http://www.iphone24.org/blog/howtos...ielle-firmware-zurueck-flashen-full-restore-1
An thermalboyz included it into his collection here: http://forum.xda-developers.com/honor-6/general/huawei-honor-6-index-t2963209
Scroll down to: 3 Button Restore not working (If you change between variant example L02>L12) Or Partition been changes and cannot restore back Stock version. Use this steps below : -
Click to expand...
Click to collapse
Hi all, I'm new of the forum, and this seems to be exactly the same issue I'm having.
I had to buy a replacement for my H60-L12 and I decided to buy a new one, so I went to the same store and I ordered the same phone.
When it arrived, the label indicate H60-L12, bon on the box and on the back of the phone. But when I switched on, the model name and the serial number indicated the H60-L02.
What is really strange is that, according to what I have been seeing on technical specification on internet, the L02 should have 16GB di memory, while this one has 32GB.
Do you have any idea if it is possible to verify from the IMEI what is the real model of the phone and if it is possible that a L02 firmware version was installed on a L12? I have the B316, I have tried to dowload the B316 for the L12 and put it on the dload folder, then local update, but it fails (probabily because it is the same version?).
I have download the H60-L02/L12 file indicated in the previous post, but it is very small. Is it ok?
After I have installed it using the local update procedure, what should I do?
Thanks!
I will share my experience with this issue.
As it turned out, my L12 was flashed with the wrong firmware and seens as a L02.
No way to restore the correct version with any more or less standard procedure (not even copying the built and prop files from the L12, the upgrad was always failing).
So, for future reference, what I did was:
- use the unbrick function to load a EMUI2.3 version of the firmware (at this point the phone was almost unusable because everything was crashing)
- copied the L12 B316 on the SD in dload directory
- installed using the three button procedure
The upgrade was correctly executed and now everything is working fine.
In case someone was wondering why I didn't use the unbrick function to load the L12 B316, the answer is: I did it, but it was not working. As I said, it seems that the unbrick function leaves a lot of the previous installation behind, and despite the load of the B313 (yes, I tried the 313 to be able to update then to 316 with the complete update package and have a clean installation), the update package was downloaded but not installed, always giving error. Same with the three button procedure.
So, the only way I found has been to revert to 2.3 and then apply the update.
Now I would like to know who flashed the L02 on my L12 and made me loose four days
HUAWEI P8 GRA-L09 - Lost Baseband & IMEI since attempting Marshmallow update & others
Hi, I'm in a right mess - since following the instructions from a post on here to download & update my HUAWEI P8 from it's stock firmware B200 (I think) to Marshmallow I ended up with the update freezing at 90% (I see there have been many others had the same problem too)
After trying to fathom out how to resolve the bootloop problem that occurs after this I have since downloaded many different firmwares from B170 onwards and using fastboot & adb flashed boot.img, recovery.img, system.img & cust.img succesfully with only B170 allowing my phone to eventually start without a bootloop. However now I have no baseband nor IMEI and being my only phone I am screwed without it.
Since then I have tried using TWRP to wipe the data, system, and caches clean and reinstalled firmwares galore to no success. If I try to update using EMUI it fails at 0% - using the search for latest file & recovery in EMUI fails too - copying any update.app to either internal or external storage in a folder named uload also fails at 0%.
Surely there must be a way of formatting the internal drive and installing a stock firmware which places everything back in its right place (including the baseband / IMEI) to start up like when it was 1st new?
DESPERATE FOR HELP - I HAVE NO OTHER FORM OF COMMUNICATION TO BE CONTACTED ON BY MY FAMILY - AND QUITE APPROPRIATELY CANNOT AFFORD TO GET THIS FIXED BY HUAWEI AT THE MOMENT- PHONE IS IMPORTANT TO ME!
Thanks to anyone reading this whom can help!
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.
It seems like there are a few people having trouble going back to stock and getting everything working.
As always, this requires an unlocked bootloader. If you don't have an unlocked bootloader then search google for a $5 service that does. It is what I did.
I flashed Project treble on my TA-1054. It worked great except it kept saying "insert SIM" when there was already a sim card inside, so I could not use it.
I tried to go back to stock but that firmware file on that google drive thread was corrupted, bad upload. Took me a few days to source this original firmware.
There is a tool called OST ( around 115MB), and a patch that comes with it (the smaller file less than 1MB)
The firmware is almost 2 GB
Download everything, including firmware.
1. Install the OST tool.
2. Replace the EXE file in the program files with the patch file you downloaded.
3. Delete the Onlineupdatetoolexe.config file. If you don't do this, the program will not start correctly.
4. Put phone into download mode ( either by powering it off, pluging into USB cable and immediately hold power and volume down. Or if you can boot into android with ADB debugging, just do a adb reboot bootloader.
5. Pick firmware file and click next.
THe first 2 times I tried this, It hanged at the last second. Third time was a charm. Give it time. Use a good USB cable.
I assume that this is the same way to flash other firmware files for other devices.
As soon as i get my hands on a android one firmware, I will flash it.
Or if anyone can guide me on how to extract the firmware on my TA-1045 USA version and flash it to my TA-1054 Chinese , let me know. Cheers.
Google drive folder with all the files I uploaded.
https://drive.google.com/open?id=1NbzO6lfSGacjM2wqrtBg3jMpljsZswne
Thanks bro...I am downloading it.
PL2-2380-0-00WW-B01.NBx.zip is global firmware name. firmware size is 4gb.
thanks! for extract is with nb0 tools FIH Mobile v3.4
https://drive.google.com/open?id=1cSgjrZUxIsN7oLbo7AP-RnILDZdswmB-
its android one firmware. I have no tool for flash...plz try and let me know
Flashing now. Will report back after flashing is done. thanks!!
Edit: Looks like the version I have for OST does not read NBX files. Will try to update that and report back. I have ntool but no working username password
I cannot flash the NBX file. I changed it to nb0 but OST LA says cannot read firmware. Is there any other way to flash?
EDIT: I went ahead and purchased a bunch of credits for NTOOL.
I will flash and see if it works!
It fails with the mdtp.img partition (no such partition) . I would think that it would just skip that partition but it did not. I will later try to extract and flash separately
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
stealthj said:
For some reason when I try to flash the golabl firmware using ntool, my bootloader gets locked after the mdtp flashing fails and I have to re-unlock my bootloader and flash the original 7.1 chinese firmware using the OLD version of OST. ( the new one kept saying firmware corrupt)
When I bought the credits for Ntool, I also got access to the downloads section so I will be uploading all the firmwares they have, ( there is like 5 different ones)
I was reading how the nokia &+ users are converting their chinese variants to global variants using the android P beta rom.
We also have a P beta rom so I will be trying to install that to see if it works or not.
As some of you may realize, I am determined to make this happen! The reason is because my USA android One version has only 3gb of ram but the chinese version comes with 4GB.
Click to expand...
Click to collapse
can u flash my chinese rom which is nbo format via ntool. I have have ntool but i dont have user name,password, i downloaded rom which u provide.my device still cant connect to mobile data.
NBX format only works on Ntool. but Ntool needs working user name and password to works. OST cant read or flash Nbx format.
if u get Ntool with working user id .. then plz flash my device also via remote mode like teamviewer.
Ntool Bricked my device. the only real restore you can do is by using ost with the stock chinese firmware. edit your apn. why is your data not working?
Global rom cant flash via ntool in Ta1054..showed error in partition. if it will be solved then china to global will be easy process..
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
safron35 said:
Its the Chinese official ROM you get it from Google drive folder in Nokia 6 mena firmware topic
Click to expand...
Click to collapse
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
stealthj said:
Actually, the one in the mena topic was corrupted for me.
I have uploaded a good version in the first post of this thread. I've only had success flashing it wih OST.
But yesterday Ntool bricked my phone. No download mode, no screen, no usb recognition with windows. I am not really sure what to do now. If i can't get my pc to recognize it then the phone might be dead./ I may do a warranty exchange when i go visit china next month but if they check my bootloader, they will void my warranty. anyone know how to unbrick?
Also. The nokia 7+ forums said that if you flash the android P beta rom, then the chinese vaqriant becomes gloabl.
I went ahead and downloaded the android P beta for 6.1 but now that the phone is bricked I can't really test anything. I will sell my extra 1045 before i get curious and brick that too.
Click to expand...
Click to collapse
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
TheImpulson said:
Can you share the link for P beta for 6.1?
Also, I own a TA-1054 model and I am in India. I ordered it from Amazon. It had Android One Oreo firmware preinstalled before I messed up and got loops. Later I flashed a GSI to at least boot it up.
Click to expand...
Click to collapse
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
stealthj said:
Ahh I see. For some reason my sim slots were not working for me with GSI. But mine is dead now, so nothing I can do.
Here is the P link.
https://drive.google.com/open?id=1R5n-JAU_dzKEQ6w0W9ncDr58dqaAKFoc
Click to expand...
Click to collapse
How to flash it?
Edit: Also OnlineUpdaterTool in your 1st post asks for a password. What's the password?
nooby_pls said:
I'm eagerly watching your progress. I'm in the same boat sitting on a TA-1054 wanting to get on Oreo without chinese firmware :x
Keep up the good work. It is really appreciated!
Edit: By the way, are the custom and original chinese firmware files available anywhere?
I saw someone mention a firmware in the google drive for TA-1054 but I'm uncertain whether that is the official one or the custom one.
Click to expand...
Click to collapse
I put the original chinese firmware on the first post.
There is an option to install google play store, but that would make your rom unable to receive updates.
I think this is a bad move to flashing this firmware. When i flashed it, I just wanted to use Android 9. I didn't really know the complication.
Recently after resetting the phone, Google pay stops working. Couldn't set up anymore as it said the firmware is altered or rooted.
And I tried different firmwares to flash it via dload folder method and none worked. Ended up with installation failed msg.
Mine is MHA-L29 C636.
So Can someone help me how I can go back to stock firmware which is Android 9 for c636?
Thanks a lot!!