[Q] Heimdall on Ubuntu still not handshaking, libusb installed - Fascinate Q&A, Help & Troubleshooting

I have Heimdall on Ubuntu 12.04 and have already installed libusb. The gui front-end shows "device detected" as checked. However, testing it (by attempting to download the PIT data onto the desktop) errors thusly:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
Re-attaching kernel driver...
Prior to installing libusb, I think "Re-attaching kernel driver..." didn't appear. I installed libusb 1.0.9 by downloading the tar, and running ./configure, make, install, etc. The didn't appear to be any issue with the libusb install. I originally tried Odin1.3 on Windows Server 2008 R2. The icon for installing device drivers appeared, but couldn't install the device. The phone usb windows driver I downloaded was from Samsung. Also, no apparent issues with that install.
This phone is a Fascinate and had an unbrickable mod installed several months ago. The phone can go into download mode (obviously), and can get to a splash screen for it's until-recently-working MIUI ROM. It cannot go to recovery mode.
This is my main phone and so is important. I've posted elsewhere (outside xda in other 'regular issue' site's forums) in attempting to solve this at the lowest level without bringing in the experts.

Related

[Q] Heimdall support

I understand that as of now Odin is the only option, but does anyone know if Heimdall is being worked on to work for the SGS3? Thanks.
I've not asked/talked/heard about it from anyone. But i could try to find out.
I would appreciate any information. Thanks in advance. I'm new to this forum, coming from the Evo 4g. Over there I know who to talk to, but I am pretty clueless when it comes to Sammy. I am reading as much as I can though.
Sent from my PC36100 using xda app-developers app
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
mrhaley30705 said:
I've emailed Benjamin Dobell (hope i spelled that right), the creator of Heimdall. I'm just awaiting a response.
Click to expand...
Click to collapse
Wow, thanks. You really went above and beyond for me. I was mostly expecting to get flamed or ignored. Cheers.
Sent from my PC36100 using xda app-developers app
All i did was send an email. It is a legitimate question since some type of flash utility is usually required to mod a Samsung phone. I used Heimdall and Odin on my captivate, but preferred Heimdall when flashing bootloaders.
FWIW, Heimdall is known to work with the international S3, and I don't see why it shouldn't work with the US variants.
I haven't rooted yet (as I'm giving it a few days unrooted), but when I do, it'll be with Heimdall, as my phones never touch Windoze (and Odin.exe) if they don't have to. My Captivate was only ever connected to my Linux boxes.
I have tried using Heimdall with my AT&T '747 and was unable to get the phone to communicate with my PC. I have read in various non-authoritative places that this is a known issue but I haven't really seen it any where I'd consider to be reliable just yet. I can't confirm 100% that its a Heimdall issue as I haven't used is successfully with another phone (I'm coming from fastboot land).
[email protected]:/home/mmschnei# heimdall flash --recovery Desktop/recovery.img
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Click to expand...
Click to collapse
NOTE: I have tried this with Heimdall v1.3.2 and v1.3.1. In the above snippet I am using 1.3.1 but I get the exact same message in 1.3.2.
Can anyone else confirm that heimdall does NOT work for them in linux/mac?
Please keep us updated if you hear back from Mr. Dobell.
heimdall v1.3.2
So, I just checked heimdall v1.3.2 out from git (not touched in 3 months), built it, put my phone in download mode, then connected USB (using Fedora 17):
Code:
Jun 30 16:16:56 ivy kernel: [ 853.566542] usb 2-1.6.2: new high-speed USB device number 104 using ehci_hcd
Jun 30 16:16:56 ivy kernel: [ 853.641091] usb 2-1.6.2: New USB device found, idVendor=04e8, idProduct=685d
Jun 30 16:16:56 ivy kernel: [ 853.641096] usb 2-1.6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 30 16:16:56 ivy kernel: [ 853.641099] usb 2-1.6.2: Product: MSM8960
Jun 30 16:16:56 ivy kernel: [ 853.641101] usb 2-1.6.2: Manufacturer: Sasmsung
Jun 30 16:16:56 ivy kernel: [ 853.641770] cdc_acm 2-1.6.2:1.0: This device cannot do calls on its own. It is not a modem.
Jun 30 16:16:56 ivy kernel: [ 853.641822] cdc_acm 2-1.6.2:1.0: ttyACM0: USB ACM device
Jun 30 16:16:56 ivy mtp-probe: checking bus 2, device 104: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2"
Jun 30 16:16:56 ivy mtp-probe: bus: 2, device: 104 was not an MTP device
Linux sees it (though "Sasmsung" is typo'd in udev), and heimdall detects it, but it couldn't print-pit, so, probably not working:
Code:
[[email protected]:0j:1023h:0e:5.85MB sgs3]$ sudo heimdall detect
Device detected
[[email protected]:0j:1024h:0e:5.85MB sgs3]$ sudo heimdall print-pit
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
Re-attaching kernel driver...
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Benjamin Dobell said:
Development and support will continue for Heimdall for the foreseeable future. Unfortunately I have been very very busy lately and haven't even had time to respond to all my e-mails, so I definitely haven't made a lot of development progress.
I do own an international SGS3 so Heimdall will definitely support that device. Heimdall 1.3.2 unfortunately broke compatibility with several devices as I attempted to add support for certain Galaxy Player devices. The SGS3 is one such affected device. So for now I recommend using version 1.3.1.
Click to expand...
Click to collapse
Thank you so much! I truly appreciate your response and all your work.

[Q] Cant post in development, can someone post my log to Adam from Casual

Im trying to jailbreak my phone with Adam's casual. I havent been able to get it to work and he asks for the log if it is not working. I am not new to rooting or romming, I just dont post in xda so I am unable to post in the development section. Can someone get my log over to him so I can figure out why I cant get mine to work. I am rooted and running casual on windows xp 64 bit machine
Thanks
[/CODE]
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\
Picking Jar File:/C:/Users/brandi/Desktop/CASUAL-BackAtchaVerizon-Revision311b%20(1).jar
Found Windows Computer
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinApi.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\AdbWinUsbApi.dll
File verified.
sleeping for Windows ADB start
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\-adb_usb.ini
File verified.
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
Found: WindowsLinux Galaxy Note 2 Jailbreak
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
State Change Detected, The new state is: 1
State Connected
Control Change requested but lock is set.
OMFGWOOT GUI running!
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
Searching for scripts
Updating Scripts for UI
From Resource: true
State Change Detected, The new state is: 1
State Connected
--WindowsLinux Galaxy Note 2 Jailbreak--
This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
Exiting comboBoxUpdate()
Extracting archive....
Unzipping Superuser.apk
Control Change requested but lock is set.
Unzipping boot.img
Unzipping busybox
Unzipping dependentinstaller.sh
Unzipping exploit
Unzipping exynos-abuse
Unzipping recoverThis
Unzipping rootGN.sh
Unzipping su
Unzipping swagBoot
Unzipping viewmem
Controls Enabled status: true
State Change Detected, The new state is: 1
State Connected
Controls Enabled status: true
StartButtonActionPerformed() Script Activated
Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
Controls Enabled status: false
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 75
Executing Scripted [email protected]
CASUAL has initiated a multithreaded execution environment
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
***WEB VERSION***[Ljava.lang.String;@1553d18
Identification: VERIZON GNOTE
ScriptRevision: 2
CASUALRevision: 308
URL: http://forum.xda-developers.com/showthread.php?t=2118348
Server Message: UPDATE: removing limits on Mac for testing purposes
Current Version 1 requires update to version 2
Script is out of date. See http://forum.xda-developers.com/showthread.php?t=2118348 for more information. Updating.
UPDATE: removing limits on Mac for testing purposes
Created Folder:C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\
Downloading Updates
Downloading http://android-casual.googlecode.co...IPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\/SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.scr
... Update Sucessful! MD5s verified!
Associated Script WindowsLinux Galaxy Note 2 Jailbreak with #0WindowsLinux Galaxy Note 2 Jailbreak
Script WindowsLinux Galaxy Note 2 Jailbreak returned #0WindowsLinux Galaxy Note 2 Jailbreak
Selected fileC:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\SCRIPTS\WindowsLinux Galaxy Note 2 Jailbreak
Lines in Script 65
Reading [email protected]
new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
COMMAND processed - C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe Are you sure?, This is your only warning.
You will be Unlocked and Rooted. Your device will
reboot once and then again into Odin mode. CASUAL
will then flash the Back Atcha Verizon Odin Bootloader
package for you.
new command: $ECHO Rebooting into download mode
SCRIPT COMMAND:$ECHO Rebooting into download mode
Received ECHO command$ECHO Rebooting into download mode
Rebooting into download mode
new command:
new command:
new command:
new command: $ADB reboot download
SCRIPT COMMAND:$ADB reboot download
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
return from ADB:
new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\libusb-1.0.dll
File verified.
Attempting to write C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe
File verified.
detected!
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
WindowsLinux Galaxy Note 2 Jailbreak.scrWaiting for Downoad Mode device.Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Installing drivers
Driver Problems suck. Lemme make it easy.
1. Check that your device is download mode and connected up.
2. Select the one that says ---Gadget Serial--- in the main window
3. Click ---install driver---.
4. Close out zadig and use CASUAL.Note: the USB port which you install this driver will be converted
to use Heimdall instead of Odin for download mode. It only affects
ONE usb port.
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.exe
To: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\zadig.exe
Downloading https://android-casual.googlecode.com/svn/trunk/repo/zadig.ini
To: zadig.ini
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\Elevate.exe###
###executing real-time command: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\heimdall.exe###
ERROR: Failed to access device. libusb error: -12Open-Source Heimdall DriversOpen-Source Heimdall Drivers configHeimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Releasing device interface...
ERROR: Protocol initialisation failed!
new command:
new command:
new command: $ECHO Your device should be rebooting into Android now.
SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
Received ECHO command$ECHO Your device should be rebooting into Android now.
Your device should be rebooting into Android now.
new command: $ADB wait-for-device
SCRIPT COMMAND:$ADB wait-for-device
sending
###executing: C:\Users\brandi\AppData\Local\Temp\BrandiTEMPCASUALDBF457A7\adb.exe###
Code:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
He's said xp isn't supported. That's why it isn't working. Try to find a more up to date computer
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
brandi1693 said:
Please, please send log again, this wasn't done on an xp machine this was done on windows 7 64 bit. I originally tried it on an xp machine at home and it didn't do anything it just stayed on the download screen so I took it to work and ran it on windows 7 64 bit and it still wouldn't work but did go a lot further and produced this log. I typed that by mistake. Thank you for your help
Click to expand...
Click to collapse
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
You know you can pm him
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
No I didn't know, I have lurked around xda for years now but never posted or responded. How do I pm him?
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Bfitz26 said:
find his thread for his jailbreaking procedure click on his name then there should be a option to message him simple bud
Click to expand...
Click to collapse
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
brandi1693 said:
Thank you everyone for your help, I finally got the bootloader unlocked. No need to send the log to Adam
Click to expand...
Click to collapse
I'm having trouble with Casual as well, it reboots my phone into download then hangs. I don't even get a chance for errors to happen! I thought it was my drivers at first, but everything is loaded just fine. Does anyone else have this problem? I'm on a WIN7 64bit, going to try linux tonight when I get off of work.
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
randy6675 said:
I am very interested in whether Linux works for you. Please post your results. Thank you!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ubuntu worked just fine, but when I flashed a rom in twrp I got the triangle, so maybe it didnt work correctly.
Unfortunately, I have to go in early so I cant mess with it again until tomorrow, just restored back to stock and updating all my apps.

CASUAL problem - protocol initilisation failed

Yes, I am a noob, at this forum at least. Yes I watched the noob video, no I did not call my mother. I have however made several searches for this problem and all return "sorry no matches" so apologies ahead of time if it does exist somewhere, but I do appreciate everyone's time.
I have rooted several Droid X's, so I am not completely illiterate. Couple weeks ago I got a Verizon Galaxy Note 2 and am attempting to root it using CASUAL. Phone is running VRALL4 current OTA, and bone stock. Using USB cable that came with phone (phone was brand new in sealed box).
Problem:
CASUAL connects to phone and hangs at "Protocol initilisation failed" and "Phone should be rebooting into Android now"
Phone does not reboot into Android, just sat on green Android "download mode do not turn off target screen". I let it sit for quite some time, nothing more from phone or CASUAL, so I bravely unplugged cable, pulled battery, and phone rebooted normally into Android, working flawlessly. Thoughts? Log is below
[INFO]We are running Windows Vista
Creating Temp Folder in:C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\CASUAL Cross-platform Android Scripting and Unified Auxiliary Loader
Revision:416 build:3205
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\Me%20and%20My%20Angel\Desktop\BackAtchaVerizon-CASUAL-Revision417b.jar --license'
for details. for source.
[DEBUG]Found Windows Computer
[DEBUG]Picking Jar File:/C:/Users/Me%20and%20My%20Angel/Desktop/BackAtchaVerizon-CASUAL-Revision417b.jar
[DEBUG]Found: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\Elevate.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\adb.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\AdbWinApi.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\AdbWinUsbApi.dll
[DEBUG]File verified.
[DEBUG]sleeping for Windows ADB start
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\adb_usb.ini
[DEBUG]File verified.
[DEBUG]
###executing: C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\adb.exe###
[ERROR]List of devices attached
[DEBUG]unknown
[DEBUG]Device List:
[DEBUG]unknown
[DEBUG]Control Change requested but Statics.MasterLock is set.
[DEBUG]OMFGWOOT GUI running!
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2.
[DEBUG]Searching for scripts
[DEBUG]Updating Scripts for UI
[INFO]From Resource: true
[INFO]--WindowsLinux Galaxy Note 2 Jailbreak--
[INFO]This is a tool which will root, unlock, and install a custom recovery on a Verizon Galaxy Note 2. Put your device into ADB mode. Credit for this exploit goes to Lee Harrison
[DEBUG]Created zipResource at /SCRIPTS/WindowsLinux Galaxy Note 2 Jailbreak.zip
[DEBUG]Exiting comboBoxUpdate()
[DEBUG]attempted to lock controls but controls are not availble yet
[DEBUG]Extracting archive....
[DEBUG]Target Script Is resource
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]State Connected
[DEBUG]Controls Enabled status: true
[DEBUG]State Change Detected, The new state is: 0
[DEBUG]State Disconnected
[DEBUG]Controls Enabled status: false
[DEBUG]State Change Detected, The new state is: 1
[DEBUG]State Connected
[DEBUG]Controls Enabled status: true
[ERROR]
[DEBUG]StartButtonActionPerformed() Script Activated
[DEBUG]Script known as WindowsLinux Galaxy Note 2 Jailbreak is running
[DEBUG]Controls Enabled status: false
[DEBUG]disk location for script resources
[DEBUG]Loading internal resource: WindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Selected resourceWindowsLinux Galaxy Note 2 Jailbreak
[DEBUG]Lines in Script 65
[DEBUG]Executing Scripted [email protected]
[DEBUG]CASUAL has initiated a multithreaded execution environment
[DEBUG]***WEB VERSION***
IDString:null
SVNRevision:null
ScriptRevision:null
supportURL:nullupdateMessagenull
[DEBUG]Reading [email protected]
[DEBUG]new command: $USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
[DEBUG]SCRIPT COMMAND:$USERCANCELOPTION Are you sure?, This is your only warning.\n You will be Unlocked and Rooted. Your device will\n reboot once and then again into Odin mode. CASUAL\n will then flash the Back Atcha Verizon Odin Bootloader\n package for you.
[DEBUG]new command: $ECHO Rebooting into download mode
[DEBUG]SCRIPT COMMAND:$ECHO Rebooting into download mode
[DEBUG]Received ECHO command$ECHO Rebooting into download mode
[INFO]Rebooting into download mode
[DEBUG]new command: $ADB reboot download
[DEBUG]SCRIPT COMMAND:$ADB reboot download
[DEBUG]sending
[DEBUG]
###executing real-time command: C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\adb.exe###
[DEBUG]
[DEBUG]return from ADB:
[DEBUG]new command: $HEIMDALL flash --8 "$ZIPFILEboot.img"
[DEBUG]SCRIPT COMMAND:$HEIMDALL flash --8 "$ZIPFILEboot.img"
[DEBUG]Expanded $ZIPFILE: $HEIMDALL flash --8 "C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\libusb-1.0.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\heimdall.exe
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\msvcp110.dll
[DEBUG]File verified.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\msvcr110.dll
[DEBUG]File verified.
[VERBOSE]detected!
[VERBOSE]Performing standard Heimdall commandflash --8 "C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\WindowsLinux Galaxy Note 2 Jailbreak\boot.img"
[DEBUG]
###executing real-time command: C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\heimdall.exe###
Waiting for Downoad Mode device...Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
[DEBUG]Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
[ERROR]
Installing drivers
[VERBOSE]Driver Problems suck. Lemme make it easy.
We're going to install drivers now. Lets do it.
[DEBUG]Attempting to write C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\CADI.exe
[DEBUG]File verified.
[DEBUG]
###executing: cmd.exe###
[ERROR]null
[INFO]
[DEBUG]
###executing real-time command: C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\heimdall.exe###
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
[DEBUG]Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
[DEBUG]new command: $ECHO Your device should be rebooting into Android now.
[DEBUG]SCRIPT COMMAND:$ECHO Your device should be rebooting into Android now.
[DEBUG]Received ECHO command$ECHO Your device should be rebooting into Android now.
[INFO]Your device should be rebooting into Android now.
[DEBUG]new command: $ADB wait-for-device
[DEBUG]SCRIPT COMMAND:$ADB wait-for-device
[DEBUG]sending
[DEBUG]
###executing real-time command: C:\Users\MEANDM~1\AppData\Local\Temp\Me and My AngelTEMPCASUALEDB226DC\adb.exe###.
are you using the BackAtchaVerizon-CASUAL-Revision417b as i wasnt and i was having the same problems as you are I just got it installed with it. Here is the link http://forum.xda-developers.com/showthread.php?t=2118348
Yes I was using the current version of CASUAL...417b
Try a different sub cable. I had the same issue. Switched cables an went through smooth as silk.....
Noel
Sent using TapaTalk on my KFHD
ok might try that. I was a little leary of rooting this time around so this has not exactly instilled me with a lot of confidence...I dont have time or the patience this time to try to bring a phone back from the dead and my Droid X was on its last leg lol

Install Android on I9300_TIZEN device

Hi all,
I own one i9300_TIZEN phone thanks to a Tizen event, and since I've saw what Tizen OS looks like (no comment), I'm really interesting in flashing Android on the device. Before coming in the forum and asking question, I previously made researchs and try some things.
So first I tried heimdall in order to directly flash a recovery (i hoped it will be as easy) but it gives the following output :
Code:
[email protected] ~/Desktop $ sudo heimdall flash -RECOVERY recovery-clockwork-touch-6.0.3.1-i9300.img --verbose --stdout-errors --no-reboot
[sudo] password for padawan:
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "SLP"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.00
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.FF
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: -1089611880
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -1089611880
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -1089611880
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -1089611880
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -1089611880
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -1089611880
ERROR: Failed to send data: "ODIN"
ERROR: Failed to send data: "�"
Releasing device interface...
It seems that the device is just not recognize by the tools, and I don't know how to solve this issue.
So for the moment I don't really know how to proceed. I know that first I may have to do a dump of my device in order to reflash it in case of issue. I saw that I may be able to do it thanks to Tizen commands, but I'm not completely sure. Some tizen tools looks very similar to android ones (like sdb with the same functions that adb), but I didn't know if it may be a solution (because tizen commands may do tizen stuff, and that's not what I'm looking for).
It may also be useful for me to know the exact hardware of my device. It may be very close to i9300, but I want to be sure before doing anything.
Another solution may be to flash a I9300 .pit file to "flash" my device, but I never use it before so i don't really understand the real risks of this solution and the process.
So for the moment I don't really know how to proceed, that's why i'm creating this thread.
Thank you,
up
I think there will no further investigation in this case. I'm interested too. But to less people got access to this devices.
So I think we have to wait until the tizen release.
Gesendet vom Handy mit Tapatalk.
Catscratch said:
I think there will no further investigation in this case. I'm interested too. But to less people got access to this devices.
So I think we have to wait until the tizen release.
Gesendet vom Handy mit Tapatalk.
Click to expand...
Click to collapse
I know but my main problem is that I don't know the tools needed to make these investigations. I don't want someone to write a precise tutorial, but I just need some advices to go further in my investigations.
http://www.youtube.com/watch?v=JXvOcGJ6zXo
Maybe in this way...
Untested from Tizen to Android...
Best Regards
Edit 1.
As hint...
Odin Tool for Android receive ODIN as text string for identification from Android handset...
Thor receive THOR from Tizen crap...
I can not try complete... as no Android nor Tizen real handset here in my hands...
Short played with S8500 and SBL Bootloader from Android handsets...
http://forum.xda-developers.com/showpost.php?p=44162575&postcount=12
http://forum.xda-developers.com/showpost.php?p=44188307&postcount=13
Edit 2.
Found this Decrypted:
https://hotfile.com/dl/234791315/5b8c314/GSIII_Recovery_guide_v2.pdf.html?lang=en
I have found this encrypted Doc and files too...
Nascar encrypted files seems often used by Sxmsung...
2.2.1 is released...
Maybe big "surprice"...
http://download.tizen.org/releases/2.2.1/tizen-2.2.1/images/RD-PQ-REF/
No idea why the wifi Version is 1100 MB big...
Best Regards

Cannot use Odin/Heimdall

Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
frangamer18922 said:
Hey everyone, I am trying to flash my SM-G9650 with TWRP but both Odin and Heimdall fail in doing so. I've tried Odin on Windows 10 (with Samsung drivers), Heimdall on Windows 10 (with WinUSB or LibUSBk) and even Heimdall on Manjaro Linux (with libusb) but none work. They all either hang at initialising, during initialising, or just fail with no error (Odin). For instance, Heimdall on Manjaro Linux gives this:
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
And this is what appears on my download mode:
Code:
RPMB fuse blown
RPMB Provisioned
CURRENT BINARY:Samsung Official
OEM LOCK: OFF
REACTIVATION LOCK: OFF
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV : b9(2,2,2,9,2) K9 S9
SECURE DOWNLOAD: ENABLE
DID: 20208B2BEA756311
I've tried the usual, different USB ports, cables, restarting PC, but nothing makes the trick. I even tried to flash the official Samsung firmware, same bit (9) and everything but still, nothing. Both OEM Unlock and USB Debugging are enabled, and I think I don't need to use CROM Service anymore, and if I do I'm in an uncomfortable situation because it doesn't even open on my Android 10 firmware...
Click to expand...
Click to collapse
Did you manage to find out what the problem was? I have a similar situation with a Note 10+. I am starting to suspect that Samsung made it unflashable after certain update, like i've read som devices can be..
And by the way how did you manage to flash official firmware?

Categories

Resources