Develop Bugs

Bricked - Can I save my phone??

Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers

Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App

You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.

I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.

I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.

celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.

That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers

celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.

Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.

No worries. Glad you got it sorted.

I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?

[solved]win7 doesn´t recognizes my device into fastboot

okay ... a new question and also soo weird....
I want that my 2 PC´s recognize my device when its in bootloader mode
1º pc recognizes it well and its running UBUNTU.
2ºmy sister´s PC RUNNING WIN7 doesn´t recognize my DHD into bootloader mode.. but if i look the screen of the device the device automatically was changed his status to "HBOOT USB PLUG" but here is the problem:
When windoze7 detects and recognizes my device It issues a sound, but when I connect my DHD it issues different other one, that is to say detects it but it does not recognize her, then the usb mode I cannot use it
but if i boot my dhd and put her in debugging mode and run adb parameters windoze recognizes the device perfectly...
i am not an experienced user in windows
and i don´t know whats the problem. its strange..
any advise?thx in advance

Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?

Mr_JMM said:
Between you and the stickman you've had every problem going!!
Have you installed HTC Sync onto your sister's PC?
Why haven't you converted her to Ubuntu?
Click to expand...
Click to collapse
lololol we have a lot of problems Especially with windows i hate it
but she is afraid of not being able to handle it if I am not in house (SHE HAS ANOTHER DHD) in addition she likes the Microsoft OFFICE. LOL (and not open office)
Yes i had installed htc sync drivers, and sdk working well in usb debugging mode with the DHD turned on

Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?

Mr_JMM said:
Get to the stage you were at before:
fastboot
connect phone to PC
Phone says HBOOT USB PLUG
Using the Android-sdk shell
type
Code:
fastboot devices
Do you get a response?
Click to expand...
Click to collapse
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically

SERGI.3210 said:
yes i tried in fastboot mode but only says "list of attached devices" and nothing more... there aren´t devices in the list..
and if i write adb shell""" says ""not devices found"" logically
Click to expand...
Click to collapse
the problem appears into fastboot and into bootloader
ok in fastboot mode into sdk shell write fastboot devices and shows me a message:
"unable to initialize the aplication because ADBWINAPI.DLL not found

Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).

Mr_JMM said:
Ok, try this:
Create an Ubuntu live CD.... you can see where I'm going with that one.
Sorry buddy, will need to wait for some other poor sap that uses Windoze to pop along.
There was an old thread I read once and someone solved it by going to device manager and updating drivers or something for the "android device". <<-- Re your new post
Other than that, usual suggestion is try a different USB socket (different side of PC).
Click to expand...
Click to collapse
ok tried another socket but the PC says to me :LOL
good idea mate... if i create aN ubuntu root/live cd i can try with the konsole
windoze please... burn in the ****ing hell
edit:with ubuntu works well again

.........................................................................................

spike_14 said:
.........................................................................................
Click to expand...
Click to collapse
good apreciation to the forum mate... LOL

okay... in advance thank´s again to my friend Mr_JMM for help me again (pressing your thank´s button AGAIN lol)
i solved my problem with "winfuck"7 (windows for microsoft´s friends)
ok when i was tried to input a fastboot code the CMD (shell) of windows returned me:
"unable to initialize the program because ADBWINAPI.DLL does not exist...
well i browsed for this file and its a library file for adb.exe commands.
under my experience fastboot parameters shouldn´t be afeccted by the ausence of this file but when i was downloaded it (a zip file with adbwinapi.exe, adbwinusbapi.dll and adb.exe) and i have put it in the folder "tools" of the sdk (Rightly where it shelters fastboot.exe) VOILÀ!!!!
i tried to enter:
"fastboot devices"
and returned to my
"HT.........."
also i tried to rebbot the device from fastboot with
"fastboot reboot" and WORKS WELL!!!!
END OF THIS THREAD.... SOLVED!!!!!!!!!!

[Q] Can't get ADB to work, have tried everything

Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies

expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.

Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.

Have you added the environment variable for the sdk directory? It won't work if you don't.

Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try

I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.

vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.

bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.

If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App

It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.

SOLVED Stick mount...?

Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
I am current and up to date with the sdk and drivers. I have fastboot installed. I know how to use it, please skip the referrals/how-to because that isn't the issue.
Spawn The Dark Ages

JediNinjafication said:
Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
Spawn The Dark Ages
Click to expand...
Click to collapse
As for fastboot, sounds like you need to get the proper driver. It's a different interface than adb. Try the naked driver efrant links to in his 101 FAQ post.
As for the other issue, I'm not sure I follow. Using a file manager on the device, you see files/folder that "aren't there" and via adb shell you don't see them? Please elaborate.

Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed. since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Spawn The Dark Ages

I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages

JediNinjafication said:
Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
Click to expand...
Click to collapse
What do you mean by external? The gnex doesn't have an external SD. Forget browsing the /sdcard with Window explorer at this moment, let's try more robust ways first. What do you see using a file manager on your device? What do you see using adb shell? (type ls -l)
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed.
Click to expand...
Click to collapse
Yes, the adb interface device and mtp device are gone because when you are booted in bootloader the phone uses another interface (fasboot). I'm sure it says best driver installed, but if 'fastboot devices' doesn't list your device I beg to differ that's true. Manually update the driver using the naked driver version 0.7: http://forum.xda-developers.com/showthread.php?t=1379875
since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Click to expand...
Click to collapse
Fastboot won't work if you're booted into Android OS. Again, it's an interface of the bootloader.

Oh..i just remembered..when i did have root, i had a program that would tell me system info and it listed internal memory and sdmemory. This was just before i restored.
Spawn The Dark Ages

My external harddrive for my computer. I know all this you just said hence i posted the thread
Spawn The Dark Ages

JediNinjafication said:
I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages
Click to expand...
Click to collapse
Afaik, stick mount is an app that allows you to mount USB thumb drives with your gnex. If you don't have one of those attached and you never used this program, I doubt it's the cause or your problem.

This is not my first Android. each time i post everyone immediately refers me to a toolkit or how to on the sdk. Let's skip all that, assume I'm current and up to date and know how to use it. Now, read the post and continue from there. Not trying to be *****y, but this check drivers and fastboot banter will continue three pages.
Spawn The Dark Ages

And that's why I'm asking because that's how my phone is mounting.
Spawn The Dark Ages

I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.

Petrovski80 said:
I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.
Click to expand...
Click to collapse
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages

Nor was there any command issued. It was a request to skip the usual fastboot/adb and get down to the issue...saving each one if us typing and time.
The time spent explaining i am current and up to date with everything is horrible. Only reason i did the fastboot is because i have never seen it say Android debug interface while my phone is powered on...only when it's in fastboot. Nor have i ever had it sharing files with my external hard drive...like it were stick mounted.
Spawn The Dark Ages

Spawn The Dark Ages

JediNinjafication said:
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages
Click to expand...
Click to collapse
You obviously think you understand what you are doing, but it us clear to everyone but you that you do not. I'm not trying to be mean here, but you are not listen to everyone who has tried to help you. I have tried in your other thread, petrovski80 tried in this one, and others in your other threads that you keep creating. One: you do not have the fastboot driver installed. Period. Two: to answer your question in your other thread, once you do install the fastboot driver, you can follow any one of the multiple guides on how to get root. Three: do not trust what you see in mtp on windows - it is not refreshed properly often. Four: no matter how many android devices you have had and have rooted and no matter how many drivers you have installed in the past, you still have not done the things you need for the GNex.
Sent from my Galaxy Nexus using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=30778314#post30778314

JediNinjafication said:
http://forum.xda-developers.com/showthread.php?p=30778314#post30778314
Click to expand...
Click to collapse
Funny, because no one suggested you use the driver that came with the SDK. If you look up to post #5, you would have seen that the driver that was linked to was the one that you should have used, and you would not have had to make any changes to any setup.inf files, and your issue would have been solved a while ago.

Funny because I had multiple different ones put in my dropboxthat didn't work either. Point being the drivers were there.
And I learned something new. Win/win

ADB Drivers

I don't see any other threads, so is it just me struggling to install working ADB drivers?
The zip file I found in another thread made out like it was installed, but apparently not...
Any tips?

Windows 7/8? The drivers that I posted in the dev thread should work.
If you're on Windows 8 though, you'll have to reboot in that insecure driver installation mode thing.
Sent from my HTCONE using Tapatalk

Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.

AndyCr15 said:
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
Click to expand...
Click to collapse
You try "ADB Composite Device" or something along those lines? When you run that one it should be good.
When you download the zip, you should just extract the whole thing. Then after that I find the driver manually instead of having it search the folders. Are you selecting the android_winusb.inf for the driver?
I'm on the same OS for my main desktop and I do a lot of my work with the N1 on there using those drivers. Are you using normal command prompt in the platform-tools folder? I don't use anything other than command prompt for adb, so I'm not sure about those picking it up.
Sorry if that isn't any help, but I'm not sure what would stop it from picking it up after you use those drivers.

the other threads zip file works fine with my win 64. Are you going through a usb hub? That can mess it up
Sent from my N1 using XDA Premium 4 mobile app

No, no hub. Yep, doing all as I should. I'll try a different cable and different port though.

Linux
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.

mybrotherischad said:
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
Click to expand...
Click to collapse
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.

ChodTheWacko said:
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
Click to expand...
Click to collapse
Running natively. No luck doing it as root.