bootloop'ed ZE551ML Z00A - ZenFone 2 Q&A, Help & Troubleshooting

Hi,
I somehow managed to get myself into a bootloop situation (it keeps rebooting and showing the asus logo until I shut it down). I had flashed the droidimg.img recovery.img and boot.img files from the latest official stock rom, but that seemed to not work and now I'm in a bootloop. I do not have fastboot or recovery or anything else. It's stuck at the logo and keeps rebooting.
To fix it, I tried to follow the "unbrick" guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785), but I can't see the MOOREFIELD device show up for long enough to even click it (only shows up for a split second under "Other Devices" section). And I can't see "Inter SOC" in device manager at all. Also, xFSTK-Downloader doesn't run (doesn't show up when I click it) at all. This is on Windows 10. I have looked at other guides and they seem to have followed the "unbrick" guide, which doesn't work for me.
Is the phone done for good or is there hope?

fengshaun said:
Hi,
I somehow managed to get myself into a bootloop situation (it keeps rebooting and showing the asus logo until I shut it down). I had flashed the droidimg.img recovery.img and boot.img files from the latest official stock rom, but that seemed to not work and now I'm in a bootloop. I do not have fastboot or recovery or anything else. It's stuck at the logo and keeps rebooting.
To fix it, I tried to follow the "unbrick" guide (https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785), but I can't see the MOOREFIELD device show up for long enough to even click it (only shows up for a split second under "Other Devices" section). And I can't see "Inter SOC" in device manager at all. Also, xFSTK-Downloader doesn't run (doesn't show up when I click it) at all. This is on Windows 10. I have looked at other guides and they seem to have followed the "unbrick" guide, which doesn't work for me.
Is the phone done for good or is there hope?
Click to expand...
Click to collapse
please don't make multiple thread uselessly. please read the guide properly. that question have already been answered multiple time. connect you phone to pc. turn it off by pressing power button long time. now run xfstk load files tick gpflags override. then click ok. and click begin download it will start waiting for device. now simply click power button to turn on device. xFSTK will force it into required mode and will start download. repeat steps as required

Related

No Recovery - No Download Mode - No Fastboot

Hey everyone,
We have an LG G3 D855 here which has been interrupted midway through flashing a KDZ file,
Powering on the device gives us,
"Cause : Boot certification verify (secure booting error)"
Followed by the screen going off and the blue red LED flashing endlessly.
Download mode does not work,
Recovery mode does not work,
However, the factory reset screen appears, but when selecting yes it reverts to the LG logo and reboots.
Here is a screen shot of what appears in device manager on my PC after I attempt to enter download mode.
As you can see, it is "QHSUSB_BULK" in device manager.
We have tried adapting this guide for the G2 with Ubuntu, but the device is not recognized by Ubuntu. http://forum.xda-developers.com/showthread.php?t=2582142
If we can get into fastboot somehow we will be fine, but nothing seems to be responding. Any advice would be fantastic.
We also have another idea, of super hard bricking the device somehow so that we can follow this tested method of getting out of the brick,
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 not sure how to get either of these though so some help would be great.
The same problem has been described here, http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-rooted-download-mode-t3003988
EDIT : After 10 hours of working on this problem we found the solution and posted our fix and explanation here http://forum.xda-developers.com/lg-...nload-mode-t3273824/post64377399#post64377399
Thanks to all parties involved.
Orcam said:
Hey everyone,
We have an LG G3 D855 here which has been interrupted midway through flashing a KDZ file,
Powering on the device gives us,
"Cause : Boot certification verify (secure booting error)"
Followed by the screen going off and the blue red LED flashing endlessly.
Download mode does not work,
Recovery mode does not work,
However, the factory reset screen appears, but when selecting yes it reverts to the LG logo and reboots.
Here is a screen shot of what appears in device manager on my PC after I attempt to enter download mode.
As you can see, it is "QHSUSB_BULK" in device manager.
We have tried adapting this guide for the G2 with Ubuntu, but the device is not recognized by Ubuntu. http://forum.xda-developers.com/showthread.php?t=2582142
If we can get into fastboot somehow we will be fine, but nothing seems to be responding. Any advice would be fantastic.
We also have another idea, of super hard bricking the device somehow so that we can follow this tested method of getting out of the brick,
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 not sure how to get either of these though so some help would be great.
The same problem has been described here, http://forum.xda-developers.com/lg-g3/help/lg-g3-d855-rooted-download-mode-t3003988
Click to expand...
Click to collapse
Have a look here >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 <<
Follow the guide above
tallman43 said:
Have a look here >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 <<
Click to expand...
Click to collapse
Thanks mate, are there no software alternatives to this problem? We have been looking literally for hours.
It works! I have found a diffrent package at web. The "Device is not in DL mode" issue is much better with! If the DL breaks, reject the USB-cable and klick start again the process should start without probs. For prevent the app to freeze exclude cust.mbn, system.mbn, userdata.mbn, cache.mbn every .mbn bigger then 50mb. This files we can flash later with Flashtool after the device is back to life
Files: https://mega.nz/#!fRwD1a4Z!Et6aea3XInKW4frrNs-GqGz5diIQdjNBjOg6uTiG6Hk
Hope it would help...
greets and very Christmas to all!

G3 D851 hard brick or is it? Need help!!!!

Hello,
I seem to have really messed up my G3 and after days of research I have not been able to get anywhere with it. I've read posts of people having similar issues, but their solutions do not seem to work for me.
What I tried to do is flash the ROM, starting with TWRP. After installing TWRP and rebooting I was getting the "no command" message on the screen. I believe (this was days ago), I used ADB to remove laf and reboot the phone (for some reason I could not back it up). The phone rebooted in fastboot and it has been downhill from there.
No download mode. When normally started the phone just hangs on the LG logo. Vol- and power gets me to the "Factory data reset", but if I do that, it flashes "erasing" for a second and it goes back to the LG logo screen.
I can get to fastboot, however, any command that I enter in CMD or Linux terminal just shows up on the phone's screen and it does not do anything. Fastboot devices shows the device as "????????" in Linux and as "?" in Windows. I have tried multiple drivers for Windows.
I tried BoardDiag (3 or 4 different versions running as admin) and shorting the pins, but any time I try to run the checks, I get an error - "No response from device" or "Device was not found in dload trying flash programmer"
I also tried SmartBootDiag, but once it detects the phone, it does its checks and it disconnects the device, without giving me an option to flash anything. Looking at the logs, it does not find any anti-rollback issues.
Any suggestions would be greatly appreciated as I am not sure what else to try.......
Thank you.
Anyone??

screwed my memory i think - not hard bricked but what is this? cant boot

after trying unsucessfully many times to get LVM to work I decided to go back to stock oppo recovery. I saw an option to unify memory in the oppo recovery and clicked that. My screen flashed for 30min with no reboot. I shut it down. This could have where it went wrong.
Now I cant boot into any recovery. Just stays stuck on the oppo logo. i DO have fastboot mode though and I CAN execute commands via the terminal/cmd prompt using adb/fastboot.
If I flash twrp, i can see it tries to boot into twrp with a blue flash of a screen but immediately it goes back to the oppo logo and stays there forever.
If I flash oppo recovery again, i can see it tries to go into oppo recovery but then the screen starts flashing bits and pieces of what I can make out as the oppo recovery.
Tried the unbrick method. I assume my memory is messed up because i tried to unify memory via the oppo recovery? I cant seem to do the unbrick method here: http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067. Tried it with win10 on test mode and cant get his specific driver names to work/show up. Shows up on mine as Marshall London boot loader or Android bootloader.
Also used the repartition tool repair scripts: http://community.oppo.com/en/forum.php?mod=viewthread&tid=20271&extra=. That did nothing. Black screen for about 1hr. Still have fastboot right now though. Still doing the same thing.
Any way to solve this? Thanks in advance to the pros at XDA!
THIS WORKED!! It took me very long to figure this out!!
http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1
For that tutorial i had to deviate from the instructions ironically, if i held down power + up, it would take me to fastboot and i could NOT install the right drivers and it would come up as Marshall London Device (windows 10 with TESTSIGNING turned on). All I had to do was just plug into usb and NOT press or hold any buttons on the phone. Then it showed up as QHSUSB_BULK in device manager and I can proceed with this tutorial.

A bit harder than a soft brick

Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------
In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.

Question I am stuck in fastboot and can only boot into fastboot please help??

I can only accsess fastboot and cannot reboot into anything except fastboot.... I tried extracting the payload bin but can only flash a few lines then I am told to reboot into fastbootd but cannot access that either... I cannot access recoveries either and I have tried to flash them but still wont budge... any ideas??
Use MSM tool
I also have this problem and I can't get it to EDL mode nothing happens stuck in fastboot.
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
xifo.0001 said:
I just typed a whole guide on how I managed to solve this in detail and the tab got closed out... in short then, download Qualcomm drivers and not oneplus's. There are many drivers in the file, just extract the whole thing and point to the file on device manager and include subfolders. It should find which I think was the HS-USB QDloader 9008 driver then install. Make sure you download the correct MSM for your version. The latest for global (or O2) is only hosted on one server and was going to take 12 hours to download on highspeed internet so I used lemonadep_22_O.05_210324 being 11.2.2.2. Use the Win7 version. Even though you cannot use EDL, you can reference these key combinations to get it recognized. If you're having a completely black screen, use the all button press hold until it vibrates. Make sure you are shutdown all the way and if needed use fastboot to. With MSM opened, drivers installed, and phone off, hold both vol keys and connect to PC. Hit Enum to refresh connections and hopefully it shows up and you can get a successful download complete. I found that the black screen was actually the device being in recovery mode. It was possible to successfully enter recovery using boot with power and volume down at times, although all sideload OTA's (along with prior fastboot flash boot *.img, fastboot -w, fastboot update, fastboot reboot-edl, ect.) failed. There was a lot of trial and error where just repeating some things after they had failed almost magically started working or stopped however this process is what worked in my case.
Click to expand...
Click to collapse
After hundreds of trys I finally got it scared ****less that I lost my phone.
holydemon said:
After hundreds of trys I finally got it scared ****less that I lost my phone.
Click to expand...
Click to collapse
lol same here, you say it's working now though?
xifo.0001 said:
lol same here, you say it's working now though?
Click to expand...
Click to collapse
Yeah but that was a hassle should've been easier to reach that interface. I was almost sending it to service for nothing but a stupid unreachable interface nonsense.
Also to note when I tried with original cable from the box was successful the other usb cable gave me problems.

Categories

Resources