Database Info

Captivate and a Hackintosh

Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?

Hmmmm
Ive never herd of this problem. It could be because its a hackintosh. I have a macbook pro and the captivate connects and does everything perfect. If you used a custom rom on the phone that can be an issue. It could be a bad flash. If you have stock then im not sure what the problem could be.
Sorry hope you fix this problem!

Probably not going to be much help but I have a hackintosh and my phone and PC play nice together
OSX is telling you the phone needs to be rebooted? Am I understanding that right? I can fiddle around and see if some settings make mine do the same thing

Are you using a pure vanilla untouched OS X build, or one of those crappy thrown together modded kernel deals.
Used to triple boot Windows, Linux, and OS X on my laptop before it fell off a table.

if you're running a vanilla build then it should work but you probably aren't. what version of OSX and what distro are you using? I suggest posting over at insanelymac since this is most likely a hackintosh issue.

How did you make your hackintosh? Feel free to PM me.
Ethere said:
Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA App

seclm193 said:
How did you make your hackintosh? Feel free to PM me.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
google can be your best friend.

I have no PC. I use XP with Parallels and Bootcamp, and It still is very finicky. Never had a Hackintoch but the newer Macs are Intel. Not sure where I'm going with this, but, yeah.

i dont have any problems with my captivate and my hackintosh. using the vanilla kernel.

Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://tonymacx86.blogspot.com/2010/04/iboot-multibeast-install-mac-os-x-on.html
I am running Cognition 3.04 on my phone. And the minute I plug the phone into USB, this is what I see on the screen. This is not my computer, but it's an image I found on google images, but that's the exact error. I guess it's a kernel panic.
{
"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"
}
Doesn't matter if I have USB debugging on, or not. I've pretty much exhausted everything I can think of at this point, unless someone else has a suggestion. On my Windows computer, the phone is seen just fine btw...not sure what the problem could be.

Ethere said:
Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://migre.me/3JFmQ
I am running... is not a phone issue but a hackintosh issue.
Click to expand...
Click to collapse

"Telling me to reboot" and "kernel panic" are two very different things.
Now it's definitely a problem for these guys:
http://www.insanelymac.com/forum/

Yeah, I posted a thread right on TonyMac's website too and they had no clue as to why that happened. Thanks for the link Mike. I'll check it out with them and see what they suggest.

this may be related
From the Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ) FAQ:
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Although Heimdall runs on OS X all Galaxy S devices tested thus far contain a bug in the secondary boot loader that prevents the device 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.

Hrm, you may have something there. I'll flash back to stock tonight and see if the Captivate works after that.

[Q] Not sure if bricked?

I've troubleshooted a lot of things on my Vibrant since 2010, but for some reason I couldn't get it right on the GS4G (and it's embarrassing). I'm not new to Odin, but I get the phone ---- ! ---- pc screen whenever I try to connect to my computer. Yes, I understand that it's another way of the phone being in download mode, but the other variables involved make it difficult to start from scratch again. Here's a list of what I've checked so far:
- 64-bit drivers from http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29 have been installed/reinstalled multiple times, and the computer (64-bit Windows 7) has been rebooted to make sure
- the computer will not recognize the device no matter what I do; all Odin attempts using files from http://forum.xda-developers.com/showthread.php?t=1480418 have had no effect
- attempts to connect to Odin and have it recognize the phone by showing the yellow COM have ended in vain
- yes, the phone in question is a Samsung Galaxy S 4G and the previous ROM on it was Black Valhalla
Another checklist I constantly read: http://forum.xda-developers.com/showpost.php?p=22234345&postcount=63 . It's basically a repeat of what I've done above. I'm just showing what I've read on how to fix this problem.
I can't even get the one-click program to recognize the phone because of some USB issue. The USB ports are seen fine by the Vibrant in download mode, so it shouldn't be any different for the GS4G. I've used all of the USB ports on this laptop and nothing works.
Any help would be greatly appreciated.

Have you tried thoroughly uninstalling all drivers including for the vibrant and restarting your laptop?

lumin30 said:
Have you tried thoroughly uninstalling all drivers including for the vibrant and restarting your laptop?
Click to expand...
Click to collapse
Yup, that's what I meant by installing/reinstalling. Sorry for being a bit vague.
I was really thorough with the USB drivers.

joe98200 said:
Yup, that's what I meant by installing/reinstalling. Sorry for being a bit vague.
I was really thorough with the USB drivers.
Click to expand...
Click to collapse
Remove them all again. Try the Heimdall One-Click guide in the second link of my signature.
In the notes I link a utility called USBDeview. Use it to double check you have all android and samsung related drivers removed. Make sure you also go into your traditional uninstall programs on your laptop and uninstall samsung drivers from there. Heimdall One-Click has drivers and everything else you need within the program.

lumin30 said:
Remove them all again. Try the Heimdall One-Click guide in the second link of my signature.
In the notes I link a utility called USBDeview. Use it to double check you have all android and samsung related drivers removed. Make sure you also go into your traditional uninstall programs on your laptop and uninstall samsung drivers from there. Heimdall One-Click has drivers and everything else you need within the program.
Click to expand...
Click to collapse
I'm getting this whenever I try to connect. All Android and Samsung-related drivers are removed already, even more thoroughly with the utility program.
{
"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 don't see USB Receiver (Interface 0). http://i50.tinypic.com/34ioirr.jpg
Is there something else I should do with these available options? The computer seems to recognize the phone now.
Edit 2: For some odd reason, Odin recognizes the phone before the drivers from the One-Click were installed. I just finished using Odin to go back to stock since the One-Click program wasn't showing the USB Receiver (Interface 0) I was looking for. Before I decided to close everything, I wanted to see what Odin thought. I assume the root of this whole problem was really the USB drivers that I couldn't get rid of without the utility program. Thanks for your help!
I never thought that annoying T-Mobile startup sound would sound so glorious.

Glad you got it.

If you do flash to the "homebrew" ICS ROMs, you'll need the Google USB drivers from the SDK; the Samsung ones won't recognize the phone.
(This applies to Windows only)

Root Symphony W60/Micromax A68

I am Gonna make this short as you guys are waiting for a Long time for this !
First of all, What is Rooting ?
Rooting your Android device involves adding in a small Linux application called “su”. It stands for SuperUser, and allows applications and commands to run with elevated permissions. Everything that runs code, whether it’s an application or the user, has a permission level set by the operating system.
Why Linux? Well the heart of the Android operating system is the Linux kernel. You'll hear a lot of nerdy geek-speak about the Linux kernel, but all you really need to know is that it's what is interfacing Android to your hardware, and ultimately has complete control. When you stray outside the "normal" way of using Android and start entering commands directly, the kernel is who you're talking to.
For More Info, Go here http://www.androidcentral.com/rooting-it-me-some-qa
Click to expand...
Click to collapse
Before Starting Here is a Proof That is Works,
{
"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"
}
Rooting,
First of all, Go to the Settings>Developer Options and Enable USB Debugging !
Connect the Phone to your PC
Now go to The Notifications and Go to USB Options and Select Media Device
And You are done with the phone, keep the phone Connected To Your Pc.
Now download and Install The Driver First,
After that Download this Software,
Extract the Rar file and go inside and run the TPsparkyroot.bat
Follow the On Screen instruction and You will be Done !
Now Your Phone Will Reboot 3 TImes, And The Third time It will say something like "Update"
And When the Phone Boots up, You will be Rooted ! XD
Hit The Thanks Button If this Helped You !

sakibhasaN said:
I am Gonna make this short as you guys are waiting for a Long time for this !
First of all, What is Rooting ?
Before Starting Here is a Proof That is Works,
Rooting,
First of all, Go to the Settings>Developer Options and Enable USB Debugging !
Connect the Phone to your PC
Now go to The Notifications and Go to USB Options and Select Media Device
And You are done with the phone, keep the phone Connected To Your Pc.
Now download and Install The Driver First,
After that Download this Software,
Extract the Rar file and go inside and run the TPsparkyroot.bat
Follow the On Screen instruction and You will be Done !
Now Your Phone Will Reboot 3 TImes, And The Third time It will say something like "Update"
And When the Phone Boots up, You will be Rooted ! XD
Hit The Thanks Button If this Helped You !
Click to expand...
Click to collapse
Contribute your contributions towards A68 here:
Micromax A68

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

[DEV] Thor Flash Utility - The new Samsung flash tool

Thor Flash Utility​This is a flash utility for Samsung devices, made from scratch in C#.
To run this, you must have .NET 7 runtime installed on your computer.
Latest release can be found on GitHub - https://github.com/Samsung-Loki/Thor
This tool was tested and works flawlessly, I'm open for any bug reports.
List of platforms​1) Linux (USB DevFS method)
2) Windows (not implemented)
3) Mac OS (not implemented)
How's it different from Heimdall?​Fun fact: Official Odin for Linux works using DevFS, and people report it working when Heimdall didn't.
1) Is able to do NAND Erase All (aka erase userdata) and erase any partition, given the length.
2) Ability to shutdown and reboot into Odin mode (not supported on every device)
3) Not using a USB transfer library and doing it natively for best results
4) Extended the PIT parser with new information being discovered
5) Can flash directly from an Odin .tar / .tar.md5 archive
6) Works with .lz4 files directly without manual extraction
7) Implemented EFS Clear and Bootloader Update options in Odin
8) Is able to change the sales code of the device
Support me​If you would like to support me and my team, donate here.
We're a team of teens (at age of 14-15) making random projects for fun.
Current list of commands​The up-to-date list of commands can be found here.
Usage guide​A comprehensive usage guide can be found here.
What devices were tested?​1) SM-M205FN/DS from 2019 0x00030000 (Unknown1: 0, Unknown2: 0, Version: 3)
2) SM-G355H/DS from 2014 0x00020000 (Unknown1: 0, Unknown2: 0, Version: 2)
Frequently Asked Questions​1) A fatal error occurred. The required library something could not be found.
This is a Linux Package Mixup, use this as reference.
2) What happened to original Thor (or Hreidmar)
This is a rewrite of Thor written from scratch, so I could implement the native USB communication.
Also, the old codebase was severely flawed in my opinion. I archived it here.
Credits​TheAirBlow for Thor Flash Utility
Benjamin-Dobell for documenting much of the Odin protocol

[reserved]

real

Bro finally revived good old Thor/Hreidmar

@TheAirBlow Thx.
Didn't test it yet but just a hint:
{
"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"
}
Link leeds to wrong version acc to your post #1, or doesn't it?

bmwdroid said:
@TheAirBlow Thx.
Didn't test it yet but just a hint:
View attachment 5938745
Link leeds to wrong version acc to your post #1, or doesn't it?
Click to expand...
Click to collapse
Yeah, that was an accident. It is indeed .NET 7

hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)

ilshatiko1988 said:
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
Click to expand...
Click to collapse
This tool could probably be used in Termux or in a root shell if you somehow could install .NET 7 Runtime. But, it does require the phone to be rooted for Thor to be able to access the USB devices connected. And additionally, you need a (first phones USB) to (second phone's USB) cable to connect, or have some adapter to make it work.