I have a TP and it was working fine ( or so I thought )
To cut a long story short, everytime I plug the usb cable into the computer I get a usb not recognised, I've installed novacom ( I have borrowed another TP and it is fine working with my pc )
If I double click on the unknown device it tells me that there is a code 43 error ( the device has reported problems so its not installed )
Can anyone suggest what I can do to get out of this fix ?
OsDoctor cannot see my device as its not recognised.
Many Thanks
S8utt
What rom are you running and what recovery CMW or TWRP.
I did have gingerbread installed and mboot etc.
In the process of trying to fix the dam thing I've probably made it worse as its completely reset ( no blue text on startup, or menu options to allow selection of what to boot )
The HP symbol just shows and it boots into WebOs
Gingerbread ? You must have done that ages ago. So it now just boots into webos , is recognized from there when you connect it to your PC if so what size is the TOUCHPADs drive showing as available /used.
Yes, I did the hack as soon as it came out and I hadn't touched it since. ( turned into the kids tablet, they complained that they couldn't install any games which is how the fun started )
So anyway, no the TP is not recognised, I get this popup as soon as I plugged the TP in
{
"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"
}
double clicking on the Unknown Device in Computer Management
Gives
I have another Touchpad, and that connects fine to the computer, so I'm guessing its the Touchpad that's at fault, not the PC or drivers, I only hope its not beyond fixing.
I was hoping there maybe a WebOs app I could download ( like a terminal ), maybe there is a way of running some commands on the TouchPad directly ?
s8utt said:
Yes, I did the hack as soon as it came out and I hadn't touched it since. ( turned into the kids tablet, they complained that they couldn't install any games which is how the fun started )
So anyway, no the TP is not recognised, I get this popup as soon as I plugged the TP in
double clicking on the Unknown Device in Computer Management
Gives
I have another Touchpad, and that connects fine to the computer, so I'm guessing its the Touchpad that's at fault, not the PC or drivers, I only hope its not beyond fixing.
I was hoping there maybe a WebOs app I could download ( like a terminal ), maybe there is a way of running some commands on the TouchPad directly ?
Click to expand...
Click to collapse
Have you tried this? Go to settings > storage and click on the 3 squares on the upper right corner. Then click on usb computer connection and make sure the MTP box is checked.
Hope this helps. Good luck.
My thoughts would be to use acmeuninstaller to hopefully remove the Android partition. Reboot and see what if any difference that makes. Before doing the above if you put it into recovery mode" power and volume up" is it recognized by either webos doctor and webos quick install ?
I haven't come across your problem before and would also suggest you give it a while to see if someone more knowledgeable than myself has any other suggestions . Meanwhile I'll put my thinking hat on.
MTP settings ? this is for Android yes ?
I don't have android on it anymore, just WebOs
chicle_11 said:
Have you tried this? Go to settings > storage and click on the 3 squares on the upper right corner. Then click on usb computer connection and make sure the MTP box is checked.
Hope this helps. Good luck.
Click to expand...
Click to collapse
I think the option to boot into Android has gone.
I put into recovery mode ( white usb icon ) still get unrecognised USB,
novacom and webos cannot find the device.
sstar said:
I think the option to boot into Android has gone.
Click to expand...
Click to collapse
Just to keep the info stream alive, even when I could boot into Android, I couldn't get it recognised (USB), so MTP option was not valid as it wasn't even seen.
I think the TP is broadcasting it has a problem which is preventing the Pc from connecting to it.
s8utt said:
I put into recovery mode ( white usb icon ) still get unrecognised USB,
novacom and webos cannot find the device.
Click to expand...
Click to collapse
My fault just boot into webos connect to your PC when webos gives you the USB option hit cancel then run/open webos quick install on your PC ,if you don't have it here is alink https://www.box.com/shared/45151ecc89fd2b4fce2f just put it on your desktop and open it.
Sorry it's been a while since I used it
sstar said:
I think the option to boot into Android has gone.
Click to expand...
Click to collapse
Duhhh. Skimming the thread too fast.........
In webOs, install preware with WOSKI, as sstar wrote. There's an android remover that you can download and install from there. Run it. Install android using acmeinstaller3.
Good luck.
Nope, webos quick install doesn't see the touchpad, well I think it does but it does work due to this code 43 error
s8utt said:
Nope, webos quick install doesn't see the touchpad, well I think it does but it does work due to this code 43 error
Click to expand...
Click to collapse
Must admit I'm at bit of a loss. As I am reluctant to suggest anything that might make your situation worse and don't know what a code 43 error is.
---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------
Re Error 43 have a look at this http://answers.microsoft.com/en-us/...cognised/6a2a5531-8b80-4798-9aa6-ee2dcb705c7f I think it maybe just what you need .
Plus the Microsoft link given .
Hope this helps .
Related
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?
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.
Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
{
"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"
}
Thanks in advance!
papalakaka
I found a way to solve this issue, but I have no idea why it worked.
I installed Windows 7 32-bit on my PC, installed the drivers, restarted and it was instantly recognized as Qualcomm (whatever) 9006.
So I started QPST Software Download app and I was able to download it. It seems that I had to use a 32bit operating system and not Windows 8, at least it looks like that. The Download button wasn't clickable and the device status has shown error on Windows 8 64bit and Windows 7 64bit. It was writable in 32bit. Hope this helps someone out.
Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick
papalakaka said:
Hi,,
I have just tried flashing a ROM on the Ascend W1 and I am getting an error, which has oviously rendered my device unusable. It does vibrate when trying to turn it on, but screen is black.
I was working with eMMC Software Download app, activated "Program Boot Loaders" and loaded a XML-file. Then I clicked on Download, as shown in the video of windowsmania.pl and in their instructions. I got the message:"Download completed - no errors detected" and my device is correctly recognized as Qualcomm HS-USB Diagnostics 9006. In the eMMC Software Download app it is listed as Qualcomm MMC Storage USB Device, which should also be correct. Still, the device status is shown simply as "error" instead of "writable". The Download button is not clickable. I have tried it with two different PCs, one with Windows 7 and another with Windows 8.
What am I doing wrong?
What does this mean and could anyone who has experience with this issue please help me out?
Thanks in advance!
papalakaka
Click to expand...
Click to collapse
You need to run as administrator
Huawei W1 does nothing as expected during flashing..
My W1-U00 started having problems with loading apps..whenever I tried to load my photos or weather channel app or whatever it looked like it tried to load the app but it redirected me on home screen. After a few days I had a problem with the space on device and some updates it needed so I tried to uninstall some of the apps but when I did so and restarted the phone the apps where back again. Since that point it's impossible to uninstall any app,impossible to reset the phone from the settings>about>reset phone and impossible to hard reset the device, I tried all the possible ways to do a hard reset but nothing, it just restarts like nothing happened and I get no sprockets logo. So after a few months I decided to reflash my device. Everything went smooth but after I clicked on the download button of the eMMC Software Download app instead make my device recognized by my pc as Qualcomm HS-USB Diagnostics 9006 the device restarts as normal and nothing happens. It's impossible to make it work, I tried all the methods available online but nothing...Any ideas??
jwiena said:
Right click the eMMC Software Download and choose run as Windows XP Service Pack 2, this should do the trick
Click to expand...
Click to collapse
Thanks bro! I was crazy...
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.
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)
Yup exact same thing, I hope somebody knows how to fix it and help us out.
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?
Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone
seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!
liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"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"
}
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one
liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.
Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.
liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.
hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.
download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification
seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.