Quote:
Originally Posted by Renate
Aw, is that UMS? Do you really want to use that? Doesn't MTP (which I don't particularly like either) give you access to more? Why not ADB? You can see /sdcard.
There's a bunch of weirdness with this device. I'm trying to make a rooted recovery. For some reason fastboot can't directly boot an image correctly. Fastboot also presents as VID/PID 1f3a/1010 which is not recognized as a stock Fastboot. You have to install a driver for it. It's basically a generic WinUsb but unless the class GUID is GUID_DEVINTERFACE_ANDROID the stock Fastboot won't find it. You need to take an Android INF file and add 1f3a/1010 to it and install it as an unsigned driver. In Linux there should be no problem as it doesn't use device class GUIDs.
|
Doing an adb install of a file manager allows me to see most, if not all, folders on the device. What I was talking about in my last email is what you get when you use the device as B&N intends you to. ; )
I haven't dug down as far as you have yet, but I've found some weirdness of my own. Some apps will not install through adb install. Terminal just hangs. I need to copy the apk to the Nook, use a file manager, select "open with" when I press on the apk, and then choose the installer. Then it installs!
Previous Nooks had their own weirdness, as I recall.
Edit: My Ubuntu VM terminal can connect with my Nook. That may prove helpful!