POSTS TAGGED: Samsung Epic 4G Touch
Posted August 31, 2012 at 11:00 pm by jerdog
While running CyanogenMod on a CDMA device has many advantages, one glaring disadvantage is the ability to update your PRL (Preferred Roaming List) or data profile, which are only available via stock ROMs. Often times if you need to run a GPS fix or update your PRL, you need to backup your CM9 install, restore to a previous stock ROM, do the ROM dance, run the desired process, dance a jig, restore to CM9 install, and hope for the best. Well now you don’t, thanks to the Epic Touch CM team.
The Epic Touch CM team has put together a nice temporary ROM which boots the FF18 stock firmware from the /EMMC partition on the Samsung Epic 4G Touch without changing your current ROM. This temporary ROM allows you to do the follow. . . READ ON »
Posted August 23, 2012 at 04:00 am by Former Writer
For those who haven’t heard, there have been some issues with Samsung ICS leaks and brick bugs. The Samsung Epic 4G Touch was no exception to kernel- and recovery-related issues. When CM9 ROMs were were first coming out on the Epic Touch, they didn’t come with a custom recovery. To flash to a different ROM, users had to flash a Gingerbread kernel containing the proper ClockworkMod recovery, and then use that recovery to flash to a new ROM. This is because the kernel being used suffered from similar issues as the hard brick bug on other Samsung devices. Thus, it meant that trying to wipe and flash a different ROM could result in a hard brick. That problem is now solved.
Posted August 20, 2012 at 09:30 pm by Former Writer
When flashing an AOSP ROM on a CDMA phone, it’s a win-some lose-some affair. You gain the functionality that comes with a pure Android experience. However, you traditionally lose USB Modem and Diagnosis Mode on your device. For those who are unaware, USB Mode and Diagnosis Mode are accessed via codes you enter into the dialer. This is not only required to activate the phone on some networks, but also helpful in alleviating some problems like restoring your IMEI using QPST. However, for many Samsung devices, that is no longer a problem. Now, you can get all this functionality back without flashing back to a stock ROM.
Posted August 15, 2012 at 04:00 pm by Former Writer
There is not much more painful to the eyes than turning on a bright display in a dark room. There are applications out there with Night Mode, but they don’t always work optimally—often eliminating colors, which makes things more difficult to read. This is a problem that the Samsung Epic 4G Touch no longer need experience.
XDA Senior Member arpruss has developed an application called GalacticNight. It requires root because it modifies the mdnie* files to adjust the colors for proper night vision. Arpruss explains the application more in depth:
. . . READ ON »
I know there is ChainFire3D, which is a great app, but this is better for nightmode. ChainFire3D does nightmode by simply dropping the green and blue col
Posted August 10, 2012 at 08:00 am by Former Writer
It would be redundant to mention yet again how prolific the spread of Jelly Bean has been over the last month and a half. With devices old and new, low spec’d and high spec’d alike, getting usable ports, it seems like almost any device is capable of running Google’s latest and greatest. To add to the already long list of devices, the HTC Flyer and EVO View 4G along with the Samsung Epic 4G Touch now have their own Jelly Bean ports.
The EVO View 4G and Flyer ports were both created by XDA Senior Member Dexter_nib with the help of several other members and developers. The Epic 4G Touch port was made by XDA Recognized Developer Sbrissen, who also helped out with AOSP ICS. Despite being early releases, bot. . . READ ON »
Posted June 8, 2012 at 04:30 pm by Will Verduzco
By now, you’ve undoubtedly heard about the Samsung HardBrick bug that has reared its ugly head on various Samsung Exynos 4210-based devices including but not limited to the Galaxy Note GT-N7000, Epic 4G Touch, AT&T Galaxy S II, and the Korean SHW-M250S/K/L. In fact, we recently featured an app made by XDA Elite Recognized Developer Chainfire aimed at determining your particular device’s risk for hard brick.
Samsung is aware of the issue, which was first noted by Elite Recognized Developer Entropy512, and is in the final stages of delivering a solution. Until then, however, it is still advised to not flash any leaked kernels, or kernels in which MMC_CAP_ERASE is presen. . . READ ON »
Posted June 6, 2012 at 04:30 pm by Will Verduzco
By now, we’re all familiar with the hard brick bug that’s plagued various Samsung when updating to leaked builds of ICS. The bug has shown up on various Samsung Exynos 4210-based devices including the Galaxy Note GT-N7000, Epic 4G Touch, AT&T Galaxy S II, and the Korean SHW-M250S/K/L.
However, as we quickly found out, not all eMMC revisions were equally afflicted. Instead, the 0x19 revision was highlighted as known bad, whereas the 0x25 is thought to be safe. Revisions between 0x19 and 0x25 are thought to be possibly bad, whereas those newer than 0x25 are probably safe. Adding insult to injury, those keen on hex will be quick to notice that 0x19 converted to decimal is 25!
Naturally. . . READ ON »
Posted May 23, 2012 at 11:00 am by Former Writer
The Team Win Recovery Project has been picking up major steam for awhile now. And since its update to version 2.1 that we covered not too long ago, it’s been getting closer and closer to being one of those must have recoveries on newer devices. Unfortunately however, not every device has made the list quite yet. That doesn’t mean it can’t be.
Samsung Epic 4G Touch users have been clamoring for a TWRP 2.1 release for some time now, and XDA Recognized Developer Dees_Troy wants all the Epic Touch users know that Team Win is listening. While Team Win can’t personally get the recovery working on the Epic Touch, as they don’t have the Epic Touch to test it, Dees_Troy wants to spur the devi. . . READ ON »
Posted May 18, 2012 at 09:00 pm by egzthunder1
Since the latest leaks for the Samsung Galaxy S2 line up have been hitting us left and right, people have been jumping between ROMs—mainly between buggy, pre-release ICS builds and very stable GB. This is, after all, what we do on XDA as a habit: We see a leak, we flash it, we use it, and we tweak it. If it doesn’t fly, we simply roll back. Of course, there is always an inherent risk in flashing stuff that should not be on your device in the first place, but the risk of fully bricking a device in this day and age is rather small. Especially, since there are tools available to bring your devices back from the dead, such as UnBrickable Mod by XDA Elite Recognized Developer AdamOutler.
Having said this, no. . . READ ON »