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.
Tldr: Heimdall cannot detect my galaxy SII on mountain lion when plugged in and set to download mode. I don't have access to a windows PC but i've also tried virtual box running windows 7 with Heimdall and Odin.
Phone: Samsung Galaxy SII (i9100)
Computer: Retina macbook pro (mountain lion)
Software: Heimdall Suite 1.3.2 (Binaries)
Problem: I did a bad firmware update and now i can't boot my phone (not even into recovery mode). I can however, boot into download mode.
My thinking is that i can re-flash clockworkmod recovery using heimdall and then flash a version of cyanogen mod once i can enter recovery mode.
I've installed the Heimdall version above and re-started my macbook. I then open a terminal and try and flash:
Code:
$ heimdall flash --kernel zImage
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
xxxxx
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:
xxxxx
Initialising connection...
Detecting device...
Failed to detect compatible download-mode device.
I've also tried with Sudo and get the same message telling me the device cannot be detected.
The device is plugged in and is visible to OSX (trimmed):
Code:
$ system_profiler SPUSBDataType
USB:
USB 3.0 SuperSpeed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBXHCI
PCI Device ID: 0x1e31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086
Bus Number: 0x14
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x7fcb00001e2d
PCI Revision ID: 0x7fcb00000004
PCI Vendor ID: 0x7fcb00008086
Bus Number: 0x1a
Hub:
Product ID: 0x0024
Vendor ID: 0x8087 (Intel Corporation)
Version: 0.00
Speed: Up to 480 Mb/sec
Location ID: 0x1a100000 / 2
Current Available (mA): 500
Current Required (mA): 0
Gadget Serial:
Product ID: 0x685d
Vendor ID: 0x04e8 (Samsung Electronics Co., Ltd.)
Version: 2.1b
Speed: Up to 480 Mb/sec
Location ID: 0x1a120000 / 4
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
My real question is: Has anyone successfully got heimdall to detect their SII under Mountain Lion? If so, what software versions and processes did you use?
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Yesterday I got a S5830i that I should try to fix. The background story is that the Google Play Services took over aprox. 100 MB (a large amount of device memory), so they were deleted or their updates were. That led the phone to being unresponsive so the battery was removed (that's what I was told). After that the phone keeps reseting ... splash screen, samsung boot animation ... over and over again.
So I checked what could be done. The phone has a stock ROM and it's not rooted. First i've found out that /data cannot be mounted (Error mounting data). Other topics suggested only flashing stock firmware using Odin.
Then I installed drivers on a windows machine, prepaired Odin with pit and a stock firmware. Then I've put the phone into download mode. The problem is ... the phone is not detected in Odin whatsoever ... changing drivers, installing kies ... nothing. Device manager says that the phone is unknow device and no driver helps.
The last attempt was on my linux machine running a ubuntu 14.04 derivate. Using heimdall 1.4.0 I only get Device detected. Using a hemdall frontend I can get it to print pit too ...
Code:
Initialising connection...
Detecting device...
length: 18
device class: 2
S/N: 3
VID:PID: 04E8:685D
bcdDevice: 0001
iMan:iProd:iSer: 2:1:3
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0040
polling interval: 05
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 20
endpoint[1].address: 02
max packet size: 0200
polling interval: 20
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
ERROR: Setting up interface failed!
Releasing device interface...
Re-attaching kernel driver...
And here it stops. I'm always getting error that setting up interface has failed. Just for test I flashed the CWM and some ROM from xda. Everything was invalidated after restart ... stock recovery, error mounting data.
Is there anything I can do? I really tried almost everything.
Update: after reinstallation of all drivers the phone can be flashed. However, after odin flash is complitet, phone reboots and recovery says "cannot mount /data (invalid arguments)" at the multi CSC section. Close but not there yet. What to do?
Hi,
i have an old samsung i9100 (galaxy S2) that i would like to prepare for my 9 yo kid.
i wanted to upgrade ROM to android 7 but it crashed and when phone boots it displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I read a lot of articles and saw several videos about it but nothing work as they said.
Therefore i was thinking to flash a new version of TWRP at first like 3.1.1 but when i do that in ODIN 3.12 it always failed. Phone is normally connected as COM1.
The same issue i have when i try to flash a new rom...it fails on CACHE part.
Someone can help me please ? I already flashed a lot this phone without any issue as 2 other Samsung S5 Neo. So i do not understand what is the problem.
if i try Heimdall i got this error when i run "heimdall print-pit --verbose" command:
Code:
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0040
polling interval: 00
endpoint[1].address: 02
max packet size: 0040
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data: "ODIN"
Releasing device interface...
thx
is there someone on this part of forum ?
Flash Lineage 16 or Carbon 7!
We give children the best things.
Let him learn. When you help your child, he will quickly chase you away.
The message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" means that you have lost the stock ROM system partitions.
You need to flash again the ROM stock you find in the Carbon thread.
With the help of Odin you flash in the download mode.
I have the stock ROM but ODIN still do not send data to mobile. Even a single PIT file worked but did not allow to flash stock ROM
heimdall just show it in command line with "ERROR: Failed to send data: "ODIN"" as error
here it is where it stucks when i upload stock firmware using ODIN 1.85
using ODIN 3.12 is almost the same issue:
i tried in comptibility "Windows XP - SP 2" and also in SP3... running ODIN under administrator
unfortunately, nothing helped so far. any idea ?