Cannot get ADB. Please help

[superflysocal]

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?

 

[Chi Ahrens]

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

 

[leapinlar]

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?

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

 

[superflysocal]

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)

 

[leapinlar]

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)

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

 

[superflysocal]

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

 

[someone0]

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.

 

[superflysocal]

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.

 

[BigDaveFromJers]

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.

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.

 

[someone0]

There are people that report a success ADB driver install on win7 64bits via my method. Check the tips thread.

 

[superflysocal]

someone0,

just curious, what firmware are you on? 2.0.4? Are you having any sd card write issues?

 

[superflysocal]

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.

 

[leapinlar]

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.

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.

 

[superflysocal]

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.

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.

 

[someone0]

No, I'm on 2.0.0