Device not recognized - Samsung Galaxy Nexus

I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...

It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.

mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..

Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.

This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.

chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot

Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.

chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?

bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?

chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).

mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?

chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.

@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.

bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.

I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader

brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*

Make sure USB debugging is turned on.
Sent from my Galaxy Nexus

mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*

Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?

mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus

Related

[Q] Think I've bricked my Desire, help needed!

Hello, I was happily using a previous miui build and updated using ROM Manager and it was going fine until the phone stopped being able to recognise the SD card whatsoever, so I tried looking that up, and was finding things about reformatting memory cards, trying different ones etc. I tried all these things to no avail, I am now trying to RUU it back to a stock Sense ROM in the hope that will fix the SD card problem but when I try to connect it via USB to the PC it isn't recognised at all. I've tried installing HTC Sync etc. I've no idea what to do anymore?
ANY ideas much appreciated!
Thanks~
You have a classic USB brick. Don't panic, it's pretty frequent. Try this: http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!
matthewamac said:
It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!
Click to expand...
Click to collapse
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?
Don't jump into restoring an RUU as you will really be in trouble then!
Trust me, I've bricked mine and gone down this road to put it right and it can be done.
Get hold of Android-SDK (Google it), get that installed and prepare to learn. In my case I managed to restore SD card functionality and thought I had won, then discovered that I still had a USB brick. Nevertheless, many hours reading and several vodkas later I had it fully restored.
If you still have clockwork recovery on the phone (I'm assuming you're using that?) then it's a pretty easy fix, don't panic! And above all, don't attempt to go back to stock as then you'll still have a knackered phone but with no root to recover it (although I doubt you can if your phone can't read it, unless you learn the fastboot stuff and flash the RUU before actually fixing the problem).
The thread linked gives some idea, there's also a lengthier one, search 'USB brick'.
And good point by paul.c, that would be far simpler but I've never tried it myself - although esentially that is indeed the command required to get the SD card working again.
Just beware that getting the SD card working may not be the end of your woes, you may then find (as I did) that USB functionality is broken and bluetooth doesn't work, classic 'USB brick' symptoms. Again, pretty easily fixed.
paul.c said:
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?
Click to expand...
Click to collapse
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?
matthewamac said:
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?
Click to expand...
Click to collapse
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App
MatDrOiD said:
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App
Click to expand...
Click to collapse
So for Android SDK should you be properly booted or should you be in the Fastboot screen?
matthewamac said:
So for Android SDK should you be properly booted or should you be in the Fastboot screen?
Click to expand...
Click to collapse
If you have to issue fastboot commands your phone has to be in fastboot.
paul.c said:
If you have to issue fastboot commands your phone has to be in fastboot.
Click to expand...
Click to collapse
My SDK is working fine for commands such as 'ADB Devices' now but when I go into Fastboot and give the command 'fastboot' it states that it's not recognized! Do you have to have S-Off for this to work?
Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone
jhonybravo4u said:
Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone
Click to expand...
Click to collapse
Ah, I just looked in my platform-tools folder and there was adb etc. but I could not find fastboot. Where can I download that?
In the device manager, it's under 'Android USB Devices' as 'My HTC' is that ok?
OK, I have the SDK working fine, but when I go to this ( http://ks25738.kimsufi.com/misc/index.php ) website to get the .img file I need I can't figure out my kernel/ROM number - in the settings it says:
Android Version
2.3.4
Baseband Version
32.54.00.32U_5.14.05.17
Kernel Version 2.6.37.6-cyanogenmod-01494-g8dc02ff
[email protected]
Build Number
MIUI.1.6.17
The wesbite states the number should be 10 characters long, anyone know which one the ROM number is?
Thanks
You are once again trying to flash an RUU. Do not do this without first fixing your SD card problems.
fastboot oem enableqxdm 0
and also
fastboot oem eraseconfig
Need more details on where you are at. If you don't fix the issues you have then flashing an RUU could leave you in a much worse situation than you are now, and where you are now is easily fixed!
Parva4 is right.. you should 1st try enabling your sd card....
what you need to do is...
first download adb drivers for your device...
power on your phone into fastboot.. by pressing volume down and power.. connect usb cable to pc.. and in device manager.. update driver to adb driver.. while in hboot.. and than run that fastboot command which Parva4 mentioned.
I sorted it out, thanks to all who helped!
I did the fastboot enableqxd 0 command to unlock the SD card then once that was able to be used I flashed back to a nand backup I had made minutes before I did the flash that went wrong and now it's working fine!

[Q] Soft-bricked my HOX, solutions exhausted

Hi guys,
Just wanted to put it out there that I'm totally new at this rooting, custom ROM thing, and I got excited which led me to fail the number ONE rule of backing-up your phone!
Anyways, here's the situation
- Rooted my HTC One X
- Tried to install a custom ROM (IceCold Jelly)
- Phone went into bootloop, after the pink unicorn screen
Some facts
- I can get into the bootloader
- When I plug the phone into the PC, PC makes a sound, but it does not recognize the phone at all
- PC detects a "fastboot" device, but no phone
- went through a few "How to save a soft-bricked" phone tutorial to no avail
- fastboot cmd stuff don't work
- i have boot.img, fastboot.exe etc all on my pc
- drivers and htc sync up to date
I'm sorry if its been answered, but in the bunch of threads I've looked at, everything revolves around being able to use the CMD and the PC actually detecting the phone. Couldn't find any way of fixing my phone, as I said above, the PC doesn't register that theres anything connected to it.
I'd appreciate some help, its been a couple of days, and having no phone is really really hurting!
I'm really really new at this, so I apologize in advance if I don't really understand the terminologies used!
Thanks in advance!
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Michealtbh said:
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Click to expand...
Click to collapse
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
appasionata said:
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
Click to expand...
Click to collapse
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
appasionata said:
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
Click to expand...
Click to collapse
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
Michealtbh said:
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Click to expand...
Click to collapse
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
Go to the folder with boot.img and fast boot exe, hold shift and press right mouse button on this folder. Than choose run cmd here (or smthng like this, I don't know how it called in English). Than type commands
Sent from my HTC One X using xda app-developers app
If you'd like a hand, I could help you do it remotely via TeamViewer.
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Michealtbh said:
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Click to expand...
Click to collapse
Thanks for the help guys, I'll keep trying and will let you guys know. I think the root of the problem is that I'm inputting the fastboot commands right as I enter the cmd prompt from the windows search bar.
Will keep you guys posted, thanks for the help so far. Don't have my phone on me this minute as its with my friend whos trying to fix it too, will get it back in the morning!
Alright,
I've tried it now, and now theres a different problem. When I try to get into recovery from the bootloader, a picture of a htc device and red triangle and exclamation mark appears. And the custom rom load screen no longer appears. PC still does not recognize the phone.
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
incident said:
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
appasionata said:
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
Click to expand...
Click to collapse
I think he means that have you unlocked your bootloader via the htcdev.com website?
Sent from my HTC One X using xda premium
OP's first post states that he tried to install a rom, so his bootloader must be unlocked and a custom recovery must have been installed at some point.
@OP - all you have to do is download a custom recovery (CWM or TWRP) then flash it using "fastboot flash recovery nameofrecovery.img", then follow the steps previously explained to you in this thread.
Problem is though he says he rooted HOX he has no idea about unlocking bootloader at HTC Dev? So when he says he's rooted did he unlock the bootloader? He mentions he has an "operator" unlocked phone, and I think this is where he's getting confused. Otherwise suggesting further flashing will make a bad problem worse.
Also it sounds like he's trying to run CMD from start menu. He needs to run it from from where the fastboot file is located, or at least "point" to it in CMD.
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
If you can get into bootloader as you stated have you tried a factory reset?
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
andyharney said:
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
Click to expand...
Click to collapse
Thanks, I really appreciate it, I think I might have to resort to this. How do we go about it? shall we talk about it via PM? I'm pretty busy this whole week, so we can do it on the weekends?
Looks like you have a stock recovery, try to install the correct RUU (stock ROM for your phone, manuals, can be found in a sticky post of the ROMs thread). So first get back to stock, then start over and read the f**king manuals very carefully. no offence.
If you don't know what you are doing, please don't start at all.
Manuals: http://forum.xda-developers.com/showthread.php?t=1832891
Sent from my HTC One X using xda premium

[Q] Fastboot cannot find device (Ubuntu/Win7)

Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
neutrino37 said:
Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
santod040 said:
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
Click to expand...
Click to collapse
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
BygSii said:
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
Click to expand...
Click to collapse
ADB works fine over USB 3.0 for any Android device if you have the proper drivers installed. If you have a mixture of 2.0 and 3.0 ports, as I do, use the 2.0, as it is more reliable, though slower. I'm using ADB on my device via USB 3.0 as I type this, using Windows 7 x64.
If your motherboard has an Intel chipset, you can try this method to get Fastboot working over USB 3.0, just disregard the download links about making it work on Windows 8, as the drivers were designed for Windows 7. My motherboard has an Asmedia USB 3.0 controller, and I am unable to use the Intel drivers, and thus unable to use Fastboot over USB 3.0, which isn't really a problem for me, as I also have the USB 2.0 ports.
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
kdj67f said:
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
neutrino37 said:
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
Click to expand...
Click to collapse
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
neutrino37 said:
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
Click to expand...
Click to collapse
Open a terminal emulator on your phone then get root access:
su
After that, cd to the location of the .img file: (i.e. if it was on the root of the sd card then...)
cd /sdcard/
Finally, flash the image to the recovery partition:
dd if=recovery.img of=/dev/block/mmcblk0p21 (not sure if this location will be different on this phone..someone else may want to chime in)
Then exit the terminal emulator and reboot.
IceDragon59 said:
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
Click to expand...
Click to collapse
Thanks, not clicking the reboot made it work with fastboot (even in Win7!). I was confused by the statements about rebooting "into fastboot" and assuming that once it displayed "fastboot USB" I should reboot. Took me 2 seconds to install TWRP once this PEBKAC was resolved .
I would've tried the dd option from the terminal, but I'm glad I didn't have to (have used that wrong once on a Linux system and it was not pleasant!).
Glad you figured it out, even with my typo!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Commands
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Hi, I have been trying to debrick my tp and I've posted in forums asking basically this question.. seems it goes fine till failed to install/find Fastboot.. would you send me the command? thanks..

Can you ADB push files to the sd card without an OS installed???

I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.
DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles
Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5

Im having trouble with fastboot when returning to stock

Hi guys, i want to return to stock (i.e relock my bootloader and install stock oxygenOS) but i cant get my laptop to recognise my op3 whenever i type "fastboot devices" in cmd. Ive tried multiple programmes to install the correct drivers but it just doesnt seem to work.
Has anyone had similar problems or any solutions??
Im currently running windows 10 on my computer
Thanks
Do you have fastboot / adb tools installed and phone is in fastboot mode?
What does it say when typing fastboot devices?
Thanks for the reply, I type fastboot devices and nothing follows just another line to type a command. I'm pretty sure I have adb/fastboot tools installed, I used an installer which was linked on another thread
cl0g said:
Do you have fastboot / adb tools installed and phone is in fastboot mode?
What does it say when typing fastboot devices?
Click to expand...
Click to collapse
Do I need to be on a stock version of OOS in order to get my laptop to recognise my device in fastboot?
afrolong said:
Do I need to be on a stock version of OOS in order to get my laptop to recognise my device in fastboot?
Click to expand...
Click to collapse
No. Thats independent of OS
Are you in the fastboot/adb folder, where fastboot.exe is, when typing in cmd?
The mode where you should be is called "bootloader" on the phone.
cl0g said:
No. Thats independent of OS
Are you in the fastboot/adb folder, where fastboot.exe is, when typing in cmd?
The mode where you should be is called "bootloader" on the phone.
Click to expand...
Click to collapse
Yeah that may be the problem, would you mind directing me as to where I can find this fastboot/adb folder so that I can determine if I've even installed it properly haha
Well, if the cmd does not say something like "fastboot was not found", then that might not be the problem.
In which state is the phone, when trying fastboot?
Wrong drivers... Make sure you install the right one. Preferably follow the first few steps of the unbrick guide go get the right ones.. You are probably using the ones by Windows which do not work.
Puddi_Puddin said:
Wrong drivers... Make sure you install the right one. Preferably follow the first few steps of the unbrick guide go get the right ones.. You are probably using the ones by Windows which do not work.
Click to expand...
Click to collapse
Thanks for the help got it all sorted, had to select the correct drivers in Device Manager when i plugged the phone in in different states.

Categories

Resources