[PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.3.0 Available)
- Thread starter Benjamin Dobell
- Start date
Haven't seen this thread get too much attention, but it is a really cool idea especially for non-windows users. Just to kick it off:
Phone Name: Samsung Captivate (JH3 Firmware)
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c
Phone Name: Samsung Captivate (JH3 Firmware)
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c
It would be nice if someone was willing to see if the Captivate works with this app. Having a cross-platform standardized program is a good idea.
Right now there seems so be a number of different ways to achieve a goal. What we need is a standardized app that devs can make "packages" for where we can select what we want and a rom, zip file or whatever could be built on the fly. easy peezy I say.
Right now there seems so be a number of different ways to achieve a goal. What we need is a standardized app that devs can make "packages" for where we can select what we want and a rom, zip file or whatever could be built on the fly. easy peezy I say.
Phone Name: Samsung Captivate (JH2 Firmware)
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c
Country: United States
Carrier: AT&T
Hardware IDs:
USB\Vid_04e8&Pid_681c&Rev_0400
USB\Vid_04e8&Pid_681c
Phone Name: Samsung Captivate I897 (JF6)
Country: USA
Carrier: AT&T
Hardware IDs:
venim@venim:~$ lsusb
Bus 001 Device 027: ID 04e8:681c Samsung Electronics Co., Ltd
seems all of the captivate IDs are 681c, which mirrors the international version.
Country: USA
Carrier: AT&T
Hardware IDs:
venim@venim:~$ lsusb
Bus 001 Device 027: ID 04e8:681c Samsung Electronics Co., Ltd
seems all of the captivate IDs are 681c, which mirrors the international version.
Just to throw in my 2 cents:
I'm a linux user (have windows on dual boot on one machine, but hate going into it just to flash), so I really hope this project moves forward. I'd be willing to test any early linux builds once they're ready.
Phone Name: Samsung Captivate
Country: USA
Carrier: AT&T
Device ID: 04e8:681c Samsung Electronics Co., Ltd
I'm a linux user (have windows on dual boot on one machine, but hate going into it just to flash), so I really hope this project moves forward. I'd be willing to test any early linux builds once they're ready.
Phone Name: Samsung Captivate
Country: USA
Carrier: AT&T
Device ID: 04e8:681c Samsung Electronics Co., Ltd
If we had some documentation for the bml devices, it might be possible to provide a utility that could flash kernels from an update.zip. There its a flashing utility, vmlwrite, for the Moment, and it even runs on Galaxy S, but whatever mechanism it uses to map labels to partitions doesn't work. I've been looking for sources to see if they can be modified for our use, but I haven't found anything yet.
Sent from my SAMSUNG-SGH-I897 using XDA App
Sent from my SAMSUNG-SGH-I897 using XDA App
Just thought I'd drop by and let you all know a stable beta has been released. I've only personally tested with two GT-I9000's (UK and Australian models) so I'm not 100% certain what Galaxy S derivatives will work.
This release includes source code and Windows binaries. It compiles and runs brilliantly on Linux but unfortunately I haven't been able to get phones detected on OS X. If someone else would like to give it a try that would be great.
Please post any questions in the official thread so I can keep track of them.
This release includes source code and Windows binaries. It compiles and runs brilliantly on Linux but unfortunately I haven't been able to get phones detected on OS X. If someone else would like to give it a try that would be great.
Please post any questions in the official thread so I can keep track of them.
USHERROB
Senior Member
---------- FORM ----------
Phone Name: Samsung Captivate i897
Country: USA
Carrier: AT&T
Hardware IDs:
USB\VID_04E8&PID_681C&REV_0400
USB\VID_04E8&PID_681C
Phone Name: Samsung Captivate i897
Country: USA
Carrier: AT&T
Hardware IDs:
USB\VID_04E8&PID_681C&REV_0400
USB\VID_04E8&PID_681C
I have been following and posting on the original thread. Windows 7 and Windows Vista pcs and a captivate-i897.
As i posted, i had a few problems at first,, but successfully used this to flash today. Will continue testing and reporting.
As i posted, i had a few problems at first,, but successfully used this to flash today. Will continue testing and reporting.
Always remember that bad things CAN happen when you mess with the areas this program messes with. Also, bad things can ALSO happen when you aren't VERY careful with beta releases in general. Therefore, if you put those things together, like you are doing with this program, you are doing a dangerous thing. YOU CAN KILL YOUR PHONE!!!
I'm not saying it WILL happen, just that it CAN..... so BE CAREFUL!! Don't be afraid to test, but carefully.....
And yes, I support this program, I just don't wanna see people willy-nilly jumping in and possibly damaging their devices, then saying it's not their fault.
I'm not saying it WILL happen, just that it CAN..... so BE CAREFUL!! Don't be afraid to test, but carefully.....
And yes, I support this program, I just don't wanna see people willy-nilly jumping in and possibly damaging their devices, then saying it's not their fault.
Pulling from my phone directly to make own firmware odin using either Heimdall/odin
Hi, I tried to create this thread.
http://xdaforums.com/showthread.php?p=15695721
The idea is how to make it own firmware after make custom ROM.
I'm still not sure for boot.bin and Sbl.bin if pulling from my phone will cause any problem or not.
Should I use from stock firmware to use your program while flashing?
Can I say Primary boot loader is boot.bin and while secondary boot loader is Sbl.bin?
It seem your program Heimdall will suitable to build package.
But I still having difficulties how to use your program to create a package firmware like stock firmware.
Hi, I tried to create this thread.
http://xdaforums.com/showthread.php?p=15695721
The idea is how to make it own firmware after make custom ROM.
I'm still not sure for boot.bin and Sbl.bin if pulling from my phone will cause any problem or not.
Should I use from stock firmware to use your program while flashing?
Can I say Primary boot loader is boot.bin and while secondary boot loader is Sbl.bin?
It seem your program Heimdall will suitable to build package.
But I still having difficulties how to use your program to create a package firmware like stock firmware.
heimdall saved me awhile back! Phone was really messed up, wouldn't connect to PC, windows didn't reckognize it so I booted up my linux install, downloaded heimdall and boom, phone is working well over a year down the road! Great for those who don't use windows or have problems with USB drivers on win 7
[Q] None Galaxy S Samsung devices?
I get "Server not found" when clicking on the official thread link.
Nonetheless, I have a question: will this work with non-Galaxy S devices? I'd like to try it out on my Samsung Sidekick 4G, which should arrive this week.
I get "Server not found" when clicking on the official thread link.
Nonetheless, I have a question: will this work with non-Galaxy S devices? I'd like to try it out on my Samsung Sidekick 4G, which should arrive this week.
Heimdall Kernel flash unreliable
I seem to have problems using Heimdall 1.3.0 on Mac OS X to flash my phone. I'm just trying to flash a kernel as follows:
But it often times can't find my phone even though it connected in Download Mode. When it does find my phone, it seems to get stuck at Kernel 0%. After that, it seems I need to restart Download Mode on my phone before I can attempt again, after getting stuck at Kernel 0% several times, I finally got it to finish the full flash, but it seems like it shouldn't take so much effort. Is this normal for Download Mode on a Samsung Captivate or might it just be a bad USB cable? I think I have the Gingerbread Captivate bootloaders currently installed, but do other bootloaders work better with Heimdall?
Here is the full log of a failure with Kernel 0%:
I seem to have problems using Heimdall 1.3.0 on Mac OS X to flash my phone. I'm just trying to flash a kernel as follows:
Code:
heimdall flash --kernel zImageBut it often times can't find my phone even though it connected in Download Mode. When it does find my phone, it seems to get stuck at Kernel 0%. After that, it seems I need to restart Download Mode on my phone before I can attempt again, after getting stuck at Kernel 0% several times, I finally got it to finish the full flash, but it seems like it shouldn't take so much effort. Is this normal for Download Mode on a Samsung Captivate or might it just be a bad USB cable? I think I have the Gingerbread Captivate bootloaders currently installed, but do other bootloaders work better with Heimdall?
Here is the full log of a failure with Kernel 0%:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
0%
ERROR: Failed to send file part packet!
KERNEL upload failed!
Ending session...
ERROR: Failed to send end session packet!I seem to have more issues flashing with Heimdall 1.3 then I did flashing with 1.1 as well. Similar issue as the one you're having granted I don't think it's ever failed a flash once Heimdall's seeing my phone...
Are you using heimdall front end 1.3.0, or are you using command line. In the front end version under utilities there is a detect device feature. I always check to insure it sees my phone before I flash. Also what version of OSX are you on, because I'm pretty sure its not compatible with lion just yet
Sent from my SAMSUNG-SGH-I897 using xda premium
Sent from my SAMSUNG-SGH-I897 using xda premium
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2I started a thread on how to make Heimdall One-Clicks here: http://xdaforums.com/showthread.php?t=1348392
Heimdall One-Click is a controlled environment which a single java jar file will deploy everything needed and then flash a Heimdall package on Linux, Windows, or Mac. Everything is automated, several safety features were implemented over Heimdall's integrated safeties and a Heimdall One-Click is a self-contained installer/dependency manger/flashing utility with an overhead of just 20MB over that of a Tar.Gz file.
Heimdall One-Click is not a replacment for Heimdall Frontend. It's just a method to keep flashing easy, compacted to a single file, and cross-platform.
Check out the One-Click packaging utility here: http://xdaforums.com/showthread.php?t=134839211
This problem was fixed by psych0phobia in this thread today: http://xdaforums.com/showpost.php?p=17432044&postcount=10
The changes should be pushed upstream shortly. The problem is that Heimdall was not properly repartitioning.. I've verified that it is working now. If you're able to build from source, you should be able to get things working.1
New posts
-
Allwinner R16 (astar_d7) Android 6.0.1 Marshmallow - Partition Dump & Information- Latest: old.splatterhand
-
-
-