I haven't rooted my nook yet, but I have run into a peculiar issue. I plugged it into my computer tonight after work, and instead of seeing it as a nook, I am getting 2 removable drives. When I click on either of the two removable drives, I am asked to insert a disk into the removable drive.
When I open the Adobe Digital Editions software (to put Google Books on my nook), it no longer sees the nook, either.
Any thoughts on why this would happen?
Win7 Pro x64
I have now done a factory reset, data clear, and still unable to see the nook properly. All I get is two removable disks, with no devices inserted, when I plug the nook into either of my computers.
Try inserting an SD card into your NC and see if one of the removable drives stops asking for a drive to be inserted.
I'm assuming the two drives are the internal NC storage and the SD card slot. That's how it shows up on my rooted one. Can't recall what it looked like before root. Next time I reset mine, I'll take a look and check in here.
By chance, do you have an Android Phone device in your Device Mangler?
no, I did not see it.
I was able to resolve the issue, though. I ran through AutoNooter, then did a full reset (after playing around with the rooted version, of course ). After that, it worked just fine. I think it had something to do with the way the VMWare player saw it the first time I had it connected. If I have VMWare running, when I plug the nook in, it shows up as a VMWare Virtual USB device, even though it's not connected to the guest.
Not a big deal, I was able to transfer files/movies/etc. to it earlier today, and that was what I was looking to do.
Related
Hello everyone, I have been using this forum for a while now, but havent really posted anything much as I have always found answers to any questions through searching the threads, however, I am unable to find a solution to a problem I have just recently encountered and was hoping someone out there may be able to shed some light on it.
I am using an unbranded handset running JPO which has been performing superbly until today, however, when I connect the phone via USB to my PC and select mass storage the computer does not seem to recognise the phone is plugged in. The strange thing is it worked perfectly before and the only changes I have made since was upgrading the micro SD card to a 16 gig one. I try unmounting the external card and even removing it completely to no avail. I have tried the phone on 3 PCs now, even my Linux PC does not recognise it.
I have rebooted the phone, tried connecting selecting Kies mode instead of mass storage, all to no avail. As soon as I connect the USB to the computer, the phone recognises the connection and asks what I want to do, I select mass storage, then I get the option to mount via the little green android, which turns orange stating it is connected, but the phone just does not show on the pc.
Any ideas would be most welcome, I don’t really want to have to format the internal memory but I think I may have to.
Many thanks in advance.
Additional:
I seem to remember on Eclair that I was able to unmount the internal sd card in the settings menu, however, with froyo, I only have the option to unmount the extrernal sd card. Would someone running JMO be good enough to check and see if they have the otion to unmount the internal sd?
Right, I seemed to have found the problem, so for anyone else who has a similar experience, it was the USB lead. SGS working as it should agian, phew..
I seem to be having an issue that I can't find a solution for. I have followed the directions in this thread (http://forum.xda-developers.com/showthread.php?t=942424) to the letter, but when I get to the point where I have to turn off the Nook, put the uSD card with the AN image on it into the Nook, and then plug the Nook into my computer, my Nook simply boots up normally, and is in USB connected mode when it starts up. It never boots into Android. It just boots into stock unrooted Nook UI.
However, it does do something strange. Whenever I try to boot from the AutoNooter uSD card, when I unlock the screen for the first time, it is in USB mode (with the screen saying "You may now safely transfer files to your NookColor..."), and it keeps dropping the connection sporadically. The "You may now safely transfer..." screen goes away for a split second, and then it comes back almost right away, making the noise it makes when you connect your Nook to a computer via USB. This only happens when I boot using the AutoNooter imaged uSD card by plugging in the USB cable.
Any suggestions or help would be appreciated.
Sounds like your Nook doesn't recognize your uSD card as bootable. If you have another uSD card handy, write the AutoNooter image to that one.
Otherwise, try unmounting and formatting the uSD on the Nook itself. Then make sure your Nook can access it using the built-in file browser in the Library app. If that's all good, power down your Nook and pop out the uSD card and re-write the AutoNooter image to the uSD. Hopefully, your Nook will boot off it this time.
fugitoid said:
Sounds like your Nook doesn't recognize your uSD card as bootable. If you have another uSD card handy, write the AutoNooter image to that one.
Otherwise, try unmounting and formatting the uSD on the Nook itself. Then make sure your Nook can access it using the built-in file browser in the Library app. If that's all good, power down your Nook and pop out the uSD card and re-write the AutoNooter image to the uSD. Hopefully, your Nook will boot off it this time.
Click to expand...
Click to collapse
I've tried another older 1gb uSD card I had lying around, and that one didn't work either. I bought another 8gb class 4 card that I will try.
I did format the 16gb card I was using from the Nook, and put some pictures and mp3s on it to test to make sure it was not a bad card. The Nook was able to see those, but like you said, it doesn't seem like it recognizes the uSD with the AutoNooter image as bootable.
Rattor said:
I've tried another older 1gb uSD card I had lying around, and that one didn't work either. I bought another 8gb class 4 card that I will try.
I did format the 16gb card I was using from the Nook, and put some pictures and mp3s on it to test to make sure it was not a bad card. The Nook was able to see those, but like you said, it doesn't seem like it recognizes the uSD with the AutoNooter image as bootable.
Click to expand...
Click to collapse
That is weird. Have you tried any other bootable images? If not, try the Monster RootPack. That should boot you into Clockwork Recovery but don't do anything in there. If you can't even boot off of that image, I would have to say that there is something about how you are writing the images to the uSD that is the problem.
Rattor said:
However, it does do something strange. Whenever I try to boot from the AutoNooter uSD card, when I unlock the screen for the first time, it is in USB mode (with the screen saying "You may now safely transfer files to your NookColor..."), and it keeps dropping the connection sporadically. The "You may now safely transfer..." screen goes away for a split second, and then it comes back almost right away, making the noise it makes when you connect your Nook to a computer via USB. This only happens when I boot using the AutoNooter imaged uSD card by plugging in the USB cable.
Click to expand...
Click to collapse
I have a bad NC USB cable that causes the appearing/disappearing act within Windows. Just for giggles, when booting w/o the uSD card installed, wait until it gets to the home screen. Connect to your computer. If the mounts properly, carefully flex the USB cable connector at the NC end. If you start getting weirdness, then you either have a bad cable or the NC's USB connector has gone a bit wonky.
Finally got it working. Apparently, creating the image using the built-in SD card reader in my laptop was messing something up. I used an external one that my wife has lying around, and it worked the first time.
Thanks for all the help I got in this thread
I tried AN 2 with 1.0.1 and got nothing.
(wouldnt boot at all when I plugged into USB, just stayed off)
I tried AN 3 with 1.1 and this also failed. It did boot on its own when I connected it to PC with USB, but simply went to standard B&N interface, no Android.
I noticed elsewhere someone mentioned having problems with Patriot cards - I have a 4gb class 4 that detects OK (pc & nook) and appears to write fine, but no dice. As a last resort, I did the 8x interrupt boot to reset the Nook and carefully followed the AN instructions, wiping the card yet again. Let it sit...and B&N interface boots.
Ideas?
Edit: I didn't mention it, but I am using an external, stand-alone USB SD card reader, so that shouldnt be an issue
This is kind of strange. I have a 32gb Touchpad and Win 7 32bit computer. Upon first use of the Touchpad, I followed the guide posted in the tweaks and tips section right away.
I updated to 3.0.2, turned off/down logging settings, installed Preware, installed all of the recommended patches, installed Uberkernal and Govnah, and OC'd to 1.5mhz.
I then went to load some media (songs, videos, ebooks etc.) onto the touchpad by connecting the usb cable to the Win 7 machine. The computer makes the found new hardware sound and the touchpad then asks if you want to put it into USB storage mode (which I did). The computer should then pop up with the window of the Touchpad drive and assign it a drive letter (just like any other usb mass storage device), but it doesn't. when I go into windows explorer, it shows a new drive letter has been added, but when I click on it to presumably see the contents of the Touchpad's drive, the computer does nothing. In fact, it even caused Windows Explorer to stop responding.
I almost positive this is a Novacom driver issue, but that doesn't make sence due to the fact that those drivers should (and were) loaded when installing Preware.
I am not sure how to resolve this. If anyone has any suggestions, they would be much appreciated. Regards, Dcartes-
I'm have a similar drive issue but it consist of the touchpad (I think), not recognizing when I disconnect the drive via the computer. This always results in that error message stating that I didn't safely remove it after I physically unplug it.
crbeezy said:
I'm have a similar drive issue but it consist of the touchpad (I think), not recognizing when I disconnect the drive via the computer. This always results in that error message stating that I didn't safely remove it after I physically unplug it.
Click to expand...
Click to collapse
I'm not sure on the OP's question but as for the quoted response you need to go into my computer and right click the touchpads drive letter and then choose eject..
simply unplugging or using "safely remove hardware"will result in the error you are seeing
And if I connect TP via USB and then disconnect it w/o PC "eject" thing, then next time PC wont recognized TP in USB mode. And I have to restart TP to make it "recognizable" again
I go through all the normal, safe, and necessary steps but no matter what the tp always stays connected. I've even went so far as to shut my computer down completely with my tp still connected and it still stays in disk drive mode.
crbeezy said:
I go through all the normal, safe, and necessary steps but no matter what the tp always stays connected. I've even went so far as to shut my computer down completely with my tp still connected and it still stays in disk drive mode.
Click to expand...
Click to collapse
I get this same issue.
dcartes said:
This is kind of strange. I have a 32gb Touchpad and Win 7 32bit computer. Upon first use of the Touchpad, I followed the guide posted in the tweaks and tips section right away.
I updated to 3.0.2, turned off/down logging settings, installed Preware, installed all of the recommended patches, installed Uberkernal and Govnah, and OC'd to 1.5mhz.
I then went to load some media (songs, videos, ebooks etc.) onto the touchpad by connecting the usb cable to the Win 7 machine. The computer makes the found new hardware sound and the touchpad then asks if you want to put it into USB storage mode (which I did). The computer should then pop up with the window of the Touchpad drive and assign it a drive letter (just like any other usb mass storage device), but it doesn't. when I go into windows explorer, it shows a new drive letter has been added, but when I click on it to presumably see the contents of the Touchpad's drive, the computer does nothing. In fact, it even caused Windows Explorer to stop responding.
I almost positive this is a Novacom driver issue, but that doesn't make sence due to the fact that those drivers should (and were) loaded when installing Preware.
I am not sure how to resolve this. If anyone has any suggestions, they would be much appreciated. Regards, Dcartes-
Click to expand...
Click to collapse
I've had to same problem--finally tracked it down to the original usb cable. Touchpad would still charge but was not recognized by the computer. Changed to the cable that came with my Samsung phone and everything works like a charm.
Ouch message when ejecting
FishDoc said:
I've had to same problem--finally tracked it down to the original usb cable. Touchpad would still charge but was not recognized by the computer. Changed to the cable that came with my Samsung phone and everything works like a charm.
Click to expand...
Click to collapse
Thanks for the tip about the cable. I had the "Ouch That Hurt" message the other day after moving some pictures from my PC to the Touchpad and then ejecting the Touchpad. Ejection did not work. After the ejection process, the TP was no longer an option with either of the normal methods for ejection. So, my PC thought the TP had been ejected. But the TP did not think it had been. So, no option left but to turn off my PC or unplug the USB cable from the Touchpad to the PC.
However, I have noticed an issue with charging the Touchpad lately where I have to wiggle the cable where it connects to the Touchpad to get it to charge properly. Could be that this same flaky connection gave me a problem when trying to eject the TP after transferring the picture files? Though the pictures DID transfer properly. Will try a different cable next time. Hope I don't get a "wrong cable" message when doing that. Hate it when the TP does not eject properly as I fear I may be introducing file errors when that happens.
Galtha58 said:
Thanks for the tip about the cable. I had the "Ouch That Hurt" message the other day after moving some pictures from my PC to the Touchpad and then ejecting the Touchpad. Ejection did not work. After the ejection process, the TP was no longer an option with either of the normal methods for ejection. So, my PC thought the TP had been ejected. But the TP did not think it had been. So, no option left but to turn off my PC or unplug the USB cable from the Touchpad to the PC.
However, I have noticed an issue with charging the Touchpad lately where I have to wiggle the cable where it connects to the Touchpad to get it to charge properly. Could be that this same flaky connection gave me a problem when trying to eject the TP after transferring the picture files? Though the pictures DID transfer properly. Will try a different cable next time. Hope I don't get a "wrong cable" message when doing that. Hate it when the TP does not eject properly as I fear I may be introducing file errors when that happens.
Click to expand...
Click to collapse
the only way to eject is from MyComputer > right click HPTP > eject.. or it will complain..not from the tray icon
ppl will bet that your prob is cable..
i went to national electronics store, they had phone section w/ many cables and phones plugged in..
i tried their cable to my HPTP and my cable to their phones...
cable was for sure bad.. they wanted 20$ for a 3' cable.. too much..
amzon wanted 4$ for set of 2 @ 10'..+ free s/h..
guess where i bought from..
For some reason, out of nowhere, my phone doesn't seem to want to work completely with my PC. I've never had any issues before, worked fine yesterday. But today, when I plug it in, and select mass storage, only the Internal Storage gets recognized and comes up for me to open the folders, but its not recognizing or showing my Removable Storage, aka my SD Card. I have restarted my phone and my PC. Unplugged several times and tried again, but no go. My sd card reads just fine when my phone is unplugged, all my music and everything I have my SD card shows up on my phone and I am able to access it through my phone just fine and move files between the two. But my PC just wont recognize it and wont show up in my computer. Any thought on why this is happening and what I can do to fix it ?
I had that problem while testing with windows 8. Try plugging into another USB port on the PC.
Just had this issue a couple days ago, I think I took out the battery of the phone and took the sd card out and put both back in
Haxcid said:
I had that problem while testing with windows 8. Try plugging into another USB port on the PC.
Click to expand...
Click to collapse
That was one of the first things I did, cause the first USB port I plugged into wouldn't recognize the phone at all, which I've had that problem quite a few times recently, but if I switch USB ports it starts to work fine, but this is the first time that it only brought up the internal storage and not external (SDcard) storage. It's still not working....
Gel Pen6 said:
Just had this issue a couple days ago, I think I took out the battery of the phone and took the sd card out and put both back in
Click to expand...
Click to collapse
I tried that as well, someone on another forum suggested that, and it didn't help. I don't get what the problem is. You would think it would be an issue with the SDcard, but as I said in my OG post, when the phone isn't plugged in through USB, the phone itself reads the SD Card fine, I am able to access stuff from it, move files to and from, etc etc. This is pissin me the hell off tho, that's for sure !
Any other Suggestions/Ideas ?
EDIT - I forgot to also say, I put my SDcard in another phone and plugged in it via USB, and it recognized it just fine. And so then I thought, Great, its my phone itself, either the USB cable, or the SDcard slot on the phone, so not only did i try a new USB cable, but I also put a different SDcard in my phone, and it worked fine, so then i did the same thing, except with my USB, and it still worked fine, but as soon as I put my SDcard back in, it wouldn't work. I am like outta ideas here, I am about to just send my phone in, I have insurance, and since they are about to discontinue this phone, they will have to give me a different phone of equal or better quality/specs, So this might work out in my favor. I can prolly at least trade it in and get a discount off the phone i really want, which is either a LG Spectrum or a Samsung Galaxy Nexus, or possibly an HTC Rezound. I really want an HTC One X but no go for Verizon and the one i really really want, the Samsung Galaxy S III isn't out yet, and from what I've been reading in the news, it might not come out on time, Apple is seeking an injunction, preventing Samsung from Selling the Galaxy S III in the US until the Patent issues are resolved in court or through settlement. Which I hope to god that wont happen. Germany already agreed to ban the sell of Xbox360s for the time being over there, so its something that definitely could happen over here.
I don't know if it helps or has anything to do with your situation, but have you checked to make sure the phone is connecting as mass storage, and not charge only or internet connection mode?
Joker420 said:
I don't know if it helps or has anything to do with your situation, but have you checked to make sure the phone is connecting as mass storage, and not charge only or internet connection mode?
Click to expand...
Click to collapse
Mass storage is the default, or the always ask. You have to actually manually go in and set charge mode or internet mode each time you want to use them.
Did you switch cables? I had the same issue when I used a generic cable instead of the VZN supplied one. Some of the imported pacific rim cables only charge (2pins instead of 4 pin usb internals) Also use the usb headers on the motherboard (rear of pc) not a hub or front ports.
here is what I did...
I used root explorer to execute the driver file on my phone. When I plugged i into my computer it ran the bootstrap which installed the drivers on my computer. It worked and linked up just fine. I then used the .tot files and got my phone to do the otas.