October 9, 2012 By: Joseph Hindy
It’s quite common for a hacked phone to not play nicely with OEM software created to interface with the devices. Notable examples include HTC Sync and Samsung Kies. When a phone is rooted and running custom firmware, these services may not read the phone properly and may not recognize the device as one that needs an update. In rare cases, they don’t even recognize the connected device as supported. Samsung Galaxy S Blaze 4G owners have been having a problem with Kies recently, and now there is a fix.
Okay, to call it a fix may be stretching it. XDA Forum Member jparnell8839 has figured out that Kies won’t recognize the phone on any stock firmware after UVLB7. So if you’re running something that came after that and want the next official update, you will run into an error where Kies claims the phone isn’t compatible with their software upgrade service. Says jparnell8839:
Finally, I thought “hmmm, it still says custom binary when im in download mode, even though I’m stock with stock recovery” so I went to sammobile and got the pre-july 16th image (UVLB7) and flashed just the tar.md5 file (no pit) made sure repartition wasnt checked, etc. in Odin
upon reboot, Kies immediately recognized there was a firmware update and pushed me up to UVLF4 (flash counter is at 4 btw). When it rebooted to download mode from Kies, it said Samsung Official binary this time
In order to be more helpful, jparnell8839 has uploaded the firmware that was used to fix this problem for others to download and use. With it, stock users can upgrade to the next update easily. For more information, go to the original thread.
April 11, 2012 By: Will Verduzco

Recently, we’ve seen quite a flurry of development activity for Samsung Galaxy S Blaze 4G. As the little brother to the T-Mobile Samsung Galaxy S II, the Blaze is not exactly Samsung’s flagship device on Magenta. However for those looking for a powerful device with a less huge screen and a lower price tag, the Blaze packs quite a punch that may make other, higher priced smartphones a bit nervous. Featuring a powerful 1.5 GHz dual-core Snapdragon S3 processor and 42 Mbit HSPA+ connectivity, the Blaze certainly lives up to its name.
Now thanks to the burgeoning development community, we have root, recovery, and a return-to-stock ODIN package. Given the development activity and countless requests from our awesome community, we saw it fit to give the device a home on our forums. If you already own or are interested in picking up the Blaze, head over to the Samsung Galaxy S Blaze 4G forum to get started.
March 31, 2012 By: Joseph Hindy

It’s always exciting when the development of one devices causes positive change in the development of a different device. Sometimes rooting a device means getting new software to older phones, as is the case with the Sony Xperia Line Up, and it’ll happen with even more phones in the future.
This is now happening for the T-Mobile Samsung Galaxy S II. XDA Forum Member johnrbell has just announced that the Galaxy Blaze has been rooted. While the Blaze isn’t the most popular phone out there, there will be some users happy to hear that and awaiting the method to be made public for future use.
However, the meat and potatoes of rooting the Galaxy Blaze, for most users anyway, is the radio. XDA Recognized Developer Master&Slave™ has pulled and posted the radio from the Galaxy Blaze, which has been a long awaited development for T-Mobile Galaxy S II owners. In his words:
-My Data has increased by about 4Mbps, which is a + in my case
-Dont ask me for screenshots
-Tested after removing my build.prop and init.d data tweaks for true results.
-Speeds will vary depending on your location.
Users looking to get a new modem on their already rocking SGS2 can head on over to Master&Slave™’s modem thread for the downloads and discussions about the modem. Currently, the modem is being tested without ROM tweaks to see the true benefits, but with a 4 Mbit increase in speed, results look promising. Before flashing, be sure that you have a real T-Mo SGS2 modem handy in case something goes wrong that you can revert to.