Hello everyone!
I know some of you are still roaming around here and there trying to root your phone; others wanting to root the phone without knowing what rooting is...
Wandering if it's illegal or not; and why should they be Rooting their Devices.
Well that's why i've done this tutorial with a lot of help from different sources.
It has been almost 2 days reading; reading; reading; and writing this tutorial to simplify and compact information scattered around this forum and the web.
Knowing the Basics
In order to explain everyone (specially noobs / starters); please follow this link.
(I advise you to open it in a "new Tab" or "Window"; so you don't loose yourself)
One thing before starting:
I found out that it is important to reboot the device and the PC after installing and Updating the following apps: "Super one Click" and SDK with your firmware version API's.
Some errors that occur during the Rooting with the "Super One Click" happen due to some kind of need to reboot of the machine and device.
As mentioned in Step #9
[...]
Now that you understand what rooting is; let's ROOT your Android.
P.S - As you already know; you are responsible for doing this process; or for anything that goes wrong.
“Rooting Your Android Phone”
Requirements:
Download: "android-sdk_r15" or Later Version.
After Downloading and Installing SDK; download the API's according to your Firmware Version.
(Check Step #1 and #12 of the Easy Rooting Method)
Download: "Super One Click Program"
(Link Goes to XDA Developers "Super one Click Program" Thread)
Download: "Java SE Development Kit 7" (or later)
I. (Easy Method - Using “One Click Rooting Program”)
Note: This method works for almost every Android phone.
1) Take a note of you brand model and android Firmware/ROM installed on you device.
(You need to know the version of your O.S to download your SDK API's later)
i.e:
“Model: Acer C4 Liquid Mini (E310)”
“O.S: Android Froyo v2.2”
2) Download/Install your Android Drivers. (PC)
3) Download/Install your Android SDK/ADB. (PC)
4) Open SDK (as Administrator) and mark the following things to download:
- “Tools” (Select the entire Folder)
- “Your Firmware/ROM Version Installed” (i.e: “Android 2.2 API”) (Select the entire Folder)
5) Now press “Install Packages” (The download will start; follow the next step after it’s completed)
6) Download / Install the Latest version of the rooting program (Super One Click Rooting Program); unzip it and install it on your computer.
7) Make sure that your phone has the "USB Debugging Mode" ON.
NOTE: To turn it on go to your device and press: “Menu” > “Settings” (Icon) > “Applications” > “Debug / Development” > “USB Debug”
8) Make sure you turn Off your Device and Remove the SD Card. It must be done without the SD Card.
9) Safely disconnect your Phone from the PC; and restart. (PC and Device)
10) When your Phone and Windows are ready; connect your phone to the PC.
Note: Just plug the cable. Do NOT select any option in the Phone.
Also you will notice that a small Android Icon will appear at the top left of the screen.
That means that you phone is prepared for debugging Mode.
11) Once again make sure that your phone has the "USB Debugging Mode" ON.
12) Run SDK/ADB as Administrator.
(Windows XP Users just double click to open)
13) Right Click the “Super One Click Rooting Program” and open it as Administrator.
(Or just double click; if you are using Windows XP)
14) Press "Update Check"; just to make sure you have the latest files. (Don't worry with the app version error; if it happens means you just downloaded it/you have the latest version)
14) Click the "Root" button and wait it to finish. (There should be no errors)
15) Once done; you should see “Superuser” permission in your phone’s apps.
Note: If so; your Device is Rooted. Congratulations!
II. (Advanced Method - Manually Rooting)
Pre-requisites
There are a few things that you need to have before you start rooting.
Obviously, you will need an Android device with Android 1.5 or higher and a USB cable to connect it to your computer.
You will also need to have some files for this:
SuperOneClick.zip and the Android SDK/ADB up and running on your computer.
(Run as Administrator if not using Windows XP)
If you are unfamiliar with ADB, GoodAndEvo site has an awesome ADB tutorial that should get you up to speed.
(Note that the tutorial in the Good and Evo Page is for HTC Devices)
First, we need to move some files around to make running commands a bit easier.
Unzip the SuperOneClick.zip and copy the following files: su-v3, busybox, Superuser.apk, psneuter, and GingerBreak; to the Android “ADB Platform-Tools folder”; which is contained in the Android SDK folder on your computer.
i.e: C:\Program Files\Android\Android-SDK\Platform-Tools\
These files can be found in the following SuperOneClickv2.1.1-ShortFuse folders:
- “Busybox” -> “Dependencies” folder
- “psneuter” -> “Exploit” folder
- “GingerBreak” -> “Exploits” folder
- “SuperUser.apk” -> “Root” folder
- “SU-V3” -> “Root” folder
Once copied rename “su-v3” to “su”.
If you are on Windows, you will also need to have proper drivers for your phone installed.
These can usually be found by going either to the manufacturer website or searching for the name of your phone and the word "Drivers."
Once you find drivers, download and install them like any other application.
Rooting your device
Now that you have ADB setup and the proper exploit files, you are finally ready to Root.
Before you start running commands, you need to put your phone in "USB Debugging" mode.
(Menu > Settings > Applications > Development > Enable USB Debugging) and connect the device to your computer.
Note: Just plug the cable and do not select any option in you device.
Now, open command prompt to run some commands.
Windows Vista/7 Users:
(Press "Windows Key" > Type: "CMD" > Right Click on "CMD" and Run it as Administrator)
In Linux, open whichever terminal emulator suits you. Once you have a command prompt, you need to enter your platform-tools folder, also called a directory.
You can use the "CD" or Change Directory command to accomplish this.
If your SDK folder is called "android-sdk" the command should look like this: cd android-sdk_r11-windows/platform-tools.
This command will leave you with a shell prompt in the platform-tools directory.
From here, you can run the commands that will actually root your phone.
Be sure to run these commands exactly as they are written.
The commands with an "$" or "#" will only run after the "adb shell" command.
First, here are the commands that run the” psneuter” exploit and gain a root shell.
Type them in the following order.
…Yes after the ADB and the “$” there is a “Space”.
• adb devices
• adb push psneuter /data/local/tmp
• adb shell
• $ cd /data/local/tmp
• $ chmod 777 psneuter
• $ ./psneuter
At this point, the exploit will run and close the shell.
You will need to run these commands to restart the ADB server.
• adb kill-server
• adb devices
Now comes the moment of truth.
Type:
• adb shell
...command to open a shell.
If you see a "#" sign, you have root access, so go ahead and continue to the next part of this tutorial.
If not, you can go back and try the previous steps again, or ask for help in the comments.
We now need to make this root permanent.
From the root shell you just opened, type the following commands.
• # mount -o remount,rw -t rfs /dev/block/st19 /system
• # exit
• adb push busybox /system/bin
• adb push su /system/bin
• adb install Superuser.apk
• adb shell
• # chmod 4755 /system/bin/busybox
• # chmod 4755 /system/bin/su
• # mount -o remount,ro -t rfs /dev/block/st19 /system
• # exit
• adb reboot
At this point, your device should reboot.
You can check for the Superuser icon in the app drawer, and then try a root only app like Titanium Backup.
If that app works, congratulations!
You have successfully rooted your Android device.
Prepare to enjoy all the benefits of root.
If you are having trouble with this tutorial or want to offer others a tip, please leave a comment.
Me or every XDA developer/user shall gladly help you out clarifying any error message or issue. (at least if i know how i will help)
Just make sure you did exactly as described; and only then post your question / expose your issue(s).
P.S
- Use “Code” Tags to report Logs.
- Remember to "Thank" if this tutorial helped you or if you find it usefull.
Special thanks to:
XDA Developers (Users & Staff)
Pocketables.net (Aaron Orquia)
CLShortFuse (For bringing such Great App)
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
niki40 said:
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
Click to expand...
Click to collapse
Greetings;
What's your device Make and Model?
Try/Check the following:
- Download the "Super One Click Program" Again. Since there is a new Fix for it.
Follow this Link to download and get more detailled info:
http://forum.xda-developers.com/showthread.php?t=803682
- Check that you have the USB Debug Turned ON (in your device)
---> List > Settings > Applicatons > Development > USB Debugging
- Check what version do you have in your device; and verify that SDK Manager has downloaded your Version API's; and Tools folder. (Look at status tab; it should say installed)
- Did you Restart the machine after the install of Super One Click and SDK Manager? (Only then Root the Device)
- In a Last case there's a small percentage that your phone isn't compatible with "Super One Click".
Thanx a lot bro
You Can Add This To The OP If You Want .
Press Thank If I Help .
For Sony Ericsson Xperia Only .
I Use A Sony Ericsson Xperia X10 And It Work Well .
The File Name Is Call Flash Tool .
The Fuction It Has Is ( Latest 4.2 )
Root
Flash Kernel
Flash Rom
One Click Unlocked Bootloader .
Click to expand...
Click to collapse
Thing You Need To Do Is :
Download The Two File .
Install In The Same Place .
Open The File .
Open Driver Folder .
Install The Driver .
And Open Flash Tool exe .
See If The Computer Detect Your Phone .
USB Debugging Must On .
Click to expand...
Click to collapse
Thing Your Need ( For Rooting Only ) :
https://github.com/Androxyde/Flashtool/downloads
==================================================
Unlocked Bootloader Try At Your Own Risk . Sony Ericsson Xperia X10 Success ) :
Only For Sony Ericsson Xperia Phone .
Download Generic version 2.3.3 build 3.0.1.G.0.75 ( http://www.multiupload.com/564T6TLUD8 )
Download DoomLoard Boot Manager . ( http://doomlord.sylvester20007.com/...tmanager/X10_2.3.3_Stock-BootManager-v1.3.ftf )
Put This Two File In Flash Tool Frimware Folder .
Open Flash Tool .
Press Flash .
Select All The File Inside .
Reboot Your Phone .
Root Your Phone .
And Install DoomLoard Boot Manager .
You Can Now Install Unlocked Bootloader Rom .
Click to expand...
Click to collapse
If Anyone Know Anything And Notice I Say Wrong Here Please Private Message Me Or Comment Here To Tell Me
Special Thank To :
Every One That Teach Me Last Time .
Androxyde For Flash Tool . http://forum.xda-developers.com/showthread.php?t=920746
DooMLoRD For DoomLoard Kernel And Boot Manager . http://forum.xda-developers.com/showthread.php?t=1278318
Every Body Who Click Thank .
Every Body Who Read .
Click to expand...
Click to collapse
==================================================
Do It At Your Own Risk . Press Thank If I Help
And Yes It Work For New Xperia ( 2011 Lines )
nice share...but i already rooted my xperia
Hi everyone!
I have Nexus S. Currently installed ICS ROM. Now I'm trying to root it, but I cannot access the folder where fastboot.exe is located.
I open CMD and type cd \nexussrootICS
nexussrootICS is a name of the folder where fastboot.exe is located.
but when I type that, it says that "system cannot find the path specified".
I've checked many times the path. It is C:\user\myname\ + nexussrootICS
but I cannot access it from CDM.
What am i supposed to do? maybe some changes are required in environment variables???
Thanx in advance!
Do you have latest sdk installed? I always cd android-sdk-windows/tools (which is where fastboot.exe is), but I think it taken out in some of the most recent updates to the sdk so I'm just usin an older fastboot
Sent from my Nexus S 4G using Tapatalk
is this the guide your using if not this guide worked for me http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Thanks guys, already fixed! It was about semicolon in environment variable>> path.
i did OTA update on my mom's galaxy tab 2 7.0 today
the update seems to have worked fine with the exception that there is a yellow text overlay on the home screen
the overlay disappears when running apps or even entering "settings"
the yellow text is located in a transparent box on top of the home screen
its contents are:
PDA: P3110xxxxxxx
Phone: N/A
CSC: P3110xxxxxxxx
H/W : MP 0.600
RF Cal Date: N/A
SMD : 01P, PBA : 04N
CAMERA : N/A, FrontCAM : N/A
TSP : 17
TSK : N/A
Band : N/A, CH : N/A
UART : N/A, USB: N/A
UN : CM808Exxxxxxxx
BATT_LEVEL: 87
Wifi is turned off by default but if I turn it off I seem to have internet access no problem.
Aside from the text, the tab is still usable, but just annoying as hell.
When returning to home screen, sometimes there would be a few seconds delay before the yellow text overlay shows up
Does anyone have any idea how to fix this please?
actng said:
i did OTA update on my mom's galaxy tab 2 7.0 today
the update seems to have worked fine with the exception that there is a yellow text overlay on the home screen
the overlay disappears when running apps or even entering "settings"
the yellow text is located in a transparent box on top of the home screen
its contents are:
......
Wifi is turned off by default but if I turn it off I seem to have internet access no problem.
Click to expand...
Click to collapse
I have exactly the same problem with my friend's tab 2 7.0" (P3110). Some people were lucky enough and the fix described in this thread worked for them, but not for me, unfortunately. I still suggest you to try, though.
[SOLVED]
I've found the solution.
1) backup /efs/FactoryApp and /efs/imei
2) remove /efs/FactoryApp and /efs/imei
3) reboot
4) if device is rooted
Code:
su
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
if device is not rooted, you have to have adb tool from android sdk, after installing sdk run SDK Manager (if it doesn't start, use sdk\tools\android insted) you have to select and install Extras/Google USB Driver, then
4.1) reboot into recovery mode
4.2) install Google USB driver from driver manager (there is a guide for this but I can't post external links yet)
4.3)
Code:
adb shell
4.4) run commands:
Code:
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
This did it for me.
Question
My apologies if the question sounds silly. But trying to figure out how to execute these commands? Are these executed on the device itself? Or are they executed on a computer with the device tethered via USB? I think it is the latter, but if you could confirm, that will be appreciated. What utility is used for executing these commands?
I have Galaxy Tab 7.7, so these instructions may not work ... but I will do some trial and error once I know how to get started.
thanks in advance
ADB works only on computer.
So computer.
TabUser77 said:
My apologies if the question sounds silly. But trying to figure out how to execute these commands? Are these executed on the device itself? Or are they executed on a computer with the device tethered via USB?
Click to expand...
Click to collapse
It depends, if your device is rooted, install terminal emulator (any will do) and proceed according to the first batch of instructions in the beginning of my post. If your device is not rooted proceed according to the second part of my post, you'll have to install SDK and use adb utility from the SDK, this implies tethering your device via USB and typing those commands in adb shell environment.
I have no idea if this instructions will help with Tab 7, but if you backup everything before deleting (changing) it most probably won't do any harm. But, of course, I can't guarantee that.
AlexCzar said:
It depends, if your device is rooted, install terminal emulator (any will do) and proceed according to the first batch of instructions in the beginning of my post.
Click to expand...
Click to collapse
My bad ... did not realize that the terminal emulator is an android app .... will try this our. I have a rooted tab.
You beat me to the answer
__
Sent from my GT-I9300 using xda app-developers app
AlexCzar said:
You beat me to the answer
__
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Btw: Still searching for the solution for my Galaxy Tab 7.7 Model SCH-i815. May I ask you how you came to figuring out your solution? Anything you can do to redirect me to figuring out how to solve this problem?
Thanks in advance
I googled a lot, after all proposed solutions didn't work I sinthesized my own based on those provided - just randomly poked mentioned files and directories - deleted, changed contents and so on. Just don't forget to backup everything before you do that.
Sent from my GT-I9300 using xda app-developers app
Easy way just did it
Rooted phones only go into root explorer root
Efs
Factory app
Factory mode text file
Text editor
Change it to either on or off whatever is opisite of what is there
Save and exit might ask if you want to backup the file just say yes
Restart phone and it will go through prompts
And it will be gone
Sent from sprint note 3 rooted
AlexCzar said:
I've found the solution.
1) backup /efs/FactoryApp and /efs/imei
2) remove /efs/FactoryApp and /efs/imei
3) reboot
4) if device is rooted
Code:
su
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
if device is not rooted, you have to have adb tool from android sdk, after installing sdk run SDK Manager (if it doesn't start, use sdk\tools\android insted) you have to select and install Extras/Google USB Driver, then
4.1) reboot into recovery mode
4.2) install Google USB driver from driver manager (there is a guide for this but I can't post external links yet)
4.3)
Code:
adb shell
4.4) run commands:
Code:
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
This did it for me.
Click to expand...
Click to collapse
Worked, thank god, (and you of course). Had to realize that I needed to go in and delete everything prior to typing out the commands in the terminal emulator, but once I did, that stupid yellow text went away. Again, thanks!
Hello Everyone;
Quick intro: I just found this group while looking for tcsh to load on my Samsung Galaxy 10.1 tablet. First post.
I've been running Linux since 1995, Slackware 1.2 kernel, downloaded the source code over a 1200 Baud MODEM, Gen'd kernels, etc.
I just rooted the tablet and am loading Linux utilities on it.
--
I downloaded and installed the tcsh I found on here - written by corinna.
Two things:
1. Question: where is tcsh looking for the .tcshrc file? I made /root my home but I have to source the .tcshrc file (works fine).
I use <.logout> to copy my <history> to a logfile. I find this to be a great idea - because if something gets messed-up, I can backtrace the commands. Every year I copy it to history.[year] and can look up everything I've ever done to the system.
2. The anomaly: If I do "history >> logfile" on the command line, it works as expected - but if I put that command in a shell file, the history does nothing.
Sample shellfile
#!/bin/tcsh -f
echo `date` >> /root/Log/history.log
history >> /root/Log/history.log
history -c
cp /dev/null /root/.history
--
The dates appear in the file, but no data from the history.
I am THRILLED that corinna ported tcsh to Android - because it is my favorite shell.
regards,
TOMOTH
Fixed One Problem
Solved the "source .tcshrc" problem: had to put the .tcshrc file in the / directory.
regards,
TOMOTH
Hi
the content of "/sdcard/android/obb" from device and adb is not same!!!
- Folder "is not shown on adb" is created using RootExplorer
- Folder "IS NOT SHOWN ON DEVICE" is created using mkdir command
What is the problem?
The phone is Samsung S4 running Android 4.2.2