So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium
C-4Nati said:
So I'm trying to flash the L preview. I plug my n7 in and do adb devices and it shows up, I adb reboot bootloader and it boots into the boot loader, but while in it if I do adb devices nothing comes up and if I do the flash-all.bat it just stays stuck on waiting on device. And yes I have USB debugging, and just updated drivers and installed SDK fresh. This just seems odd.
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.
mdamaged said:
When you are in bootloader mode, the correct command to list devices is: fastboot devices
Let me know if that command gives you a device id.
If it does not, then you must get your drivers situated.
Click to expand...
Click to collapse
Well not working while using the flash-all.bat would still indicate it's not recognized in boot loader mode. Which is weird when it is while its on.
Sent from my LG-D801 using xda premium
Any ideas?
Sent from my LG-D801 using xda premium
C-4Nati said:
Any ideas?
Sent from my LG-D801 using xda premium
Click to expand...
Click to collapse
I already suggested what needs to be done, you need to get your drivers working correctly. There are different drivers for the different modes.
Here is what I did to get my N7 2013 recognized in every possible mode: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
Do you have a syncing program for your handset/tab installed?
If so I'd uninstall it as they tend to take over the USB when you plug your device in, changes the USB port com ID and only meant for an up and running system and not in bootloader/recovery/etc
As for an actual response as in an ID/model/etc using adb or fastboot I've never seen it shown when I've tried it even with official and unofficial drivers others have had responses with!! ..but not had any problems flashing except with a sync program on pc
(personally never use sync progs since then )
Bashing away at my HTC Desire C
Related
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
David 617 said:
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
Click to expand...
Click to collapse
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.
try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.
^Ninja'd lol
fastboot devices comes up blank.
in device manager my phone comes up as other devices - android 1.0
i guess my driver is bad. where can i get a good one?
(i just installed the one from samsung.. same thing.)
what have you used
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Randroidran said:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.
I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.
thx ill try now
.
.
.
works!
thx a million
I did the stupid mistake of deleting everything on my phone from my pc, and i can't remember correctly but i did something else, now my phone is not recognized by my PC. I have a rooted samsung galaxy nexus. and i installed the driver for my phone. My pc recognizes the device on the device manager but i can't find it on my computer unfortunately. there is an entry in the device manager says (Android device 1.0 with an exclamation mark).
Thanks in advance.
Sounds like your fastboot driver may not be installed. Try uninstalling and reinstalling them. If you are using a Windows 8 machine it seems like there's also an extra step. efrant has it here.
http://forum.xda-developers.com/showthread.php?t=1812959.
Sent from my Galaxy Nexus using xda premium
Pierceye said:
Sounds like your fastboot driver may not be installed. Try uninstalling and reinstalling them. If you are using a Windows 8 machine it seems like there's also an extra step. efrant has it here.
http://forum.xda-developers.com/showthread.php?t=1812959.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Still nothing, i followed the steps in this and nothing, I can boot the phone to recovery nothing more, I just need to see my phone in My Computer that's all.
Unplug your phone from the PC. Power down and reboot to fastboot(power+volume up+volume down) then plug it into the PC again. Does the "Android 1.0" designation change to "Galaxy Nexus?"
Sent from my Galaxy Nexus using xda premium
Pierceye said:
Unplug your phone from the PC. Power down and reboot to fastboot(power+volume up+volume down) then plug it into the PC again. Does the "Android 1.0" designation change to "Galaxy Nexus?"
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If i am in boot loader screen, there is (Android device), and under it samsung galaxy nexus bootloader interface.
But if i go so recovery mode it changes to samsung android ADB interface no exclamation marks. Still nothing on My computer
ErMaX83X said:
If i am in boot loader screen, there is (Android device), and under it samsung galaxy nexus bootloader interface.
But if i go so recovery mode it changes to samsung android ADB interface no exclamation marks. Still nothing on My computer
Click to expand...
Click to collapse
It won't show up under my computer *face palm*, you need to use fastboot or adb to interact with the filesystem.
No exclamation mark means a driver is installed. You don't have fastboot driver installed. Reboot to recovery, use adb. Reboot to bootloader, use fastboot.
Sent from my i9250
bk201doesntexist said:
It won't show up under my computer *face palm*, you need to use fastboot or adb to interact with the filesystem.
No exclamation mark means a driver is installed. You don't have fastboot driver installed. Reboot to recovery, use adb. Reboot to bootloader, use fastboot.
Sent from my i9250
Click to expand...
Click to collapse
Now i have (Portable devices) MTP USB device (with exclamation mark) which is the problem. i am new to those stuff and from what i understand my PC can not communicate with my phone because of that. Please the drivers can not install the MTP section.
trying desperately for s-off. adb finds my device but says its offline. I'll follow any instructions cause ive tried everything and cant get it to be seen as online. please and thanks
zeer.row said:
trying desperately for s-off. adb finds my device but says its offline. I'll follow any instructions cause ive tried everything and cant get it to be seen as online. please and thanks
Click to expand...
Click to collapse
http://www.wugfresh.com/faq/7/
Have you already Tried this?
Sent from my ADR6300 using xda app-developers app
Tigerstown said:
http://www.wugfresh.com/faq/7/
Have you already Tried this?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
just looked at it. yes i accepted the prompt already and i can see my device when i list, but its listed as offline.
zeer.row said:
just looked at it. yes i accepted the prompt already and i can see my device when i list, but its listed as offline.
Click to expand...
Click to collapse
I get this occasionally on a different device. But if I unplug and then plug it back in again, sometime takes more than once, it works
Sent from my Nexus 5
jd1639 said:
I get this occasionally on a different device. But if I unplug and then plug it back in again, sometime takes more than once, it works
Sent from my Nexus 5
Click to expand...
Click to collapse
ive been at it for 4 hours
heres a pic
zeer.row said:
ive been at it for 4 hours
Click to expand...
Click to collapse
Do you have usb debugging enabled?
Sent from my Nexus 5
jd1639 said:
Do you have usb debugging enabled?
Sent from my Nexus 5
Click to expand...
Click to collapse
yes, and unknown sources checked , and unchecked verify apps
zeer.row said:
yes, and unknown sources checked , and unchecked verify apps
Click to expand...
Click to collapse
And you're using the same cable that came with the phone? Also use usb 2.0 not 3.0 ports. These are the only things I can think of.
Sent from my Nexus 5
ADB
If you are trying to connect ADB for Weaksauce, you have to open apps folder,
run Weaksauce and accept prompt,
then run SU and accept prompt,
Then start giving your ADB commands.
just download drivers straight from htc thats all
I had the same problem at first. Then I installed Android SDK and copied the path to where the folder is on my C drive. Afterwards, Turned OFF USB Debugging, used the "revoke usb authorization" option, then Turned On USB Debugging on the phone again and the Key Verification window popped up on my phone and selected "ALWAYS" for adb to be used on the attached computer. Then tested with the command "adb devices" and now my m8 is all good and ready to go. No more offline or unauthorized.
has to be a driver situation thats stuck on my pc, used another laptop (different computer) downloaded latest sdk n it worked. this can be deleted. genuine thanks to everyone who gave input!!
michaelbsheldon said:
If you are trying to connect ADB for Weaksauce, you have to open apps folder,
run Weaksauce and accept prompt,
then run SU and accept prompt,
Then start giving your ADB commands.
Click to expand...
Click to collapse
I'm not using weaksauce because I wasn't sure if it worked on a Sprint phone. Does it?
thendyy said:
I'm not using weaksauce because I wasn't sure if it worked on a Sprint phone. Does it?
Click to expand...
Click to collapse
Just checked at the weaksauce website, and it says that it 'may' work for sprint.
If yours isn't running newest HTC releases for your phone, weaksauce could work.
I'd try it: worst thing that could happen is that you'd have a do a factory reset from hboot.
Best wishes -
mike
I got the offline message also and found out that i have to disable my USB 3 driver in Device manager.
When they are disabled i can use adb to my phone.
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Are you using a pc running Windows 8. That was my problem. Worked fine on an old laptop running Windows 7
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
same happened with me. It turned out there was a prompt on my M8's screen asking for permission for my computer to use USB debugging. I gave it access and adb was working fine.
I had the same problem on windows 8. I installed HTC sync and everything worked fine.
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
grentuu said:
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
Click to expand...
Click to collapse
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
grentuu said:
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
Click to expand...
Click to collapse
I had the same issue on my Windows 8 pc.. I was able to rectify the adv device not found issue by going into device manager , clicking on the HTC one icon and manually installing the drivers by browsing through my computer and using my Nexus adb drivers and everything worked fine after that
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
umjammerlammy said:
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
Click to expand...
Click to collapse
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Canadianreaper said:
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Click to expand...
Click to collapse
Glad I could help!
I had the same problem using Windows 8.1. adb and fastboot were definitely installed correctly as I already used them for flashing other ROMs on my Nexus 7. The solution in my case was to download and install the HTC Sync Manager. After installing the hsm the adb and fastboot commands worked perfectly.
Best regards,
B.
I recently soft-bricked my KF2 while trying to install 2nd-bootloader on it (solid red screen). I just plugged it into my computer via a fastboot cable and it got to the fastboot screen perfectly fine. From here, I cannot access the device to recover it.
Any fastboot command gives me "Waiting for Device"
fastboot devices returns a blank line
It's listed in Device Manager as otter2-prod-4 and I can't seem to get any drivers working for it.
Does anyone know if there's anything I can do about this?
DoctorDelta said:
I recently soft-bricked my KF2 while trying to install 2nd-bootloader on it (solid red screen). I just plugged it into my computer via a fastboot cable and it got to the fastboot screen perfectly fine. From here, I cannot access the device to recover it.
Any fastboot command gives me "Waiting for Device"
fastboot devices returns a blank line
It's listed in Device Manager as otter2-prod-4 and I can't seem to get any drivers working for it.
Does anyone know if there's anything I can do about this?
Click to expand...
Click to collapse
Make sure you're using the -i 0x1949 parameter in your fastboot commands. If that isn't helping, we can continue with driver installation. Do let me know if you're using Windows 8+/10, as the driver installation process will require an extra step for those Windows versions.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Make sure you're using the -i 0x1949 parameter in your fastboot commands. If that isn't helping, we can continue with driver installation. Do let me know if you're using Windows 8+/10, as the driver installation process will require an extra step for those Windows versions.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I have same problem. But my pc do not recognize my kindle as otter2-prod-4.
Any Help?
bachmx said:
I have same problem. But my pc do not recognize my kindle as otter2-prod-4.
Any Help?
Click to expand...
Click to collapse
If you're using Windows 10, you need to disable driver signature enforcement in order to install the Kindle drivers. Here's a tutorial to do just that. After the reboot, install the drivers like normal and then reboot. After that, your kindle should be recognized.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you're using Windows 10, you need to disable driver signature enforcement in order to install the Kindle drivers. Here's a tutorial to do just that. After the reboot, install the drivers like normal and then reboot. After that, your kindle should be recognized.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I did it. Then I installed drive download from here: http://forum.xda-developers.com/showthread.php?t=2544410.
But nothing work.
Please see attachments.