BLN-L24 Bricked/Bootlooped after rollback - Honor 6X Questions & Answers

I was rooted with TWRP but I want to sell this phone so I was rolling back to stock. I was able update successfully both times (back to B300 and then initial B310 firmware) and after the 2nd update it did an automatic data reset just like the instructions said it would. Now my phone is bootlooped stuck on the honor screen and I need some help getting it back. I read that rolling back will relock your bootloader so I assumed (incorrectly obviously) that it would just return everything to stock.
I now have stock recovery and erecovery works as well. Tomorrow when I get into work I'll be able to get it into fastboot then what do I need to flash to get this thing working again? Thanks in advance

just flash the respective firmware via dload and it will lock both bootlaoder and FRP and should be good to go with full stock.
let me know in case need help, will try as much as can.

Which firmware? I already used the dload method in my attempt to rollback to emui 4.1 since I read that would relock my boot loader. Both parts of the 2 part rollback were successful according to the updater . After the first update my phone boot and I was able to check in settings that I was rolled back to B300 firmware. I then did the dload with the B110 firmware and upon completing sucessfully it automatically reset my phone and went straight to bootloop.
In the following post the person says unroot and relock boot loader first which I did not, does that have anything to do with it?
https://forum.xda-developers.com/honor-6x/help/how-to-rollback-package-huawei-gr5-2017-t3574399

Dazed No More said:
Which firmware? I already used the dload method in my attempt to rollback to emui 4.1 since I read that would relock my boot loader. Both parts of the 2 part rollback were successful according to the updater . After the first update my phone boot and I was able to check in settings that I was rolled back to B300 firmware. I then did the dload with the B110 firmware and upon completing sucessfully it automatically reset my phone and went straight to bootloop.
In the following post the person says unroot and relock boot loader first which I did not, does that have anything to do with it?
https://forum.xda-developers.com/honor-6x/help/how-to-rollback-package-huawei-gr5-2017-t3574399
Click to expand...
Click to collapse
Nope. Dload woll lock the bootloader. I tried today but seems some issue and we may need to flash the boot.img before proceeding. Tried 3-4 times today but no luck. Will try later now as this is primary phone with all official apps installed

shashank1320 said:
Nope. Dload woll lock the bootloader. I tried today but seems some issue and we may need to flash the boot.img before proceeding. Tried 3-4 times today but no luck. Will try later now as this is primary phone with all official apps installed
Click to expand...
Click to collapse
Are you saying I need to flash the boot image? I thought boot, recovery and all the necessary images were contained in the update.app and are flashed on a successful dload update. I do know my boot loader is relocked
Like a fool I forgot my SD card on the bedside table this morning so I won't be able to dload anything but I will be able to ABD/fastboot once I get to work. I.was thinking of extracting the boot.img from the update.app and flashing it via adb

Dazed No More said:
Are you saying I need to flash the boot image? I thought boot, recovery and all the necessary images were contained in the update.app and are flashed on a successful dload update. I do know my boot loader is relocked
Like a fool I forgot my SD card on the bedside table this morning so I won't be able to dload anything but I will be able to ABD/fastboot once I get to work. I.was thinking of extracting the boot.img from the update.app and flashing it via adb
Click to expand...
Click to collapse
I am not saying this exactly but yeah, after unroot via zip, i got the message on recovery that i may need to flash the boot.img to completely unroot it and then proceed but I never did that.
I used dload main zip content and was success but device went to bootloop. Then later I tried the 2nd file and same. Earlier I used to flash both fine but only 2nd would boot me fine and main zip will lead to bootloop.
yeah, update.app contains all, not sure why its not working and flashing the boot.img directly.

In fastboot phone is locked FRP unlocked. I cannot flash boot.img, says
FAILED (remote: command not allowed)

Dazed No More said:
In fastboot phone is locked FRP unlocked. I cannot flash boot.img, says
FAILED (remote: command not allowed)
Click to expand...
Click to collapse
Tried unlocking the BL? Once that is done, you may proceed further

Unlocked BL and flashed boot.img from B110 update.app and still no boot
edit: last night booting into recovery (vol + and power) gave me three options: Reboot/Wipe Date Reset/Wipe Cache. Since unlocking the bootloader and flashing the boot.img today the same button combo launches eRecovery with Wifi update option but it fails getting package info.
Is it normal for factory reset after lock/relock to go from 15% to 100% and say succesful?

I used the team mt huawei multi tool app and after using the unbrick option it flashed boot, cust, recovery, system and userdata.img and my phone now boots! Shashank thank you for taking the time to respond.

Related

Frp locked

Ok, here is the deal, i was being impatient, i flashed nougat yesterday on my phone, after flashing it there was no keyboard to enter my email to login, so i stupidly but unknowingly so changed my gmail password to an easier one cause the only input method i had was voice commands, anyways, i got helped out by another xda member, and i got FRP locked for changing my password, then i attempted to rollback to MM, now my bootloader is relocked and it says FRP LOCKED, the thing is i did a nandroid full backup with twrp of everything on my phone before starting all this and every step along the way when something went wrong i went to twrp to recover but the restore did not appear despite having it on my sd card so idk if it have to be on internal memory or there is something wrong with twrp, currently my phone is bricked and i need help recovering it since i am broke these days and i can't afford another phone and it's out of warranty, if the backup can be restored somehow or any other methods, please guys let me know, any help is greatly appreciated
i flashed rollback package, then b320, then black screen, then flashed b200 failed at 5%, b162 also failed at 5%, then flashed the rollback package one more time, now i am stuck with the huawei logo, can't flash anything else, any long press just shuts the phone for a second then takes me back to the huawei logo, i can only access the bootloader and it is FRP locked
Read here:
https://forum.xda-developers.com/mate-8/help/frp-locked-bootloader-update-to-n-t3524202
Flash latest recovery2.img of nougat and then try dload
Use huawei exrtacor to get recovery.img
And then flash using fastboot
Then dload ur original FW before updating to nougat
h4ni said:
Use huawei exrtacor to get recovery.img
And then flash using fastboot
Then dload ur original FW before updating to nougat
Click to expand...
Click to collapse
and how do i flash this img?
Tavros said:
Read here:
https://forum.xda-developers.com/mate-8/help/frp-locked-bootloader-update-to-n-t3524202
Click to expand...
Click to collapse
i read there and asked and no one replied me back yet, i also tried the method listed in one of the comments about rollback then 320 and that didnt work
Armali said:
and how do i flash this img?
Click to expand...
Click to collapse
"And then flash using fastboot "
Pfeffernuss said:
"And then flash using fastboot "
Click to expand...
Click to collapse
i'm FRP LOCKED, my bootloader is locked, and i can't use ADB commands
I have the same problem. I am on nougat and I cant enter my google account details because I only have google keyboard voice input wich doesnt work... so its dead now?

stock recovery corrupted

apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
same here. did you managed to work it out?
Solved
eelc said:
same here. did you managed to work it out?
Click to expand...
Click to collapse
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.
Mass1veDynam1c said:
Yes finally. You have to download the update file for whatever version of the rom you currently have installed. Then extract userdata, boot, system, and erecovery1 and erecovery2 images. Fastboot flash them in bootloader mode. Reboot device. Shutdown device. Boot to system recovery and do a full system restore. All set.
Click to expand...
Click to collapse
can u make the total tutorial video of this whole process ???
I would ask if you could post a link to the update you used and a list of the commands you used..im in the US ..so it is honor 6x for the US
bricked honor 6x
You need three softwares
1. huawei multi tool by mt,,,,, in english version bro
2. Huawei update extractor
3. Firmware file update .zip
First extract the zip file , there you will get update.app file . Extract BOOT.IMG RECOVERY.IMG SYSTEM.IMG USER DATA.IMG using Huawei extractor software .
NOW open huawei multitool app (internet connection required)
Put all these files you extracted in unbrick folder of huawei multi tool
Follow steps to unbrick your device
Thank you..
can you send the links please....thank you!
Mass1veDynam1c said:
apparently my stock recovery is corrupted. I am unable to flash back to stock or apply any updates. the phone hangs at the bootloader unlocked warning screen every time. I have tried everything to try to fix it but nothing works. I extracted the stock recovery and even tried to fastboot flash it but it didn't work either. does anyone have any suggestions? the phone is not rooted, but the bootloader is unlocked. thanks so much is advance.
**also mean to mention that erecovery will not work either. it always says download failed
Click to expand...
Click to collapse
Try to flash twrp first , later flash stock recovery from twrp by clicking on flash image . Be sure u are installing a working recovery but not a corrupted one

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

Stuck with fastboot mode.

Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.
casperskie said:
Ok, so I had oreo in my 6x indian variant, and wanted to flash elemental OS V8. But for some reason the TWRP was not able to access the data partition. And when I read somewhere in XDA (in other device's forum) that changing the file system from f2fs to ext4 can help and did so and it worked. I could access my internal storage and everything on TWRP. But I didn't change the file system back to f2fs and sideloaded the elemental 8. It worked find and I installed it. When rebooting it got into bootloop. After that I tried to get into the TWRP but didn't work. I flashed the TWRP again which said flashed OK, but when I tried to enter it took me to the stock recovery. When I tried the dload method with the nougat B360 version, it gave me blank screen with red led blinking and nothing working after that. I tried dload with the oreo file which gave me back the stock recovery and erecovery, but again flashing TWRP didn't work. After dload, it reboots to erecovery and asks me to wipe data partition since it is severely corrupt but says factory reset failed. In some cases it does go factory reset but doesn't boot into OS. Since I do not have access to TWRP I am not able to bring it back. I had got into this situations before but the dload always worked. Maybe now it isn't because I am on Oreo and the partitions are different from Nougat? I also tried formatting/erasing partitions from fastboot but gives me error/ remote command not allowed. I also tried Multi-Tool8 and used the unbrick option. but doesn't work it gives me all flashed, and when i flash the oreo files gives me all flashed Error#1, Complete, Something went wrong and bootloops again or gives me blank screens.
I have attached a screenshot of my device info. If anyone could help me breath life into it.
Click to expand...
Click to collapse
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Mannan Qamar said:
What command you use to flash TWRP? And what image are you trying to flash? Try this. In Fastboot flash RECOVERY-V2.img (Elemental ROM TWRP) via command.
fastboot flash recovery_ramdisk RECOVERY-V2.img
After it's flashed, press and Hold Power and Volume Up till you see Honor logo then let go. It Should boot to TWRP. If not then extract the Uodate.zip (the large one) and you will get Update.app and using Huawei Update Extractor extract System.img, Ramdisk.img and Recovery_ramdisk.img then boot phone to fastboot and flash them manually as
fastboot flash boot boot.img
fastboot flash recovery_ramdisk Recovery_ramdis.img
And,
fastboot flash system system.img
This should work. It's a boot error.
Click to expand...
Click to collapse
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
I actually relocked and unlocked the bootloader again, just to be sure. But will try the B340 one, didn't try that. Thanks for the links will check them out
casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Yes, boot is ramdisk in oreo and recovery is ramdisk_recovery.
shashank1320 said:
I was in same mode in fastboot when i updated to Oreo and it was b340 which saved me from this via dload. You give it a try.
You may not be able to flash twrp now as your BL me be locked after dload.
Click to expand...
Click to collapse
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?
casperskie said:
So the B340 dload didn't work for me. Gives the same results. Always boots into erecovery and then fails to factory reset. Also the phone doesn't get switched on or boot into recovery without connecting to the USB. Only when it is connected it works, that too after 5-10 mins after I press the Power button or the Recovery key combination. And I used a 4GB memory card, could this be the reason the dload didn't work?
Click to expand...
Click to collapse
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?
casperskie said:
I did try that but from the unbrick option from Multi-Tool. And also there are two recovery images in the UPDATE.APP and I don't know which one to flash. When I tried from the Multi-Tool, it says you're trying to flash the wrong image. Also I think the boot partition in oreo is ramdisk? I am not sure... because there is no boot image in the unbrick option. Although I didn't try flashing them individually. I will try it and let you know. Thanks.
Click to expand...
Click to collapse
Nope flashing the files individually also doesn't work. it's all the same.
shashank1320 said:
You may need 8 GB SD card if you have or can borrow and see if that helps. Whats the size of update.app file?
Click to expand...
Click to collapse
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app
casperskie said:
Something around 3.3 GB. There's only some 250mb left in the card when I copy the update.app
Click to expand...
Click to collapse
May be you can try with 8 gb once if it is easily available for you
Hi, so none of the methods work. But I could get back to TWRP for Elemental Rom. Still flashing roms from TWRP doesn't boot me in. And now the dload screen doesn't appear when I press the combination. All I have is fastboot mode, erecovery and TWRP installed. But none of the methods work. I am not able to figure what I am doing wrong!!
Try hurupdater.
http://https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
0.3 for nougat or 0.4 for oreo (in my case works)
And remember format data in first time
You need the firmware for your 6x...
Good luck!
hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.
ppawan said:
hey i am in the same situation as yours, all i am able to boot into is fastboot, nothing beyond that is working, i have the extracted update.app for oreo , the last system i flashed was emui oreo , and nothing else is working i have tried all the options suggested.
could someone guide me on the actual steps needed to flash the .img files as i'm unable to boot into recovery of twrp or openkirin
any help will be appreciated.
Click to expand...
Click to collapse
Just dload the b340 image of nougat and back to nougat.

Help me unbrick my device - stuck on TWRP logo

So I tried to put Lineage on my phone, I did on my previous one as well. Something went wrong though (during wiping in TWRP) and I restarted the phone, and now I can't get it to at least factory condition. I guess something got messed up with encryption.
My problem is that the phone gets stuck on TWRP splashscreen and I don't know how to fix this.
My build number is: (bootloader) :BKL-L09 9.0.0.203(C432E4R1P12)
I have downloaded a full OTA but the dload method failed me. Is there a way to flash stock eRecovery? I have tried this below which didn't work
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
I pulled from the UPDATE.APP to no avail.
Is there something I can do to make my phone work again? Or is my phone just bricked?
EDIT: The bootloader is unlocked and FRP is unlocked too. I get boot into rescue mode and my phone get recognized by the adb.
boot to Bootloader and execute adb cmd 'fastboot -w',next step brush official rom on Bootloader mode,it's should be normal reboot.
changnesia said:
So I tried to put Lineage on my phone, I did on my previous one as well. Something went wrong though (during wiping in TWRP) and I restarted the phone, and now I can't get it to at least factory condition. I guess something got messed up with encryption.
My problem is that the phone gets stuck on TWRP splashscreen and I don't know how to fix this.
My build number is: (bootloader) :BKL-L09 9.0.0.203(C432E4R1P12)
I have downloaded a full OTA but the dload method failed me.
Click to expand...
Click to collapse
I've had trouble with the dload method myself at first, too, but I eventually managed by doing this : https://forum.xda-developers.com/t/...ed-from-firmwarefinder.3847443/#post-84862197

Categories

Resources