Thanks Revolutionary for the exploit, Denys Vlasenko/chris41g for busybox, ChainsDD for su,
chris41g for EG30/EG31/EK02/EL13/EL26+CWM5(repack), JoshMiers for no-CIQ scripting,
squshy 7 for EG31, Przekret for EG30/EL26, kingsway8605 for EK02, LuffarJoh for EL13,
puertoblack2003/Przekret for EL29, calkulin/acs for FB15/FB17/FB21/FC06/FC14/FC18/FC22/FC24/FD02/FD05,
qbking77/acs for FB27, hunterkiller/sextape for FC05/FC07/FC13/FC15/FC24/FF02/FF18,
Steady Hawkin for EL26/EL29/FB15/FB17/FB21/FB27/FC06/FC07/FC18/FC22/FC24/FD02+CWM-Rogue(repack)
agat63/chris41g for FF02/09/11/18+CWM-agat
This guide is for directly rooting EG30/EG31/EK02 (NOT EL13/newer) Android for the Samsung E4GT using a 100% automated script.
If you want a Rooted EL13/newer+CWM use the appropriate pre-rooted ODIN thread [EL13/EL26/EL29],
then come back here and use Option C to install EL13/newer+CWM (NOTE: a GB kernel/zImage will NOT allow an ICS ROM to boot)
If you want a Rooted FB15/newer+CWM use the appropriate pre-rooted ODIN thread
then come back here and use Option D to install FB15/newer+CWM (NOTE: an ICS kernel/zImage will NOT allow a GB ROM to boot)
This root method uses your EXISTING kernel/initramfs/recovery/rom, so it shouldn't suffer from LOS (unless you had LOS with stock to start with)
Nothing is flashed, so you just get your existing setup with the addition of ROOT.
This will NOT trigger the Yellow Triangle nor will it increase your ODIN flash count.
If you are on Mac or Linux see Reference Section B
If you want CWM see Reference Section C (to install an official OTA update, reinstall the non-CWM version PRIOR to accepting)
Videos by qbking77 [Install Root / Install CWM] thespotlite [Install ANY User-Provided zImage/Recovery]
[Optional] If you are looking to start fresh, first perform the appropriate ODIN Restore
0) Backup anything important
With this particular ROOT procedure there is very little chance something bad will happen, but it is good practice to backup before making any changes.
1) Prerequisites Checklist
USB Debugging is ENABLED - [Menu->Settings->Applications->Development->USB debugging]
USB Storage Mode is OFF - [Drag down the notification bar and tap on "USB Connected" - should be off by default - pic]
Samsung [USB/Android drivers] are INSTALLED
Phone is connected to USB port and recognized
2) Download the E4GT automated rooting package
Lite versions contain EG30/EK02/EL26/EL29 and 3 latest versions of ICS (most people will use this), Full versions have all versions
NEW: Even easier self-extractor for windows (Just run .exe - SKIP Unzip and Step #3) e4gtauto-sfx.exe [Lite / Full]
Download the E4GT automated rooting package e4gtauto.zip [Lite / Full]
UNZIP to top-level directory of your C: drive
Note #1: zergrush is a known exploit being used to root your phone. Your Anti-Virus software may quarantine or cause the download to be incomplete. Disable your Anti-Virus software if needed so the download can complete.
3) Run the E4GT automated rooting package
From PC command prompt, run "runfirst" and select Option A:
(if you have an aversion to typing, you can use file explorer to navigate to C:\e4gtauto and double-click on RUNFIRST.bat)
c: cd \e4gtauto runfirst
4) You are DONE!
You can now use market apps that require root. To unroot, redo Step #3, use Option B. If you want CWM, see Reference Section C
Note #1 - Keep in mind, should you CHOOSE to run "su", you MIGHT be prompted for permissions on the phone's screen the first time it is run. If you don't realize that, you'll get "permission denied" and think the root didn't work. Make sure your phone is NOT on the lock screen or you won't see the prompt. It is NOT required that you run "su". You ARE ROOTED regardless.
Note #2 - It is suggested you run your phone as "stock rooted" for at least 1 day before you start installing custom ROMs. This will help you narrow down issues should they arise. Also be aware that some custom ROMs install their own BootImg/zImage/Kernel/Recovery so the "stock" Kernel+CWM you installed using this tool might get overwritten. If you experience kernel-related issues, see if your custom ROM included a zImage.