Hello,
I have big problem. I tried to upgrade to lollipop version, used it for one hour and then decided to get back to kitkat. For the procedure I used some tool from killerdogKD which name is MT7-L09 Unbrick (it is a fastboot). The procedure went, phone rebooted and got stuck in boot loop (only logo is showed for few seconds). Now I can only get in fastboot and rescue mode. I've tried to flash stock rom, but without success. Any suggestions? PS. Yes, I now I am jackass and sorry for my bad English:angel:
Stock recovery installed (extracted from official KK ROM)??? 3 button procedure already tried?
Will not work. Are there no going back. He can recover only 5.1.
For the people hanging in Bootllop because they have the 4.4.X Recovery flashed.
Load zip, go to the boot loader and the two flash imgs.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
If both of the 5.1.
https://mega.co.nz/#!DNw13JhK!7ATC9p...G50saLGZG3vKzM
KK is not possible 5.1, just with dload the flash 5.1 again. Is indeed just about the one that has 5.1 Recovery again.
Here read next time.
http://forum.xda-developers.com/mate-7/general/mate-7-update-to-lollipop-screenshots-t3125227/page28
I have the same problem and probably caused by same thing. But I can' even enter bootloader. When phone was bootlooping, I turned it off. Then I tried to get into recovery (by holding power + volume down), but phone always shut down after Huawei logo appears (shut down with short vibration).
It does not matter when I release the buttons, I also tried the recovery (vol up + power) or the force update mode (vol up + vol down + power).
Is there any solution to this? I really hope so...
Look at my post and Liks.
Thank you Fooox1 for trying to help, but the problem is, that I can't even enter the bootloader (and your steps require that). I think that international Mate7 have different key combination for entering bootloader? Check also this: http://forum.xda-developers.com/mate-7/help/fastboot-mode-t3086531
It is true that even before I was not able to get into bootloader with vol down + power, so maybe there is just different key combination or it is not possible at all...
I think I will try to write to Huawei support.
In the bootloader you come when the power is off and you Vol - holding down, then to the PC. To turn it off properly you must Vol - and Power button until it vibrates.
Key combination is the same for all.
I know, that is what I am doing it. And I already did it with many other phones successfully, so its not like this is my first time.
I am holding down power + vol down
Phone vibrates, I am still holding both buttons
Huawei logo appears, I am releasing power button, but still holding vol down button
Phone vibrates and turn off
I also tried to release power button when phone vibrates, or not release both buttons at all or I don't know what else. Tried 100x times.
I will try to contact Huawei, maybe it is known issue. It should really be same key combinations for all devices.
Thank you.
The Mate mus but this depend on the USB, otherwise it does not come into the bootloader.
Whoa! I did it. Yes, it was connected in USB, but in quickcharge USB. I tried different one and I am in!
For some reason, it did not like the quickcharge USB port, strange.
@Fooox1: but thank you, with your last comment I got the idea to try different USB
Well, I am little bit furhter, but still not working unfortunately. I got into bootloader, I flashed the boot and recovery. Then I was trying to three buttons force update and it is still failing.
I have Update.zip in dload folder on sd card, but update is failing immediatelly...
So now, I started the three buttons update while connected to computer via USB and it is actually doing something. But it is too soon to say if it helped (43%).
can't boot too
I need your help Guy's
My Mate 7 did not start after i rooted the lollipop rom with kingroot. I tried to put back the 5.1 boot.img and the recovery.img. After that i tried to flash the ota 5.1 rom agian with the 3 bottons mode. The phone startet the Update but it get stocked by 90%. I waited ca. 10 min after i just rebooted the phone. Now the Phone starts with the Huawei Ascend sign two times and after that i am in recovery mode. I don't know what i can do now! Can anyone help me please?
Yes, I have the same problem
driver84 said:
I need your help Guy's
My Mate 7 did not start after i rooted the lollipop rom with kingroot. I tried to put back the 5.1 boot.img and the recovery.img. After that i tried to flash the ota 5.1 rom agian with the 3 bottons mode. The phone startet the Update but it get stocked by 90%. I waited ca. 10 min after i just rebooted the phone. Now the Phone starts with the Huawei Ascend sign two times and after that i am in recovery mode. I don't know what i can do now! Can anyone help me please?
Click to expand...
Click to collapse
Same here! Help!
must we send in warranty?
So it seems to me, that problem is Huawei. Once, they are using Update.APP and later Update.ZIP, not sure why.
- recovery from 5.1 is working, but it is expectin Update.APP, but 5.1 update is in Update.ZIP, so it fails immediately (with error Update.APP not found). Yes, when you connect to phone to computer, it seems that it is doing something and it will get to 90%. But it is actually doing nothing, you can even pull out the sd card and it is the same. I think it is waiting for some action from computer, but not sure which (I also tried to install HiSuite and do something with it, but no success).
- recovery from update B137 will accept Update.ZIP, but when you try to flash it you won't be able to get in it, it is not working (I also tried B127).
So now, we either need recovery, which will work on 5.1 and will accept Update.ZIP or we need update packed as Update.APP (and yes, I tried to rename it etc.). So actually, our phones are pretty ok, we can get in recovery etc., but Huawei is messing with this different formats for some reason
@Fooox1: Do you have any ideas? Maybe you have another bootloader / recovery image? How did you got the 5.1? Thank you...
Edit: maybe the problem is, that we are trying to run the update OTA (Update.ZIP) instead of full rom (Update.APP)? Is this how it is divided, Update.ZIP is just incremental update, while Update.APP is full rom? If that is the case, we will need the full rom, maybe Huawei can release it?
I have not the problem, but users in our forum. I have the boat and recovery.img from the update unzip, a user has then flashed via fastboot and sin device was running again. For him only recovery was gone after he has the Kang Recovery flashed. The Update.zip he did not need to flash.
Other users have only the boot and recovery.img flashed and then the not unpacked update.zip in a folder (dload) on the SD and these then flashed three fingers method. What also has to work.
Here is still the boat and recovery.img of 5.1.
https://mega.co.nz/#!DNw13JhK!7ATC9pAUID0VyX5N3pQwQLbb_VyuOG50saLGZG3vKzM
And update.zip
https://mega.co.nz/#!vdYlxQIA!P34e3RI-hQT1ZY2WnfOosGmkq2wlr6NViq6ehQuWN5k
I think it may help if somebody will create *.img files from Lollipop, then we might be able to flash it via fastboot (the same as it is in this MT7-L09 Unbrick). I think we will need:
boot.img - ok
cache.img
cust.img
recovery.img - ok
system.img
userdata.img
Can make you yourself. Unzip, when present therein Update.app the extension .app in change .zip and unpack. Now you have another Update.app, this you can unpack the Huaweiextraktor, you've got your files. However, it does not contain all IMGs.
You could try but the resulting Update.app to pack in the dload folder and flash. If so, then the original and encrypted.
Hallo again,
i just called the Huawei Service Center in Germany. They openend up a Ticket for me. They told me to make a factory reset and after that the Phone should boot normaly. I did that, but still the same is happening. The shows the Huawei Ascend Logo 2 times and after that i am in recovery mode again.
The only thing i can do next, is to send the phone to the Huawei Service Center and hopefully i will get it back in 7 Days.
Related
Hello, after updating my MT7 - TL10 unbootable .
At startup the screen remains black , the LED flashes orange one and a green three times ( three cycles). With a hard reset is the same except that the screen is white.
Someone already you had this problem ? I begin , thank you kindly help me.
Merlin-69 said:
Hello, after updating my MT7 - TL10 unbootable .
At startup the screen remains black , the LED flashes orange one and a green three times ( three cycles). With a hard reset is the same except that the screen is white.
Someone already you had this problem ? I begin , thank you kindly help me.
Click to expand...
Click to collapse
Which kind of update method did you used? 3bts? Or FORCED UPDATE?
Have you tried to go into STOCK recovery (volume up+power button)? Is it working?
Have you downloaded and put in the DLOAD folder the CORRECT firmware for Ur phone?
Please double check and, in case, better to re-download it (be sure it is the correct one for TL-10).
Then try 3btns again.
If procedure works, it' s always a good thing to gointo stock recovery AFTER UPDATE proceure, and apply a full WIPE CACHE AND WIPE DATA/FACTORY RESET.
Hello Tuddu .
I made a forced update .
The method of the three buttons does not work = more white screen LED flashing amber and green three times ( three cycles).
When I connect it to the charger , it is happening. I fear the worst .
Merlin-69 said:
Hello Tuddu .
I made a forced update .
The method of the three buttons does not work = more white screen LED flashing amber and green three times ( three cycles).
When I connect it to the charger , it is happening. I fear the worst .
Click to expand...
Click to collapse
Have you the stock recovery installed?
Does the recovery works (can you enter into recovery properly?). If not, you should try to re flash the stock recovery, of course if the HAM7 is recognised by Windows.
Differently, i fear, it could be an hardware problem...
Sent from my S5+ using XDA Free mobile app
The situation evolved !
I come now to start the phone mode " Fastboot & Rescuemode ." But then I do not know what to do.
Here you could if the bootloader is open, the respective imgs (boot, recovery cust, and system) or flash when closed, flashing with a Huawei HiSuite FW.
can I use fastboot to install : boot.img , recovery.img , system.img .
I extracted the .img from the firmware.
I would still flash the cust.img. Then fastboot reboot and hope it starts. The question is, what your battery still says.
If it does not start, then it is probably a case for the service.
I Flasher cust.img , boot.img , recovery.img , system.img . But it does not start. What can I do more for the mode " Fastboot and rescuemode " ?
You could still try the Huawei HiSuite. Furthermore you can flash a Stock Rom. Much more remains not.
Then I flash a ROMSTOCK using cmd fastboot
Only works with the HiSuite.
tuddu said:
Which kind of update method did you used? 3bts? Or FORCED UPDATE?
Have you tried to go into STOCK recovery (volume up+power button)? Is it working?
Have you downloaded and put in the DLOAD folder the CORRECT firmware for Ur phone?
Please double check and, in case, better to re-download it (be sure it is the correct one for TL-10).
Then try 3btns again.
If procedure works, it' s always a good thing to gointo stock recovery AFTER UPDATE proceure, and apply a full WIPE CACHE AND WIPE DATA/FACTORY RESET.
Click to expand...
Click to collapse
I also have the same problem. I wonder if you could help me out also. I've been having these problem for 3 weeks now. Here's the story. I was going to sell the phone to my friend, so I was unrooting and installing stock firmware on it. I downloaded the stock firmware from Huawei website. Flash the stock recovery extracted from the firmware update.app. Put the firmware in dload on a newly bought 8GB SanDisk, and forced update. The update failed saying that the update.app could not be found even tho it is under 'root of the sdcard'/dload/upload.app. So I flashed CWM and flash the repacked update.app using the Huawei Update Extractor. It was fine until I redo the forced update process. EMUI showed up half way and failed with the same reason, it could not find the update.app. I restart the phone and it is bricked.
Condition right now. BL is unlocked.
- Turn on normally: It flashes [Red Green Green Green] x 3 before turning off.
- Turn on with Vol+ + Power to get to the recovery: Same result as turning on normally.
- Turn on using 3BTNs: It shows "HUAWEI Ascend" logo and stays there for 48 hours. Then I figured it wasn't going to do anything.
- Turn on into bootloader with vol- + power works fine. I can get to the bootloader.
What I've done so far. Most are suggestion on XDA forum, somes are from other sources.
- fastboot flash boot, recovery, cust, userdata, and system of 3 different versions of firmware (MT7-TL10 for Global, Chinese, and MT7-TL09 Global). All firmwares are from Huawei website. None of them work.
- fastboot flash CWM recovery. Didn't work. I could not get to the recovery mode.
- fastboot flash many boot.img from custom roms hoping it would at least take me to the recovery. Didn't work.
- bought another micro sd card, which didn't matter since both cards work fine on other devices.
- Try using older version of Hi-Suite that has the restore function. This is the weird part. Hi-Suite would starts itself as soon as it detects the phone in bootloader mode, but it says "Phone is not connected." Unfortunately, this fails also.
I wish there were a way to force boot the phone into the recovery mode other than the button combos. What do you think I could do? I'll try anything. Thanks.
i have same problem too . anyone get working way ??????
Dear All,
I got a real problem,
i tried to update my 5.1.1 (B311) to 6.0 (B513),
but unfortunally i messed up, i tried to do a local update.
but used a update.zip as update.app, and a update failed,
or partially finished.
After that, it was a mess.
i could enter (stock) recovery, tried to do factory reset,
but my files were done, and it only got worse;
After i tried to flash a different recovery,
to update by a update.zip on my sd card or so,
i could not even enter recovery.
When i try to flash recovery or even cust.img, boot.img, etc. from a B127,
i got nothing, all i can enter is my fastboot, with pc connected (it won't even go to fastboot without pc)
and i will see faastboot&rescue mode, can somebody please advise, and help me unbrick my phone.
I guess i failed, big time..
Thanks in advance
http://forum.xda-developers.com/mate-7/development/finally-rollback-513-331-511-326-t3325803
I tried to flash a update.app but my mate7 will hang on logo and then shutdown...
is your Bootloader unlocked?
Yes thank god
you are now in MM or LP which device you have TL09 or TL10?
I dont know actually since my phone does not boot anything anymore, only the boot logo then it shuts down/crashes..
The update was from lollipop to marshmellow, so i don't know what is inside the phone everything looks to be false, i also tried to flash the boot.img,system.img etc,recovery.img , but without success..
My phone is tl09
edit: If you are just looking for the solution, plz click here: http://forum.xda-developers.com/showpost.php?p=68626049&postcount=11
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
mike175de said:
Hey there,
first of all I want to say Thank You for this great community and the work at XDA. Awesome. :good:
I bricked my Honor 6 H60-L02 and I am lost to bring it back to life. :crying:
Where it started:
I was using the official ROM from this thread [OFFICIAL] Honor 6 (L02, L12, L04) Stock ROMs. To be more specific it was the latest Android 6.0 EMUI 4.0 B823 that I installed with all the different OTA-Files starting with the original 5.1 ROM B535. The Honor was rooted and also the bootloader is still unlocked (I already checked the status via Fastboot.).
After I while the Honor 6 started to crash sometimes and the headphone-buttons didn't worked anymore. Then a few days ago the phone crashed and I was not able to boot it again.
And so I tried this:
Using the Rollback-Zip to go back to 5.1. But the 3btn-method didn't worked. The phone didn't want to boot into the recovery. Also the Vol+ and Power-Button didn't work to start the Recovery of the phone. Result: Bootloop.
So I installed ADB and Fastboot (with all necessary drivers) and tried to flash the phone with the 5.1 B535 (as mentioned in Honor 6 H60-L02 Hard Bricked - Only access to fastboot (Vol+ and Usb PC)) because there isn't a 6.0 B823 ROM available. I was able to flash boot, recovery, cust, system, userdata and another one I forgot right now. But the result was the same: Bootloop and no 3-btn or recovery via Vol+ and Power-Button. I also tried to flash it with the HonorTool. Same result.
Then I tried to flash different TWRP versions as recovery. Result: The same as above.
So I tried another official ROM 5.1 B526 because someone had the same problem and was able to recover his phone with this ROM (another thread in the forum). But that didn't worked ether.
Then I tried to flash all the img-files of the 5.1. B535 as crc, ptable and so on because I thought that there could be the problem. But when I tried e.g. to flash crc I get the error FAILED: command not allowed. So I tried to unlock the phones partition via Fastboot and fastboot flashine unlock_critical. But using the command unlock_critical gives me also the Failed error. So I was lost again.
Status right now:
I'm still able to boot into the bootloader via Vol- and Power. But right now the phone was running out of battery. Means I see the red battery symbol when I try to start the phone via the power button (without connecting to the PC or charger) but it isn't booting even into the bootloop. The red battery symbol pops up for a second and the screen went black again.
When I use the charger then the symbol changes to a green battery and stays there, but not the moving one that indicates that the phone is charging. When I use the Power button with usb-charger connected to start the phone I'm trapped in the bootloop again.
You see I already tried a lot of different things I could find on the forum. But nothing worked for me.
I know that it was a fault to try to install 5.1 B535 without the rollback, but I wasn't able to rollback as mentioned under point 1.
Maybe anyone could give me a hint and help me to bring my phone back to life.
Thx a lot! I appreciate that al lot!
If you need anymore informations, plz let me know.
Greets, mike175de
P.S: Sorry for my school english. It is a little bit rusty ;o)
Click to expand...
Click to collapse
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
With which version?
muradulislam said:
Just flash boot, Cust, recovery and system images and let it boot normally. Don't do any button combo. I have had instances where it works. Give it a try.
Click to expand...
Click to collapse
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
mike175de said:
Thx for your reply.
With which version should I flash? B535 or B526? Should I only flash the three images boot, cust and system? Nothing else?
Thx for a reply!
Click to expand...
Click to collapse
You can use any firmware but the latest one should be better, and flash four images, boot, Cust, system and boot and let it boot normally.
Then put the dload folder with update.app in sd card and do an update from settings.
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
mike175de said:
Thx. I will give it a try when I'm back from work.
I let you know if it is working.
Click to expand...
Click to collapse
I meant to say flash boot, Cust, recovery and system images.
Wrote boot twice
Nothing changed
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
mike175de said:
Hey muradulislam,
Thx again.
I flashed the images (boot.img twice) but without success. Still the same error (with normal booting aka without any special button combination or with button combination). The honor boots and stays in the bootmode aka bootloop with the led blinkin red. And I still can't boot into recovery via Vol+ and Power..
Any other suggestions?
mike
Click to expand...
Click to collapse
Of all the things you have already tried, the only thing remains to take it to a Huawei service center.
May be someone else can help you here but I have read most of honor 6 and 7 posts and I don't think there is anything there for this problem atm.
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
mike175de said:
Hmm, thx. That is bad...
I bought this phone in China when I was there for work. And I suppose that the german service of Huwaei will not help me at all with this phone.
Does anybody else have any clue how to bring the phone back to life?
Thx a lot.
Click to expand...
Click to collapse
I myself have an H60-L01, bought it from china, bricked and tried everything to revive it but could not, still have to try Huawei customer service in Pakistan, am not sure whether they will be able to help me or not, but will give it a try. I wish you luck buddy. Hope you find a solution.
It's alive ;o)
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
The same can not restore brick
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
igorxxl said:
Hello! In what condition I have a phone? My phone is loaded in error func_boot_kernel.
Click to expand...
Click to collapse
Have you unlocked and rooted it?
When does it says that message?
error! no func. func_boot_kernel or _recovery
zinko_pt said:
Have you unlocked and rooted it?
When does it says that message?
Click to expand...
Click to collapse
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
igorxxl said:
The bootloader is unlocked. Root is. Phone is loaded into the error! no func. func_boot_kernel. If you try to enter into the recovery, the error! no func. func_boot_recovery.
The error is the same as here club.huawei.com/thread-7962289-1-1.html
I tried to put EMUI4.0, then the phone stopped working. Through ADB stitched, weighting system, boot, recovery, cust.img. It shows all ok. But then the error again. He tried to put different versions of TWRP. On the 3 button also does not work.
Thank you for your attention to my problem.
Click to expand...
Click to collapse
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
igorxxl said:
Nothing helps. I sew different versions via Fastboot. Everywhere all shows OK. However, when you restart the exact same mistake again ..
Click to expand...
Click to collapse
You can also try installing custom recovery and restore a twrp backup of ROM.
zinko_pt said:
You can't use 3 button with custom recovery and root. It wont work.
You need stock recovery in the same version as the rest of files used to flash other partitions.
Flash all stock partitions, then just boot the phone. Check if it works. Forget about TWRP and root for now. One thing at a time.
Click to expand...
Click to collapse
goldfinv said:
You can also try installing custom recovery and restore a twrp backup of ROM.
Click to expand...
Click to collapse
i'm in the same situation with my honor 6 plus pe-ul00 i'll try this metod!
mike175de said:
The phone is working again.
Here are the steps I did for everybody else confrontated with same problem:
1. Download your last working ROM or OTA-File: In my case the OTA-File OTA-EMUI 4.0_H60-L02-L12_B811_B823.zip from this Mega-Link:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!KwhlRKYR
2. Unzip the file and extract recovery.img and boot.img with the Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454).
3. Boot the phone into fastboot mode (connect the USB cable, press the power button to turn off and immediately press the volume down button).
4. Use fastboot to flash the two images of 2. If you need fatsboot you can find it here http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip (Extract adb.zip and copy the extracted files from 2. in the folder adb. In the adb folder run cmd.exe as administrator.)
5. Use this commands for flashing:
fastboot devices => If the device is recognized correctly it is displaying a series of numbers
fastboot flash recovery RECOVERY.img
fastboot flash boot BOOT.img
fastboot reboot
6. Charge the phone with the Huawei charger, not via USB/PC! (50% is enough.)
7. Download in the meantime the Developer ROM H60_EMUI3.1_Android5.1_6.1.1.zip from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
8. Extract the zip file from 7. and copy UPDATE.app onto your SD-Card into /dload
9. Insert the SD without connecting.
9.1. Disconnect the USB cable from your PC or charger.
9.2. Press the Power button to turn off (maybe that is not necessary.)
9.3. When you feel the vibration press 3btn (Vol+ and Vol- and Power).
9.4. When the Honor logo appears connect your SD-Card (continue to press 3btn for 8 -10 more seconds) => Wait for the recovery process, it should start automatically.
10. After installation Android boots. Skip the first step installation (you should now have the 6.1.1. Developer-Edition installed). Rollback to Android 5.1.1 with the Rollback-File Rollback 591 EMUI3.0.zip from here:
http://www.mediafire.com/download/9qrd8zm9280gy5e/Rollback+591+EMUI3.0.zip
Do do so put the unzipped UPDATE.app from the Rollback-File onto your SD-Card and do a local update via the Update Manager.
11. Boot into Android again (it will still be the 6.1.1 Developer Edition). In my case I want to install the latest Android 5.1.1 B535 from here:
https://mega.nz/#F!ztYliaxL!4gfyXozSW51eNahGZBDgBQ!6w5inQ6Z
I did it via local update again.
12.. After installation and booting => Voila here is your working Android 5.1.1 B535 again. Have fun
13. Brick it again with updating to Android 6.0 [emoji14]
I hope I could help somebody with my experience to bring his/her phone back to life.
CU, mike
Click to expand...
Click to collapse
I got a problem at 9.3 or 9.4. The recovery wont start i see only honor logo i used PE_EMUI3.1_Android5.1_6.1.1.zip (as developer edition i.e sdcard/dload/UPDATE.APP) and PE-UL00-V100R001CHNC00B200.zip to extract and flash BOOT.img and RECOVERY.img
any ideas why i can't enter in recovery? =(
EDIT: "fixed with DC-Phoenix tool"
Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..
fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available
jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....
I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..
I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?
Edit & Update: I tried all method's, unable to boot into bootloader, or access the recovery, eRecovery & the dload (to force update) I took it to the service centre and got the firmware flashed from them. If this happens to you, take it to a service centre.
Don't worry, you still have a chance and it is using the dload method. For doing that, the only thing that you need is your firmware package, then there's a keys combination (vol up+vol down+power) that if pressed on a phone that is off, gives the input to flash what is in the dload folder. Begin to recover your firmware package, then I'll be here for any help.
that would be difficult, I cant get into the erecovery or the recovery mode. i am worried the device is bricked. also can the fastboot mode be corrupted?
Surely something went really bad, looks like some partition is messed up if neither fastboot mode is accessible... But for doing the dload method you won't need fastboot not recoveries, you just have to press the 3 keys on phone while is off to let the flashing process begin. But for doing this you'd need to obtain the UPDATE.APP extracted from your actual firmware package, and place it on your phone's memory or external SD card in a folder called "dload". Connecting the phone to the PC gives some results, of any kind?
yes something did go reallly bad, i stil dont know what that was. But for the 3 keys method to work, shouldnt the force update thing be accessible? atleast it will show some option, to force update, ayt I will try that method. Connecting the phone to the PC while in blackscreen yields no results. ADB or FASTBOOT cant detect it either.
my current firmware is BLN-L21C185B371
using firmware finder on PC, I have found 3 files to download which are;
1: update.zip
2. update_data_public.zip
3. update_BLN-L21_hw_meafnaf.zip
Which of these should I download?
theres been an update to the situation:
the phone died ( Battery depleted ) and so after I plugged it in, it rebooted to the ROM, and now it is working, but I am still unsure whether the next time i try rebooting whether it will work or not
Hello, I had the same problem, so it cannot be just something went wrong case. I have a BLN-L24 model, EMUI updated to 5.0 amd Android 7.0 online before unlocking the bootrom. I was able to exit the boot screen pressing the 3 buttons as suggested and I got the error of missing files, but after the reboot it goes back to the ROM. I tried again to copy berlin.img file for TWRP but same problem. So either I give up on TWRP or keep trying doing more research. To be on the safe side (in case it works) could anybody provide me with the original img file for this phone?
I am unable to exit the warning sign. if I power it off, it auto boots into the warningit boots into the ROM when the power is depleted, but if I try to restart or anything else, it shows the warning screen only until power is drained.
I am confused, I thought you were able to boot to the ROM after your battery died. The warning sign will be always there, the problem is only when you force the recovery mode, the TWRP image doesn't load.
it boots into the ROM only after the battery has drained off all the power. then after that when I charge and try to boot into recovery or fastboot it shows this: https://i.imgur.com/FpcxllE.jpg