Hi, after some frustrated searches I am stuck with the following situation.
A laggy i9000 with the following rom I9000XXJPM.
Since I am a Mac OS user, I cannot use ODIN (have XP on my bootcamp, but does not see my phone). Yet, I would love to replace the current recovery 3e with 2e so I can install unsigned updates. That way, I can flash new roms through "Rom manager", and even install Voodoo.
Can anyone tell me how?
Help is much appreciated.
I've never used it personally but you can look at Heimdall.
http://forum.xda-developers.com/showthread.php?t=755265
"What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0."
Thanks, I'll give it a try.
I have to give this a try
Related
I only have access to linux computers.
Can I flash a new ROM without winblows?
You do not need windows. Search heimdall, as an odin replacement
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Lhon0901 said:
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Click to expand...
Click to collapse
Uncheck the partition box. Whenever it's grayed out, it means that for one of your options you haven't met the pre-reqs. For example partition requires a PBL, SBL and a recovery file I believe. Error -12 after clicking start refers to a driver issue.
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
btyork said:
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
Click to expand...
Click to collapse
Okay, I'll try the partition part and see if it works, but I beleive it's not checked as I put no file in it... As for the second post, yes, I have found the firmware I need but it's extracted and not in tar form... That's why I need heimdall...
Maybe if somebody can point me on how to compile it to TAR again I'll just use odin...
***Added: I got my hands on a DXKM3 firmware that came with my phone here. Now if someone can help me put those files again in the TAR format I would be very glad... Getting heimdall to work would, too...
Thanks for the replies!!!
You're right!!! I failed to notice that factory.rfs is not yet extracted, and "Start" magically became selectable!!!
I feel kinda stupid... T_T
Was able to flash now... Thanks for the help guys!!!
Hi,
I tried rooting my mother's SGS with the cyanogen wiki guide (using heimdall to flash a zImage)
Unfortunately I got a bit ahead of myself and the zImage was for a froyo rom.
So, the phone no longer boots (I can still get to recovery and download mode)
But I cannot find a stock zImage to flash back onto the phone,
so if anyone has one or knows where I may acquire one, it would be much appreciated.
-Nipqer
Download a new ROM from www.samfirmware.com
Use a Windows PC and not a Mac. They're much more reliable, i feel.
Managed to use a custom eclair kernel to get it working again.
Used this kernel
-Nipqer
Hello xda!
So, after months of running Dlev's v5.0 ROM I figured its time for a change so I thought to give Apex 12.2 a shot but, while following the provided guide I got (sadly) stuck in step:
"Heimdall or ClockworkMod?
Are you already running an I9000 based ROM with ClockworkMod recovery version 3 or higher? If so, you may choose to install the kernel/modem package through CWM rather than Heimdall."
Thing is, I've never had to use Heimdall before (Odin has worked for me in the past just great) so I cant for the life of me get it to work: I put my phone succesfully in Download mode, then then i click on "Start" it gives me an "libusb error -12".
I've tried using other computers, switching USB ports, other operating systems, lots of drivers.. rebooting between each driver install, power-cycling both my captivate and pc.. Is there something wrong with my download mode/captivate?
(When powered on, i can correctly mount and read files from my sdcard on any computer, i can also mount the sdcard while on recovery, adb works just fine too)
I figured since the Dlev rom uses a i9000 JVQ firmware (2.3.4), and it comes with DarkCore Recovery v3.0.2.8x I could get away with using CWM rather than Heimdall?
Extra:
About phone info:
Baseband: I9000UGKC1
Kernel: 2.6.35.7-I9000XXJVR-CL425308
Any other info you may need, ask away!
Many thanks in advance
Alex.
seed_87 said:
"Heimdall or ClockworkMod?
Are you already running an I9000 based ROM with ClockworkMod recovery version 3 or higher? If so, you may choose to install the kernel/modem package through CWM rather than Heimdall."
I figured since the Dlev rom uses a i9000 JVQ firmware (2.3.4), and it comes with DarkCore Recovery v3.0.2.8x I could get away with using CWM rather than Heimdall?
Click to expand...
Click to collapse
You're answer is right there.... Use cwm.
The heimdall flash if for if you're NOT on an I9000 ROM. So it can flash the proper bootloaders, which you have already.
Thanx studacris, now running Apex 12.2
Alex.
Hello, today I wanted to try putting Cyanogenmod on my phone. I tried following this guide:
Installing the ClockworkMod Recovery
This guide assumes the Samsung Galaxy S already has Android 2.3 or higher installed on it. If the Samsung Galaxy S already has the ClockworkMod Recovery installed, skip this section.
WARNING: INSTALLING A CUSTOM RECOVERY IMAGE ON THE SAMSUNG GALAXY S WILL VOID THE WARRANTY.
Download hardcore's kernel with the ClockworkMod Recovery and the Heimdall Suite:
hardcore's Kernel with the ClockworkMod Recovery 2.5: Download
md5: be7f5e02254c9c3fa91d1067f815dac1
Windows:
Heimdall Suite 1.3.2: Download
NOTE: The Heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
Heimdall Suite 1.3.2 Command-line Binary: Download
Ubuntu 64bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
Heimdall Suite 1.3.2: Download
NOTE: The source code for the Heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Run the included zadig.exe in the drivers folder of the Heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
Heimdall can now be used safely on the Windows computer.
NOTE: For more information about the Heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar hardcore's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S now has the ClockworkMod Recovery installed. Continue to the next section.
Click to expand...
Click to collapse
Everything went well, until the last step:
A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S now has the ClockworkMod Recovery installed. Continue to the next section.
The blue transfer bar did appear, and the phone rebooted. However now it's stuck in a reboot loop. And I have no idea how to fix it again. I tried going back into download mode (which I can still do), but I have no idea where to go from there...
Can anyone tell me how I fix my phone?
Sorry for the doublepost/unnecessary thread.
But, I managed to get it working again. I followed the same steps as in the guide but this time, I used this
Code:
XXJW4/XXJW4/OXAJW4/Sbl (MultiCSC): Download (140 MB) (Build date: Mon Mar 19 20:51:30 KST 2012)
(MultiCSC: CPW, DBT, KOR, XEO, XEU)
Which can be found http://forum.xda-developers.com/showthread.php?t=1102881]here.
So if anyone ever stumbes across the same issue, I guess this is how you fix it again.
If you want to get out of the bootloop you just need to flash the odin version of semaphore kernel, pull battery, go into CWM and reflash CM9.
beardedwonder said:
If you want to get out of the bootloop you just need to flash the odin version of semaphore kernel, pull battery, go into CWM and reflash CM9.
Click to expand...
Click to collapse
Sorry, I have no idea what that means. I'm completely new to this community.
Justin9826 said:
Sorry, I have no idea what that means. I'm completely new to this community.
Click to expand...
Click to collapse
Well it would be worth finding out in case you ever get bootloops again.
It's good to flash rom while having a kernel in separate file as well. If you are having a bootloop after flashing a new rom, simply switch off (take battery out if needed), boot into recovery witch 3 button combo and reflash the kernel only. This helped in my case. If you have no separate kernel try flashing the rom itself once again.
...
Justin9826 said:
Sorry for the doublepost/unnecessary thread.
But, I managed to get it working again. I followed the same steps as in the guide but this time, I used this
Code:
XXJW4/XXJW4/OXAJW4/Sbl (MultiCSC): Download (140 MB) (Build date: Mon Mar 19 20:51:30 KST 2012)
(MultiCSC: CPW, DBT, KOR, XEO, XEU)
Which can be found http://forum.xda-developers.com/showthread.php?t=1102881]here.
So if anyone ever stumbes across the same issue, I guess this is how you fix it again.
Click to expand...
Click to collapse
Hey did you have the BELL galaxy S gt i9000m and what android were you running before 2.3.3?