Root your device EASILY! [CASUAL] [Linux] [Windows] [Mac]

ZADIG step failure

Failing on ZADIG

reading ini file 'zadig.ini'
default driver set to 'WinUSB'
11 devices found.
Using inf name: Gadget_Serial_Control.inf
Succesfully extracted driver files.
Installing driver. Please wait...
libwdi:info [extract_binaries] successfully extracted driver files to C:\usb_driver
libwdi:info [wdi_prepare_driver] succesfully created 'C:\usb_driver\Gadget_Serial_Control.inf'
libwdi:info [wdi_prepare_driver] Vista or later detected - creating and self-signing a .cat file...
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\amd64\winusbcoinstaller2.dll'
libwdi:debug [AddFileHash] 'gadget_serial_control.inf': INF type
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\gadget_serial_control.inf'
libwdi:debug [AddFileHash] 'wdfcoinstaller01011.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\wdfcoinstaller01011.dll'
libwdi:debug [AddFileHash] 'winusbcoinstaller2.dll': PE type
libwdi:info [ScanDirAndHash] added hash for 'C:\usb_driver\x86\winusbcoinstaller2.dll'
libwdi:info [CreateCat] successfully created file 'C:\usb_driver\Gadget_Serial_Control.cat'
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_04E8&PID_685D (libwdi autogenerated)' from 'Root' store
libwdi:info [RemoveCertFromStore] deleted existing certificate 'CN=USB\VID_04E8&PID_685D (libwdi autogenerated)' from 'TrustedPublisher' store
libwdi:debug [CreateSelfSignedCert] set Enhanced Key Usage, URL and CPS
libwdi:debug [CreateSelfSignedCert] created new key container
libwdi:debug [CreateSelfSignedCert] generated new keypair
libwdi:info [CreateSelfSignedCert] created new self-signed certificate 'CN=USB\VID_04E8&PID_685D (libwdi autogenerated)'
libwdi:debug [SelfSignFile] successfully created certificate 'CN=USB\VID_04E8&PID_685D (libwdi autogenerated)'
libwdi:info [SelfSignFile] added certificate 'CN=USB\VID_04E8&PID_685D (libwdi autogenerated)' to 'Root' and 'TrustedPublisher' stores
libwdi:info [SelfSignFile] successfully signed file 'C:\usb_driver\Gadget_Serial_Control.cat'
libwdi:info [SelfSignFile] successfully deleted private key
libwdi:debug [wdi_install_driver] using progress bar mode
libwdi:debug [installer process] got parameter gadget_serial_control.inf
libwdi:debug [process_message] got request for device_id
libwdi:debug [installer process] got device_id: 'USB\VID_04E8&PID_685D&MODEM\6&13ED99AD&1&0000'
libwdi:debug [process_message] got request for hardware_id
libwdi:debug [installer process] got hardware_id: 'USB\VID_04E8&PID_685D&REV_0100&Modem'
libwdi:debug [installer process] got user_sid: 'S-1-5-21-1251222588-1426079406-2303531386-1000'
libwdi:debug [installer process] using syslog 'C:\Windows\inf\setupapi.dev.log'
libwdi:debug [installer process] sylog reader thread started
libwdi:debug [installer process] successfully disabled the system restore point creation setting
libwdi:debug [process_message] switching timeout to infinite
libwdi:debug [installer process] Installing driver for USB\VID_04E8&PID_685D&REV_0100&Modem - please wait...
libwdi:debug [process_message] switching timeout back to finite
libwdi:debug [installer process] more recent driver was found (force option required)
libwdi:debug [process_message] installer process completed
Driver Installation: FAILED (Resource already exists)
11 devices found.
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB&VID1002&PID4397&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (0): USB\ROOT_HUB\4&209DFF44&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB&VID1002&PID4397&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (1): USB\ROOT_HUB\4&21F60AC4&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB&VID1002&PID4399&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (2): USB\ROOT_HUB\4&67395F2&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB&VID1002&PID4397&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (3): USB\ROOT_HUB\4&CA1A60D&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB20&VID1002&PID4396&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (4): USB\ROOT_HUB20\4&318406F3&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB20&VID1002&PID4396&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (5): USB\ROOT_HUB20\4&37566865&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ROOT_HUB20&VID1002&PID4396&REV0000
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbhub USB device (6): USB\ROOT_HUB20\4&3892A9E2&0
libwdi:debug [wdi_create_list] Hardware ID: USB\ASMEDIAUSBD_Hub&VID_040E&PID_0100&REV_0000
libwdi:debug [wdi_create_list] Driver version: 1.10.0.0
libwdi:debug [wdi_create_list] asmthub3 USB device (7): USB\VID_040E&PID_0100&ASMEDIAUSBD_HUB\5&2AE38653&0&0
libwdi:debug [wdi_create_list] Device description: 'USB Root Hub'
libwdi:debug [wdi_create_list] Hardware ID: USB\ASMEDIAUSBD_Hub&VID_040E&PID_0100&REV_0000
libwdi:debug [wdi_create_list] Driver version: 1.10.0.0
libwdi:debug [wdi_create_list] asmthub3 USB device (8): USB\VID_040E&PID_0100&ASMEDIAUSBD_HUB\5&3708C5E2&0&0
libwdi:debug [wdi_create_list] Device description: 'USB Root Hub'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_045E&PID_074B&REV_0260
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbccgp USB device (9): USB\VID_045E&PID_074B\5&1CC56EFC&0&1
libwdi:debug [wdi_create_list] Device description: 'Microsoft® SiderWinderTM X6 Keyboard (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_045E&PID_074B&REV_0260&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
libwdi:debug [wdi_create_list] Driver version: 9.3.161.0
libwdi:debug [wdi_create_list] HidUsb USB device (10): USB\VID_045E&PID_074B&MI_00\6&1F82CADC&0&0000
libwdi:debug [wdi_create_list] Device description: 'Microsoft® SiderWinderTM X6 Keyboard (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_045E&PID_074B&REV_0260&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17514
libwdi:debug [wdi_create_list] HidUsb USB device (11): USB\VID_045E&PID_074B&MI_01\6&1F82CADC&0&0001
libwdi:debug [wdi_create_list] Device description: 'Microsoft® SiderWinderTM X6 Keyboard (Interface 1)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_045E&PID_074F&REV_0140
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
libwdi:debug [wdi_create_list] Driver version: 9.3.161.0
libwdi:debug [wdi_create_list] HidUsb USB device (12): USB\VID_045E&PID_074F\5&1CC56EFC&0&4
libwdi:debug [wdi_create_list] Device description: 'Microsoft® 2.4GHz Transceiver v5.0'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04E8&PID_685D&REV_0100
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_02&SubClass_02&Prot_01
libwdi:debug [wdi_create_list] Driver version: 2.9.507.0
libwdi:debug [wdi_create_list] dg_ssudbus USB device (13): USB\VID_04E8&PID_685D\5&27095923&0&2
libwdi:debug [wdi_create_list] Device description: 'MSM8960'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04E8&PID_685D&REV_0100&Modem
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_02&SubClass_02&Prot_01
libwdi:debug [wdi_create_list] Driver version: 2.9.507.0
libwdi:debug [wdi_create_list] Modem USB device (14): USB\VID_04E8&PID_685D&MODEM\6&13ED99AD&1&0000
libwdi:debug [wdi_create_list] Device description: 'Gadget Serial Control'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_058F&PID_6364&REV_0100
libwdi:debug [wdi_create_list] Compatible ID: USB\DevClass_00&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17586
libwdi:debug [wdi_create_list] usbccgp USB device (15): USB\VID_058F&PID_6364\058F63646476
libwdi:debug [wdi_create_list] Device description: 'Mass Storage Device (Composite Parent)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_058F&PID_6364&REV_0100&MI_00
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_08&SubClass_06&Prot_50
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17577
libwdi:debug [wdi_create_list] USBSTOR USB device (16): USB\VID_058F&PID_6364&MI_00\6&82F8931&0&0000
libwdi:debug [wdi_create_list] Device description: 'Mass Storage Device (Interface 0)'
libwdi:debug [wdi_create_list] Hardware ID: USB\VID_058F&PID_6364&REV_0100&MI_01
libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_00&Prot_00
libwdi:debug [wdi_create_list] Driver version: 6.1.7601.17514
libwdi:debug [wdi_create_list] HidUsb USB device (17): USB\VID_058F&PID_6364&MI_01\6&82F8931&0&0001
libwdi:debug [wdi_create_list] Device description: 'Mass Storage Device (Interface 1)'
----------------------------------------

Windows 7 64 bit
Removed Samsung Drivers with - USBView
Installed Factory Samsung Drivers
All drivers installed
Ran program,
Got ZADIG popup
Failure on installing driver

Any plans to support the Rogers variant of the S3 at any time? I get an unsupported device message when trying to run the application.

AdamOutler said:

^^ You selected Gadget Serial Control, not Gadget Serial.

Click to expand...

Click to collapse

Only item listed was "Gadget Serial Control." And the screen shot shows that is what the instructions state.

Hum....

What versions of android on the at&t sgs3 will this root?

I would like to try this on the RPi, because thats more fun.

AdamOutler said:

You may need to remove drivers from "device manager". Uninstall and select "delete drivers" also. Sometimes people get funny drivers installed. Do you see a Composite device per chance?

Click to expand...

Click to collapse

Ended up having to pick MSM8690 instead of Gadget Serial Control. Worked.

-B

Radarscratch said:

Ended up having to pick MSM8690 instead of Gadget Serial Control. Worked.

-B

Click to expand...

Click to collapse

This is correct for me as well

Sent from my d2att running RootBox 3.9.1

Is this by any chance able to root SGSIII on Cricket?

xxqbnxx said:

I have Mac and would like to participate and help in testing but I have a GS3 for T mobile will it work on my phone?

Click to expand...

Click to collapse

Tried this on my macbook 10.8.2 i got an error of "ERROR:Claming Interface failed!" and it was a no go after that.

ReelFiles said:

Is this by any chance able to root SGSIII on Cricket?

Click to expand...

Click to collapse

Unknown, have you tried:

http://www.cricketusers.com/cricket...laxy-s3-root-recovery-tutorial-cwm-video.html

Sent from my SGH-I747 running RootBox 3.9.1

Will this work with the Bell GS3? It's also under the "d2att" name so I'm hoping this will work with my phone.

Thanks,
Spike

That Baker Guy said:

Tried this on my macbook 10.8.2 i got an error of "ERROR:Claming Interface failed!" and it was a no go after that.

Click to expand...

Click to collapse

Do you have Samsung Kies installed on you Mac?

Sent from my SGH-I747 running RootBox 3.9.1

---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------

53Spike said:

Will this work with the Bell GS3? It's also under the "d2att" name so I'm hoping this will work with my phone.

Thanks,
Spike

Click to expand...

Click to collapse

It should, yes. Though I don't know if it's been tested, so report back with the results please.

Sent from my SGH-I747 running RootBox 3.9.1

Just reflashed stock on my Galaxy S3 GT-I9300 to test it but as expected, it said "Unsupported device". Please Adam, make it work for all. Rooting will then be a child's play for all.

raakaysh said:

Just reflashed stock on my Galaxy S3 GT-I9300 to test it but as expected, it said "Unsupported device". Please Adam, make it work for all. Rooting will then be a child's play for all.

Click to expand...

Click to collapse

Eventually, it will get there. He's working on getting it up and functional on OSX right now. That is I9300, not I9300T right?
I'll put together a script for his approval and we'll go from there.

jrloper said:

Do you have Samsung Kies installed on you Mac?

Sent from my SGH-I747 running RootBox 3.9.1

---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------



It should, yes. Though I don't know if it's been tested, so report back with the results please.

Sent from my SGH-I747 running RootBox 3.9.1

Click to expand...

Click to collapse

i did not have kies installed, i just ended up launching parallels and doing it in win7

That Baker Guy said:

i did not have kies installed, i just ended up launching parallels and doing it in win7

Click to expand...

Click to collapse

Ok, the reason I ask is because that is known to cause this issue.

http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html

I tired to open the App but i get an error message "The java JAR file "CASUAL-Revison308b.jar" could not be launched" "Check the console for possible error messages"

Any Ideas I have MAC 10.6.8

xxqbnxx said:

I tired to open the App but i get an error message "The java JAR file "CASUAL-Revison308b.jar" could not be launched" "Check the console for possible error messages"

Any Ideas I have MAC 10.6.8

Click to expand...

Click to collapse

Mac compatibility is in its very early stages yet.
If you would like to aid in development testing

Please

1. Download (according to your system)
32bit: https://android-casual.googlecode.com/svn/trunk/repo/Heimdall_1.4RC3_mac32.pkg
64bit: https://android-casual.googlecode.com/svn/trunk/repo/Heimdall_1.4RC3_mac64.dmg
2. Install it
3. Put your device into Download Mode
4. open a terminal and type: heimdall close-pc-screen
5. Your device should simply reboot.

If it doesn't reboot, pull the USB cable, remove and replace the battery, and turn it back on. Let me know so that I can continue working on this package.

Please let me know the results. Also let me know if Heimdall was installed on your system previously.

Post your results in this thread or https://plus.google.com/104711040110222472212/posts/HWFZRq82LH5

Thanks