• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

No Command prompt when updating phone

Mine kept powering off and on and did that all night, I finally just left it alone because I was going insane trying to figure out the issue.
I checked on here this morning and followed the SUA suggestion. There was a little trial and error. I had the same issue with phone not being detected. If you disconnect from usb, turn phone off and then vol down with power till START shows then let go. Once you do that you scroll to the Bootloader I think it was and leave it there, dont touch anything, your phone has to be on and not stuck in the reboot/restart cycle mine went through last night. Connect again to usb and it should auto detect with the SUA open.
 
aotoole said:
Darn, I'm using a USB 2 port and no luck. I'm in Fastboot mode and have the SUA up, but it is not detecting my phone. It says that "this screen will go away once fastboot mode is detected." Odd because when I plug the phone in the computer, I can hear the 2 beeps the computer makes signifying something has been connected. Ugh. Any other ideas? I'm ready to scream.
Click to expand...

I just checked exactly what mode I was in and I had selected "Restart Bootloader." That may have nothing to do with having my Laptop (Win8) recognize the device.
 
When I'm in Fastboot mode is says my device is locked. Does anyone know if this could be causing the issue of not being detected?
 
Thats what you need but dont click on the power to get into that actually prompt. Just scroll till you are there and connect the usb and it should start to autodetect the phone from there. Your phone, if you are having the same issue as I was, will keep restarting and if it is doing that the SUA wont detect it, it has to be on and stay on.
 
aotoole said:
When I'm in Fastboot mode is says my device is locked. Does anyone know if this could be causing the issue of not being detected?
Click to expand...
I see that you did get it work, but, just to answer this question, it means that the bootloader has not been unlocked, which is normal.
 
You must log in or register to reply here.
Back
Top Bottom