Database Info

PLEASE HELP problem with android build h60-l12

Hi, I have the following problem.
A friend of mine gave me a Honor H60-L12 with a problem with calls. No audio or microphone was working. It was a stock phone, with emui 2.3 and Android 4.4.2
I decided to upgrade it, and downloaded an h60-l12_emui3.0_4.4_5.8.5. That solved the problem, but now, I have a chinese phone, without google play market, or google account, AND, it only works on 2G. No matter what I set on the APN. Same sim card works perfect on another phone.
I tried to restore the phone with differents update.app, with the 3 button method and the local update method, nothing works. Is there anything I can do to get a normal android build on emui3.0 or i bricked the phone?
Thanks a lot

Go to fastboot and flash manually. Check the method to flashing rom through fastboot mode.
For this, you need to download the stock rom(miui 2.3 specificly for your version only, else it won't work) and then you have to extract it using "Huawei Extractor" to get the required files. Then those files can be flashed using following fastboot command.
- fastboot flash recovery RECOVERY.img
- fastboot flash system SYSTEM.img
- fastboot flash boot BOOT.img
- fastboot flash cache CACHE.img
- fastboot flash cust CUST.img
- fastboot flash userdata USERDATA.img
I have tried this and I succeed.
Refer the below link(Its using multi tool):
http://forum.xda-developers.com/honor-6/development/guide-to-stock-rom-method-t3099261

Ashishakp, thanks for reply!!! My phone is now on stock ROM again.
I still have the problem with the chinese firmware version. Is there a way I can update it to the ROM that came with the phone? It was a USA android build, with google market and google account.
Best solution would be EMUI 3.0 International via OTA.
Is that possible?

I have a H60-L12, it was on B116 (but it was marked as B1116 in settings....) and it never got any OTA, even honor suite still say it's up to date. And when I go in "updates" it was like a simple OTA checking screen, not with the blue EMUI logo.
I was previously rooted so the bootloader is unlocked.
So I flashed the latest EMUI 2.3 (B121), only flashing recovery and system in fastboot. And it worked well. Now I have the blue EMUI update screen with the local update button. I put the update.app for EMUI 3.1 (B532) on the dload folder on SD card, used the local update button, it reboot but it say the update failed and come back to the B121.
Then I flashed the recovery and system from B532, but once it reboot it stay on the honor logo (with the powered by android at the bottom). But nothing else, I waited 5 minutes. Hopefully it was not bricked, I go in fastboot mode again and flashed back B121, reboot and all normal again.
I still don't get where is the problem. The 3 button method don't work too, but i tested under B116, it just take the honor screen without any menu to flash update.app.

Flashing new TWRP 3.1.1 lead me to no recovery

Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.

My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.

Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.

Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...

I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....

Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"

Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?

Let's see

Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader

Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see

Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x

you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?

shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out

Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4

So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.

Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.

Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment

Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.

The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)

I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.

Help! L29C432 Mate 8 bricked

Hi,
I believe I bricked my Mate 8 when I wanted to go back from rooted B320 to stock firmware via offered OTA. After OTA ran through device rebooted and got stucked in black screen. After this I tried flashing everything to get the device back working: dload B320, dload B330, dload B180, rollback method etc. Some of the trimes the dload ran through to 100% but after reboot the Huawei logo appeared and after 2 seconds I get a black screen. When I reinstall TWRP for EMUI 4.1 I it can't mount data and storage. I treid to restore an older backup with no sucess (backup was installed but phone not booting)
What I still can do is:
-enter fastboot mode
-unlock bootloader
-flash files via fastboot
-install and boot into TWRP for 4.1
Is there a step by step guide to get this device back working to stock firmware?
Thank you very much in advance for your help!

kika1992 said:
Hi,
I believe I bricked my Mate 8 when I wanted to go back from rooted B320 to stock firmware via offered OTA. After OTA ran through device rebooted and got stucked in black screen. After this I tried flashing everything to get the device back working: dload B320, dload B330, dload B180, rollback method etc. Some of the trimes the dload ran through to 100% but after reboot the Huawei logo appeared and after 2 seconds I get a black screen. When I reinstall TWRP for EMUI 4.1 I it can't mount data and storage. I treid to restore an older backup with no sucess (backup was installed but phone not booting)
What I still can do is:
-enter fastboot mode
-unlock bootloader
-flash files via fastboot
-install and boot into TWRP for 4.1
Is there a step by step guide to get this device back working to stock firmware?
Thank you very much in advance for your help!
Click to expand...
Click to collapse
Try installing a rollback package that corresponds to your firmware. I tried 2 and failed at 5%. When I put the update.app from b330 on SD card and tried dload method, it worked. Only difference was my screen wasn't going black. I think the problem is the same as I had, Your phone is trying to find the boot.img but can't because what you have is incompatible.
Have a look at somboons post in mate 8 development. SRK tool is pretty good for mate 8 and other Huawei devices. Read the posts. I think rollback packages are your best bet though.
Sent from my AL10 using Tapatalk

Hi, I managed it now with DC Phoenix. After testing hundreds of combinations phone booted wit method 2 and AL10 Boardsoftware and L29C900B187 Firmware. Upgrade install went wrong with the following output:
18.01.2018 15:39:33 Starting to write device in UPGRADE mode...
File to update: NXT-L29B_C900B187_Firmware_Nonspecific_HQ_Nonspecific_Android6.0_EMUI4.0.APP
Validating file...
Looking for attached port...
Preparing to write...
Writing partition: SHA256RSA...OK
Writing partition: CRC...OK
Writing partition: CURVER...OK
Writing partition: VERLIST...
Error downloading file NXT-L29B_C900B187_Firmware_Nonspecific_HQ_Nonspecific_Android6.0_EMUI4.0_3.dtwork, partition: VERLIST
Error writing software
18.01.2018 15:39:54 Starting to write device in UPGRADE mode...
File to update: NXT-L29B_C900B187_update_data_hw_eu.APP
Validating file...
Looking for attached port...
Preparing to write...
Device does not support this update file
Error writing software
18.01.2018 15:40:14 Writing device finished with ERROR [/SIZE][/FONT][/FONT][/SIZE][/SIZE]
But after reboot phone started and shows now NXT-L29C432B187 Firmware. Will I receive OTA updates now or do I have to flash somethiing manually to get to Android 7.0?

OTA with C432 should work, try HI suite via PC...
C900 - dont receive OTA

everything fine now - I managed it with DC Phoenix AL10 Boardsoftware & C432B170 Firmware. Device bootet and I was able to receive OTA updates to B192 and B560.
Now I have to correct the Serial number wit HCU Tool.
Thank you very much for the support.

I think I hard-bricked my phone

I was trying to root my phone but messed up really bad. Before, whenever I bricked my phone, I just used the dload (UPDATE.APP) method to fix it. But now, when I put a UPDATE.APP file in my SD card and press Vol Up+Down+Power. It doesn't go into dload. It just gets stuck into Your phone is booting up.
Now I only have access to fastboot mode and TWRP. Nothing else. TWRP says no OS Installed

What was your build number and what's your model number?

If you can boot into bootloader mode:
1. Download a firmware compatible for your honor from firmware finder for huawei
2. Download and install huawei extractor
3. Extract system.img, boot.img, recovery.img from the firmware
4. Plug your phone to the computer and boot into bootloader
5. Open command prompt and type:
Fastboot flash system system.img
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
6. Shut down your phone and boot into recovery
7. Perform a factory reset
8. Should be done!

hackslash said:
What was your build number and what's your model number?
Click to expand...
Click to collapse
When I bought the phone, it came with FRD-L19C636B360 firmware but it says FRD-AL10 on the back of my phone. So, I don't know what's wrong there. Now that I managed to flash erecovery and go back to stock ROM (FRD-L19C900B131), I'm stuck with EMUI 4.1 and no updates.

SirDarknight said:
When I bought the phone, it came with FRD-L19C636B360 firmware but it says FRD-AL10 on the back of my phone. So, I don't know what's wrong there. Now that I managed to flash erecovery and go back to stock ROM (FRD-L19C900B131), I'm stuck with EMUI 4.1 and no updates.
Click to expand...
Click to collapse
Hello,
So it's a rebranded phone, many of imported Honor phones come rebranded by reseller...
I advise you to debrand your phone, a rebranded chinese phone from chinese to europe version can't get working firmware above B380.
To do that, you need to unlock your bootloader and root your device. (Guide: here)
Then you can use this tool to change "vendor/country": Huawei_Multi-Tool_by_Team_MT_v7.1.exe (Avoid v8 update if you can, but if you can't you can launch "v7.1" from v8 interface)

Bootloop and eRecovery fails, dload fails - no way to recover

Hi people,
I need some help here and I hope anybody got an idea to get my FRD-L09 (C432 - on B521 base with OpenKirin's RROS Oreo) to work again somehow.
Situation is: After a failed attempt to upgrade the firmware base to B562 my device is now bootlooping, and goes into eRecovery, after one or two tries to boot, which is then offering to "Download and recovery". That fails at getting package info ("Getting package info failed").
Next I tried to install full OTA-PV package (extracted UPDATE.APP) via dload folder on my SD - that fails at 5 % ("Software install failed!"). For this I took the service ROM from this thread (see post #24 for Oreo version) and version B521 for FRD-L09C432 from firmware finder.
I also tried to get into TWRP 3.2.0 from Huawei Multi-Tool by TeamMT but this suddenly reboots after a few seconds everytime - so this is also useless (I tried several TWRP versions I found - maybe 'bootcomplete=false'?). I hoped to flash the extracted .img files with it.
Flashing the extracted .img files (specially the vendor image, because I think I destroyed it somehow) via fastboot also fails with error "command not allowed". Replacing the eRecovery with TWRP is also not possible (not allowed).
Flashing to system, recovery_ramdisk, kernel etc. via fastboot is possible without any problems - which shows that bootloader and frp are both unlocked.
Info btw: in this few seconds in TWRP I could see that vendor partition cannot be mounted - which shows that it's likely an error on this partition.
Is there any way to flash any "other" (vendor) partition via fastboot? Or do you guys have any ideas to this what I can try - except for bringing this thing to service center for repair :silly:? And please ask, if something is not clear or I forgot to give any info.
Any help is very appreciated.

cypher187 said:
Any help is very appreciated.
Click to expand...
Click to collapse
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.

cypher187 said:
Okay, I brought it back to life again.
TWRP by Pretoriano80 and zxz0O0 for BKL (Honor view 10) (link) worked and let me flash firmware again. I used HuRU to flash B562 - and now it's booting again.
Soo... what can I do next to mess up my device :silly:
And note for me: HiSuite, eRecovery and 'update via dload' are all useless in case of a problem.
Click to expand...
Click to collapse
In my case eRecovery save my a*s 2 times

ScardracS said:
In my case eRecovery save my a*s 2 times
Click to expand...
Click to collapse
Usually dload did the job well for me. I don't know why it didn't in that case.
But I'm still looking for an easy way to upgrade the firmware base for future use (in case we get some) :laugh:

Next time just use HiSuite windows version with Firmware Finder's DNS trick to flash any stock ROM version what you need, only works with version 5.0.2.300. I've got the same issue and recoered by this method ease.
You can download it here.