Database Info

[Q] Download Mode/Odin not working on Nexus S 4g

I can't get Odin to work on my 3 day old NS4G. If I put the phone in download mode (a pain in itself because half the time it boots android), Windows 7 and odin won't recognize it.
However, adb still works if the phone is fully booted or in fastboot, and the fastboot commands work. I guess I can get by with fastboot but I was wondering if anyone has run across this problem.
I'm using the pdanet drivers.
Thx...

no real reason to use odin, take my word on it fastboot is easier overall once you learn the commands and much safer

nexus s boot problem
i updated my samsung nexus s to 2.3.6 officially from phone update. but now it wont start without plugging in charger or usb cable connected to pc. if i start the phone without the charger or usb cable plugged a screen pops up saying 'downloading.. do no turn of target' what should i do to remove this bug. would really appreciate any help

"Key Driver Not Found.. " on Bootloader 4.2.1

So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...

MaMMiTs said:
So this morning my brother was using his TF300T in its dock. He undocked it and the screen went blank. Screen was still on but nothing displayed. I rebooted it for him (volume down and power button for 10s). After a minute of it powered on the screen went blank again, so I rebooted it again, but this time the Asus splash screen displays and the lock screen flickers before quickly going blank.
Thought a reinstall of the ROM would fix the problem but I now can't even boot into recovery or fastboot! Had no problem the first time I rebooted and selected cold-boot in the bootloader options. With the tablet on and screen blank I plugged it into a PC and Win7 detected and installed the proper drivers (I think). ADB commands seem to work, but the command to boot into bootloader only resets the tablet. Fastboot command does not work. Also noticed the below message flash before a flicker of bootloader options are shown. The PC seems to have access to the internal storage (I can see folders from the tablet) when plugged in via USB.
"Key driver not found.. Booting OS
Android cardhu-user bootloader <2.00 e> released by "US_ePad-10.6.1.8-20130PPt" A03"
Could it be a hardware issue? I ask because I see similar problems with the Asus splash screen indicative of a logic board problem when diagnosing a PC (images pixelated)...
Click to expand...
Click to collapse
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.

tobdaryl said:
It is unlikely windows installed the proper drivers for adb and fastboot. The drivers for accessing the internal sdcard yes.
See my signature for installing proper drivers in windows 7 and another for entering the bootloader after you have the proper drivers.
When I have seen that message it does not relate to hardware but software.
I don't suggest plugging and unplugging the dock when powered.
Click to expand...
Click to collapse
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...

MaMMiTs said:
Will try what you suggested, but does it matter that I'm using the same PC I used to initially fastboot TWRP to the tablet? I thought once the driver is installed it there would be no need to re-install the driver...
Click to expand...
Click to collapse
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"

tobdaryl said:
It will probably be ok. I was going by your comment "I plugged it into a PC and Win7 detected and installed the proper drivers (I think)"
Click to expand...
Click to collapse
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .

MaMMiTs said:
Yeah. My problem is I can't get to fastboot mode on the tablet itself, and based on what I saw on another thread it seems like I'm going to have to replace the mainboard .
Click to expand...
Click to collapse
OK.
Good Luck!

I unplug mine and reconnect all the time when on. Never had a issue.
Sent from magical jelly bean.

My brother's TF300T is back up and running!
As a last resort I opened it up to disconnect the battery. Still could not get into fastboot, so I left the battery plugged in and let the battery run out. After 48 hours of the battery being completely dead I charged it fully to see if I could do anything. Battery LED indicator was green and the first thing I noticed was that the unit was still off. (I wasn't able to completely shut it down before letting the battery completely drain). I powered it on thinking it would display a blank screen, but it powered up as usual! Everything seems to be working. I immediately flashed CROMI-X 4.3b6 on it (what my brother originally wanted me to do).
Thought I'd post this as a last resort hope for those who think they may have bricked their machine. I do recall completely draining the battery then waiting over 24 hours as a solution for one of the many machines I've hacked. Just thought disconnecting the battery would achieve the same purpose. Guess I was wrong . Hopefully this is a solution for someone else out there who may have bricked their machine. Sure doesn't hurt to try .
I'm actually mystified as to why this worked. Anyone know? I'm guessing completely draining the battery reset whatever was inside. I also have noticed more users have reportedly bricked their machines after Android 4.2.1. Coincidental? Thank God I'm perfectly happy with Android 4.1.1 based CROMI v3.4.6 .

Restarts from fastboot when connected to USB

Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher

melkhaldi said:
Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher
Click to expand...
Click to collapse
It seems to work fine now... I honestly kept tinkering around, it seems to work now. I wish I could offer a better answer. But I am not sure I am able to remember what I did exactly... it was a bunch of plugging and unplugging, restarts, and lots of prayers.

I had a same problem and similar solution
I believe i had found the solution when I change the USB port from my notebook where I had plug my the USB cable from my smartphone.

Same issue here.. I think it is because of USB 3.0. My laptop don't have USB 2.0 hence fastboot or adb wont detect my device, I was using a USB extender which works as USB hub (2.0) it worked many times before now again facing same reboot on usb connection issue.

Dead Pixel for black friday

I woke up this morning and my Pixel is dead. Completely unresponsive, can not get into bootloader from the phone.
Any ideas?
I got a replacement ordered through Google, and am using my Nexus 6 for now. It's a little frustrating that they authorize the replacement cost of the phone to process the order when I've got multiple credit cards on file with my Google account (which goes back to when Gmail was invite only) but I'll deal with it.

Just went through this yesterday. Put a hold on my card to replace even though I paid in full for the first one. So now I'm out the cost of 2 and have no phone.

Are you guys still stock?

magnumtripod said:
Are you guys still stock?
Click to expand...
Click to collapse
Yes. Stock. Bootloader unlocking enabled in developer settings but not unlocked. Running the latest OTA.

This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.

sn0warmy said:
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
Click to expand...
Click to collapse
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.

atlp99 said:
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
Click to expand...
Click to collapse
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.

sn0warmy said:
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
Click to expand...
Click to collapse
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.

atlp99 said:
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
Click to expand...
Click to collapse
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the bootloader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that doesn't mean it wouldn't communicate with the phone using fastboot commands. Like I said, myself (and many others on this forum) have been in your EXACT situation with a completely unresponsive phone which the computer wouldn't recognize as a connected USB device. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.

sn0warmy said:
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the boot loader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that that doesn't mean it wouldn't connect to the phone using baseline fastboot commands. Like I said, I've been in your EXACT situation with a completely unresponsive phone and the computer would not prompt me that a new USB device was connected even when the phone was plugged into it. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
Click to expand...
Click to collapse
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.

atlp99 said:
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
Click to expand...
Click to collapse
"fastboot oem unlock" is just the first part. You still need a responsive phone to unlock the bootloader by hitting 'volume up' and then 'power' as the final step to unlock the bootloader. The computer won't recognize the phone via ADB because the phone is unresponsive and won't power up fully. But just because the computer won't recognize/communicate with the phone via ADB commands, doesn't mean it wouldn't recognize/communicate with it via fastboot commands.
It's pretty common that people have run into an issue where their phone won't recognize ADB commands but still recognizes fast boot commands, especially with bricked phones.
https://www.google.com/search?clien...not+working+but+fastboot+is&ie=UTF-8&oe=UTF-8
I'm telling you, if your bootloader was unlocked, I'd bet money that you would still be able to communicate with your bricked phone using fastboot commands. The inability to communicate with your phone using ADB commands does not negate that.

Possible workaround...
Try holding the power and volume down for 20 seconds no matter what the phone does, or whether you even see anything on the screen, and if you get nothing, then try to do the same with volume up. I have had phones get stuck "in between" modes, for example trying to leave bootloader, recovery, or whatever else, and got stuck on a black screen, when the phone was in fact on. Everyone else's responses here were legit, though. I agree totally on the communicating with the phone via fastboot etc. If you can get it to bootloader even with the screen off, you can flash the entire phone. Of course this means you may lose items saved on the device.

I had this same issue happen...black screen but could hear the phone connect to the computer but fastboot wouldn't work...tried every possible combination oh buttons to get into anything and could...had to replace

http://forum.xda-developers.com/pix...ader-total-t3503963/post69713209#post69713209
Me too.

Well I got the replacement from Google on Wednesday and everything is running fine.
They did send a new phone, in retail packaging with all new chargers and cables. At least it wasn't a refurbished one.

I think my Pixel 2 is bricked!

So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!

RomBetaTester said:
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
Click to expand...
Click to collapse
Did you use the same USB cable each time? If yes try different ones, even if it seems to work with other devices. On your PC go to device manager, then view and then hidden devices. Remove anything that has to do with Android. Then try connecting your device. Does an andriod driver show up after you've connected your device?

I have tried 3 different cables. But will try another one

RomBetaTester said:
I have tried 3 different cables. But will try another one
Click to expand...
Click to collapse
Did you go to view, hidden files in device manager and delete all Android drivers? And if you did, did anything show up after connecting your device?

I am having a similar issue after trying to flash the March update. During the script, the System image failed to transfer completely. I tried again using deuce flash all script, and it got a little further (4/5) with the System image but ultimately failed. Things got worse when my computer stopped recognizing the phone. Now I can't even try anything else because there is no communication, similar to OP. I have tried three different computers, three different cables, and have tried deleting Android related drivers in the device manager. No luck, unfortunately. I tried installing USB drivers from Google which also did not help. I welcome any other ideas of what to try next and appreciate any help.
EDIT: I solved the problem by draining the battery completely. In order to drain the battery, I first left the barcode screen on until eventually just the battery image is displayed on-screen when pressing power. Then eventually there will not be enough power to light up the screen at all, but the LED indicator will blink red while holding the power button. Now, I set up my phone such that the power button was held pressed down and left it there until the LED stopped blinking. Now that the power is completely drained, I could successfully get my computer to recognize it! I followed the steps in this post:
https://forum.xda-developers.com/showpost.php?p=78726736&postcount=13
EDIT2: I should also note that the system image didn't flash successfully the first time and I had repeat step 12 which is flashing the update. Luckily it worked the second time!

I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31

ricky56789 said:
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
Click to expand...
Click to collapse
Man you just saved me =)