I've been working with leapinlar in this thread
http://forum.xda-developers.com/showthread.php?t=1994129
to get my HD+ ready for sideloading and root. One thing to know up front is that I'm running with HD+ OS 2.0.2. I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
I have other BN drivers installed for my other Nooks (a Touch and Tablet). These have the same Vendor ID (2080) but different Product IDs. I don't think I should have to uninstall them, doesn't seem like that should be necessary.
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
My apologies in advance, but I was hoping posting this in its own thread would maybe provide better visibility.
Per the NEW announcement,
http://forum.xda-developers.com/showthread.php?p=34819554#post34819554
I redeclare this thread open...
tonyp22 said:
I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
Click to expand...
Click to collapse
I'm having the same problem. Were you able to get it working?
I think it has something to do with the OS being 64 bit and not being able to install the driver but it recognized it as an Android Composite Something once before I tried installing the driver on it and restarting but now it won't recognize it if I enable the developer option. It just keeps repeating the device disconected sound over and over and over OMG THE SOUND!
please let me know if you were able to fix it and how.
BTW, has ANYONE been able to get adb to work on win7 x64?
I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.
lkmiller said:
I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.
Click to expand...
Click to collapse
Didn't work for me.
r1c47 said:
I'm having the same problem. Were you able to get it working?
BTW, has ANYONE been able to get adb to work on win7 x64?
Click to expand...
Click to collapse
I've got it working with win7 64-bit and so does my husband.
Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.
Thanks all for these suggestions. I had tried using various combinations of disbling / uninstalling but it never worked. I went to my Win XP Pro laptop and got it all hooked up in seconds that way.
r1c47 said:
Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.
Click to expand...
Click to collapse
This worked great for me as well, thanks so much! I'm struggling to figure out how to use ADB to install an APK that I extracted from my phone. Aptoide worked for every app I wanted that I hadn't paid for in google play. But I have three apps I'd like to install that Aptoide does not have because they are paid apps. I'm stuck where I am trying to use ADB. All of the APK installers did not recognize the files if I just moved them to my nook from the computer. These are the files on my SD card. View attachment 4649607
The highlighted ones installed but the red circled one was a paid app and it did not even get recognized by the installer. I've gotten as far as getting my nook to be recognized in command prompt. I'm attempting to use command prompt to install the .apk but I think it may be a problem with the .apk itself. Do you know how to go about that? This is where I get stuck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My other struggle is that my nook also does not allow me to send anything to it. It connects. It's recognized but it will not allow files to go onto it.
I'm not sure what to do now. It doesn't let me type anything at this point and my nook doesn't even respond to the fact that I'm trying to send something to it. Please let me know if I'm doing it all wrong. I realize how green I am. I know this was forever ago for you so if you can't remember it's no biggie.
Related
Hey Guys,
Firstly just got my captivate a couple of days ago and i am still struggling to get to install drivers and have my pc detect the phone. I am totally new to android (coming from iphone)... there might be some obvious things that I might be missing here...
Here is what has happened so far
I have pretty much tried all the drivers on the web and I am still unable to see the drives on my PC. Driod explorer is unable to detect the phone. Device manager is showing a USB device by the name "SAMSUNG Android USB Composite Device".
In the phone i have enabled usb debugging. Once the cable gets connected, I also open notification and enable USB storage.
I am still not able to see the drive or have any applications in my pc detect the phone. What am i missing?
A simple usb device installation has never given me so much trouble. Starting to get frustrated.
Appreciate any pointers in resolving this issue.
Thanks
So you chose "Mass Storage" in settings? And once you connected, pull down the drop down men you, press USB, and then press the "Mount" button?
Mine worked just fine on WinXP and Win7 64 bit once I enabled mass storage and then confirm "Mount" each time you connect.
yes I did choose mass storage option & mount it.
I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
s1lverdream said:
I am able to see the usb drives in windows xp. But cant resolve the issues with win 7 64bit. I am using the following drivers
SGH-i897_Captivate_USB_Drivers_5_02_0_2.zip
Click to expand...
Click to collapse
I know a few people who had connections problems too. They were able to fix it using this driver: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Some others were also able to do it using the Samsung Kies program.
Just one thing, though. You said in your post you're selecting 'Mass Storage'. Did you try selecting 'Kies' (this is even without installing the Kies program)? Try doing that. Also, try having USB debugging off when you perform the aforementioned test.
All I can get with debugging on or off and mass storage is this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no matter what drivers i use. I cant mount it on Windows 7 but I can on vista
My desktop is running Windows 7 64-bit, and I couldn't get it to recognize my phone for anything, even with the drivers from Samsung. The computer doesn't even pick up the phone as a device, much less one it recognizes. I had to use my netbook (Windows 7 32-bit/Linux) to do all my phone-related hacking stuff.
I'm using Win 7 64-bit and here's what I did after reading some suggested steps in another thread:
Install Samsung Kies first, before ever connecting the phone.
Run the program, then connect the phone to a USB port on the motherboard. Not one on the front of the case.
Windows SHOULD start installing the drivers.
I think I selected the Kies option on the phone the first time. Three or four different drivers were installed I believe. When I connected the phone again and selected Mass Storage, two or three different drivers were installed by Windows.
Does this mean I have proper drivers:?
Hi guys,
I just bought a new hp computer with win 7 64 bit os. I am able to use microsoft synctoy to syn itunes to my cappy. Does this mean that I have the proper usb drivers installed on my computer for my phone. I was thinking about rooting my phone and wanted to have the correct drivers installed.
Thanks, I consider myself a newby to the forum and to rooting, so any help would be appreciated.
drewfs7270
Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.
The newest Kies will install a driver pack when you download it now.
MAkE SURE YOU REMOVE ANY SAMSUNG DRIVERS THAT ARE CURRENTLY INSTALLED
1.) download the newest Kies http://www.samsungapps.com/about/onPc.as?COUNTRY_CODE=CAN&LANGUAGE_CODE=ENG
2.) Install it. While it's installing it will install a driver pack.
3.) Plug your phone in.
This works for X64. I just used it on my own pc last week.
jack_slapped said:
Has any headway been made on this as I just got windows 7 64 bit, and am having a similar problem. Tried various drivers and whatnot but still cant seem to get the usb to mount like a flash drive. It is being recognized and can receive commands like reboot into download mode from AOI toolbox, but no mounting.. Kinda driving me up the wall bc Ive been stuck on the same rom for a few weeks now and Im itching to get back to flashing all the fresh new cm7 stuff out and just in general new roms.
Click to expand...
Click to collapse
Turn on USB Debugging.
Lol I know how to enable USB debugging man. What I'm saying is windows wont allow it to mount for some strange reason. Going to try the kies driver mentioned earlier. Maybe that will work.
So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.
jack_slapped said:
So I tried the kies drivers, and Im getting the same problem. The drivers will install and it will even trick me by showing the removable letters for my storage, but then after a second or so they disappear. When looked at under device manager they are just shown as unknown device. I just wanna backup my data like I used too.
Click to expand...
Click to collapse
I definitely don't want to insult anyone's intelligence here (which usually means I am going to). i assume we've tried restarting the computer again.....a couple of times.......and if that doesn't work, then manually uninstalling all the drivers which have been installed so far and then starting over using just kies?
Yea, all those mentioned have been tried.
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't know if this means anything, but windows can recognize my device. Sorta. I tried flashing to stock in hopes that would fix the problem, but it didn't. Isn't it strange that I can flash my phone but not be able to mount my storage??
Sent from my SAMSUNG-SGH-I897 using XDA App
okay...
So i was able to connect to my Win 7 64 bit computer for a little while ... had to in order to update to Mini Keis 2.2 (ran into problems there but fixed it <if you have questions about it PM me>)
But now that i am in 2.2 i am not able to connect. I get an error saying drivers could not be installed. I have uninstalled the original drivers and installed the ones from AT&T and also tried the ones from Samsung... still same problem. Does anyone one have an idea as to what i can do to solve this problem.
Thanks to any one who can help
I've had luck by doing the following:
Had my phone plugged in - it went fubar - computer didn't recognize the phone.
Re-installed USB drivers (ones Design Gears posted and the ones linked in the Q&A sticky btw) over the top of the existing drivers with the phone plugged in - USB De-Bugging on.
Rebooted PC - winblows found the phone and everything was peachy. Windows 7 64 is definitely nice - but still has issues with detecting drivers and USB devices sometimes. Its still Windows after all
If it works on another PC than you know its a software issue with windows.
If your still getting the same error on another PC - then its possible that your internal card might be fubar.
Well I have tried EVERYTHING. Multiple drivers, uninstalling, reinstalling, rebooting, usb debugging on/off, flashed to stock....Nothing. Windows 7 64bit. I hate hate hate you and hope you die of viral infection.
For some reason I cannot get ADB to work with my NC. I cleaned out ADB and reinstalled with all updates except for the Galaxy Tab add ons. I used the driver that is available all over the forum and got the proper device id in device manager. When I try to check devices I just get nothing connected. Does anyone have any ideas? Any help is appreciated. Device manager also still has the USB as mass storage also.
*Running Win 7 x64
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall the Android Composite ADB Interface driver
Download the updated adb drivers from here
http://forum.xda-developers.com/showthread.php?t=882751
and reinstall them. A reboot of your pc should show your device.
So nooks good just no adb via PC? Win7 64bit puts it c:/program files (x84)/android/android-sdk-windows/platform-tools
If not just type adb.exe in the search box above winows start
sent from a Nook Color using xda-app
thanks for the responses.
camwinnn said:
So nooks good just no adb via PC? Win7 64bit puts it c:/program files (x84)/android/android-sdk-windows/platform-tools
If not just type adb.exe in the search box above winows start
Click to expand...
Click to collapse
ADB is not the issue, it must be some kind of driver problem. the SDK is in my path, it will run no matter what directory im in. It works fine on the vibrant.
ewong90 said:
Uninstall the Android Composite ADB Interface driver
Download the updated adb drivers from here
http://forum.xda-developers.com/showthread.php?t=882751
and reinstall them. A reboot of your pc should show your device.
Click to expand...
Click to collapse
thats what I used orginally to get to this point. plus the 1.01 image. I tried it again just to be sure. The composite device shows when plugged in but so does the mass storage, does that matter? should the storage still mount?
Here is what I have for drivers.
uninstall all the nook mass storage device drivers
ewong90 said:
uninstall all the nook mass storage device drivers
Click to expand...
Click to collapse
Here is what I did, (just to be clear)
Plugged in Rooted Nook.
Uninstalled USB Mass storage
right clicked "nook" and hit update driver
selected driver from downloaded Win7 post
clicked install unsigned driver
adb composite device showed up
reboot
plugged nook back in, now both USB storage and Adb composite device show up
Be lazy, get adb wireless from the market. I didn't even bother setting up my PC
sent from a Nook Color using xda-app
There's a thread somewhere around here with a solution that worked for me, it involved adding 0x2080 to the adb_USB.initial file in /user/yourname/.android.
Edit: Oh yeah, adbwireless is awesome so give that a try if you can't get USB to work.
+1 for AdbWireless!!!
Its free and you can get it from the market.
(I finally gave up after days of trying to get the usb drivers figured out on my computer.)
camwinnn said:
Be lazy, get adb wireless from the market. I didn't even bother setting up my PC
sent from a Nook Color using xda-app
Click to expand...
Click to collapse
Didnt even think of that. I use it for my Vibrant and love it. thanks.
My wireless works great...but I still need the usb connection to modify wireless settings to allow connection to adhoc network (mywi on iPhone 4).
I've tried everything and am still having a problem.
I am running a Windows Vista machine. When I attempt to install the USB drivers, it runs through the steps, but at the end, it says:
"Windows found driver software for your device but encountered an error while attempting to install it.
Android Composite ADB Interface
The data is invalid.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I've cleared it all and still have the same problem.
I ran it on an XP machine, and was able to install the drivers, however, the nook still does not show up in the list of devices.
Any ideas?
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!
Hi everyone,
So, I've got a windows 7 64 bit machine, and a 32 GB HP touchpad. A couple of years back, I installed JCSullins' Kitkat CM ROM... I think that's what it's called, anyway, it's been a while..
From what I remember, the install went off without a hitch - I got the novacom drivers, and then I ran the TP Toolbox which made the process quite easy.
Now I'm interested in tinkering with the touchpad more... possibly trying out a new ROM, or something like that.. but the problem is that I can't get the TP Toolbox to even start. When I run the batch file, I don't receive any error messages. The USB cable I'm using (which came with my old Samsung Galaxy S3) seems to be fine - I can use the TouchPad in windows explorer as an MTP device without any issues. Also, I don't think it's an issue with the novacom drivers, they seem to be working fine.
In addition to that, I can't get the storage to mount as a USB mass storage device... when I try to do this, I get an 'Unknown Device' showing up in Device Manager... I tried installing the generic USB Mass Storage driver to no avail. I also tried booting the device into TWRP and using the mount option in there but that didn't do anything that I could discern (mind you I wasn't looking too hard, I tried this before the other stuff I've already talked about, so it might be worth another shot I suppose).
And I do have developer options enabled, does this matter..? I can't remember whether I turned this on myself after installing CM Kitkat or if it somehow came already enabled (not sure if this is even a thing).
Thanks so much!
-Tim
HP TOUCHPAD Novacom Repair Android
[email protected] said:
Hi everyone,
So, I've got a windows 7 64 bit machine, and a 32 GB HP touchpad. A couple of years back, I installed JCSullins' Kitkat CM ROM... I think that's what it's called, anyway, it's been a while..
From what I remember, the install went off without a hitch - I got the novacom drivers, and then I ran the TP Toolbox which made the process quite easy.
Now I'm interested in tinkering with the touchpad more... possibly trying out a new ROM, or something like that.. but the problem is that I can't get the TP Toolbox to even start. When I run the batch file, I don't receive any error messages. The USB cable I'm using (which came with my old Samsung Galaxy S3) seems to be fine - I can use the TouchPad in windows explorer as an MTP device without any issues. Also, I don't think it's an issue with the novacom drivers, they seem to be working fine.
In addition to that, I can't get the storage to mount as a USB mass storage device... when I try to do this, I get an 'Unknown Device' showing up in Device Manager... I tried installing the generic USB Mass Storage driver to no avail. I also tried booting the device into TWRP and using the mount option in there but that didn't do anything that I could discern (mind you I wasn't looking too hard, I tried this before the other stuff I've already talked about, so it might be worth another shot I suppose).
And I do have developer options enabled, does this matter..? I can't remember whether I turned this on myself after installing CM Kitkat or if it somehow came already enabled (not sure if this is even a thing).
Thanks so much!
-Tim
Click to expand...
Click to collapse
Read this guide and download the ISO, it will fix or get the Tablet all clean and ready to go:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
When ready then follow this guide to flash any ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
HP_TOUCHPAD said:
Read this guide and download the ISO, it will fix or get the Tablet all clean and ready to go:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
When ready then follow this guide to flash any ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
Click to expand...
Click to collapse
Thanks very much for the helpful reply!
So, if I'm understanding this correctly.. Windows 7 has been updated since I last used the TP Toolbox, and the novacom drivers no longer function properly?
Does this mean that I won't be able to mount the Touchpad as a USB Mass Storage device? From looking at the top posts in that thread you linked me to, I see only an MTP option available for file transfer...
Also, the thing you posted seems to be a workaround for novacom drivers that don't function properly?
I tried what I was talking about in my initial post, mounting the device in TWRP, and this did work, though I was only able to see the recovery partition (which I guess is all that TWRP will load, makes sense in retrospect..). I was able to do this by installing the novacom driver when windows asked me to provide a driver after seeing the device booted into TWRP.
But that says to me that it isn't a driver problem, I think..? Thus that workaround seems unnecessary (sorry, not trying to be rude, I do appreciate the help regardless). Also the novacom driver does load up properly when I boot the device into the WebOS recovery mode.
I really would like to be able to have the device mount as UMS in Windows 7, if possible..
Edit: Also, forgot to mention that when I do try to load the TP toolbox, it does seem at some point to show the HP logo for some reason, which I think it's supposed to as it loads the toolbox..at least this happens when I try to run the batch file a second time after it fails to do anything the first time (not sure if this means anything at all..).
Thank you again!
[email protected] said:
Thanks very much for the helpful reply!
So, if I'm understanding this correctly.. Windows 7 has been updated since I last used the TP Toolbox, and the novacom drivers no longer function properly?
The novacom driver works even in Windows 10, if the user know how to install it and use it properly.
Does this mean that I won't be able to mount the Touchpad as a USB Mass Storage device? From looking at the top posts in that thread you linked me to, I see only an MTP option available for file transfer...
The Tablet USB mass storage device can only be mounted ( and use) by booting into TWRP recovery or Android, not the USB symbol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you see the instructions and Images? Even the Toolbox can be loaded.
Also, the thing you posted seems to be a workaround for novacom drivers that don't function properly?
Is a Linux boot disk with built in Novacom drivers, that will boot on any PC and allows to repair, load the Toolbox and do everything need it.
I tried what I was talking about in my initial post, mounting the device in TWRP, and this did work, though I was only able to see the recovery partition (which I guess is all that TWRP will load, makes sense in retrospect..). I was able to do this by installing the novacom driver when windows asked me to provide a driver after seeing the device booted into TWRP.
The novacom driver is only use to load uImages into memory, troubleshoot, it does not offer USB transfer.
But that says to me that it isn't a driver problem, I think..? Thus that workaround seems unnecessary (sorry, not trying to be rude, I do appreciate the help regardless). Also the novacom driver does load up properly when I boot the device into the WebOS recovery mode.
If the user does not know how to load uImages into the Tablet, it does not matter if the novacom are working properly or not.
That is the reason of the Linux bootable CD, make it easier for those that have issues and are not technically incline.
I really would like to be able to have the device mount as UMS in Windows 7, if possible..
Edit: Also, forgot to mention that when I do try to load the TP toolbox, it does seem at some point to show the HP logo for some reason, which I think it's supposed to as it loads the toolbox..at least this happens when I try to run the batch file a second time after it fails to do anything the first time (not sure if this means anything at all..).
Thank you again!
Click to expand...
Click to collapse
The HP Logo will show before the Toolbox gets loaded into memory, then the print screen of all commands will show and finally the Toolbox loads.
Is impossible to provide technical support for issues relating to the novacom drivers on any PC with all the operating systems options available and the different configuration.
The bootable CD is available, just click and load anything to the touchpad, follow all the directions, read it all.
If the user try to take shortcuts, it will be a long way to accomplish nothing.
Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
CyanFrank said:
Hello.
I want to transfer files from Windows to Pixel 7 via USB but unfortunately I can't. When I set MTP/PTP on my phone it start disconnecting and connecting endlessly (I hear the sound from Windows).
There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
I have USB-C male to male cable only. I don't have USB-A to USB-C cable so I can't test it. And I don't want to buy any new cables just to see the issue is still present.
Tested the USB-C port in my laptop to check if it doesn't support file transfer - it worked on another cable with my old phone.
Tested the USB-C port in Pixel - I managed to transfer files from old phone to Pixel via USB cable so it's working as well.
Same effect with cable added to phone and the bought one.
Tried to manually remove & install Google USB drivers, ADB etc. - only ADB seems working.
Any tips?
Click to expand...
Click to collapse
Airdroid. No need for a cable.
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
If the MTP makes it stutter it could be a problem with MTP or simply that MTP does more traffic and is uncovering lower level problems.
CyanFrank said:
...There are two devices in Devices Manager that seems to be associated with Pixel: Android Composite ADB Interface (listed as Android Device, not LeMobile) and so-called "external Bluetooth device" (deleted it many times, it appears automatically when phone is plugged). However Pixel is listed as Unknown device in "Devices and Printers".
Click to expand...
Click to collapse
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager? If not, replace what's listed under Android with Google's USB driver while still in Fastboot Mode, then reboot the phone. If Windows USB drivers are complete and the cable is good, you should only need to enable File transfer under Settings/Connected devices/USB to manage files between Windows and Android.
Click to expand...
Click to collapse
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Renate said:
When you put the USB mode to "No data transfer" does it still disconnect on you?
(You still should have the ADB working. Try adb shell and a bunch of ls -l)
Click to expand...
Click to collapse
No, phone is charging and debugging is enabled so that I see two notifications.
Tried the first command and phone started disconnecting just like with MTP enabled. ADB had stopped working.
manjaroid said:
When you're connected to Windows over the USB cable and the phone is in Fastboot Mode, is the Android Bootloader Interface driver listed in Device Manager?
Click to expand...
Click to collapse
It used to, but apparently I messed up with drivers while trying to solve the issue, so it's not working right now.
hammered58 said:
You could also check when your phone is connected to the pc,, under windows update, advanced option, view optional updates updates,, to see if there are any drivers it wants to install
Click to expand...
Click to collapse
Yeah I noticed LeMobile drivers are available to download. There is Android Composite ADB device listed as "LeMobile" but ADB still not fixed.
And it seems like I'm back to sqaure one because there's the very first issue I had: after choosing MTP on my phone all options become gray and it returns back to "only charging" after few seconds. Sometimes it even starts disconnecting/connecting.
Yeah it seems something is particularly wrong with my home PC because MTP works flawlessly with my work PC. Didn't have to install any drivers etc.
Do you have the latest windows platform tools installed?
Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Tulsadiver said:
Do you have the latest windows platform tools installed?
Click to expand...
Click to collapse
Yes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bobby janow said:
That's a good thought but I'll bet it's a Windows driver. Happened to me some years ago and I had to manually install an .inf in the windows directory. So long ago but maybe something like wmf.inf not sure. I'll try to root around (no pun) see if I can find it again.
Click to expand...
Click to collapse
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
CyanFrank said:
Yes.View attachment 5774787
Well if you mean wpdmtp.inf I tried to install it but not worked.
I'll just try clean installing Windows when I get a time.
Click to expand...
Click to collapse
That could be the one. If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one. I searched and there are a bunch of "solutions" out there and I hope you find the correct one before you have to reinstall the whole darn OS. I'll keep looking though. I was so frustrated by it I wanted to throw the laptop out the windows. lol. I still think it's one pesky driver.
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick. Sucks to completely reinstall Windows just to get MTP functionality.
Click to expand...
Click to collapse
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall. I'd fight this one tooth and nail until I figured it out. Damn drivers.
Click to expand...
Click to collapse
I mean I probably would do the same but if OP is already at the point of reinstalling Windows, I figured I would provide some less annoying options. Virtual machines have saved me immense amounts of frustration over the years and Player is phenomenal for something free of charge.
bobby janow said:
If I recall correctly, I had to uninstall the driver that had the exclamation mark in device manager and then find the .inf file in win directory, right click it and install. But this was literally 5 years ago or close to it so perhaps it's dated. But that could be the one.
Click to expand...
Click to collapse
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
EtherealRemnant said:
I would grab VMWare Player and install Windows there honestly rather than reinstall Windows. Or grab a Linux distro ISO like Mint that comes with MTP drivers and will mount your Windows drive as read only and boot it from a USB stick.
Click to expand...
Click to collapse
Yeah, actually didn't think about that, thanks. I'll give it a try when I get enough time.
bobby janow said:
At least I would try a USB A-C first. And the thing is it might not fix the problem with the reinstall.
Click to expand...
Click to collapse
As I said, I have no USB A-C cable that supports data transfer. But I'll borrow one to at least try.
And the thing is it might not fix the problem as well if drivers are screwed up.
If you have another USB-C port, I would try that as well. Sometimes different ports, even on the same controller, can have different results.
Unfortunately I have just one USB-C port.
CyanFrank said:
Well, there's not any device with an exclamation mark. The thing is after I plug in the phone I can't see Pixel 7 in Device Manager - there is only "Android ADB Composite Interface". "Pixel 7" is visible in the tab on another PC though.
Click to expand...
Click to collapse
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
bobby janow said:
That's good and bad lol. Good because it won't try to auto reinstall an incorrect driver but bad because you can't really update it from device manager. As for the .inf driver wpdmtp.inf I believe is the older version that was replaced by winusb.inf. Have you tried to install either or both drivers via right click - install on the file name? That was the fix some time ago but as I said many moons.
Click to expand...
Click to collapse
Yeah, I tried that as well.
And forgot to mention that I borrowed USB A-C cable and MTP actually worked. It's not as stable as it should be (sometimes it disconnects) but still it works.