- 4,431,022
REGISTERED - 32,753
ONLINE NOW
April 3, 2012 By: AdamOutler
Heimdall Suite, an Open-Source Cross-Platform set of tools designed to flash firmware to Samsung devices, has received an incremental update to version 1.3.2. This latest update supports Galaxy S II GT-I9100, Galaxy Player, Captivate, Vibrant, Fascinate, Mesmerize, Epic 4G, Galaxy S 4G, Infuse 4G, GT-I9000T, Galaxy Tab (7 and 10.1 inches) and of course the Galaxy S GT-i9000. If your Samsung device is not listed here, testing is required.
Heimdall has always been a favorite among kernel developers and those who frequently flash the latest kernels because no flashable update.zip or Odin packaging is required. A Heimdall user can simply put their device into Download Mode, and click a button to flash a new zImage directly. XDA Recognized Developer Benjamin Dobell‘s latest release improves compatibility with Loke (the flash receiver on the device) and expands comparability to several new devices.
In the words of the developer:
Version 1.3.2 addresses some compatibility issues with several devices i.e. the Galaxy Player 5.0 and Galaxy S II. In particular the “Failed to confirm end of file transfer sequence!” error should no longer occur under regular use. This was fixed by mapping a previously unknown protocol parameter, which I’ve now called “chip identifier”, to information in a device’s PIT file. A big thanks goes out to XDA developers user ambrice, who helped identify the cause of the issue.
Head on over to the original thread , get the source code , and check out the official product page.
January 22, 2012 By: PoorCollegeGuy
Ice Cream Sandwich might be taking its time rolling out to phones that don’t have a Nexus branding, but that hasn’t stopped Team ICSSGS from delivering their namesake, ICS for the Samsung Galaxy lineup.
They began their work nearly 2 months ago in November with the release of ICS on the Samsung Captivate and has been a solid run of bug fixing and new releases that brings us up to their Samsung Vibrant release just a few days ago, with a little ICS goodness for the Samsung Galaxy S i9000 folks in-between.
The builds themselves are incredibly stable and have very few, if any, issues with no custom themes or proprietary applications. The team has expressly stated:
We did not add any modifications unless they were absolutely required to make it work correctly.
This makes this the cleanest vanilla experience for the supported phones to date and provides options for those who want to give AOSP Android a shot.
For those who’d like to give their pure, unadulterated ICS AOSP builds a try, they have their work up for the original Samsung Galaxy S line of phones. You can check out their Samsung Captivate build here, their Samsung Galaxy S i9000 build here and, just freshly released, their Samsung Vibrant build here.
November 28, 2011 By: Sam Caplat
Ice Cream Sandwich ports are highly sought after, given the hype and price of the phone that runs it. However, providing there is support behind development, there is every chance you can run it on your device. This article is here to list the current ICS ports on our most popular forums and their individual stages in progress. Should your device not be listed below, you can always visit your device’s development forum on XDA and search for any ROMs listed with “Ice Cream Sandwich”. Check out our list! READ ON »
August 25, 2011 By: Will Verduzco
How would you like to create your own bootloader? Sounds a bit daunting, no? Aside from the inherent “cool factor,” having this ability could get your device out of some tough spots that would otherwise require the use of JTAG.
Thanks to the work of a team lead by XDA Recognized Developer Rebellos, this is now possible for Samsung S5PC110-based (read: Hummingbird) devices. Since there are quite a few Hummingbird-powered devices roaming about XDA, this can prove quite useful for when ODIN is not enough or if your JTAG pins are nonfunctional.
In the words of the developer:
What is it?
Info how to bypass secure booting mechanism built in S5PC110 CPU’s iROM on lowest level and create code loadable even with totally damaged bootloader, without use of JTAG.Okay, how useful is it?
I’ve got no clue, it all depends on you. Our main target, which is almost done, is ability to revive any hard-bricked hardware built on S5PC110 without use of JTAG (for eg. when JTAG pads had been damaged)
In order to get started, venture forth to the original thread.
[Thanks AdamOutler for the tip!]
July 4, 2011 By: mic_888
For those of you who haven’t made the leap to Gingerbread, for whatever reason but would really like to have WiFi calling on your Android device, check out XDA Senior Member Segnaro‘s latest work.
The XDA member, after spending many hours trying to get WiFi calling working on the Samsung Vibrant running Android 2.2.1 has finally succeeded! You’ll need to flash using CWM, and note that the mod was tested on the BiWinning 3.0 ROM.
The XDA member notes that you should test both WiFi calls and Normal calls are working and that WiFi calling does not force close.
Fore more information and to download the zip, head on over to the forum thread.
April 9, 2011 By: mic_888
Forgetting about setting proper permissions when pushing a custom framework can lead to some nasty problems on your Android phone as discovered by XDA forum member birgertime.
To avoid this in future, the XDA member has written a script to fix this in a flashable zip. Upon every boot, the script will scan /system/app, /system/framework and /data/app and set the proper permissions for all the files in those locations.
Note that after flashing the script, you may still be required to use adb to set the correct permissions in order for the script to work on every boot.
If you are interested in the actual script, the dev has also provided the code. For more information and to download the script, head on over to the forum thread.
March 17, 2011 By: mic_888
If seeing your MMS’s in your Vibrant call log annoys you, XDA forum member Br1cK’d has posted a ‘How To’ on stopping them appearing.
Based upon two other threads on fixing call logs by XDA members eury23 and Mammon88, the XDA dev has written a detailed tutorial on how to take the LogsProvider.apk from you ROM and decompile with apkmanager or a similar program.
You’ll need to navigate and edit the corresponding LogsProvider.smali file and then recompile being sure to delete the classes.dex.
For the detailed steps, head on over to the tutorial thread. Requires knowledge of apkmanager or apktool to decompile apk files.
March 10, 2011 By: orb3000
If you have a Samsung Vibrant device, this may be of your interest. XDA member connexion2005 compiled a great thread containing links to how to´s on video. Topics such as how to flash, backup and restore, how to soft UN-Brick any Galaxy S, how to enter recovery and download Mode, rooting, networking, and reviews.
No doubt a great thread to have in mind if you want to modify your device. Please say thanks or leave your comments.
Originally posted by connexion2005
[VIDEO] Samsung Vibrant Video How-To ThreadThis thread will serve as the OFFICIAL thread for all of my How-To tutorials for everything VIBRANT. Keep an eye out as I’m developing new videos on a daily basis. This will just be known as the central repository for all video tutorial links. Please post requests you’d like to see as well and if I’m capable, I’ll create them.
SIDE NOTE: There are many different ways and methods to do a number of the steps in my videos. I know this. I am illustrating what I feel is the easiest and most simplistic way to perform the steps to achieve the goal at hand. Constructive criticism is appreciated but remember, the target audience is a user who has no clue about how to complete the solution. Filler is included along with detailed info about steps to educate the user as well as instruct he or she.
Please consider donating as all of my work is non-profit and I do it for XDA and Android enthusiasts alike. I would have greatly appreciated these videos when I was a newbie and I’m sure you will to. Donation button is in my AVATAR to the left
Continue to the original thread.
January 20, 2011 By: egzthunder1
XDA member jmerchant informed us earlier today that there is something coming. Something that will hit all Vibrant users in the “happy” spot. Well, that last sentence came out wrong, but basically this will make them really happy. After months of speculations and complaints against Samsung and T-Mobile, it seems that the version of the Galaxy S will finally get a taste of Froyo… not just a port, but rather the full fledged official stock ROM. Vibrant users have been screaming for this pretty much since the release of the device as this OS release is supposed to come loaded with fixes to ensure that these devices perform in the way they were advertised to do so. As a little background, the device has had several issues including major lag, GPS issues, speed problems, and much more. As with any carrier/manufacturer update that we have seen coming out of every single player in the smartphone industry, the new update will likely come with new locks in place, to prevent rooting and such. To that I say, “developers…. start your engines!”
Do you think that this is happening for real? or maybe this is just an unfounded rumor like the many that have surfaced in the past. Leave us your thoughts and more importantly, let us know if you get the update.
You can find more information in the discussion thread.
Want something published in the Portal? Contact any News Writer.
January 4, 2011 By: mic_888
So you’ve got a Vibrant and you’re running FroYo, but you want to add a few more apps, tweak some settings, change launchers and all in one ROM.
Why not try out a new tool by XDA forum member birgertime? It’s a customisation tool for the Vibrant (currently for Windows only) and should work with any FroYo Vibrant ROM.
In order for the app to run, you must have Java installed. It’s a case of clicking through the tabs and selecting the options that you require. The app will generate a zip which you can copy to your SD card and flash with ClockWorkMod.
birgertime states that eventually the tool will work properly on Linux and OS X too. The program currently does have a large file size since it includes every single program – this may be optimised in the future so that the programs can be downloaded from the internet to make the utility much smaller.
The app is in alpha, and for more information including more screenshots and download link, head on over to the application thread.
January 2, 2011 By: mic_888
There are a lot of mods at XDA, and this one is for the Samsung Vibrant, courtesy of XDA forum member siirial.
If you fancy a front facing camera for your Vibrant, take a look at this mod – you’ll need a specifically compatible ROM for the front facing camera, the right kernel, a front facing camera (of course!) and be up for part dismantling your device.
The internal battery cover and Vibrant camera will need to be removed and cleaned out. The XDA member states that he used a metal flat head screw driver, however you should proceed with extreme caution.
For full instructions including compatible ROMS, kernels and where to source a front facing camera, head on over to the modification thread.
December 24, 2010 By: egzthunder1
It seems that Samsung cannot get away from problems with the Galaxy S devices. Some of the most common things that you will see if you went into any of the Samsung S fora would be issues with GPS, lag, and more. The kiss of death for any hardware manufacturer happens when the device begins to exhibit hardware flaws, limitations, or failures, with the latter being the worst. There have been numerous reports from many of our members that the Bell variant of the Vibrant has issues with the internal SD failing. Upon contact with Samsung, many users were prompted to ship their devices back to the manufacturer where they traced the error back to a faulty motherboard or even a bad flash, which required them to use Samsung tools to reflash the devices. Others have reported Samsung blaming the failures on the Froyo updates.
The truth of the matter is that none of these seem to be neither the root nor the cause of the problems. Many members, including XDA member An Droid have been wondering about this and decided to create a poll asking others who may have experienced this premature failure what their take on this was. The results do not match with what Samsung is saying. For instance, people have been having similar issues even before the Froyo update, and as for the ones who sent their device to Samsung for repairs (whether it is a new flash or a new motherboard), units have been reported to fail once again.
The whole thing points to the internal SD storage card failing, which in essence will prevent Android from booting. This has been confirmed by many, and since proper root cause analysis seem to not be taking place, XDA member arr0ww has taken this matter into his own hands by starting a formal complain against Bell and Samsung.
I have been in contact with Chris Olsen from “Olsen On Your Side” from CTV about our issue with the i9000m sd card failures.
He has suggested that the best way to go about sending proper complaints is to go through the Commissioner for Complaints for Telecommunications (CCTS). The Commissioner has the pull to start pushing these big companies around. The Commissioner already brought a case against Bell for the National Do Not Call List that Bell did not abide by.
Chris Olsen will contact the Commissioner in the new year to see how many complaints he has received.
So, what do you think? Should Samsung pay attention to their customers and maybe try to see if the internal SD is at fault? Leave your comments below.
If you are having this problem and would like to participate in the complain, please follow the instructions in this thread.
Want something published in the Portal? Contact any News Writer.
Thanks AllGamer for the tip 
December 24, 2010 By: mic_888
If you’ve been getting a bit bored of the same old lockscreen and have recently upgraded to the leaked JL5 firmware on your Samsung Vibrant, check out this mod from XDA forum member untermensch.
The LockScreen mod is specifically for the recently leaked JL5 firmware and the dev has helpfully given users a choice – you can pick the deodex zip file for custom ROMs or the stock zip file if you flashed with Odin or Heimdall.
Additionally, uploaded is the source zip file, which is for developers looking to port the mod to other ROMs and devices.
Please note that the framework-res.apk is a little larger, so you will need to ensure to allow enough memory on the system partition in order to install.
For more information and to download the file of your choice, head on over to the modification thread.
YouTube
Follow
Like
Google+
