Related
hello I ask you a hand
I have a model TL10 with unlocked bootloader and the recovery
I tried the rom rom published on need (the SP03 with the root)
the phone now goes into boot loop and not part
I can go into recovery and bootloader but I can not solve
[email protected] said:
hello I ask you a hand
I have a model TL10 with unlocked bootloader and the recovery
I tried the rom rom published on need (the SP03 with the root)
the phone now goes into boot loop and not part
I can go into recovery and bootloader but I can not solve
Click to expand...
Click to collapse
Can you resolve by performing a recovery?
Additionally the ROMs on NEEDROM at the moment are the Chinese ROMs and there is a raft of additional Chinese only applications installed and no GAPPS. my biggest issue if you use them is the fact that you are unable to tell which SIM you wish to use as the 4G sim as it forces the top SIM only to 4g.
hello
* Yesterday I tried advice
I pulled out the original recovery and tried to install the original recovery and the result which I quoted in the terminal Lock but I had no other result of restart except that now I have the white screen on and off
The very strange thing is that I can not start in any way the restoration of forced dload, this is very strange
I tried putting some original ROM into the sd card in dload but pressing keys vol + vol- on --more vol + and vol - not restoring the rom
are disoriented, more 'than anything else I do not understand why not use an external software to recover if the terminal is in bootloader
other strange thing I find the opportunity to go to cmr even if the phone back and lock
at this point I have to focus on the hard repair but I can ..provo another micro sd?
can be unusable even the function of enforcement with dload?
andytom69 said:
hello
* Yesterday I tried advice
I pulled out the original recovery and tried to install the original recovery and the result which I quoted in the terminal Lock but I had no other result of restart except that now I have the white screen on and off
The very strange thing is that I can not start in any way the restoration of forced dload, this is very strange
I tried putting some original ROM into the sd card in dload but pressing keys vol + vol- on --more vol + and vol - not restoring the rom
are disoriented, more 'than anything else I do not understand why not use an external software to recover if the terminal is in bootloader
other strange thing I find the opportunity to go to cmr even if the phone back and lock
at this point I have to focus on the hard repair but I can ..provo another micro sd?
can be unusable even the function of enforcement with dload?
Click to expand...
Click to collapse
Have you tried loading the updated original firmware to see if this resolves it, resolved my issues: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
:highfive:
thank you
I solved. in practice I loaded the original firmware in dload because I had the recovery cwm
I re write the original recovery (via fastboot) and run the flash version 120sp07 very Chinese
but now I'd like to put an international version but I can not get back with dload forced
maybe we should change the build prop
if I try to write forced dload with your version starts then stops
andytom69 said:
thank you
I solved. in practice I loaded the original firmware in dload because I had the recovery cwm
I re write the original recovery (via fastboot) and run the flash version 120sp07 very Chinese
but now I'd like to put an international version but I can not get back with dload forced
maybe we should change the build prop
if I try to write forced dload with your version starts then stops
Click to expand...
Click to collapse
I have the same problem, is there a way to revert back without having to unlock my bootloader and gaining root access?
Hi guys..hope somebody can help me to get my phone working again..i had lollipop installed and by accident I deleted the internal memory..the only thing what I can is to reboot to recovery twrp..and then on my pc phone shows up..1 cust drive and 1 internal..which is empty..do you have any idea about that? thanks a lot..please help )))
Download the stock rom for your phone model (tl-10) official one, NOT beta version, better directly from Huawei web site.
Extract stock recovery from downloaded file (by using huawei extractor app).
Using ADB commands, flash stock recovery. Then copy stock rom to sdcard and proceede with 3button procedure.
If any of these operations sound new to you, please use "search" button in these forums.
tuddu said:
Download the stock rom for your phone model (tl-10) official one, NOT beta version, better directly from Huawei web site.
Extract stock recovery from downloaded file (by using huawei extractor app).
Using ADB commands, flash stock recovery. Then copy stock rom to sdcard and proceede with 3button procedure.
If any of these operations sound new to you, please use "search" button in these forums.
Click to expand...
Click to collapse
I have downloaded from Huawei web site 120sp04 firmware. I extracted recovery, flashed with adb commands. Copied the stock rom to sd card, and i am not able to force my phone to start update. keeps restarting. is the a special trick for this 3 button procedure? phone should be off, but from bootloader i cannot switch of the phone. Is it possible that the phone doesn't recognize my SD Card? please advise.
Please check, there' s a command trough ADB (I think adb reboot) wich reboot phone.
Then, someone, has been forced to keep the SD card NOT inserted into the phone, waited for reboot and then (after huawei logo I think, but I'm not sure; please check) inserted the SD card.
Then proceede with local update (forced method).
As for the 3button method, simply press and keep pressed volume up+volume down + power on button. All togheter.
Then the phone must boot automatically into recovery and start the procedure itself.
It i clear: stock recovery MUST be already installed !!!
tuddu said:
Please check, there' s a command trough ADB (I think adb reboot) wich reboot phone.
Then, someone, has been forced to keep the SD card NOT inserted into the phone, waited for reboot and then (after huawei logo I think, but I'm not sure; please check) inserted the SD card.
Then proceede with local update (forced method).
As for the 3button method, simply press and keep pressed volume up+volume down + power on button. All togheter.
Then the phone must boot automatically into recovery and start the procedure itself.
It i clear: stock recovery MUST be already installed !!!
Click to expand...
Click to collapse
The only thing what i can do is, to flash recovery and boot from fastboot.zip( http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888 ) i guess for L09 version, where i can get to update mode with 3 buttons...all other possibilities are not possible. even if i extract from original firmware recovery and boot images, nothing work..i was going from B125 back to B123 to B128 and B313 when in TWRP i deleted everything. Phone is charging, i can turn it off..OS is missing..is it possible that somebody would make a back up in twrp and i would flash it on my phone? or what version of firmware i should start with? what about sideload? does it help? please advise.
alworth said:
The only thing what i can do is, to flash recovery and boot from fastboot.zip( http://forum.xda-developers.com/mate-7/help/5-1-to-4-4-2-bootloop-t3132888 ) i guess for L09 version, where i can get to update mode with 3 buttons...all other possibilities are not possible. even if i extract from original firmware recovery and boot images, nothing work..i was going from B125 back to B123 to B128 and B313 when in TWRP i deleted everything. Phone is charging, i can turn it off..OS is missing..is it possible that somebody would make a back up in twrp and i would flash it on my phone? or what version of firmware i should start with? what about sideload? does it help? please advise.
Click to expand...
Click to collapse
Hello!
I have similar problems, but i have the L09.
Check if you can mount system. Or if you can wipe system, because i can't
Good luck!
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?
I would like to clarify some things first.
I know I fuked up big time, I did things I didnt know how to do, flashed shlt from strange links and the like, I completely assume the responsibility, I fuked up big time and its my fault. Im a stubborn mf and decided to take care of my device without much knowledge.
I apologize beforehand if the answer to this is already somewhere, but i am so so tired im writing this thread and going to sleep, hoping to find an answer tomorrow or at least discuss with you people a solution to the situation I created.
In the span of 24 hours I completely messed up my phone. Its a honor6x, bll-l22 model. It had huawei Nougat on it which i installed months ago, working and smooth. I wanted to upgrade to Android Pie or Oreo at least, and messed it up. I would try to recall and tell you what happened first but I swear i downloaded so many files and roms i cant order it in my head.
I flashed twrp with fastboot, and from twrp i flashed one of those roms. Phone died probably because of incompatible OS. I tried fixing it with DC phonenix but to no avail, phone stil bricked.
Its on a bootloop, huawei logo keeps appearing and dissapearing again and again. When i hold vol up + power it goes to a blank rescue mode screen, please update system again, and also says failed to load recovery. vol up vol down and power doesnt take me to upgrade mode anymore (which is why i cant finish the flashing with dc phoenix, since it asks for you to put your huawei in upgrade mode to finish the firmware install) and the only accessible mode is fastboot (vol down + power) which gives me certain hope to save my device from a hard brick.
i tried flashing a stock marshmallow firmware for my phone model (the extracted .img files of recovery, boot, cust, and system) through fastboot but it says that remote command is not allowed. the only thing i can flash is recovery, so i installed the stock one to see if i get any options to wip/restore/update from sd card/anything but it all failed. i got the twrp for honor6x (berlin) and after flashing and booting directly to recovery, it fails and boots into stock recovery/fails to load recovery and shows the rescue mode i talked to you about in the beginning.
i just tried flashing stock recovery, it says flash okay and when i boot into it, it takes me to rescue mode now, doesnt even boot the stock recovery anymore.
i just checked and its in a loop between rescue mode and boot logo, one comes after the other endlessly.
ive been all day searching for a fix, ive spent 18 hours in front of the pc with breaks for taking a shlt, pissing or eating something, which for me is a lot, im not used to it. so im gonna post this here and sleep a lot and come back tomorrow, i cant stand this screen for one more seconds my eyes are burning.
thank you in advance, i appreciate any help :good:
Can you try reflashing TWRP? Or boot into TWRP? Also, what is the phone status in the bootloader screen. Does it say locked or unlocked? Assuming you can flash and boot into TWRP I would say go to wipe -> format data and then advanced wipe -> mark everything except sd card and wipe it. If not then I recommend dirty flash of your ROM you were using before boot loop i.e latest version of Android 7 for your model through hurupdater. You can find more info about it by searching for it. If the flash is successful boot into the ROM. I think your problem is mostly die to corrupt partitions and hurupdater should fix that. Also download the firmware files from Firmware Finder and rename them accordingly. If you are able to boot into the ROM, then reflashing TWRP and then wipe everything again (except SD Card) and then reflashing the same ROM using hurupdater again. This will remove the dirty flash.
Another alternative u could try is HWOTA 7. It will also upgrade you to Android 8 if you provide the correct files. Just search HWOTA 7 for Honor 6x. And follow the steps. Hope this helps your case
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page14
Here is the HWOTA 7 thread. If hurupdater fails try this
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Here is the link to hurupdater. It works on Honor 6x. Couldn't find the particular thread. Download the Hurupdater zip and official firmware from Firmware Finder and follow the instructions.
Mannan Qamar said:
Can you try reflashing TWRP? Or boot into TWRP? Also, what is the phone status in the bootloader screen. Does it say locked or unlocked? Assuming you can flash and boot into TWRP I would say go to wipe -> format data and then advanced wipe -> mark everything except sd card and wipe it. If not then I recommend dirty flash of your ROM you were using before boot loop i.e latest version of Android 7 for your model through hurupdater. You can find more info about it by searching for it. If the flash is successful boot into the ROM. I think your problem is mostly die to corrupt partitions and hurupdater should fix that. Also download the firmware files from Firmware Finder and rename them accordingly. If you are able to boot into the ROM, then reflashing TWRP and then wipe everything again (except SD Card) and then reflashing the same ROM using hurupdater again. This will remove the dirty flash.
Another alternative u could try is HWOTA 7. It will also upgrade you to Android 8 if you provide the correct files. Just search HWOTA 7 for Honor 6x. And follow the steps. Hope this helps your case
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page14
Here is the HWOTA 7 thread. If hurupdater fails try this
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Here is the link to hurupdater. It works on Honor 6x. Couldn't find the particular thread. Download the Hurupdater zip and official firmware from Firmware Finder and follow the instructions.
Click to expand...
Click to collapse
Hey man! Thanks for your long answer, just got up with a fresh head and stronger hopes so I will keep trying it all. I couldnt boot into twrp dik why. I flash it succesfully with fastboot but after that it boots me into recovery/fails and blank rescue mode screen. I by some miracle button combination achieved to boot straight into twrp right after flashing, so I will try that.
Bootloader is unlocked (phone unlocked) and FRP says "unlock". idk if that is a statement or a command to do it actually haha.
As soon as I boot into twrp, ill wipe it all and follow your instructions
Ill try to use twrp first, then hurupdater and then hwota7.
What do you mean by renaming the firmware accordingly? How can I do that? Isnt that iirelevant since inside the firmware files it still says some things that do not match the title i renamed?
oh, forgot something. fastboot commands are limited. i can flash a recovery.img but not a boot.img or use certain commands. remote command not allowed.
inkainsa said:
Hey man! Thanks for your long answer, just got up with a fresh head and stronger hopes so I will keep trying it all. I couldnt boot into twrp dik why. I flash it succesfully with fastboot but after that it boots me into recovery/fails and blank rescue mode screen. I by some miracle button combination achieved to boot straight into twrp right after flashing, so I will try that.
Bootloader is unlocked (phone unlocked) and FRP says "unlock". idk if that is a statement or a command to do it actually haha.
As soon as I boot into twrp, ill wipe it all and follow your instructions
Ill try to use twrp first, then hurupdater and then hwota7.
What do you mean by renaming the firmware accordingly? How can I do that? Isnt that iirelevant since inside the firmware files it still says some things that do not match the title i renamed?
oh, forgot something. fastboot commands are limited. i can flash a recovery.img but not a boot.img or use certain commands. remote command not allowed.
Click to expand...
Click to collapse
Renaming them means that when you download them from Firmware Finder they will be named different. You just rename them normally. The linked threads will provide you detailed info. Just rename them accordingly and you are good to go. Good Luck.
BTW don't be so hard on yourself. We all make mistakes. Just because you flashed something incompatible doesn't mean you deserve hate. You are a noob. The first time I bricked my phone was when I flashed a zip that was supposed to redesign the settings menu of Android 7 to resemble Android 8. LoL. So don't be hard on yourself. If the phone boots it can be saved.
The combination is power and volume +. Also don't try everything. If the wipes are successful, then just flash hurupdater and you are good to go. If they are unsuccessful then format data first and try again. Format data option is in the same menu
Mannan Qamar said:
Renaming them means that when you download them from Firmware Finder they will be named different. You just rename them normally. The linked threads will provide you detailed info. Just rename them accordingly and you are good to go. Good Luck.
BTW don't be so hard on yourself. We all make mistakes. Just because you flashed something incompatible doesn't mean you deserve hate. You are a noob. The first time I bricked my phone was when I flashed a zip that was supposed to redesign the settings menu of Android 7 to resemble Android 8. LoL. So don't be hard on yourself. If the phone boots it can be saved.
The combination is power and volume +. Also don't try everything. If the wipes are successful, then just flash hurupdater and you are good to go. If they are unsuccessful then format data first and try again. Format data option is in the same menu
Click to expand...
Click to collapse
Haha of course i dont deserve hate, but i was really stubborn, thats it.
Yeah, cant boot into any recovery at all, so hurupdate is impossible.
Also, Im getting lost on all the hwota threads, unfamiliar concepts and stuff i miss so i will posibly do something wrong.
Could you reply with noob-friendly steps on how to install oreo on my device? And if thats not possible ill be satisfied with nougat or even marshmallow, as long as phone works :/. Of course i prefer oreo if possible.
No recovery, when i flash one (stock or twrp) through fastboot, it flashes succesfully but phone doesnt boot into it (yes with vol+ and power), it just goes straight to rescue mode blank screen. Upgrade mode is failing too. Only fastboot works.
inkainsa said:
Haha of course i dont deserve hate, but i was really stubborn, thats it.
Yeah, cant boot into any recovery at all, so hurupdate is impossible.
Also, Im getting lost on all the hwota threads, unfamiliar concepts and stuff i miss so i will posibly do something wrong.
Could you reply with noob-friendly steps on how to install oreo on my device? And if thats not possible ill be satisfied with nougat or even marshmallow, as long as phone works :/. Of course i prefer oreo if possible.
No recovery, when i flash one (stock or twrp) through fastboot, it flashes succesfully but phone doesnt boot into it (yes with vol+ and power), it just goes straight to rescue mode blank screen. Upgrade mode is failing too. Only fastboot works.
Click to expand...
Click to collapse
So you can't enter TWRP? I would recommend that later you flash TWRP through fastboot instead of rebooting press and hold volume up & power button on the bootloader screen. If that doesn't work try flashing TWRP with the following command:
"Fastboot flash recovery_ramdisk (nameofrecovery.img)" . Also HWOTA 7 requires TWRP to be functional. If by any chance you can enter TWRP then make the wipes. Don't wait for anything. Have the Hurupdater files in a SD card along with the firmware.
See myself in the story too LOL. Still can not remember how I got out.....
Try to flash twrp
then run: adb reboot recovery
To fash recovery run:
in Nougat: fastboot flash recovery xxxtwrp.img
in Oreo: fastboot flash recovery_ramdisk xxx.twrp.img
Maybe run both and see what u get.
my phone is hard bricked. it wont even boot to fastboot ot bootloader. three button not working. any help. it just keeps diplaying your phone is now booting. i dont even get three options. please any help would be appreciated
Eww bud is the battery dead? Maybe try to reflash your recoveries
mightyblazer said:
Eww bud is the battery dead? Maybe try to reflash your recoveries
Click to expand...
Click to collapse
even after tye batteries died i am unable to boot into fastboot........
Oh ya hmm not sure about that sorry
Mannan Qamar said:
my phone is hard bricked. it wont even boot to fastboot ot bootloader. three button not working. any help. it just keeps diplaying your phone is now booting. i dont even get three options. please any help would be appreciated
Click to expand...
Click to collapse
Same thing happened to me... any progress?
mangesh2000 said:
Same thing happened to me... any progress?
Click to expand...
Click to collapse
Fixed a few months ago,used it for a while and then sold it.