Database Users

[Q] Troubles with ADB on Windows XP SP3. Help.

Hi,
I have a Windows XP SP3 (i386) that just won't let me use ADB. It doesn't work in ways I will describe shortly, and it never worked, on none of the ROMs I had. I had four roms in total in the past 3 weeks: Rooted original 2.1, non rooted JPM, rooted Kyrillos 3.0 and now I run rooted Lestatious 2.0 Build 1.2.6, akin' to go for 1.7.0.
I am primarily a Linux user (fedora 14 x86_64), and adb works fine for me there. As does ADB over WiFi (both Linux and Windows). For all my needs so far, Linux was enough, ODIN worked from the start, so I never bothered to find what's wrong with the Windows' adb.
But trying out Lestatious, I now have the need to update the rom using Windows, and it wouldn't be bad at all to use some other already prepared scripts for Windows I stumple upon on the forums.
As far as drivers go, I have the freshest Kies installed. I have the necessary Android SDK parts installed. Debugging mode is selected on the phone.
Actually, I am at the point where I have the WHOLE Android SDK installed, and have spent way more time on researching and googling and debugging than I would've needed to convert Lestatious' batch scripts into bash ones. And almost literally, pulling my hair out.
I'm no total noob when it comes to flashing/hacking/rooting/modding devices. I've even done my own Pandora battery switch mod for PSP for God's sake!
But this just stumps me....completely.
All this behaves the same, no matter what combination of starting and killing adb I do, pulling cable out, disabling debugging mode, plugging in, unplugging, enabling debugging, plugging in, etc. It also makes no difference whether I use Android SDK adb or, let's say, Lestatious' supplied adb.
Also note that I have both tools and platform-tools folder in my PATH variable.
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
myserialno;-) device
C:\>adb remount
error: protocol fault (status 72 65 6d 6f?!)
C:\>adb shell df
error: protocol fault (status 2f 64 65 76?!)
C:\>adb shell ls
error: protocol fault (status 73 71 6c 69?!)
C:\>adb root
error: protocol fault (status 61 64 62 64?!)
Although it does give me protocol fault, the device does disconnect/reconnect:
Code:
C:\>adb usb
error: protocol fault (status 72 65 73 74?!)
Phone does reboot:
Code:
C:\>adb reboot
error: protocol fault (no status)
Have to break this one, because it never returns:
Code:
C:\>adb shell
^C
Any help will be greatly appreciated.
Thank you.

can i post reply?

[email protected] said:
can i post reply?
Click to expand...
Click to collapse
STOP! NOW!
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO

Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?

Thom47 said:
Sounds like a Samsung USB driver issue to me. Make sure you got the right ones. Are you using 64-bit or 32-bit windows?
Click to expand...
Click to collapse
Thanks for taking interest in my problem.
I'm using 32-bit Windows XP (with SP3).
I did not fiddle with any drivers, I would if I found any . The drivers were installed with the Samsung Kies software. I also tried uninstalling and installing Kies. The Kies is version Kies_2.0.0.11032_12_9.exe downloaded from UK Samsung Support for Galaxy i5800.
Just to be sure, and because I have access to two completely identical machines (yes, hardware and software is the same, except the Android part).
On one machine I have the complete Android SDK, earlier version of Kies (updated yesterday to the latest version).
On the second machine I have only the latest Kies (never updated, installed it this morning). And no SDK, just Lestatious' adb.exe and AdbWinApi.dll.
The behavior stays the same.
Thanks

Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.

Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
Thanks. I will try it as soon as I get home from work.
Thanks again.

Thom47 said:
Well, try these. They're Samsung's USB drivers for our phone. If possible, try starting from the beginning eg. remove all traces of KIES and your phone, and then apply the downloaded driver. By this I mean "uninstall" the phone from your computer.
Click to expand...
Click to collapse
So, I used usbdeview to uninstall the device first. Then I uninstalled Samsung Kies. And finally Samsung USB drivers that get installed with Kies automatically.
I rebooted, just to be sure. Installed the drivers linked in Thom47's post, and rebooted again.
I ran the adb start-server. Connected my device (which was correctly recognized, just as before). The end result is the same. Although status gives a bit different numbers:
Code:
C:\Documents and Settings\Miki>adb shell ls
error: protocol fault (status 1b 5b 31 3b?!)
C:\Documents and Settings\Miki>adb shell
^C
But looking at the adb client source code, I see that the numbers represent 4 Bytes of data read from some file descriptor when getting adb status. It's a bit too late to follow up what file descriptor, but as readx (used to transfer the first 4B from file descriptor into buffer) is sometimes used for reading device drivers because of its portability, this definitely points a finger to some sort of driver issue.
Just thought that it might help to list connected devices when the phone is plugged in (debugging mode, of course):
ADB Interface->Samsung Android Composite ADB Interface
Disk Drives->SAMSUNG GT-I5800 Card USB Device
Modems->Samsung Android USB Modem (is this supposed to be here?)
USB Controllers->SAMSUNG Android USB composite device
Click to expand...
Click to collapse
Update: I just quickly skimmed through the code to see what is the file descriptor, and it's actually just a socket connection to ADB port. So, if I understood it correctly, the first 4B read by readx are reply from the device (?!). Still could be driver related in my opinion.
Thanks

Right, well that's where my knowledge on linux and stuff ends, so I think you should make a new thread to some general forum, since this might not be related to our phone only.

Will do. Thanks for the help.
--
Sent from my GT-I5800

Just thought someone ought to know...

While trying to resurrect my bricked Nexus S I9020a, I used the Unbrickable Mod software, and the software itself crashed. I'm on Arch Linux 64-bit. I tried both JDK6 and JDK7. Here is the stack trace, along with everything else the code printed out.
$ /opt/java6/jre/bin/java -jar Downloads/UnBrickableResurrectorR40.jar
System temp folder created sucessfully in: /tmp/rodpriceHeimdallOneClickF28C53DE/
Uncompressing HIBL Payload to /tmp/rodpriceHeimdallOneClickF28C53DE//n
/tmp/rodpriceHeimdallOneClickF28C53DE/UnBrickPack.zip
Problem while executing arch in Shell.sendShellCommand() Received
Building command list
#S5PC110 (Galaxy S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: Sbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Problem while executing arch in Shell.sendShellCommand() Received
Clearing Previous Instance
Building command list
#S5PC110 (Nexus S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: nexus_sbl.bin LOCATION:0x33040000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button while holding button combination
5. Download new software with fastboot for Linux.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Exception in thread "Thread-1" java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String;
at com.AdamOutler.LowLevelUnBrick.Shell$1.run(Shell.java:191)
at java.lang.Thread.run(Thread.java:662)

rodprice said:
While trying to resurrect my bricked Nexus S I9020a, I used the Unbrickable Mod software, and the software itself crashed. I'm on Arch Linux 64-bit. I tried both JDK6 and JDK7. Here is the stack trace, along with everything else the code printed out.
$ /opt/java6/jre/bin/java -jar Downloads/UnBrickableResurrectorR40.jar
System temp folder created sucessfully in: /tmp/rodpriceHeimdallOneClickF28C53DE/
Uncompressing HIBL Payload to /tmp/rodpriceHeimdallOneClickF28C53DE//n
/tmp/rodpriceHeimdallOneClickF28C53DE/UnBrickPack.zip
Problem while executing arch in Shell.sendShellCommand() Received
Building command list
#S5PC110 (Galaxy S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: Sbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Problem while executing arch in Shell.sendShellCommand() Received
Clearing Previous Instance
Building command list
#S5PC110 (Nexus S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: nexus_sbl.bin LOCATION:0x33040000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button while holding button combination
5. Download new software with fastboot for Linux.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Exception in thread "Thread-1" java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String;
at com.AdamOutler.LowLevelUnBrick.Shell$1.run(Shell.java:191)
at java.lang.Thread.run(Thread.java:662)
Click to expand...
Click to collapse
If I remember correctly, it requires gksudo.

[Q] Problem running CASUAL

I'm trying to use CASUAL with my AT&T GS4 (sch-i337) as discussed in this thread:
http://forum.xda-developers.com/showthread.php?t=2297900
Sadly I seem to be the noob who proves that it is not noob-proof. My post count is too low to post in that thread, so I'm posting here instead.
I get nowhere because CASUAL never detects my phone. My phone has USB debug mode enabled and is running pure stock MDL firmware, unrooted . My computer is running Win 7 x64, has AV and firewall disabled, latest Java installed, and no 3rd party USB drivers for the phone. The phone shows up normally in Windows Explorer, and I can browse the files on it. I tried 2 different USB cables, rebooted both the phone and computer, and always get the same result.
Here's the CASUAL log:
Code:
[DEBUG]working
[INFO]We are running Windows 7
Creating Temp Folder in:T:\Temp\CASUALMomDad-2013-07-30-23.56.04\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:774 build:6,461
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'T:\samsung_i337\Root-and-Recovery-ATT-TMO-GS4-CASUAL-R774b--Nightly.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]ClassJar:jar:file:/T:/samsung_i337/Root-and-Recovery-ATT-TMO-GS4-CASUAL-R774b--Nightly.jar!/CASUAL/CASUALTools.class
[DEBUG]launching GUI
[DEBUG]Picking Jar File:/T:/samsung_i337/Root-and-Recovery-ATT-TMO-GS4-CASUAL-R774b--Nightly.jar ..scanning.
[DEBUG]Found Windows Computer
[DEBUG]Attempting to write T:\Temp\CASUALMomDad-2013-07-30-23.56.04\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write T:\Temp\CASUALMomDad-2013-07-30-23.56.04\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write T:\Temp\CASUALMomDad-2013-07-30-23.56.04\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write T:\Temp\CASUALMomDad-2013-07-30-23.56.04\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]Searching for scripts
[DEBUG]Setting executable T:\Temp\CASUALMomDad-2013-07-30-23.56.04\adb.exe. Result=true
[VERBOSE]TimeOut on T:\Temp\CASUALMomDad-2013-07-30-23.56.04\adb.exe after 5000ms. Returning what was received.
[VERBOSE]ADB Server Started!!!
[DEBUG][TRANSLATION]@interactionWindowsDeviceNotDetected
[DEBUG][STANDARDMESSAGE]@interactionWindowsDeviceNotDetected
[RESPONSEEXPECTED]
Thanks in advance for any help.

Uninstall the phone drivers from your computer. Remove kies if it is installed. Reboot pc and phone. Give her another try.
When you connect the phone, run casual and let it get the correct drivers. Don't install them via windows.

I assume you have read and know this but open your settings and select about phone and then make sure your baseband does not end with MF3. Otherwise CASUAL won't work. A root method and all that jazz still needs to be found for that baseband.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

system is not seeing your device, make sure debug is selected, and it looks to me also that you have a driver conflict, if you have keis, I suggest removing the drivers.

xBeerdroiDx said:
Uninstall the phone drivers from your computer. Remove kies if it is installed. Reboot pc and phone. Give her another try.
When you connect the phone, run casual and let it get the correct drivers. Don't install them via windows.
Click to expand...
Click to collapse
Thanks, but no phone drivers or Kies have ever been installed on that computer. Rebooted phone and computer several times. Tried several different builds of CASUAL. Phone is never detected by CASUAL.

CAG-man said:
I assume you have read and know this but open your settings and select about phone and then make sure your baseband does not end with MF3. Otherwise CASUAL won't work. A root method and all that jazz still needs to be found for that baseband.
Click to expand...
Click to collapse
Thanks, but as mentioned in the OP, the phone has stock MDL baseband, so that's not the issue. I never actually get far enough for that to be an issue.

Gave up on original Win 7 x64 computer. Switched to another computer with Win Vista x32. As be.fore, this computer has never had phone drivers or Kies installed. When I plug the phone into the computer, Windows successfully detects it and I can browse the files in Windows Explorer. And yes the phone definitely has USB debugging mode enabled.
With the last couple of nightly builds, CASUAL tells me that the phone is detected. However, there seems to be an error in those builds because the script is missing. Looking in the temp folder where CASUAL extracts the files, there is no SCRIPTS subfolder. Therefore the "Do It" button does nothing. Here is an example log:
Code:
[DEBUG]working
[INFO]We are running Windows Vista
Creating Temp Folder in:C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:778 build:6,497
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Admin\Downloads\gs4\Root-and-Recovery-ATT-TMO-GS4-CASUAL-R778b--Nightly.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]launching GUI
[DEBUG]Picking Jar File:/C:/Users/Admin/Downloads/gs4/Root-and-Recovery-ATT-TMO-GS4-CASUAL-R778b--Nightly.jar ..scanning.
[DEBUG]Found Windows Computer
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]Searching for scripts
[DEBUG]Setting executable C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\adb.exe. Result=true
[VERBOSE]ADB Server Started!!!
[VERBOSE]TimeOut on C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.49.17\adb.exe after 5000ms. Returning what was received.
[DEBUG]Controls Enabled status: true
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]Device Connected
[DEBUG]@stateConnected
[DEBUG]Controls Enabled status: true
Going back to the last instabuild R773b, it does properly extract the SCRIPTS folder, but it never detects the phone (or detects it only momentarily). Here's the log:
Code:
[DEBUG]working
[INFO]We are running Windows Vista
Creating Temp Folder in:C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:773 build:6,423
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Admin\Downloads\gs4\Root-and-Recovery-ATT-TMO-GS4-CASUAL-R773b--InstaBuild.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]ClassJar:jar:file:/C:/Users/Admin/Downloads/gs4/Root-and-Recovery-ATT-TMO-GS4-CASUAL-R773b--InstaBuild.jar!/CASUAL/CASUALTools.class
[DEBUG]launching GUI
[DEBUG]Picking Jar File:/C:/Users/Admin/Downloads/gs4/Root-and-Recovery-ATT-TMO-GS4-CASUAL-R773b--InstaBuild.jar ..scanning.
[DEBUG]parsing SCRIPTS/
[DEBUG]Found Windows Computer
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]parsing SCRIPTS/-build.properties
[DEBUG]parsing SCRIPTS/GS4 Root and Loki Recovery.meta
[DEBUG]parsing SCRIPTS/GS4 Root and Loki Recovery.scr
[DEBUG]parsing SCRIPTS/GS4 Root and Loki Recovery.txt
[DEBUG]parsing SCRIPTS/GS4 Root and Loki Recovery.zip
[VERBOSE]found zip at SCRIPTS/GS4 Root and Loki Recovery.zip
[DEBUG]parsing SCRIPTS/-logo.png
[DEBUG]parsing SCRIPTS/-Overview.txt
[DEBUG]
Starting CASPAC unzip.
[DEBUG][TRANSLATION]@noUpdateRequired
[INFO]Verified up-to-date.
[DEBUG]unzip of SCRIPTS/GS4 Root and Loki Recovery.zip is beginning.
[VERBOSE]Unzipping busybox
[VERBOSE]Unzipping pwn
[VERBOSE]Unzipping Superuser.apk
[VERBOSE]Unzipping su
[VERBOSE]Unzipping recovery.img
[VERBOSE]Unzip Complete
[DEBUG]unzip of SCRIPTS/GS4 Root and Loki Recovery is complete.
[DEBUG]Searching for scripts
[INFO]misc hacks for AT&T Galaxy S4
[DEBUG]adding SCRIPTS/GS4 Root and Loki Recovery to UI
[INFO]
[DEBUG]Setting executable C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\adb.exe. Result=true
[VERBOSE]ADB Server Started!!!
[VERBOSE]TimeOut on C:\Users\Admin\AppData\Local\Temp\CASUALAdmin-2013-07-31-22.56.50\adb.exe after 5000ms. Returning what was received.
[DEBUG]Controls Enabled status: true
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]Device Connected
[DEBUG]@stateConnected
[DEBUG]Controls Enabled status: true
[DEBUG]State Change Detected, The new state is: 0
[DEBUG]@stateDisconnected
[DEBUG]Device Removed
[DEBUG]Controls status: false
The originally posted build 527 also does not detect the phone. Here's a log from that version:
Code:
[INFO]We are running Windows Vista
Creating Temp Folder in:C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:527 build:3,811
CASUAL Copyright (C) 2013 Adam Outler
This program comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it, under certain conditions; run
'C:\Users\Admin\Downloads\gs4\Root%20and%20Recovery%20for%20ATT-TMO%20GS4-CASUAL-R527b.jar --license'
for details. http://android-casual.googlecode.com for source.
[DEBUG]Picking Jar File:/C:/Users/Admin/Downloads/gs4/Root%20and%20Recovery%20for%20ATT-TMO%20GS4-CASUAL-R527b.jar
[DEBUG]Found Windows Computer
[DEBUG]Found: GS4 Root and Loki Recovery
[DEBUG]OMFGWOOT GUI running!
[INFO]misc hacks for AT&T Galaxy S4
[DEBUG]Searching for scripts
[DEBUG]Updating Scripts for UI
[VERBOSE]From Resource: true
[INFO]--GS4 Root and Loki Recovery--
[INFO]This will install root and recovery for you Qualcomm based Samsung Galaxy S4
##############################
# Motochopper Copyright (C) 2013 Dan Rosenberg (@djrbliss)
# Loki Copyright (C) 2013 Dan Rosenberg (@djrbliss)
# TWRP recovery - Team Win
##############################
# Instructions:
# 1. Put your device in debugging mode
# 2. Attach it via USB
# 3. Click the Do It button
##############################
[DEBUG]Created zipResource at /SCRIPTS/GS4 Root and Loki Recovery.zip
[DEBUG]Exiting comboBoxUpdate()
[DEBUG]attempted to lock controls but controls are not availble yet
[DEBUG]Extracting archive....
[DEBUG]Target Script Is resource
[VERBOSE]Unzipping busybox
[VERBOSE]Unzipping pwn
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\adb.exe
[VERBOSE]Unzipping Superuser.apk
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\AdbWinApi.dll
[VERBOSE]Unzipping su
[VERBOSE]Unzipping recovery.img
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]sleeping for Windows ADB start
[VERBOSE]Unzip Complete
[DEBUG]Attempting to write C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\adb_usb.ini
[DEBUG]File verified.
[DEBUG]###executing: C:\Users\Admin\AppData\Local\Temp\AdminTEMPCASUAL9F5DDC95\adb.exe###
[VERBOSE]List of devices attached
[DEBUG]Device List:
[DEBUG]unknown
At this point I've wasted several hours trying to get this tool to work and have gotten nowhere, so I'm feeling pretty frustrated.

Success!!
It seemed to me that I was having driver problems (except for the builds that are missing the script). So despite all the advice to the contrary, I decided to try installing the Samsung USB driver and then retry CASUAL. That did the trick (on the Vista machine, I didn't try it on the Win 7 machine).
The Samsung USB driver can be downloaded here:
http://www.samsung.com/us/support/owners/product/SGH-I337ZKAATT
After installing that (which literally took about an hour with the hard drive constantly busy), then I ran that latest CASUAL instabuild (r773b) and it worked like a charm.
Yay! Now off to freeze the stupid AT&T software update tasks to make sure they don't push MF3 to me.

spocko said:
Thanks, but as mentioned in the OP, the phone has stock MDL baseband, so that's not the issue. I never actually get far enough for that to be an issue.
Click to expand...
Click to collapse
Yikes. Sorry. I reread OP and I missed the MDL part. I see it now. Lol
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

spocko said:
It seemed to me that I was having driver problems (except for the builds that are missing the script). So despite all the advice to the contrary, I decided to try installing the Samsung USB driver and then retry CASUAL. That did the trick (on the Vista machine, I didn't try it on the Win 7 machine). The Samsung USB driver can be downloaded here:
http://www.samsung.com/us/support/owners/product/SGH-I337ZKAATT After installing that (which literally took about an hour with the hard drive constantly busy), then I ran that latest CASUAL instabuild (r773b) and it worked like a charm. Yay! Now off to freeze the stupid AT&T software update tasks to make sure they don't push MF3 to me.
Click to expand...
Click to collapse
Good job! It seems to always be that way -several hours of frustration where every "correct step" just does not work, then all of the sudden . . .success! Not sure I would have figured it out quickly either -although I did load the Samsung driver myself prior to using CASUAL so I did not have any experience of CASUAL getting drivers for me. . . It's a good data point thanks! Good idea to kill the AT&T OTA as soon as you can! Next stop. . .nice roms to customize!

[Q] sm-n900 heimdall fails to flash recovery

I'm having issues flashing cwm with heimdall. It says:
Code:
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #3 failed. Result: -7
WARNING: Control transfer #4 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -99
ERROR: Failed to send data: "ODIN"
It does detect the device:
Code:
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
Serial No: "?"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
Has anybody had any luck with heimdall 1.4.0?
Tried running Odin in Virtualbox, but have given up on the samsung usb drivers. They install everything but a samsung usb modem device which is only active with usb debugging on or with the phone in download mode.

I don't think heimdall is compatible yet.

designgears said:
I don't think heimdall is compatible yet.
Click to expand...
Click to collapse
Thanks,
It could be the same issue as i9502 is having: github.com/Benjamin-Dobell/Heimdall/issues/152 But I'm not sure it's safe trying to use that zero packet hack on the sm-n900.
And getting this "SAMSUNG Mobile USB Modem #2" device recognized in windows XP seems to need some black magic. I've tried manual install with most of the .inf files in the driver package, took a while...

Got it detected and flashed with Odin 3,09 on a w7 machine. Kies3 installed and used it's reinstall driver function.
Rooted

[HELP]Debrick failed. A DEVICE_DESCRIPTOR_FAILURE T00J

I got a soft-brick T00J and tried debrick it
Unfortunately the usb cable disconnected while running Debrick.bat.
(my bad, I should use a better cable, not a ****ty one. cmdline output below)
Code:
XFSTK Downloader Solo 1.3.6
Copyright (c) 2012 Intel Corporation
Build date and time: Feb 12 2013 13:33:18
.Intel SoC Device Detection Found
Parsing Commandline....
Registering Status Callback....
.Initiating Download Process....
...........................................22734498848407500
............................................................................................................................................................................................................................................................................................................XFSTK-STATUS--Reconnecting to device - Attempt #1
Now Windows 10 recognize it as an "Unknown USB Device (Device Descriptor Request Failed)"
And phone seems to be EPIC BRICK now, no screen, no vibrate.
Is there any solution

Same here, somebody can help?