Database Info

A self inflicted wound

Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.

hushpup131 said:
Loaded my BL 1.1 with [ROM - 1.2] BETA ICS 4.0.X - Team DRH, worked like a charm. I got greedy and attempted to load [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery. It didn't go well.
I knew that if I can get into the APX mode, I would eventually Flash myself back to the original BL 1.1 3588. After many hours I did succeed and got the invitation to take the 3588 OTA. That went well. I was trying to get CWM to switch on (power plus Volume+) because even though I was able to see the internal SD card, side load the ICS 4.0.X & the Gapps, I knew there was no way to partition (2048/0) as well as unpack the new ROM.
During one of my attempts to get CWM to switch on, I was invited to take a BL 1.2 update, #5379 I think. That reboot really locked me out. I have the cover off to access the reset button. I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is essentially it doesn't see the tablet.
May I ask for some suggestions? I'm ready to Flash away but....
“Please follow the steps in the OP. If you follow those, you will actually be flashing the newest CWM touch recovery and our rom.
HOW TO INSTALL
• Boot into current version of CWM and "Wipe data/factory reset"
Dear fosser2,
“I have the cover off to access the reset button, I'm getting no audible (USB to PC). I've tried several attempts to reflash but the response from the BAT file is it essentially the Flash doesn't see the tablet.”
Thank you for your excellent work. Your steps are very explicit for a flawless installation.
The situation I have failed to make clear is that I am unable to reach the APX mode. There is no audible tone (high to indicate APX mode, low to indicate Not in APX mode).
My attempt to reflash to stock blindly, in the audible sense, has the response “USB device not found.
I’m going to repost this in the General section. I would be grateful for any suggestions.
Click to expand...
Click to collapse
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053

jamcar said:
can you get into APX mode?
---------- Post added at 05:19 PM ---------- Previous post was at 05:12 PM ----------
if so just use my BL update
http://forum.xda-developers.com/showthread.php?p=20410053#post20410053
Click to expand...
Click to collapse
I am not able to get into the APX mode. The basis of my belief is there is no audible signal (USB to PC) and there is no new window opening inviting me to explore a new drive.

I have disconnected the battery both short term as well as over night, no response from the power only and power plus volume – buttons.
The charge light has turned green; no response from the buttons.
Measuring the voltage at the charger tip read 12+ volts. I am using a new USB to PC cable. Out of curiosity I unplugged the battery connector and re-connected to see the charge light switch off and on while the charger was connected. As a novice here, I suspect that test eliminated the charging circuit as a fault.
I'm in UBUNTU
loaded and extracted gtab.nvflash.1.1.branch.20110422 with cwmv8.zip
the response says:
"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
@set /p batuserinput=Press enter to continue:
- what does this mean?

1. Is there any sort of display brightening (even briefly?) after you power on? In APX mode, for example, the screen will brighten slightly, then go dead again.
2. Try this test on Ubuntu to see if the tablet has gone into APX mode:
Code:
[I]Power off gTab.
Power on gTab using Power & Vol [-].[/I]
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[18045.279886] usb 1-1.2: new full speed USB device number 6 using ohci_hcd
[18045.384823] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7820[/B]
[18045.384830] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18045.384835] usb 1-1.2: Product: APX
[18045.384839] usb 1-1.2: Manufacturer: NVIDIA Corp.
$
A USB product id of 7820 indicates APX mode on the gTab.
Post the exact output (if any) of your run here.
For reference this is the output when the gTab is running either CWM or the ROM:
Code:
$ [B]sudo dmesg -c >/dev/null[/B] [I] Clear old kernel logs.[/I]
[I]Now connect the USB cable to the gTab.[/I]
$ [B]dmesg[/B] [I] Get latest log message.[/I]
[17516.799429] usb 1-1.2: new full speed USB device number 5 using ohci_hcd
[17516.911353] usb 1-1.2: New USB device found, idVendor=0955, idProduct=[B]7100[/B]
[17516.911361] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17516.911366] usb 1-1.2: Product: NVIDIA Harmony
[17516.911370] usb 1-1.2: Manufacturer: NVIDIA
[17516.911374] usb 1-1.2: SerialNumber: 0270308341006257
$
The product id will be 7100.

[email protected]:~$ coonected USB to Gtab, power button plus vol minus 2 minutes
coonected: command not found
[email protected]:~$ sudo dmesg -c >/dev/nul
bash: /dev/nul: Permission denied
[email protected]:~$ pwd
/home/ubuntu
[email protected]:~$ cd ..
[email protected]:/home$ cd ..
[email protected]:/$ pwd
/
[email protected]:/$ sudo dmesg -c >/dev/null
[email protected]:/$ dmesg
[email protected]:/$
[email protected]:/$

It's not surprising that you got no output--I screwed up. The sequence of steps was incorrect: the cable has to be connected between the 2 dmesg commands. Please repeat.
(If you want to insert inline comments on the command line do it like this:
Code:
$ [B]# This is just a comment.[/B]
The shell will ignore everything from the `#' character to the end of the line.)
And, this video is what I recommend to people whose bootloader seems to be trashed--which is what I think your problem is: How to unbrick your Viewsonic G-Tablet

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$

The first 2 commands are not needed:
hushpup131 said:
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ # power plus volue - for 3 seconds, USB inserted
[email protected]:~$ dmesg
[email protected]:~$
Click to expand...
Click to collapse
Yeah, as I suspected, its a bad bootloader and/or other critical partition problem.
If you are certain that the USB cable and ports are OK (check using another device--try a "sudo adb devices" command with a phone, for instance) and you ran the second dmesg command after connecting the USB cable (otherwise, power off and do the sequence again), then your only option now is to follow the K1 pad-shorting procedure shown in the video.
BTW, you didn't answer question #1 in post #5, above. Is there any change in the display brighness after powering on?

[email protected]:~$ sudo dmesg -c >/dev/null
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
[13557.908045] usb 4-1: new low-speed USB device number 4 using uhci_hcd
[13558.145227] input: Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00 as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input17
[13558.145525] generic-usb 0003:045E:00E1.0003: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse\xffffffc2\xffffffae\xffffffae 1.00] on usb-0000:00:1a.1-1/input0
[13558.256080] usb 1-4: new high-speed USB device number 6 using ehci_hcd
[13558.397196] scsi9 : usb-storage 1-4:1.0
[13559.397403] scsi 9:0:0:0: Direct-Access Motorola A855 0001 PQ: 0 ANSI: 2
[13559.398816] sd 9:0:0:0: Attached scsi generic sg3 type 0
[13559.403602] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[email protected]:~$
question one, post five... there was no change in the display
There was no change in the display after shorting K1

hushpup131 said:
[email protected]:~$ dmesg
[13557.584148] usb 4-1: USB disconnect, device number 3
Click to expand...
Click to collapse
Your USB cable seems OK, but, I don't like that line above. Can you describe exactly what you did when you captured that output?
And, run through that dmesg sequence once again exactly as described and post the output. Also, connect the gTab directly to a USB port, and not through a hub.

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

[Q] $20 who fixes this: Tf101 totaly bricked

Hi Folks,
I have tried everything...... But I can't get my BRICKED device back to life! Pleae help, the person who will FIX this wil be donated $20,- for his help, because i've tried everything that I know.
The problem is:
I have a TF101 and it's BRICKED
It has ClockworkMod Recovery v6.0.1.3 installed, TWRP is also recognized at last time I was live and kickin in ROM MANAGER, but YES I was stupid and flashed ClockworkMod Recovery v6.0.1.3. Now I can't get /sdcard/ mounted. ADB drivers can not be installed even in APX modus windows 8,7, and XP are all saying UNKNOWN DEVICE.
When I try to format /system the log says:
Formating /system ...
Done.
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
LabeL:
Blocks: 131072
Block groups: 4
Reserved block gorup size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Done.
I:Can't format unknown volume: /sdcard
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
I can't push a rom to anywhere with ADB
Please help me!!!! You'll really earn $ 20,- when I get my device fixed with TWRP running and a good ROM.
I can pay through PAYPAL, normal IBAN account or by donate button if you have one. I wil pay when the system is running again!
I hope someone can help!
:crying::crying::crying::crying::crying::crying::crying::crying:

what sbk is the TF?

scottyf79 said:
what sbk is the TF?
Click to expand...
Click to collapse
Hello Scotty,
I have an B60, so my version should be an SBK-1
Thanks for your reaction on my post!

I also can't push files ADB won't recognize my device.
I think the partion or something is also damaged.
The thing is definitly totally wiped!
I hope someone can help me.

APX should always work, unless there is a hardware defect.
Try these drivers. Try if possible with XP.
Then use easyflasher to install recovery or stock rom again.
Remember:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
AND NEVER USE Rom Manager again on TF101!!

gls9 said:
APX should always work, unless there is a hardware defect.
Try these drivers. Try if possible with XP.
Then use easyflasher to install recovery or stock rom again.
Remember:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
AND NEVER USE Rom Manager again on TF101!!
Click to expand...
Click to collapse
I know the APX modes. So that's one thing i am aware of. The strange thing is that wether i start up in the CWM revoverymodus, or APX, or try to COLD BOOT (hangs) or normal startup. In al was windows 7,8 and XP are telling me UNKNOWN DEVICE.
When I manually try to update drivers, the system won't except the drivers because the shouldn't be compatible?!?!?!?!?
So the naked drivers haven't worked!
If could only get in a working APX mode.... I could manage it from there, but that;s the major issue.
Is it possible that UBUNTU should recognize the tablet?? I could even install DOS or LINUX on a spare machine..... But then I won't have an USB support.

Erik Stroot said:
I know the APX modes. So that's one thing i am aware of. The strange thing is that wether i start up in the CWM revoverymodus, or APX, or try to COLD BOOT (hangs) or normal startup. In al was windows 7,8 and XP are telling me UNKNOWN DEVICE.
When I manually try to update drivers, the system won't except the drivers because the shouldn't be compatible?!?!?!?!?
So the naked drivers haven't worked!
If could only get in a working APX mode.... I could manage it from there, but that;s the major issue.
Is it possible that UBUNTU should recognize the tablet?? I could even install DOS or LINUX on a spare machine..... But then I won't have an USB support.
Click to expand...
Click to collapse
If you see unknown device in device manager, just point to the driver by hand.
Use XP.
A time ago I used Ubuntu ubuntu-11.10-desktop-i386.iso.
Driver was included because I could use nvflash in it. I made a backup with nvflash in Ubuntu. Don't know about later versions of ubuntu.
But first give a try in XP because then you can use easyflasher.
edit: I see you already did by hand.
Which driver you are pointing to ?
I have a nvflash.zip with driver included (usbpcdriver directory). You can also point to universal naked driver.

Have a read through this thread, if your tablet supports NVFlash it should work so long as there are no hardware issues
http://forum.xda-developers.com/showthread.php?t=2270850

I did try to point them by hand, but it's not working.....
I'm using XP on a machine where the tablet was never been used on. So conflicts are also terminated by that.
I did lose my tablet's battery when I was formatting the /data partition. Could that also be the problem? (Dummy
)

This is DUTCH, but the fault is displayed in english.

Erik Stroot said:
I did try to point them by hand, but it's not working.....
I'm using XP on a machine where the tablet was never been used on. So conflicts are also terminated by that.
I did lose my tablet's battery when I was formatting the /data partition. Could that also be the problem? (Dummy
)
Click to expand...
Click to collapse
Not for APX. APX should always work because it is in the hardware.
Did you use a usb 2.0 port on XP ?
Which drivers you are pointing to ?
(where are they are coming from)
You can give Ubuntu a try. You can use the live cd. Installing is not necessary.
---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------
Erik Stroot said:
This is DUTCH, but the fault is displayed in english.
Click to expand...
Click to collapse
Cannot read it. Picture is to small.

Thanks *DETECTION* I'll will read that thread also.
@gls9:I'm pointing to the naked driver as you said to me, it won't work!
DO you know a alternative way???

Erik Stroot said:
Thanks *DETECTION* I'll will read that thread also.
@gls9:I'm pointing to the naked driver as you said to me, it won't work!
DO you know a alternative way???
Click to expand...
Click to collapse
What message you are getting ?
Point to the main directory of the drivers, not to the i386 directory (just to be sure).

gls9 said:
What message you are getting ?
Point to the main directory of the drivers, not to the i386 directory (just to be sure).
Click to expand...
Click to collapse
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
PS I am know on UBUNTU LIVE DVD, but over there I can't find the device list, but only a view with DISPLAY, MOUSE etc.
IS there an one click flasher for UBUNTU for SBK-machines????

Erik Stroot said:
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
PS I am know on UBUNTU LIVE DVD, but over there I can't find the device list, but only a view with DISPLAY, MOUSE etc.
IS there an one click flasher for UBUNTU for SBK-machines????
Click to expand...
Click to collapse
First try this on Ubuntu
Then you know apx and nvflash will work.
After this you can try nvflash from here
You have to flash the SOS partition (=recovery). Get it from the easy flasher zip. It is also there.
I don't know if there is a one click flasher for linux. Maybe you can use this
---------- Post added at 09:46 PM ---------- Previous post was at 09:26 PM ----------
Erik Stroot said:
I am pointing in the directory and i am getting the message:
Can not find newer drivers for hardware
Strange.... because there aren't any drivers.... UNKNOWN DEVICE is "installed" without any drivers!
Click to expand...
Click to collapse
Is unknown device gone when disconnect TF101 ?
(to make sure you looking at the right one)
Edit: did you also installed Asus Sync on XP ?
If yes, deinstall and try again with driver.
If not, install Asus sync and try again.
What I also did ( in XP):
- disconnect TF
- start TF in APX mode
- connect cable
(don't know if it is relevant but you can try)
With NVFLASH you must be sure what you are doing. I never restored with it.
I prefer the easyflasher method.

gls9 said:
First try this on Ubuntu
Then you know apx and nvflash will work.
After this you can try nvflash from here
You have to flash the SOS partition (=recovery). Get it from the easy flasher zip. It is also there.
I don't know if there is a one click flasher for linux. Maybe you can use this
---------- Post added at 09:46 PM ---------- Previous post was at 09:26 PM ----------
Is unknown device gone when disconnect TF101 ?
(to make sure you looking at the right one)
Edit: did you also installed Asus Sync on XP ?
If yes, deinstall and try again with driver.
If not, install Asus sync and try again.
What I also did ( in XP):
- disconnect TF
- start TF in APX mode
- connect cable
(don't know if it is relevant but you can try)
With NVFLASH you must be sure what you are doing. I never restored with it.
I prefer the easyflasher method.
Click to expand...
Click to collapse
Hi GLS9,
Yes when I turn of the device, unknown device disapears!
I also did the connecting in your way.
I have also tried installing asus sync.... Also no succes!
I'm trying to connect within Ubuntu, but i can not instal pakages on the normal way as they are descriped in multiple threads.
Tomorrow or Monday i'll Will install Ubuntu in stead of running it from dvd. I will try further! For now i Will have to run! Thanks for your support till now.

Erik to fix unknown device, you have to uninstall it in device manager, then with tab reconnected and on, Windows will try to install the drivers automatically DO NOT ALLOW IT, cancel installation , then head back to device manager and manually install the naked drivers.
Steps
1. Tab is connected and displays unknown device
2. Uninstall unknown device from device manager
3. A reboot of the pc and turn the tablet off and then back on.
4. After reboot reconnect tablet, Windows will try to automatically install drivers " stop immediately " do not allow installation.
5. Go back to device manager and manually install naked driver.
It would be better to do this on Windows 7 if you have it, Windows 8 has driver enforcement which can be extra work to disable.
Sent from my Transformer Prime TF201 using XDA Premium HD

In device manager, try going to VIEW > SHOW HIDDEN DEVICES
That might solve your disappearing issue
But to force a driver install, instead of telling the update driver window to look in a folder, tell it you have the file on your PC and direct it exactly to that driver

Erik Stroot said:
Hi GLS9,
I'm trying to connect within Ubuntu, but i can not instal pakages on the normal way as they are descriped in multiple threads.
Click to expand...
Click to collapse
What packages do you want to install ?
As I remember correctly, nothing is needed.

Would you like me to attempt to walk you through fixing it in windows?
I can use the teamviewer software to either take control of or direct you on where to click (RC or Meeting) and see if I can't help you get the drivers working. I had a tablet in a similar condition that I fixed in this manner for someone.
Pm or quote me if you want, otherwise continue with trying advice in this thread. I don't have much else to add reading through other than making sure the drivers are done right.

Please Help! Nexus 4 shattered screen

Hello Helpers, I shattered my Nexus 4 screen, and the phone has a Pin lock, and is currently in Airplane Mode with BlueTooth enabled. It does Not have USB debugging enabled.
My objective is just to pull out the video, audio, and pictures files, after which I would throw the phone away. I appreciate any feedback, or if someone can help me post a reply to "k.janku1" at the post here http://forum.xda-developers.com/showthread.php?t=2786395 Please refer to point (4) below.
So is there a way I can enabled USB debugging or pull my files out? Following are what I have done, and none are successful in accessing the phone:
1) I have an OTG cable with a mouse. Nexus 4 would not recognize it. I did try to have this OTG Cable + Mouse plug into another Motorola phone and it worked, just not Nexus 4.
2) I plug my Nexus 4 into the PC through the USB cable, the Windows 10 recognize it but when I try to browse that Nexus 4, no files show up.
3) I installed the Android Studio 2.2.2, with various SDK (5.0 and 5.1 SDK) + Google USB driver. And then proceed to run the ADB "shell" or "devices" command located in folder "platform-tools", and the command line would tell me -- "error: no devices/emulators found", or "List of Devices attached" but with NO list of devices displayed. I even boot into Recovery Mode and the ADB command still not seeing any phone.
4) I even try the post here, and I could not get it working either -- http://forum.xda-developers.com/showthread.php?t=2786395
i) I tried the steps listed here http://forum.xda-developers.com/showpost.php?p=66731042&postcount=260 but it does not work for me. The step (2) here returned me "No devices", while step (3) is sort of confusing as it involves TWRP (??) and it said BootLoader would erase all my data files!
ii) Another post here in the same thread -- http://forum.xda-developers.com/showthread.php?p=62398797#post62398797 which mentions the use of "Flash through ADB". But then my phone does not have USB Debugging enabled, so how can ADB talk to the phone in the 1st place? And compile his codes in Android Studio perhaps?
iii) Another post of same thread -- http://forum.xda-developers.com/showthread.php?p=61792353#post61792353 which is lengthy and involves self-custom kernel + compile using Kernel Kitchen. Would this really work?
Thanks
Sean

I had the same of your situation i search and tried a lot of things even show the phone screen in pc but me too i didn't have usb debugging enabled, so what i did is :
Flash the stock ROM for my phone by Odin (it don't need usb Debugging enabled it is for Samsung phones) and by flashing new ROM all your files will be stay in the internal storage, after that the files will be showed in the PC, i don't know if u try that before so that is my solution
Sent from my GT-I9300 using Tapatalk

Xkirnel99 said:
...
Flash the stock ROM for my phone by Odin (it don't need usb Debugging enabled it is for Samsung phones) and by flashing new ROM all your files will be stay in the internal storage, after that the files will be showed in the PC, i don't know if u try that before so that is my solution
Click to expand...
Click to collapse
Thank you for the hint. But I doubt if this approach would work for Nexus 4. I searched online for Odin + Samsung, seems like Samsung phone has a Download mode where the phone would accept the new image file put to it. There is no such mode for Nexus 4, so the phone would not read anything in easy steps like Download mode.

Android driver

Hi,
I have Senter ST907 tablet. When I turn it off and connect it to my PC via USB cable, three devices with name "Android" are displayed in device manager. However, windows can't install drivers for them. All three devices have VID: 05C6 and PID: ADB1. What driver should I install for them?

gaminn said:
Hi,
I have Senter ST907 tablet. When I turn it off and connect it to my PC via USB cable, three devices with name "Android" are displayed in device manager. However, windows can't install drivers for them. All three devices have VID: 05C6 and PID: ADB1. What driver should I install for them?
Click to expand...
Click to collapse
I found a list of various Qualcomm drivers when I did a search using the VID: that you posted above, but I didn't find anything specific to your device, scroll to the bottom of the page linked below and use the phone numbers or the email address to contact the manufacturer and request the correct drivers.
http://m.senter-e.com/news/senterst9077inchtabletpc-ruggedindustrialandro-7048932.html
Sent from my LGL84VL using Tapatalk

If you can't find an USB driver for the tablet on its official website, you may try to install a general-purpose usb driver for Android devices released by Google.
---------- Post added at 09:10 AM ---------- Previous post was at 09:07 AM ----------
In fact, several days ago, I installed that general-purpose usb driver for my Huawei mobile phone and it works well till now.

I have three USB devices:
VID_05C6&PID_ADB1&MI_00
VID_05C6&PID_ADB1&MI_01
VID_05C6&PID_ADB1&MI_02
Not sure how to modify android_winusb.inf to correctly install the driver.
These are USB configuration descriptors of these devices: http://gaminn.sweb.cz/config_desc.txt

gaminn said:
I have three USB devices:
VID_05C6&PID_ADB1&MI_00
VID_05C6&PID_ADB1&MI_01
VID_05C6&PID_ADB1&MI_02
Not sure how to modify android_winusb.inf to correctly install the driver.
These are USB configuration descriptors of these devices: http://gaminn.sweb.cz/config_desc.txt
Click to expand...
Click to collapse
This might help with what you're talking about. I found a list of Qualcomm USB drivers yesterday but they weren't descriptive enough to figure out which ones you need.
https://anomaloushacker.blogspot.com/2011/01/qualcomm-usb-drivers-for-windows-7-x64.html?m=1
Sent from my LGL84VL using Tapatalk