Database Info

One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!

One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!
Here's a new one click root. 2.4.0 now flashes clockworkmod recovery for you. It's also a little less likely to fail, and is tested to work on Froyo.
It will also work correctly if you are on a pre-rooted kernel. It will install superuser, busybox, and clockworkmod.
http://firon.net/xda/one.click.root.exploitv2.5.5.zip
Here's 2.5.0 of the one click root, now with the clockwork redirector integrated.
I cleaned up noobnl's script a little bit and ensured that adbd would run as root when booted into recovery. Also made sure we symlinked every single applet that recovery's busybox provides.
Now the one click also avoids pushing playlogo unless it detects that you have the old joeykrim root installed, to avoid any potential issues with future froyo releases.
Linux and Mac users users chmod +x run.sh and run it
THANKS FIRON
Here's 2.2.7, that simplifies the root process thanks to the discoveries here: http://forum.xda-developers.com/showthread.php?t=800483
I also increased the timeout after running the root (fails less), moved more things to /system/xbin to reduce the risk of breaking things, and removes all the old files leftover from joeykrim's root (including his modified playlogo that runs at boot every time).
It also means your system will no longer be mounted as read-only every time you reboot and there's no more problems with jk-su overwriting your existing su binary.
1. you need samsung galaxy s drivers
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
v2.2.4 added busybox and the remount script and fixes sprint animation not showing
2.2.5 superuser.apk & su added!
v2.2.6 installs busybox to xbin
uninstaller http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip

Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?

lordcyrus said:
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
Click to expand...
Click to collapse
no it doesn't break it

Gonna test this right now!

Sweet!!! Thanks!!! Going to do this after i get my epic after work.
Longest day ever!!!

OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.

Fixter said:
Gonna test this right now!
Click to expand...
Click to collapse
You first Boriqua.

Fixter said:
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Click to expand...
Click to collapse
updated the post and dl link!

NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.

Will this nand unlock?

vazquezcmp said:
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Click to expand...
Click to collapse
Odds are its 32 but heres how to check:
Click Start
Right Click Computer
Click Properties
Then look where it says System Type

32. Thanks man. I'm next.

Hmm.. Still not working.

Bring on the custom ROM's

Alright, well you needed to copy the folder to the Tools folder of the SDK.

I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????

jfenton57 said:
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
Click to expand...
Click to collapse
I'm not even seeing RUN2.

My phone went completely black. Not responding to anything.

I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.

GrandMstrBud said:
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
Click to expand...
Click to collapse
Download Titanium Backup.

[GUIDE][10/5/10]Comprehensive Guide to Rooting, Flashing, and Android Basics!

1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.​
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!

[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.

None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."

Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!

Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?

DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.

Good work! This should be a sticky!
Sent from my Epic 4G

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.

You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App

mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App

i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?

The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.

dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread

^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App

bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.

you might wanna add how to set adb

Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.

Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.

not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David

[GUIDE] Newbie's Step-by-Step: From Stock Cellular South Showcase 2 Kernel/ROM +

After bdemartino wrote his AWESOME thread for the Mesmerize it seemed only fitting that the Showcase get their very own... And since his Thread was Flawless, with his permission I'm mostly copy/pasting word for word.
THIS GUIDE IS SPECIFICALLY FOR THE SHOWCASE
If you're Looking For FROYO Skip down to the bottom of this post to the Section Labled FROYO!!!!!
Keep in mind there are many variations to each step, this is what worked for me the easiest.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps to Customize Your Stock Showcase (For Eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Showcase on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
I use Root Explorer
It's a few bucks, but there's hardly a day that goes by when I don't use it.. (Well worth the money)
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two Files you need from the bottom of this post
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/zImage /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the Showcase. This is just what works with our model.
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
Accessing Recovery!!!!!
NOTE: There are a few ways of getting into recovery mode. The easiest is to download QuickBoot.
Once installed you can install the widget to any homescreen or just use the app from the app drawer. Once you open the app, click Recovery and it automatically reboots the Phone into Recovery..
You may have to click the install update.zip (while you're on the stock kernel after Voodoo you won't have to anymore)
The other method, which you will need incase you EVER Bootloop! Is the 3 finger method (Hold down the volume up and down keys and the power button all at the same time when you're turning your phone on) Once you see the Samsung splash screen you can remove your finger from the power button, but keep holding down both volume keys!!!
Incase of Bootloop, remove the battery and do this while Rebooting...
AGAIN WHILE YOU STILL HAVE A STOCK KERNEL, YOU WILL PROBABLY HAVE TO *apply sdcard:update.zip* after you enter the FIRST RECOVERY...
The next Screen will be Clock Work Mod, this is where you will want to do your First Nandroid Backup!!!!
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
Now onto Installing a Voodoo Kernel
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
Now you can install Voodoo Control and get new life out of those earbuds!!!
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
4) Custom ROM : Download and install the ROM of your choice.
Right now we really only have 1 that I recommend..
It's Phidelt82's PicknPack Rom
This is a deodexed Rom which allows you to use MODS and themes. This ROM is 100% Stable, I've been running it for a WHILE with ZERO issues...
MODS/Themes/Customization
NoClock in the Status Bar
Midnight Theme
HoneyComb Digital Clock
Shutdown Animations or Images
Bootanimations with new Boot Sounds
Of course there is WAY more than these listed, but this should fill up your afternoon playing around with your new and IMPROVED Showcase!!!
FROYO FOR THE SHOWCASE = YUMMY!!!!
Yes, for those of you that didn't already know, thanks to Phidelt82 we now have Froyo!!!! I've been running it for about a week and it's Delicious!!!
I'm not going to Write as much as I did for the 2.1 b/c the directions are in the threads already.. Just follow the Directions, if you have any problems after that read through the threads and see if anyone's already figured them out...
And this will work with a Factory Showcase!!!!!
First of all you need to go to:
[Froyo-Odin] Showcase EB11 - Cellular South Update (be sure to Thank Phidelt82)
After this you will have 2.2, now you can use:
SuperOneClick to root your new Froyo Showcase (if you want)!!!
And if you plan on doing Mods/Themes/etc.. You should go ahead and Flash the EB11 Showcase Pick-n-Pack, again be sure to thank Phidelt82 for this!!!
If you flash the PicknPack Rom made by Phidelt82, then there's no need to root... It comes PREROOTED.. You only need to ROOT if you're staying on the Stock 2.2!!!
If you're flashing the picknpack do a Nandroid backup after you're done.... If you're going to stay on the Factory 2.2, do you a Nandroid backup after that...
Thanks to lmartin92, JT1134, Phidelt82, we now have a voodoo kernel with lagfix for 2.2 which can be found HERE...
If you're new to using voodoo lagfix kerenls.. Remember to always disable lagfix before doing Nandroid Backups/Restores/Flashing mods/Themes for YOUR SAFETY
I'm working on a few themes... sbrissen has already Made us the NoClock and NoAmPm mod (you have to be on the picknpack for these)
For a list of the Mods/Themes/Roms for the showcase look HERE
Always check the Mesmerize forums for new Android Development, Mods, Themes, etc...
And for help Don't be afraid to ask (after you've read this legnthy post) or drop by the #samsung-mesmerize channel at http://webchat.freenode.net/
Thanks to Phidelt82 for all of his dev support for our phone!!! If you want to donate to him click HERE
Thanks to bdemartino who wrote the AWESOME tutorial HERE that i mostly copied/pasted from!!! Be sure to click his thank you button if this helped you out...

Reserved FOR Me!!!!

Great work elijah, you are the Showcase king

bdemartino said:
Great work elijah, you are the Showcase king
Click to expand...
Click to collapse
my Kingdom sure is small lol

It is probably bigger than you think Elijah

ocs111 said:
It is probably bigger than you think Elijah
Click to expand...
Click to collapse
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069

I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse

ocs111 said:
I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
Click to expand...
Click to collapse
I'm hoping Bubbakoush will test since he has a showcase that needs to be flashed back to factory... I wouldn't recommend flashing this until after he can confirm it works

elijahblake said:
my Kingdom sure is small lol
Click to expand...
Click to collapse
Hey bro, don't think we're not around... I'm just enjoying my rooted Showcase, waiting for some more ROMs to give a try.
Thanks for all the work putting this together, and everything else you've been working on for Showcase!

Nice write up!

elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse
We're here... For the most part i'm waiting on a stable 2.2 or 2.3 based rom. Running pick-n-pack for now with Voodoo5.

Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.

blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
you more than likely are going to need to install Root Explorer onto your phone.. And use it to move the files (that's what I and many others had to do)

blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
Are you typing su first to grant root permissions? You should see a # instead of a $ at the prompt.
Sent from my voodoo froyo Mesmerize

I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?

blroberts228 said:
I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?
Click to expand...
Click to collapse
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
will Root Manager allow you to do this? If not Rootexplorer will.
if you do this:
I'm not sure if you can do this through terminal or not... I did mine from my pc... you may have to leave off adb shell and just start at su when using terminal...
This is making the file executable
adb shell
su
chmod 777 /sdcard/redbend_ua
while it's still on the sdcard (Before moving it then you don't need to worry about it)
Ok, it seems that the Mes instructions were infact different on this method... I've updated the first post... If you'll read now you'll see what you should be typing in..
sorry about that, and thanx for pointing it out

I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?

blroberts228 said:
I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?
Click to expand...
Click to collapse
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.

elijahblake said:
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=860250
look at that thread and tell me where you're at....

Yep, ive done all of that stuff also...and whenever I take the entire zip file, rename it to update.zip and reboot into recovery it tells me that the sdcard is busy

[STICKY]NEW Showcase Newbie Guide

After bdemartino wrote his AWESOME thread for the Mesmerize it seemed only fitting that the Showcase get their very own... And since his Thread was Flawless, with his permission I'm mostly copy/pasting word for word. as I am copying most of this from elijablake . . . so thanks this thread needs some editing, and I will be working on that in the future . . . . specifically the CWM / ROM manager which will not work. I could use some assistance in rewriting that part. TY!
BEST. ADVICE. EVER. #samsung-mesmerize on irc.freenode.net
<3<3<3<3<3
Also, read the Glossary for definitions and such. I was not the sharpest tool in the shed and it took me a while to find this . . .
Disclaimers
CSOUTH IS RELEASEING 2.2 UPDATE THIS WEEK (6/26). You may just want to wait for that to be released. This thread will be updated when the release occurs as how to flash recovery that you can flash roms with etc.
Keep in mind there are many variations to each step, this is what worked for me the easiest. READ ALOT BEFORE PROCEEDING WITH ANYTHING!!
There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
Steps to get to 2.2 (EB11) on your phone:
**Please note that the links were removed by CSouth for copyright (COPY WRONG *****ES) reasons. So if you can find the files somewhere (ahem . . . ) then you can follow these steps. THIS GUIDE IS PURELY FOR EDUCATIONAL VALUE, I DO NOT ADVOCATE BREAKING COPYRIGHT LAW.
I highly recommend using Heimdall rather than Odin. Don't ask me why . . . maybe because it has a command line utility and it is cross platform. So my instructions will be for using Heimdall.
After you have the downloaded files (from wherever you might have gotten them, you bad bad person) unzip and look for the following files:
-factoryfs.rfs
-modem.bin
-recovery.bin
-zImage
1) Put your phone in download mode by powering down your device, removing the battery, connecting the USB to your computer, and holding the volume down button. It shouldn't take long. You should see a little Android with a shovel.
2) In Heimdall, if using the GUI, put all of the files in their obviously appropriate spots. Don't worry if not everything is filled, just use the files that you have. (You should be using the repartition with the .pit file, the zImage with the Kernel, the recovery, and the modem)
If using the command line utility, cd to the directory where you unzipped the files and
Code:
heimdall flash --repartition --pit atlas_v2.2.1.pit --factoryfs factoryfs.rfs --kernel zImage --modem modem.bin --recovery recovery.bin
Wait for the process to finish, your phone will reboot at the end.
3. That is all, now your phone is updated to 2.2.1. Put the battery back in and boot your new shiny toy!
DO NOT DISCONNECT USB DURING THIS PROCESS AS IT COULD BE POTENTIALLY DISASTROUS!!! DON'T EVEN TOUCH IT AS I HAVE FOUND THE USB CONNECTION TO BE A BIT FLAKY!
Also, it is ok if it takes your phone what seems like forever to boot. This happens whenever you install a new kernel, just be patient.
If you have gotten the most updated batch of files, you should have the proper recovery to begin flashing. If not, well seek help . . . You should have RED RECOVERY!
See here for more information about CWM or go on irc.
To access recovery, you can use the three finger method. (Hold down the volume up and down keys and the power button all at the same time when you're turning your phone on) Once you see the Samsung splash screen you can remove your finger from the power button, but keep holding down both volume keys.
You should then go here to check out themes and mods.
Steps For Rooting either 2.1 or 2.2.1
Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
**NOTE: most custom roms come rooted, so if you are installing a custom rom in 2.2.1, you most likely don't have to go through these steps. Just flash to the ROM you want . . . ***
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Showcase. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
I use Root Explorer
It's a few bucks, but there's hardly a day that goes by when I don't use it.. (Well worth the money)
THE ECLAIR SECTION IS REMOVED AS CSOUTH IS RELEASING UPDATE THIS WEEK (6/27)

Hehmmmm....

nice write-up!

Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.

cpflow said:
Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.
Click to expand...
Click to collapse
Kies has 2.3 out now =)

Kies Mini have 2.3.5 out now for generic cdma showcase.
Sent from my SCH-I500 using Tapatalk
*Edit*
It seem everyone forgot about the Samsung Showcase Galaxy S Generic CDMA.
I managed to Root it flash CWMR and flash TSM TW 4.0 ROM. but then try to go back to stock and lost 3G. So I returned it and get a new one. No more mods for me I'm done no one cares about Generic CDMA.

Can someone provide directions to install a custom rom for a Showcase running stock 2.3.4? I don't have root. I'd really appreciate any help!

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.