What WinXP command proves USB drivers are installed and working?

What WinXP command proves USB drivers are installed and working?

I have never rooted an Android phone but I plan on doing so.
Therefore, I went through the motions and wrote up the instructions below.
About 95% of what I wrote below comes from the first URL.
But I modified it to clarify where I was confused.

One place that I need to further clarify is that I need to tell people HOW
to prove that they have the necessary "usb drivers" on Windows XP.

Hence my question above:
Q: What WinXP command proves USB drivers are installed and working?

-----------------------------------------------------------------
NOTE: Below is the work in progress rooting tutorial.

http://androidcentral.us/2014/04/roo...ung-galaxy-s3/
How to Root T-Mobile Samsung Galaxy S3 (SGH-T999) on Android 4.3 Jelly Bean
Firmware

Requirements:
a. Windows computer with USB drivers installed
b. Fully charged T-Mobile Samsung Galaxy S3 SGH-T999 with USB data cable
c. CF-Root zip package

http://download.chainfire.eu/234/CF-...mo-sght999.zip
d. Odin3 v3.09 Flashing Utility (note the version available is 3.10)
http://androidcentral.us/2013/11/download-odin/
e. Optional: QuickHash for Windows XP
https://sourceforge.net/projects/quickhash/

Phone:
1. Settings More About device (repeatedly tap) Build Number until it
says "you are now 4 steps away from being a developer".
2. Tap developer mode 4 more times until it says "you are now a developer".
3. Enable USB debugging on your phone by the following options:
Settings More Developer Options Debugging USB debugging (check
the box)
It will say:
Debugging mode launches when USB is connected.
Allow USB debugging?
USB debugging is intended for development purposes only.
It can be used to copy data between your comptuer and your device,
install applications on your device without notification, and read log
data.
Press "OK".

NOTE: To turn off developer mode in the futu
Settings More Developer options (slide the green slider from
ON to OFF)
You may need to click "Revoke USB Debugging Authorizations".
You may need to go to apps all settings Clear Data.
Some say you may need to also do a factory reset.
4. To verify root access later, open the Google Play Store app on your
phone and install "Root Checker" by "joey krim".
https://play.google.com/store/apps/d...krim.rootcheck
Use "Root Checker" to confirm root access.
5. Install Titanium Backup root freewa

https://play.google.com/store/apps/d...TitaniumBackup

Windows PC:
1. Extract CF-Auto-Root-d2tmo-d2tmo-sght999.zip to its own folder
Name: CF-Auto-Root-d2tmo-d2tmo-sght999.zip
Size: 17.3 MB (18,147,068 bytes)
MD5 Hash: 6BC132736171F96A59ECF5934B7C30BE
SHA-1 Hash: 72B4547023003064736BF428305AF102031E15D1
SHA256 Hash:
FC0393F86C7A6FD88C3104B09117D6D3C744AEE65F0C339777 2B40E42A1250BF
SHA512 Hash:
DDF472763717672A1D34C726D0A16D1CEAAEB2F8F34253ECA9 8EC558DE5EFA1CEFCB5E58DF9EC247CCBF6E430DD57A232015 AF57F4917C28571C2441479DC7FD
2. Extract Odin v3.09 files to its own folder
NOTE: The only version available is Odin v3.10 which doesn't have a
"PDA" button (it has a PIT button instead).
Name: Odin v3.10 by Ohguideme.rar
Size: 801 KB (820,656 bytes)
MD5 Hash: A51C897BF6B317D545110181D4464C3B
SHA-1 Hash: 1F1B73FACB01E286C1C73F4675EC97B6E14280E2
SHA256 Hash:
6CE9DB71BE56B4B59CB3171BB8FF16765BD7B66102FE0F3D1A EF2D8C4423D5B7
SHA512 Hash:
633414971EE3D6E672C7407B0AB4A67F95511D341B3336F464 A1A9B4D88634E5D93FF962D7042CAC1847B5949B833A147055 A780499C5002A0512F48044EC13E
3. From the Odin extracted folder run Odin3-v3.o9.
4. Reboot your T-Mobile Galaxy S3 into Download Mode:
a. Turn Off Galaxy S3.
b. Simultaneously press & hold the three buttons "VolumeDown+Home+Power"
until you see a warning on your screen.
When you press the buttons, within a couple of seconds, you'll feel a
buzz & the green, white, & yellow message comes up:
Warning!!
A custom OS can cause critical problems in phone and installed
applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel.
Volume up: Continue
Volume down: Cancel (restart phone)
c. After the warning, press once the Volume Up button to continue.

5. While in download mode connect your GS3 to PC via the USB data cable.
Make sure that Odin3 detects your device.
6. In the Odin GUI, make sure that only "Auto Reboot" & "F. Reset Times"
options are checked.
(Leave the rest of the options off, which are the default settings).
7. In the Odin GUI, click the PDA button and from the extracted folder
select the CF-Rooted kernel file and hit the START to flash the kernel.
8. Wait for Odin3 to complete.
9. When completed, Odin will notify you via the PASS!! message in Odin and
at this stage your phone will automatically reboot.
10. Once normally booted, check that SuperSU has been installed.

a. Now you have full root access to your phone.
b. You can also install apps which require root access.
c. You can get rid of the stock apps (using the Titanium Backup app).
d. If you?re planning to install a Custom ROM or Mods then you want to
install ROM Manager, which will then help you to flash Custom Recovery,
TWRP or ClockworkMod, depending on your choice.

Stijn De Jong wrote:
What WinXP command proves USB drivers are installed and working?

https://s2.postimg.org/ddmcjzeex/usbflash.gif

That does not guarantee that all partitions will mount.

Only the first partition of a USB flash will mount in Windows.

While Linux will easily allow four partitions
to be created. And the Linux ones will all mount in Linux.

Paul

On Tue, 07 Mar 2017 00:00:29 -0500, Paul wrote:

Stijn De Jong wrote:
What WinXP command proves USB drivers are installed and working?

https://s2.postimg.org/ddmcjzeex/usbflash.gif

That does not guarantee that all partitions will mount.

Only the first partition of a USB flash will mount in Windows.

While Linux will easily allow four partitions
to be created. And the Linux ones will all mount in Linux.

Thanks for that pointer to the "this device is working properly".
http://i.cubeupload.com/F8AiNN.jpg

As you are aware, we all have had to troubleshoot devices where that
message was displayed, so, I'd normally not put any credence whatsoever
into it, unless you're pretty much convinced that this is the best test.

Here's what mine says on WinXP SP3:
Device Manager Universal Serial Bus Controllers
Right click on "USB Mass Storage Device" Properties
Device General Device status This device is working properly.
http://i.cubeupload.com/F8AiNN.jpg

If that's the best we have, then that's what I'll put in the instructions!

Stijn De Jong wrote:
On Tue, 07 Mar 2017 00:00:29 -0500, Paul wrote:

Stijn De Jong wrote:
What WinXP command proves USB drivers are installed and working?

https://s2.postimg.org/ddmcjzeex/usbflash.gif

That does not guarantee that all partitions will mount.

Only the first partition of a USB flash will mount in Windows.

While Linux will easily allow four partitions
to be created. And the Linux ones will all mount in Linux.

Thanks for that pointer to the "this device is working properly".
http://i.cubeupload.com/F8AiNN.jpg

As you are aware, we all have had to troubleshoot devices where that
message was displayed, so, I'd normally not put any credence whatsoever
into it, unless you're pretty much convinced that this is the best test.

Here's what mine says on WinXP SP3:
Device Manager Universal Serial Bus Controllers Right click on "USB
Mass Storage Device" Properties Device General Device status
This device is working properly.
http://i.cubeupload.com/F8AiNN.jpg

If that's the best we have, then that's what I'll put in the instructions!

You can check Disk Management then, and see if a block device is present.
A USB flash stick will not show up in File Explorer, until somehow the
system discovers it has a file system. Disk Management is one way to
examine it.

The tools in WinXP aren't all that convenient. It can be
difficult to "erase" a USB flash, if you were to copy
a hybrid ISO onto the thing with "dd". Don't expect Disk
Management to do everything you could ever want. Disk Management
GUI and "diskpart" command line, work best with conventional
storage devices. USB flash isn't treated quite as well.
USB rotating disk drives (enclosures) work a bit better than
USB flash. This is related to the status of the RMB bit.
Some larger USB flash sticks, actually have the opposite value
of RMB, than previous lower-capacity ones.

http://www.uwe-sieber.de/usbstick_e.html

You are right to ask questions about USB flash, as it's likely
to have more issues than other storage choices.

And not all desktops can boot from them either. The USB support
module has only been in the BIOS for the last 10-12 years or so.
My oldest two PCs cannot boot from a USB flash.

Paul

On Tue, 07 Mar 2017 01:09:33 -0500, Paul wrote:

You are right to ask questions about USB flash, as it's likely
to have more issues than other storage choices.

Thanks Paul for the disk management suggestion to prove that the phone was
recognized.
http://i.cubeupload.com/Mo5BlN.jpg

In my case, the phone was NOT recognized in either the USB method or the
DISK method, so, pretty much my conclusion is that my USB port on my phone
is kaput.
http://i.cubeupload.com/iPWGCb.jpg

I haven't used it for a year (I charge the batteries in a separate
charger), so, I was just hoping I'd get it to work, but I'm going to root
the phone without using a cable.

This one-click "Kingoroot" method looks promising for example.
https://www.kingoapp.com/

Stijn De Jong wrote:
On Tue, 07 Mar 2017 01:09:33 -0500, Paul wrote:

You are right to ask questions about USB flash, as it's likely
to have more issues than other storage choices.

Thanks Paul for the disk management suggestion to prove that the phone
was recognized.
http://i.cubeupload.com/Mo5BlN.jpg

In my case, the phone was NOT recognized in either the USB method or the
DISK method, so, pretty much my conclusion is that my USB port on my
phone is kaput.
http://i.cubeupload.com/iPWGCb.jpg

I haven't used it for a year (I charge the batteries in a separate
charger), so, I was just hoping I'd get it to work, but I'm going to
root the phone without using a cable.

This one-click "Kingoroot" method looks promising for example.
https://www.kingoapp.com/

Your phone is not a USB Flash key.

For general device recognition, use UVCView or USBTreeView.
The latter is much easier to find.

http://www.uwe-sieber.de/usbtreeview_e.html

When USB devices connect, "endpoints" have to be set up
so that the config space of the device can be read. If an endpoint
forms, and "information" such as USB class comes from the device,
that's proof the physical layer (i.e. the port), is working. Just
seeing the right-hand pane on USBTreeView populate with the
phone info, is proof it is "connected".

Phones use MTP, which is not a conventional file system. The
phone appears as a "device", rather than as a conventional file
system. Operations are done at file level rather than block
level. You cannot "format" the phone from the Windows side.
But you can read a whole file, write a whole file. The granularity,
and where the device appears in GUI interfaces, is different.

On WinXP, the MTP driver is delivered via Windows Media Player,
as it was intended as a path for loading potentially DRM-protected
content into the device. (And in turn, downloading and using the
WMP package involves a "Genuine Check".) On later OSes, the MTP driver
is an in-box driver. Microsoft decided delivering the MTP driver
as "just a driver", wasn't enough.

If all devices had been designed with USB Mass Storage,
the story would have been a lot simpler and more useful
for end-users. (The time required to "get things done" would
be less, because it would "just work".) MTP is meant to be
a form of hand-cuffs.

Paul

On Tue, 07 Mar 2017 16:31:53 -0500, Paul wrote:

If all devices had been designed with USB Mass Storage,
the story would have been a lot simpler and more useful
for end-users. (The time required to "get things done" would
be less, because it would "just work".) MTP is meant to be
a form of hand-cuffs.

Thanks Paul. In the end, I just gave up with the USB because my phone is
worse than most due to the fact the USB port is kaput (which is apparently
common with Samsung S3 phones).

I'm not sure what I did since I installed a foreign APK, but it seems to
have worked to download an APK to kingoroot using Firefox on the phone.

It didn't use Windows, in the end, so this is off topic, but to close the
loop, here's what I did (although I'm not sure what 'type' of root a
"kingoroot' is in the end).
http://i.cubeupload.com/HY1E6B.jpg

I downloaded the ZIP installer (which Android calls an "APK" but it's just
a zip file):
http://i.cubeupload.com/uleVfF.jpg

Then I tapped on the zip file (which is equivalent to a Windows
doubleclick):
http://i.cubeupload.com/Z4uCU6.jpg

That installed the "kingoroot" app:
http://i.cubeupload.com/GxVyyC.jpg

Here is the kingo root app organized in my system folder on my one desktop:
http://i.cubeupload.com/XRjvkP.jpg

I tapped on that Kingoroot app and this came up:
http://i.cubeupload.com/CJlJEg.jpg

I pressed the button to root the phone, which took about 90 seconds:
http://i.cubeupload.com/9Sd1TC.jpg

I started getting scared, but I soon saw a message "root succeeded":
http://i.cubeupload.com/nlIV1u.jpg

To confirm I had root access, I started a separate root-checker app:
http://i.cubeupload.com/9qx4JW.jpg

That root checker app confirmed I now had root access:
http://i.cubeupload.com/DG7PjD.jpg

Then I ran the Titanium Backup free app (which requires root access):
http://i.cubeupload.com/OQHqGv.jpg

And voila! I can now backup my phone to an sd card, to an internal
partition, to a computer, to the cloud, whatever!
http://i.cubeupload.com/aVDyfp.jpg

Thanks for your help, and I hope this helps others, even though it turned
out to be a non-Windows solution that I ended up using (because my phone
USB port was bad).