Database Info

{TUTORIAL} How I rooted my Epic using "One Click Root"

I take no credit for figuring out how to root the Epic, nor do I take any credit for creating the .bat file.
All credits go to joeykrim for the manual root. And noobnl for the .bat file.
I was having trouble rooting as many of you have been but I have figured out a simple solution that actually worked for me and I hope it works for you.
[STEP 1] First you need to make sure you have android's latest sdk. You can download it at http://developer.android.com/sdk
[STEP 2] After installation (if i remember correctly) sdk should of been installed into the root of your hard drive, normally (C:/). It will be labeled "android-sdk-windows" if you installed the windows version. To make things a lot more simple, you can rename this to "sdk". Anyways, download and install the Samsung Galaxy S drivers. This is the one I installed. http://www.mobile-stream.com/beta/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
[STEP 3] Go over to "One click root for the Epic 4G! v2.2.4 Now has Busybox & remount scripts!" and grab the latest zip file. I used v2.2.4.
[STEP 4] Extract the folder to the "android-sdk-windows" folder and rename it to "epic". Or something smaller if you want.
[STEP 5] Next open up command prompt (cmd). Start/Run/cmd or start/all programs/command prompt.
[STEP 6] In the command prompt, type "cd \sdk\epic" (sdk, and epic are to be replaced with what you have the folders named). Do not close command prompt.
[STEP 7] Type run.bat and let it do its work.
[STEP 8] Once the phone is rebooted, keep the phone connected and in that same command prompt type "adb shell" you should get a "$" symbol.
[STEP 9] Now type "su" and you should get a "#" symbol.
STEP 10] If you got those symbol's, then you are now rooted. Now go into the market and download "Superuser" by "ChainsDD".
You should now be rooted. This was tested on a Acer Aspire One netbook running Windows XP. If you are running Windows Vista/7, then the only different step you need to do is right-click the cmd/command prompt and select "run as administrator".
This was also done without mounting the sd card like some users have done to make it work. If it doesn't work, try mounting the SD card. If all else fails, restart the phone and try again. What I did was pull the battery out and then tried it.
As stated before, credits go to joeykrim at sdx-developers and noobnl from our very own xda-developers.
Have a nice day

OMG..... I GOT IT ROOTED YEEEEHHHHHAAAAA )))
Thank you so much for everyone involved in making this possible for all of us )

I'll add something I've noticed while fiddling around with all of the "one-click" installations:
Do not let your phone lock/go to sleep while they are running (step 7 above).
I couldn't figure out why they would work sometimes and not others (device not found errors) and I think this may have been it.
You can also launch the .bat by double-clicking it wherever you extracted it to instead of going through the command prompt to save a couple steps.
If this is way off base please let me know what is really causing the problem or just delete this post!

puppetmstr said:
STEP 10] If you got those symbol's, then you are now rooted. Now go into the market and download "Superuser" by "ChainsDD".
Click to expand...
Click to collapse
If you want to use the superuser app you need to do some additional modifications because the root method actually replaces su every time you reboot. I wrote the steps out in this thread. http://forum.xda-developers.com/showthread.php?t=788939

i finally got it to work for me
after several times trying to install and nothing just $ after $ after $ then i noticed the advise on removing the battery at the very end
so leaving the phone connect my cmd window still open i pulled the battery waited bout a 30 seconds then put the battery back in booted the phone
once the SD finished its scan
i ran the ADB SHELL and typed su and got the #
so thanks much for the help guide

richse said:
If you want to use the superuser app you need to do some additional modifications because the root method actually replaces su every time you reboot. I wrote the steps out in this thread. http://forum.xda-developers.com/showthread.php?t=788939
Click to expand...
Click to collapse
2.2.5 fixes this and comes with superuser.apk built in.

Folders one click root
cant seem to get my computer to see my epic when in debugging

How do i root with adb?

Hello, i just got my new samsung 7 plus with honeycome 3.2 and im loving it
I want to know what is the step by step instruction to rooting my device using adb?
the root.zip i found on here dont work for me. when i save the file to /sdcard and n reboot n go into wher i applie the zip from sdcard it shows no files at all on my card. i bought the 16gb version of this tab so i dont have the externel sdcard. i thought that i read one the forum you can only use the externel card not the interel. i believe they added the folder /sdcard to the internel drive and thats why it not viewing.

The rooting instructions say to put it on an "external" sdcard for a reason as recovery will not recognize the internal storage. Do you have adb installed on your computer and at least know how to use it? If not it is going to be way easier for you to just go and spend the $10 for an 8 GB sdcard and install it that way.
I can at least get you part way, installing the sdk and jdk. Here are the instructions for installing the android sdk (adb) direct from google. You also need the java jdk installed on your commputer and google has a link in their instructions.
http://developer.android.com/sdk/installing.html
You first need the proper usb drivers installed and not exactly sure on how to do that. I already had the android usb drivers installed on my computer for my phone and I just let the compter install whatever else it needed the first time I connected my tab to it.
You will need usb debugging turned in your settings and then power the tab off. You would then plug the usb cable into the tab and computer then boot it into recovery. Once into recovery Mount/System. You then run adb in a command window and change the drive to the platform-tools directory where adb resides. It would look something like this in a command window (c:\android-sdk-windows\ is how I set my computer up yours may be different):
cd c:\android-sdk-windows\platform-tools
To check and see if your device is recognized by adb run the command:
adb devices
If nothing is listed then adb isn't recognizing the device and you would need to troubleshoot your installation or boot method.
As far as installing the root.zip file I'm not sure as I've never had to do that before as I've always had an external sdcard on my devices. Maybe someone else can take you thru the last step. I believe all you would do is push the file inside the zip folder over to the tab. The su file inside the root.zip folder needs to be in the same directory as adb, platform-tools directory.
adb push su /system/bin
I'm not sure if you need to change permissions on this file or not and that is done thru a chmod command in adb shell but not sure of the proper code to use for the GTab to do this. For my phone setting permissions looks like this:
adb shell
cd /system/bin
chmod 0644 Su
exit
Do not use this chmod as I'm not sure it will work on the GTab or what it will do to it, it just an example.

In summary these are the basic steps you are trying to accomplish:
1. Install Java JDK
2. Install Android SDK
3. Install USB drivers
4. Turn USB debugging on in Tabs settings
5. Boot Tab into recovery while connected to PC
6. Mount/System in recovery
7. ADB push su file to system/bin
8. Set permissions of su???
9. Exit adb
10. Reboot phone and install superuser and busy box from market

Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk

ronlsjr said:
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
Click to expand...
Click to collapse
Yes any sdcard will do and that is the easiest way. Though I think everyone should learn how to use adb anyways as it is useful especially if you get into modding.

Yes i do want to learn how to use adb. My desire is to become a developer.
Sent from my GT-P6210 using Tapatalk

Just follow the link I provided previously to the android developers site and follow the instructions. You will first have to have Java JDK installed and a link to that is provided on the android developers website in the link. Once JDK is installed download and install the SDK. It will only put the basic functions onto your computer and you will have to install the rest through SDK Manager, this can take a while, up to an hour or so depending on what packages you want to install. At the minimum you would want the Android 3.2 API (GTab 7+ uses this) and the Google USB drivers and then any other API's for phones you may have. I myself installed all the API's as my first phone had Donut (Android 1.6).

I know this may be a stupid question but why root? what special features does it give you? I am not sure If I want to or not.

Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App

don't get confused by the lingo...
Noah321 said:
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
Click to expand...
Click to collapse
There's a difference between "flashing a ROM" and "adding root access".
A custom ROM implies someone has taken the stock software infrastructure, altered/tailored/customized it, and packaged it for others to easily use.
"Rooting" a device just simply gives you access to certain folders, permissions, files, etc.
It's like giving yourself Admin Rights to your work computer (assuming you're over 18 and/or working).
It allows you to do things that the manufacture probably didn't want you to do - like delete "bloatware" (unwanted apps).
If helpful, click "Thanks"

[Q] Problems With CMB command prompt. HELPPP

Hi i'm having a problem trying to get my evo shift Perm Rooted. There's like 4 different guides that i've found on how To root an Evo or even more specifically the Shift. I've followed all these guides and still no luck.
I already have my phone Temp Rooted through VISIONary, my problem happens when I have to go to the CMB (Command Prompt)
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
I make it to where I need to type in adb shell and what it says is adb server is out of date. killing... *daemon started successfully*
Then it shows the $ sign.
What i'm supposed to do now is type su
Then when I do it says su: permission denied
This is where i'm lost at. I followed everybody's instructions perfectly but cant move on till I get pass this... Can anyone help me please?
Thank you

What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?

Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.

prboy1969 said:
What Android version are you on?
2.2 ?
2.3.3 ?
2.3.4 ?
Click to expand...
Click to collapse
2.2
Is that good or bad? Should I upgrade?

sparksco said:
Check the permissions under properties of adb.exe (right-click adb.exe and select properties) in your sdk/platform-tools folder. Make sure it is allowed to run as a program.
Click to expand...
Click to collapse
I have a Windows XP So when I go to properties the best I can do is Run it as an older version in compatibility mode? I'll still try it out to see if any older version works
*edit, tried and didnt work

tmb04 said:
2.2
Is that good or bad? Should I upgrade?
Click to expand...
Click to collapse
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.

prboy1969 said:
NO DO NOT UPGRADE!!! If your on 2.2 it's very easy. Just download and use THIS TOOL. It will do it all for you. Just connect the device via USB Cable, and choose charge only. Extract the Zip file that you downloaded onto your desktop, and run the program. Then click the ROOT Button. Make sure your Anti-Virus and Firewall are disabled before you start. Then just follow the Prompts. When it's all done go to the Play Store ( Android Market ) download Rom Manager Free. Open up Rom Manager follow the prompts to Flash CWM Recovery. That's it your Rooted with a Custom Recovery.
Click to expand...
Click to collapse
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.

tmb04 said:
I downloaded what you said, I run the program and disable the firewall, I clicked on Root and it says "Error running ADB try again"
I know that means I probably did something wrong in an earlier step but still unaware where I messed up at.
Click to expand...
Click to collapse
You need adb working... In order for adb to work you need to have android debugging checked under Settings > Applications > Development on your phone. It's not enabled by default on Sense roms so you'll need to make sure it's enabled and turned on.

Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up

tmb04 said:
Ok I made it past the part I was stuck at. Rooted my phone, downloaded ROM manager, clicked on Flash ClockworkMod Recovery, and before it finishes it says " An error occurred while attempting to run privileged commands! "
I'm sorry for asking for so much help but I'm not trying to mess anything up
Click to expand...
Click to collapse
All good about asking questions. When the message pops up asking for SuperUser Permission, you have to click yes. Otherwise it will not run.

I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?

tmb04 said:
I ended up factory restoring my phone and followed a youtube video for the same exact guide that you told me to use. I followed it step by step and now my phone works perfect. I appreciate all the help.
Instead of me creating a new post, can you recommend a good guide for me to flash my shift to boost mobile?
Click to expand...
Click to collapse
You should be able to find to find the info you need HERE.

[Q] First step to get Rooted

I have been searching for a week now on how to root my xoom and but i am getting nowhere..
I am currently running stock os.. ICS 4.0.4 IMM76..
I was able to unlock my zoom via adb
I was trying to push recovery-Tiamat-R4c-100611-1150-cwm.img via adb, it will go through the process but after reboot I can not find superuser or busy box installed.
Please help or direct me to right path to get my xoom rooted.
thank you.

You push the recovery through ADB like you were doing....but you boot in to recovery on the Xoom and install the root "update.zip" from there.
That installs su, Superuser.apk and busybox.
You were on the right track...you were just skipping a step. The link that had the recovery.img file you downloaded should also have the root "update.zip" as well.

Stock MF3 to MJ9 through sideload for those that can't update through OTA

Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.

Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.

Ota link
raidel00 said:
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/show...&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Click to expand...
Click to collapse
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325

Bimboy said:
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Click to expand...
Click to collapse
silrosriv said:
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Click to expand...
Click to collapse
Ok...fixed it. Thanks for pointing it out!:good:

Help!
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted

does this wipe the device? or does it keep all your apps / data?

Update
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.

silrosriv said:
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
Click to expand...
Click to collapse
probably due to some users having some issues with mms

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Interesting....It worked so smooth for me I don't know what else to say.

jherring002 said:
does this wipe the device? or does it keep all your apps / data?
Click to expand...
Click to collapse
If you do it by sideloading it from the computer it will not wipe the device. If you do it by running it from the SD card....it will wipe the device.

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.

dwanhala said:
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
Click to expand...
Click to collapse
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yup. I chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
I think I'll jist wait for it to come back.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

It's working pretty good on my phone. I quit using the lookout security app though. It's not really needed. I know they pulled galaxy s3 update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Had the same problem when I tried to sideload the update. I was on MF3 and was rooted. What worked for me was to delete all busybox files and unroot using SuperSU and odin back to stock, just in case. After that, I was able to sideload and the phone booted up with no problems.

It works pretty good on my phone also. Was on mj6 and it was having random FC's also random vibrating but now on mj9 I don't have those problems anymore.
Sent from my SAMSUNG-SGH-I337 using xda premium

Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I was getting the same error. What I did was re-load mf3 (via odin) and then sideload this update.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yeah, at this point I just rooted again (which of course set my device status back to official from the custom that it had changed to when I unrooted) and I'll wait to see if AT&T is going fix the problems before proceeding.

finally
I can't believe it
- Restore my S4 AT&T to 4.2.2 stock with Odin all the 4 files in MF3 using (download mode)
- Sideloaded to 4.3 ...MJ9 File with the Framework using (recovery mode)
Now my phone is even rooted with SuperSU (starting the root with vroot and converting it to SuperSU)
with the following sort video tutorial that found on youtube this morning
youtube.com/watch?v=isHYNqWCfSc