Develop Bugs

ADB only recognizes phone when it's in recovery. Why?

I used to be able to
1. Plug my phone in via USB (unmounted - meaning "charge only")
2. Open up a command prompt and navigate to the correct folder.
3. Type "adb devices"
4. Receive a long string of characters that indicated that adb recognized the device.
Now this only happens for me if the phone is in recovery already. For example:
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT05SHL05247 recovery
Things I've tried:
* Re-installed SDK
* Re-installed HTC Sync
* Manually re-installed drivers for phone
It is interesting to note that when the phone is on and plugged in, Device Manager sees it as a disk drive no matter if the phone is mounted as a disk drive or not. Strange.
Everything worked fine until I went on vacation. Now it's messed up!
The question is: how do I get adb to recognize my phone again?

is usb debugging still on?

when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill

Thanks for the responses.
mdwoods said:
is usb debugging still on?
Click to expand...
Click to collapse
Yes, I checked and USB Debugging is selected.
btedeski said:
when you plug in the USB cable do you get the screen to select
charge only, HTC Sync Disk drive etc..
if not go to "Settings" -> "Connect to PC"
and turn on "Ask Me"
I had a bad USB port, would only charge could not get any PC connection to work until phone was replaced, works now
Bill
Click to expand...
Click to collapse
Yup, when I plug it in I get the pop-up asking me what kind of connection I want.
Any other ideas?

Still nothing! I'm going to be selfish and bump in case a fresh pair of eyes can help me solve this.

Something similar happened to me. I tried many things over and over again. I changed kernals, roms, reinstalled drivers, etc. Eventually, I just reformatted my computer and it worked. I don't know why reinstalling the drivers wouldn't work when reformatting did. I honestly have no idea, but that reformat did the trick for me.

ADB not working when booted is a somewhat commonly-reported problem with King's kernels. Try flashing the stock kernel and see if it starts working again. Also, wipe your caches in the future before flashing a new kernel. This seems to prevent a lot of issues.

I has this same problem. I believe I wrote a thread about it. When I toggled USB debugging off and then back on, that is what solved the problem. Believe me, I went through hours of reinstalls of multiple androidusb.inf drivers plus HTC Sync among others. It wasn't until a "what the hell, let's give it a try" moment that I toggled USB debugging off/on. Like you, I had it on the whole time. Still don't know what caused the mishap but this is what fixed it for me.
Sent from my PC36100 using XDA App

Thanks for the last two ideas. I love Fresh ROM, but have been having major issues with it lately, and this must have been tied into it. I installed Baked Snack with the custom baked snack "speed" kernel and the issue went away (along with all my other issues). Yay.
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.

Sprockethead said:
I don't doubt that toggling the USB Tethering check box would have fixed it, though. And that's just funny. Sad and funny.
Click to expand...
Click to collapse
Actually, I found an answer to that question. I am experimenting with Andromadus CM10 on a HTC Desire Z and this is what happens:
The mobile phone declares what USB device it is. You can look at this on the linux computer you have connected it with:
Code:
lsusb -v -d 0bb4:0c91
The string after "-d" is what you get from a plain lsusb command. The important part of the output of that command is
Code:
bInterfaceClass 255 Vendor Specific Class
"adb devices" only shows the phone if this 255 is present.
With the phone in fastboot and recovery, I always could see the 255 on my linux box. Normally booted, I sometimes had it, sometimes not.
If I had it the device was called "HTC Vision", if I didn't have it, it was a "HTC Desire / Desire HD / Hero (Charge Mode)"
Toggling "USB Debugging" actually helped me to make it a "HTC Desire" and get adb over USB working.

[Q] Questions about Auto-Root "e4gtauto-sfx"

Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!

Are you trying to say it didn't install CWM? Did you try to boot into recovery yet and see what happens?

Try uninstalling drivers then reinstall and reboot computer
Sent from my SPH-D710 using Tapatalk 2 Beta-4

Honestly, sfhub is a great guy, very helpful with all of his stuff, I might even pm him with that same post and info.
Sent from my calculator watch.

da8vii said:
Hi folks, this is my first post so I apologize in advance for any protocol I might be breaking.
My goal is to be able to flash some of the awesome new ICS ROMs that have been developed. I was able to successfully install the rooted TAR of FC24 provided by sfhub http://forum.xda-developers.com/showthread.php?t=1573752 by utilizing ODIN. My next step was to use the auto root also provided by sfhub http://forum.xda-developers.com/showthread.php?t=1342728 to flash CWM. I have not yet been able to get my E4GT to accept the install.
I have been met repeatedly by this error:
Getting ready to
INSTALL BootImg - FC24+CWM-Rogue (requires ROOT)
Please verify ALL of the following:
USB Debugging is ENABLED
USB Storage Mode is DISABLED
Samsung USB/Android drivers are INSTALLED
Phone is connected to USB port and recognized
Press any key to continue . . .
----
Waiting for device to be connected [press CTRL-C to cancel]... Found device
Proceeding with install
----
Asking for root permissions...
Please turn ON phone and EXIT the lock screen
AFTER you press any key to continue, if you are PROPERLY ROOTED, you *MIGHT*
see a PROMPT asking for permissions. If so, please ALLOW root access.
Press any key to continue . . .
error: device not found
---- BEGIN LOG ----
BOOTIMGNAME = FC24+CWM-Rogue
BOOTIMGFILE1 = zImage-fc24
BOOTIMGFILE2 = zImage-fc24-cwm-rogue
BOOTIMGSTKREC = no
BOOTIMGSCRIPT = install-boot-fc24-cwm-rogue.sh
...Proceeding to copy necessary files...
error: device not found
push: copy2sd-img/000root/zImage-fc24 /sdcard/000root/zImage-fc24
error: device not found
push: copy2sd-img/000root/zImage-fc24-cwm-rogue /sdcard/000root/zImage-fc24-cwm-
rogue
error: device not found
----
error: device not found
---- END LOG ----
Check for any errors. Assuming there are none, BootImg install was SUCCESSFUL.
----
Getting ready to reboot...
This reboot will take slightly LONGER than usual since it will be
recreating Dalvik-Cache. If you are using ICS you will see a status
screen mentioning Android is upgrading during this process.
Your phone MAY be slightly SLOWER for a SHORT TIME after boot is
complete while it performs maintenance.
This is all NORMAL.
Press any key to continue . . .
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
Couple things to try. Were you able to boot into the rooted FC24 you flashed via Odin? If that won't even boot you will need to reflash that. That has to be working. If it doesn't boot you might want to re-download the tar/exe that says 'RESET user data' option - you can't/shouldnt use the 'NoData' when going from GB to ICS. Run that and make sure the phone boots. Also maybe re-download the e4gtauto package, possible a bad/incomplete download. Then once your sure you phone boots turn it off and go into download mode and run the e4gtauto package again.
Also and this is so freaking important I can't overstate it: Try a NEW AND GOOD USB cable. I personally have had problems that I could have solved in seconds (by using a different cable) take me hours! Just had a 'good' amazon cable fail me this week - trying to get my nandroids off my SD card to my PC and copy over new ROM zips; device would not be recognized. I resinstalled samsung drivers, kies, rebooted systems (phones and computers) and other crap. Then took my own flippin advice pulled a new USB cable out of my drawer and BAM device recognized. Sometimes simple should be done first. Good luck!

da8vii said:
I have tried different USB cables, different USB ports, uninstalling and reinstalling the Samsung drivers and Kies. I have Superuser available in my app drawer and USB Debugging is definitely enabled. I have wondered if my issue might be with not having USB storage mode disabled, but it seems FC24 doesn't give you an option to enable or disable that function.
I appreciate anyone who took the time to read this and I welcome all constructive feedback. Any enlightenment on this issue would be very helpful.
Thank you in advance!
Click to expand...
Click to collapse
I don't think your issue has to do with USB Storage since as you noticed, there is no UI to enable mass storage mode and by default it is off (actually it can't be turned on by default on FC22/FC24 because the USB port is set to MTP mode and the USB utilities UI is removed)
I've actually never seen it pass the "Found Device" stage and then later on come up with an "error: device not found" Usually it will stay waiting for the device if there is something wrong with the connection.
Can you get an "adb shell" session started? If you can get that working, then everything should work. If you don't know how to start "adb shell", use Option E (Extra Options) followed by Option G (adb shell)
Once you start the adb shell session, also verify the /sdcard is mounted properly by typing
Code:
ls -l /sdcard
and making sure the contents look like what is on your /sdcard (ie it shouldn't be an empty directory)

Alternative: Buy Mobile Odin from Android Playstore, aka the market...put el26 cwm tar here: http://db.tt/rIxjBIk8 on your sdcard. Flash cwm el26 using Mobile odin and at "First Samsung screen " after boot hold volume up and power button until you see recovery... Then, flash your choice of ics rom.. (at your own risk of course) I do this daily and I have had to go back to gingerbread a few times from ics, and omw back to ics this is what I do... Works perfect! Just make sure you have whatever zips you want to flash on sdcard previous to this.. Sure you know all that...You can repeat this method every time you flash another ics rom... I do, and have about 100 times already. Lol. For real!
I know this is a little late, but Happy flashing!!
You can read about Mobile Odin here: http://forum.xda-developers.com/showthread.php?t=1347899 and here: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
Sent from my SPH-D710 using Tapatalk 2 Beta-5

There is some driver or USB issue where "ADB" cannot see your phone. This is a standard android sdk tool that Auto Root is using to copy files to your phone.
There are various things you could try. Personally I think you should figure out why adb isn't recognizing your phone as it will help you in the future, especially if you get in some binds, but the quickest way to get CWM installed is to just download the Auto Root zip file to your phone. Then use Mobile ODIN to flash one of the zImage files contained in the copy2sd-img/000root directory in the zip file. You are basically treating the auto root zip file as a complete archive of every stock and cwm recovery that was released for this phone.
Alternatively you could also use the manual instructions in the 2nd post of the auto root thread. The only thing ADB is really being used for in the case of installing cwm is copying files to your phone. Everything else is being handled by scripts that run on the phone itself, which can be done on a terminal running on the phone.
If you want to figure out what is wrong with adb, I can help with that also and I'm sure you'll eventually figure it out, it'll just take a little more time.
First thing I would go over is this troubleshooting post:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Also make sure you are booted into Android rather than Recovery. Stock recovery doesn't enable the ADB interface. Also make sure USB debugging is enabled.

Ok a couple of things. first of all make sure you have your drivers working properly. I'm sure they're good since you rooted..but you never know. Next make sure that when you connect the USB that you don't go into USB mode on your phone. Just plug it up but when your phone asks if you want to connect the USB to share files don't press ok. Make sure system debugging is enabled and accept unauthorized software is checked. Then it should recognize your device.

Recovery Mode?

Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?

with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec

Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk

Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered

Check this command
adb devices
does it even show up on the list?

Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.

https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem

Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.

Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again

darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm

[Q] HTC M8 not being seen in adb

OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.

reubendevries said:
OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.
Click to expand...
Click to collapse
Might be a driver issues... Try those: https://www.dropbox.com/s/nr91z4bveeugaow/googleUSBdrivers.zip?dl=0
Sent from here

1) Unplug the phone from your computer
2) Uninstall anything related to HTC (drivers, sync managers..)
3) Reboot the computer
4) Install the latest (direct URL) HTC Sync Manager
5) I tend to uninstall the manager right afterwards (optional)
6) Reboot the computer & plug in your device
7) Report back

abyssis said:
1) Unplug the phone from your computer
2) Uninstall anything related to HTC (drivers, sync managers..)
3) Reboot the computer
4) Install the latest (direct URL) HTC Sync Manager
5) I tend to uninstall the manager right afterwards (optional)
6) Reboot the computer & plug in your device
7) Report back
Click to expand...
Click to collapse
Yeah that didn't work unfortunately

lukes91 said:
Might be a driver issues... Try those: https://www.dropbox.com/s/nr91z4bveeugaow/googleUSBdrivers.zip?dl=0
Sent from here
Click to expand...
Click to collapse
Yeah that didn't work, I even tried installing the USB Driver manually and that didn't work either. Still comes up as not connected, it's super frustrating.

Not sure if this helps but for some reason my Android Phone isn't showing up under Android phone in my Device Manager, it's showing up as Portable Devices. I don't know if this is an issue or not, anyone care to give an opinion?

reubendevries said:
OK using a windows 8.1 Pro laptop, ADB installed properly with HTC Sync Manager, both Windows, HTC Sync Manager and the Device Manager in the Control Panel can see my phone. I tick on USB debugging and then press revoke USB debugging authorizations. Unplug my phone and plug it back in. I'm using the original USB cable from HTC. Everything pops up and shows like it's connected, except when I type in
Code:
adb devices
in the command prompt, then it just comes up blank. I've attached screen shots so you guys can see what I am talking about. If you have any ideas it would be much appreciated. I've attached some photos just to show that I've dotted all my i's and crossed all my t's as far as I can see. I also want to point out this is the second computer I've tried this on.
Click to expand...
Click to collapse
check and unchecked camera under USB settings when its plugged in

reubendevries said:
Not sure if this helps but for some reason my Android Phone isn't showing up under Android phone in my Device Manager, it's showing up as Portable Devices. I don't know if this is an issue or not, anyone care to give an opinion?
Click to expand...
Click to collapse
That's normal as the phone is using MTP, the Android Phone entry only appears once the drivers are installed. It's definitely a driver issue but as to what I can't say as I have no issues on my 8.1 Pro laptop

I think I figured something out, just flash CM 12 - (God it's amazing. ) and now I can see my phone on ADB, so whatever ****ery was going on I am blaming it on HTC stock rom.

reubendevries said:
I think I figured something out, just flash CM 12 - (God it's amazing. ) and now I can see my phone on ADB, so whatever ****ery was going on I am blaming it on HTC stock rom.
Click to expand...
Click to collapse
is cm12 worth the hassle?

Sorry for the necrobump, but I ran across this thread while researching the same issue on my M8 and wanted to save anyone else the trouble if they also stumbled across this same issue.
Though the solution discussed would likely work, if you don't want to hassle with a new ROM, it is possible to fix it on your existing ROM provided you have root.
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option

NFSP G35 said:
Sorry for the necrobump, but I ran across this thread while researching the same issue on my M8 and wanted to save anyone else the trouble if they also stumbled across this same issue.
Though the solution discussed would likely work, if you don't want to hassle with a new ROM, it is possible to fix it on your existing ROM provided you have root.
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
Click to expand...
Click to collapse
Thanks for this guide you put up. Interesting that there was no option for you to revoke USB authorization. My device is S-ON and have been using Viper for a while with the option available. Same for HTC stock. Good for you getting that fixed. Had a similar issue on a different device months ago.

Obtained Sprint Nexus S 4G, Stuck on ICS

So my buddy gave me this Nexus S 4G, since I like to collect phones. Unfortunately, it appears to be stuck on 4.0 ICS. I tried to check for an update to 4.1 ICS, but for some reason, it reports that my phone is up to date??? Wtf. So I tried doing it manually, I can't flash this random OTA which may or may not (probably is) Jelly Bean in stock recovery, but it fails. I tried doing it even more manually using fastboot, but for some reason, I can't get the USB drivers to work. My next step is to use a Macintosh, as they seem to work better with Android, but I don't have access to it yet. In the mean time, is there any other way to get this phone updated or, at the very least, rooted and ROM'd?

@Dr. Hax
I'm assuming you are using windows? If so burn a Linux iso, Mint or Ubuntu are both great. You can make a bootable iso using a thumb drive or CD. Then set up your pc for dual boot. You'll never have a driver issue on Linux.
I'm sure you probably know this but how I have gotten windows to work and see my device is install the fastboot and adb 15 second installer from here: https://forum.xda-developers.com/showthread.php?t=2588979
Then reboot of course. And when I plug my device in have developer options enabled and usb debugging enabled and be watching phone for the little box pop up that you just checkmark really quick so your pc can communicate with the device... Also if you scroll down on the phone in developer options to "default usb configuration" and change that to "file transfer", that will usually bring the little box up on my devices to check mark so they can communicate..It only shows for a second then it's gone. But if it hasn't popped up yet then open terminal and type sudo adb devices (hit enter) and again be watching your phone because that little box should then come up that you must quickly check mark on phone so pc and phone can communicate.
I always uninstall and reinstall drivers on windows and reboot afterwards. Also make sure check device manager and see what's there. But that 15 second fastboot adb installer for windows is a life saver and makes it all super easy!! On Linux none of this happens. Ever! ? You just plug in your phone and the model of your device shows up on the computer screen. IDK if this makes sense much but I tried to word it where it did best I could. Hopefully this helps or you already got it going.