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
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?
While my original NC is running quite well with the CM10 nightlies, I have lost my ability to use the USB cable as my file transfer source since leaving CM 7.2.
I now do all of my files transfers directly to the SD card by removing it and accessing it directly via my computer.
I get the following when the cable is connected: "USB device not recognized".
I have tried both Media Device and Mass Storage settings to no avail.
This was not an issue with CM 7.2.
Seems to be the only real issue I am experiencing since I was able, with forum help, to redo my inadvertently updated NetFlicks.
Thanks in advance for any suggestions.
harryzee said:
While my original NC is running quite well with the JZO54K nightlies, I have lost my ability to use the USB cable as my file transfer source since leaving CM 7.2.
I now do all of my files transfers directly to the SD card by removing it and accessing it directly via my computer.
I get the following when the cable is connected: "USB device not recognized".
I have tried both Media Device and Mass Storage settings to no avail.
This was not an issue with CM 7.2.
Seems to be the only real issue I am experiencing since I was able, with forum help, to redo my inadvertently updated NetFlicks.
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
First, don't call the ROM JZ054K, it is CM10. You confuse folks. The problem probably is you have USB debugging enabled. Go to settings, developer options and uncheck Android debugging.
Sent from my Nook HD+ using Tapatalk
Followed your suggestion and unchecked Android Debugging. Rebooted and then hooked up the USB/Recharge cable. Still have same result with the "USB device not recognized" being displayed by Win7/64 with both Media Device or Mass Storage being selected.
Any other paths to explore on this?
Utilized my ROM nomenclature based on "About tablet: Bulid Number" and will switch to CM10 if that is a confusing issue.
leapinlar said:
First, don't call the ROM JZ054K, it is CM10. You confuse folks. The problem probably is you have USB debugging enabled. Go to settings, developer options and uncheck Android debugging.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
harryzee said:
Followed your suggestion and unchecked Android Debugging. Rebooted and then hooked up the USB/Recharge cable. Still have same result with the "USB device not recognized" being displayed by Win7/64 with both Media Device or Mass Storage being selected.
Any other paths to explore on this?
Utilized my ROM nomenclature based on "About tablet: Bulid Number" and will switch to CM10 if that is a confusing issue.
Click to expand...
Click to collapse
The device id and vendor id are different in the CM10 from CM7, you would need to edit the android_winusb.inf file to include them.
harryzee said:
Followed your suggestion and unchecked Android Debugging. Rebooted and then hooked up the USB/Recharge cable. Still have same result with the "USB device not recognized" being displayed by Win7/64 with both Media Device or Mass Storage being selected.
Any other paths to explore on this?
Utilized my ROM nomenclature based on "About tablet: Bulid Number" and will switch to CM10 if that is a confusing issue.
Click to expand...
Click to collapse
Are you sure it is still unchecked? Did you go back and look after rebooting. You should not have to reboot to turn it off. That device not recognized issue is it is looking for ADB drivers because the debugging box is checked.
Sent from my Nook HD+ using Tapatalk
Yes, went back and looked and it was still unchecked. Normally reboot when I make any changes but went back and redid your suggestion from scratch without rebooting with same result.
leapinlar said:
Are you sure it is still unchecked? Did you go back and look after rebooting. You should not have to reboot to turn it off. That device not recognized issue is it is looking for ADB drivers because the debugging box is checked.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
harryzee said:
Yes, went back and looked and it was still unchecked. Normally reboot when I make any changes but went back and redid your suggestion from scratch without rebooting with same result.
Click to expand...
Click to collapse
The only thing I can think of is to go device manager in Windows and uninstall any devices in portable devices, android phone and under USB controllers, any mass storage devices. Then unplug and replug it back in, assuring debugging is still of. You should now get messages that things are installing, hopefully automatically.
Sent from my Nook HD+ using Tapatalk
I'm having the same issue, was using the Dec 2 and now 3 nightly. when I get time tonight I will roll back to Dec 1 since I know it was working there. Win7/Win8 here fyi
Unsuccessful
Tried: "...and under USB controllers, any mass storage devices." This actually allowed WE to show "Nook Color" but when I clicked on it, there was nothing there. The unit did temporarily display a USB connection at that time also.
Again, this was not an issue under CM7.2.
Thanks for your ongoing assist!
Update: Okay tried every conceivable way of deleting some or all of USB drivers under DM and reinstalling. Even went into BIOS and turned down USB 3.0 to 2.0!
Again erratically got the Andoid USB screen temporarily a couple of times but could not maintain it.
Definitely getting a Windows "Code 43" error indicator.
leapinlar said:
The only thing I can think of is to go device manager in Windows and uninstall any devices in portable devices, android phone and under USB controllers, any mass storage devices. Then unplug and replug it back in, assuring debugging is still of. You should now get messages that things are installing, hopefully automatically.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
harryzee said:
Tried: "...and under USB controllers, any mass storage devices." This actually allowed WE to show "Nook Color" but when I clicked on it, there was nothing there. The unit did temporarily display a USB connection at that time also.
Again, this was not an issue under CM7.2.
Thanks for your ongoing assist!
Update: Okay tried every conceivable way of deleting some or all of USB drivers under DM and reinstalling. Even went into BIOS and turned down USB 3.0 to 2.0!
Again erratically got the Andoid USB screen temporarily a couple of times but could not maintain it.
Definitely getting a Windows "Code 43" error indicator.
Click to expand...
Click to collapse
If you are getting windows errors installing drivers you may want to look at this post. It is for the HD+ and trying to get ADB working, but there is some interesting stuff there about unsigned windows drivers that may apply to you.
http://forum.xda-developers.com/showthread.php?p=34954992
Sent from my Nook HD+ using Tapatalk
Ongoing!
Will do!
It was very frustrating seeing the Android USB screen fleetingly appear several times and not be able to nail it down. I even got the WE screens for both drives briefly at one point!
Any idea as to why the issue exists with CM10 and not CM7.2?
leapinlar said:
If you are getting windows errors installing drivers you may want to look at this post. It is for the HD+ and trying to get ADB working, but there is some interesting stuff there about unsigned windows drivers that may apply to you.
http://forum.xda-developers.com/showthread.php?p=34954992
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
Followup
Went there (http://forum.xda-developers.com/showthread.php?p=34954992) ...did that. Did not work at first, but it did work (somewhat) after I went back in and deleted the three drivers. I was then able to connect and utlilize WE to probe and adjust both emmc and sdcard. Calibre recognized that it was connected but I could not transfer anything directly from it to the NC.
Thanks for all of the help with this. Since I am probably around eight weeks from purchasing my HD+, I will just use the SD card to manually transfer files.
Interesting issue nonetheless!
leapinlar said:
If you are getting windows errors installing drivers you may want to look at this post. It is for the HD+ and trying to get ADB working, but there is some interesting stuff there about unsigned windows drivers that may apply to you.
http://forum.xda-developers.com/showthread.php?p=34954992
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I plugged my nook into a couple different computers and it was like the computer didnt even recognize something was plugged into the computer, though it charged the nook fine.
Had same problem, I went to settings - storage - then the menu box top right (three dots) then choose USB computer connections.. For the most of the time I just leave mine on Mass Storage -- On the second - I just leave the stock file manager and install any others I use - stock is not a lot of overhead for me to bother removing...
concise69 said:
Had same problem, I went to settings - storage - then the menu box top right (three dots) then choose USB computer connections.. For the most of the time I just leave mine on Mass Storage -- On the second - I just leave the stock file manager and install any others I use - stock is not a lot of overhead for me to bother removing...
Click to expand...
Click to collapse
Thanks, that got it working!:good:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
jamus28 said:
I had to install the Google USB android drivers from the SDK as well. Without these, I spent hours trying to get it to work. The b&n drivers alone were not enough.
Win 7 x64
Click to expand...
Click to collapse
Thanks both Ardent_V and jamus28 for the explanation.
Yes I have to apply both methods in order to have the adb command to recognize my Nook HD+ device ID.
I'm using windows 7 x64.
Sorry. I assumed if you had adb you would have the SDK and Google drivers as well.
On previous devices, adb.exe and a few DLLs were enough.
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Steve Tack said:
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
Click to expand...
Click to collapse
That's just me being lazy and not gettin around to pass around serial number yet.
Steve Tack said:
Thank you for posting this!!!
I did have to deviate from the instructions a bit to get it working though.
1. In the INF file, I had to use the *second* line from Hardware Id's, not the first. The value that worked for me in the INF file is:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&MI_01
The first Hardware Id's line has a "REV_02" in it; Windows would not accept the driver with that in it. Took that part out and it worked!
2. Instead of updating the driver in Device Manager from Portable Devices, I had to update the "BN NookHD+" that was listed with a yellow symbol under "Other devices." Then I got the expected Android Phone -> Android Composite ADB Interface device to show up in the list.
3. ADB at first listed the device as "offline." I had ADB working on stock and didn't realize that the newer version of Android has an extra security check. I actually had to Google it to realize that I just had to unlock the tablet and hit "Accept" on a dialog box on the device! After that, it went from "offline" to "device" and all was well.
What's a bit strange is that before ADB listed a random bunch of letters and numbers (a device ID I guess?). But now it lists the Nook as 012345679ABCEDEF. I'm guessing that's just how it works under CM10.1? I suppose it hardly matters.
The bottom line is that I got it to work, thanks to this thread. Nice!
Click to expand...
Click to collapse
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
verygreen said:
That's just me being lazy and not gettin around to pass around serial number yet.
Click to expand...
Click to collapse
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------
dawgpoundfan said:
Made sure that I had updated Google Drivers and tried both strings and Windows showed no erros but when I type adb devices it is blank.
Click to expand...
Click to collapse
Do you see a device category in Device Manager called Android Phone? On my system, I see that and under that is a device called Android Composite ADB. Both times I've set it up, it wouldn't show up in ADB until I got to the point where that device showed up in the list.
If you do see that device, I suppose you could try "adb kill-server" before "adb devices" just for grins.
Steve Tack said:
Hehe, figured it was something like that. Is there any downside to not having the real serial number returned? Doesn't seem to cause any issues that I've seen.
Click to expand...
Click to collapse
Dunno, but 6/30 release added that. I imagine some apps might be using serial number for things like ensuring you don't steal stuff, also google play probably uses that to distinguish between several identical device you might have
If you are running the latest Carbon B11 emmc, and are wondering why you can't get "adb devices" to show your device, you need to insert a line to:
%userprofile%\.android\adb_usb.inf
add: 0x2080
Without this, ADB will not recognize a device with a B&N VID.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
Crap, just realized I skipped step 7 in Leapinlar's thread on setting up ADB...
error
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
2. Enable Android debugging in developer settings.
3. Plug Nook into PC and open Device Manager.
4. Go to Portable Devices/BN Nook HD/HD+ and open properties.
5. Go to the details tab and then hardware ID's in the menu.
6. Leaving that window open, unzip the usb driver. Open the folder, and then open android_winusb.inf in an editor. (I used Notepad++)
7. In the .inf file, scroll through [Google.NTx86] and find your device name. Replace USB\whatever with the first hardware ID in the list from step 5.
8. Do the same in [Google.NTamd64]
9. Save and close the file, and then go back to device manager. Click update driver/browse my computer for software in properties.
10. Navigate through and choose the modified usb_driver_r04-windows folder.
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
toplist said:
I followed all the steps. I got the device connected. When I tried to sideload a stock rom zip, I get an error. "failed to write data protocol fault <no status>". What can I do to fix it?
Click to expand...
Click to collapse
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
What do you mean sideload a stock rom zip? Sideloading is for apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
toplist said:
I had bokbokan's hybrid running on nook hd+. I saw an experimental version of cm10.2 and wanted to give it a try. I thought that since I can boot to stock and cm, I don't need to go back to my original bn rom. So, I deleted my cm10,1 zip from my internal storage and replaced it with cm10.2. I turned off my tablet, took out my sd card with hybrid and rewrote it with cwm for sd cm10.2. The cm10.2 updates but doesn't work when you reboot. When I turned back on, my nook gets stuck on infinite loop cyanogenmod logo instead of booting to stock . Clockworkmod shows that I have a backup but when I try it says "no files found." I have backups for original bn rom and a cm version on my pc. But since there is only 115 mb space left on my sd card after writing, I can't copy my 1+ GB back up files. I was searching on google and I came across how to update rom using adb sideloading and was trying that. That's where I get this error message. Is there any way for me get out of this mess and go back to cm? :crying::crying::crying:
Click to expand...
Click to collapse
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
See my response in my HD/HD+ Tips thread linked in my signature.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
toplist said:
I read your post and went through 15 pages to see if you wanted me to find anything specific. But I'm not sure what I should look for. I tried step 1 and step 2 from your post. When I tired to sideload app, I get "errors:closed" (attached image). I don't know what to do :crying:. My sdcard has CWM based recovery V6.0.3.2 for hybrid. When it is inserted, I boot to recovery. When I take off the sdcard, I get to cyanogenmod logo with infinite loop (attached image). Did I break my tablet? Is there any solution to fix this?
Click to expand...
Click to collapse
I wanted you to respond on my HD/HD+ Tips thread, that is why I posted the answer there. I don't want to clutter this thread with non ADB things. Continue this discussion on my thread.
It is not broke. Make the CWM SD as detailed in item 1a. Then use that to restore your stock backup.
Sent from my Nook HD+ running CM10.1 on emmc.
Ardent_V said:
ADB has all kinds of uses, but it's a pain to enable on Windows 7* with a Cyanogenmod Nook HD/HD+, especially with the spread out documentation. Not with this guide, however. (This is for emmc, no idea if it works with sdcard/hybrid installs)
Credit to Leapinlar for noticing the changed device ID.
EDIT: As jamus28 noted, you will also need the Google USB drivers. They come with the ADT.
1. Download usb_driver_r04-windows-B&N.zip here, courtesy of Leapinlar and B&N.
[Steps 2 to 10 removed for brevity.]
11. Open your adb file location in command prompt and type adb devices. If a random string of letters and numbers show up labeled device, it worked. You can now use adb over usb. (and wifi, after enabling network adb on your device)
*Probably similar for other versions of Windows
Click to expand...
Click to collapse
I recently installed the CM10.2 ROM on my Nook HD (I don't mind living dangerously!) To my surprise, I found that ADB worked out of the box, and the Nook showed up as MyNook in Windows Explorer and in Device Manager (under Portable Devices). However, after I installed the Eclipse+ADT bundle on my PC yesterday, ADB over USB stopped working, although I could still use ADB over wifi and could still open MyNook in Explorer.
So I thought I would try the instructions in the above post to repair ADB over USB. Everything seemed to work fine, there were no error messages, and ADB over USB is indeed working again. BUT, the MyNook Device Manager entry under Portable Devices has disappeared, to be replaced by an Android Composite ADB Interface entry under Android Phones, and the Nook no longer appears in Windows Explorer. In Devices and Printers it appears as a camera icon labelled "MTP" - strangely, as of course the Nook HD doesn't have a camera.
Does anyone have any suggestions for how I might get everything working again? Or would I be best to use System Restore to go back to how things were before?
My PC is running Windows 7 SP1 Home Premium.
UPDATE
=======
I have now solved this. I disconnected the Nook HD, disabled the Android Composite ADB Interface in Device Manager, and reconnected the Nook. Windows 7 installed the drivers, and the Portable Device entry reappeared in Device Manager, this time called "BN Nook HD" rather than "MyNook" (an improvement!). I then re-enabled the Android Composite ADB Interface, and everything is now working. The Nook is visible in Windows Explorer; ADB is working via USB; and the Nook's icon in Devices and Printers is now that of a portable media device - it's still labelled "MTP", but I can live with that.
Android_winusb.inf entry for HD+ running official CM11
FWIW, I just installed ADB on my Win 8.1 PC and found that the entry needed in android_winusb.inf for the HD+ running official CM11 is:
Code:
;Nook HD+
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0005&MI_01
Note the trailing &MI_01, my ADB interface will not come up without it.
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.
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
rboklewski said:
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
Click to expand...
Click to collapse
Perhaps the photos were somehow uploaded to your Google+ account?
A
scream4cheese said:
Perhaps the photos were somehow uploaded to your Google+ account?
Click to expand...
Click to collapse
They were to a point, but not like the last year
rboklewski said:
I can't believe I did it, must of accidentally deleted photo album. Stayed up for hours last night and all of this morning trying to find a way to recover the album. I have a bunch of my daughter's pics in that album and I really need them back.
I have a Nexus 4 with 4.4.2 loaded on it and the phone is not rooted. I have been trying to find a way to root the phone without wiping the data so I can try to use diskdigger to recover what I can. I don't know if there is a way with this version, but if there is and you know, please post. If you can show me a way and it is successful you will have some paypal money coming your way. Thanks in advance!
Click to expand...
Click to collapse
My first response would be to use disk digger like you said, but as much as rooting is a wonderful thing, I don't think it is needed in this case.
Disk digger is actually derived from a desktop app of the same name, that does the same thing with desktop and laptop hard drives.
Web page here
http://diskdigger.org/
If you connect your phone to your computer as external storage then you should be able to run the program on the computer but targeted at your phone, hence recovering your lost files.
Note: if this works then LOTS of files will be found, (including ones you never knew were even on your phone) so be prepared to search through them all.
I really hope this helps, I know what it is like to loose precious files, safe to say you should backup everything valuable from hereon
Let me know what happens either way and I will try and help if it does not work
Sent from my Nexus 4 using Tapatalk
captaindyson said:
My first response would be to use disk digger like you said, but as much as rooting is a wonderful thing, I don't think it is needed in this case.
Disk digger is actually derived from a desktop app of the same name, that does the same thing with desktop and laptop hard drives.
Web page here
http://diskdigger.org/
If you connect your phone to your computer as external storage then you should be able to run the program on the computer but targeted at your phone, hence recovering your lost files.
Note: if this works then LOTS of files will be found, (including ones you never knew were even on your phone) so be prepared to search through them all.
I really hope this helps, I know what it is like to loose precious files, safe to say you should backup everything valuable from hereon
Let me know what happens either way and I will try and help if it does not work
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
yeah, just tried the pc software for diskdigger, phone doesn't show in list. Has a advanced tab, but only lets you choose .vhd files it looks like. If only you could get the phone into a vhd.
OK, so the first question is if the phone is mounted correctly, does it show in 'my computer' and when double clicked on can you see files?
Next question is if you are using the .exe correctly, take a look at this tutorial: http://diskdigger.org/node/1025
I'm sorry if this sounds condescending, but I don't know your experience with computers
Sent from my Nexus 4 using Tapatalk
captaindyson said:
OK, so the first question is if the phone is mounted correctly, does it show in 'my computer' and when double clicked on can you see files?
Next question is if you are using the .exe correctly, take a look at this tutorial: http://diskdigger.org/node/1025
I'm sorry if this sounds condescending, but I don't know your experience with computers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
LOL...no problem. Been a systems admin for about 10 years. Anywho, yeah, this is the nexus 4 so it only has internal memory, no sd card. I can see the phone in my computer, but there is no drive letter assigned, apparently that changed in 4.3 up through 4.4.2, which I am on. So what that means is no mass storage option where drive letter gets assigned, so routine recovery software can't read it as an attached drive.
rboklewski said:
LOL...no problem. Been a systems admin for about 10 years. Anywho, yeah, this is the nexus 4 so it only has internal memory, no sd card. I can see the phone in my computer, but there is no drive letter assigned, apparently that changed in 4.3 up through 4.4.2, which I am on. So what that means is no mass storage option where drive letter gets assigned, so routine recovery software can't read it as an attached drive.
Click to expand...
Click to collapse
Hmmm, you should still be able to mount as external storage, I have done so before on that android version.
First thing then is if USB debugging is enabled, this will be in your settings under developer options and should not require root.
Then it is a question of whether your computers drivers are correct, android has a tendency of not liking to do drivers correctly, I used PDAnet to install the correct USB drivers (note these are different to the ADB drivers which you don't need)
Get back to me with the results of those 2 points
Sent from my Nexus 4 using Tapatalk
captaindyson said:
Hmmm, you should still be able to mount as external storage, I have done so before on that android version.
First thing then is if USB debugging is enabled, this will be in your settings under developer options and should not require root.
Then it is a question of whether your computers drivers are correct, android has a tendency of not liking to do drivers correctly, I used PDAnet to install the correct USB drivers (note these are different to the ADB drivers which you don't need)
Get back to me with the results of those 2 points
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yeah, I had developer options enabled and USB Debugging mode on, maybe it could be a driver issue. I tried PDAnet and that didn't seem to update the drivers for the phone. The device shows okay in device manager, no exclamation point, shows as Nexus 4 as well and the driver seems to be a Microsoft driver. Are you sure you had the same android version? Everywhere I look any version after 4.2.2 cannot be used as a mass storage device because of the MTP-PTP change in 4.3 and 4.4.
rboklewski said:
Yeah, I had developer options enabled and USB Debugging mode on, maybe it could be a driver issue. I tried PDAnet and that didn't seem to update the drivers for the phone. The device shows okay in device manager, no exclamation point, shows as Nexus 4 as well and the driver seems to be a Microsoft driver. Are you sure you had the same android version? Everywhere I look any version after 4.2.2 cannot be used as a mass storage device because of the MTP-PTP change in 4.3 and 4.4.
Click to expand...
Click to collapse
I am on 4.4.3 now, and have the phone connected fine right now, have you tried switching between MTP and PTP?
Note: I am on MTP and it is working.
I am sure there is a problem with something to do with connecting your nexus to the computer, as mine is doing so right now. If we can resolve that issue and access the internal storage then you should be able to then recover the files with disk digger.
My best guess would be a driver issue as android has never really played well when trying to set up drivers. But like you said the computer is recognising it correctly. I think perhaps testing the drivers connection my be the next step, use ADB with the command 'adb devices' (without quotes) to see the devices connected to the adb server. If nothing comes up then we may be able to start troubleshooting :good:
Perhaps ADB is the difference, i have it installed and sorted, do you?
If you have never used ADB before, here is a good place to get started and here is another mention of the drivers, perhaps another attempt may be worth a try, with a clean intall
Safe to say in my drivers list it is connected under android device > android composite ADB interface.
Actually yes, thinking about what i have just written i am confident it is ADB and drivers, you should not be connected with Microsoft drivers, they are the automatically installed ones and never work. Follow the guides above (and perhaps some googling) to get the proper drivers and ADB set up, once you think you have test it with the 'adb devises' command, once you get it returning a serial number for your phone then take a look in 'My Computer' again and see if the storage is visible.
nexus 4 only support MTP, not USB Mass Storage, so can't be mounted with a drive letter and can't be used with undelete software . If you know any working solution without root - please tell us, but test first yourself before writing please
P.S. you are on 4.4.3 ?
RolF2 said:
nexus 4 only support MTP, not USB Mass Storage, so can't be mounted with a drive letter and can't be used with undelete software . If you know any working solution without root - please tell us, but test first yourself before writing please
P.S. you are on 4.4.3 ?
Click to expand...
Click to collapse
My most sincere apologies, i was mistaking the mounted MTP device for the mounted drive, i now see what you mean.
In this case rooting is your only option, you need to run the file recovery natively.
I had hoped that this would not be necessary as unfortunately the rooting process will perform a lot of write operations so you must be prepared for some of your images to become corrupted or incomplete, (hence why i wanted to attempt other options) this is just the risk that you will have to face. How many will be damaged is difficult to say.
So use one of the many tool-kits or root manually, install the disk digger APK and you are good to go.
to root you will need to unlock phone bootloader and that will wipe all your device ...