My Honor 8 (FRD-L04) with official firmware (latest), unlocked bootloader and TWRP recovery, ended in a boot loop
turns on, blue screen, gives the orange unlocked bootloader screen, loads animation and stays on blue screen with honor in white, dims screen and reboots
happened after tinkering around with Magisk and AppSystemizer
moved GPS Joystick to /system/app/ and enabled the options in app, rebooted my phone and it kept rebooting
I can get to fastboot and twrp,
I made the not so wise decision of a partial backup after installing twrp, only backing up Boot, Cache, System and Vendor (didn't have enough space for full)
I downloaded HuaweiUpdateExtraxtor and did the following:
1. Extracted the recovery.img from update.app
2. Fastboot flashed the extracted recovery.img
3. Copied the update.app to a folder named dload located on my uSD root
4. Unplugged and rebooted while pressing vol up, vol down and power
It loads the EMUI update screen says installing update, 5% and fails
tried those steps with B122, B141, B150, B162
Am I missing something?
I had a very similar experience about a month ago.
I was never able to get back to stock because the dload method failed on all my tries on my L04 at 5% so maybe I'm not one to say whether you're doing it correctly but that's the same method I've used that I found from multiple sources.
If you don't have a back up phone I'd suggest flashing twrp and going to a custom rom, aospa is working very well for me, otherwise I think the best bet is to wait for a new update and get that update.app because every link I've tried thats supposed to direct to hicloud L04 B385 update.app is broken, while the L09 links seem to work.
Edit: According to this guide , you should only be pressing volume up and power, so try that.
progress so far, I followed Rommco05 instructions and downloaded
http://update.hicloud.com:8180/TDS/d...ull/update.zip
from https://forum.xda-developers.com/ho...tock-firmware-packages-honor-8-t3501942/page8
flashed TWRP and installed the first one through TWRP, when rebooted gave me a red exclamation! (can't remember what it said)
Downloaded B360 from
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=FRD-L04&firmware_page=0
and copied the update.app to dload folder on uSD
vol up, vol down and power and it finally installed something, but was asking for storage password and keyboard was missing
read somewhere that the recently flashed firmware was trying to use the previous firmware storage or something like that and was fixed by deleting /data
so I went to erecovery (vol up, power) and wiped data... it fixed the storage password but it booted a weird firmware (very laggy, said it was B389 and had no keyboard!!! )
finally followed instructions on link provided by gophillyourself (Thanks!) and that rolled me back to B122!
Currently updating using updater
Related
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.
I found a guide to downgrade my honor h60 l02 and it said to replace the recovery and system with the stock ones from SYSTEM.img and RECOVERY.img in official roms (through fastboot) and I got those files from version b535 using huawei extractor. After flashing those 2 I couldn't start the 3 button format procedure to update with the b535 rom in the dload folder on my sdcard. So I searched for an unbrick procedure and found one on multitool honor 6 xda page. I flashed the boot,cust,system,recovery from b535 with multitool unbrick procedure and still couldn't get in the emui installation screen by pressing vol+vol-power. I tried reformatting sdcard to fat 32 and put again dload folder with update.app inside. I even tried to press the 3 buttons with card partially introduced but still can't start the update procedure. Used another microsd card but no starting. I finally tried to install a custom recovery but only got to install twrp 2.8.70 v2 for emui 4.0 . Before the whole BIG problem I think I had rom with 6.1.19 version which actually had problems with the bluetooth not starting and that was the reason I wanted to downgrade. I also tried to install 2 custom roms for h60 l02 but I got error on zip installation which seems weird considering at list that should work if I can't use the update procedure. I could probablly use fastboot to install all images required for rom but I can't find a scatter file info or a partition guide anywhere for h60 l02 because I cant install any zip from twrp recovery except gapps.
Any help is welcomed! I'll buy you a bear if u can help me !
Problem solved
So I finally got to fix the phone. I found out that the phone was updated to a Marshmallow rom in the beta stage by my friend who gave it to me. The rom was identified succesfully after some searches on 4pda.ru forums where a couple of russians are experimenting how to put android 6 on honor 6 devices. The version was 5.12.31_beta which in device id I think it apears as h60-C00b690sp01. I put the stock recovery and boot from that image with fastboot on phone. Wanted to put also system and cust images but the rom is an update zip which has mixt type of data (system, cust and a few other partition datas are directly in the zip with meta and inf datas while boot,recovery and a few other partition datas are inside the update.app in the zip). Luckilly for me after the boot and recovery flash I could start stock recovery with vol+power button press and also could finally start force update procedure with vol+vol-power buttons pressed (keep in mind that from fastboot I pressed the 3 buttons continuoselly while the phone restarted , went to a honor logo display, after about 5 seconds it restarted and started emui installation screen; for some reason even from powered off state the device needed to go to the honor screen before on the restart to emui installation screen and Ive seen videos where the devices just go straight to emui installation screen). I got a downgrade package from 4pda.ru forums and tried to install it with forced update procedure but it got stuck at 5%. After 1 more day I figured out that I need to pull the usb cable out before the emui installation screen because it would show a usb connected icon on screen instead of showing emui installation icon (I thought at first that thats how it should look for marshmallow stock roms xD) and Im thinking that if u keep usb cable plugged in it tries to get flash image from usb and if that is unplugged it tries to get image from sdcard dload folder. So I flashed the downgrade version and after restart to honor logo screen I restarted device to fastboot mode with ofc vol-power buttons pressed and pulled the sdcard out. I replaced downgrade package (update. app from H60-LX2_EMUI4.0_2_EMUI3.1 dload) with the dload folder of the b535 stable rom (H60-L02-L12_EMUI3.1_Android5.1_C00B535 rom) on the sdcard. I restarted device and used again 3 button update without usb plugged in xD and it installed all the way. After 100% installation the device rebooted and after showing a big „w” it got to pulsating honor logo screen and after about 10 minutes it showed me language menu for language selection. And the desperation saga ended xD. Happy ending!!!
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Download the 70mb package for firmware downgrade and the latest marshmallow firmware from your regional huawei's website.
Extract the small package and put the .app file in a folder called dload on the SD card and insert it in your phone.
Boot by holding volume + volume - and pressing power, holding all 3 buttons until the phone vibrates.
The package will flash and afterwards you repeat the process, this time using an .app file from the full marshmallow firmware.
The 70mb package installs not matter how messed up your file system is, and makes your phone ready for the MM firmware. This process brings any brick back to life. Good luck.
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
menriquez said:
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
Click to expand...
Click to collapse
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
sysak said:
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
This is truly one of the worse phones I have ever had when it comes to root and such. My frustration over what, for a unbranded unlocked phone that *should* probably SHIP with root, this phone has and is putting me through is super high.
That being said...so I flashed the new 3.1.0.0 recovery. Before doing that, I had just tried to Unbrick the phone with flashing B162 image with 3.0.3.0...so now the phone is totally frozen in the "Your device has been unlocked and can't be trusted..." screen. Nothing I seem to do can get it out of this mode.
I want to install the rooted b378 boot.img file I just downloaded, but am unable to find the button commands to get the bootloader loaded. Does anyone have any suggestions in somehow trying to save the day with this damned phone?
much thanks in advance.
EDIT: So I got the phone in bootloader mode by pressing vol up/vol down/power and inserting the usb cable...i flashed the rooted boot.img and twrp 3.1.0.1 to both recovery and recovery2 and now i can get into recovery. I feel like I may actually have a chance now to fix this damn thing...
So can anyone point me in a direction where, from this point with the new recovery loaded and the modded boot image installed, where i can get this phone working?? ill use ANY ROM it dont really matter at this point...
Don't worry. It's really easy, once you know what to do, just realy easy to screw up if you don't. If your phone is a mess just roll back to android 6 using the procedure i described above. Once your phone works, update to nougat and install twrp and root following this guide: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Same issue
Ramonator said:
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Click to expand...
Click to collapse
I pretty much have the same issue. No keyboard showing, just the stupid voice thing, and the Bootloader is Relocked. How did you get it fully unlocked. I can't get it. I guess let me get that resolved first (the bootloader) and I can try to go from there. Please help me.
UPDATE: Never mind I fixed it. I'm not really for sure how either but I think it mainly was just persistence.
Didn't work
Hello, so earlier today I tried to install RROS newest version in hope to get magisk/unrooting my phone because I'm addicted to snapchat and I rooted my phone with SuperSU earlier but didn't know u can't login to snapchat after that. It failed idk why, (I followed instructions very clearly and searched info from internet before doing that) causing me to brick my phone so when I booted it, it only showed black screen. After couple hours not finding way to get into twrp with my circumstances I managed to flash boot, recovery and system images, I tried to reboot and see what happens, (just in case, I kinda knew I didn't had ROM installed at the time, I also was hoping RROS to boot) nothing happened expect my phone got stuck in boot screen for booting EMUI, which was not installed obviously. Again after couple hours I stumbled to your post and managed to finally get myself into TWRP, I followed again ur instructions and everything was going fine, no erros, not anything. When Gapps was finished installing, I rebooted and again it just got stuck into booting screen. I did press and hold Power button, vol+, vol- and got myself into some kind of ROM installing screen, (hard to explain I don't exactly know what is name of it) and no it wasn't Huawei erecovery screen (Power button & Vol+ and no it didn't work me either saying that "getting package info failed") so in that ROM installing screen it just was stuck at 5% installing, and now I don't know what to do. My phone got locked again and I'm stuck at booting screen.
Note:
I don't have SD Card, should I get one and install stock rom?
Sorry for being kinda unclear but I'm tired it was 7 hours ago I got my phone bricked and have surfed on the web finding for answers ever since.
Also as you might notice, yes, I'm new to modding devices etc but still I'm not totally noob. Please help ASAP.
[SOLVED] So after hour of watching netflix as depressed teen I tried to reboot my phone again just in case, got stuck in booting screen. Then I held Power Button + Vol+ and got myself into EMUI stock recovery mode, I chose wipe cache partition and wipe data/factory reset, after that I rebooted my phone, it was stuck in booting screen for like 2 minutes but then it actually finished booting and now my phone is again functioning and god bless locked & unrooted.
[Deleted /]
Ok. lets try this again.
My device is a FRD-L19 fresh out of the box deliverd with C432B131. My original plan was to just wipe EMUI and install Linage. So the very first thing I did was unlock the bootloader and install TWRP as described in this thread. Only to find out that I have to update EMUI to 5 in order to install Linage. I tried but the updater did not offer any updates. So i decided to roll back and thats where I made the mistake to flash the rollback package from N to MM, while still on MM.
My system seems gone or at least unable to boot up. Im stuck in the "Your device has been..." message. Here is what I tried:
- I'm able to boot into fastboot via Vol- Power and USB cable plugin.
- Full Wipe in TWRP
- flash new images via fastboot (Unbrick option in Multi Tool with images from this file from the hihonor web page )
- dload via external sdcard with the update.app from the above fails at ~ 45% tried 3 times
- I can get to the EMUI Logo with Vol+ + power button, but I'm not sure if that is erecovery(I have never seen it). If I do so the percentage count up to about 10% and then fails with message The update package does not exist.
- I searched a lot of the Honor 8 Q&A and guides section for someone that was as stupid as I am, but seems I'm the stupidest.
Well after swallowing all this and giving this thread some information I can only beg for help. Has anyone an idea on how to unbrick this?
BTW: TWRP was my last option to switch the device of, but as I changed it to stock its gone. maybe I try to reflash twrp for now just to turn the device off.
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