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?
Related
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 ??
I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"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"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.
Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:
I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?
How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.
Thank you
Thank you sir, this helped me a lot.
recovery link is asking need access plzz help
My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??
hi,
my english is bad ^^'
ihave Problem,
critical error !
fastboot mode started
no recovery,no download mode
LG G2 D801 (T-Mobile)
I can not do Flash using LGFlashTool2014
I will explain the reason in detail:
Open twrp, then delete all the options accidentally:
(system + data+ internal storage + cache)
Image is for illustration only
{
"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"
}
help pls.. :'(
use this tool here
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
mid95 said:
use this tool here
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Click to expand...
Click to collapse
Thank you,
I did this nothing happened
But remain on this situation for a long time!
Selection:
4. Fixed Utility.
1. Fixed fastboot mode started.
Copy all files to the fastboot folder
I best and only method here to fix your phone is using srktool. I was in the exact same situation recently and i fixed using this method.
1) boot into qhsusb_bulk mode
2) connect the phone to your computer and start srktool
3) after that you will be able to boot into DOWNLOAD and RECOVERY mode
4) make sure that you phone is d801. To check, see the back side of your motherboard. It will be written there.
5) download your phone's version's tot and dll files and flash it.
farhanshaikh671 said:
I best and only method here to fix your phone is using srktool. I was in the exact same situation recently and i fixed using this method.
1) boot into qhsusb_bulk mode
2) connect the phone to your computer and start srktool
3) after that you will be able to boot into DOWNLOAD and RECOVERY mode
4) make sure that you phone is d801. To check, see the back side of your motherboard. It will be written there.
5) download your phone's version's tot and dll files and flash it.
Click to expand...
Click to collapse
I did this before, since they were showing me hard disks "15"
hi all,
The problem was solved and my phone was fixed ?
That's all I've done to fix the phone
1- Follow up on this subject until phase 9
https://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
2- Download SRK Tool 2.1 Then open it.. (Follow the image above) here
link Download SRK Tool 2.1 :
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Then:
3- After successful flash of images, remove battery connector and other connectors and reattach buttonsplate.
4- After attaching buttons plate,check your device going into download mode, and use flash tool to flash stock rom..
-----------------------------------
Thanks mid95 + farhanshaikh671 for the replies ?
+
thanks george7565 for the subject and explanation ?
thanks somboons for the program ?
Finally, thank you XDA for the everything ❤
***Even tho I restart it, it'll go back to fastboot. What should I do?
I dont know how to fix this o
***Even tho I restart it thru ps :|
View attachment 1479060
I tried booting on boot.img, but error
also twrp, error also.
I tried ".\fastboot reboot" but still going back to fastboot
View attachment 1479059
Re-flash Stock ROM to get rid off of all the mods you have applied.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all the mods you have applied.
Click to expand...
Click to collapse
Can I have the best tutorial youve got? Im pretty noob bout' this. Sorry
{
"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"
}
Restarted but still going back to fastboot :|
Luciferr. said:
***Even tho I restart it, it'll go back to fastboot. What should I do?
I dont know how to fix this o
***Even tho I restart it thru ps :|
View attachment 1479060
I tried booting on boot.img, but error
also twrp, error also.
I tried ".\fastboot reboot" but still going back to fastboot
View attachment 1479059
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
kenchan1505 said:
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
Click to expand...
Click to collapse
Hey,
I'm in the same boat, how exactly do you get those images? The stock rom doesn't include the recovery.img
I'm kind of pulling my hair out, I'm now permanently stuck in fastboot
Hi
my P10 lite crash suddenly now loop in this screen
{
"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"
}
can't boot to system and recovery, eRecovery only can boot to fastboot mode please help what can i do?
Huawei P10 lite (was-lx1a)
Okay first of all explain what you were doing before the problem occurred and how did this happen?
LesterDMolester said:
Okay first of all explain what you were doing before the problem occurred and how did this happen?
Click to expand...
Click to collapse
I was changing the screen for Phone and after the change I used the device normally and during use it suddenly turned off and then the mentioned problem started,
but sometimes a similar problem occurred. Sometimes if battery dead and restart device , the same problem occurs and its solution is to enter the recovery, now I can’t enter the recovery at all and I tried to reinstall it from fastboot
mohammed h.Gamer said:
I was changing the screen for Phone and after the change I used the device normally and during use it suddenly turned off and then the mentioned problem started,
but sometimes a similar problem occurred. Sometimes if battery dead and restart device , the same problem occurs and its solution is to enter the recovery, now I can’t enter the recovery at all and I tried to reinstall it from fastboot
Click to expand...
Click to collapse
does eRecovery work at all?
Can you try downloading the firmware on to your pc than flashing it using dload method?
LesterDMolester said:
does eRecovery work at all?
Can you try downloading the firmware on to your pc than flashing it using dload method?
Click to expand...
Click to collapse
Can,t enter to erecovery
and yes I,m try reinstall I, m use custom rom and nothing
flash twrp put the dload folder with firmware inside internal storage and flash nocheck recovery and install the firmware using dload method
LesterDMolester said:
flash twrp put the dload folder with firmware inside internal storage and flash nocheck recovery and install the firmware using dload method
Click to expand...
Click to collapse
Try flash twrp but can't enter
I will explain the problem to you again to clarify
I try flash twrp More than once Every time I try to enter recovery, it reboots over and over again
And try enter erecovery to restore but it refuses to enter and restarts again and again until the battery dead when charging, it does not enter charging mode, only restarts
LesterDMolester said:
flash twrp put the dload folder with firmware inside internal storage and flash nocheck recovery and install the firmware using dload method
Click to expand...
Click to collapse
I've been busy lately and I didn't know the way, could you explain it to me step by step?
I couldn't believe what was the cause of the problem. It was a very, very silly problem, The reason is due to the type of screen that was installed recently And it was showing what was in it fastboot this code:
AP_S_PMU 144
ocp_ldo17 ocp_ldo31
This problem has been resolved by returning the old screen And it works normally
I do not believe this
I am very, very sorry for the inconvenience, and thank you for the help. I am grateful
This problem came while I was changing screen. after I finished from installing the screen I test it and everything it's ok after that suddenly it stop working and bootloop and can't boot and flash anything except fastboot
and shows in the fastboot this code:
AP_S_PMU 144
ocp_ldo17 ocp_ldo31
I search for this and clearly because of the new screen
Solve the problem reinstall the old screen and boot normally