i am trying to get host mode working on the droid with little luck.
These are the commands i have tried.
"cat /sys/devices/platform/musb_hdrc/mode"
i get "b_idle" when nothing is connected to the micro-usb port or i
get "b_peripheral" if the device is in factory test (Ethernet mode) or
connected to the PC. i am trying to force the droid into usb host by
using this command
"echo host > /sys/devices/platform/musb_hdrc/mode".
but nothing happens. I don't know if the android OS is blocking the
device from going into this mode or if the android gadget driver is
blocking it.
Seen this? http://www.tombom.co.uk/blog/?p=124
del
i don't know if this has been answered already.
How or What application to use in accessing the USB flash drive in NST. I have already update the kernel that support USB host mode and multitouch.
I don't really use this enough to have looked into it more, but to mount a USB drive from a shell:
Code:
mount -o rw,remount rootfs /
mkdir /usb
mount -t vfat /dev/block/uba1 /usb
Yes, it works!! ...Thanks Renate....
Though It has to be mounted manually every time we use it, at least there always a way...
couldn't you install terminal on the nook and run the same command? I don't remember how but isn't there a way to make an icon/shortcut run a command i terminal?? I think it involved a 3rd part app.
persichini said:
couldn't you install terminal on the nook and run the same command? I don't remember how but isn't there a way to make an icon/shortcut run a command i terminal?? I think it involved a 3rd part app.
Click to expand...
Click to collapse
Yes you can.
Much easier to use ADB tho - you can cut&paste
I have since bought an OTG cable. I can switch to host mode with the state at a_host. I can't mount my USB drive, and neither does the light go on.
I can get my USB mouse to work.
tehriddler said:
I have since bought an OTG cable. I can switch to host mode with the state at a_host. I can't mount my USB drive, and neither does the light go on.
I can get my USB mouse to work.
Click to expand...
Click to collapse
To mount your USB drive, you should know how to use ADB wireless and get and ADB command shell, and follow those shell commands mentions by Renate on her post above.
@tehriddler:
I forget if you need a special uImage for USB mass storage, I think you do.
Some thumb drives take a bit of current, maybe too much for a Nook.
Try to get it working with a hub first, the light must be on.
Us the UsbMode app, it will show you if the drive is being detected and if the driver is loaded.
Look at the "View USB". If there is a black dot there, then the driver is loaded.
I'm typing the commands into TerminalEmulator. /dev/block/uba1 doesn't exist because I can't mount the drive.
(I don't have ADB wireless/Android SDK at the moment as my computer is away for fixing.)
ETA: How did sugaray get theirs to work? I tried with two different flash drives. Errr for a powered USB hub I'm not stripping the OTG cable and rewiring it like the method you described, and the only powered USB hubs sold in stores are powered by AC.
Is this the app https://play.google.com/store/apps/details?id=in.zatta.USB_switch&hl=en or another specifically for the Nook? Will try again with the app.
No, I meant this UsbMode app: http://forum.xda-developers.com/showthread.php?p=25613941#post25613941
I see - I had the old version of the app that didn't have the View USB button.
Yep the drive has been detected.
MUSB HDRC host driver.
However I the light of my USB drive doesn't go on and I can't find the mount path. There's no /dev/block/uba1
My original response:
The USB system on the Nook is not so hot on "un-detecting" devices.
It could be that the system initially identifies the flash drive, then it drops out.
By a "powered" hub, I just meant a regular hub that would be supplying the current to the flash from a wall wart.
I didn't meant a modified "back powering" hub that would charge the Nook.
In any case, with either powered hub or "back-powered hub" no cables need to be modified.
Click to expand...
Click to collapse
Oops! I reread your response:
tehriddler said:
Yep the drive has been detected.
MUSB HDRC host driver.
Click to expand...
Click to collapse
No, that's not being detected at all.
That is the host adapter and will show without anything plugged in.
You should have a treeview with another box under there saying "Mass Storage Device".
There should be a black dot to the right of it to show that the driver is loaded.
I have the treeview with my flash drive's name but no black dot (your screenshot link is broken)
MUSB HDRC host driver
- DT 101 II (my flash drive)
There's a file called 074 in /dev/bus/usb/001 which has been created when the drive was detected.
Oh, then you need mali100's uImage with the USB mass storage support.
(Oops, I guess that XDA thinks a 2nd link is hotlinking. Here's the capture, note the black dots.)
Nope there's no black dot next to my flash drive's name.
I'm using mali100's uImage with Multi-touch and USB host.
Additional USB related drivers (usb-storage, usb-serial ...)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1570637&highlight=uimage
Even with nothing plugged in a "ps" in ADB shell should show (something like) this:
Code:
root 607 2 0 0 c02d00fc 00000000 S usb_mass_storag
Code:
root 595 2 0 0 c02cde14 00000000 S usb_mass_storag
Ok, are you running the flash drive with power from a hub?
Have you tried another flash drive?
I'm using an OTG cable because I don't have a powered hub. I didn't buy a powered hub because they're not portable - they only use AC adapters, no battery-powered ones.
Last night I was reading using my LED light. I changed back to peripheral mode after using OTG mode for powering the reading light. There was 40% battery left (in the pop up shown after switching back to peripheral mode). The next morning, the battery drained and my Nook turned off because the battery was low. Am I supposed to quit the app after I'm done?
I tried a flash drive that I bought last month. This one doesn't work at all. The name doesn't even show up in View USB.
ETA: Same result as the first drive. Its name shows up in View USB but no black dot.
Try with a powered hub.
This is diagnostics, not your preference for portability.
I'm a game developer, and I just picked up the MOJO because I'd like to use it for development using ADB and the standard android tools. I bought a Male to Male USB cable to hook it up to my computer, but it doesn't seem like that works the same way that the micro USB works on Android phones and Ouya.
Has anyone gotten the Android working for development? If I had to guess, it sounds like you have to root it, then enable ADB over wifi? I found instructions to root it, but are there any instructions for getting ADB over WiFi (or the ethernet plug) running on it?
Thank you for your help!
I haven't debugged on my mojo yet, so I"m not 100%
Do you have developer options enabled?
I would look at Nvidia info, ie:
http://docs.nvidia.com/tegra/index.html#Getting_Started.html
The shield is simular.
https://developer.nvidia.com/getting-started-shield
You've got to ADB over the network. Find the assigned IP address of MOJO in the Settings>About MOJO>Status page.
Then go to your PC and type adb connect xxx.xxx.xxx.xxx into a command line to connect to MOJO - you can then ADB to your heart's content.
Hey all,
Has anyone been able to successfully root from a MacBook Pro 2016 with USB Type C ports? Having problem getting adb to list my Shield. This is on:
2016 Macbook Pro w/ macOS Sierra 10.12.3
WAWPI USB 3.0 A Male to A Male Cable
Apple USB-C to USB Adapter
Android Debug Bridge version 1.0.36 (Revision 84e3321d5db3-android)
System Information -> USB shows Shield but adb devices does not. I was able to connect with adb connect <IP> but not USB. I've seen various threads pointing to a possible issue with Mac USB Type C/Thunderbolt 3 ports.
Any help would be appreciated.
EDIT: adb command works with about mentioned cable and adapter. The real issue is fastboot. It constantly freezes/crashes macOS. I think my Mac was in a funky state preventing adb command from listing devices. Unfortunately, this still prevents me from performing a complete root from this macbook. I was able to complete root with another macbook with USB ports. So does anyone have a fix or workaround for fastboot other than running a VM or bootcamp?
EDIT2: In case anyone is following this thread... There's an open bug for this and a fix is in QA. New release coming.
Thanks for this post.. I was confused about what the issue was.
Hi,
adb doesn't detect my ZUK Z1 device.
I followed all instructions and tutorials I could find. I Enabled USB debugging and OEM unlocking, added vendor ID in
Code:
~/.android/adb_usb.ini
(My Galaxy Tab 3 is listed by adb when connected, btw.)
I would first like to know that it's not a hardware / OS / driver issue.
What I find odd is that it doesn't even charge when connected to the PC. Does this indicate a more general problem? (Charging only works with a power adapter with ~2A output.)
PC is a DELL Latitude E6540 which is supposed to have 4 USB 3.0 ports.
I'm running Elementary OS which is Ubuntu 16.04 based. It seems that it's not officially supported by Dell.
The USB cable was the issue.
I replaced it and everything worked like charm.
I didn't think the cable was the problem because it still worked for charging.