Database Users

[Q] What's the micro usb port for?

Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq

It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.

Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.

I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was

I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq

Drivers from acer website.

I have adb installed should this not be enough?

You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.

I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq

I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6

I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium

Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq

don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.

If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App

gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.

I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.

sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.

Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try

Getting Nexus S to mount on Linux

I just recently installed Arch Linux with KDE as the GUI and I can't for the life of me figure out how to mount my Nexus S. It doesn't show up in /media so I don't know how on earth I can mount it. I've tried in CWM with mount USB and still nothing shows up anywhere on my system. Prior to Arch I was running OS X (10.7) and it was mounting fine. Obviously very different OS and Arch is a lot more complicated to use. I've spent several hours trying to figure out how to mount it but I can't find anything that solves it. Maybe anybody out there using linux could give me a hand?

Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.

Harbb said:
Arch is best Good choice.
Easiest way is to mount it manually. First you'll have to find out which device it is. Plenty of ways to do this, using "fdisk -l" in terminal, gparted, etc. It will be something like "/dev/sdc1". Once you know this, you need to create a folder to mount it. Something like:
mkdir /media/nexus
Now, you need to mount it (after you've chosen to mount on the phone). To do this:
mount -t auto /dev/sdc1 /media/nexus
auto is the file system, you can type fat32 also but it can figure it out. Then the disk location, then where to mount.
You may need root permissions or changes to the sudoers file to do these. Type "man mount" or "man command" for just about every commands manual. I'm on the phone so I can't write up anything much better than that.
Also, the arch Linux wiki is an invaluable resource, make the most of it.
Click to expand...
Click to collapse
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.

Try in recovery first if it doesn't show up in Android. If it still doesn't show up I'll try to break my arch and fix it, whether its in android or cwm.

tycruickshank said:
Thanks very much for your help. I'll work on this later tonight since I have a lot of school work I need to get done now. Oh yeah you say to mount the device on the computer after pressing mount on the phone but that dialog never actually shows up when I plug the phone in. The phone doesn't recognize it's being plugged into a computer it just shows that it's charging. The arch wiki is definitely a great place for all things arch. Best documentation for any operating system I think I've ever seen.
Click to expand...
Click to collapse
I've experienced this before as well. It turned out that I had a dodgy cable that's just not compatible with my NS for some reason.
If you want a pop on your KDE desktop when you enable UMS mode on your phone, make sure you udev is added to the daemon list in /etc/rc.conf. Then, you can either reboot or do /etc/rc.d/udev start and restart KDE again.

I've tried everything that you guys have said and still no luck. Its not showing up anywhere. Not in fdisk -l, I tried lsusb, looked in /dev/disk and it wasn't there. Nothing was pointing to a device being connected. I checked the everything.log file as well. Last photo is the everything.log and of course these were all taken with my phone connected to my computer. I tried multiple different USB cables too.
Sent from my Nexus S using Tapatalk 2

Just curious, with the phone on, and screen unlocked, what do you get with:
adb devices
?

Sorry but try to check it with other OS to be sure that your USB host is good .
Sent from my Nexus S

Unplug the USB. Then plug it back in then immediately run lsusb. If you dont see the device should be /dev/sdb1 should be the device according to your current fstab.
If it does not show in /dev/ or lsusb you have a bad cable.
Sent from my Nexus S 4G using xda premium

Well this morning it decided to work. I had turned my computer off last night and I tried it this morning with the same cable and it decided to work. I hope it's not going to be intermittent but seems to be working for now. Thanks everybody for all the help!

[Q] how to access flash drive?

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.

[Q] howto get USB-host on Glowlight rooted w. NookManager

Hi folks, I am new here - have been reading for a few months and used NookManager to successfully root/re-root 2 NST and 1 NSTGlowlight now. Huge thanks to all developers!
Being a newbie with <10 posts, I was not allowed to post in the NookManager thread (http://forum.xda-developers.com/showthread.php?t=2040351). So I hope my post is more or less well-placed here.
I am very happy with the functionality of the Glowlight with firmware 1.2.1 rooted with NookManager.
The rooting process is really super-easy! So if possible I'd like to stick with it.
But... now I'd like to have the USB-host functionality as well to connect a keyboard and use the Nook for "typing-in-the-sun".
I have done some research but haven't found an easy way to achieve this.
I have found a description to add USB-host to a 1.2.1 NST (without Glowlight) which had been rooted with Nookmanager here: http://lararthompson.wordpress.com/2013/07/12/e-ink-writing-201-nst-1-2-1-rooted-with-usb-host/
... but unfortunately the uImage and uRamdisk linked/described in that article had the nasty side-effect of turning my NSTGlowlight into a simple NST (without Glowlight). So I had revert to my former backup and re-root with NookManager.
So my question is: What is the best and easiest way (if any) to achieve USB-host on a NST Glowlight with firmware 1.2.1 rooted with NookManager.
Thanks for your attention and help!

same situation
Hi, I'm also new on the forum, just bought my nook simple touch, did the root (Nook manager) and cound't post in the mentioned thread either so I decided to ask here. I wanted to ask if the apps/patches from the first site of that topic are ok for my firmware version 1.2.1? And can anyone explain how to:
1) apply the .diff file? I couldn't find any tips
2) how to install the usb host switcher? When I clicked the github link (from the post) I expected some .apk files, but there are some folders and other files instead. Where to put them so that it works?
3) I don't really get this: "Meanwhile you can simply switch the mode from adb, type
Code: echo host > /sys/devices/platform/musb_hdrc/mode" Where should I type it? Can it be done via cdm (windows) when I already connected my nook with the computer via wifi (and adb works fine)?
I would be really grateful for any hints. Android stuff is really not my thing, however, I would love to attach an external keyboard (I already bought a micro usb one). I have no problems following the instructions and I hope somebody will be that nice to explain it to me like I'm a child.

i want to buy an NST with glowlight but does usb host works on NST with glowlight??

There is a long thread on getting USB host support to work here: http://forum.xda-developers.com/showthread.php?t=1457971
In short, you need a kernel (uImage) that has some fixes in it for USB host mode.
Then (currently) you need something to force it into host mode.
I use my UsbMode.apk (download in the signature).

Glowlight and USB Keyboard
Hello there,
I've been through this and similar threads ten times now looking for a solution to have my NST Glowlight together with both - Glowlight AND usb-keyboard simultaniously. Unfortunately none of the uRamdisks posted do the trick. The one for 1.1.5 doesn't help in my case either because I'm on 1.2.0 (?)
So status as of todate is: I can either run the keyboard or have the lights on, depending on what uRamdisk is currently installed. I could live with that if I could take that solution outside into the sun, but:
bad girl is out playing until its dark and now wants to read a book, having no lightbulb near and having left home the laptop (with ADB to push uRamdisk for the light switch) and the Nook is running on the uRamdisk for the keyboard.
I'd like to ask now if there's the possibility to keep 2 uRamdisks on my Nook and switch them with RootExplorer or anything similar - but I can't find the uRamdisk anywhere on my Nook so I could just overwrite it. There's no boot - which might be good for girls like me who have no respect for the gadgets boot partitions But is there any (simple) way to make that partition visible using some (simple) tool that is on the Nook ? And then is it safe to just overrite that file and reboot ? Actually it shouldn't be any different from pushing the file via PC and do a restart, right ?
Would be so great if someone could help me, or was even still working on that problem of having an external keyboard working without losing the Glowlight. You guy's are doing such great work in providing people with more freedom to do what they want to do. So thank you so much, for all the information here !

No, you probably don't want to deal with two separate uRamdisk's.
(Ok, you could keep one bootable system on SD card and one internal, but that's a hassle.)
There should be a NG1 (Nook Simple Touch with Glowlight, the black case) uImage with support for glowlight and USB mode.
Unfortunately there are so many uImage/uRamdisk floating around that I've lost track.

uImage and uRamdisk
Found it. Can hardly believe it. Thought I really had tried them all. Thanks Renate for your reply. You mentioning that there MUST be one that fits tricked me into starting to search and test from scratch
5 hours later ...
Its "uImage_mt_usbhost_nopowercheck_115.zip" and "uRamdisk_NTG_115_usb.zip" and I have no idea where i found them but with the file name others should be able to find them i hope.
For those with the same problem:
my Nook ST Glowlight has Software Version 1.2.0 (which can't be changed or updated, god knows why ...) and was rooted with NookManager plus NSTAppsAttack installed. For everyone having the same device, the two files above work. They enable keyboard support and keep Glowlight and Multi-Touch working. Just push uImage and uRamdisk using ADB to the boot partition (after rooting) and everything should be fine.
Thanks to all the guys here at xda providing so much help

SusanneM said:
Its "uImage_mt_usbhost_nopowercheck_115.zip" and "uRamdisk_NTG_115_usb.zip" and I have no idea where i found them but with the file name others should be able to find them i hope.
Click to expand...
Click to collapse
Can you please tell me what does the "nopowercheck" signify ?
and what is 115 ? is it the build number, same as 166, 174, 176 ?
Thanks.

115 refers to the (then most recent) Nook software version 1.1.5
The kernel did not change much (I don't think) between 1.1.5 and 1.2.1
You should all be using the 1.2.1 Nook update with whichever kernel works for you.
The latest white Nook Glow has version 1.3 which actually has some older parts in it than the 1.2.1

SusanneM said:
Just push uImage and uRamdisk using ADB to the boot partition (after rooting) and everything should be fine.
Click to expand...
Click to collapse
Hello,
I'm new to the Nook simple root community and new to the Android world.
I try to enable the usb port of my NG1, to use an external keyboard, but i have some difficulties
I've tried to push uImage and uRamdisk via adb but:
1. can't push it, i have the read-only message
2. what is the boot partition, i tried /boot and /root
Thank you if you have any information to help me do this.

/dev/block/mmcblk0p1 is the boot partition.
If you are using noogie, it's mounted and it's what you see.
If you are running ClockWork Mod there should be an option to mount /boot
If you are just running ADB:
Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

Thanks for the quick answer.
In fact, i'm trying with adb, but i think i can't connect because mu computer is on RJ45 and not wifi.
So, how Noogie and Clockwork let me change the uImage et uRamdisk ? via usb ?
edit: in fact i'm lost here, i don't understand how to replace the uImage and uRamdisk files without adb ...

I used the noogie root method to acces the boot partition and replace the uImage and uRamdisk.
After rebooting, i plugged the mini usb keyboard i bought, but it didn't light up. Any way to be sure the usb host is activated ?

Use UsbMode.apk (in the signature).
You need to use an OTG adapter (any kind) that grounds the ID pin in the micro USB connector.
There's a whole long thread on this:
http://forum.xda-developers.com/showthread.php?t=1457971

I installed the UsbMode.apk, thank you.
Do i understand well ? I need to buy an adapter that turns the micro USB connector of the keyboard into a regular USB + an OTG that turns the regular USB into another micro USB in order to ground the ID pin ?

There are plenty of adapters for sale that are micro USB plug (with grounded ID pin) to female full-size USB.
Look up "USB OTG adapter" on eBay.

Since my keyboard is already a micro USB plug, i was wondering if it could work with 2 adapters.
But i try with a micro USB femelle to regular USB before the OTG and it works. Thanx
Now i need to install a azerty french keyboard.
I use, as i read, ES FILE EXPLORER to place the keyboard.apk into system/app, but it refuses to copy.
I'm wondering why...

The copy is probably failing because you haven't given write access to the system.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

Oh. How do i do that ?

You can just use a regular install, it doesn't have to go into /system/app
You'll have to enable the keyboard after it is installed.

[Q] USB mounting after rooting

I can't get my Nook to mount on my computer after rooting with NookManager. Is this normal? I looked for a setting to re-enable this feature but couldn't find it. Any ideas? thanks

I forget where that is on settings, but if you have ADB working you can fix that.
You need sqlite3 installed on either host or Nook.
Code:
/data/data/com.android.providers.settings/databases/settings.db
update secure set value=1 where name='usb_mass_storage_enabled';
OTOH, if you have ADB, why would you want UMS?

Renate NST said:
I forget where that is on settings, but if you have ADB working you can fix that.
You need sqlite3 installed on either host or Nook.
Code:
/data/data/com.android.providers.settings/databases/settings.db
update secure set value=1 where name='usb_mass_storage_enabled';
OTOH, if you have ADB, why would you want UMS?
Click to expand...
Click to collapse
Thanks. I'm hoping I can find the setting. I don't really know much about ADB. I just want to be able to side load books easily.

Renate NST said:
I forget where that is on settings, but if you have ADB working you can fix that.
You need sqlite3 installed on either host or Nook.
Code:
/data/data/com.android.providers.settings/databases/settings.db
update secure set value=1 where name='usb_mass_storage_enabled';
OTOH, if you have ADB, why would you want UMS?
Click to expand...
Click to collapse
Shouldn't need to change the setting for a root with NookManager. USB mounting works but I have noticed sometimes that after connecting to the PC then disconnecting it looses its ability to be connected again as a USB drive until you reboot your Nook. Haven't spent the time to track down why the Nook looses its brain sometimes and won't connect.

straygecko said:
Shouldn't need to change the setting for a root with NookManager. USB mounting works but I have noticed sometimes that after connecting to the PC then disconnecting it looses its ability to be connected again as a USB drive until you reboot your Nook. Haven't spent the time to track down why the Nook looses its brain sometimes and won't connect.
Click to expand...
Click to collapse
I've rebooted. I've used sqlite to read and verify that 'usb_mass_storage_enabled' is set to 1. I've verified getprop reports that persist.service.mount.umsauto is 1. Still no usb automount.
Rooting isn't worth not being able to use Calibre

Is the host machine Windows?
if you loaded the ADB driver things can get out of whack and the UMS interfaces are driverless.
Normally when you connect a Nook to a host two new (UMS) disks will appear.
Whether those disks have backing (data behind them) is another question.
Are you missing the disks or the data?

Renate NST said:
Is the host machine Windows?
if you loaded the ADB driver things can get out of whack and the UMS interfaces are driverless.
Normally when you connect a Nook to a host two new (UMS) disks will appear.
Whether those disks have backing (data behind them) is another question.
Are you missing the disks or the data?
Click to expand...
Click to collapse
I am running Windows and have tried two different host machines that both worked with the Nook before the root.
The Nook does NOT show up whatsoever in "My Computer". Thanks for your help, I may just reset the firmware and give up on rooting it.

Classic773 said:
I am running Windows and have tried two different host machines that both worked with the Nook before the root.
The Nook does NOT show up whatsoever in "My Computer". Thanks for your help, I may just reset the firmware and give up on rooting it.
Click to expand...
Click to collapse
Sometimes Windows won't show a removable disk if another disk it has seen has been assigned the same drive letter. Plug your Nook into your PC and go into Administrative Tools | Computer Management | Disk management and see if the disks show up there. If they do
right click on them and select Change Drive Letter and Paths and assign them drive letters. It should stick after that unless you assign the same drive letter to another removable disk.

straygecko said:
Sometimes Windows won't show a removable disk if another disk it has seen has been assigned the same drive letter. Plug your Nook into your PC and go into Administrative Tools | Computer Management | Disk management and see if the disks show up there. If they do
right click on them and select Change Drive Letter and Paths and assign them drive letters. It should stick after that unless you assign the same drive letter to another removable disk.
Click to expand...
Click to collapse
Nope. I don't here the normal USB device connected sound that I here with other things, also the Nook doesn't show the normal popup that indicates its in USB mode.
I typically don't have an SD card in it, that shouldn't matter right. I've tried it with an SD card but most of the time I don't have one in.

You have ADB working on WiFi or USB?
If it's working on USB then you obviously do have it showing in Device Manager.
A somewhat tangental comment:
There seems to be lots of people who say, "I tried to root using Mega-Super-Giga-Updater" and it didn't work so I'm going back to stock 1.1.5".
Nook firmware is old and getting older with no update in sight.
I would strongly recommend standardizing on 1.2.1
Remember, the essence of "rooting" on the Nook is just enabling ADB.
All the other stuff is just the trimmings.
I have no knowledge/experience/insight of any of these "Super-Duper-Nooters".

Renate NST said:
You have ADB working on WiFi or USB?
If it's working on USB then you obviously do have it showing in Device Manager.
A somewhat tangental comment:
There seems to be lots of people who say, "I tried to root using Mega-Super-Giga-Updater" and it didn't work so I'm going back to stock 1.1.5".
Nook firmware is old and getting older with no update in sight.
I would strongly recommend standardizing on 1.2.1
Remember, the essence of "rooting" on the Nook is just enabling ADB.
All the other stuff is just the trimmings.
I have no knowledge/experience/insight of any of these "Super-Duper-Nooters".
Click to expand...
Click to collapse
The problem was the USB cable, which straygecko mentioned in different thread. Never thought of trying a different one since this one worked fine for charging. Thanks to both of you

Oh, you probably had a "charging" cable.
I ran into one of those once.
They only have 2 conductors in the cable.
It probably saved them a whole $0.02.
It's a cruel trick to play on somebody.

Renate NST said:
Oh, you probably had a "charging" cable.
I ran into one of those once.
They only have 2 conductors in the cable.
It probably saved them a whole $0.02.
It's a cruel trick to play on somebody.
Click to expand...
Click to collapse
Don't chuck them!
I find them invaluable if you want to charge a phone or nook without using it pop up as mass storage or MTP. They are also ALOT longer.
Great for car charging or grabbing power from public usb sources.
If booting from nookmanager to PC to copy backup across (something you should do asap before you forget) then trying to connect NST to computer after rooting you will find it won't appear in windows explorer.
This is windows getting confused. If you click on the safetly remove device icon you will see two drive letters are assigned its just explorer that can't access them. Easy fix is to reboot. If your like me and dozens of web browsing windows open and regard rebooting as something the power company forces on me few times a year you can do this to access.
Start->settings->Control Panel->Administration Tools->Computer Management->Disk Manager.
You will see the drive letters for your nook there. Right click (don't click format or delete!) and chose open. Explorer will now happily open a window with your drive contents.