The second I saw this story on the XDA thread, I envisioned many Verizon Samsung Galaxy S III users giving Verizon the proverbial middle finger. This locked bootloader issue with Verizon’s Samsung Galaxy S III has certainly made a full circle. It started off with many angry customers when Verizon formally announced that the bootloader will be locked on their Galaxy S III, but soon after there was hope as a couple of miss-informed Verizon and Samsung reps told various people that an update for the S III would be out soon that would unlock the bootloader. Verizon quickly denied that rumor and left us all with the hopes of XDA soon finding a way to crack Verizon’s lock on the bootloader.
Well folks, that day has come as the XDA developer by the name of AdamOutler has released instructions on how to unlock your Verizon Galaxy S III’s bootloader. Before I give you all the instructions, it’s important to first read AdamOutler’s precautionary statement first:
Let me make this clear. If Samsung updates your device’s bootloaders, using this tool could potentially brick your device. Once you apply this, never accept a factory update without first flashing the Odin Packages in the Original Post of this thread. As a general rule, you want to be the last guy to apply any Samsung update. Run custom.
As of the date of this posting, this works great on Linux and it should work wonderfully on Mac too. If you’re using Windows, I recommend downloading Windows Ubuntu Installer(WUBI) to install Ubuntu from within Windows.
First you’ll need to download the file needed for this:
If you have a Samsung Galaxy S II phone that is running a custom Jelly Bean ROM, you have probably noticed that you do not have NFC capabilities on your device. If you would like to restore that functionality, we have good news – XDA Senior Member jthatch12 has created a hack.
This will only work on phones that had the necessary NFC hardware built into the phone. The other requirement is that the phone is running Jelly Bean. Thus far users have confirmed success on i777 and M250k/M250s devices. The hack should work on:
- i9100 = NO
- i9100P = YES (it’s an i9100 exactly, but with NFC. ROMs for i9100 will work, but need to be modified to show NFC settings, otherwise no NFC options will show)
- i9100G = NO, it’s completely different from the i9100 hardware (TI-OMAP instead of Exynos). ROMs from i9100/P don’t work.
- T989 (T-Mobile GS2) = YES, but it’s completely different from the i9100 hardware (Snapdragon S3 instead of Exynos). ROMs from i9100/P don’t work.
- i777 (AT&T GS2) = YES, AOSP based roms have it but i9100 hellraised roms are missing it(due to NFC not being a feature of the i9100)
- D710 (Sprint GS2) = NO
If you are interested in trying this hack out on your NFC equipped Galaxy S II, you just need to download the file from the XDA forum thread (use source link below) and then flash it onto your device from recovery mode.
source: XDA Developers Forum
While reading all the reviews and hands-on articles about the Google Nexus 7 revealed last week at Google I/O, readers may have noticed the device runs the Android 4.1 Jelly Bean phone interface. That seems to be an odd choice for Google to make and has prompted users to work on getting the tablet UI onto the device. XDA forum member SladeNoctis has figured out a relatively simple way to accomplish this task as outlined in the source link after the break.
As we’ve seen over the last few days, folks are hard at work creating Jelly Bean ROMs for a variety of devices. Up to this point, work seems to be limited to smartphones or Nexus tablets. That appears to have changed with some work done by user randomblame over at XDA. He has succeeded in creating an SDK port of Jelly Bean for an Acer Iconia A500. It is not yet ready for daily use as several items are still not functioning, including audio, wifi, sdcard access, and usb mounting of flash drives. While work continues on those issues, users can at least get a taste of Jelly Bean if they are willing to root their device and install the ROM. Hit the source link for instructions and access to the files.
The HTC One X has gotten itself an SDK port of Google’s Jelly Bean firmware thanks to the XDA developer by the name of tgascoigne. At this point it’s nothing you can use as a daily driver, but serves as a great way to get yourself a nibble of Jelly Bean if you’re a One X user. Many things don’t work such as the camera, WiFi, audio, and much more. The developer has stated that he’s already working with the actual Galaxy Nexus OTA of Jelly Bean ported to the One X. If he’s able to get that working that build should be far more superior than the current SDK build. If you don’t mind your phone pretty much unusable but still want to give Jelly Bean a shot, then head on over to the XDA thread and flash away. Of course, needless to say, your One X will have to be rooted and the boot-loader unlocked in order to flash the ROM. You can also watch the video at the bottom to see this port in action.
One of the casualties of Apple’s war on Android was a court order forcing HTC to remove any hyper-links derived from data like phone numbers or email addresses within Sense. While we could go on all day about how ridiculous a decision this may have been, we’re here to fix problems not dwell on them. As usual, the wizards over at XDA have found a solution. XDA user Steal25 came up with a simple build.prop edit that will turn the functionality back on, just like it was before Apple’s legal assault. The current method works with the EVO 3D, the One X and the Evo 4G LTE, but should work with other crippled HTC phones as well. Let’s dig in.
Want to make your Galaxy Nexus screen appear even bigger than it already is? Then you need to check out this awesome mod created by Rootz Wiki member CurrentWeb. What he has done is create a flashable .zip file that will trick your ROM into thinking your GNex is actually a tablet. This means that instead of having the typical status bar up top and the navigation bar at the bottom of your screen, you will now have the exact same layout as any Android tablet. The nav buttons and status bar will be moved to the bottom, your app drawer and Google search will be up top, and you will have more room to place apps on your home screens. It seems that this would make more sense in landscape mode but actually looks pretty good in portrait mode, too.
There is already a large list of compatible ROMS and the developer plans to keep adding to it. If you are running any of the more popular ICS ROMS right now you will be pleased to see that it is most likely already supported. All it requires is a simple flash over your current ROM and your up and running in tablet mode! The developer is even working on some sort of toggle so that the mod can be turned on or off with a simple reboot. I don’t know about you but I think this is a pretty sweet idea and may give it a go later today barring any major user reported issues. As it stands right now, some ROMs are having a few issues but the dev is looking into all reported problems. If you’re ready to check it out for yourself hit up the source link below.
source: Rootz Wiki
OK guys, I finally got around to creating this how-to video on getting your ASUS Transformer Prime all ready for modding! In this video you will find directions on how to root, unlock, and flash ClockworkMod Recovery to your tablet. This all-in-one tool, ViperMod PrimeTime v4.5, will do everything I just mentioned and can even unroot your Prime in case you need to send it in for service. This tool works on any version of ICS, and will even work on Honeycomb. For those of you OG Transformer owners, you can even use the root tool as well but do not try to flash recovery. Reports show that trying to flash recovery will bork your original Transformer (TF101).
Once rooted, you will not loose the ability to receive future OTA updates from ASUS, but it is highly reccomended to grab Voodoo OTA RootKeeper from the Android Market to prevent any future updates from breaking root. You can find the download link at the end of this post.
Big thanks to ViperBoy for creating this super easy tool, it’s by far the easiest method available for doing any or all of these steps. You don’t have to complete every step if you dont want (i.e. remain locked), and if you are already rooted or unlocked you can still use the tool’s other features as well. I will include brief instructions below, but for a more detailed walk-through refer to the video. You can also find the necissary download links at the end of this post. Ready? Lets get started!
I am sure many of you are familiar with Dr.Dre’s Beats Audio line and that HTC bought exclusive rights to integrating the audio improvement software in their devices. I’ve heard people say that their HTC/Beats device provides a sound that is unmatched to other devices they have owned and I’ve also heard folks say the improvement isn’t even noticeable. While I am still on the fence on whether or not this software actually makes a noticeable difference, at the same time I have yet to couple the experience with a quality pair of headphones. Either way, the Beats Audio software is no longer tied to just HTC devices and is now flashable for non HTC owners to enjoy. Now you can be the judge on whether or not HTC spent their money wisely.
Since Beats Audio is nothing but software, thanks to XDA members fuss132 and willblake13, we now have an easy way to flash Beats Audio to any rooted device running a Gingerbread ROM. It’s pretty simple really, all you need to do is hit up the XDA link at the bottom of this post, download the .zip file, and flash through CWM. Not much to it. The real question is whether or not you will notice a difference. Although fuss132 takes a similar stance as I do and says “I think at some ponts beats audio is only a audio marketing strategie,” he also claims “The sounds will be more natural, playing with more clarity.” However contradicting that may sound, he includes some test results that clearly show that there is some level of improvement to be gained. So if you’re the flash-happy type of person I think you are, you should check it out and decide for yourself. Test results after the break.
Beat on my friends… Beat on
Update: It looks as though this didn’t bode well with someone (most likely HTC) and the thread has been removed from XDA already. If you have more insight please let me know, I am curious.
Last week we reported that the most recent Chrome Beta update broke compatibility for some custom Android 4.0 ROMs. The update proved to be beneficial on devices that are running stock ICS so I wanted to figure out a way to get it up and running on my rooted Galaxy Tab 10.1 running a CM9 kang. Apparently some of the custom ROMs have a build.id and display.id that reflect an Android version other than ICS even though they actually run Android 4.0. There is a simple workaround for this and I will give you a quick walk-through in the video below. Basically you will just need to make sure your build.id and display.id read IML74K.
If the thought of editing your build.prop file sounds daunting to you, maybe you should just wait until the developer updates the ROM in the future. If this sounds like something you can handle then check out the video and let us know in the comments if it worked and what ROM you are running. By the way, anything you do to your device is at your own risk, myself or Talk Android will not be held responsible for any problems you may encounter. Happy hacking! :-D
Video after the break.