Database Info

[Q] Nexus S not appearing in device manager in fastboot

I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?

stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?

stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.

Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader

Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor

vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot

Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....

OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse

Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...

fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g

Nexus S boot problem

Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.

SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck

cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:

SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning

Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?

uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?

polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?

SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.

polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".

SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.

polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..

SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.

polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..

SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?

polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.

SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.

polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.

[Q] Too many pattern attempts... No Recovery menu

hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"

mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
did you try to pull out the battery?
if not take it off,put it again
then hold volume down + power button until it shows the bootloader screen

mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?

mmcr said:
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
Click to expand...
Click to collapse
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.

heavy_metal_man said:
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
Click to expand...
Click to collapse
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?

mmcr said:
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
Click to expand...
Click to collapse
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.

heavy_metal_man said:
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
Click to expand...
Click to collapse
boots up in safe mode

mmcr said:
boots up in safe mode
Click to expand...
Click to collapse
hmmmm. running out of ideas now. was this your device? do you know the google account ect?

heavy_metal_man said:
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
Click to expand...
Click to collapse
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.

mmcr said:
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
Click to expand...
Click to collapse
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.

So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?

se1000 said:
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
Click to expand...
Click to collapse
i've tried that several times bro, just the same out come everytime

heavy_metal_man said:
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
Click to expand...
Click to collapse
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.

mmcr said:
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
Click to expand...
Click to collapse
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.

heavy_metal_man said:
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
Click to expand...
Click to collapse
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices

mmcr said:
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
Click to expand...
Click to collapse
indeed so. but you cannot fault it as a security measure :silly:

Phone died afeter bootloop

Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's

Sv22 said:
Hi,
i've do an error with sense 5 rom flash.
I have rebooted the phone before flashing boot.img. I have try to put the one x in fastboot or recovery mode but nothing (this phone have very **** keys). After I shot down phone but now don't start. If I connect to charger red light works, same at PC. Windows recognize phone as HTC mtp devices and show me unity letter but i can't do nothing.
Battery 70%.
Any ideas?
Thank's
Click to expand...
Click to collapse
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on)
If you still can't see the screen while in bootloader, then your screen is dead.

exad said:
If you're phone is read as an mtp device that means it's not dead and the rom is loaded. The screen is black I take it and won't come on?
reboot to bootloader
either using adb (adb reboot bootloader)
or
manually (hold power button until capacitive buttons blink a bunch of times and the phone shuts off then let go of power and press and hold volume until bootloader comes on.
If you still can't see the screen while in bootloader, then your screen is dead.
Click to expand...
Click to collapse
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing

Sv22 said:
yes, my phone is read but on the control panel there is a yellow icon on driver. and if I push keys phone do nothing
Click to expand...
Click to collapse
ok.. did you try what I posted above?

exad said:
ok.. did you try what I posted above?
Click to expand...
Click to collapse
yes, but nothing. ADB show me list devices blank, fastboot no devices.....mmhhhh....I have no word. This morning was alive...

today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?

Sv22 said:
today I have turned on the phone in bootloop.
I have volume down key was not working. Any ideas?
Click to expand...
Click to collapse
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?

redpoint73 said:
Are you saying the buttons are actually not working properly?
MTP mode plays havoc with adb, and sometimes fastboot. Of course, if you are not able to access recovery, adb, or fastboot, you are in a very tough spot.
Is the device S-off or S-on?
Click to expand...
Click to collapse
my devices is s-on.
I hate this kind of situation. Very comic......

Damn, wont' even load fastboot!

OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US

If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.

Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.

Hold power button until phone turns off. Turn phone on while holding volume down.

tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.

lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP

So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.

mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.

Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G

mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again