How to root the Samsung Exhibit 4G SGH-T759

If you’re dying to root your Samsung Exhibit 4G SGH-T759 but you’ve got no idea how, you’ve come to the right place. Whether the Exhibit 4G is your first Android phone, or you’re not just confident in rooting it, this rooting method is one of the easiest available. We’ll also give you the instructions on how to install ClockworkMod Recovery for you to enjoy the full Android experience. Just follow our instructions and you’ll be well on your way to customizing your Exhibit 4G.

For those of you who are unfamiliar with the term, rooting is the process by which you regain administrative access to your phone. One of the main reasons why Android users root their phones is to gain freedom and control as well as the ability to tweak the phone just the way you like it. You can even improve your device’s performance, alter system files and choose to install applications to your SD Card. If you’d like to read more about rooting, you can read our “Rooting for Dummies” guide.

Requirements

Samsung Exhibit 4G SGH-T759
A Windows PC
Make a backup of all your important data in case anything will be lost or corrupted during the rooting process.
Fully charge your Exhibit 4G’s battery. This prevents your Exhibit 4G from shutting off in the middle of the rooting process.
Enable USB Debugging. You can do this through “Settings > Applications > Development > USB Debugging.” The USB Debugging box should be ticked.
Enable Unknown Sources so you can install apps from third-party sources. You can do this through “Settings > Applications.”
Get the ADB USB drivers (TMO_T759_ADB_Tether_Drivers.zip, 3.7 MB) and install them to your PC.
Download the Rooting package (Zerg rush root.rar, 890.5 kB) to your PC.

Instructions

Extract the contents of the rooting package into a folder on your computer. You will need a RAR extraction program (e.g., WinRAR) to extract the files in the archive.
Connect your Samsung Exhibit 4G to the computer using a USB Cable.
On your computer, open the folder where you extracted the contents of the rooting package. Inside the folder you will find a file named ZergRushTempRoot.bat.
Double-click on the ZergRushTempRoot.bat file to launch it.
A command prompt window will open. Follow the instructions on the screen.
It should take about 5 minutes to root your Exhibit 4G.
On your phone, download and install the Root Checker app from the Google Play Store to determine if you’ve got root. Tap on the Verify Root Access button on the app and it should inform you if your device has got root access.

Congratulations! You have now successfully rooted your Samsung Exhibit 4G SGH-T759.

NEED TO KNOW!

Comments

Jamesksiazek

How about a list of programs that can safely be deleted or anything else to help improve performance?
Shotguncodeman

I think it’s bull that u have to have a computer to root, I don’t got one, they should figure out a way to do it without one
Abhirathod95

also should add unmounting SD card… some phones wont do it unless its unmounted… its in the settings and sd card i think
Jesbyjop

al hacer esto afecta la red de la operadora del telefono?
ps el mio es un t mobile y lo tengo trabajando con claro
http://www.facebook.com/profile.php?id=100001724315131 Donny Ray Hedge

if its rooted can any SIM card work on with it? i know before it was rooted i couldnt put my sim card in cause it was locked…will my sim card work with a rooted phone?
Mhanson

Went to download rooting file and got this

High security alert!!!

You are not permitted to download the file “Zerg_rush_root.rar” because it is infected with the virus “Linux/Lotoor.AH!exploit”.

URL = dl.xda-developers.com/attachdl/6bd32049ae48122b054392fdd8e1cd21/4fdb7534/7/5/9/5/1/8/Zerg_rush_root.rar

File quarantined as: 3f63f69d.[fortianalyzer].
drew

Does anyone know if there’s a CWM Recovery for the Exhibit?
http://www.facebook.com/josh.mccue1 Josh McCue

I opened the command prompt and the only instructions on the screen were “press any key to continue”. I did that and absolutely nothing happens.
Mr Riggs

Is this post still monitored? I followed this guide along with others and I still get nothing, it does restart the phone, followed instructions but it never roots, the terminal app is there but no superuser app, its weird, rooted many phones but for some reason this is my third attempt at this phone and get nothing..:( any ideas? THANKS!
Brian

I have gingerbread 2.3.6. on my Samsung Exhibit 4g. I believe this version has been patched to close the known exploits. SuperOneClick, and Zerg Rush haven’t worked for me. Still looking for a solution.
- Auralius
  
  Same here… rediculous. nothing works. Adb registers my devce as 0123456789abcde
  - zx6guy
    
    See my response above.
jamann

will this method work on the exhibit 2 4g as well??
jarey

all I get is adb wait for device
Freelnsky

Did nothing
http://www.longren.org/ Tyler Longren

This is such a crap phone. No dev community at all. Stay away from this phone at all costs, unless you enjoy running stock everything. Even stock doesn’t work very well.
- zx6guy
  
  Are you running 2.3.6? If so google “root samsung exhibit 2.3.6″. I rooted mine last summer but don’t expect any huge performance increases.
  - http://www.longren.org/ Tyler Longren
    
    Yes, its running 2.3.6. It’s my wife’s phone, and she’s had more problems with it than any other phone. No service, constant random reboots, people can’t hear her.
    
    I’ve got a Nexus 4 and that’s probably what I’m going to buy her as well.
    - zx6guy
      
      It only has 512MB of ram so you don’t keep an eye on running programs it’ll become a slug and behave strangely. Also, I forget which radio it has but its not as fast as the 42 M/bit unit in your N4. Its something like 14M/bit and you’ll be lucky to see half that IRL.
FUCK THE SAMSUNG EXHIBIT

[**] Zerg rush – Android 2.2/2.3 local root

[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0×00025118

[+] Found a Samsung, running Samsung mode

[*] Scooting …

[*] Sleeping a bit (~40s)…

[*] Waking !

[*] Sending 149 zerglings …

[+] Zerglings found a way to enter ! 0×10

[+] Overseer found a path ! 0x000257c8

[*] Sleeping a bit (~40s)…

[*] Waking !

[*] Sending 149 zerglings …

[+] Zerglings caused crash (good news): 0x40219cd4 0×0054

[*] Researching Metabolic Boost …

[+] Speedlings on the go ! 0xafd2563d 0xafd390ef

[*] Sleeping a bit (~40s)…

[*] Waking !

[*] Popping 24 more zerglings

[*] Sending 173 zerglings …

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

+++ LOG: write failed (errno=14)

[+] Rush did it ! It’s a GG, man !

[+] Killing ADB and restarting as root… enjoy!

AKA DOES NOT WORK… >_> This phone is shit… Can’t fucking do ANYthing with it. And it doesn’t even work good on it’s own…

Tip Us!

How to root the Samsung Exhibit 4G SGH-T759

Requirements

Instructions

WRITER

WRITER

NEED TO KNOW!

categories

popular devices

useful links