Database Users

[Q] Any Mac users get DK17 modem to flash?

I've been messing around with heimdall all day and can't get it to recognize the device.

If you plan on flashing a lot just get bootcamp and use windows. Makes things a lot easier.

ragnarokx said:
If you plan on flashing a lot just get bootcamp and use windows. Makes things a lot easier.
Click to expand...
Click to collapse
Exactly. Not worth the time (or risk) fooling around in OSX. Just grab an old XP disc and run bootcamp.

Thanks for the advice. I have a windows laptop too, but I'd really like to get it working on the mac. Maybe it's just the sadist in me, but if it can work it should. Kind of what this whole forum is about isn't it?

Even in bootcamp I could not get the modem to flash on my Mac. Had to go to a true blue windows machine.

i got odin to read using 1.1 of noobnl's odin in parallels, but after that ive had nothing. ive had to bootcamp in win 7 to get it to read. using a black macbook model 4,1.

brianbrain said:
Exactly. Not worth the time (or risk) fooling around in OSX. Just grab an old XP disc and run bootcamp.
Click to expand...
Click to collapse
Since this isn't an option for some of us. Does anyone have another idea of how to get DK17 Modem on my Epic without Odin?

plainbrad said:
Since this isn't an option for some of us. Does anyone have another idea of how to get DK17 Modem on my Epic without Odin?
Click to expand...
Click to collapse
Unfortunately, it isn't possible at the moment. I have the same problem, so I used a very old, barely functional Windows machine.

tru2life said:
Even in bootcamp I could not get the modem to flash on my Mac. Had to go to a true blue windows machine.
Click to expand...
Click to collapse
I use Window 7 on my Macbook Pro and out flashes fine.
Sent by a little green robot

odub303 said:
Unfortunately, it isn't possible at the moment. I have the same problem, so I used a very old, barely functional Windows machine.
Click to expand...
Click to collapse
That is unfortunate. And I assume no one here has the resources to bake the modem into their rom?

plainbrad said:
That is unfortunate. And I assume no one here has the resources to bake the modem into their rom?
Click to expand...
Click to collapse
That's precisely why we have to flash with Odin. The current modem is not installable from anything on the phone side that we currently have available.

Heimdall
Has anybody been able to get their epic to be detected by heimdall?
Apparently there is a secondary boot loader installed with newer versions of Froyo that allows Galaxy S phones to be sen by heimdall on a mac.

jsnryn said:
Has anybody been able to get their epic to be detected by heimdall?
Apparently there is a secondary boot loader installed with newer versions of Froyo that allows Galaxy S phones to be sen by heimdall on a mac.
Click to expand...
Click to collapse
I could not get Heimdall to recognize that my device was connected to my MBP. I was able to use adb, but not Heimdall.

jsnryn said:
Has anybody been able to get their epic to be detected by heimdall?
Apparently there is a secondary boot loader installed with newer versions of Froyo that allows Galaxy S phones to be sen by heimdall on a mac.
Click to expand...
Click to collapse
Here's the update on the Heimdall site:
Although Heimdall runs on OS X all Galaxy S phones tested thus far contain a bug in the secondary boot loader that prevents the phone registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Update: Samsung have released an updated secondary bootloader that corrects the issue. The correct bootloader is included in the official Froyo release. Obviously you have to get Froyo on your device somehow, but from then on it’s smooth sailing.
Note: Keep in mind if the version of Froyo you’re running is not official then the updated Sbl.bin may not have been included.
To test what we've got, I flashed the "[Stock Flash][Odin]DK17 Extended 11/18/2010 w/Camera Fix" on my Windoze 7 machine using the included Odin and files. Then I booted the Epic into downloading mode, plugged it into my macbook pro, opened a terminal window, navigated to the heimdall directory (where I had another flashable rom's files waiting) and entered
./heimdall flash --pit epicpit.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata datafs.rfs --boot boot.bin --secondary sbl.bin --param param.lfs --kernel zimage --modem modem.bin
Heimdall didn't recognize the device. I had thought that the Odin-flashed DK17 stock update would have the 'updated' bootloader so that this might work, but no joy.
1) Was my process or execution flawed (my linux shell knowledge is limited)? Or,
2) Maybe the secondary bootloader isn't the problem (but that's a whole 'nother can of worms), or
3) Perhaps this [stock]DK17 release did not have the 'new' secondary bootloader - if so, then
[REQ] Official Froyo Secondary Bootloader sbl.bin Please! ​
And finally
4) The OP's Q, still unanswered: Has anyone under any circumstances (excepting using another OS) been able to flash an Epic with Heimdall on a Mac?

bilestoad said:
Here's the update on the Heimdall site:
Although Heimdall runs on OS X all Galaxy S phones tested thus far contain a bug in the secondary boot loader that prevents the phone registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Update: Samsung have released an updated secondary bootloader that corrects the issue. The correct bootloader is included in the official Froyo release. Obviously you have to get Froyo on your device somehow, but from then on it’s smooth sailing.
Note: Keep in mind if the version of Froyo you’re running is not official then the updated Sbl.bin may not have been included.
To test what we've got, I flashed the "[Stock Flash][Odin]DK17 Extended 11/18/2010 w/Camera Fix" on my Windoze 7 machine using the included Odin and files. Then I booted the Epic into downloading mode, plugged it into my macbook pro, opened a terminal window, navigated to the heimdall directory (where I had another flashable rom's files waiting) and entered
./heimdall flash --pit epicpit.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata datafs.rfs --boot boot.bin --secondary sbl.bin --param param.lfs --kernel zimage --modem modem.bin
Heimdall didn't recognize the device. I had thought that the Odin-flashed DK17 stock update would have the 'updated' bootloader so that this might work, but no joy.
1) Was my process or execution flawed (my linux shell knowledge is limited)? Or,
2) Maybe the secondary bootloader isn't the problem (but that's a whole 'nother can of worms), or
3) Perhaps this [stock]DK17 release did not have the 'new' secondary bootloader - if so, then
[REQ] Official Froyo Secondary Bootloader sbl.bin Please! ​
And finally
4) The OP's Q, still unanswered: Has anyone under any circumstances (excepting using another OS) been able to flash an Epic with Heimdall on a Mac?
Click to expand...
Click to collapse
Ben the developer tells me that " Samsung initially told me that all official Froyo releases contain the fixed bootloader, although recently I've found this not to be the case." So, uh, I guess we're stuck with finding windows machines for a bit.

odin problem (driver not successfully installed)

i can get download mode on the phone, but both my computers (both win 7 64bit) say "device driver software was not successfully installed". but the samsung drivers are installed on both computers (i've used adb on both computers). so odin doesn't recognize the phone on either comp... and i don't see a linux friendly version (cause of course drivers always work better in linux).
and i stupidly (read: drunkedly, and yeah, still drunk posting this) forgot to disable voodoo before flashing another (non voodoo) rom ironically trying to show a new iphone owner (who still has an incredible) how safe flashing android roms is... lol..
and for the record i tried searching, but search on xda has been down for 30+ min...

Try Heimdall if you are having problems with Odin
I have a thread on the latest 1.1 version of Heimdall
It has a linux version as well

oka1 said:
Try Heimdall if you are having problems with Odin
I have a thread on the latest 1.1 version of Heimdall
It has a linux version as well
Click to expand...
Click to collapse
link please? i tried looking at heimdall, but search is broken (and i can't look through your previous posts because it gives the same search error).

got heimdall to work. thanks.
the vibrant lives again.
*edit*
i'm a liar... i can get to recovery but flashing any rom fails... i have bionix v 1.2 (wipe) and edt 2.2.1 on my sd and both fail. when i get to recovery i get:
E:Can't mount /dev/block/st111 (Invalid argument)
errors (three of them)
*edit**edit*
lulz.... didn't have the cache/dbdata/and modem fields.
IT'S ALIVE!!
=p
*edit**edit**edit*
it's great it's taken me 8+ months(?) to finally have to figure this out. thank you devs for making it so hard that i had to be drunk trying to flash an alpha rom at a bar to finally have to do this... lol.

funeralthirst said:
link please? i tried looking at heimdall, but search is broken (and i can't look through your previous posts because it gives the same search error).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=944598
there you go
Glad you got the phone back up....... get this as a back up anyway good to have

Link for the Android 2.3.3 GRI54 for the Nexus S 9023

I flashed my Nexus S with CM7 RC 4. Accidentally my original nandroid backup got deleted. I want to flash my device with the factory android 2.3.3 image. Please let me know the link to download the Android 2.3.3 for SNS 9023 GRI54.

You find it on:
http://forum.xda-developers.com/showthread.php?t=973534

I have already downloaded the rom files and the odin but the odin don't recognise my NS.
Can you tell me how to do a fastboot flash ?

If you want odin to recognize your nexus you have to install the samsung usb drivers .. You can find them here: http://forum.xda-developers.com/showthread.php?t=728929

I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.

I do not have a fastboot image for you ..btw the google drivers are not the same as the samsung drivers ..for odin you will need the samsung ones ...
To go into downloadmode :
turn on you phone, plug your phone into a sb port ( as if you wanted to put something on the phone) then while your phone is still connected to your pc , switch you phone off and keep holding vol up + vol down ..you will see that if you keep holding them phone will go into download mode after you phone is switched off

jaivinder said:
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
Click to expand...
Click to collapse
You installed the samsung drivers, make sure that your phone is power on,disable the usb debugging, ceheck that microsoft.net framework is installed on your pc. When you connect your phone (on your device manager) you must have "android phone" and below that "nexus s" with out any question symbols.If so then select to update your driver and give the path you installed the samsung drivers (eg c:\program files\samsung ....).
Power off you phone, open Odin and follow the pdf file from samfirmware to load the files (bootloader,pda,modem,csc). Hold your phone from the middle of volume buttons(between vol up and vol down) and immediately connect your phone to your pc with the usb cable .you are going to see the yellow triangle with the android.
Try it

Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.

hamajiro said:
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
Click to expand...
Click to collapse
What kind of error?on Odin or on your phone?

afilopou said:
What kind of error?on Odin or on your phone?
Click to expand...
Click to collapse
On Odin. The error message is in Korean so I don't know what it says, but it says something about the PDA tar. Please see the attached image.
Thanks

If I do it without PDA, I don't get an error...

hamajiro said:
If I do it without PDA, I don't get an error...
Click to expand...
Click to collapse
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522

afilopou said:
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
Click to expand...
Click to collapse
Thank you so much for your help.
I don't have a windows PC, but I'll install Windows 7 to my MBP using bootcamp and see how that goes.
I'll check the md5 check sum as well.
Sent from my Nexus S using XDA Premium App

Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App

hamajiro said:
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Looks like that the virtual machine (vm fusion) on macosx generates problems.As far as i remember only parallels worked ok.I have imac as well but i have bootcamp win7 in order to avoid all these problems. Hope to help
Sent from my Desire HD using Tapatalk

Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...

hamajiro said:
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
Click to expand...
Click to collapse
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk

thanks, really needed this link

afilopou said:
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No, I don't remember the initial values...
I'll check them at a Vodafone store when I get a chance.
Sent from my Nexus S using XDA Premium App

OK, so I had a chance to go into a local Vodafone Australia store.
The Baseband version under 'About phone' from the settings was I9023XXXKB1.
Under fastbootmode, the bootloader and baseband versions were I9020XXXKA3 and I9020XXXKB1.
However, CARRIER INFO is 'XSE' for Vodafone Australia, where as the CARRIER INFO from the Samfirmware.com ROM is 'EUR'.
Almost back to factory stock condition! Is it possible to change the carrier info? Does anyone know where I can get the stock Australian ROM for Nexus S?

Are there ways to flash a new modem besides ODIN?

I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?

pharmer81 said:
I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?
Click to expand...
Click to collapse
I don't believe so. Did you try running Heimdall on linux on the Mac? Heimdall also has Windows drivers if Odin doesn't work on that PC then maybe Heimdall will. You need to use modem.bin in Heimdall....extract it from the .tar file with 7zip.

I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7

stilesja said:
I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7
Click to expand...
Click to collapse
According to the Heimdall website, the second bootloader problem for Mac was fixed with Froyo 2.2. Of course Heimdall doesn't officially support Epic and I don't have a Mac (just Linux and Windows) so I haven't tried it.
To the OP:
What version of Heimdall are you using? Are you using the GUI or the command line?
There may be a problem with the GUI not acting the way it's expected. If nothing else works, I would recommend:
1. install Heimdall 1.2.0 (command line).
2. boot phone into download mode (power + 1 key)
3. attach phone to computer
4. see if heimdall recognizes the phone by using the command
heimdall print-pit
Click to expand...
Click to collapse
. That should give you a listing of the partitions on your phone. It will reboot your phone.
If that works, then repeat steps 1-3. Then to upload a different modem just use
heimdall flash --modem <file name>
Click to expand...
Click to collapse
where <file name> is the file name for the modem. I don't know how you specify the directory for files in Mac, but in linux I just navigate to the file and open the terminal window to save on the cd commands.

I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?

Yes it's will do it with ec05
Sent from my SPH-D700 using XDA Premium App

pharmer81 said:
I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?
Click to expand...
Click to collapse
I just started to use Mint 11. It's been almost 15 years since the last time I used linux shell.

Cannot flash BL or Modem

Hi guys! I do have a Galaxy S5 SM-G900F,running latest Blisspop rom. I wanted to update the MODEM (Currently I have BOD3 on both modem and BL),but as the process finishes and phone restarts, BL and Modem are still the same. I already tried changing USB port and on another PC. Thanks!

Desactives kies if you ve installed it
& dont use Windows 8 because
you must adjust its parameters
By options in win8 reboot

yanis488 said:
Desactives kies if you ve installed it
& dont use Windows 8 because
you must adjust its parameters
By options in win8 reboot
Click to expand...
Click to collapse
Hi.
I do not have Kies Installed. I am using Win10 Pro.

Wolf80 said:
Hi.
I do not have Kies Installed. I am using Win10 Pro.
Click to expand...
Click to collapse
You can retry flash twice
like indicated on threads
Or changes with other usb cables
& other Os like xp win or w7
It is not ever easy so good luck
Man !

UPDATE: I tried flashing on Windows 7 with Odin 3.09 and 3.10.6,BL and Modem still wont flash. I am starting to think for problems related to NAND.