If you have help, thank you. If not, just move on. I'm asking for an answer, not a smart ass remark. And yes, I know I'm an asshole. :laugh:
Anyways...
My computer won't recognize my phone when it is in fastboot. I've looked at other threads saying that Windows 8.1 (my computers OS) will not work with ADB, but I no longer have that problem. Fastboot still doesn't work however. Any direct answers? Can you point me to a thread that will help?
Much appreciated.
Do you have the proper drivers? And are you using using the correct "fastboot devices" command?
Sent from my HTC One XL using XDA Premium 4 mobile app
pandasa123 said:
Do you have the proper drivers? And are you using using the correct "fastboot devices" command?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Proper drivers are installed. (99% sure about that) And I am using the right commands. Nothing comes up with "fastboot devices" and any other fastboot command just says "waiting for device"
Hmm...are you in fastboot usb or just bootloader only?
Sent from my HTC One XL using XDA Premium 4 mobile app
pandasa123 said:
Hmm...are you in fastboot usb or just bootloader only?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot USB
ConnorAAVance said:
I've looked at other threads saying that Windows 8.1 (my computers OS) will not work with ADB, but I no longer have that problem.
Click to expand...
Click to collapse
If still on Windows 8, my guess would be that is the culprit.
ConnorAAVance said:
And yes, I know I'm an asshole. :laugh:
Click to expand...
Click to collapse
Not really. fastboot and adb can be amazingly finicky, and I've had any number of the "usual" fixes not work for me. And your issue with adb working, and fastboot not is a little curious (the opposite or both not working seem to be the much more common cases).
But I can appreciate your . . . uh . . humbleness.
redpoint73 said:
If still on Windows 8, my guess would be that is the culprit.
Not really. fastboot and adb can be amazingly finicky, and I've had any number of the "usual" fixes not work for me. And your issue with adb working, and fastboot not is a little curious (the opposite or both not working seem to be the much more common cases).
But I can appreciate your . . . uh . . humbleness.
Click to expand...
Click to collapse
That's how it was for awhile. ADB and fastboot would not work, but i downloaded the current SDK and the update for HTC Sync and that fixed my ADB problem. The fastboot just didn't change. I've been wanting to go back to Windows 7 for quite some time now; I guess this problem is whats going to get me to do that.
I had a lot of trouble with my computer not recognizing my phone in fastboot also. I have a windows 7 laptop with windows 8 as a dual boot. When trying to s-off my phone, windows 7 wouldn't recognize my phone. I ended up doing the s-off process with windows 8 as everything worked fine there. I definately think the problem with yours is windows but not necessarily windows 8. What I would do if i was you is partition the hard drive, get a copy of windows 7 and install it to the new partition. A fresh copy of windows could make the difference. Either that or you could back up your hard drive and do a factory restore with windows 8. The dual boot is better because if you have problems, with one, you can boot up the other operating system and try again. Just a suggestion.
Or you could just download VirtualBox and install Ubuntu virtually, then download ADB and away you go. A lot easier than dual-booting two OS's that are essentially the same..
Related
I missed out something i think.
I have my sdk, with those files.
I went to cmd and type the commant
bla bla bla
fastboot devices >>> no error, means connected
fastboot oem unlock
>>>> it is connected but why it still waiting for my device?
I added the path to the system too, but still cant get rid of
I search the net and I cant get the solution.
Any idea anyone?
What drivers did you install? And yes, I read the "fastboot devices"
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Phone has to be in bootloader mode?
Sent from my Nexus S using XDA App
yup.. it is in volume up + on mode.
If you plug your NS in and look in the Device Manager, do you see an unknown device with the question mark? If so, you should try to manually install the driver located in android-sdk-windows\extras\google\usb_driver
And when you issue the command
Code:
fastboot devices
It should display your NS device id, not just a blank line.
melvinchng said:
installed everyhing...
samsung adb + google package
samsung driver
pdanet
Click to expand...
Click to collapse
"samsung" driver... no
you use the drivers obtained from the Android SDK or PDAnet
Pretty much what suksit said.
Try pdanet! Last place i go y find drivers
Sent from my Nexus S using XDA Premium App
I tried sdk driver, pdanet driver. I can't unknown driver, it is listed as android. Means my phone is found by computer
I have android 2. 3. 4. Does it effect?
Sent from my Nexus S using XDA Premium App
Just curious, did you enabled the option in Settings > Applications > Development > USB debugging?
In Device Manger it should say something like "Android Composite ADB Interface"
I enabled it too... maybe I will try to reinstall and root it via my XP in VM.
I rooted my wildfire with this pc last time, maybe the drive mixed up.
Sent from my Nexus S using XDA Premium App
Just noticed that your location is in Malaysia. Could it happen that you have the i9023 (SLCD) model? If that's the case then I think you should try this.
Ya, I bought slcd set.
I will try it tomorrow at night and report back to you guys.
--------------------------------
It is really strange. Tried everything and won't work.
Pdanet detected my device that it is connected to computer, but it just show wait for device.
----------------------------------------
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
melvinchng said:
Ya, I bought slcd set.
Edit: my full charge is 95%, it is normal right?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yeah thats normal, Samsung did some weird battery calibration thing!
However people here have found to get 100% or close to it.
When charging just leave screen on for 1 hour and have tethered wifi On, so far im charging full up to 98%, just waiting to squeeze in the last 2%.....could take awhile.
and yeah the 95% charge is normal. heres a explanation in further detail
Your battery gauge is lying to you (and it's not such a bad thing)
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
j0l6 said:
make sure u have following dlls in fastboot folder
AdbWinUsbApi
AdbWinApi
Click to expand...
Click to collapse
i have these in tools. and still waiting for device.
anyone any idea?
I forgot to tell you guys that my windows is 64-bit
Sent from my Nexus S using XDA Premium App
Try this or this then (the latter is quite hard to read anyway, I think they messed up the code formatting)
Unlocked bootloader!
thanks!
Sent from my Nexus S using XDA Premium App
melvinchng said:
I haven't root yet.
After I root, my storage and Rom will be wipe? So I need to install new Rom?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Rooting will add su binary and Superuser app to your NS. But your data will be wiped (both on phone and SD card) when you unlock the bootloader -- it's the same as doing a factory reset. However, your system partition will not be affected so no need to install new ROM if you prefer using stock.
Im using the revolutionary method i get my beta key.
when i run the program it type in my beta key, and it accepts it and the comes up with ''zerging root. . . this might take a minute or so. . .'' but nothing happens and it stays like this. is it supposed to boot into bootloader or something? i have usb debugging enabled. and im on htc sync mode.
Did you install USB driver on rev site? Happenned to me when I try rooting it.
Sent from my HTC Sensation 4G using XDA Premium App
Shouldn't be in Sync mode, just connect it in charging mode
Ive tried what both of you have suggested but its still the same? is usb debugging supposed to be on or off?
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
EddyOS said:
USB Debugging = ON
Seriously, read the guide - http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
Thats the guide im following and its not working. My galaxy s2 was a piece of cake to install a custom rom on
it works perfectly up to the point when i type in the beta key? which i know im doing it correctly.
it just hangs there? also when i boot into fastboot it has ***LOCKED*** at the top in pink, so does this mean i need to unlock my bootloader first?
No, it gets replaced with 'Revolutionary' once done.
Try a different USB port/PC
Just calm down and take a break, then re read the instruction. You must miss something
Sent from my HTC Sensation 4G using XDA Premium App
still no luck, and i have no idea why accept this sort of thing always happens to me ive managed to root a desire z in the past so this shouldnt be a problem on my laptop because it worked fine before?
This what comes up
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
dav08094194 said:
This what comes up
Click to expand...
Click to collapse
Your phone gonna reboot into HBoot a few time to get root. Are you seeing your phone reboots?
Sent from my HTC Sensation 4G using XDA Premium App
EddyOS said:
We know what's coming up, that's normal. Have you tried a different USB port/PC at all?
I take it you're using Windows 7. If so, run your DOS prompt as an Administrator
Click to expand...
Click to collapse
Yeah windows 7 and ive tried all 3 usb ports. not sure what DOS Prompt is but im running the program as administrator anyway.
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
EddyOS said:
Then I suggest trying a different PC. Although, have you always tried it as Admin? Funnily enough it worked for me once I STOPPED using Administrator rights
Click to expand...
Click to collapse
got it to work in the end. i had to install windows 7 on my linux ubuntu pc
Hi there,
I was trying to change the splashscreen with use of adb, when i tried to reboot into bootloader the error devices not found poped up, i thought well no worries ill do it myself then. When in fastboot usb mode it still doesn't find it. things u tried:
usb mode by recovery
usb mode by fastboot
normal usb at homescreen
charging mode
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
------------------------------------------------------------------------------------------------
i can only check this question again later tonight.. (gst 1+) so ni about 4 to 5 hours.
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
azzledazzle said:
use this instead. Much easier and friendly
http://forum.xda-developers.com/showthread.php?t=794638
Click to expand...
Click to collapse
+1 on you but i need it for other things to like superCID/making superCID undone...
i did try adb that comes with sdk stuff...
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
azzledazzle said:
Arrrr i see.
Well dowload ADB again, make sure drivers are upto date, Make sure ADB is in the correct location. And always make sure the commands are correct.
Click to expand...
Click to collapse
check,check,check
if adb devices gives nothing and adb reboot bootloader neither then i guess it doesnt lie down to my adb drivers, since i used them before my laptop just randomly blanked itsself and i needed to get everthing up and running again
You got USB Debugging checked ??
azzledazzle said:
You got USB Debugging checked ??
Click to expand...
Click to collapse
myself said:
Hi ...
htc sync mode
i did check usb debugging and it was checked
i run OrDriod 2.0.1(2.0.2 in a couple of min) FW 3.32 bricked 0.65 kernel
Click to expand...
Click to collapse
that must say it?
haha sorry i didnt read that bit lol....
azzledazzle said:
haha sorry i didnt read that bit lol....
Click to expand...
Click to collapse
np i just need it working again since that flash tool for splash screen doesnt work ether
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
azzledazzle said:
android flasher works perfect , I was using it less than 10 mins ago....
ADB not working - Android flasher not working ... Seems like some issue with your PC / Drivers
Click to expand...
Click to collapse
i thought more of the phone
Possibly,, But providing USB debugging is checked, And there seem to be no other faults / problems with the phone, I cant figure out what could be causing this ?? On the phones part i mean.
Damn i really need adb fixed got a kinda ride splash screen and every watches my screen...
Sent from my Sensation using xda premium
ADB is in the right location yeah ?
what error does android flasher give (if any)
Non just cant go further then starting the daemon srrver because there is no phone connected in fastboot usb mode xD
Sent from my Sensation using xda premium
did you uncheck the 'im already in fastboot' box on android flasher ?
Yes as well as check if devices are connected by adb was non
Sent from my Sensation using xda premium
Hmmmmm. Very strange.
What OS do you have on your PC ?
Btw updated to 2.0.2 with 0.7 bricked kernel
Sent from my Sensation using xda premium
Windows 7 64 bit
Sent from my Sensation using xda premium
I've tried a couple of various "naked" adb drivers, also the "Universal" adb driver from Koush ( http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/ ). No dice. Whenever I plug in the phone, my computer happily recognizes it as an MTP device and nothing else. Nothing comes up when I type "adb devices". I have tried rebooting etc. I even gave up and finally installed HTC Sync (bleh). Still nothing.
I'm running Win8 64-bit on my desktop and CleanRom 6.5 on my phone.
Any ideas?
loneBoat said:
I've tried a couple of various "naked" adb drivers, also the "Universal" adb driver from Koush ( http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/ ). No dice. Whenever I plug in the phone, my computer happily recognizes it as an MTP device and nothing else. Nothing comes up when I type "adb devices". I have tried rebooting etc. I even gave up and finally installed HTC Sync (bleh). Still nothing.
I'm running Win8 64-bit on my desktop and CleanRom 6.5 on my phone.
Any ideas?
Click to expand...
Click to collapse
Hopefully you have usb debugging enabled? You didn't mention if you did.
Also, HTC Sync would only make things worse as it interferes with the HTC driver while it's running.
I remember vaguely that there was a specific driver for windows 8? I could be wrong. I'll search for it for you when I get a moment.
---------- Post added at 09:11 AM ---------- Previous post was at 09:03 AM ----------
loneBoat said:
I've tried a couple of various "naked" adb drivers, also the "Universal" adb driver from Koush ( http://www.droid-life.com/2013/04/08/koush-releases-universal-adb-driver-for-windows/ ). No dice. Whenever I plug in the phone, my computer happily recognizes it as an MTP device and nothing else. Nothing comes up when I type "adb devices". I have tried rebooting etc. I even gave up and finally installed HTC Sync (bleh). Still nothing.
I'm running Win8 64-bit on my desktop and CleanRom 6.5 on my phone.
Any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2074407&page=2&highlight=windows+8+htc+driver
That link has some ideas on fixing it with successes, so I would try that. If none of those work, you could create a VM with windows XP or 7 or ubuntu, or use an ubuntu boot disk.
Good luck.
exad said:
Hopefully you have usb debugging enabled? You didn't mention if you did.
Click to expand...
Click to collapse
Yes, it's enabled. Thanks for the reminder, though. I wouldn't put it past me to forget something like that!
Thanks for the suggestions.
I think I installed and then uninstalled HTC. That leaves the needed driver behind. I think I also had to switch my phone from MTP to mass storage.
Sent from my One X using xda app-developers app
lauterm said:
I think I also had to switch my phone from MTP to mass storage.
Click to expand...
Click to collapse
Hmmm, how do you do that?
loneBoat said:
Hmmm, how do you do that?
Click to expand...
Click to collapse
I too am curious about this. I didnt know you could on stock.
Sent from my Sony Tablet S using xda app-developers app
exad said:
I too am curious about this. I didnt know you could on stock.
Click to expand...
Click to collapse
(note that I'm not on stock. per my initial post, I'm running CleanROM 6.5.)
On CM you can go to settings > storage and hit menu and touch USB computer connection to change it.
Sent from my One X using xda app-developers app
loneBoat said:
(note that I'm not on stock. per my initial post, I'm running CleanROM 6.5.)
Click to expand...
Click to collapse
Cleanrom is pretty stock :d
Sent from my Sony Tablet S using xda app-developers app
Uninstall all of your ish drivers from the device manager menu. Don't worry they will reinstall then plug your phone on and it will install the drivers for your phone. That's how I fixed it .
-Sugardaddy
Thanks for all the replies. After a long, unreproduceable (because I have the short-term memory of a goldfish) series of installations/un-installations/reboots/cursing it magically started working. Go figure.
Thanks everyone!
usbdeview uninstall all the old htc devices from older drivers or rom changes then plug phone back in it will reconfig the drivers properly or atleast it should if you have the correct drivers installed
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than tried to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than trues to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Click to expand...
Click to collapse
Have you endabled USB debugging under Developer options in your Settings?
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
whozilla said:
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. That should get them working
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
whozilla said:
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry eddy. It seems you misread my posts. Im not having an issue understanding the difference between adb and fastboot. Allow me to clarify. While phone is on. With USB debugging enabled. I type
adb devices
in the command prompt under platform tools.. My device shows up and I have authorized it
When my phone is in the bootloader in fastboot mode. I type
fastboot devices
Nothing. That is my issue. Feel free to scroll back up and read the details. Any help is good help :beer:
Sent from my Nexus 5 using xda app-developers app
EddyOS said:
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
Click to expand...
Click to collapse
I quoted myself by mistake haha. PS
I have manually updated drivers. After uninstalling them to be clear. That's what I meant when I said I tried the universal drivers. For the record. All attempts I have made to get fastboot to recognize my device have been done using forums with detailed instructions.
Sent from my Nexus 5 using xda app-developers app
Sounds like Windows isn't wanting to use the driver. Manually update the driver and point it to the *.inf file in the SDK. It should then work fine
Solved. Such a small detail. Eddy you were right. Before I could see your post I realized. Vuala! I needed to update the drivers manually with the phone plugged in in fastboot mode!. That was my mistake. Cf root did the rest.
In device manager you will see a yellow triangle under other devices when the nexus is plugged in on fastboot mode. I installed drivers from the .exe found in this thread.tool adb fastboot drivers. I let the computer search on its own for updates. Done. Rooted
Sent from my Nexus 5 using xda app-developers app
jd1639 said:
Google tool adb fastboot drivers xda. That should get them working
Click to expand...
Click to collapse
Thank you sir. You lead me in the right path
Sent from my Nexus 5 using xda app-developers app