NOTE: I am not responsible for any damage or any thing because of this article, do it on your own risk
Note：You need to install your device's driver on your pc before do this.
Step 1: Before starting with rooting your Android device, it must be put in USB Debugging mode. To turn it on, go to Settings > Applications > Development and check the box.
Step 2: Download Unlock Root from its official website http://www.unlockroot.com/
OR
download from here
Step 3: Now just open the Unlock Root application by double clicking on the runnable file.
Step 4: Do ensure that your phone is connected with USB cable and you have enabled the JSB debugging before continuing. As you plug your phone, it will help you in detecting your device automatically (the following screen will show up).
Step5: Now click on the 'Root' icon towards the left and you are ready to go.
Step 6: After rooting, it will pop up a new message box where you will be asked if you want to install PowerSaver application in your Android. Do install this application recommended by unlockroot.com, as it helps to extend the battery life of your device
Step 7: In the final step it will ask your permission to root your device, click "yes" your android will be rooted.
Enjoy .. :))
Image source: unlockroot.com
Limitations of Rooting
Bricking
The major reason not to root your device is the potential risk of "bricking" it. Bricking your device means screwing up your phone's software so badly that your phone can no longer function properly and is as useless as a brick. You most likely ought to purchase a new Android device since the manufacturer of your device will void the warranty after any attempts at rooting.
Security Risk
There is an increased risk of unknowingly installing malicious software when you root an Android device. Root access circumvents the security restrictions that are put in place by the Android OS. There isn't really an effective way to tell just what the application intends to do with that "superuser" power. You are putting a lot of trust into the developer's hands. In most cases, these applications are open source and the community can take a look at the source code to assess the risk. But, nevertheless, the risk is there. May be the application your are using through rooting is from a hacker himself.
Note：You need to install your device's driver on your pc before do this.
Step 1: Before starting with rooting your Android device, it must be put in USB Debugging mode. To turn it on, go to Settings > Applications > Development and check the box.
Step 2: Download Unlock Root from its official website http://www.unlockroot.com/
OR
download from here
Step 3: Now just open the Unlock Root application by double clicking on the runnable file.
Step 4: Do ensure that your phone is connected with USB cable and you have enabled the JSB debugging before continuing. As you plug your phone, it will help you in detecting your device automatically (the following screen will show up).
Step5: Now click on the 'Root' icon towards the left and you are ready to go.
Step 6: After rooting, it will pop up a new message box where you will be asked if you want to install PowerSaver application in your Android. Do install this application recommended by unlockroot.com, as it helps to extend the battery life of your device
Step 7: In the final step it will ask your permission to root your device, click "yes" your android will be rooted.
Enjoy .. :))Image source: unlockroot.com
Limitations of Rooting
Bricking
The major reason not to root your device is the potential risk of "bricking" it. Bricking your device means screwing up your phone's software so badly that your phone can no longer function properly and is as useless as a brick. You most likely ought to purchase a new Android device since the manufacturer of your device will void the warranty after any attempts at rooting.
Security Risk
There is an increased risk of unknowingly installing malicious software when you root an Android device. Root access circumvents the security restrictions that are put in place by the Android OS. There isn't really an effective way to tell just what the application intends to do with that "superuser" power. You are putting a lot of trust into the developer's hands. In most cases, these applications are open source and the community can take a look at the source code to assess the risk. But, nevertheless, the risk is there. May be the application your are using through rooting is from a hacker himself.
0 comments:
Post a Comment