Database Users

[Q] LG G2 bricked and can't flash stock firmware!

So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information​
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happened​I actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I did​So I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happened​After that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...

Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2

XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!

Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions

evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?

Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:

evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!

Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:

evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!

Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out

my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all

Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app

We now have LOLLIPOP for F400K!! Yayyy! Download link in thread

Here, guys. Linking to a thread from a Chinese forum.
And it's not a troll thread! I decided to be brave and flash it! Yayyy! I now have Lollipop on my G3 F400K version but WiFi doesn't turn on as of now. And no root.
Shall use it for the better part of the day and post here.
http://www.cnanzhi.com/romdetail/4919

I cannot understand how to use that... can u help me?

It's pretty straightforward.. Download the three files in the link provided above and flash them from your custom recovery.
Use Google translate for every link.
I've got this on my phone since the last 5 hours and I haven't used it much for bug testing. But the phone works perfectly and the software is a daily driver for sure!

Did you flash modem? Is WiFi working well?

Didn't flash any extra modem. Wifi not turning on. See the first post.
That's only bug I see as of now.

I think modem can help that problem... I ll try. I hope this file won't wreck my recovery partition as 19c did...
And sorry for my bad English

DokdoIsKoreanTerritory said:
I think modem can help that problem... I ll try. I hope this file won't wreck my recovery partition as 19c did...
And sorry for my bad English
Click to expand...
Click to collapse
you will see the modem and mods in the info translate it theirs a link there for modems ,patches and mods sorry for my bad english ehehe

is it really for F400K ? I dont think that, it look like a ported from D855
I also saw a ported package from F400S at http://www.fshare.vn/file/1CMRFVXM4A/ (I flashed and it worked - 1 week ago - I back to stock 4.4.2 to wait for OTA)

where did you get that link can u share the forums?

i lost root. And now I can't flash a new ROM. Any heads up?

frankmehta said:
i lost root. And now I can't flash a new ROM. Any heads up?
Click to expand...
Click to collapse
I think you're screwed since you're running the new bootloader (or kernel, not sure) you can't downgrade, and since there isn't lollipop for f400k you need to wait

frankmehta said:
i lost root. And now I can't flash a new ROM. Any heads up?
Click to expand...
Click to collapse
Have you tried a "adb reboot recovery"? My f400k on cloudy won't enter bump recovery with any of the usual start up sequences I have found. The only way I can do it is with reboot to recovery on the restart menu or "adb reboot recovery" maybe yours is the same?

Mine boots into stock recovery.
I don't even have root.
Kdz method doesn't work because Flash toll recognizes the phone has a d855.
Flashing a d855 dll is suicide.

frankmehta said:
Mine boots into stock recovery.
I don't even have root.
Kdz method doesn't work because Flash toll recognizes the phone has a d855.
Flashing a d855 dll is suicide.
Click to expand...
Click to collapse
Have you had a look at the return to stock guide? http://forum.xda-developers.com/showthread.php?t=2785089
I haven't done it from Lollypop nor do I know much about this kind of thing so make sure you do some research first.

daveaus said:
Have you tried a "adb reboot recovery"? My f400k on cloudy won't enter bump recovery with any of the usual start up sequences I have found. The only way I can do it is with reboot to recovery on the restart menu or "adb reboot recovery" maybe yours is the same?
Click to expand...
Click to collapse
Heyy mine is like yours, I can't enter recovery when on boot. But can enter with a app or menu (tweakbox).
How do I fix this? I am afraid of bootloops and want to get into recovery when I get one.

KingOfDope said:
Heyy mine is like yours, I can't enter recovery when on boot. But can enter with a app or menu (tweakbox).
How do I fix this? I am afraid of bootloops and want to get into recovery when I get one.
Click to expand...
Click to collapse
Please let me know if you find out.
I asked the super helpful guys in the bump IRC chat room but no luck. I am going to be super careful about what I flash until a method is found.

P8 Lite strange brick

Hello i'm a new user of this forum and i'm italian so sorry for my bad english. I'm an enthusiast android user.
now i have a perfectly working p9 lite but 1 year ago i had bricked my old p8 lite and today i returned to work on it but the problem are the same as before.
1 year ago the android 5 lollipop was the latest for the p8 lite and i rooted with no problem with random root application unfortunally maybe kingroot...... but all was ok for months. after i updated my p8 lite to android 6 mm and i tried to root, after many tryes i sucsessfull root my device, but the xda framework didnt work at all at that time the mm version was too new. so i tried to rollback to android 5, but i didn t know about a correct rollback update, so i flashed android 5's boot, cust, recovery and system.img via fastboot. i saw that the sim didn't recognised and so i discovered that the imei was lost........ And believe it or not, this is not entirely the problem.... after that i was in panic and i went to assistance and there they tell me that the motherboard was to replace.... so for the cost of the entire phone i decided to not pay. after i tried to follow so many guides my friend, you not even any ideas.... but one guide seems to work, i had to flash b049 or b52 (don not remember) and after my b190 but at the b49/b52 it give balong problem, after i fixed with a vendor little flash but the imei was completely gone in every versions..... i was sad... but while a flash and another thi biggest problem born.......... the phone bootloop, but NOT a normal bootloop, it starts correctly every versions but after 10 seconds of a working os ( i can go in settings, start application ec but it give up and restart totally not explayned.... i've formatted 1000 times and the force update fail or bootloop itself at 10 or 11% (10seconds....) same with recovery... only in rescue/fastboot mode it do not restart after 10 seconds and in the twrp 3.0.2 that i tried to flash every modded firmware in zip and at system flash it restart (seems like the 10 second stuff). now the imei problem is not a request because now i've the p9 lite and i dont need the phone things but the system.... its unplayble with the 10 secodns restart loop.... please is hard but HELP.

Franseven said:
Hello i'm a new user of this forum and i'm italian so sorry for my bad english. I'm an enthusiast android user.
now i have a perfectly working p9 lite but 1 year ago i had bricked my old p8 lite and today i returned to work on it but the problem are the same as before.
1 year ago the android 5 lollipop was the latest for the p8 lite and i rooted with no problem with random root application unfortunally maybe kingroot...... but all was ok for months. after i updated my p8 lite to android 6 mm and i tried to root, after many tryes i sucsessfull root my device, but the xda framework didnt work at all at that time the mm version was too new. so i tried to rollback to android 5, but i didn t know about a correct rollback update, so i flashed android 5's boot, cust, recovery and system.img via fastboot. i saw that the sim didn't recognised and so i discovered that the imei was lost........ And believe it or not, this is not entirely the problem.... after that i was in panic and i went to assistance and there they tell me that the motherboard was to replace.... so for the cost of the entire phone i decided to not pay. after i tried to follow so many guides my friend, you not even any ideas.... but one guide seems to work, i had to flash b049 or b52 (don not remember) and after my b190 but at the b49/b52 it give balong problem, after i fixed with a vendor little flash but the imei was completely gone in every versions..... i was sad... but while a flash and another thi biggest problem born.......... the phone bootloop, but NOT a normal bootloop, it starts correctly every versions but after 10 seconds of a working os ( i can go in settings, start application ec but it give up and restart totally not explayned.... i've formatted 1000 times and the force update fail or bootloop itself at 10 or 11% (10seconds....) same with recovery... only in rescue/fastboot mode it do not restart after 10 seconds and in the twrp 3.0.2 that i tried to flash every modded firmware in zip and at system flash it restart (seems like the 10 second stuff). now the imei problem is not a request because now i've the p9 lite and i dont need the phone things but the system.... its unplayble with the 10 secodns restart loop.... please is hard but HELP.
Click to expand...
Click to collapse
Do you have access to rescue mode/fastboot? Maybe flashing TWRP would help
P.S.-- DON'T EVER RUN KINGROOT ON P8LITE; MAYBE IT WILL SUCCESS, BUT YOUR DEVICE WILL BE MESSED UP

XTutorials said:
Do you have access to rescue mode/fastboot? Maybe flashing TWRP would help
Click to expand...
Click to collapse
yes, Maybe I was not clear but rescue mode is the only one where no automatic restart occurs. I twrp it and tried it but it did not help. If you are expert please give me more advice

Franseven said:
yes, Maybe I was not clear but rescue mode is the only one where no automatic restart occurs. I twrp it and tried it but it did not help. If you are expert please give me more advice
Click to expand...
Click to collapse
I have some questions:
1. What means"I twrp it" ? I know you're italian but please more details; did you flashed it succesfully?
More, I want a response to this question first

XTutorials said:
I have some questions:
1. What means"I twrp it" ? I know you're italian but please more details; did you flashed it succesfully?
More, I want a response to this question first
Click to expand...
Click to collapse
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system

Franseven said:
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system
Click to expand...
Click to collapse
Try here it might work

cristi.blidariu said:
Try here it might work
Click to expand...
Click to collapse
in fastboot mode hicare don't see my device, If you think that this particular version b132 changes something I try but I think it will restart every 10 seconds as the others ..

Franseven said:
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system
Click to expand...
Click to collapse
For this fix, you should have and sd card
Download sokkoban's emui 4.0.3 B596, copy to sd card, erase everything in TWRP (cache, dalvik, data, system, internal storage), then flash the .zip you copied to the sd card.

XTutorials said:
For this fix, you should have and sd card
Download sokkoban's emui 4.0.3 B596, copy to sd card, erase everything in TWRP (cache, dalvik, data, system, internal storage), then flash the .zip you copied to the sd card.
Click to expand...
Click to collapse
Also by deleting everything in the twrp recovery the other .zip phones will restart as twrp is copying system, with b596 should not happen?

Franseven said:
Also by deleting everything in the twrp recovery the other .zip phones will restart as twrp is copying system, with b596 should not happen?
Click to expand...
Click to collapse
Maybe, try

XTutorials said:
Maybe, try
Click to expand...
Click to collapse
nope.. i've tried right now and it do same thing

Franseven said:
nope.. i've tried right now and it do same thing
Click to expand...
Click to collapse
Try to erase everything in twrp -->>advanced wipe-->> tick everything and click wipe.
Then flash latest TWRP (3.1.0-1) And try again flashing B596

XTutorials said:
Try to erase everything in twrp -->>advanced wipe-->> tick everything and click wipe.
Then flash latest TWRP (3.1.0-1) And try again flashing B596
Click to expand...
Click to collapse
ok done.
install zip
successful
but down i see
E:unknown command [errno]
dalvik wiped
now reboot
and....splash logo ok...reboot.......splash... again.. yes bootloop, but now seems normal
my initiative , i m going to hard resetnow
factory reset done
reboot
bootloop again my friend.
EDIT:
tried again, after 3 bootloop emui show to load but restart again. after that emui load and while the language selection it shutdown automatically, this time don't restart. we see tomorrow

Franseven said:
ok done.
install zip
successful
but down i see
E:unknown command [errno]
dalvik wiped
now reboot
and....splash logo ok...reboot.......splash... again.. yes bootloop, but now seems normal
my initiative , i m going to hard resetnow
factory reset done
reboot
bootloop again my friend.
EDIT:
tried again, after 3 bootloop emui show to load but restart again. after that emui load and while the language selection it shutdown automatically, this time don't restart. we see tomorrow
Click to expand...
Click to collapse
Oh my god.... that error is just a log, everything works, don't panic so again.
Go to twrp-- wipe-- advanced wipe-- tick(check) all and clikc wipe
reflash twrp 3.1.0-1,
flash again zip, and don't care about that error, that means it succesfully flashed the rom

XTutorials said:
Oh my god.... that error is just a log, everything works, don't panic so again.
Go to twrp-- wipe-- advanced wipe-- tick(check) all and clikc wipe
reflash twrp 3.1.0-1,
flash again zip, and don't care about that error, that means it succesfully flashed the rom
Click to expand...
Click to collapse
i've done what your saying, and the result is that when the device reach the boot logo starts a sort of timer, and after 10 seconds the os crash in every case with every firmware... thats not help

Franseven said:
i've done what your saying, and the result is that when the device reach the boot logo starts a sort of timer, and after 10 seconds the os crash in every case with every firmware... thats not help
Click to expand...
Click to collapse
Then I'm done... I don't know man other fixes. I've read os kinda same type of hard brick that if you disconnect the battery and plug it in back does something

XTutorials said:
Then I'm done... I don't know man other fixes. I've read os kinda same type of hard brick that if you disconnect the battery and plug it in back does something
Click to expand...
Click to collapse
in the p8 lite the battery is unremovible, i must try with deassemble tutorial?
but have you ear of this type of bootloop? with this strange timer crash?
EDIT:
i just followed a guide for battery sostitution, i've unplagged and replugged and the "timer boot loop/ os timer crash" continue.
now i m trying to unplug for 5 mins to do safe.
Ok done. same bad result.. please if you can't help, make this post still alive invite if you have expert friend, i'm going mad.

I think it's problem with the hardware, that the power button pressed continuously.
Because in our phone if you keep pressing it for 10 seconds it will force restart.
Actually I don't know about twrp flashing problem, if it also do the same or not...
you may check the power button..

salembream said:
I think it's problem with the hardware, that the power button pressed continuously.
Because in our phone if you keep pressing it for 10 seconds it will force restart.
Actually I don't know about twrp flashing problem, if it also do the same or not...
you may check the power button..
Click to expand...
Click to collapse
oh i thought that... i can try to dissassemble but i hope to not damage the device..
wait a minute... but when i click the power button i can hear sonor "clak" don't seems to be pressed costantly..
EDIT:
its definetely not a power button problem, i dissassembled, i replug the battery, so pressed power button, while booting i unplugged the contact of the power button and volume +- so i cant even seems pressed. same happened after 10 seconds it restart. sorry bad english

P9 Lite wont turn on

Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...

fr4nk32 said:
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
Click to expand...
Click to collapse
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck

Dadditz said:
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Click to expand...
Click to collapse
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.

fr4nk32 said:
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
Click to expand...
Click to collapse
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery
(name.of.recovery).img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added

Dadditz said:
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery.img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Click to expand...
Click to collapse
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.

fr4nk32 said:
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
Click to expand...
Click to collapse
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...

Dadditz said:
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Click to expand...
Click to collapse
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!

fr4nk32 said:
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
Click to expand...
Click to collapse
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.

Dadditz said:
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Click to expand...
Click to collapse
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.

fr4nk32 said:
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
Click to expand...
Click to collapse
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards

Dadditz said:
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Click to expand...
Click to collapse
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....

fr4nk32 said:
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
Click to expand...
Click to collapse
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )

Dadditz said:
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Click to expand...
Click to collapse
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:

fr4nk32 said:
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
Click to expand...
Click to collapse
Ok i'm glad to see that worked..
I wish to thank in a special way Firmware Finder TEAM that with their
programs gave us the chance to solve many problems, THX guys. :good:
See you

Hard bricked,only vibrates

Hello guys,i was trying to flash LOS and after many tries i hard bricked my phone.At start,screen wasnt turning on and phone vibrated sholtly every 1 sec.I did EDL and then flashed different roms but still phone just vibrates but for a bit longer.When i do EDL it gets recognised by pc.Also when i flash a rom before i try to boot,if i connect it to power the led is blinking.
I dont want to be this guy who opens a thread that has opened many times,but i couldnt figure out a solution whatsoever.Thanks in advance.

Did you try downgrade from pie to oreo? Can you enter fastboot mode?
I bricked my phone too. Nothing worked for me. I hope you have more luck.

How it got bricked? Did you read the whole tutorial ?

emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.

degen1997 said:
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
Click to expand...
Click to collapse
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp

emiljano539 said:
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
Click to expand...
Click to collapse
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.

degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
Check it :https://forum.xda-developers.com/showpost.php?p=75711835&postcount=2
I hope it helps

degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.

XtraWater said:
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
Click to expand...
Click to collapse
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me

emiljano539 said:
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
Click to expand...
Click to collapse
I recommend you to read a lot about flashing custom ROMs before trying to do it.
LineageOS has a pretty explicit installing tutorial.

If you can get into fastboot mode there is hope.
Remember that you must have the bootloader unlocked.

my thread
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
Hi everyone, I have rooted Mi A1 (pie), I have a hard brick. but fixed, when flashing Rom with TWRP, my phone cannot receive the partition / 'cache', when root receives the message: error: 28, I need help, thank you very much