Develop Bugs

Stock Recovery Image LU6200 Required or Method to extract a Stock Recovery Image

Hi Everyone,
Please help me if anyone have the stock recovery image file for lu 6200 or a method to extract the stock recovery from the phone for flashing the recoveryfile only to get back to stock recovery instead of flashing the whole phone to stock and doing all the setup and configurations.
I searched everywhere but not found any yet for 6200
---------
Here is the stock recovery I am able to extract from the 6200 can be flashback to phone atleast it worked for me.
Download:
LG Optimus LTE aka LU6200 Stock Recovery
Note: Flash it on your own risk, it work fine for me however I have no responsibility for anything go wrong

hackenggr said:
Hi Everyone,
Please help me if anyone have the stock recovery image file for lu 6200 or a method to extract the stock recovery from the phone for flashing the recoveryfile only to get back to stock recovery instead of flashing the whole phone to stock and doing all the setup and configurations.
I searched everywhere but not found any yet for 6200
Click to expand...
Click to collapse
have u made recovery for ur phone? likely not, so other cant be used imho.

abuulala said:
have u made recovery for ur phone? likely not, so other cant be used imho.
Click to expand...
Click to collapse
I have not made the recovery, my question is how to extract the default stock recovery to .img file so I can replace the cmw recovery anytime I need or if any one already have extracted the stock recovery that is by default made by LG and put into the phone initially

hackenggr said:
I have not made the recovery, my question is how to extract the default stock recovery to .img file so I can replace the cmw recovery anytime I need or if any one already have extracted the stock recovery that is by default made by LG and put into the phone initially
Click to expand...
Click to collapse
u have to do flashing to load lg bootloader and with that bootloader installed u cant use cmw or modified rom. after alot of search, i have not found a way to boot into stock recovery once cmw is installed. u can instal rom mananger from playstore if ur phone is rooted than make a back up of ur rom on sd card plus all cmw recoveries provide backup but i found twrp recovery much better as it provide better ui and more functionality

abuulala said:
u have to do flashing to load lg bootloader and with that bootloader installed u cant use cmw or modified rom. after alot of search, i have not found a way to boot into stock recovery once cmw is installed. u can instal rom mananger from playstore if ur phone is rooted than make a back up of ur rom on sd card plus all cmw recoveries provide backup but i found twrp recovery much better as it provide better ui and more functionality
Click to expand...
Click to collapse
Thanks I will try the Rom Manager to see if it can backup the original bootloader and the recovery to flash it later instead of flashing the whole kdz and setup everything again

abuulala said:
u can instal rom mananger from playstore if ur phone is rooted than make a back up of ur rom on sd card plus all cmw recoveries provide backup but i found twrp recovery much better as it provide better ui and more functionality
Click to expand...
Click to collapse
I tried the rom manager but it can't extract the default recovery. However what I get now by searching for many hours that what I want is dumping the stock recovery and stock bootloader and combining into single .img file i.e bootl.img and recovery.img that I able to push back furing the normal running to get the stock recovery back and the bootloader without the ICE Engineer version showing after I flash the custom rom
twrp have the better ui but the one I found for 6200 have some problems I not remember but it had some issue mounting the system for wipe I think so I use the CMW instead both are good and perform the required function I suppose

hackenggr said:
I tried the rom manager but it can't extract the default recovery. However what I get now by searching for many hours that what I want is dumping the stock recovery and stock bootloader and combining into single .img file i.e bootl.img and recovery.img that I able to push back furing the normal running to get the stock recovery back and the bootloader without the ICE Engineer version showing after I flash the custom rom
twrp have the better ui but the one I found for 6200 have some problems I not remember but it had some issue mounting the system for wipe I think so I use the CMW instead both are good and perform the required function I suppose
Click to expand...
Click to collapse
excelent work done. what software u used? system extractor?

Thanks. I not able to dump the recovery and bootloader yet but I am researching to do it, will post the files if I able to pull that out finally for anyone else with the same question as me

hackenggr said:
Thanks. I not able to dump the recovery and bootloader yet but I am researching to do it, will post the files if I able to pull that out finally for anyone else with the same question as me
Click to expand...
Click to collapse
why not try system extracter 1.1! it can extract files from phone as well.

abuulala said:
why not try system extracter 1.1! it can extract files from phone as well.
Click to expand...
Click to collapse
I will check it out, thanks

abuulala said:
what software u used? system extractor?
Click to expand...
Click to collapse
Not used any software just the adb and command prompt using this guide
[GUIDE] Making Dump Files Out of Android Device Partitions

hackenggr said:
Not used any software just the adb and command prompt using this guide
[GUIDE] Making Dump Files Out of Android Device Partitions
Click to expand...
Click to collapse
system extracter is script to do all these work in one click.

abuulala said:
system extracter is script to do all these work in one click.
Click to expand...
Click to collapse
Yes I checked that it is just the script for extracting the data from the system partition not from other partitions Thanks btw

hackenggr said:
Yes I checked that it is just the script for extracting the data from the system partition not from other partitions Thanks btw
Click to expand...
Click to collapse
any progress/ success bro?

abuulala said:
any progress/ success bro?
Click to expand...
Click to collapse
yes able to extract the stock recovery and flashed it back was working fine for me however flashing the stock bootloader gives the secure boot error as it is not signed and LG have the signing key so only stock recovery can be flash back for now, untilll someone have the signed bootloader
including the recovery I extracted in the first post

hackenggr said:
yes able to extract the stock recovery and flashed it back was working fine for me however flashing the stock bootloader gives the secure boot error as it is not signed and LG have the signing key so only stock recovery can be flash back for now, untilll someone have the signed bootloader
including the recovery I extracted in the first post
Click to expand...
Click to collapse
great work done, i stumbled upon this site while googling, may b of some help it has all the colection of every possible itsi bitsi about lg lu6200.
http://translate.google.com/transla...PK577SD577&espv=210&es_sm=93&biw=1600&bih=799

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,

I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....

mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.

mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?

XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!

mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.

XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again

mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??

mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!

XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..

mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.

XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!

mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.

@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!

Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk

freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

Messed up with TWRP

Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!

rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.

Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?

rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.

Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.

Thanks all! I flashed the patched boot.img again and it seems to be working OK

OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!

rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:

Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?

rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:

Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?

rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/

rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse

Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary

rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.

Is Xposed worth having these days? Are people still actively developing useful mods?

rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:

I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.

Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.

rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.

FingerPrint and themes not working

I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..

iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.

mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?

iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.

mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..

iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008

mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%

iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.

mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.

iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.

mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.

iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.

mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685

iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)

mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method

iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions

mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.

iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.

Honor 7x BND-L24 (USA version) boot image error (bricked?), help required

I have Honor 7x BND-L24 (USA version) which is stuck at a screen which says:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Before this screen I had EMUI 5.1 with Android 7.0 installed version BND-L24C567B150CUSTC567D001 and TWRP custom recovery. I wanted to do OTA update so went and installed stock recovery and that somehow damaged my boot image. After factory reset it goes to the screen mentioned above. I can't even turn it off anymore.
I can still boot into fastboot mode, I can still go into recovery by holding both volume buttons and power button but the install always fails and brings me back to the same error screen. Is there any way to fix the boot image error?
Fastboot flashing does not work anymore and gives errors:
Code:
fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15170 KB)...
OKAY [ 0.395s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.406s
The bootloader is unlocked:
Code:
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
I have also seen in the forums that a dload method (creating a dload folder in the sd card and adding UPDATE.APP file into it) could be used to recover, but it always stops at 5% and fails. Maby I am doing it wrong because the stock ROM has two .zip files (update.zip and update_full_BND-L24_hw_usa.zip) and they both have the UPDATE.APP file in it. If someone could give me a guide on how to propertly use the dload method I would like to try it.
Any additional comments or solutions to try unbricking the phone will be appreciated. Thank you in advance.
P.S. after searching the xda forums it seems that for the dload method I would require a specific rom called the service ROM dload. I have tried searching for it but could only find it for BND-L21, if anyone has a service ROM for BND-L24C567 (USA version) please give me a link, I would like to try the dload method with it.
SOLVED !!!
Thread can be closed. If anyone need the solution on how to fix this issue just send me a message.

Hey how'd you fix it dude? I accidentally broke my boot image and im getting the same error as you did. the only thing i can do is use root shell in stock recovery. I'm trying to figure out how to flash twrp (Ice cream sandwich) to recovery2 but so far no luck.
Can you help me out?

Kr1msonReaper said:
Hey how'd you fix it dude? I accidentally broke my boot image and im getting the same error as you did. the only thing i can do is use root shell in stock recovery. I'm trying to figure out how to flash twrp (Ice cream sandwich) to recovery2 but so far no luck.
Can you help me out?
Click to expand...
Click to collapse
Is your bootloader unlocked and frp unlocked?
if yes then:
Get the stock recovery, boot, system and etc. by going into the OpenKirin website, there is a nice guide there in the support section on how to download and extract the stock recovery and boot images and etc.
Hold down the volume down key and plug in the usb cable. Use fastboot to flash in the stock recovery.
flash them using "fastboot flash" command with the adb and fasboot tool.
if not then:
download Chimera tool.
Pay for 3 day trial (~12 eur)
Do system restore in the application, worked for me. BND-L24 USA version, I now have EMUI 9.1.0 by installing BND-L21 9.1.0.141(C432E2) ROM using the Chimera tool.
Hope this helps.

DBxda7x said:
Is your bootloader unlocked and frp unlocked?
if yes then:
Get the stock recovery, boot, system and etc. by going into the OpenKirin website, there is a nice guide there in the support section on how to download and extract the stock recovery and boot images and etc.
Hold down the volume down key and plug in the usb cable. Use fastboot to flash in the stock recovery.
flash them using "fastboot flash" command with the adb and fasboot tool.
if not then:
download Chimera tool.
Pay for 3 day trial (~12 eur)
Do system restore in the application, worked for me. BND-L24 USA version, I now have EMUI 9.1.0 by installing BND-L21 9.1.0.141(C432E2) ROM using the Chimera tool.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the advice! I repeated the process you provided and so im not bricked, I have all the partitions of ice cream sandwich. The only problem is, the dload method and upgrade from sd card thing stops at 5% and when i use dload, it says image verification failed, because i was trying to upgrade to Nougat. I have the bootloader and stock recovery though. How did you upgrade to pie after doing this?
Also how is pie? maybe I'll install the pie rom for L21 and use english. I actually intall the AL10 once haha. It was horrible. Almost nothing worked and it tried to prevent booting into recovery or bootloader.
Thanks!
-Kr1msonReaper

Kr1msonReaper said:
Thanks for the advice! I repeated the process you provided and so im not bricked, I have all the partitions of ice cream sandwich. The only problem is, the dload method and upgrade from sd card thing stops at 5% and when i use dload, it says image verification failed, because i was trying to upgrade to Nougat. I have the bootloader and stock recovery though. How did you upgrade to pie after doing this?
Also how is pie? maybe I'll install the pie rom for L21 and use english. I actually intall the AL10 once haha. It was horrible. Almost nothing worked and it tried to prevent booting into recovery or bootloader.
Thanks!
-Kr1msonReaper
Click to expand...
Click to collapse
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!

DBxda7x said:
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for the advice! I'll try it soon, but as far as i know, from here in ice cream sandwich, it says image verification failed when flashing recovery and other partitions except not system or boot and others for some reason.
Actually I've previously installed RR and Lineage ROMs--maybe you forgot that they must not be flashed in TWRP? Anyway, thanks! Pie sounds like it must be the best option here. I'll go ahead and install it. Oh, and just so you know, the dload method can work on the Honor 7x but you have to flash a patched version of the recovery called BND-RECOVERY-NoCheck.img, except I only have the oreo one so it can't help me.
Thanks!
- Kr1msonReaper

DBxda7x said:
dload method does NOT work on this particular phone. I have tried it multiple times.
Best way is to find the ROM that works for your phone. I have tried a lot of the ROMs for this phone including all of the ones in the OpenKirin website, like the Ressurect, Lineage and etc. those do not work, it just bootloops. But the L21 worked perfectly, only issue is that you need to flash every partition (system, boot, recovery, ram_disk and etc.) and then do a factory reset. If you do not do a factory reset after the installation in will not boot.
Just go to Firmware finder, get EMUI 9.1 ROM, extract all .img files and flash them in using fastboot.
Good luck!
Click to expand...
Click to collapse
Hi, I have a BND-L34 (mate se) and could use some help. I'm not very good with rooting but I followed the directions found here
https://www.desinerd.co.in/how-to-huawei-mate-se-root-twrp-recovery/
which was mentioned from this XDA post about unlocking the bootloader and rooting
https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
So I was able to write the TWRP from the guide on the "recovery_ramdisk" but not the second partition like the guide mentioned. So if try to boot into TWRP I get an error 11 and error 2.
Phone appears to be working otherwise.
I suspect that if I were to ever factory reset the phone I would be in the same situation as you were. Could you tell me how you flashed the EMUI 9 files? Like what the commands were? thanks in advance.

teatimecrumpet said:
Hi, I have a BND-L34 (mate se) and could use some help. I'm not very good with rooting but I followed the directions found here
https://www.desinerd.co.in/how-to-huawei-mate-se-root-twrp-recovery/
which was mentioned from this XDA post about unlocking the bootloader and rooting
https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
So I was able to write the TWRP from the guide on the "recovery_ramdisk" but not the second partition like the guide mentioned. So if try to boot into TWRP I get an error 11 and error 2.
Phone appears to be working otherwise.
I suspect that if I were to ever factory reset the phone I would be in the same situation as you were. Could you tell me how you flashed the EMUI 9 files? Like what the commands were? thanks in advance.
Click to expand...
Click to collapse
@teatimecrumpet we have the same phones . . . .
Ok so, first, are you on Oreo or something lower? If you're on oreo I have the proper TWRP img for the ramdisk partition. If you flashed your TWRP to recovery but not recovery_ramdisk, I recommend reflashing the stock recovery and then flashing mine to ramdisk. But you shouldn't worry, you can't even factory reset anyway, if you've overwritten your recovery. So if you say your phone's fine now it should continue to work. I have not yet upgraded to Pie like @DBxda7x suggested, but I will soon.
In any case, here's the TWRP you must flash to the ramdisk.
-Kr1msonReaper
OreoTWRP: https://www.dropbox.com/s/ztzh7hejp3j9fuz/BND_twrp_true_Oreo.img?dl=0

Kr1msonReaper said:
@teatimecrumpet we have the same phones . . . .
Ok so, first, are you on Oreo or something lower? If you're on oreo I have the proper TWRP img for the ramdisk partition. If you flashed your TWRP to recovery but not recovery_ramdisk, I recommend reflashing the stock recovery and then flashing mine to ramdisk. But you shouldn't worry, you can't even factory reset anyway, if you've overwritten your recovery. So if you say your phone's fine now it should continue to work. I have not yet upgraded to Pie like @DBxda7x suggested, but I will soon.
In any case, here's the TWRP you must flash to the ramdisk.
-Kr1msonReaper
OreoTWRP: https://www.dropbox.com/s/ztzh7hejp3j9fuz/BND_twrp_true_Oreo.img?dl=0
Click to expand...
Click to collapse
Hey Krimson, thanks for the reply. It's been awhile since I had that error...it's a bit hazy. But I'm on oreo now and am trying to either downgrade back to nougat or try to flash oreo again. Reason being the phone was working fine but now my GPS doesn't really work and I can't pick up any satellites and I kind of need google maps to work.
I tried to use hisuite to upgrade to the newest firmware and downgrade to nougat but no luck it just boots to TWRP.
When I first rooted I know I flashed recovery and recovery2 (but recovery2 turned out to be erecovery on oreo...I remember it was a pain trying to figure out.)
I can't seem to find a simple guide to follow and like I said I'm not very good with this. Do you think you could give me the commands to either flash what you have or do the pie update? I'm totally fine going back to stock and then trying to root Nougat again.
Thanks!

teatimecrumpet said:
Hey Krimson, thanks for the reply. It's been awhile since I had that error...it's a bit hazy. But I'm on oreo now and am trying to either downgrade back to nougat or try to flash oreo again. Reason being the phone was working fine but now my GPS doesn't really work and I can't pick up any satellites and I kind of need google maps to work.
I tried to use hisuite to upgrade to the newest firmware and downgrade to nougat but no luck it just boots to TWRP.
When I first rooted I know I flashed recovery and recovery2 (but recovery2 turned out to be erecovery on oreo...I remember it was a pain trying to figure out.)
I can't seem to find a simple guide to follow and like I said I'm not very good with this. Do you think you could give me the commands to either flash what you have or do the pie update? I'm totally fine going back to stock and then trying to root Nougat again.
Thanks!
Click to expand...
Click to collapse
Hey, I know it's been a while, it is pretty hazy. I actually got into a situation where i bricked my phone from trying to downgrade from Pie to Nougat directly. Don't EVER do that. If you're on Oreo now, I know that there are some guides on how to use HWOTA to downgrade to nougat pretty easily. Here's the link:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649