Hi, my Nexus S was working before I rooted it and with an older version of Banshee. Then I recently upgraded to Ubuntu 11.04 and Banshee 2.0.0 and also rooted my Nexus S (and installed CM7 and an alternative kernel) and now it is not recognized by Banshee.
I've tried following the advice on this thread http://forum.xda-developers.com/showthread.php?t=624240 by creating an .is_audio_device file in the root of the mounted SD drive, but that didn't help.
Any ideas? Thanks.
BTW: I'm able to work around this now by:
1) connect Nexus S
2) Disable (if enabled) USB Debugging
3) Re-enable USB Debugging
So, this, at least, means it *can* work - I'd just like to figure out how to get it to work without this awkward workaround.
Related
Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?
Not recognized? You mean on USB? No volumes mounted?
You can certainly transfer your books over ADB on WiFi if that's working.
If you can get to a shell on ADB try a "mount" command.
The last two lines should be like:
Code:
/dev/block//vold/179:6 /media vfat rw ...
/dev/block//vold/179:17 /sdcard vfat rw ...
DoomMunky said:
Apologies if this duplicates an old thread, but I couldn't find another one...
I rooted my Nook Simple Touch using Touchnooter 1.1, and now it can't be recognized by my PC. I can't copy files to it.
I bought several Google eBooks recently that I'd like to read on my NST, but they can't be loaded, as Adobe Digital Editions can't see the Nook (or doesn't recognize it). Google Books doesn't work, either. It just stays on a rotating 'loading' icon forever, never loading the book.
Any thoughts?
Click to expand...
Click to collapse
Using a root method that enables ADB over USB can mess up the drivers on Windows and make the Nook partition inaccessible.
There are two options:
1: Re-root with a ramdisk that enables ADB over WiFi (might not help)
2: Properly install Google drivers for ADB over USB (search this forum)
Dammit. It's so darn complicated. I was hoping to recommend this method to my non-geek friends so they could have simple little tablets too, but this all is just too much work for them (and for me). This is why people buy Apple.
If I go back to a rooted Nook (I returned to stock) I'll look into this stuff. Thanks for the tips, folks.
Oh! Check what driver you have on the Windows machine.
Under "Device Manager" if it shows Android anywhere then you have the Android ADB USB drivers loaded.
This would prevent the USB Mass Storage driver from being loaded.
Did you load the ADB USB drivers?
God, I have no idea if I loaded the ADB USB drivers. I just did the normal TouchNooter1.1 install, which includes basic Google Apps.
Then when my PC didn't recognize the rooted NST, I gave up and went back to stock! I'm not a true rooter.
@DoomMunky: Aw, don't get disheartened. Soon you'll be rolling your own kernels!
So you got your Nook to be recognized by your PC now?
Only by reverting to stock firmware. I'm running basic 1.1 now, no Android anything, and it's fine.
If I end up re-rooting in the future, what steps should I take to ensure my PC still allows simple book transfers to my Nook Simple Touch?
Hi All,
First post here, please be gentle! I don't think this issue is related to Glazed directly, so I'm posting it in this forum.
I installed Glazed ICS ROM on my Kindle Fire a few weeks ago. Yesterday I upgraded it to to 7/6 release. Afterwards, I tried connecting it to my Windows 7 PC. The driver is installed properly it seems (it shows up in Device Manager w/ no errors). I click "Turn on USB Storage" - however, it never shows up as a drive.
When I run the KFU - it says
"ADB Status: Offline
Boot Status: Unkown"
Thoughts? What other info do you need to help this poor fella out?!
Thanks for your help!
Josepho1997 said:
Try uninstalling the drivers you installed when you rooted it.(Android Composite Interface or whatever its called) That worked for me.
Also enable USB Debugging or whatever its called.
After uninstalling the drivers, plug in your Kindle. In the status bar you should see a usb icon. Click on it and turn on USB Storage or whatever ICS calls it.
Click to expand...
Click to collapse
Only drivers I found associated with the Kindle in device manager was Android ADB Interface. Removed it, checked USB Debugging (Was already enabled) plugged in Kindle, still no USB drive
thoughts?
Some of the ICS ROMs don't have USB mounting enabled yet. Try mounting manually in TWRP, that's what I've done. Sucks I know, but it's something.
thecashblaster said:
Hi All,
First post here, please be gentle! I don't think this issue is related to Glazed directly, so I'm posting it in this forum.
I installed Glazed ICS ROM on my Kindle Fire a few weeks ago. Yesterday I upgraded it to to 7/6 release. Afterwards, I tried connecting it to my Windows 7 PC. The driver is installed properly it seems (it shows up in Device Manager w/ no errors). I click "Turn on USB Storage" - however, it never shows up as a drive.
When I run the KFU - it says
"ADB Status: Offline
Boot Status: Unkown"
Thoughts? What other info do you need to help this poor fella out?!
Thanks for your help!
Click to expand...
Click to collapse
The problem is in the kernel. It's an issue that Hashcode has been working on for a while now. The best thing that most people have been suggesting is to use AirDroid or to mount using TWRP. AirDroid lets you connect through wifi without having to reboot in to recovery, which is always nice. It's also completely free in the Android Market.
As title says, I cannot connect the storage on my N7 through MTP after SmoothROM (Trinity Kernel) install. PTP does work but that's fairly useless.
I've found a fix but it's not working. The fix was to remove and reinstall the driver in device manager.
Since that didn't work, I've also tried the USB Deview tool from NRT. Unfortunately, this doesn't work either.
I'm using win8 on my main computer, which is where it does not connect. I've tried my win7 laptop and it goes without a problem there.
So any help?
If you need more information, feel free to ask.
Thanks in advance.
EDIT: ugh. I fixed it. I feel stupid for not enabling USB debugging. -.-
Mods may close this thread or even delete it.
I know it's a really common and simple problem but I google it several time and I can't figure out how to solve this.
When I plug the device onto the PC it begin to charge, but I can't browse the folder inside the N4 cause it's not seen by the PC itself.
the N4 has stock rom android 4.3 with stock kernel, unlocked bootloader and root permission.
I tried to:
-use different cables
-use different usb ports (2.0-3-0)
-enable USB debugging
-install MTP driver from microsoft site
-install ADB driver from google nexus toolkit
-put it in PTP mode
-install other driver suggested by another toolkit
when I was on 4.2.2 all worked fine, but since I installed CM 10.1 and android 4.3 I can't see the folder such as music or download.
Someone can help me? this thing is really annoying
Lamerlengo said:
I know it's a really common and simple problem but I google it several time and I can't figure out how to solve this.
When I plug the device onto the PC it begin to charge, but I can't browse the folder inside the N4 cause it's not seen by the PC itself.
the N4 has stock rom android 4.3 with stock kernel, unlocked bootloader and root permission.
I tried to:
-use different cables
-use different usb ports (2.0-3-0)
-enable USB debugging
-install MTP driver from microsoft site
-install ADB driver from google nexus toolkit
-put it in PTP mode
-install other driver suggested by another toolkit
when I was on 4.2.2 all worked fine, but since I installed CM 10.1 and android 4.3 I can't see the folder such as music or download.
Someone can help me? this thing is really annoying
Click to expand...
Click to collapse
Do you use a pin on your lock screen?
I'm on Carbon nightly and use a pin and have to unlock my screen to get access through PC
mrhiab said:
Do you use a pin on your lock screen?
I'm on Carbon nightly and use a pin and have to unlock my screen to get access through PC
Click to expand...
Click to collapse
no pin neither other methods, just the standard slide
Lamerlengo said:
I know it's a really common and simple problem but I google it several time and I can't figure out how to solve this.
When I plug the device onto the PC it begin to charge, but I can't browse the folder inside the N4 cause it's not seen by the PC itself.
the N4 has stock rom android 4.3 with stock kernel, unlocked bootloader and root permission.
I tried to:
-use different cables
-use different usb ports (2.0-3-0)
-enable USB debugging
-install MTP driver from microsoft site
-install ADB driver from google nexus toolkit
-put it in PTP mode
-install other driver suggested by another toolkit
when I was on 4.2.2 all worked fine, but since I installed CM 10.1 and android 4.3 I can't see the folder such as music or download.
Someone can help me? this thing is really annoying
Click to expand...
Click to collapse
Is the partition marked as active within windows? start > run > diskmgmt.msc
Timboe73 said:
Is the partition marked as active within windows? start > run > diskmgmt.msc
Click to expand...
Click to collapse
nope, can't see the phone there
up
I'm having the same issue here and can't get my device to be recognized by various computers. This was after flashing CM 10.2 (Android 4.3) and the problem still persists in CM 11.0 (Android 4.4).
Prior to that the device connected normally as it showed up on device manager and my PC making the USB connect sound.
Is this potentially hardware problem as well?
Thanks in advance.
Try Usb Debugging + P2P and lmk
gt-kingz said:
Try Usb Debugging + P2P and lmk
Click to expand...
Click to collapse
Hi gt-kingz, I tried that and it won't work. Do I try wiping my system and then re-installing CM 11.0 or Android 4.4?
dmatthew said:
Hi gt-kingz, I tried that and it won't work. Do I try wiping my system and then re-installing CM 11.0 or Android 4.4?
Click to expand...
Click to collapse
It won't fix it. I have the same problem since I installed 4.4 (tried many different roms). Usb Debugging + p2p is the only working solution for me.
I tested on Xp/7/8 even with different drivers. But well, I would just use Airdroid.
I have the same problem!
Sent from my Nexus 4 using xda app-developers app
Try different USB wire. If the problem persist; uninstall and reinstall N4 drivers.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Try different USB wire. If the problem persist; uninstall and reinstall N4 drivers.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hi badboy47, have tried different USB wires and even different computers. With regards to the N4 drivers, I can't even see the device in device manager when plugged into my PC. Or did you mean uninstalling the universal ADB drivers?
Thanks!
I'm having an issue with file transfer where my computer can't 'see' the phone when an AOSP ROM is installed.
File transfer is fine when mounting in recovery, also when I have OOS installed, so it isn't a hardware problem.
I've gone through the forum searching for a solution, and I have:
Changed the default USB configuration (under Developer options) to MTP
Uninstalled the phone from Device Manager on my computer
Tried installing OnePlus drivers to my computer
Tried installing Qualcomm drivers to my computer
Can anyone suggest a solution? I'm desperate to get this sorted as I can't tolerate OOS any longer, I just want a cleanish build of Android with no OnePlus rubbish in it!
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Hitman478™ said:
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Click to expand...
Click to collapse
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
siankatabg said:
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
Click to expand...
Click to collapse
I know it's windows fault because when it have too many drivers to manage for the same thing it goes crazy.. but even removing every single driver (ADB and Android related) it doesn't work.. I'm looking in a solution on the Linux build called "forget windows use Linux" since I can't completely remove windows 10
I had same issue in Linux
Typically, issue is not the ROM
1) check the phone get set to "file transfer" when connected, you generally have option to chose
2) plugging to a usb in chain to other switches it was not work, connected directly to a usb MB port, worked.