[Q] Anybody used Heimdall yet on SGS2?

[bilboa1]

ok ok i changed it
just forgot about it

 

[elban]

ok ok i changed it
just forgot about it

could you please update the binary?
many thanks!

 

[bilboa1]

could you please update the binary?
many thanks!

the binary works fine

 

[peadarog]

I thought I should add in my progress so far for anybody else suffering from a non-working linux heimdall install.

I recompiled the program following aliander's suggestion (on the page before this one), and this time, when I ran the command:

$ heimdall close-pc-screen

the phone was recognized and I got the following output:

Claiming interface... Failed. Attempting to detach driver...
Claiming interface again... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success

Attempting to close connect to pc screen...
Ending session...
Failed to receive session end confirmation!
Re-attaching kernel driver...

After that, I tried flashing a kernel (yes, I am that stupid ) and got:


Claiming interface... Success
Setting up interface... Failed!


So, I'm back to using Odin on vbox for the moment. Thanks everybody for all of your help.

 

[perljedi]

Droid Charge

Hi Guys,

I'm trying to flash my droid charge (verizon) using heimfall in Fedora 14 x86_64. I have not been able to get past "Failed to detect compatible device", so I started today to muck iwth the heimdall source code to see what I could find. In the init method on BridgeManager.cpp I added a little bit of debuging:

   printf("Found %d devices\n", deviceCount);
   for (int deviceIndex = 0; deviceIndex < deviceCount; deviceIndex++)
   {
      libusb_device_descriptor descriptor;
      libusb_get_device_descriptor(devices[deviceIndex], &descriptor);
      printf("Examining device %d:%d\n", descriptor.idVendor, descriptor.idProduct);

      for (int i = 0; i < BridgeManager::kSupportedDeviceCount; i++)
      {
         printf("Checking against %d:%d\n", supportedDevices[i].vendorId, supportedDevices[i].productId);

Which gave me:

Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
# URL REMOVED

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:
#URL REMOVED 

Found 8 devices
# 14 IRRELIVANT LINES REMOVED HERE
Examining device 1256:26819
Checking against 1256:26113
Failed to detect compatible device

Base on that, I believe that by updating BridgeManager.cpp and BridgeManager.h which the product id from the above debug output, I will be able to get past this. Before I do so, however, I'd love it if somebody could validate my educated guess, and/or warn me if there is something elese that would need to be done to make it work. Is there code elsewhere in heimdall that needs to be update with information like where on the device to place the files being flashed?

I know there is inherent risk in rooting my phone this way, and I'm ok with that... but I feel like modifying somebody else's code (particularly when I'm modifying to to essentially bypass a safety check) without some inklinking that I've understood the situation correctly might be a bit much.

Thanks for your help.

 

[elban]

the binary works fine

yes i know, i've already used it with success, but it doesn't include the latest source patch (I've checked it against the one I had and it looks identical).
I'd compile it myself but I'm at work

 

[Benjamin Dobell]

Official support is coming, details here.

Any donations you can offer would be very much appreciated.

 

[Benjamin Dobell]

New Heimdall command line binaries are now available, let me know how you go.

 

[perljedi]

Thanks

New Heimdall command line binaries are LINK REMOVED, let me know how you go.

Thank you.

I did actually flash my phone yesterday (having compiled from source from your git hub repo). It (my phone) runs 100% smoother now.

 

[bilboa1]

yes i know, i've already used it with success, but it doesn't include the latest source patch (I've checked it against the one I had and it looks identical).
I'd compile it myself but I'm at work

just cosmetics anyhow, also, theres the official plz-donate-and-i-wont-thx-ppl version as well
on a side note heimdall should prolly fill the kernel storage area with 0's to fill it up completely to avoid issues on the sgs2

 

[endrec]

Heimdall 1.2 + SGS2 on Ubuntu 11.04

New Heimdall command line binaries are now available, let me know how you go.

Hi Ben,

I tried your software without any success.
It does not recognise my SGS2 (I put it into download mode).

My config:
SGS2 with provider firmware (H3G UK, XWKE1)
Ubuntu 11.04
Heimdall compiled from source (35cfa39)

When the phone is in upload mode, lsusb does not list it, otherwise it is listed as:
04e8:685e Samsung Electronics Co., Ltd

Can you tell me what did Iwrong?

Thanks,

Endre

 

[endrec]

Hmm... I had to find my original Samsung USB cable, and it did the magic. Now it works better. I've just flashed CWM recovery.

Thanks for the tool!

 

[ngoonee]

EDIT: I tried rebooting the phone to download mode again and running flash immediately rather than print-pit or close-pc-screen, and it worked. Would this be a bug?

Below this line is the original post for context:-
________________________________________________

Just built heimdall from git today, and I get this

heimdall flash --kernel zImage --verbose

Heimdall v1.2.0, Copyright (c) 2010-2011, 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:


length: 18
device class: 2
S/N: 0
VIDID: 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: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00

Claiming interface... Success
Setting up interface... Failed!

Any help, please? I'm in download mode, it says 'Custom Binary Download: NO though. Current Binary is SAMSUNG OFFICIAL.

 

[MrZammler]

Hi,

just to let you know I installed a CF-Root on my SGS2 with the heimdall command line utility.

Thanks a lot!

 

[jakobvoss]

Heimdall 1.3.0 on Ubuntu works so well, that I cut successfully brick my SGS2 by trying to flash the wrong firmware Download screen still works and I like Heimdall, but if anyone could provide a Heimdall firmware package file with original Stock firmware, it would be better. With easy to find firmware packages for SGS2, you could easily get back the original state after playing around with different firmware. Is there any registry of heimdall firmware package files for SGS2 and other devices?

 

[interslicer]

Heimdall 1.3.0 on Ubuntu works so well, that I cut successfully brick my SGS2 by trying to flash the wrong firmware Download screen still works and I like Heimdall, but if anyone could provide a Heimdall firmware package file with original Stock firmware, it would be better. With easy to find firmware packages for SGS2, you could easily get back the original state after playing around with different firmware. Is there any registry of heimdall firmware package files for SGS2 and other devices?

I agree with this guy - i need some stock packages to use with Heimdal! it's been 2 or 3 yrs .. why no support?

 

[centuriondan]

I think I've managed to soft brick my sgs2 using command line heimdall :-(

*** Update **** - I managed to partially unbrick my SGS2 using CWM (once I confirmed it was safe from the superbrick bug) by restoring the wanamlite firmware that was last installed. After that I even used cwm to restore back to the previous setup where my initial problem occured. Now back to fixing that.
**************

Upshot is that i can't seem to flash a kernel now.

Any advice on where to from here. (All the advice I see seems Odin oriented and talks about PDA and such like unexplained acronyms that don't seem to have much relevance in heimdall).

I'm running linux exclusively so Odin's pretty much out of the question.

Phone details:
SGS2 GT-i9100
Last running firmware installed was GT-I9100_WanamLite.XXLPQ.Deodexed.Stock.NO-WIPE.zip
I was trying to downgrade to the original Gingerbread rom when this happened.
CWM recovery v5.0.2.7 installed and still accessible, but not sure if it's likely to cause the superbrick bug as my emmc firmware version matches those that are at risk.

I have a usb jig and can get to download mode OK. Everything flashes ok except the kernel.



The details of the failure follow....

ezra:/home/centurion/Documents/Samsung SII/stock # heimdall flash --kernel zImage --verbose
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
//deleted url//
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:

//deleted url//

Initialising connection...
Detecting device...
           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

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: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
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...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Uploading KERNEL
0%KERNEL upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...

Any guidance or direction to more relevant thread would be appreciated.