Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Kamen911 said:
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Click to expand...
Click to collapse
same problem. stuck on bootloop on stock recovery
https://www.youtube.com/watch?v=cDRsEsI0qBY
Have you guys tried this method, yet?
Related
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you
hi guys....
i have a problem with my phone. (Zenfone 2 Laser ZE601KL)
the problem is i got update and when the upodate start i cancel it.
now my phone is booting directly to the recovery mode. even i make a wipe of data and cache partition but without result.
i try to flash the officiel firmware, using adb and fasboot.
adb detect my devices but cant connect to it , it show:::::
C:\Users\Poste 8\Desktop\dv>adb shell
error: closed
and fastboot no response
please help me
If you still have stock recovery, copy the official firmware to your external sd card. Boot to your recovery and apply update from sd card then find your officia firmware. Dont cancel update next time.
today i want to share my sad story with u guys , i got my phone huawe mla-al10 , i flash custom rom lineage os 13.1 from xda for huawei can-11 then it got bootloop , before this i succesfully install it without bootloop , so i decide to reset , then i go to the recovery , idk how my recovery become the stock one ,then i click format data , suddenly its stuck at 61% then keep reboot , i open fastboot then get frp locked , im start panic , then i do a research how to get rid frp locked , they said relock the bootloader , then i relock booatlader , haa its getting more worse , now icant even go to fastboot or update mood , its only goes to factory reset lowlevel.... then screen becomes black with blue led , i connect to pc , i found hs-usb diagnostic 9006 ( com 3 ) thats mean i can unbrick only with 1 way , with Snapdragoon flashtool , but i cant find nowhere for the firmware that make to unbrick using flashtool for my devices , hmmm im so sad right now , is there any way i can make my own flashtool file for snapdragon flashtool ? i hope i can fix this as soon as possible
If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new
virusdunil said:
If ADB is working,just flash your original (firmware) RECOVERY,BOOT and SYSTEM.img from the update.app zip file...after flashing those 3 img file,just reboot via adb...fastboot reboot
Phone should be like new
Click to expand...
Click to collapse
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee
shazlieyazizan1 said:
to make adb working i need to enable usb debugging bla4 but my phone is totally dead , no fastboot nothing i can do except go to edl modee
Click to expand...
Click to collapse
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?
abuapka said:
same problem adb is also not working did you find any solution?
I am having a problem i didnt do anything with my phone its huawei nova plus just 1 or 2 day ago open the boxed and try to update it using firmware finder app after downloading the full ota phone automatically restart and stuck on installing update 5% and its still on boot loop am not able to flash any firmware using sd card or update.app just because it always failed on 5 % even though am not able to wipe factory/reset it also failing. Can you guys please help me? to solve the problem?
Click to expand...
Click to collapse
try get correct model from huawei updater finder ..
if dload method not work then try to go to fastboot mode by tgis way >> Turn off your mobile and just click and hold on DOWN vol then connect it with usb it should work !
Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?
Glad you got it going :good:
I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks
1st Try to Flash with latest RAW,
If fail, Try with CSC
If still fail try with EDL File (Unbrick) - ZE552KL Libra_QFIL_8953_01020_20170714_Aboot.7z
eemmiirr said:
I was using Lineage OS on my Asus Zenfone 3 (ZE552KL). When my battery was empty it's stucks on fastboot mode. Got stuck unlocking my bootloader via adb. Phone is detecting in ADB. The phone is getting stuck at ASUS logo and I cant boot to recovery either. It does get detected by fastboot but nothing more. I have tried :-
(1) It only seems unlocked boot screen and the choices is start volume up countinue boot but isn't any happening.
(2) I used Asus flashtool (various versions- 1.0.45). The latest one says battery is -1% while the earlier version returns various errors including "ftp request server log access is denied" and "failed to write partition".
(3) I have (seemingly) couldn't recovery and boot images.
(4) I flash factory RAW rom, and then Stock Rom but It's stuck on Fastboot Mode.
Read a lot of threads but not much seems to be working.
Help please !
Thanks
Click to expand...
Click to collapse
I have this problem too. How did you fix it ?