[Q] Heimdall cannot detect device on Mountain Lion - Galaxy S II Q&A, Help & Troubleshooting

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?

Related

[Q] Has anyone managed to connect their S2 via MTP using Ubuntu?

Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Q] adb devices (Ubuntu) does not show device after upgrade to ICS

Hi!
I got OTA update to ICS today, and everything went smooth. The phone is working fine. I connect it to iMac, run adb devices, and there is see my device. I'm also using vmware fusion with Ubuntu, where I develop Android apps. Ubuntu does not see this device. Previously, it worked fine. Yes, the device is connected and configured to be available to guest machine.
dmesg and lsusb output follows:
[email protected]:~$ lsusb
Bus 002 Device 005: ID 0e0f:0008 VMware, Inc.
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ dmesg
[ 3751.650501] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3763.141707] usb 1-1: new high speed USB device using ehci_hcd and address 46
[ 3778.252927] hub 1-0:1.0: unable to enumerate USB device on port 1
[ 3778.936251] usb 1-1: new high speed USB device using ehci_hcd and address 47
[ 3794.048386] hub 1-0:1.0: unable to enumerate USB device on port 1
Does anybody know what is going on?
Thanks!
Regards,
Miha.
Am I the only one having this problem? Any other Ubuntu users with Galaxy S2 and ICS update?
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
bored_stupid said:
On the phone. Go to setttings/Wireless and networks/USB utilities/connect storage to PC.
Click to expand...
Click to collapse
This disables USB debugging. I did it anyway, but it still does not show up. Unfortunately.
I solved this by editing Ubuntu.vmx file. I added the following lines (I believe the last line makes a difference):
Code:
usb.quirks.device0 = "0x4e8:0x681d skip-reset" # Mass Storage
usb.quirks.device1 = "0x4e8:0x68a9 skip-reset" # Media
usb.quirks.device2 = "0x4e8:0x6877 skip-reset" # Kies
usb.quirks.device3 = "0x4e8:0x6866 skip-reset" # SGS2 ICS

[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.

Connecting to i5500 using adb and fastboot on Linux

I am trying to resurrect my old Samsung Galaxy i5500. A couple of years ago I tried installing some custom rom but failed and bricked the phone. The boot process halts at the Samsung logo (the very first logo to appear.)
Putting the phone into recovery mode (using the volume down button + center button + power button) works, at least i presume that it works - the logo with the android shoveling dirt and the word "Downloading..." beneath it appears - but neither adb nor fastboot can see the device.
My troubleshooting so far:
Code:
[email protected]:~# dmesg
...
[823736.755555] usb 2-1.1: new high-speed USB device number 6 using ehci-pci
[823736.851772] usb 2-1.1: unable to get BOS descriptor
[823736.857819] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=6601
[823736.857829] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[823736.857835] usb 2-1.1: Product: MSM7x27
[823736.857839] usb 2-1.1: Manufacturer: Sasmsung
[823739.903177] cdc_acm 2-1.1:2.0: ttyACM0: USB ACM device
[823739.903553] usbcore: registered new interface driver cdc_acm
[823739.903557] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[823761.102222] cdc_acm 2-1.1:2.0: failed to set dtr/rts
[email protected]:~# lsusb
...
Bus 002 Device 011: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
...
[email protected]:~# adb devices
List of devices attached
[email protected]:~# fastboot devices
[email protected]:~#
I am running Lubuntu 12.04 on my laptop.
What do I need to do to be able to connect to the phone using adb and fastboot?
Thanks!
The "recovery mode" that you mentioned, is actually download mode and it's used to flash packages with Odin.
Use it to flash a custom recovery and then use that to flash a custom ROM. Format /system and /data as ext4 before flashing the ROM.
Sent from my LG G2 Mini using XDA Labs

Vivo 1901 SP Flash Tools ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142)

Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar

Categories

Resources