Database Users

BootLoop - ZE500KL

Hi friends...
First of all, I'm sorry for my bad English.
So, my phone went to bootloop out of nowhere, no updates caused it, no root method either, just all the suddent... Went to bootloop.
Via recovery mode, I erase all user data & cache = Still BootLoop / Did not work.
Downloaded the firmware from the Asus website (concerning my model of the zenfone), also drivers & tools. So via adb installed it 100% = Still BootLoop / Did no work.
So, if anyone could be facing the same issue and solve it somehow, please let me know the way.
I've seen that this problem is a frequently issue in this phones, but, I haven't seen the solution for this Zenfone Laser 2 ZE500KL specifically.
Thanks in advance.

Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.

Solved!
M Huzaifah said:
Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.
Click to expand...
Click to collapse
Thanks buddy, it worked! did not have a clue that the ZE500KL carry that sd slot. LOL

Did not work for me

M Huzaifah said:
Place your downloaded full firmware in external sd card. Apply update through sd card in stock recovery.
Click to expand...
Click to collapse
hello
i have done something and finally removed the OS. now it says NO OS FOUND.
i have TWRP. i dont have access to fastboot mode.
when i flash a stock rom it says it is for ww phones. this phone is asus zooe- it is making this error.
do you know why i am unable to access to fastboot mode?
i have made some modifications to the updater script then successfully flashed but when i reboot stuck at the logo.
how to fix his please help me

stuck with no recovery mode
i need some help. my phone asus zenfone 2 laser ze500kl cant get into recovery mode and stuck at the asus logo screen. Cant detect the phone throw ADB in pc
Can someone help me?
Thanks

ricardosanto said:
i need some help. my phone asus zenfone 2 laser ze500kl cant get into recovery mode and stuck at the asus logo screen. Cant detect the phone throw ADB in pc
Can someone help me?
Thanks
Click to expand...
Click to collapse
Have u tried Fastboot mode.
Try
"fastboot devices"
If it does read ur device..Follow these steps
1.flash TWRP recovery
2.flash STOCK ROM
If flash fails open "update script" and remove "aseert" lines
DONE

stuck ze500kl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
akhil850 said:
Have u tried Fastboot mode.
Try
"fastboot devices"
If it does read ur device..Follow these steps
1.flash TWRP recovery
2.flash STOCK ROM
If flash fails open "update script" and remove "asert" line
DONE
Click to expand...
Click to collapse
It doesn't detect/read my device.
How to make it.i enter fastboot mode on the phone it detects it like kedacom device on the device manager in the pc but in adb nothing.
What to do?

Cannot restore system, stuck on bootloop

Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm kind of new to this.
Greedings
Kynie

Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.

How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?

In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair

Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.

Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk

I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...

Hello do you have find à solution ??

Mi A1 Bootloop after ota update and Locked Bootloader

Hi,
I've installed an ota update and the device didn't boot... it is stuck in a bootloop....
When i try to flash via fastboot, it appears an error saying that the device is locked ant cennot erase...
via fastboot oem unlock i get the error message: Remote: oem unlock is not allowed
via MiUnlocker the unlock gets to de 50% and gives an error and on its logs it says: Remote: oem unlock is not allowed
I tryed to flash TWRP with command fastboot flash recovery but the error is the same: remote: partition flashing is not allowed
Can anyone help me please??
I'm stuck on the bootloop i can't go to setting - developer - allow oem unlock option!!

Have you tried doing a Factory Reset from stock recovery?

This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?

Parnas72 said:
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Click to expand...
Click to collapse
How can i do that?

Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!

Tepig said:
Have you tried doing a Factory Reset from stock recovery?
Click to expand...
Click to collapse
No recovery.. i get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Typhus_ said:
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Click to expand...
Click to collapse
Obrigado!
I'll try it now!!

xistolas said:
No recovery.. i get this:
Click to expand...
Click to collapse
Actually you have a recovery. You need to long press the power button and, afterwards (not at the same time), press the volume + button. You'll see that all options will appear.

xistolas said:
How can i do that?
Click to expand...
Click to collapse
fastboot getvar current-slot
to show the current slot,
fastboot --set_active=a or fastboot --set_active=b
to change it.

xistolas said:
Obrigado!
I'll try it now!!
Click to expand...
Click to collapse
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------
akashavel said:
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
Click to expand...
Click to collapse
follow from step 6 to end in below link
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624

Problem with recovey installation

Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

viru78 said:
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.View attachment 5294485View attachment 5294487
Click to expand...
Click to collapse
Before flashing, try: fastboot devices
In Developer options, is OEM unlocking and ADB debugging enabled?
If fastboot devices does not recognize device, try another USB cable or uninstall USB drivers and try again

Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.

Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img

viru78 said:
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Click to expand...
Click to collapse
Seems that something is wrong with your USB driver on the PC - adb devices works but fastboot devices does not (where Bootloader is unlocked and OEM Unlocking enabled)
Try uninstalling the USB driver(s) on the PC or try another PC

yaro666 said:
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
Click to expand...
Click to collapse
Or copy the (twrp) img file right into the ADB folder on the PC, and go with CMD into the ADB folder before running adb/fastboot commands
Then no paths are needed, just like:
fastboot flash recovery twrp.img
But that will not help him as long as fastboot devices fails

I thought about address length, sometimes adb has problem with it, worth a try

fixed, thanks for your answers, the problem was the laptop and drivers, i have had used other pc and install without problems.

Question Help! Stuck in fastboot mode can't do anything

So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/

misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?

-

i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??

xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?

Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/

xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader

What if have you tried to boot into another slot fastboot --active-slot

layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?

xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best

layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?

Eventually I was able to change the active slot but sadly still looping.

yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.

Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?

If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?

I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked

Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.

I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works

xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system