Database Info

[Q] What do I need to get Heimdall to work? (Mac)

I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.

i dont know about the mac version but there should be a readme in there for installation. also i think the mac needs codeless kext installed. should be outlined in the readme but couldnt tell you for sure.

I followed the instructions as best as I could understand. The UI pops up but refuses to flash or even recognize my phone.

re: flashing rom
tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
Since you have a mac it would be a lot easier for you to flash a
clockworkmod type custom rom.
You must have clockworkmod recovery to be able to do this.
If you are running stock rom and already have clockworkmod
recovery in your phone then then you can BACKUP your stock
rom with clockworkmod and then flash a new custom rom
as long as its a clockworkmod rom zipfile.
Most all of these custom roms you see here on xda are all
clockworkmod types (zipfiles) which do NOT need ODIN
or Heimdall at all.
But you do need to have a usb card reader if your your
computer is not reconizing your samsung phone as an external
USB drive.
If your Mac computer does reconize your phone as a external
USB device then you do not need to remove the microSD card
and you do not need a card reader.
I am sure you know how to use a usb card reader so I will not
go into that now.
Here is the link to the most popular custom rom for Infuse
which is the type you need. (clockworkmod flash)
http://forum.xda-developers.com/showthread.php?t=1195571
Follow the easy step by step instructions to a "T" if you
don't want to start all over and have to do it again.
{
"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"
}
Good Luck,
Enjoy!
Please don't forget to give me a big THANKS if this post was worthwhile reading!

----------

Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.

tight686 said:
Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.
Click to expand...
Click to collapse
You are already on a rooted rom. Just get sgs lernel flasher and flash a "rainbow fix kernel." But id try to get heimdall working. it is super easy on linux. I love the debian package system.
If it doesnt see the device it sounds like an issue with that "codeless kext" which is described as being like a driver. that is unless samsung dropped the ball on the boot loaders again. the bootloaders in the odin oneclick packages for the galaxy s would prevent the device from being visable on a mac in download mode. later versions had this fixed. if i had a mac id help. i think the mac is a great system but i just dont know enough about your problem.
there is always the bootcamp or virtual machine options. if you need windows maybe i can help out if you pm me. or yu can do a quick install of mint or ubuntu which is not only more similar to mac than windows but with no need for drivers and the debian packages is easier to install heimdall on than odin is in windows.
or maybe you can contact the developers of heimdall.

tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
what version of heimdall did you download? i ask because it seems 1.3 wants a firmware.xml file that specifies compatible devices, could be an issue of it looking for that file. i still use v1.1.1, i just updated to 1.3 but dislike it and am going back, will see if 1.2 is compatable with the 1.1.1 frontend because it doesnt appear to have a frontend package.
edit:
yes v1.2.0 comandline seems to work with 1.1.1 frontend, install 1.1.1 and then you may upgrade to 1.2 (atleast that's how it works under linux)

Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.

tight686 said:
Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.
Click to expand...
Click to collapse
most use ubuntu. debian packages but there own repositories that are less likely to provide unstable updates to break your system.

[How-To]Unbrick the UnBrickable Infuse4G

{
"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"
}
Introduction
Software based resurrection is now possible on the Infuse4G after a simple hardware modification. The procedure works the same as the Captivate
Software Based Resurrection
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer. You can use this link http://www.java.com/en/download/ or use your package manger ie. apt-get install openjdk-6-jre
Unbricking:
1. Apply UnBrickable Mod to your device: http://forum.xda-developers.com/showthread.php?t=1318386
2. Run UnBrickable Resurrector(Galaxy Infused Edition): http://code.google.com/p/hummingbird-hibl/downloads/list This will only work on linux currently. Install Linux with WUBI or dual boot if you have windows. Use bootcamp for Mac.
Since UnBrickable Mod displays a black screen, we've added USB recognition to the Resurrector. This allows you to see what mode your device is in. It allows you to discriminate between a black-screen brick, UnBrickable Mod, and download mode with a bad Params.lfs. Each of these modes can show a black screen.
If you see this, your device is ready for resurrection. Press the Download Mode button to upload the HummingBird Interceptor BootLoader(by rebellos). The HIBL will be injected directly into the processor where it will authenticate with the System-on-a-Chip, call memory routines to perform initialization, then reuse the same download routine which was used to download the HIBL, but this time it's unsecure. The Resurrector will then upload a modified SBL which has been designed to put the device into Download Mode. After the resurrector has performed its duties, the device will display a black screen, but it will actually be in Download Mode.
If you see this, your device is not in UBM mode. This means your device is frozen or the mod has not been applied correctly. Remove the battery and USB cable, then plug in the battery and connect the USB cable to try again.
If you see this, your device is in Download mode, procede to step 3.
3. Run Heimdall One-Click: http://forum.xda-developers.com/showthread.php?t=1331381
4. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
Conclusion
The technology used in this resurrection process has been refined to the point of stupid-user-friendly. If you're having a problem, you're doing it wrong .
Tools
Linux one-click Resurrector: http://code.google.com/p/hummingbird-hibl/downloads/list

Very nice.
Unfortunately, with Infuse development almost dead, this won't help much.
It's great that your doing this though, hopefully dev's will be inspired to mess with the Infuse.

Excellent! More pieces to the dev puzzle to help us move farther down the road without much worry that we'll screw ourselves. Great work man!! I dont thnk development is really dead, everyone is still just waiting for the official GB package to drop so they have a full source package to work from. This may be a bastard phone but it still has some good life in it.

thumbsinblack said:
Excellent! More pieces to the dev puzzle to help us move farther down the road without much worry that we'll screw ourselves. Great work man!! I dont thnk development is really dead, everyone is still just waiting for the official GB package to drop so they have a full source package to work from. This may be a bastard phone but it still has some good life in it.
Click to expand...
Click to collapse
Oh, I know that it'll pick up once official GB drops, that's for sure, but until then.... not really
Sent from my phone. :3

I agree hasnt been hardly any devl going on lately
Sent from my SAMSUNG-SGH-I997 using XDA App

[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)

Fastboot Troubles

I've tried just about everything to get my fastboot working. I'm running on Windows 8. I've tried tool and scripts, different drivers, HTC Sync, EVERYTHING.
I've gotten ADB to work but fastboot won't recognize my phone.When I put my phone into fastboot mode, I can go into my computer and look up the phone in device manager and I do see the phone. Unfortunately, it presents an error that say the device has failed to start. This has been unchanged through out every "fix" I've tried. Any ideas?

Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita

timmaaa said:
Windows 8 is notorious for breaking fastboot. There are a few supposed ways to fix it. Exactly what have you tried? Saying you've tried "everything" doesn't actually tell us anything.
Sent from my Evita
Click to expand...
Click to collapse
Oops, sorry. I've tried the tools that are supposed to set up fastboot for you, I downloaded the SDK and got the fastboot and adb files but nothing shows up in the "fastboot devices". I've also tried the HTC Sync route as well as numerous drivers that are claimed to be the "fix".

What about some of the guides that are available that specifically address this problem?
{
"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"
}
Sent from my Evita

timmaaa said:
What about some of the guides that are available that specifically address this problem?
Sent from my Evita
Click to expand...
Click to collapse
I've tried all the results on that first page. Nearly every time, I get an error message with a yellow triangle for an icon:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.

Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita

timmaaa said:
Yeah I thought as much. I haven't seen people with Windows 8+ have much luck with fastboot. To be honest the only real fix I've seen is to use a different version of Windows, unfortunately that isn't as easy as some as it is for others.
Sent from my Evita
Click to expand...
Click to collapse
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.

KungPow90 said:
Pretty much what I'd figured. Well, thanks for the help. I think I can get by with that app Flashify for now.
Click to expand...
Click to collapse
Download latest HTC driver , go into your device manager in win 8 and in device mgr menu options on top make sure and click show hidden (not connected ) devices. You then will have to click onto the greyed out HTC or android name in device mgr tree and update manually . you have to actually go to the sub folder in the driver update and not just click the folder that its in. Lol its a pain but it does work. You can Google manually install HTC driver for win 8 and there is couple tutorials. Hope it helps. I beta tested win 8
And had to do that. Lol im back to win 7 and Ubuntu now
Senseless Power Unlocked

[Q] Using a Nexus tablet to perform fastboot/adb cmds

My question is:
Can you use a Nexus tablet or any android device for that matter, to perform fastboot or adb terminal commands to another device like a Nexus 5 for example, via USB? (terminal emulator?)
Essentially what I'm try to do is unlock the bootloader on my Nexus 5 (replacement that's coming in the mail) and any future Nexus devices, using a Nexus tablet instead of a PC.
The reason I'm asking this:
I'm fed up of laptop computers with mechanical parts, unreliable HDD etc etc..and I'm making the switch to a tablet.
I was dead set on the new Nexus tablet coming out... but then I came to realize without a PC of some sort, how the hell can I unlock the bootloader of my future Nexus devices???
My only alternative is the Microsoft Surface Pro 3 because it still has fully functional windows and can run terminal commands linked to .exe files. via USB attached to an Android.
But for functionality I think the new Nexus tablet coming out will better suit my needs, since windows is certainly not up to par in the mobile world.

no

I had the same question... I'm getting rid of my slow Microsoft PC! Luv my tab and hope someone figures out a way to do this....

Adb yes but its much harder than windows / Linux / Mac. Fastboot no.
Sent from my Nexus 5 using Tapatalk

Maybe if you got Ubuntu to run? (Not sure about Ubuntu Touch though)

Well this is a REAL SHAME, because it means anybody here with an Android, still needs a PC currently..
Unless you throw on dual boot Ubuntu on another Android device to run commands.. and that's just a maybe

Get a laptop/PC with an SSD then, and join the master race:
{
"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"
}

Would this work with a dual boot Ubuntu installed?

THE_KINGDOM said:
Well this is a REAL SHAME, because it means anybody here with an Android, still needs a PC currently..
Unless you throw on dual boot Ubuntu on another Android device to run commands.. and that's just a maybe
Click to expand...
Click to collapse
na, dont need a computer. you can use towelroot to toot your device. then use flashify to flash a custom recovery once you have root. and you can unlock/lock your bootloader with an app as well.

simms22 said:
na, dont need a computer. you can use towelroot to toot your device. then use flashify to flash a custom recovery once you have root. and you can unlock/lock your bootloader with an app as well.
Click to expand...
Click to collapse
It is a good idea to have a computer because if you run into problems and the phone can't boot, all options are exhausted without a computer... If you needed fastboot to repair.

rootSU said:
It is a good idea to have a computer because if you run into problems and the phone can't boot, all options are exhausted without a computer... If you needed fastboot to repair.
Click to expand...
Click to collapse
not saying that its not. im just saying that all is possible without a computer, thats all.

simms22 said:
not saying that its not. im just saying that all is possible without a computer, thats all.
Click to expand...
Click to collapse
True fastboot is not. Substitute methods, yes.
Sent from my Nexus 5 using Tapatalk