Database Develop

[Q] how i change rom in MAC OS X

Hi all
how can i change my rom with MAC OS X
is there Odin for mac

You could use Heimdall, it us cross-platform.

well...................u could also install XP or win 7
as virtual or as another boot.
thats how i do it..

nandihno said:
well...................u could also install XP or win 7
as virtual or as another boot.
thats how i do it..
Click to expand...
Click to collapse
Have you tried as a VM on mac osx? None of them work that way because OSX has some issues connecting to the galaxy. Only way to make it work is Windows on a bootcamp.

ashwinds said:
Have I tried as a VM on mac osx? None of them work that way because OSX has some issues connecting to the galaxy. Only way to make it work is Windows on a bootcamp.
Click to expand...
Click to collapse
I'm using windows 7 (32) running in vmware to flash mine..
and i'm running OSX
(also this is probably more Q & A the dev related)

Geee! that sounds very promising!! I've been surfing the forums for someone who has it going on vmware and you are the first I have come across! Any changes you had to make? For most of us, the device will appear and disappear - maybe it is because of 32 bit windows 7... must try. Thanks

I'm use Bootcamp with XP for flash my phone because with Parallels Desktop, Odin don't recognize my phone.

ashwinds said:
Geee! that sounds very promising!! I've been surfing the forums for someone who has it going on vmware and you are the first I have come across! Any changes you had to make? For most of us, the device will appear and disappear - maybe it is because of 32 bit windows 7... must try. Thanks
Click to expand...
Click to collapse
Had to test this and i can confirm that i can indeed run Odin now from Vmware on Mac OSX. I am not sure when this started happening but Benjamin on the Heimdall forum was saying that there were some changes by Samsung in the secondary bootloader of the i9000 which would allow people to connect. Perhaps its this - but anyway - works now - even tried a flash to make sure its ok.

i run a virtual machine with windows XP at Ubuntu OS . it can update i9000 by Odin.
Sent from my GT-I9088 using XDA App

Parallels 6 Windows VM
That works with Odin as well.

Never mind, it's already posted here.

Sell Mac -> buy PC -> Profit and fix.

I have no problem flashing my phone with odin. Im on mac running win7 (32) over paralells desktop.
Sent from my GT-I9000 using Tapatalk

ashwinds said:
Had to test this and i can confirm that i can indeed run Odin now from Vmware on Mac OSX. I am not sure when this started happening but Benjamin on the Heimdall forum was saying that there were some changes by Samsung in the secondary bootloader of the i9000 which would allow people to connect. Perhaps its this - but anyway - works now - even tried a flash to make sure its ok.
Click to expand...
Click to collapse
Maybe something did change as I was orignally running 64bit on my virtual machine and that never worked. although I did load the drivers so I don't if thats what did it??

Ibanez33 said:
Maybe something did change as I was orignally running 64bit on my virtual machine and that never worked. although I did load the drivers so I don't if thats what did it??
Click to expand...
Click to collapse
That should be the cause of. U can run a 64bit os as a vm but officially only 32bit is supported. (this counts for paralles. Dont know how it is with othet progamms)
Sent from my GT-I9000 using Tapatalk

SBVerlee said:
You could use Heimdall, it us cross-platform.
Click to expand...
Click to collapse
+1
another vote for Heimdall,
you'll find it in the SGS DEV forum
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just thought I'd stop by and confirm that Samsung have fixed the secondary bootloader. The new Sbl.bin is included in official (Norwegian etc.) Froyo releases. If you're running a non-official release then the updated bootloader may not have been included.
Now the Galaxy S is functioning under OS X I've released Heimdall OS X binaries and instructions on how to use them. They can be downloaded from the official Heimdall page on my website.

thanks all
i installed Windows 7 boot camp

AlexFLCL said:
Sell Mac -> buy PC -> Profit and fix.
Click to expand...
Click to collapse
as if, dumbass

[q] usb/unknown

Sorry for my englishg in advance... im from argentina.
I have a i9000b but maybe you can help me...
The thing is i was flashing a new kernel via CWM and something went wrong.
Now the phone doesnt start... get stock in the kernel logo.
I can get in at download mode... by pressing volume - home and power buttons.
The problems comes.. when windows doesnt recognise my phone... says usb unknown divice.. and USB\VID_0000&PID_0000\
Is anyway to force drivers?... i saw that maybe with GALAXY NEXUS driver would work.. casue my kernel was ported from that divice... couldnt.. force the drivers...
Anyone could help me please?
I wil be greatfull!
Thanks
edit: i cant enter in recovery mod

Installing android sdk will install nexus drivers.
Sent from my SGH-T959 using XDA

trailblazerz11 said:
Installing android sdk will install nexus drivers.
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
yes but i get not hardware id by windows... so i need to force the driver by editing de .inf
PD: i made a jig today is working... tried in a i9100... but not working on the i9000b stays frozen at the kernet platypus logo!

Usb drivers for galaxy s
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml for 32 bit
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml for 64 bit
Install the right one and reboot.
Put phone in download mode, make sure Kies isnt running and open Odin and now plug in your phone. Does your phone appear at all in Odin?

Same issue!
Hi guys...I`m passing through this same problem...I didn`t fixed my SGS yet...I`ve tried any different drivers (samsung, nexus, heimdall, USBview) anything is working
The bigest issue I think is some deleted or corrupted file into the ICS...cause when I star it up at CWM I`m not abble to do anything...always the same error "E: unknow mount/ storage...format/ restore failed"
My last chance will be next week when I`ll go to take it to a Samsung place.
I`ve read various Android/Samsung forums but anyone can help...It`s a "Non-perfect-brick"
Thanks...and waiting for same holpefull suggestion!
(sorry about my English)

jjuki said:
Usb drivers for galaxy s
Driver-for-Windows-x64.shtml[/url] for 64 bit
Install the right one and reboot.
Put phone in download mode, make sure Kies isnt running and open Odin and now plug in your phone. Does your phone appear at all in Odin?
Click to expand...
Click to collapse
Already tried to force this drivers.. and anything happend... i get error from windows says that is a problem trying to start the hardware (error 10 )
edit: already tried with galaxe nexus drivers... asus transformer drivers.. generic drivers... i9000 drivers... and libusb drivers.... im still getting erro 10 unable to star the divice

Try another usb port. And try on other computer if possible. And read this http://forum.xda-developers.com/showthread.php?t=1347006
Sent from my GT-I9000 using XDA

jjuki said:
Try another usb port. And try on other computer if possible. And read this http://forum.xda-developers.com/showthread.php?t=1347006
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
i tryed too i show u what i get.... still not working... notice that im only able to get my device in download mode... but hardware id... is USB/UNKNOWN... so i edit the inf of the driver to be able to install it... (tried with this driver http://www.mediafire.com/?vugbd358l4si4p4 and the sdk nexus one driver)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit: i had miui on my phone.. them i flashed ics... them i tried to flash miui again in cwm.. and them the phone crash...

What does Odin say when you plug in the phone? Could you get screenshot of that?
Sent from my GT-I9000 using XDA

jjuki said:
What does Odin say when you plug in the phone? Could you get screenshot of that?
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
odin stays like anything is conected to the pc... tomorrow i will atach a screenshoot
http://forum.xda-developers.com/showthread.php?t=1363593
i skip this note i think... so i get my brick "Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery."

any ideas? please!

nexus driver
dark Knight rom is nexus ported . So heard like need to install nexus drivers on pc to detect the phone

vibrant goes into download mode but PC wont see it in odin

problem solved thanks!

you need to have the drivers installed. Your system will not recognize the vibrant i
you need to have the drivers installed. Your system will not recognize the vibrant if you dont have the drivers installed. //This also does not belong in the development section either. Best of luck

Use the "search" button in the Q&A forum,you posted in a wrong place
Sent from my SGH-T959 using XDA

serendipityguy said:
you need to have the drivers installed. Your system will not recognize the vibrant if you dont have the drivers installed. //This also does not belong in the development section either. Best of luck
Click to expand...
Click to collapse
I have them installed.

.
94SupraTT said:
I have them installed.
Click to expand...
Click to collapse
Reinstall usb driver, check your usb cable, try to use another cable

Did u had debugging checked?

manu_ha2001 said:
Did u had debugging checked?
Click to expand...
Click to collapse
Having Debugging checked is not needed to get into Download mode or for using Odin.

94SupraTT said:
I have them installed.
Click to expand...
Click to collapse
Are you sure you have the ICS USB drivers installed? These are different than the old Froyo/GB drivers.

Shrivel said:
Are you sure you have the ICS USB drivers installed? These are different than the old Froyo/GB drivers.
Click to expand...
Click to collapse
ICS drivers... Lol... There's some funny stuff right there.
Samsung Windows drivers haven't changed in awhile for the Vibrant. Drivers are drivers for Odin
Sent from my GT-I9000 using XDA

It happen to me not long ago, and I tough my usb port was busted, and I fixed with a sharp and fine needle scraping the little usb pads very gently, my theory its that sometime got caught inside the usb port and somehow the cable wasn't making the right contacts.

fishman0919 said:
ICS drivers... Lol... There's some funny stuff right there.
Samsung Windows drivers haven't changed in awhile for the Vibrant. Drivers are drivers for Odin
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
He must be confusing boot loaders with drivers......I guess
What are you looking at shortbus......

I ended up just using a different version of Odin. 1.83 didn't want to see the phone. 1.3 did. I have no idea why but it worked. I flashed back to stock and then used AIO toolbox to flash root, cwm, and the ICS Gummy.

try to use other usb port if phone not detected again

I recently had to painstakingly cycle through 5-6 different Odin versions, 512 .pit files, and jfd .tar combinations before Odin passed. Had the same previously working odin 1.7, 512pit and jfd in a folder marked "WORKING ODIN", so I was a bit slow to accept that possibility haha.
//edit
most of the time i don't *****, but imagine how annoying 3 button combo resetting(including taking battery out) is when you have no hands
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

fishman0919 said:
ICS drivers... Lol... There's some funny stuff right there.
Samsung Windows drivers haven't changed in awhile for the Vibrant.
Click to expand...
Click to collapse
Which is why I had to use the drivers for the Nexus from the ICS SDK. When I upgraded to newer bootloaders, the old drivers from the Froyo SDK stopped working. I couldn't Odin/ADB/download mode. When I used the USB drivers from the ICS SDK, all was well again.

I've been using the same drivers for almost two years,Odining from Froyo to Eclair to ICS, back to Eclair,.........with no problem.
That includes flashing bootloaders back and forth, even though GB loaders are backwards compatible.
Sent from my SGH-T959 using Tapatalk 2

Keep trying different combos. My computer does that often. If phone goes into download mode it can't be the plug because bumbumbum.... the phone will not go into download if it doesn't get power from the USB.
Sent from my SGH-T959 using XDA

Android Bootloader interface (fix)

I don't know if any else is experiencing this, but when I'm in boot loader mode and I plug my device into windows it gives me a error (device cannot start code 10). When this happens I cannot use fast boot at all it will be stuck there waiting for device. So I have a temporary fix:
1.go to device manager while in boot loader
2. Right click on your device in device manager
3. Click uninstall driver.
4. Remove your device from the computers USB.
5.plug it back in and before it automatically installs the drivers go to device manager and right click on Android under your device name and click scan for hardware changes. Now it recognizes my device in the boot loader interface.
I wanted to post this in case anyone else is experiencing this problem.

Never happened to me, but a nice find anyway!

I installed the universal driver and I have no problems.
Sent from my Nexus 4 using xda app-developers app

wilsonlam97 said:
I installed the universal driver and I have no problems.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You mean the Google USB drivers, then yeah I have it too, but when I check
It says device cannot start code 19, so that temporarily fixes it until you unplug the device and put it back.

Hello all,
Just wondering, but are you using windows XP by any chance?

heat361 said:
You mean the Google USB drivers, then yeah I have it too, but when I check
It says device cannot start code 19, so that temporarily fixes it until you unplug the device and put it back.
Click to expand...
Click to collapse
No I meant the universal drivers.
Sent from my Nexus 4 using xda app-developers app

wilsonlam97 said:
No I meant the universal drivers.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its been a while since I posted this thread, but I managed to get everything working properly.
As for the guy who posted above I was running windows 7.

heat361 said:
I don't know if any else is experiencing this, but when I'm in boot loader mode and I plug my device into windows it gives me a error (device cannot start code 10). When this happens I cannot use fast boot at all it will be stuck there waiting for device. So I have a temporary fix:
1.go to device manager while in boot loader
2. Right click on your device in device manager
3. Click uninstall driver.
4. Remove your device from the computers USB.
5.plug it back in and before it automatically installs the drivers go to device manager and right click on Android under your device name and click scan for hardware changes. Now it recognizes my device in the boot loader interface.
I wanted to post this in case anyone else is experiencing this problem.
Click to expand...
Click to collapse
You're a lifesaver my friend. Registered for the forums just to thank you

MarkTheSpark said:
You're a lifesaver my friend. Registered for the forums just to thank you
Click to expand...
Click to collapse
No problem and Welcome to the community

Unknown USB Device
Hi, I just installed the ADB Interface Driver but I can't install the Bootloader Interface Driver. In the Device Manager, this shows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Unknown USB Device(Configuration Descriptor Request Failed)) I connected my phone tomy laptop whilst it is in recovery mode
Any help would be greatly appreciated! Thanks

help windows 8.1

fastboot usb not working after i upgraded to windows 8.1 preview?
anyone else with this problem?

martyotaku said:
fastboot usb not working after i upgraded to windows 8.1 preview?
anyone else with this problem?
Click to expand...
Click to collapse
Switch to linux
Sent via my Nexus7 | WiFi.32GB

x102x96x said:
Switch to linux
Sent via my Nexus7 | WiFi.32GB
Click to expand...
Click to collapse
thanx but that doesnt help lol

martyotaku said:
thanx but that doesnt help lol
Click to expand...
Click to collapse
Yeah, don´t let me even install the drivers

Yup..have same probleme....what ca we do????i can't flash kernel :crying: :crying:

1. Why change to a brand new OS if you didn't first check it's compatible?
2. You might have to go through the same process as Windows 8 to get the drivers installed, e.g. turn off signature checking and then install them manually

I've been having the same issue. I've tried all the Win8 methods with no luck. With a name like "8.1", it implies that it's not a brand-spanking new OS. Hopefully there's an 8.1-specific solution soon.

It doesn't even recognize the device, it only says "Enumeration failed" in Device manager. Reverting to W8 backup unfortunately...

stirkac said:
It doesn't even recognize the device, it only says "Enumeration failed" in Device manager. Reverting to W8 backup unfortunately...
Click to expand...
Click to collapse
Yup same exact thing on mine ....
Sent from my HTC One using Tapatalk 4 Beta

EddyOS said:
1. Why change to a brand new OS if you didn't first check it's compatible?
2. You might have to go through the same process as Windows 8 to get the drivers installed, e.g. turn off signature checking and then install them manually
Click to expand...
Click to collapse
I was gonna say the same thing, but if it just not work, I think at this moment its really an incompatible device
...................................................................................................
windows 8.1 was released?

Same thing happening here with my Neo V.
I just upgraded to windows 8.1 preview two days ago and just realised yesterday when i wanted to flash a kernel that my computer detects it as usb enumeration failed , theres an icon saying the drive malfunctioned but i think it should be driver fault.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A shocking discovery i found though i installed the drivers :

Regarding the Fastboot drivers i have contacted microsoft and might be a fault at their part as they told me that not all drivers are installed in the preview version...

bump .......anyone figure this out?

we will just have to wait for windows 8.1 stable or downgrade for now... , no other workarounds yet

boylush said:
we will just have to wait for windows 8.1 stable or downgrade for now... , no other workarounds yet
Click to expand...
Click to collapse
Damn that sucks :crying:

same here. ray and x8 !!

That's what you get for using gey OS

man, I am having the same issue... beh 8.1

U guys might want to try flashing kernels from ubuntu (install ubuntu via wubi)

boylush said:
U guys might want to try flashing kernels from ubuntu (install ubuntu via wubi)
Click to expand...
Click to collapse
Last time i checked wubi was not working from windows 8 if you installed it with EFI support though. If your still on old Bios mode you will be good i think.
Ps. Ubuntu dropped wubi so they found out it's not working very well with EFI.