Bricked zenfone 5z (tried everything!) - Asus Zenfone 5Z Questions & Answers

Hi, my zenfone 5z is hard bricked. I installed twrp and deleted all data.
Things to consider:
- My zenfone wont turn off, its STUCK on fastboot mode;
- I CANNOT enter the Recovery mode;
- The phone just restart everytime i press the buttons (and come back to fastboot mode);
- The PC do not recognize the phone on adb (tried multiple ports, and another PC, with a new cable).
How can i fix it?

Up

savenx said:
Hi, my zenfone 5z is hard bricked. I installed twrp and deleted all data.
Things to consider:
- My zenfone wont turn off, its STUCK on fastboot mode;
- I CANNOT enter the Recovery mode;
- The phone just restart everytime i press the buttons (and come back to fastboot mode);
- The PC do not recognize the phone on adb (tried multiple ports, and another PC, with a new cable).
How can i fix it?
Click to expand...
Click to collapse
I'm stuck in the same step. However, I can reboot into twrp by connecting to a PC and typing fastboot reboot recovery. May have to repeat it sometimes. Apart from that, nothing else works, TWRP doesn't sideload.

1> Try booting into TWRP with "Fastboot boot twrp.img" and do complete device whipe from there.
OR
2> Find a matching RAW firmware from the forum here and re-flash the firmware from Fastboot
OR
3> If above not working, and EDL flash may be the only option out.

Related

[Q] No Download mode, no fastboot mode, no hard reset mode

Dear all,
Thanks for reading this post first. I have a G3 D855 with a unknown ROM inside (as i bought it from others, i don't know what the ROM is, but it is obviously a custom ROM). I try to flash a stock ROM and search the method from the net, but no method i can use for the following reasons:
1. i can't go into download mode (tried turn off phone, hold volume+ and plug in cable method)
2. i can't go into recovery mode with any key combination (used the method online, the screen will light up but LG logo won't show, there light off, keep looping like this)
3. i can't hard reset with any key combination
4. as you can see above, i can't get into fastboot mode with any key combination (but i do can use program in Win7 to call the phone into fastboot mode)
5. When i connect the phone (turned on) with Windows 7, it can recognised as LG G3, and i can explore the internal storage. But if i try to connect it for the Download Mode, then it can't be recognised, just "dang dang" sound from the computer. (i have installed the latest LG drivers). My phone can't be recognised in Ubuntu.
So, i try to figure out what has happened to my phone, and after searching for few days, i believe that i may flash sbl1.img, aboot.img, rpm.img, tz.img to get back the above modes for my phone (see http://forum.xda-developers.com/showthread.php?t=2582142). I would like to know if my thought is correct at this point.
If yes, can i just make my phone into fastboot mode with the help of the Windows Program to flash back those img, or can i use Flashify to flash those image?
Thanks for all your help.

Am I bricked or is it a step I may have missed? ZenFone 2 ZE551ML

Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.
@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks
Which recovery are you using to flash and which file are you trying to flash?
I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.
The phone is running a MM bootloader? What about MM or LP based ROMs?
I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704
You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?
I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks
Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator

ZE551ML stuck in fastboot mode

Hello,
My Asus Zenfone 2 ZE551ML is stuck on fastboot mode and shows the message "continue the fastboot process".
Whichever option I choose, Normal Boot, Recovery Mode, Restart Bootloader, it boots back into the fastboot mode. I tried connecting it to my PC so that I could flash a recovery or flash it back to stock ROM but it does not get recognized by my PC. In device manager it shows Unknown USB Device (Port Reset Failed).
Can anyone please help me recovering my phone?
Thank you very much in advance. I would definitely treat you with coffee and some cookies.

Nord N100 EDL Mode - Dead / Gone

I flashed the 11.0.1 global boot image to my BE82CB to attempt root via these instructions: https://forum.xda-developers.com/t/...eplus-nord-with-magisk-and-temp-root.4340113/
Unfortunately, it bricked my device. It boots to a T-Mobile loading screen but feezes there.
I'd like to use the MSM for 10.5.8.BE82CB to unbrick this, but I can't enter EDL mode. These are the ways I've tried:
a) hold down vol up / down for 10 seconds - attach USB
a result) device boots to fastboot
b) fastboot reboot emergency
b result) device boots to fastboot
note: even just plugging in a charging USB boots the device to fastboot
Any ideas on how to get my phone into EDL mode, or did I kill it and permanently brick my phone?
let me help you here. if youre in fastboot you still have flashing access. do you remember your old version number?
I have exactly the same problem, after installing twrp I accidently formatted some partitions including system, and they aren't mounted, because of this I can't use edl and i can't decrypt data to get access to system partition. I can use only fastboot.
does fastboot reboot edl work? if not you might have to buy a deep flash cable off amazon to get it into edl, only about $10-15
You have to enter recovery mode and make windows look for the Qualcomm driver first. May take a few reboots of the phone in recover to trigger windows but you'll see optional link inwindows update when it does find something. Click and download the comm driver. mine was "Qualcomm HS-USB QDLoader 9008 (COM3)" your COM may not be COM3.
Reboot PC and turn off phone.
Open the msm downloader and click start
hold UP and DOWN only - plug in phone -> phone will seem like nothing happens but you should see a COM pop up in the software
then continue with the download, it take some mins.
hope it helps some. I have N100 sprint/t-mobile
i can say that the software saved me for sure. it took me back to android 10 but im ok with it.
Possibly unrelated, I was testing different GSI images accidentally wiped system. wouldn't turn off just rebooted. I was able to get into EDL mode I just had to hold down volume up & down just after selecting power off in fastboot menu. maybe this will help, but no guarantee.
bouyakasha said:
I flashed the 11.0.1 global boot image to my BE82CB to attempt root via these instructions: https://forum.xda-developers.com/t/...eplus-nord-with-magisk-and-temp-root.4340113/
Unfortunately, it bricked my device. It boots to a T-Mobile loading screen but feezes there.
I'd like to use the MSM for 10.5.8.BE82CB to unbrick this, but I can't enter EDL mode. These are the ways I've tried:
a) hold down vol up / down for 10 seconds - attach USB
a result) device boots to fastboot
b) fastboot reboot emergency
b result) device boots to fastboot
note: even just plugging in a charging USB boots the device to fastboot
Any ideas on how to get my phone into EDL mode, or did I kill it and permanently brick my phone?
Click to expand...
Click to collapse
I had to use a cable, but it worked well. Make sure the drivers are installed before. It took a few tries and I had to rotate the cable, but it worked eventually. Install the drivers, reboot, make sure phone is off, plug in cable and press the button. Qualcomm should show up under ports in device manager and you should be all set.

Question Need help unbricking -> EDL not accessible for MSM

[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!

Categories

Resources