Related
I've combined toastcfh's and TheBiles how-to's in this tutorial, so if you've already rooted using TheBiles previous method, skip to step 9. I'll make this a bit more presentable when I get home from work today. I just thought this would be helpful to those who aren't comfortable with using adb.
I'm not responsible for damages to your phone, yada yada yada, you know the drill.
IF YOU HAVE A PROBLEM THAT HASN'T BEEN ADDRESSES IN THE SECOND POST, LET ME KNOW. OTHERWISE, SEE SECOND POST FOR FAQ'S. Follow these directions exactly as they are written and you won't run into any snags. It'll save us both a lot of time.This tutorial entails making the root process as fast and easy as possible, that means we won't be backing up any of your stuff (you can if you want, of course) nor will we be doing a nandroid backup, and even better, we won't be using adb to push files. With that being said, let's get started.
Step 1. Connect your phone to your pc via usb, then pull down the notification bar at the top of your screen and open the tab that says Charge Only and select Disk Drive then click done.
Step 2. Download this file http://link.geekfor.me/rootedromzip and put it on the root of your sd card by going to the start menu of your computer and opening up My Computer, then drop the file into the icon that reads Removable Disk. This is the root of your sd card. Remember that if you don't already know.
Step 3. Right click on the Removable Disk icon and select Eject. We're gonna flash the debug image now, say goodbye to any pic's, music, apps, texts, etc that you may have.
Step 4. Power down your phone.
Step 5. Hold down the volume down and power key simultaneously and keep holding it down until you see 3 android dudes on skateboards.
Step 6. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 7. Once you've rebooted you will officially have root access. Congrats, but that's not all. There's a few more steps to gain -full- root access.
Step 8. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. To rename the .zip file, right click on PC36IMG.zip and select rename.
Step 9. Download these files:
PC36IMG.zip -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
mtd-eng.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
flash_image.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
recovery.img - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img
PLEASE NOTE SOME OF THE MIRRORS YOU ARE DOWNLOADING THESE FILES FROM ARE NAMED SOMETHING DIFFERENT, SO YOU WILL HAVE TO RENAME THEM ACCORDINGLY. The only one that I know of was the PC36IMG.zip file, it was named something else when I downloaded it. So name it accordingly. Right click, select Rename, then type in "PC36IMG" only, your pc adds the .zip.
Step 10. Extract the flash_image.zip and mtd-eng.zip files, do so by right clicking on them, then select Extract To flash_image\ and Extract To mtd-eng\ Open the newly extracted folders and take the flash_image file AND the mtd-eng file inside and drop them into the root of your sd card. (we remember how to do that, don't we.)
Step 11. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 12. Make sure your sd card is no longer mounted to the computer, do so by pulling down the notification bar and switching Disk Drive to Charge Only.
Step 13. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 14. Remount your phone, and drop the PC36IMG.zip file onto the root of your sd card. MAKE SURE YOU USE THE CORRECT PC36IMG.ZIP FILE THAT YOU DOWNLOADED FROM STEP 9. Power down your phone.
Step 15.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 16. Once your phone has rebooted, put the recovery.img file you downloaded earlier on the root of your sdcard.
Note: If the recovery image is named something other than "recovery.img" then rename it by right clicking and typing in "recovery" as the name.
Step 17. Still know how to use terminal emulator? Open it up and type in these commands. Make sure your USB connection is in Charge Only mode first.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
*INTERMISSION*
Take uh break, eat uh cookie.
If you've made it this far and you've had no errors, then you now have full root access as well as a legit recovery.
Time to flash a ROM and the latest radio.
Step 18. Power down your phone and power it back on by holding down the Volume Up and Power key.
Step 19. Select BOOTLOADER then select Recovery.
Step 20. Select Wipe: Select wipe data factory reset then select wipe dalvik cache.
Step 21. Downlaod any ROM you'd like, I'm running BuglessPete's Bugless Beast ROM, here's the link if you want to run this one as well http://bit.ly/az4cWq
Step 22. Download the latest radio here http://link.geekfor.me/radio139000531
Step 23. In recovery mode, select the USB-MS toggle option, this mounts your sd card to your pc.
Step 24. Move your newly downloaded ROM and radio to the root of your sd card by dropping them onto the Removable Disk icon on your computer.
Step 25. Press the power key to disable USB-MS toggle.
Step 26. Select Flash Zip From Sdcard.
Step 27. Select the ROM you downloaded and you will be prompted whether or not you want to flash the file, follow through with the power key.
Step 28. Select flash zip from sdcard, then select the latest radio .zip file that you just downloaded and flash that mf'er.
Step 29. Try not to freak out when you see a static image of a phone with green arrows circling around it. Wait...
Step 30. Select Reboot System Now.
And that's it, you're done!
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
Grammatical errors? I just worked a 12 hour shift and got right on this, I have to be in bed in about an hour, so **** you.
Problems flashing a ROM after you've completed the process?
This is more than likely on account of the Dev who made the ROM not signing it, tell them if they sign it that you'll love them forever. Or switch to Koush's recovery. This is pretty much guaranteed to work, as Koush's recovery has a toggle signature verification feature. http://forum.xda-developers.com/showthread.php?t=702214 Or, if you've the know-how, sign it yourself. http://forum.xda-developers.com/showthread.php?t=473580
ATTENTION: To the few getting the not enough space error when flashing the recovery image, Amon Ra has addressed the issue here, to no avail according to those who have tried his alternative recovery. At least we now know what the cause of the error is. Thanks again, Amon Ra.
Amon_RA said:
You have a bad block in your recovery (like a bad sector on your harddisk), these bad blocks are skipped when flashing. A bad block means you have less usable space on your recovery partition, hence the not enough space left to flash this recovery...
I made this recovery specially for you, it's 1MB less than the normal recovery (left out the evo charging stuff), all functions of the normal recovery should still work. Could you please give it a try and let me know?
Code:
fastboot flash recovery tiny-recovery.img
OR
flash_image recovery /sdcard/tiny-recovery.img
Click to expand...
Click to collapse
Bad block? Not enough space on sd error when trying to flash the recovery image? Try these.
Amon_RA said:
Could you please try to flash recovery-RA-evo-v1.7.0.2.img and use fastboot to flash :
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-evo-v1.7.0.2.img
I'll most likely not make my recovery compatible with Koush's rommanger because I would need to almost rewrite it fully.
Click to expand...
Click to collapse
tlisak25 said:
If people are still having problems tell them to unroot and start from scratch without doing system update from Sprint thanks for all or your help
Click to expand...
Click to collapse
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
arozer said:
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
Click to expand...
Click to collapse
Exactly. Also, it's for those who rooted using TheBiles Idiot Proof method and were confused as to whether or not they could follow through with toastcfh's part 2nd part on gaining full root access.
Re: (How-To) FULL ROOT WITHOUT ADB.
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
TheBiles said:
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Totally agreed. But this method is meant to make rooting as fast and easy as possible (for those who don't know how to neither set up, nor use adb, as setting it up as well as familiarizing yourself with it takes time) Although learning adb is a definite must.
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
bdd123456789 said:
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
Click to expand...
Click to collapse
I'm just glad it helped. Lol If there's anyone you should donate to, it's toastcfh. Without him, we wouldn't have root.
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
Just a second, I'll get you a link.
the recovery.img link in step #9 is broken as well...
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
http://www.joeyconway.com/sdx/evo/troot/eng-PC36IMG.zip
Got it from toastcfh's thread. Should work. I'll update the link now.
Go damn it. -.- I'll update them all now. Thanks for the heads up.
thx for the hard work.
Lol Not really doing much but stealing links. They're all updated now.
evo root
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
crpercodani said:
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
Click to expand...
Click to collapse
Exactly! It took me 2 solid days of searching for the required driver for my laptop. I finally got it to work last night. None of the instructions on xda worked. The USB remover listed here didn't work, the driver in the SDK kit didn't work, nothing worked. I finally found another download for the USB remover and another link to a 32-bit driver that finally worked.
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
It's pretty much the fastest/easiest (if you don't have adb set up) way to get full root access on your Evo, so...yes, that'd be a good idea. Lol
S
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
Oh yeah, start from step 9 since you're coming from the first part of TheBiles Idiot Proof guide.
The rooting method for the EVO 4G is close to the same as the Droid 2, just recently created by Sebastian Krahmer at http://c-skills.blogspot.com/, but with a little variation.
Here is the step-by-step I just did on my brother's (dwizzy130) EVO 4G that came with 2.2 from Sprint.
I am NOT responsible for any damages (bricking, not working, basically anything that goes wrong) This has been tested and works. Over the next few days, I will be cleaning this post up and making the steps more clear.
Special thanks to:
Sebastian Krahmer for the exploit
dwizzy130 (my brother) for letting me test on his EVO (since I don't have one)
The unrevoked team for their methods
Toastcfh for his mtd-eng.img
Topgun966 over at evo4g.me for hosting the files
djR3Z over at TheDroidDemos.com just made a GREAT video walkthrough that should make this MUCH easier for all of you. He spent a TON of time making it yesterday, so please give him lots of thanks!
VIDEO WALKTHROUGH (2 parts)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.40 here
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Windows 7 Users:
Go to your start menu, then control panel. When that is open, (if you are in category view mode) click on "Uninstall a program" and then choose HTC Sync to uninstall. If you are in Icon view mode choose "Programs and Features" and then click on HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Other Windows Version Users:
Go to your start menu, then control panel. When that is open, select Add/Remove Programs, and then choose HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Next,
Download my evo-root.zip.
It contains a few files necessary to root the EVO.
Unzip the contents of the zip to your android sdk tools folder.
Download the unrevoked-forever.zip
Place this zip in your tools folder as well, as a zip, not extracted.
Download this PC36IMG.zip || Mirror(This is the same as running an RUU, so it will delete all of your user data when we use it later in the guide, so backup everything you want to save on your phone first)
MD5: e52f6ec4f8f5fd6dc251ef19ee19750b
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of evo-root.zip to your android sdk tools folder and placing the PC36IMG.zip and unrevoked-forever.zip in the folder, move on.
Step 4: Make sure USB Debugging is ON (checked) on your EVO. Go to Settings > Applications > Development > and make sure it is checked.
Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 6: Open up a command promt from your android-sdk/tools folder.
Windows 7 users:
Open up the android sdk folder and hold shift and right click on the tools folder. You will see an option that says "Open command window here" Choose that one and you will be set. the command prompt should read something like C:\android-sdk-windows\tools>
Other Windows Version Users:
Go to the start menu, go to All Programs, then Accessories, and click on command prompt. Once open type
Code:
cd C:\android-sdk-windows\tools
Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/
Note: the PC36IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.
Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/flash_image
Ok now for the root shell.
*
(still in adb shell)
Code:
cd /data/local/tmp
Code:
./rageagainstthecage-arm5.bin
You will now see some text on your cmd prompt screen explaining the exploit.
Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
Once that dumps you out of the shell, type
Code:
adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
now type
Code:
cd /data/local
./flash_image misc /sdcard/mtd-eng.img
that will flash your misc partition with Toast's mtd-eng.img.
This should return you to a blank line with #.
If you get an "Out of memory error" with a huge list of weird lines, here's how to fix it.
Reboot your phone normally.
Open a command prompt and go backwards in this guide until you see the big red * and start from there.
Once it is flashed correctly, move on:
Type
Code:
reboot bootloader
Remember how you pushed that huge PC36IMG.zip to your sdcard earlier? This is where that comes in handy. Once you booted into hboot, Select "bootloader" with your volume up/down buttons and hit the power button. Let it sit for a little bit while it loads the PC36IMG.zip. This can take up to 5 minutes. When it finally asks if you want to apply this zip, choose YES. (Remember, this is the same as running an RUU, so it will delete all of your user data).
If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue.
Once it is finished, select restart. You now are on the stock 2.1 build of Android.
Next step, mount your sdcard on your computer, and delete the PC36IMG.zip from it. This is because the next step requires using hboot, and you don't want to sit and wait while it loads up again, just for you to say "no" to the install. Please follow this step, for it saves 5-10 minutes of waiting ahead.
I worked extensively with Matt Mastracci, so this rooting guide will use the unrevoked method to root 2.1. This is what worked for me testing on my brother's EVO, so if you do end up trying something else to root 2.1 with, PLEASE do not post it here or ask questions, for I will only support the unrevoked team.
Now open up your web browser on your computer and navigate to Unrevoked
Choose the correct operating system to download for.
*
Make sure you install the modified android usb driver that comes with the unrevoked3 install (see the html file included when you extract the exe)
Once downloaded and extracted, run the program on your computer.
Make sure your EVO is plugged in with USB DEBUGGING ON!
It will reboot to the bootloader, and it will wait for you to use volume down to select HBOOT USB. (the last option)
After you have selected it (by pressing the power button) let the unrevoked3 program handle the rest of the flashing.
If you have had any trouble with the bootloader freezing or not moving for over 3 minutes, you most likely forgot to uninstall HTC Sync (as directed at the beginning of this guide), or you need to install the modified hboot drivers that come with the unrevoked3 program, OR a nasty combination of the both.
For the modified drivers and explanation on how to install them, open the "hboot driver.htm" file that gets extracted when you extract the reflash_package.exe. It will explain everything. You will have to reboot your phone after you install the drivers. Once you have repaired this go back to the big blue *
As soon as it is booted into recovery, you are done with that.
Next in recovery go to
Code:
install zip from sdcard
then
Code:
choose zip from sdcard
and choose the
Code:
unrevoked-forever.zip
This will flash the unrevoked forever hboot unlock.
_____________________________________________________________________
Part 2
Note: This section would not have been possible without the amazing testing and help of cilio87. He earns a gold star *
Now it's time to finish up the process and flash the stock 2.2 build of Android. You need to do this before any custom ROM in order to re-update the partitions we downgraded in the rooting process.
Step 1: Download either the update zip with
ClockWorkMod recovery included
or
Amon_RA's recovery included
This is the most up-to-date version of Amon_RA recovery that allows you to back up WiMAX partition.
(Either zip contains the final touches to the root process, one flashes clockworkmod recovery, and the other respectively, Amon_RA's recovery)
Extract the 3 files inside the zip to your desktop.
If you are still in recovery (from part one or the guide) go back to the main menu of recovery on your phone (if you aren't already at the main menu, hit vol up & down at the same time) Select
Code:
Reboot System Now
Let the Rom load, and when it gets to the sign in screen for Google, just skip everything and let the ROM boot.
If you are already on a custom rom, boot into it and follow from here.
Once It is fully booted, mount your sdcard onto your computer, and copy the 3 files you extracted from the zip to the sdcard.
Once copied, Unmount your sdcard from the computer.
Step 2: Unplug your phone from the computer. Power it off completely. Now while holding VOLUME DOWN turn on the phone with the power button, continuing to hold volume down. This will boot into hboot. You can release the buttons once you get to the hboot menu. Then use the power button to click on bootloader. This will scan the sdcard for the new PC36IMG.zip you just copied to the sdcard. When it asks "Do you want to start update?" Hit Volume Up for Yes. It will reload the zip and then start the flash. Once the flash is complete (may take 5 or so minutes) Choose NO when it asks you to reboot.
Step 3: After choosing NO to the reboot, you will see a menu again. Select Bootloader from the menu, then use the Volume Down button to hover over "Recovery" and press Power to click on it.
If your phone gets stuck at the White EVO 4G screen, pull your battery, and then power on while holding volume down again. It should boot to the bootloader again, where you can select recovery.
Once you are booted into this custom recovery, go to
Code:
Install Zip from sdcard / Flash zip from sdcard (Amon_RA)
and then (clockworkmod only)
Code:
choose zip from sdcard
You will then see the 2.2-root.zip. Click on that and accept the flash.
Once that flash is complete, return to the main menu of recovery and Select
Code:
Reboot System Now
You now have stock Android 2.2 with root and all updated partitions!
If you would like the flash_image binanry so you can flash new recovery images quickly from adb shell, flash the zip that is attached below as a normal zip in recovery AFTER you have completed this entire guide.
IN ORDER TO FLASH CM6 OR DAMAGE CONTROL, YOU NOW NEED TO FLASH THE ENG SPL. LOOK FOR IT IN THE EVO 4G ANDROID DEVELOPMENT FORUM.
Here is the ENG SPL
Good Luck!
Dan Wager
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Yes! I look forward to the rest of your post
Sent from my PC36100 using XDA App
Great news everyone!
Eagerly awaiting.
Awesome xD
Sent from my HTC Evo 4G using XDA app.
Oh thanks! Gonna be watching this all night! This is gonna be AWESOME!!
Vandam500 said:
Finally no more people asking about it
Click to expand...
Click to collapse
if only you were right...
I love the xda forums, good job to everyone involved, another reason I love my evo.
Sent from my PC36100 using XDA App
I wish I didn't just take my xanax. Ughhhh
Vandam500 said:
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Click to expand...
Click to collapse
I'll add with another question that will "end"
Will this allow me to have PRI 1.40?
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Details---
I've heard the process is more than a simple click like simple root or unrevoked... But at least we have root.
It will be nice to see the detailed failsafe guide so I don't go around bricking phones and hopefully an automated prog is made to make it a breeze.
A great help!
Having a B-day tomorrow, and have searched the month of August for a complete method to root my froyo 2.2
Thank you in advance for your expertise and assistance..
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Thank you
OMG you guys are the best devs ever ill be stuck to this like glue once again XDA is the best forum on the planet.
edufur said:
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Click to expand...
Click to collapse
no, once you get to that point you have other stuff to do.
just wait til the guide comes out... We've waited how long for this thing? an extra hour or so won't kill you. (hopefully)
Yeah, almost done writing the guide. Try not to give out anymore details yet, I should be posting the full guide shortly.
sprink0281 said:
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Click to expand...
Click to collapse
And your message is wholly important? Yes, the title says "guide" but that means that the original post will contain the guide. This is a forum, not a wiki. (I know my message doesn't help at all either)
Hooray, root on 2.2!
please make it easy for us newbies too please
Greenfieldan said:
please make it easy for us newbies too please
Click to expand...
Click to collapse
I'm getting the basics out tonight and will make it an easy read like my Hero rooting guide tomorrow sometime, because I am exhausted tonight.
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
Hi,
Is there any method to keep using stock Rom with root and do not wipe the data?
Thanks
Root nexus s rom 2.3.6
Ehi!
I'm also looking for that!!
I just got the nexus S whit the 2.3.6 rom and I want to root it, but I haven't find any answer online
someone can help us??
thanks!
http://forum.xda-developers.com/showthread.php?t=1007782 read this topic page1 and page 49 very important...
please click thanks button
- -
easiest way
just install from recovery this file
if i didn't upload wrong file...
does not work for me, signature verification failed...
here is the link for your question:
http://forum.xda-developers.com/showthread.php?t=935819
the link does not work for 2.3.6 as google fixed the issue on fasboot boot...
---------- Post added at 04:09 PM ---------- Previous post was at 04:01 PM ----------
Damned what a crap...
Has been two days looking around to find a solution, and seems not possible for the 2.3.6...
What a shame google to pretend having open source system and having no way to unlock your device without loosing your data as
- The data is wiped as you unlock the device.
- To fu**ing backup the data you need to have a fu**ing unlocked device.
WTF, I just got it in my ass..
If someone at last know a way....
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
plipness said:
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
1. Make sure Part 1 is completed.
2. Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
3. Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
4. Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
5. We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
6. With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
7. Open a command prompt window (Start > Run > cmd.exe).
8. Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
9. Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
10. We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
11. Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
12. Using the Volume buttons and Power button, select install zip from sdcard.
13. Select choose zip from sdcard.
14. Select the su-version#-signed.zip file you downloaded earlier and apply it.
15. Select yes (there are lots of nos).
16. Confirm it says something like this: install from sdcard complete
17. Select Go Back.
18. Select Reboot.
19. Done! You should still have all your data present on your phone, and have root access!
all credits goes to Jonathon Grigg
Click to expand...
Click to collapse
As said before, does not work anymore for 2.3.6 as google has fixed this exploit...
Root & TWRP Lenovo Tab 2 A8-50F (MT8161)
Ok so this is a in depth tutorial on obtaining root and installing twrp for the device in the title. Anything in "quotes" eg, type in cmd "adb devices" quotes should be ignored. This guide is for those who know what root is and know there way around windows and Linux. If you did something wrong i am not liable and maybe you should have read things before trying.
EDIT: for those of you who want to root in one or two clicks i have added support for this device in the ZEUS TOOLKIT wich will root without installing custom recovery.. LINK >> http://forum.xda-developers.com/showthread.php?t=2644166
REQUIREMENTS/DOWNLOADS:
-Windows PC & Linux (Ubuntu. virtual box would be fine although i have my pc dual booting both os's)
-Driver Signing Disabled on Windows 7 and above
-Device Drivers
-SpFlash Tool (including scatter file)
-Adb Tools
-TWRP + SuperSU Files
-Insecure Boot.img
LINK FOR ALL REQUIRED FILES >> DOWNLOAD << DOWNLAOAD AND EXTRACT TO DESKTOP
Downlaod all of the above and extract/move everything to a folder which for this guide i will assume will be called ROOT on your DESKTOP
SOME READING:
The Lenovo Tab 2 A8-50F is a rather locked down device with the ability to reflash the stock rom on every reboot if required. In this guide you can only do things in a specific order to be able to get it rooted and stop the stock recovery reflashing. It took me a few times of (soft)bricking my device before i could get it sorted to a stable rooted system with twrp installed. TWRP recovery was not built from source by me personally (it was obtained from a russian website) although i have had to modify the TWRP image as it was boot looping but its sorted and working now. So roughly this is how things are going to go, we will use SpFlash tool to readback the system partition, then use linux to modify a file in the system.img the use SpFlashtool to refalsh the modified system.img. Then we are going to unlock the bootloader and then flash an insecure boot.img along with twrp and then root using chainfire's latest binarys.
THE GUIDE:
STEP 1 - installing the drivers
For this i will assume you you have already got adb driver installed if not please google it i personally used googles generic adb driver.
Please make sure you have disabled driver signing for windows "GO HERE". Now open device manager and right click on your pc's name at the top of the list and select add legacy hardware > click next > check "install the hardaware that i manually select from a list (advance)" and click next > highlight "show all devices" and click next > click "have Disk" > click "browse" > browse to the desktop\root\MTK Drivers all windows\ and choose the folder to match your windows installation and then choose the 32bit or 64bit driver file depending on your windows install > click open > click ok > highlight "MTK USB PORT" > click next > click next > if a warning pops up click install anyway > click finish. Your drivers are now installed for spflash tool to recognise your device.
STEP 2 - backing up system partition
Make sure your device is truned off and disconnected from your computer. Open SPFlash Tool form "Desktop\ROOT\SPFlash_tool\flash_tool.exe" > click "scatter-loading button > browse to "Desktop\Root\ and open MT6735_Android_scatter.txt > click the readback tab > click add > double click the entry which is now listed >browse to "Desktop\Root" and in the filename box type "system.img" > click save > check "HEX" > for region select EMMC_USER > for start address type "0xb000000" > for length type "0x74000000" > click ok > click readback. now with your device turned off connect the usb and the SPFlash tool will begin to backup your system partition to "Desktop\Root\system.img" wait until its finished and continue to the next step.
STEP 3 - editing the system.img
Now we have the system.img transfer it via usb (or whatever means) to your ubuntu machine place system.img in your ~/Home/ folder eg. ~/Home/System.img now open a terminal by pressing CTRL + T > type "mkdir output" press enter > now type "sudo mount -t ext4 -o loop system.img output/" press enter > type your sudo password > press enter > type " cd output" press enter > type "sudo mv recovery-from-boot.p recovery-from-boot.bak" press enter > type "cd" press enter > type "sudo umount output/" press enter. The system.img has now been modified and can be transfered back to windows. Goto next step.
STEP 4 - unlocking bootloader
With device booted to android and usb debugging enabled open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot bootloader". Your device will now reboot into fastboot mode when it displays "fastboot mode in the bottom left of the screen type into cmd "fastboot oem unlock" > press enter > screen will change and ask you to confirm do this by pressing vol+ > wait and when a screen with three boot options appears DO NOTHING and go to next step.
STEP 5 - flashing insecure boot.img
Now you should have the ability to flash the boot. Type into cmd "fastboot flash boot boot.img" the device will let you know it is done and when it is done flashing just type into cmd "fastboot reboot" and let the device fully boot and goto the next step.
STEP 6 - flashing modified system.img
now open SPFlash tool again it should have remembered the scatterfile if not reload the scatter file. In the main window of the download tab make sure ONLY system is checked then in the location colum click the space in line with system and browse to your modified system.img and click open. At this point before doing anything make sure your device is turned off and not connected to the computer in any way. Now click Download in SPFlash tool then connect your device via usb while turned off and the tool will begin flashing the system.img wait until it is finished and a green tick appears in flash tool and if your device does not boot automatically then unplug it and reboot it wait until it fully rebooted and goto next step. You can close flash tool for now.
STEP 7 - flashing TWRP recovery
with your devfice now booted with a custom boot and system image open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot bootloader" > press enter your device will boot into fastboot mode again when it has type "fastboot flash recovery recovery.img" > press enter > when its done type "fastboot reboot" > press enter now wait for the device to fully boot and goto next step
STEP 8 - flashing Supersu by Chainfire
Now your device has rebooted it will be missing the super user app and all binary's so open file explorer on your computer and copy the SuperSU-v2.46.zip from the ROOT folder on the desktop to the download folder on your device after doing that open cmd prompt and type "cd C:\Users\robert\Desktop\ROOT\adb" > (replace "robert" with your username) press enter > type "adb reboot recovery" > press enter. Your device will now reboot into TWRP recovery check the little box and swipe the arrow at the bottom to continue now touch install > touch Download > touch SuperSU-v2.46.zip and finally swipe to install. when it is finished reboot. Hey presto one rooted device with a fully working twrp. reboot and download busybox from play store and install as some programs like system app remover need some binarys from busybox.
After following the above steps you will have a fully rooted device wich can be backed up via twrp and flashed via twrp. now i have figured this out, i think its someone elses turn to build a rom for it preferably Cyanogenmod Thanks for reading this guide and all the best luck with your new rooted device. please remember to click thanks.
Have you found a way to root it without the need for Linux?
Hi
I would like to know if this guide will work for MT-8735
Thanks in advance,
Dimitris
Anyone found a way to root MT8735 version A8-50L or A8-50LC?
The files seem to be missing...
Any help would be much appreciated. I used the guide fine up until the Step 5.
Now I'm a bit stuck.
Gromit1996 said:
The files seem to be missing...
Any help would be much appreciated. I used the guide fine up until the Step 5.
Now I'm a bit stuck.
Click to expand...
Click to collapse
I used something called Kingroot along with the info and files found here https://forums.lenovo.com/t5/Androi...-to-root-TAB2-A8-50-WiFi-version/td-p/2181021 to help me root without using linux. There is a ROM listed there. If you use Kingroot.apk, you'll have to run it 2 or 3 times to get the ROOT to stick, then you can enable debugging, and oem unlocking in dev options. Afterwards, you can use fastboot to unlock the bootloader and once that's done, use the SP Flash tool to download Max Choen's rom to the device, install SuperSU and Busybox and your gravy!!!
what files? that post does not have any files provided and could someone upload the files that are missing from the post so we could also use them?
keith.valdez said:
I used something called Kingroot along with the info and files found here https://forums.lenovo.com/t5/Androi...-to-root-TAB2-A8-50-WiFi-version/td-p/2181021 to help me root without using linux. There is a ROM listed there. If you use Kingroot.apk, you'll have to run it 2 or 3 times to get the ROOT to stick, then you can enable debugging, and oem unlocking in dev options. Afterwards, you can use fastboot to unlock the bootloader and once that's done, use the SP Flash tool to download Max Choen's rom to the device, install SuperSU and Busybox and your gravy!!!
Click to expand...
Click to collapse
Who is Max Choen and there are no files in the link provided.
Sent from my LG-D852 using Tapatalk
If you guys read the entire post in the link I sent you might be able to get where I got. I'm not a dev and not much for writing tutorials but my process went,
1. KingRoot
2. Unlock boot loader
3. Flash twrp via fastboot or flashify
4. Factory reset
5. Reinstall King root and re root.
6. Format and partition memory card
7. Install apps2sd
8. Install Xposed
9. Install obb to SD module
10. Enjoy tablet with 64gb of space with tons of large data games installed!!!! (Note that this step requires you own a 64 gig memory card)
keith.valdez said:
If you guys read the entire post in the link I sent you might be able to get where I got. I'm not a dev and not much for writing tutorials but my process went,
1. KingRoot
2. Unlock boot loader
3. Flash twrp via fastboot or flashify
4. Factory reset
5. Reinstall King root and re root.
6. Format and partition memory card
7. Install apps2sd
8. Install Xposed
9. Install obb to SD module
10. Enjoy tablet with 64gb of space with tons of large data games installed!!!! (Note that this step requires you own a 64 gig memory card)
Click to expand...
Click to collapse
Where are you getting a twrp build for this tablet?
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Gromit1996 said:
Where are you getting a twrp build for this tablet?
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Click to expand...
Click to collapse
I will post it in the morning, I think it's on my wife's laptop. The link I posted USED TO lead you to a post that had the files I mentioned and the process I followed. Now they are just suggesting you simply root using Kingo... Which is fine and dandy but does not give you the ability to format your memory card. I will post my recovery image for yall in the morning. You would just have to use KingRoot and then flash TWRP using Flashify once you have a successful root. Then you can format your card and install apps2sd of your choice and xposed with the obb2sd module! That's what I got going on, got TONS of large data games on the tablet cause I installed a very fast 64gb memory card, and BIGGITY BAM!!!! Turned this little budget tablet into something decent for the kiddos! Just wish we could do something about that terrible 1gb of memory, but hell, I was able to get this far so I'm pretty happy!:laugh::good:
keith.valdez said:
I will post it in the morning
Click to expand...
Click to collapse
Define morning in your neck of the woods. [emoji2]
Sent from my Lenovo TAB 2 A8-50F using Tapatalk
Here it is!
Had some things to take care of first. Got a wife and kids to care for before I do my geek stuff. This is not a flashable zip! You must unzip the .img file and use Flashify after a successful KingRoot.
P.S. all credit goes to the original creators of this build of twrp I originally obtained in This Very XDA post we are conversing in! All I did was download this file, I am not a dev andi do not take credit or responsibility for any of the files I've used to root this device! Cheers!!!!
Okay... Thanks. I have SuperSU installed and working. TWRP installed and working, but I haven't unlocked the bootloader.
Will this prevent me from installing xposed framework, do you know?
And the which apps, by which developers, do you install to move apps to SD card?
Thanks for your help!
Sent from my LG-D852 using Tapatalk
I am using Link2SD, Xposed OBB2SD module. That's about it. Not sure if bootloader unlocking is even necessary for anything.
keith.valdez said:
I am using Link2SD, Xposed OBB2SD module. That's about it. Not sure if bootloader unlocking is even necessary for anything.
Click to expand...
Click to collapse
Just to get the custom recovery to stick.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Can you flash supersu from stock recovery or do i have to flash twrp first?
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip" 2016-04-06 version
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
for those of you who want to root in one or two clicks i have added support for this device in the ZEUS TOOLKIT wich will root without installing custom recovery.. LINK >> http://forum.xda-developers.com/show....php?t=2644166
Hi,
The link does (no longer) work, can you please update it?
Thanks!