Hi XDA, need some help. Please? My Zenfone 2 ZE550ml got froze so I went and turned it off but when I was turning it back on it stucks on the USB Logo. Tried to go to the droidboot menu and recovery but it won't. Tried press and hold vol up& power then release power when phone vibrates but it wont do anything. I downloaded adb, intel driver and system (droidboot.img, recovery..img, boot.img, system.img) to do the adb flashing but it wont detect my phone and I think its because i cant set it to adb, droidboot, fastboot, recovery, usb debugging etc. Kept getting 0 device on the adb device list on the CMD when I was doing adb devices. I've been trying to do this for almost 3 weeks now and tried almost every possible solution offered by the internet but still unable to. Tnx in advance XDA
When you hold power and vol up, was the phone already plugged to the PC? I experienced that it won't go to recovery if it's plugged.
You can revive your unit using method 1 of rooting (fastboot of pre-rooted system.img).
Same like me,,i have this problem and my imei number not real,just sim 2 can use,,but now dont have sulotions,,everyday i search at google,,but no answers,,so bad
Jaymz123 said:
When you hold power and vol up, was the phone already plugged to the PC? I experienced that it won't go to recovery if it's plugged.
You can revive your unit using method 1 of rooting (fastboot of pre-rooted system.img).
Click to expand...
Click to collapse
No, it wont do it. Tried it numerous times.
Achilles.22 said:
No, it wont do it. Tried it numerous times.
Click to expand...
Click to collapse
Needs to be RMA'ed... Send back to Asus...
I wish i could send it back. Screen is cracked.
Related
Hi there,
I am using the Jellytime ROM with my desire HD. When turning my phone on the Jellytime splash screen appears and after that there is only a blank black screen and remains like that. Then I tried to boot the phone into recovery mode by holding down the volume down and power button but that did not work (my volume keys were working fine before) and nothing happened.
Then I looked around for solutions and I found the ADB method. With necessary drivers installed etc. I still was not able to boot into recovery mode since I cannot enable debugging mode and ADB showed the device as offline.
I have no idea what to do from now, anyone know of a solution?
Thank you.
ssj4sunny said:
Hi there,
I am using the Jellytime ROM with my desire HD. When turning my phone on the Jellytime splash screen appears and after that there is only a blank black screen and remains like that. Then I tried to boot the phone into recovery mode by holding down the volume down and power button but that did not work (my volume keys were working fine before) and nothing happened.
Then I looked around for solutions and I found the ADB method. With necessary drivers installed etc. I still was not able to boot into recovery mode since I cannot enable debugging mode and ADB showed the device as offline.
I have no idea what to do from now, anyone know of a solution?
Thank you.
Click to expand...
Click to collapse
What did you do to get in that state?
This all happened after I charged my battery from it being drained. Ive tried 3 other batteries too thinking it would make a difference but it didnt
ssj4sunny said:
This all happened after I charged my battery from it being drained. Ive tried 3 other batteries too thinking it would make a difference but it didnt
Click to expand...
Click to collapse
Does your computer recognize the phone? If so what about in Fastboot USB mode?
thekool said:
Does your computer recognize the phone? If so what about in Fastboot USB mode?
Click to expand...
Click to collapse
Yeah the phone is recognized as a 'MyHTC' or something similar which I think is because of the HTC drivers I installed. I have the android phone drivers installed but the phone doesn't seem to be recognized as one.
I have tried to use fastboot via CMD but the device was offline. I cannot access the menu since I think my volume down key is not working.
Deconnect the battery, wait 1 minute, connect it again, then hold volume down (till bootscreen come) while pressing power for 1 second
Had the same problem, so i solved it
If you have the attached image on your recovery-screen (after pressing "recovery") you have no recovery-image installed
Thanks for the help everyone. I realised it was the battery case that wasnt functioning correctly. Just ripped off a piece of foil and put it between the connectors which fixed the volume button problem (i think) so i was able to boot into recovery .
Thanks.
Good day!
After searching everywhere in the web and using different methods, I decided to create an account and ask you guys how to solve my problem
Basically, I have a HTC Desire HD phone, this is unlocked, rooted and using cm-Jellytime_42_R11 ROM. I decided to change ROM and go back to Android Revolution. What I did first was I deleted a couple of folders in my clockwork folder, I deleted both backup to free space. Afterwards, I was trying to connect my phone to my laptop but to no avail (it only charged) then I decided to just boot into recovery. After a couple of tries trying to access and going to bootloader/recovery mode it just wont push through. So I decided to normal boot, then the phone won't boot anymore. It just hanged in the Jellytime loading screen.
Note: I removed the battery a couple of too many times since I was trying to boot into recovery.
Thanks in advance to anyone who can help me with this problem
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Gussta said:
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Click to expand...
Click to collapse
no, i couldnt go to Hboot while holding down volume - and power.
The phone gets stucked in the Jellytime loading screen. It just stops. help me please
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
bananagranola said:
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
Click to expand...
Click to collapse
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
richardrip10 said:
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
Click to expand...
Click to collapse
WHen it getts stuck in the roms boot animation, connect usb to the phone and try
Code:
adb devices
Most devices show up via adb during the boot animation.
If the device shows up there, enter
Code:
adb reboot bootloader
then go here and download 4ext recovery.
extract the .img file from the zip. Rename it to recovery.img and place it in your adb directory and enter this whiles in fastboot
Code:
fastboot devices
to make sure your device shows up
then
Code:
fastboot flash recovery recovery.img
after it has successfully flashed reboot to recovery ad try and flash the rom u want.
hope i helped. Click on the thanks buttton.
You can ask if you still have problems.
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
richardrip10 said:
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
Click to expand...
Click to collapse
What recovery were you using before this happened?
mickeyasamoah said:
What recovery were you using before this happened?
Click to expand...
Click to collapse
cwm sir.
richardrip10 said:
cwm sir.
Click to expand...
Click to collapse
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
sorry, it still didn't work. Is this a bricked phone?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
btw, my computer really cant detect my phone. It doesnt make any sound when it is connected through USB. but other devices can be detected by my computer. I tried inserting the usb into a 2.0 and 3.0 usb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
hey bro, I actually made it work. problem is when im flashing the recovery, it shows Failed<remote: not allowed>
what should I do?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
richardrip10 said:
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
Click to expand...
Click to collapse
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
mickeyasamoah said:
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
Click to expand...
Click to collapse
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
richardrip10 said:
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
Click to expand...
Click to collapse
I am happy i was able to help.
Instead of saying thanks only, you could actually hit the thanks button.
Have a nice day.
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
SF-Echo18 said:
My HTC One M8 (Verizon) is seemingly bricked. My phone is rooted, S-Off, with the stock ROM. I have been trying to update to the latest OTA update by returning to stock. I had previously modified some entries in the Build.prop and Platform.xml. I knew those had to be default in order for the OTA to work. I had copied the original files and pasted them to my SD Card so that I could simply cut the modified versions, paste them to my SD Card, and cut the originals from my SD Card and put them in their corresponding system folders.
Upon a reboot something apparently went horribly wrong because all my phone does now is boot with the white screen and green HTC Logo, then the screen goes black. I have tried the typical Power Button + Volume Down but it won't enter the boot loader. The good news is that the USB port seems to still work for my windows computer recognizes a device connecting to it but it doesn't show up as an interactive device in windows explorer..if that makes sense.
Please Help!
Click to expand...
Click to collapse
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
BerndM14 said:
When you connect it to the PC can you pick up the device with adb? If so, have you tried to run the command from adb to boot it into bootloader? adb devices ... if found, adb reboot bootloader
:fingers-crossed:
Click to expand...
Click to collapse
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
SF-Echo18 said:
I'm not too familiar with ADB commands but I typed in "adb reboot recovery" and it said: "error: device not found" so even if my command was wrong it's still not detecting it. I also tried: "fastboot reboot bootloader" and it just says "waiting on device for device"
Also I feel like it's worth mentioning the phone is automatically rebooting every two minutes or so (haven't timed it exactly but it's a while). Still showing the green HTC Logo then the screen goes dim, then the screen turns off.
Click to expand...
Click to collapse
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
BerndM14 said:
Try holding volume UP + Power button, this simulates a "battery pull", just hold it in for a while it can take a while to "pull", when it's off try again booting into bootloader, volume DOWN + Power button.
Click to expand...
Click to collapse
I held Volume Up + Power Button and it showed the white screen with the green HTC logo. I then released all buttons. Once the screen turned off I then held Volume Down + Power Button for two minutes straight and nothing happened.
Even though we haven't found a solution yet, I am appreciative of the help.
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Just remember to change directory in command prompt to the folder where adb.exe is located.
I don't know why the device doesn't reboot into bootloader though when you hold volume down + power button, shouldn't have to hold it for 2minutes. Holding volume up + power button to simulate a "pull" should only take up to 20 seconds or so at most and pressing volume down + power will then immediately take you into bootloader mode, or at least it's supposed to.
Did you release the volume up / power combo when the screen went dead or before? Try holding it until the phone shuts off and then right away press volume down + power.
Sorry if I'm not answering right away though, busy eating, and will be here and away for the next hour or so while I get ready for work =o( once I leave for work I'll only be able to help some more after like 2 hours or so. Hopefully we can do something before then though =o)
wase4711 said:
sounds like you never installed the htc drivers for your phone, hence your pc doesn't see the phone when you are doing ADB commands.
install the drivers for it, then try the ADB commands via your pc
and dont mess with the build prop or other system files unless you have a working back up and are 101% certain about what you are doing..
Click to expand...
Click to collapse
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
SF-Echo18 said:
You're right, I didn't install the drivers. I did so and ADB was able to recognize it and I was able to access the bootloader. Thank you everyone for your help. I won't be making the mistake again.
Click to expand...
Click to collapse
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
BerndM14 said:
So you'll be able to fix it from here on then? I was just about to link this thread to you as well should you have gotten adb to work again, it's for the RUU for Verizon seeing as you said you're on Verizon.
But going by your response up there you might already know how to fix this issue further :good:
Click to expand...
Click to collapse
Indeed I appreciate it, but I just finished installing the RUU ha. Hopefully this thread will be of use to someone in a similar circumstance in the future.
Share another method of getting into recovery mode on non-responsive blank screen
Hi,
I just want to share how I accessed recovery mode with the same build.prop issue but with S-ON (might work with S-Off too).
I found the solution from here:
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
To get into recovery mode on a non-responsive blank screen, hold the power button and volume up button at the same time and then approximately after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. After, a white boot screen will give an option to go into recovery mode.
i was rooting my zenfone 2 ZE551ML , and during the process i accidentally restar my phone, and now i have the bootloader unlocked screen (white asus logo screen) and i cant enter to recovery now, noting happens, i try using this guide but the MOOREFIELD driver appear for only 1 second and the phone turn again to the bootloop. i don't now what i can do to fix my phone please i need help. ADB don't work because i cant enter to bootloader or something like that
:crying: :crying: :crying:
sorry for my bad english.
grandjulio said:
i was rooting my zenfone 2 ZE551ML , and during the process i accidentally restar my phone, and now i have the bootloader unlocked screen (white asus logo screen) and i cant enter to recovery now, noting happens, i try using this guide but the MOOREFIELD driver appear for only 1 second and the phone turn again to the bootloop. i don't now what i can do to fix my phone please i need help. ADB don't work because i cant enter to bootloader or something like that
:crying: :crying: :crying:
sorry for my bad english.
Click to expand...
Click to collapse
are you able to go to bootloader screen?
sukhwant717 said:
are you able to go to bootloader screen?
Click to expand...
Click to collapse
No, i cant only show White screen with asus logo, and I can not enter to bootloader, Simply when I press the power button and volume does not enter.
Hey,
I have the same problem, MOOREFIELD driver appear for only 1 second and the phone turn again to the bootloop. But i have access to the fastboot. I tried to flash a stock recovery but it doesn't change, it stuck to fastboot screen
Open xFSTK, press and hold the power button until the phone turns off, start download in xFSTK, connect to the computer. If the phone tries to power up, press and hold the power button down to force the phone to power off. It took me a few tries but I got xFSTK to bring up fastboot.
audit13 said:
Open xFSTK, press and hold the power button until the phone turns off, start download in xFSTK, connect to the computer. If the phone tries to power up, press and hold the power button down to force the phone to power off. It took me a few tries but I got xFSTK to bring up fastboot.
Click to expand...
Click to collapse
Zephyrell said:
Hey,
I have the same problem, MOOREFIELD driver appear for only 1 second and the phone turn again to the bootloop. But i have access to the fastboot. I tried to flash a stock recovery but it doesn't change, it stuck to fastboot screen
Click to expand...
Click to collapse
thanks for the reply but sukhwant717 help me to solve the problem, is just a mistake in the steps using xFSTK, i follow this guide https:// drive. google.com/file/d/0B2oMRhweQ4CHaFJnMEZ4NUg1YlU/view
Today I Bricked My LG820Qm
I was updating my Lg g8 using LG UP, When the Process on 64% my PC power off
After that my phone stuck in Qualcomm HS-USM QDLoader 9008
Any solution to come out from this mode to Downloaded Mode so that i can update using LG up.
I was updating G820QM10i_00_NAO_US_OP_0401 to G820QM20b_00_NAO_US_OP_1224
My LG up LGUP_Lab_Frame_Ver_1_16_0_3
Can you try to switch to download mode by press&hold VOL+ while inserting the USB cable (connected to PC). Phone needs to be off while doing so.
tron1 said:
Can you try to switch to download mode by press&hold VOL+ while inserting the USB cable (connected to PC). Phone needs to be off while doing so.
Click to expand...
Click to collapse
I tried not working
If i press&hold VOL+ while inserting the USB cable still my phone come with Qualcomm HS-USB Mode
thanks for your reply
What happens if you press&hold VOL- (furing the whole procedure) push the power button until the phone vibrates, release the button und press&hold the power button?
tron1 said:
What happens if you press&hold VOL- (furing the whole procedure) push the power button until the phone vibrates, release the button und press&hold the power button?
Click to expand...
Click to collapse
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode
I don't know where to ask so I'm gonna try here. My G820N is stuck on Android 10 beta. Whenever I flash an official kdz, it only allows for emergency calls. Can't do anything. Any help would be appreciated
Following, in right here with ya.
atsuisofu said:
Following, in right here with ya.
Click to expand...
Click to collapse
Try entering download mode with phone disconnected from USB cable.
Also try to see if it gets recognized by LG-UP or by LG Bridge. These 2 softwares don't need download mode to be able to flash, just the phone to be recognized on some PORT.
Try also factory reset hard menu. Also try switching between Slot A and Slot B. There is also this backup method. Phone is not dead on one of those slots.
If nothing works (but slot a slot b should 100% work) , wait for the firehose, it's just around the corner. That will restore the phone back 100%.
For more info search v50thinq on telegram app. :good:
I can t get to download as it freezes and without the USB cable it doesn't even try and enter. I appreciate the recommendations. I was thinking of the a/b seit hbut without the use of fastboot I am at a loss of how to switch between the two as I thought the system chose and the switch happened upon rebooting once a system had been selected ie as in turning the unit off after loading the os set a flag to go to the opposite system upon completing the inftframs and boot sequence.
vikramanananda said:
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode
Click to expand...
Click to collapse
Hi, i'm facing the same problem today, my QM will not go into any mode other than the Qualcomm mode. Were you able to recover your phone finally ?
vikramanananda said:
Which ever combination, Vol- + power phone power of
with in sec it boot to Qualcomm mode
Click to expand...
Click to collapse
did you ever get it fixed. im having the same problem.
johnnycm77 said:
did you ever get it fixed. im having the same problem.
Click to expand...
Click to collapse
me too, do you fix it?
vikramanananda said:
Today I Bricked My LG820Qm
I was updating my Lg g8 using LG UP, When the Process on 64% my PC power off
After that my phone stuck in Qualcomm HS-USM QDLoader 9008
Any solution to come out from this mode to Downloaded Mode so that i can update using LG up.
I was updating G820QM10i_00_NAO_US_OP_0401 to G820QM20b_00_NAO_US_OP_1224
My LG up LGUP_Lab_Frame_Ver_1_16_0_3
Click to expand...
Click to collapse
So, if the device, as you say, lost power during an update like that, then almost assuredly you have at least one, if not numerous corrupted partitions.
And, it's specific partitions on the device that allow it to enter download mode. One of these most know about or have heard of is the laf partition. But other have to be there also for it to work, I don't remember exactly what the others off the top of my head, but that info is easily found.
The key thing you need (or any others commenting same prob), is to be able to enter EDL mode and have qfil installed and recognizing the device. If you can get that far, it would be easy to find the correct partitions you could flash with qfil and then immediately go from qfil to download mode.
Many many people have done this. Just get qfil set up (see guides section) and get the device recognized. that takes some effort but it's def doable.