Zenfone A500KL csc mode only invalid boot image - Zenfone 5 Q&A, Help & Troubleshooting

Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards

I have the same problem...
I have tried everything and I am still stuck with csc mode.
Please help
Best!
jaza-g said:
Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
Click to expand...
Click to collapse

Do you happen to be QDLOAD mode or QHSUSB? My experience working with SD400 devices, you need to nuke one of your partition to be able entering QDLOAD mode.
edit : For some reason I believe the CSC mode you got into is actually fastboot mode. Did you tried running any fastboot command? If fastboot cant detect, manually replace csc driver in device manager with fastboot driver.

Can you provide a picture of the error codes ?

http://imgur.com/QQ7OxDZ
like this i believe?Im having the same problem

Hi All,
If you have CSC MODE and ERROR: INVALID BOOT IMAGE
I found a solution, that is worked for me.
You don't have to turn on the USB debugging on your phone, connect to the PC, etc.
Steps:
1. Download recovery.img from Official Stock ROM (e.g. WW_12.4.5.58)
1.1. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
2. Download Official Firmware from asus.com/Phone/ZenFone_5_A500KL/HelpDesk_Download/ (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
2.1. Read the Description!!!
2.2. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
3. Copy the recovery.img and the <firmware>.zip files to the root of external SD card
4. Power off your device
5. Simultanously push the Power + Volume Down button and waiting for the choice screen
5.1. Choice screen:
1. Enter SD download mode
2. Exit update mode
6. Choose the "1. Enter SD download mode"
7. Choose the "apply update from external storage"
8. Choose the the <firmware>.zip file (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
9. Waiting for the installation finished
10. Choose the "reboot system now"
Best Regards,
R.

invalid boot image means doesn't go to boot loader, how can i update from sd card then ?

Steve Al-Mousa said:
invalid boot image means doesn't go to boot loader, how can i update from sd card then ?
Click to expand...
Click to collapse
boot doesnt mean bootloader...

thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks

Try this
https://forum.xda-developers.com/zenfone-5/general/stock-a500kl-zenfone-5-lte-t3303475

Did you ever get this sorted? I have the same issue......
Steve Al-Mousa said:
thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks
Click to expand...
Click to collapse

Dagk66 said:
Did you ever get this sorted? I have the same issue......
Click to expand...
Click to collapse
I have been informed by the stupid Asus Thailand that the main board should be changed

Related

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

[Guide] Fix for boot-loop and bricked Honor 8 (probably others too)

The reason I'm making this thread is because I was trying to root my Honor 8 and things just didn't work out in TWRP. Rebooted my phone and I realized I had bricked it since it would not boot after 10 minutes. Solutions seem to be scattered throughout different threads so here's guide for when you're stuck in a boot loop or you bricked your Honor 8.
What you'll need:
1. The firmware currently you are on. @Coolyou posted a guide for a firmware finder. Here is the post.
2. SD Card
What to do:
Step 1.
Download the correct firmware. It will be a .zip file.
Step 2.
Create a folder called dload in the root of your SD card, not your internal storage. Copy the .zip file the folder and unzip it or unzip it else where and copy the content into the dload folder
Step 3.
Power off Honor 8 (if possible, sometimes it'll auto boot up when forced shutdown)
Step 4.
Make sure your device is not plugged into a computer as it will load into something else.
Hold Vol+ & Vol- & Power. It will being to install the firmware from the dload folder if done correctly. If it instantly fails that means you downloaded the incorrect firmware the device is already one.
You're done! However, if your device does not go past the startup logo within 3 minutes proceed to step 5.
Step 5 is probably necessary as everytime I've bricked my device, I've had to do the next step.
Step 5.
Power off. Hold power and Vol+. Once in Recovery mode (not eRecovery), clear cache and format your device. Once done, reboot.
Ta-da, you're device is now back to normal.
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Let go off the power button after the first vibration. Also make sure your phone is not plugged to a pc. With pc connected it boots into eRecovery instead of recovery. Good luck!
Edit:Also the guide does not make it 100% specific but the dload folder on the sd card needs to have the update.app file right inside it. If the structure is sd\dload\folder\update.app it also won't work.
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
i have same problem, you can fix this? help me please
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
thekubiaks said:
Add me to the list, two soft bricked Honor 8's. Once I made the jump to Nougat and installed the Nougat version of TWRP 3.0.1-1, I started having issues. So, I tried to downgrade to FRD-L04C567B150 from FRD-L04C567B320 and had big problems installing B150. Always getting unable to load /data Has to be something to do with the new data structure of Nougat I have a copy of the full stock rom of B150 and B162 and have wiped the phone. I am trying to dload full B150 from SDcard but will fail immediately and says Wrong Version. I can get to fastboot and ADB. I also tried custom ROMs but that wont work because they need the basic Nougat structure to work from. I don't have a clue how to proceed seeing that I can't even wipe the phone and install a Full stock ROM B150 or B162??
Any help would be extremely appreciated.
Click to expand...
Click to collapse
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Hi, my device is still not booting up after installing the matching dload firmware on my device from the honor 8 website (FRD-L09).
Is there still anything I can do to maybe get this fixed?
I created a nandroid backup of all partitions that I were able to back up, but even rolling back all partitions did not make it boot again.
Sadly, I am not able to get the device into e.g. fastboot mode anymore because it is not booting anymore and therefore cant get an adb shell on it.
I can still enter recovery mode, but when trying to boot it just stays at the blue screen with the white "honor" text after the short boot animation with the 3d text
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Lorog said:
Hi,
my phone keeps entering eRecovery and my PC does not recognize it so please how can I access it to install files. I think I have installed a wrong boot.img and recovery.img version of firmware.
Please I need help.
Thanks
Click to expand...
Click to collapse
Same here on a Note 8 did you find a solution?
thekubiaks said:
UPDATE : It freaking worked!!! After an entire weekend of hair pulling and going way deep into Nougat and MM trying to find the cause, it was a simple Full ROM B162 that I dloaded and three fingered from the SD card (of course it has to be the exact ROM for your phone such as FRD-L04C567B###). WOW, two phones are back. I'll stay at FRD-L04C567B162 and like it.
Lesson Learned: When you try to do an eRecovery and the Honor 8 starts downloading new firmware from the internet it creates a new folder on the sd card called something like HwOC. In that folder is stored the new firmware that erecover plans to use on the recovery. IF this HwOC folder is present and you try to do a Full ROM three finger install with the B150 or B162 firmware in the dload folder, the recovery will stop and say something like invalid version. To fix, remove the HwOC folder so that only dload is present, now do the three finger start and the firmware will install without error. Worked twice for me.
Click to expand...
Click to collapse
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
nickp22127 said:
Do you have the link for the b162 full firmware?
edit:
also what recovery did you have installed when you did this?
Click to expand...
Click to collapse
Its erecovery
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
alec_trikki said:
i have same problem!
i can't reboot in download mode: it vibrates twice and reboot in blue screen always, even leaving power button after first vibration.
How can i fix this?
please help..!
Click to expand...
Click to collapse
tiagoesbastos said:
i have same problem, you can fix this? help me please
Click to expand...
Click to collapse
i have the same pblm...can u tell how did u managed to solve it???
oops, wrong thread
abbassbhai said:
i have the same pblm...how did u both managed to boot it then??
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
i have the same pblm...can u tell how did u managed to solve it???
Click to expand...
Click to collapse
Do you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Did you find a solution? I have the same problem!
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi, I have the exact same problem. Have you managed to fix it?
Same problems as other people above, couldn't load any recovery. Anyone can help us out?
Rakeen70210 said:
Unfortunately, I cant seem to get to the part where it detects my dload folder and installs from the UPDATE.APP file. My phone keeps auto restarting whenever I try to turn off, and since bootloader is locked, I cant flash any images. Every time I hold down Vol+, Vol-, and power button the phone just vibrates twice and goes to the blue honor boot logo. I have successfully managed to get to the Fastboot menu by holding down Vol- and power button, but this menu is useless as bootloader is locked. Is there anything I can do?
Click to expand...
Click to collapse
Hi even I have the same problem with Honor 8 Pro.. Did you get any solution??
Hi even I have the same problem with Honor 8 Did you get any solution??

Can't enter fastboot mode

Hello
I bricked my M3 and tried using Huawei Tool to unbrick it.
I followed all the instructions, and realized that the bootloader needed to be unlocked. I unlocked it and since then, I can't enter Fastboot mode.
I've tried pressing Vol - and power and it's stuck in a loop where it tells me
"Your device has been unlocked...
Your device is booting now"
And then it doesn't move.
Am I screwed?
Thanks a bunch
My device is a BTV-W09
I saw many of the same symptoms and I showed the same symptoms.
At this time, there seems to be no recovery method.
Same symptons as you. I guess the fastboot partition wiped itself after unlocking so there's no way else to get in anymore.
Same here: unlocked bootloader than flashed TWRP (maybe not the right one) and now the TABLET power ups for only 3 seconds with the message "Your device has been unlocked...Your device is booting now" and then it shuts down!!
Anyone could suggest me how can I return to fastboot mode to try to relock the bootloader?
Thank you very much!!!
(I tried VOLDOWN+POWER / VOLUP+POWER with and without USB cable connected with the PC but after 3 seconds of warning message it shuts down!!)
Anyone could help?
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
ETOSoft said:
I've found a possible solution: pressing BOTH VOLUME UP AND DOWN and POWER the tablet search for a system update inside SD CARD. I've tried with the only one update I've found online and in fact the system waits few seconds with a blank screen before rebooting again. This is a different behaviour from the usual brick loop.
I think that the update found in the SD card isn't compatible with my tablet.
Anyone knows where can I find the right or compatibile upload->UPDATE.APP for CPN-W09 model? I think this could be the only one way to restore a bricked recovery partition that cause this boot loop.
THANKS!
Click to expand...
Click to collapse
Volume up + Hold Power for 3-4 Seconds during the locked boot. When the screen goes blank let go of both and it should go into recovery like it was supposed to. You have to let go though at the right time. I unbricked some op phones doing the same thing but it's been awhile.

Mega Bricked 7X - Calling out all Senior/Pros for HELP!!

HI, I will get right to the point. My phone is Honor 7x (BND-AL10C675 INDIAN) I screwed it up.
Now, the fastboot or recovery or E recovery nothing works!!
There is only one screen which keeps coming in a loop rebooting with a vibration
It says " ERROR MODE"
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
It keeps rebooting and the phone doesn't even turn off. I tried the download mode (Volume UP & Down Power button, SAME SCREEN comes up)
Let me know if you want me to write a detailed version of how I got here or ask any specific questions.
Now, all I need is at least FASTBOOT so I can do something about it. Is there anyone who can help? I hope SOME PRO OR A GEEK is able to solve this issue magically. I just can't tell you what I'm going through.
UPDATE:
As Christo31 requested and maybe it's useful for other people to help me out. Here is what I did. It's a real long story!!
I have Honor 7x (BND-AL10C675 INDIAN) I had unlocked bootloader and twrp and I was on emui 8 beta which I flashed manually using one of the tutorials here on the forum. One day, I decided to get back to stock as I was stuck in emui 8 beta and no OTA updates so I downloaded the emui 8 stable rom from firmware finder and put it in sd card "dload" folder. Now, for this method to work, we need to relock bootloader and flash stock recovery which I did and it completely wiped everything out.
Now, the "dload" method fails at 5% every time. I tried different roms for this very model but no it doesn't work. (Also, my build no. was stuck at B141 for a long time no matter what rom I changed : Yes, this is stupid, I should have fixed it first) Maybe that's why the "dload" method doesn't work.
So, in this forum I saw some with similar issue but somewhat different " Frp locked & bootloader unlocked" and I was told that the DC phoenix software might fix this and I bought some credits and used the software. Here's what I discovered
My observations with the software:
* I put the phone in fastboot and downloaded the update.app full Ota (same one emui stable) and tried to flash. The software flash well ok as it says "the software is written" but the phone doesn't boot and goes directly into the recovery mode and again the bootloader and frp are locked.
*Here, I noticed that it shows something like "opening backdoor" and then the Bootloader status goes to red and says "UNLOCKED" it means it was definitely doing something so the next I repeated the same process but as soon as the phone was "UNLOCKED", I pulled the usb cable out and I kept my command ready and tried "fastboot flash recovery_ramdisk recovery.img" and guess what it flashed that twrp file and I could see in the command line that it went "okay" so I immediately booted to recovery but again the stock recovery comes up. Also, I tried system.img also it flashes fine but phone doesn't boot. Same recovery.
REMEMBER: THE ABOVE STEPS MAY WORK FOR PEOPLE WHO HAVE UNLOCKED BOOTLOADER BUT FRP LOCKED. IN MY CASE BOTH ARE LOCKED SO THAT'S THE DIFFERENCE.
* I tried another update.app I guess it's BNDL22.ZIP or something and this time the software was trying to flash in "upgrade mode" and somehow the recovery was broke. There was some "ERROR MODE" basically the recovery was broke. I didn't care much. Although flashing another update.app would have fixed it.
* The next step I tried after a lot of trial & error for about 1.5 days. This time I did the same when the bootloader was unlocked, I pulled the cable and tried the command "fastboot oem unlock unlock code" ( I should have got this idea before, I mean it's a mess guys, I didn't sleep for too long) and I was shocked to see that it showed the options "Unlocked bootloader yes or no" and I clicked "yes" and I jumped hoping that it's over but... I ended up with 'ERROR MODE' which I described above.
* I feel, because the recovery was broken, it ended up in error mode. Just imagine if my recovery was fine and then I tried this command then it would have erased everything and maybe I might have been presented with fastboot screen with both "frp & bootloader Unlcock" or at least 'bootloader unlock" in either way, I could have flashed a 'system.img' and get into settings and BEATH THE HELL OUT OF THAT "ENABLE OEM UNLOCK' in settings. The rest you know.
I wrote this not just because someone might help me but because a lot of posts on this forum really helped me a lot and posts like these can help a lot of people down the road.
Now, my phone is still in the same loop. Reboot, Honor logo, Error mode...REPEAT
I heard that once the phone drains down completely, we may get back fastboot. Fingers crossed. Sadly, I have Mac so I borrowed windows laptop for this purpose from a friend. This is the last day and I guess I'm going to put it on sale and sell it as a scrap or something for display and stuff.
How much does motherboard cost? anyone any ideas? if it's below 4K or about 80$ then I might go for the repair if nothing works!!
I'm going to update on this very soon. Le'ts hope for a miracle. Either way my HONOR 7X IS A LEGEND.
UPDATE :
After waiting for hours, my phone got discharged and I curiously plugged in the phone pressing "volume down" button OR power + volume and all other types of combinations but the phone just goes to the same "ERROR MODE' and keeps going in the same loop.
So, I really hate Huawei for not providing stock firmware or some type of recovery for people like me to get back to stock. For example : Xiaomi has that fastboot ROMS which you can easily flash in EDL mode no matter what happens to you and of course some other ways to recovery the bricked phones.
The Huawei E recovery?? What the **** is it? Does it ever work? It's some kind of a joke. The hisuite is again **** It says 'My model is not supported" and it only showed me two very older and ancient models that are supported for recovery.
I'm not expecting warranty but at least they should give the service for the customer. Did I tell you that this phone was in Service centre for three days when it had FASTBOOT, RECOVERY, E RECOVERY working. They could n't fix it in 3 days so I rushed them to get my phone back hoping that I would recover it with the above method.
Now, I got the Redmi Note 5 Pro and my 7X is a dead brick and I'll try selling it as scrap for display etc...
Finally, I really love the XDA forums and the friendly members who are very helping and so empathetic. Thanks guys, you are the best
I'm not leaving. I'll see you on the other side. I mean, the Redmi Note 5 pro development. Keep hustling
You need to tell us what you did exactly first for any help
Thetpcguy said:
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
Click to expand...
Click to collapse
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
azerty11 said:
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
Click to expand...
Click to collapse
Hi, thanks for your help but the phone doesn't turn off. it just keeps rebooting and there is honor logo and then error mode and then phone reboots and the same cycle. I tried what you said also with other possible things but I guess I need to let the battery drain out completely as some people said it worked for them. It's almost 9 hours and it's still not drained (it was on full charge) anyway Fingers Crossed!!
christo31 said:
You need to tell us what you did exactly first for any help
Click to expand...
Click to collapse
HI, I Updated the post in full details. I hope my phone is rescued.
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
vaasu_g_wills said:
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
Click to expand...
Click to collapse
It didn't work out. It only boots in error mode and keeps going in a loop.
Thetpcguy said:
It didn't work out. It only boots in error mode and keeps going in a loop.
Click to expand...
Click to collapse
Did you try huawie suite system recovery??
vaasu_g_wills said:
Did you try huawie suite system recovery??
Click to expand...
Click to collapse
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Thetpcguy said:
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Click to expand...
Click to collapse
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
---------- Post added at 10:59 PM ---------- Previous post was at 10:27 PM ----------
[/COLOR]Follow this steps.
1. Just flash with Dc phoenix
3 extract two update. App with huwai firmware extractor.
4. Check the log of dc phoix. Check which files are not flashed. By comparing with extracted files You will observe some files are not flashed. (some files are not in log of dc phoinix) Like Vendor.img product.img cust.img etc.. Note down which imgs are not flashed..
5. Now use multitool and go to unbrick option. There will be option of flashing around 5 img. Flash the 5 imgs. You will get this 5 img from extracting Update.app
6.then your phone will be working but not perfectly. Flash TWRP with fastboot.
7. Aftee flashing TWRP flash all other imgs which were not flashed by dc phoenix.
Then boot. Your phone must be good.
And again if you want then re flash with HWOTA tool. Your phone will be running now.
mrmazak said:
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
Click to expand...
Click to collapse
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Thetpcguy said:
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Click to expand...
Click to collapse
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
mrmazak said:
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
Click to expand...
Click to collapse
I tried that also. Power+Volume UP+Volume Down to get into download mode but it just goes into that "ERROR MODE'
Normally, it should but maybe because I broke my stock recovery also and then tried to unlock the bootloader when the frp was locked with the DC phoenix trick (Pulling out the plug) that it's really screwed up beyond all this. Let me know if you want me to post pics or maybe if the clips canoe uploaded here, I will make short clip with what's happening. I guess I need some factory or manufacturer level stuff or I need to replace the motherboard. BTW the local guy told me it costs 8K INR which is around 125-130 USD which I'm not willing to spend. I got Redmi Note 5 Pro and I'll probably never ever buy Huawei phones ever.
ANYONE HERE WHO CAN DONATE THE MOTHERBOARD, PLEASE PM ME:laugh:

Need help installing twrp with odin

first of all sorry for my english
i have a Samsung Galaxy Tab A 8.0, and of course like anyone else in this forum, i want to have stock android installed on my device. I have once tried this before with my Sony Xperia Z and it worked flawlessly. So that means that i have a little experience on the process. I approach it using the common method which is using fastboot and adb command. But later i found out that i can install twrp with a software called Odin. Here's where the problem came. I followed the instructions on the net, but the feedback i got was something like "bla3 installing recovery bla3 nand writting! bla3 resetting bla3 res ok! bla3 PASS!" The status box always shows "RESET!" for a few minutes then "PASS!" But twrp still isnt installed. I think that the software tried to install it but then it resets it back to default... Please someone help me trough this
my device condition
- missing oem unlock
- cant get fastboot to work (didn't detect the device in device manager while in fastboot)
- not sure if it's unlocked or not
- cant get into stock recovery after tried to install twrp with odin ( stuck at samsung logo with some writings on the top left corner)
piece of potato said:
first of all sorry for my english
i have a Samsung Galaxy Tab A 8.0, and of course like anyone else in this forum, i want to have stock android installed on my device. I have once tried this before with my Sony Xperia Z and it worked flawlessly. So that means that i have a little experience on the process. I approach it using the common method which is using fastboot and adb command. But later i found out that i can install twrp with a software called Odin. Here's where the problem came. I followed the instructions on the net, but the feedback i got was something like "bla3 installing recovery bla3 nand writting! bla3 resetting bla3 res ok! bla3 PASS!" The status box always shows "RESET!" for a few minutes then "PASS!" But twrp still isnt installed. I think that the software tried to install it but then it resets it back to default... Please someone help me trough this
my device condition
- missing oem unlock
- cant get fastboot to work (didn't detect the device in device manager while in fastboot)
- not sure if it's unlocked or not
- cant get into stock recovery after tried to install twrp with odin ( stuck at samsung logo with some writings on the top left corner)
Click to expand...
Click to collapse
Before you install twrp, disable auto restart option in Odin. When you have done, do Power + Home + Volume Up to make it shutdown and immediately to to recovery (if not shutdown do volume down then when screen shuts immediately put up).
The system removes twrp so that's why it happens.
diegopietro said:
Before you install twrp, disable auto restart option in Odin. When you have done, do Power + Home + Volume Up to make it shutdown and immediately to to recovery (if not shutdown do volume down then when screen shuts immediately put up).
The system removes twrp so that's why it happens.
Click to expand...
Click to collapse
First of all, thank you for replying, but that didn't change anything. I made sure that I followed the instruction on the web including untick auto reboot. But I realized something yesterday, HOW does the software manage to "communicate" with the tablet??? Because when I clicked start, there's something happening on the tablet screen, so that means that they had successfully communicated to each other in fastboot right??? But when I used the manual way, my pc can't communicate with my tablet in fastboot mode, because when I typed in "fastboot devices" i got no result and when I tried "fastboot flash recovery" it just says "waiting for device" so that means that there's something wrong with my driver right? device manager looks fine and i made sure that the driver is installed (samsung usb driver) but it still won't do anything when i typed in any fastboot command. But somehow Odin managed to communicate with my tablet??? idk why
PLSSSS HELP MEEEEEE

Categories

Resources