[Confirmed Working] ODIN via Parallels on Mac OS X - Verizon Samsung Galaxy S III

Hi Everyone - I'm copying another post I just submitted to the Samsung Captivate forum (where a specific question about ODIN via Parallels Desktop on Mac was posed). I was able to bring my phone back from the dead (soft brick - flashed a recovery zip instead of a recovery IMG) using the following method
Successfully ODIN'ed a new recovery IMG on Windows 7 (in conjunction with Parallels 6 for Mac OS X 10.6.8)
Used a random Windows 7 iso I had lying around. This was a brand new Windows installation, and no out-of-the-box modifications were made to OS X, Windows, or Parallels (except for downloading/installing the Samsung USB drivers, as suggested in a separate post in the Samsung Captivate forum).
My SGS3 was actually soft-bricked (Could not boot into recovery OR download mode.. Holding the power button would greet me with a "Could not do normal mode. Booting into Odin Mode" error)
Turned phone on (auto-booted into ODIN mode), plugged it into the Mac via USB, and was greeted by a dialog noting that a USB device was detected. It asked if I wanted to access the USB device via Mac or Windows 7. Chose Windows 7, and Odin was able to connect to it flawlessly.
If there are any questions, please let me know. I was running around like a chicken with my head cut off trying to find a solution (I'm on vacation in Germany and for some reason Windows PC's are avoided like the plague) and didn't want to go through the trouble of using Parallels unless it was confirmed working. For others in the same boat as me, let this be your confirmation. It works!!!

It also works with vmfusion. I can testify to that....

justreboot said:
It also works with vmfusion. I can testify to that....
Click to expand...
Click to collapse
+1

Related

A tale of Tilts, Macs, and Roms . . .

So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file. In the meantime . . .
I think I did everything right. HardSPL worked fine, but then, when I tried to flash Dutty's Dual v4 ROM, it stopped at 6% and told me there was a communication error. I tried it a few more times, tried Dutty's Touchflo Rom (that got to 4%) . . . still no luck. Same error. In between each try, I reset using the stylus and sometimes the stylus while holding down power and camera.
Am I doing something wrong, or was my mistake trying to do this via parellels?
Current screen says:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
USB
Thanks, guys.
I can confirm that if you install xp via boot camp then you can flash fine on a mac. I haven't tried going through an emulator such as parallels though. It should work fine though as long as parallels has taken over the usb ports.
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
By the way
It is error 262 that I'm getting . . .
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
drewcopeland said:
It is error 262 that I'm getting . . .
Click to expand...
Click to collapse
I might have to look into that. My "solution" didn't work. I'm going to try to find the original ROM somewhere . . .
zenrandom said:
I went through bootcamp boot as well, I rather assumed that I was going to need direct access to the hardware rather than the pass through of parallels...
btw you can set up parallels to boot a bootcamp partition... so you can use the direct boot and parallels from the same installation.
Click to expand...
Click to collapse
I am using Fusion instead of Parallels but this is what I do. I only have 1 copy of xp installed via bootcamp but I can also access it through Fusion.
I also have fusion on my MacBook Pro, and it failed when tried to flash. So I bootcamp and started XP and it flashed flowlessly
If you own original XP CD (like me) you can always call microsoft to activate, and since it is installed in 1 PC then fine (you'll have 1 license for parallel & another for Bootcamp)
drewcopeland said:
So, I tried to use Parallels (running windows XP) on my Intel Imac to flash a Kaiser Rom onto my AT&T Tilt. I'm currently stuck on the bootloader. I think I did find a solution, but I need to wait 10 minutes til I can download another Rapidshare file.
Click to expand...
Click to collapse
Which version of parallels do you have? In version 5160 the usb flashing works fine, in 5582 it is broken, as is in version 5584. They had an special build 5582.5 which allowed me to flash my phone correctly and according to parallels, the "next" version will include those usb fixes.
I'm using the latest version 5584 and when I need to flash my phone, first i shut down windows vm, install parallels 5160 over the current version and then boot up windows. I ignore the installation of parallels tools and just flash my phone. Then shut down windows again, re-install parallels 5584 and all is fine again.
Hope this helps you...
that does. Do you mean the most recent update will work?
edit: never mind. the most recent is 5583. I'll try to find 5160
drewcopeland said:
Yeah, the USB connection wasn't the problem. And, unfortunately, I don't have extra XP licenses lying around to bootcamp. my mac.
Anyone have any idea? I'll give you a cookie . . .
Click to expand...
Click to collapse
If you have a valid license for parallels, then you have a valid license to use bootcamp...
That said, I have flashed through parallels and vmware fusion TONS of times (about to do it again, in fact). So long as you've routed the "HIGH GENERIC RNDIS" device to the virtual machine it should work fine.

[FIX] Stuck at S/W Upgrade, Running Windows 7 64bit

I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
http://forum.xda-developers.com/showthread.php?t=1056847
And if you have a P990, you're in the wrong forum (this forum is for the P999).
omerika.emir said:
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
Click to expand...
Click to collapse
The Roms for the p999 and the p990 are not inter changeable. Different frame work.
jrfaulkin said:
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
Click to expand...
Click to collapse
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Erocks said:
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Click to expand...
Click to collapse
VMware with XP on it/Google how to bypass limitation?
Found this to get Xp Mode on home edition idk if it works I just use VMware personally
http://m.tomshardware.com/news/windows-xp-mode-windows-7-win7,10213.html
Sent from my LG-P999

[Q] Samsung Galaxy 5 (GT-I5500) won't connect to PC!

I've tried a few other forums but haven't got any replies, I guess since the Galaxy 5 isn't such a popular device. I figured if there's anyone who can help me they will be here though.
I wanted to put CWM on it so I could get a CM7 port on. Unfortunately it's just about impossible for it to get detected on USB. I've installed Kies (and even the generic USB drivers found in the SDK). In 2 days I only got it to connect once, and then I went and bricked it.
The one time it finally connected I ran Odin and tried loading CWM onto it. It still hadn't finished after half an hour so I figured it ended with an error that was never displayed. So I unplugged it and as expected - brick! I can get into download (upgrade/firmware) mode so I think it can be fixed if I can get CWM on it (and just install the CM7 port I had originally intended to put on).
Problem is I cannot get the darn thing to connect! to my computer I've tried two separate PCs, one running Window 7 x64 and another running XP x32. Is there a a certain process of connecting things? I haven't ran across anyone making mention of one.
Has anyone else experienced USB problems like this with Samsung phones? Would it even be possible to flash CWM on after it's been bricked like this? When I boot (normally) all I get is an image showing a phone and a PC with and exclamation error connecting the two. Please help!
Try to look for stock firmware on the forum.xda-developers.com and flash via ODIN. You need to be able to put the phone into download mode, so maybe get an USB jig. That should do the trick. Odin has to recognize your phone. First of all right click on the ODIN executable and select "Run as administrator" on windows. Plug the phone in the DL mode and wait until it appears as active in Odin. Then flash the ROM and pit file. (Don't use ODIN one click). If ODIN does not recognize your phone try a different USB port or reinstall Kies. The Kies trick was which I used and it was able to recognize my phone.
Thanks, martin0176. I can still manage to get the phone into download mode - it's getting recognized by a PC that's the problem.
Could you tell me more about the pit file? I only have an ops file.
Try a different cable. I was having the same problem on the Samsung Continuum and it turned out that the cable was working for power, but not for data.

Samsung Infuse is stuck

I have installed a rom on my phone today but when it powers up, it gets stuck on the Samsung screen. I have tried putting it into download mode to restore to factory and start over, the problem is that I cannot get neither Odin nor Heimdall to recognize that the phone is plugged in and in download mode. On a windows machine, the device manager doesn't even pick up the phone is plugged in. The windows machine is the one I usually use for this procedure.
I have a Ubuntu machine as well that I am trying to use but it isn't recognizing the phone either.
Any suggestions besides toss it out the window on a busy freeway?
Thanks in advance.
jmonroe said:
I have installed a rom on my phone today but when it powers up, it gets stuck on the Samsung screen. I have tried putting it into download mode to restore to factory and start over, the problem is that I cannot get neither Odin nor Heimdall to recognize that the phone is plugged in and in download mode. On a windows machine, the device manager doesn't even pick up the phone is plugged in. The windows machine is the one I usually use for this procedure.
I have a Ubuntu machine as well that I am trying to use but it isn't recognizing the phone either.
Any suggestions besides toss it out the window on a busy freeway?
Thanks in advance.
Click to expand...
Click to collapse
First wrong section...lets move this to the q&a or Gen sections....then we can and will address your issues...kk
jmonroe said:
I have installed a rom on my phone today but when it powers up, it gets stuck on the Samsung screen. I have tried putting it into download mode to restore to factory and start over, the problem is that I cannot get neither Odin nor Heimdall to recognize that the phone is plugged in and in download mode. On a windows machine, the device manager doesn't even pick up the phone is plugged in. The windows machine is the one I usually use for this procedure.
I have a Ubuntu machine as well that I am trying to use but it isn't recognizing the phone either.
Any suggestions besides toss it out the window on a busy freeway?
Thanks in advance.
Click to expand...
Click to collapse
From your post I assume you are able to get in download mode.
Try using different USB cable and different USB port. Also clean USB port on phone.
Sent from my Galaxy Nexus using XDA
Alright Joe...posted it to the Q&A Forum. Feel free to delete this one.
Thanks.

Oneplus 6 unable to be unbricked

Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!
EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.
Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.
It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!
Make sure u use the cable included with the phone. Some cables doesn't work
Neither. I tried with the original and two others that I have.
if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?
I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.
Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~
I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen

Categories

Resources