i finally got my drivers to work for adb with my mt4g but now when i "adb devices" it shows up but it says "offline" how do i get it to online?? please help!
OMG, im sorry i dont have an answer but im having the same problem. actually adb devices is working but when i try to flash a splash screen thru adb and fastboot, all goes well then i get "waiting for phone" then nothing. i have redownloaded drivers and nothing is working. this is a replacement phone and my other phone before this one had no problems like this
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
read the update on after 6. i followed this steps and didnt have a problem.
Related
First let me get the stats out of the way in case it's a compatibility issue (doubtful):
Mytouch 3g 32b
Hboot 1.33.2005
Radio 2.22.23.02
Running on the last cm6 nightly (307, i believe)
Using this kernel: http://droidbasement.com/db-blog/?p=1531
All flashed through recovery.
Ok, so the problem..
Following this guide, http://forum.xda-developers.com/showthread.php?t=532719, I successfully got the ADB to work properly (calling "adb devices" on a terminal returns my device). However when I boot the phone into fastboot, connect it to the PC via USB and call "fastboot devices" through the terminal (yes, I first cd to the android-sdk/tools folder), it returns nothing. Calling something like "fastboot reboot" simply returns "<waiting on device>" indefinitely.
I googled for HOURS last night searching for a solution but to no avail. I uninstalled the drivers via the Device Manager and tried the PDANet method, but nope. Uninstalled drivers again, rebooted everything, and reinstalled using the method posted in the above guide again, pointing it to the google/usb_drivers folder, just in case I had f*'d up somewhere along the way. I just ended up with the same problem. ADB works. Fastboot doesn't. What am I doing wrong? :/
Basically, I'm stumped. While it's not completely necessary to get this working, I'd like to free up some ram on my phone (http://forum.xda-developers.com/showthread.php?t=831139) and for this I need fastboot. I'm not that noobish so I'm willing to experiment. Any help is appreciated.
Nobody? :/
Thanks to my persistence I finally got it working. I'll share in case anyone else has the same problem.
Apparently there were still old HTC related devices under the Device Manager that would not show even when I clicked on "Show hidden devices." I fixed this by adding a new system variable.
Variable name: devmgr_show_nonpresent_devices
Variable value: 1
This allowed me to see a bunch of HTC labeled grayed out devices under 'Disk drives' and under 'Universal Serial Bus controllers,' some grayed out USB Mass Storage Devices and one USB Composite device which I believe was also a culprit. Uninstalled all of them.
I then restarted the process of setting up ADB using these drivers, mediafire.com/?wzdjcmowziw, which I got from the guide I link to in the first post. Then when I hooked up the phone to the PC under fastboot mode, I used the drivers supplied by PDANet. Worked immediately.
Thanks for all the help. (sarcasm)
Hi,
I own an HTC Panache, never rooted it or anything. Yesterday I factory reset my phone, battery must have died while trying to sync all my apps. Now the phone won't turn on or charge (no indicator light for charging). I tried to load into recovery, doesn't work either. When I plug it into my computer it get's recognized in device manager as "other device" even though I believe I have the drivers installed, and it won't try to mount the sd-card. Finally "adb devices" will return nothing in cmd.
Do you think it's a dead battery problem, and could I recover from this?
Thanks,
Corey
corey.t.m said:
Hi,
I own an HTC Panache, never rooted it or anything. Yesterday I factory reset my phone, battery must have died while trying to sync all my apps. Now the phone won't turn on or charge (no indicator light for charging). I tried to load into recovery, doesn't work either. When I plug it into my computer it get's recognized in device manager as "other device" even though I believe I have the drivers installed, and it won't try to mount the sd-card. Finally "adb devices" will return nothing in cmd.
Do you think it's a dead battery problem, and could I recover from this?
Thanks,
Corey
Click to expand...
Click to collapse
I just wanted to add that my computer is recognizing the device as "QHSUSB_DLOAD"
I found this link that makes it possible to undo this for the HTC Sensation, has anyone tried this on a panache/mytouch4g
http://forum.xda-developers.com/showthread.php?t=1522351
what do u mean by "adb devices" will not return anything?
just so its clearer for others....
u didnt root but installed adb drivers properly? (or just opened cmd & typed adb devices?)
here is a link you can try to make sure u have adb installed correctly & try to downgrade to stock with temp root...or just might as well go all the way
Hello,
First of all, the problem started when Android Kitkat update ota came to my device. After downloading it, my device was not able to verify it, as a result of which, it started downloading the update all over again. It downloaded the update more than 10 times without any success.
So finally I decided to sideload it. I set up everything properly, double checked everything. As I was going to send the update.zip to my tablet through command, the cmd prompt showed me "error: device not found".
I restarted the device, checked the drivers in my computer, even checked whether adb recognized it by commanding "adb devices". It did.
So again I turned it off, entered fastboot mode, But this time before entering recovery, I connected the device (it gave the connecting sound as on Win7). I ran the command "adb devices" and it showed no device at all!
My device is complete stock, unrooted. Usb debugging is turned on and MTP is selected.
Use a toolkit to install\test adb drivers then slide load using it. Some times windows install some crap adb drivers u have to remove them and install the naked drivers.
Toolkit is in development section.
I tested with wugfresh toolkit.
Please ignore my spelling mistakes. English is not my native language.
Hi xda community,
I have always sideloaded the OTA in recovery using a Windows machine. Yesterday, I tried to use my Chromebook running Ubuntu. I can see my device when Android is up and running (meaning Android is running and not in recovery or bootloader) by typing "adb device" using the terminal within Ubuntu. The problem I'm having is not being able to see my device when in Recovery mode and selecting the sideload adb mode.
$adb devices
List of devices attached
<---------this line is blank
$adb sideload update.zip
error: device not found
I've made sure /etc/udev/rules.d/51-android.rules are configured. I also checked the post regarding .android/adb_usb.ini but this is only for the Nook and should not apply to the Nexus 6P.
I also tried adb kill-server and adb start-server with no luck.
I've read post about being able to see the device in fastboot. I tried this as well and can't see the device either. My device does not have an unlocked bootloader but this should not matter. The device doesn't need to be for a sideload. This worked in Windows with no issues. You might ask, what is the problem then? I just want it to work in Ubuntu.
Does anyone have any suggestions on how I can fix this?
Thank you in advance for just reading.
After some more searching I found a suggestion to run the following command and it fixed my problem:
/etc/init.d/udev restart
http://android.stackexchange.com/questions/58187/adb-can-discover-devices-but-not-fastboot
My Acer Chromebook 11 only has two ports: 2.0 and 3.0 USB. I noticed the device would not show up after typing in "lsusb" which would normally show the Google device. I unpluged the USB cord from the 2.0 and plugged it into the 3.0. I read another post online stating this sometimes causes the problem.
When in fastboot I can type "fastboot devices" and "adb devices" in recovery and my device now shows up.
I hope this helps someone. Thank you all.
Mods feel free to close out this thread.
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)