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 Issues -___-

So, yes before anyone tells me to read, Ive read the instructions on how to use Odin again and again. I downloaded Odin and the 64 bit usb drivers, i have a laptop running on windows 7. I put my phone in downloading mode and connected it to my laptop, but nothing seems to happen in Odin, no COM number, just nothing, I uninstalled the drivers and Odin and installed them once again, and i tried a different port...still nothing. I'm running on the leaked android 2.2.1, the phone is not rooted, just flashed with the update.
Any suggestions??....

Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Another idea... Try right clicking on Odin and running as administrator (not sure if this will effect anything, just throwing ideas out there).

Koadic said:
Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Click to expand...
Click to collapse
Yeah I bought another cable i know the one that comes with the phone is useless.
Will give a shot to the administrator idea and see what happens o.0,
thanks

The other thing is that you must put your phone in download mode, open ODIN and THEN plug in your phone. Aside from that, the USB thing is your best bet.

Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>

My last bit of advice would be to check in IRC at #samsung-epic the people there are very versed in using ODIN and are very helpful

monnie27 said:
Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>
Click to expand...
Click to collapse
I've had this issue before myself. I have two Windows 7 machines, both 64 bit. One would recognize my phone in download mode, and the other would not. I installed the correct drivers on both machines.
Make sure you are connected to one of the USB ports on the rear of the machine. Some people have had issues using the front USB ports.

ok thanks, I managed to get it to work somehow, i repeated the process od uninstalling and installing the drivers, Odin and somehow it worked this time. However i had Kies installed on the laptop, so i decided to uninstall it just for the heck of it ....and well after that, Odin recognized the phone o.0.
But thanks to all of you for the support ^_^

i would love to know the source of the x64 driver...as i found it to be a load of horsecrap
the driver found on the samsung website installs on both x86 and x64 machines in my experience
i was running windows server 2008 x64 at the time and only got the phone working with the driver directly from the samsung website
peoples long winded history of drivers and windows makes for a bad situation...at least be willing to try THE MANUFACTURERS option first
i bought my phone used...but it did come in the original box...
i just wasn't sure enough, then, to say that it is BS for a company like samsung not to distribute some kind of media/drivers with, or preloaded on, the device.
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR

well..i got the drivers from this page:
http://forum.xda-developers.com/showthread.php?t=798067
and used BitZipper to extract them, it worked this time.

good news
enjoy dk28
it saved me from believing android was a suckers solution to windows mobile
my phone instantly locks gps now and the easy access to enabling 3g via the power button menu was nice
i am a believer...adb is my new god...reborn in code...blahblah...
actually i'm just glad something like a cellphone can simply work simply as it should
finally after billions of ages of fail

Well im actually having some problems with the gps navigation and lock. The location is not accurate, it was extremely accurate when i was running on 2.1 and i had no probs with neither of them. I saw a thread related to this issue before and ill see what can be done..
Sent from my SPH-D700 using XDA App

the only method that worked for me:
odin back to dI18 (.md5 extention removed/renamed to .tar extension)
get gps lock
odin dk28 modem (modem only) with victory_8G_100528.pit
gps lock again
odin dk28 (.md5 extention removed/renamed to .tar extension)
i actually didn't even try to get a gps lock after flashing the dk28 modem...
the key here seems to be performing the modem flash separately/first as there are multiple bootloaders working

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?

Heimdall and Litening rom 1.4

Hi,
I flashed Litenin (and other custom roms) with Heimdal on Linux flawlessy up to version 1.4 which hangs at boot.
I had to replace factoryfs.img with previous version's one (kernel and modem are from 1.4 still and it works....).
Is it a bug in heimdall or something wrong with Litenin rom 1.4 ?
A factory reset didn't help either, 1.4 can't be installed on my phone, at least not with heimdall.
Ciao
Max

bump !
Nobody using heimdall and litening rom here ?

I have exact the same problem....

tschakk said:
I had exact the same problem....
Click to expand...
Click to collapse
Did you solve it ? Flashing with Odin does the trick ?

No.. I dont have access to a win box...
but i think odin should work - another user reported after switching to odin everything was ok....

weird.
I'll try later on unpacking and repacking the factoryfs.img, maybe there's something on it which makes heimdall behava wrong.
Thank you for feedback

Could u resolve the problem?
Sent from my GT-I9100 using XDA App

Nope, unpacking and repacking didn't work either.
It seems that heimdall don't like 1.4 version

OK. thanks for the try...
I could access a windows computer this weekend. Odin worked fine...

I never got Heimdall working. It cant find my phone.

hmmm I did nothing special. What OS u use?
(Ubuntu)
1. I Install libusb-1.0 like described on the official heimdall homepage.
2. Install the heimdall .deb package.
3. put your phone to download mode
4. Start heimdall like: sudo heimdall print-pit
I only used the console edition (1.2.0) - not the gui edition...
For flashing type:
sudo heimdall flash --<partition identifier> <filename>

Lite'ning Rom v1.5 XXKF2
Lite'ning Rom v1.5 XXKF2 has just been released. Has anybody tried flashing the new version via Heimdall?

The link has been removed before I could try it

Yes, I saw that people were having problems with it. When the new version is up we can try it again.

Ok, just flashed Litening v1.5 with heimdall.
Everything worked as expected...

Nice, I'll try it tonight.

I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!

TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I've used the same configuration to flash my SG2. But you do realize that VirtualBox is using the same ubuntu (linux) drivers for usb?
And why do you find windows to be more reliable?

TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I cant share your opinion. Im working now for more than a year with Android. We have our own android build. And i had much less problems working with Linux (Ubuntu) than with Windows...

Flashed Litening rom 1.5 just fine with Heimdall in Ubuntu 11.04.

Can't flash, can't root, can't sleep

I have been at this for a week now. I've tried Heimdall 1.1.1, 1.3.2, AND Odin3 v1.83, v1.85, to reflash the stock Verizon firmware on my Galaxy Tab SCH-i800. I was an idiot and flashed U.S. Cellular firmware, which changed the boot animation and the cell service text. I've scoured the internet on how to do this and everything I've tried has failed. With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12" I'm getting my files from SCH-I800_VZW_stock.zip, it's been extracted. When trying to flash a .tar file with Odin, it works successfully, then my phone goes into bootloop. I can get back to Download mode, but every time I try flashing a stock .tar, I get the same results. I'm starting to go crazy. Anyone help?

maybe you have missed with your partions? if so, i think you need a specific pit file for this stock rom, i dont know where it is, but you might start looking for it.
edit : look in this thread, you might find it useful http://forum.xda-developers.com/archive/index.php/t-940046.html
and this is also important http://theunlockr.com/2012/06/28/ho...axy-tab-sch-i800-back-to-stock-and-unroot-it/
last one http://gizmoninja.com/2011/04/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
best regards ^_^
Sifou

chrispysaid said:
....With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12"
Anyone help?
Click to expand...
Click to collapse
Did you properly install the Samsung drivers on your PC using the heimdall utility? And you put your Tab in download mode?

The Problem may lie with youe Heimdall setup.
Make sure you have Keis installed. Then make sure you activate the drivers for Heimdall.
This is a great rom to flash to your VZW Tab. follow this thread http://forum.xda-developers.com/showthread.php?t=1325469