Related
Hello, I have CM 7.0.3 encore with the overclocked kernel on my nook. Lately I have not been able to get the thing to connect to my computer in either windows or Linux. (It's XP and "Lucid Lynx" 10.04 Ubuntu if that helps)
If I connect my cable to either the front of back USB ports (because I have tried both under both OSs) at best I get my windows install to see and start to run auto hardware install. This, of course does not work and the machine will inform me that my new hardware (which it correctly ids as a nook until this point) may not work correctly. And, it does not. It displays as 'removable drive' and clicking on it pulls up an 'insert disk please' message.
In Ubuntu the Nook will show up as B&N Ereader. Both SD cards (the internal and the card in slot) show as the same thing. Clicking on them brings up a message that this drive is not a folder and cannot be opened as such.
This thread leads me to think that there should be a notification in windows about the usb being connected...and as soon as I post this I will be restarting to check that... but I really rather do this under Ubuntu. ETA. This does not work for me. Canceling the install software wizard does not work either. (I have been uninstalling the faulty installs each time and rebooting the comp without the nook attached. Oh, and the Nook IS awake too. )
Searches bring up nothing, and I'm a bit lost.
I must be missing something so basic and simple no one has had this issue but me. I mean, Android is a Linux variant, right? They should be able to talk to one another!??
If your trying to accomplish what I think you are then it doesn't matter what your computers says. Plug your Nook into the PC and open your notifications window. There should be a USB icon on the status bar waiting for your input. Just follow the prompts.
Given you have gone through the process of installing the Android SDK, in Linux, from the terminal you need to change to your target folder to
Code:
~/android-sdk-linux_86/platform-tools
then you need to log in as root and kill, then start the server. make sure to exit root when you are done.
Code:
su : enter password
# ./adb kill-server
# ./adb start-server
# exit
then it should pick it up.
I have the same problem as OP and went crazy trying to figure out what I was doing wrong. It's not as simple as everyone suggests.
To be clear I'm using Linux, Ubuntu Natty. I have a Samsung Vibrant also running CM7 nightlies. Start adb, plug in Vibrant, shows up in adb devices list without any problem. Plug in the NC no device in adb. running lsusb there is no android vendorID for the NC but there is for the Vibrant. The NC only shows a vendorID for the mass storage just like the OP says.
The NC is booting with CM7 nightlie on the SD card, not eMMC. Will that make a difference?
IFLATLINE, Thing is, there is no notification popup on my Nook for me to tap.
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
I did manage to brick the nook trying to update the build last night so I'm in the middle of reflashing it. So, as soon as I finish making a boot micro SD (I know, I should just have one I keep for this but I don't) I will be flashing phiremod's version of CM7 on the nook.
digver, I did find somewhere on here that the OC kernel was causing some people grief and that once they removed it they had no issues connecting the the computer... but I think they were windows. I'm not sure if that will fix this very annoying little problem.
katsrevenge said:
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
Click to expand...
Click to collapse
personally i <3 linux. It's the only way to fly esp with dealing with Androids. Android Central has a GREAT write up on how to install the SDK on your Linux unit.
I'll have to look up the link @ home. I'm at work and WebSense blocks 99% of everything.
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
marchingknight11 said:
Apologies if this is already posted somewhere. just point me to the link and I'll take a look, but everything I have tried so far has failed.
I have been trying to get adb working on my NookColor under Windows 7. I am running a rooted 1.4.2 stock image. I installed the sdk by following the guide at http://nookdevs.com/NookColor_USB_ADB, but when I get to step III.3.1, the device does not show up where the guide tells me it should. I gget a myNOOKcolor device under Portable Devices instead. I tried following the same procedure for this device, but when I get to step III.3.2.3, I get an error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I was able to follow the same procedure to install the driver for my MyTouch 4g. It looks to me like the problem s that Windows identifies my Nook as a portable storage device, rather than an unidentified device type, like my MyTouch was. I've tried uninstalling the driver, but it just reinstalls itself when I unplug and plug the device back in.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
leapinlar said:
I think the problem is the device id. I posted a workaround for CM9. It might be the same for your upgraded stock. See if my post helps. Look here:
http://forum.xda-developers.com/showthread.php?p=21665649
Click to expand...
Click to collapse
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
marchingknight11 said:
Thanks for the post!
I looked at your workaround and it did not help. There is no nook entry under "Other Devices" in the device manager. the only entry for my nook is the "myNOOKcolor" under portable devices. When I right click on that and go to details, there is no device id listed.
Is there any chance that I may need to revert to 1.4.1 in order for this to work?
Click to expand...
Click to collapse
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
leapinlar said:
With CM9, you have to be sure to have usb debugging turned on before the device will show up. That guide was written for an earlier version of the stock software. Is there anything like that in your stock software? Do you have to install nook tools to get at the setting? It's been a long time since I played with stock and the software has changed.
Edit: There is an alternate script listed in that referenced page you listed. Did you try that?
Click to expand...
Click to collapse
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
Yes, but with difficulty. But you don't really want to install to /system, you want to install to /data (on emmc, which is the difficulty doing it from SD). You can use terminal emulator in CM7 to copy the files to emmc /data/apps. You first have to mount emmc /data. If you want to try that, I can help you.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
marchingknight11 said:
Well something else actually occurred to me. Will I be able to copy apps to my sdcard (not the CM7 bootable, just a regular sd card), then copy them to /data/app using root explorer? If I can do that, there there's really no problem, I'll just have to deal with the fact that adb doesn't work.
If I can't do that, then yes, please help me do it using a bootable sd
Click to expand...
Click to collapse
If you have root explorer working on emmc, yes you can do it that way. You can actually have root explorer just install for you also.
Sent from my Nook Color running ICS and Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
marchingknight11 said:
I have trtied all the troubleshooting steps in that page, if that's what you mean. Nothing has worked for me so far. I have tried disabling automount and usb debugging, to no avail.
I guess I should ask a new question. If I create a bootable CM7/CM9 sd card, will I be able to copy apk's to /system/app on my nook? That is really the only reason I need adb to work, so I can install non market apps.
Click to expand...
Click to collapse
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Droidatar said:
I am using CM10 on my nook color after spending 8+ hours yesterday finally being able to get back to where I started. I can again see my nook and the card but it is now showing up under portable devices. I used to have them listed as drives. this is fine as I have access to the card after I click on the nook in File explorer. I would like it the previous set-up just because Calibre has my card and device flipped and its easy to confuse me. I learned that if I can label my nook f and the card g Calibre will think the first letter is the main drive.
My original reason for this post: I can not find where to disable the automount in CM10 can you tell me where you disabled it? and if anyone can wave their magic wand and get me back to where I can name my nook and card THANKS:fingers-crossed:
Click to expand...
Click to collapse
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
You need to activate USB Mass Storage in CM10. It uses MTP by default. Go to settings, storage, menu, USB computer connection and check off Mass Storage rather than MTP. Then they show up as drive letters instead of under portable devices. You may also have to activate in the notification area.
And I think in Windows you can control what the drive letters are. Go to manage computer and select disk management and you can change the drive letters.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
THANK YOU, so very much it has been driving me crazy. I knew where that was to change it to mass storage but I just never guessed to hit menu. After I read your post I saw the tiny 3 dots in top right. I really should just wear my glasses
and Yes I have changed the letters in the past as you have noted. However it seems a mute point Calibre just released a new version that lets me correct that problem. However it's nice to have the mass storage issue fixed.
Thanks again
So I just bought a brand new Nook HD+ from best buy. It is in shrink wrap so looks factory new.
I first turn it on and it gives me the select the lanuage and country page (No wifi selected). I do not proceed. Press volume down and tap lower left hand corner. If gves me the Enable ADB button. I do not press it yet. Instead I plug it into computer, which then puts it in MTp mode.
I unplugged cable and now press the Enable ADB button. I plugged it back in and same MTP mode.
I then decided to skip OBE. So I press lower volume button and then lower left screen followed by lower right screen. Then I press the Factory button. Then the Skip OBE option.
Now I am at home screen, I go to settings, then developers, and I confirm the ADB status. just to be sure, I uncheck ADb and then rechecked it. Plugged it back in and same result. It puts it in MTP mode.
I then confirm by going to Device Manager and see no entry for Android Composite device.
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Need Windows Driver for Nook
I believe you need a windows driver for the Nook HD and HD+ on Windows. On Ubuntu, I just do "android update device && adb kill-server && adb start-server && adb devices"
I can't post links. google usb_driver_r04-windows
superflysocal said:
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Click to expand...
Click to collapse
They could be working now on out of the box 2.0.2 now. Don't know.
You are not telling us much about your PC, which we need to know to help you. What version of Windows are you running? Have you got ADB running on any other devices?
No other new devices are showing? Did you follow the B&N trouble shooting guide section 4.6 which I reference in my HD+ tips thread linked in my signature.
Sent from my Nook HD+ Running CM10 on SD
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
superflysocal said:
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
Click to expand...
Click to collapse
Well, since you had other devices using ADB, then go to device manager and look under USB controllers. Uninstall any USB composite device there, especially any that has the device id under properties and details listing 2080 as part of the number. That will force the system to re-recognize and reinstall the right driver you can get from my HD+ tips thread.
Sent from my Nook HD+ Running CM10 on SD
There was a usb composite but it was for my wintv usb, I uninstalled it anyways. Nothing else, still not doing anything. Any chance this is a new hardware version that has this locked down?
It did come with 2.0.2 instead of 2.0.0
I don't see a reason for a hardware revision, and there is no reason for 2.0.2 instead of 2.0.0 other than bug fix since you can still root with 2.0.0 - 2.0.4. The inability to ADB is on your part. Seriously I don't see why would B&N lock down people ability to ADB since it's a requirement for people to develop for Nook platform. It's not like B&N will make 2 different versions of each device, one for developers and the other for consumers. I can still see B&N may lock down ability to root with current method on future revision (say 2.0.5+) but as of now it's open. ADB will never be lock. I think the fact that ADB for Nook devices are hard to get to will not only deter people from root but people to develop for the platform as well. Personally I think it's a bad choice on B&N part to have it hard for people to ADB.
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
superflysocal said:
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
Click to expand...
Click to collapse
I just bought a HD+ from Walmart. It was 2.0.2 out of the box and I was able to root the device successfully after OOBE was completed. I don't remember if the device upgraded itself to 2.0.4, I'll check later. I did the all in one root process on a Win7 64bit lappy so try it and see if it works.
IMO the person who posted about the sdcard file corruption has hardware issues but who knows? No one else is reporting having this issue afaik.
There are people that report a success ADB driver install on win7 64bits via my method. Check the tips thread.
someone0,
just curious, what firmware are you on? 2.0.4? Are you having any sd card write issues?
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
superflysocal said:
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
Click to expand...
Click to collapse
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
leapinlar said:
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
Click to expand...
Click to collapse
Oh you are so rght. I never did figure out what is blocking it, too impatient to uninstall stuff.
BUT, I did find an old seldom used laptop with win 7 32-bit. When plugged in it gave me error that drivers could not be installed!. Went to device manager, found the device and updated driver. Adb achieved and all in one root done.
No, I'm on 2.0.0
Please help but beware I am a totally noob so you may have to explain things like you would to a five year old.
I rooted my Nook Color (firmware 1.4.3) with instructions from a Youtube video. (CyanogenMod 7) It allows us to boot to CyanogenMod with the sd card OR by removing the sd card it boots normally into the Nook Color.
It worked great for me but I lent the Nook to my sister and when she connected it to her pc (Windows 7) it indicated that it could not find the driver software for the nook - there is now a "yellow !" in her device manager so we uninstalled that and rebooted with the Nook plugged in and turned on but it still indicated that it was unsuccessful. The two drives do appear in my computer (F & G) however if we click on either one of them it says to insert a disk.
We have tried booting without the sdcard in it - tried different ports on the pc (in fact she has another pc running Windows 7 & it does the same thing) - we also tried a different cable. Nothing has helped so far.
Please help. Thank you in advance.
soxenme said:
Please help but beware I am a totally noob so you may have to explain things like you would to a five year old.
I rooted my Nook Color (firmware 1.4.3) with instructions from a Youtube video. (CyanogenMod 7) It allows us to boot to CyanogenMod with the sd card OR by removing the sd card it boots normally into the Nook Color.
It worked great for me but I lent the Nook to my sister and when she connected it to her pc (Windows 7) it indicated that it could not find the driver software for the nook - there is now a "yellow !" in her device manager so we uninstalled that and rebooted with the Nook plugged in and turned on but it still indicated that it was unsuccessful. The two drives do appear in my computer (F & G) however if we click on either one of them it says to insert a disk.
We have tried booting without the sdcard in it - tried different ports on the pc (in fact she has another pc running Windows 7 & it does the same thing) - we also tried a different cable. Nothing has helped so far.
Please help. Thank you in advance.
Click to expand...
Click to collapse
I am assuming you want to connect to the PC to transfer some files back and forth rather than to connect ADB. If you don't know what ADB is, that means you were not wanting that.
To fix the issue, boot to CM7 and go to settings, applications, development and uncheck Android debugging. Then connect the cable to the PC (I always have to do it twice), and a screen on the nook will pop up saying "USB connected" with a "turn on USB connection" button. Touch that button and a confirmation box pops up. Click OK. You should now see the drives on the PC and they should work. If that first screen does not pop up after plugging in twice, open the notification area from the bottom of the screen and a notification that says "USB connected" should be there. Touch that and the pop up will open.
The issue was the debugging choice which is an advanced feature you probably did not want and Windows was looking for a driver to make it work.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
You are spot on - i have no idea what "ADB" is and just want to be able to transfer files from the pc to the Nook Color. We will try as you suggest and let you know how it goes - THANK YOU for helping!
This worked PERFECTLY!!!!! Thank you leapinlar for your 'easy to understand' directions and providing us with the answer so quickly. We just couldn't be happier! Many many thanks!
Hello, nookies!
Today I have decided to make an easy-to-follow guide on mounting USB devices (cameras, USB sticks) on your Nooks! Hooray! :good:
DISCLAIMER - I am not responsible if you brick your Nook, break your USB device, the current state of the economy, or why Obama is the president. Please do research on these topics if you would like to know more.
DISCLAIMER 2 - I did not make either of the apps attached, I have merely posted them here for easy access.
So let's get started with some prerequisites!
Prerequisites:
A rooted Nook Touch or Nook Touch Glow with software 1.2.1 installed, as well as Superuser and su binary installed
A terminal app (attached below)
Renate NST's UsbMode.apk (attached below)
A USB host-enabled kernel correctly installed and working (see my signature for a Nook Touch Glow one)
A USB OTG cable
Steps:
Make sure that your Nook is completely charged before continuing!
Make sure that your kernel is definitely working and that USB mode is properly working, too!
1. Open up Renate NST's UsbMode.apk app. Tap the "Off" button. (This will stop your Nook from trying to charge itself from the USB device by turning off the current.)
2. Plug your USB OTG cable (without anything attached to it) into your Nook's USB port.
3. Tap "Host" in the UsbMode app. (This turns on Host mode.)
If the LED beside your Nook's USB port has turned solid green at this point, you are doing well!
4a. For USB devices that have a separate cord (cameras): Turn on the USB device. Plug its cord into its USB port. Now, connect both the device's cord and the device into the open end of the OTG cable that is attached to your Nook.
4b. For USB sticks/drives: Plug the drive directly into the open end of the OTG cable that is attached to your Nook.
5. Tap "View USB" in the UsbMode app. You should see the Nook's main listing at the top, as well as the plugged-in device's listing under it. The device's listing should have a black dot next to it.
Good job! You're doing well so far! :laugh:
6. Now, open up the Terminal Emulator app I attached below. You should have installed it already. When it opens, you should see a dollar sign ($) at the far left of each line.
7. Type in
Code:
su
. Now, instead of a $, there should be a # at the far left of each line.
8. Type in
Code:
mount -o rw,remount rootfs /
. This remounts /system as read-writable.
9. Type in
Code:
mkdir /usb
. This creates a directory called /usb in the root of your Nook's filesystem; it will be used to mount your USB device in.
10a. For USB devices (cameras, etc.), first type in
Code:
mount -t vfat /dev/block/uba /usb
. You will get some sort of error message, that's okay. Now, after typing that, type in
Code:
mount -t fvat /dev/block/uba1 /usb
.
10b. For USB sticks/drives. just type in
Code:
mount -t vfat /dev/block/uba1 /usb
.
11. If the above commands worked properly, you should now be able to go into a file explorer, navigate to the /usb directory, and boom! You can now manage your USB device's filesystem straight from your Nook!
Unmounting your USB drive
It is important that you unmount your USB device/drive properly before physically taking it out of your Nook. Here's how to do that.
1. Open up your Terminal Emulator app again.
2. Type
Code:
su
.
3. Type
Code:
mount -o rw,remount rootfs /
.
4. Type
Code:
umount /usb
.
5. Type
Code:
rmdir /usb
.
6. Take the whole cord/USB drive out of your Nook with the OTG cable.
7. Open up the UsbMode app again.
8. Tap "Auto". (This turns your Nook's current back to being automatically determined, instead of being off.)
9. Tap "Peripheral". (This makes your Nook return to having the ability to charge from an AC outlet (or whatever).)
10. You have successfully unmounted your device!
Hope this helps all of you guys who want to manage your USB devices on your Nooks! :good:
Reserved
Reserved for future use/expansion.
I hate to do this, but...
Bump.
I'm sure that someone can profit from this tutorial, right?
There was a whole thread on using my modified volume daemon to do this all automatically.
I've pretty much abandoned that train of thought.
I'm not really sure that anyone really wants to mount USB drives.
It's really a pretty current-intensive way to get data.
It's better to just use a 32 GB SD card in the Nook, formatted with something better than vfat.
Renate NST said:
There was a whole thread on using my modified volume daemon to do this all automatically.
I've pretty much abandoned that train of thought.
I'm not really sure that anyone really wants to mount USB drives.
It's really a pretty current-intensive way to get data.
It's better to just use a 32 GB SD card in the Nook, formatted with something better than vfat.
Click to expand...
Click to collapse
thanks for the efforts @Renate NST in creating the USB mode app, I really envy you guys for the knowledge and understanding you have of the tech involved.
I agree with you on the practicality of the application.
At the same time and more we can never let go off the THRILL in trying the invaluable efforts you manage to put in.
Kudos.
Coming back to the thrill of it all ...
@NoogiE ... thanks for the link to this thread ...
i am on 1.3.4 version of your 1337 ROM, assuming the USB kernel is in place, i opened @Renate NST's USBMode app and pressed Off, then i connected the OTG cable and pressed Host ... no action no led action ... if you can help ... thanks.
thanks,
aiamuzz said:
no action no led action ...
Click to expand...
Click to collapse
Hmm. You have this rooted and the UsbMode is not showing any "<errors>"?
You're sure that it's an OTG cable? (I've never seen one over 6" long. If you know of a longer molded cable, please tell me!)
You're sure that your kernel has the OTG fix?
You should get a quick flash (50 mS or so) out of the LED just pushing the host button on UsbMode even with nothing connected at all (no adapter).
With an adapter connected you should get a solid LED.
I've never gotten into writing/patching kernel drivers, but I always thought that someone would fix the buggy USB driver so that UsbMode would not be needed for regular OTG operation.
Renate NST said:
Hmm. You have this rooted and the UsbMode is not showing any "<errors>"?
You're sure that it's an OTG cable? (I've never seen one over 6" long. If you know of a longer molded cable, please tell me!)
You're sure that your kernel has the OTG fix?
You should get a quick flash (50 mS or so) out of the LED just pushing the host button on UsbMode even with nothing connected at all (no adapter).
With an adapter connected you should get a solid LED.
I've never gotten into writing/patching kernel drivers, but I always thought that someone would fix the buggy USB driver so that UsbMode would not be needed for regular OTG operation.
Click to expand...
Click to collapse
Hey thanks for looking into it @Renate NST ...
I am using the small 4-5 inch cable ... had a spare lying around.
I am not getting the quick flash you talk about while a press the Host button.
However when i open the USB Mode app the first line 'Request' shows empty, when i press the Host button it says <write error>
when i engage the buttons (off, 100mA, 500mA, 1.5A & Auto) the Max Current line blinks between <write error> and Auto ...
If that helps !!!
and the kernel part, I am running a copy of Yattaro and Nookie's 1337 ROM(the latest 1.3.4) which claims it supports USB host capability.
Is there any way i can run a command to check if the kernel supports ? Not that i doubt/question this ROM developers efforts/claims.
aiamuzz said:
Hey thanks for looking into it @Renate NST ...
I am using the small 4-5 inch cable ... had a spare lying around.
I am not getting the quick flash you talk about while a press the Host button.
However when i open the USB Mode app the first line 'Request' shows empty, when i press the Host button it says <write error>
when i engage the buttons (off, 100mA, 500mA, 1.5A & Auto) the Max Current line blinks between <write error> and Auto ...
If that helps !!!
and the kernel part, I am running a copy of Yattaro and Nookie's 1337 ROM(the latest 1.3.4) which claims it supports USB host capability.
Is there any way i can run a command to check if the kernel supports ? Not that i doubt/question this ROM developers efforts/claims.
Click to expand...
Click to collapse
You seem to be having a an su binary issue. Check and see if the su binaries are in /system/bin; if they aren't, copy them there from /system/xbin and reboot. Should work like a charm.
ИΘΘK¡€ said:
You seem to be having a an su binary issue. Check and see if the su binaries are in /system/bin; if they aren't, copy them there from /system/xbin and reboot. Should work like a charm.
Click to expand...
Click to collapse
hey Nookie ... copied the su to to /system/bin and the led came up ... but i can't see the connected device under 'View USB', could it be bcos i am using a Micro SD card on in USB adapter ?
PS: and hey i saw swapon and swapoff files(binaries?) in /system/xbin, does it mean your ROM supports SWAP ? With swap and hopefully NookKat the RAM deficit could be manageable ? My first Android Device was LG Optimus Pro, C660 which had 256 MB RAM & 140-160 MB internal storage for apps, The stock ROM used to keep popping the close any programs popups every now and then rather freqeuntly, On a custom CM7 official port ROM with swap support & dark tremors ap2sd scripts, i was able to get rid of the annoying pop up and install 60-70 user apps to SD card and still have a daily ROM. Do you think our device supports a similar setup with swap and darktremors aap2sd scripts ?
thanks
Quick N00b question- I am trying to get a GPS signal into my rooted NST. It has a micro USB. Do I need to do this in order for an app to get my serial signals?
I will paypal someone to help me get GPS signals into my NST using an app called Simple Sailor! Thx
lolokai said:
Quick N00b question- I am trying to get a GPS signal into my rooted NST. It has a micro USB. Do I need to do this in order for an app to get my serial signals?
I will paypal someone to help me get GPS signals into my NST using an app called Simple Sailor! Thx
Click to expand...
Click to collapse
Maybe. I'd have to look into your quest more to know for sure.
ИΘΘK¡€ said:
Maybe. I'd have to look into your quest more to know for sure.
Click to expand...
Click to collapse
Thx Nookie.
Is an app that can see what serial data is being provided via USB? Or, a GPS testing app that grabs data from the USB. Do apps always look for GPS data to come in via USB or is there another place that an app would look for GPS data?
lolokai said:
Thx Nookie.
Is an app that can see what serial data is being provided via USB? Or, a GPS testing app that grabs data from the USB. Do apps always look for GPS data to come in via USB or is there another place that an app would look for GPS data?
Click to expand...
Click to collapse
To tell you the truth, I don't think either of those exist. I could be wrong, though - @Renate NST has done some stuff using an old GPS puck on her Nook, so you can ask her.
ИΘΘK¡€ said:
To tell you the truth, I don't think either of those exist. I could be wrong, though - @Renate NST has done some stuff using an old GPS puck on her Nook, so you can ask her.
Click to expand...
Click to collapse
Hey thanks Nookie. I have found some info from both Top hat Soaring (glider people who needs daytime screen visibility as well as ADV riders - motorcycle navigation with again, daytime visibility) so I'll be pursuing those. Thanks again.
I looked into all this a while ago.
You should be able to go right from serial into the LocationProvider.
Strangely enough, most of the stuff I saw back then was using the mock location to handle the data.
This seemed like a detour to me.
I really should follow this up.
Using USB host mode and serial USB is not optimum due to the wackiness in the USB driver and the current draw.
This is a 1.8V GPS module: https://www.sparkfun.com/products/10890
Besides the advantage of low voltage/low power, the 1.8V serial can interface internally and directly to the Nook.
I think that I'll be ordering one of these.
I do not know anything about programming.
But I can do all the manual. ))
What am i doing wrong?
Excuse me. Forum does not post a link to the picture. I'm new here ... It is necessary to dial 10 messages.
You must manually copy the link in Internet Explorer.
http:
//i5.imageban.ru/out/2015/08/27/
1dcc71f5ed606d4e51a1c7ed10cec568.png
Nik782 said:
I do not know anything about programming.
But I can do all the manual. ))
What am i doing wrong?
Excuse me. Forum does not post a link to the picture. I'm new here ... It is necessary to dial 10 messages.
You must manually copy the link in Internet Explorer.
http:
//i5.imageban.ru/out/2015/08/27/
1dcc71f5ed606d4e51a1c7ed10cec568.png
Click to expand...
Click to collapse
It looks like your Nook is not recognizing any drives being plugged into it.
Can you give me some more details on your progress thus far?
NOOK!E said:
It looks like your Nook is not recognizing any drives being plugged into it.
Can you give me some more details on your progress thus far?
Click to expand...
Click to collapse
Here is my story in detailed illustrations.
https:
//ww
w.dropbox.com/sh/47n1bhgd3usq15q/
AAAh5uIrxWnVWbbgoXY7PQy3a?dl=0