Database Info

Boot Animation with SkyRaider

Sorry about the post but I cannot find the post were it tells me how to install custom boot animations. I also need to be able to do the sounds. As far as I understand I have to put it in the media folder. I found the original one but it does not allow me to move it. I'm assuming I have to do it from recovery but I don't know how. Detailed instructions would be appreciated. I have a cold and the old brain is doing so well. Thanks

s-off your dinc and you can do it while booted

I was trying to avoid that because they do not have a way to undo s-off yet. Just incase my phone dies I dont want verizon to say I voided the warranty. Any way to do it without?

You can flash some of them from rom manager...that's how I did mine.

If you have rooted your phone, which you must have in order to install a custom ROM, you've already voided your warranty.
Adding S-OFF wouldn't change anything in the eyes of Verizon, and you can always drop your phone until it's physically broken if you need to take it in.

rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from

MMBosstones86 said:
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
Click to expand...
Click to collapse
When I try to install from Rom manager it doesn't load it says verification failed or something. Does anyone know how to manually install Droid 2 boot screen.
HTC incredible
SR sense 2. 5. 2
Radio 2. 15
Sent from my ADR6300 using XDA App

Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.

Doctor Butts said:
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Click to expand...
Click to collapse
I'm not sure how to do step 2 your referring to. If you have a link to a thread that explains how to do that, it would be greatly appreciated.
Sent from my ADR6300 using XDA App

Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.

Doctor Butts said:
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Click to expand...
Click to collapse
THANK YOU SIR. MUCH APPRECIATED.
Sent from my ADR6300 using XDA App

Coby Kyros Internet Tablet MID7005-4G

HSN Launches Coby Kyros Internet Tablet 7" Android OS 2.1, 800MHz with 1080p HDMI review by me (note just click on the image to get to the review)
Coby Kyros Internet Tablet MID7005-4G Work-in-Progress Review by me
(note just click on the image to get to the review)

hi
hi where did you buy this ive been looking for a while?

I got a 7105-4g at k-mart yesterday.

Hey, I have a Kyros MID 7005-4G too. Unfortunately, it's pretty screwed at the moment. I'm looking for a recovery image for the device. If anyone can get me a recovery image of one of these, I'd be very grateful. I've tried a recovery image MID 7015, but they don't seem to be similar enough to work. Anyone?
Edit: On second thought, the Framework.jar file from an MID 7005-4G would help too.

Market
Yea, I just bought the MID7005 and it's cool. The resistant touchscreen is a little difficult at times. I really want googles market on it though. Id love to know how? Anyone?

clockworkmod/cyanogenmod/market on 7005
If you're interested in modding your 7005, I bought a used one on ebay. It was locked and the password lost by the previous owner when I got it, and it seems like it's been dropped because the charger is pretty intermittent. I don't think my battery is charging...
Anyway, if you want google market on it you will need to root your device and install a custom recovery.
What you will need:
SD card 1gb <
computer with the Android SDK (you need to use the ADB)
z4root
dump-recovery-signed.zip
clockworkmod recovery for the X5A-G
Cyanogenmod 7 for X5A-G
GAPPS (Google Apps) flashable zip
NOTES
***if you're very brave you can try using terminal emulator, but I don't recommend it. This tablet doesn't have a lot of power and crashing or freezing at any time during this process will almost definitely brick it. Just use the ADB and don't take the risk!***
I can confirm that both Clockworkmod Recovery and the Cyanogenmod 7 ROM for the X5A-G work on Kyros 7005.
1. install z4root and permanenty root. reboot
2. link removed at owner's request
you can get into the recovery by either holding home and power at bootup, or by enabling USB debugging on the tablet and then issuing the command
Code:
adb reboot recovery
Once you are in the recovery, select update from .zip file. This will trick your tablet into thinking it is preforming a firmware update, when in fact it is running a script that is backing up the recovery to your SD card.
3. download the x5a-g clockworkmod recovery .zip. Renaming it as 'update.zip' and attempting to flash using stock recovery does not work. You will have to do this manually, either via the adb or terminal emulator. I strongly suggest using the adb.
4. extract the clockwork mod recovery .zip file and find the recovery.img file. Copy recovery.img to the root of your sd card (in other words just drag and drop the recovery.img into the sd card)
5. obtain a root shell. If you don't know what that means you REALLY should not continue with this tutorial!!! open up a terminal/cmd prompt and start the adb.
Code:
adb shell
Code:
su
The prompt should now change to # indicating that you have gained root access. a prompt screen may show up on your tablet asking you to allow "unknown" root access. Click allow and proceed to the next step.
6. Flash the recovery.img from the root of your SD card
Code:
flash_image recovery /sdcard/recover.img
* I think this should go without saying, but you do have to insert the sd card into tablet and allowing android to mount it...
7. reboot into your new recovery
8. make a backup of your system. This is a precautionary measure to ensure that you will have at the very least a working system to boot back into. Reboot.
9. before you flash the cyanogenmod rom, you will have to do a factory reset and format /system from recovery. Once you've done this, you can proceed to flashing Cyanogenmod 7 rom. After the flash completes, reboot the tablet. Don't be alarmed or think that you've bricked your device. The first boot takes a LONG time. After you boot up for the first time you should be prompted to calibrate the screen. if the tablet doesn't automatically prompt you to calibrate the screen, fire the adb shell back up and enter the command
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
** it has been my experience that after first calibration the screen will not operate properly until after a reboot. Don't be alarmed! Just reboot using the command
Code:
adb reboot
since you probably won't be able to get the tablet to do so from the screen/buttons.
10. Once you have booted back into your tablet which should take considerably less time than the first boot after flashing, you will now be looking at the Cyanogenmod 7 desktop for the first time! Now you need to gain access to the google market. reboot into recovery, which can easily be done now from the shutdown menu.
11. flash the gapps .zip file and reboot
12. Your tablet will go through the "New Phone Setup" process. you will be prompted to set up a bunch of things, but you can skip past a lot of it. once you get to the desktop, connect to your wifi, open the market and off you go!

[Q] Recovery for my ZTE V790?

Hi...
I need Flash the CWM Recovery in my ZTE V790, I've searched on google but I found nothing ...
u.u...

Late response but may help others
manubarz said:
Hi...
I need Flash the CWM Recovery in my ZTE V790, I've searched on google but I found nothing ...
u.u...
Click to expand...
Click to collapse
Look here: https://ztev790support.wordpress.com/instructions/instructions-for-flashing-recovery/
OR FOLLOW THESE INSTRUCTIONS WHICH MAY BE EASIER TO ROOT THE ZTE V790 AND INSTALL CWM:
0. You will need the flashable SuperSu v2.46.zip from here (https://download.chainfire.eu/696/SuperSU) and the CWM v5 recovery zip from here (http://v790.blogspot.com/2013/06/recovery-for-zte-v790.html) but don't run the bat file. Place the SuperSu zip and the recovery.img on your SD card.
1. Set USB Debugging to ON from the Development option and place the SD card in the phone.
2. Use Kingo Root to root the phone...normally this will result in the phone being rooted. If the phone is properly rooted with the super user app installed, then reboot the phone and go to step 5.
3. If Kingo Root reports that the phone is successfully rooted but you don't see KingUser or SuperSu installed, then you have to proceed with some other steps to complete the rooting process:
a. Place a copy of the extracted CWM recovery.img into a folder on your Windows computer
b. Connect the phone to the computer via USB cable
c. Open a windows command prompt at the directory where the CWM recovery.img is stored on the computer
d. Execute the adb commands: 1) adb reboot bootloader 2) fastboot boot recovery.img (this will TEMPORARILY run CWM on your phone)
e. Once CWM is running on your phone in recovery mode, you can now flash the SuperSu v2.46.zip from the SD card
f. Your phone is now fully rooted
4. Reboot the phone normally (CWM was only temporarily being run in order to flash the SuperSu zip...we will permanently flash the CWM recovery onto the phone in the next steps). Be sure you have a copy of the CWM recovery.img on the SD card.
5. Download a Terminal Emulator from the PlayStore (or however you please) and install it on the phone.
6. Execute the following while in Terminal Emulator:
a. su
b. flash_image recovery /sdcard/recovery.img
7. You're all set with CWM permanently on the phone. Note that the first 4 steps above were simply to root the phone. The CWM installation is trivial once your phone is properly rooted.
Angelo

Root & TWRP Lenovo Tab 2 A8-50F (MT8161)

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!

RCA Voyager III (RCT6973W43MD) Root Using Magisk_Manager and Stock Boot Image

First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB." Also make sure "Install Apps from Unknown Sources" is enabled.
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sd card in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.

akonobi said:
First I want to say that I'm not a developer nor in any way an expert and I'm sure that will be apparent as you read my post. I was able to root my Voyager III tablet by reading and following the work of people like diplomatic and topjohnwu, and using the products of their work. I looked everywhere for a specific root method for this little tablet but could never find one. The fact is there has always been a method since topjohnwu's Magisk_Manager's ability to patch stock boot images and re-pack them for use in your specific MTK-based phone or tablet. It just hasn't been obvious that the RCT6973W43MD Android 7.0 was a candidate for that root process...at least not to me. In any case, this is what I did to achieve root. But first...
**Do these steps at your own risk. They worked for me but I won't be responsible for any damage you do to your phone or tablet**
Unlock Bootloader
1. In your tablet, enable Developer Options by going to Settings> About Tablet> Build number. Press "Build number" 7 times to reveal "Developer options." Press Back button to see and enter "Developer options." Enable "OEM Unlock." While you're there, enable "USB Debugging," disable "Automatic system updates" and "Verify apps over USB."
2. Using adb, after your device is recognized, type:
adb reboot fastboot
fastboot flash oem unlock
fastboot reboot
Your bootloader should now be unlocked. On your boot screen it will say, "Orange State." (never try to re-lock the bootloader because that will put your device into "red state" which is very bad. You've been warned!)
Extract Your Tablet's Boot.img file using MTK-su
1. You need the boot.img file of your specific ROM to allow Magisk_Manager to patch it...in order that Magisk may be installed as superuser. What better place to get that file than your own device? Use diplomatic's MTK-su exploit to gain temporary superuser access to your tablet's root file system. Your boot.img file can be found in /dev.
2. Still superuser under MTK-su, copy the boot.img file to your sdcard in at least two locations. The reason for this is to make sure you can easily find it later when you've left MTK-su's root shell. Something like this should work...
cd /dev
cp bootimg /storage/emulated/0
cp bootimg /storage/emulated/0/Download
**Note** In /dev your boot.img file is named "bootimg". When you copy (paste) it to your sd card it will appear as "boot.img".
Patch Your Tablet's Boot.img file with Magisk_Manager
1. Download Magisk_Manager v7.5.1 apk and install on your tablet. Patch your boot.img file. Press Install . Install> "Select and Patch a file". Navigate to your boot.img file and select it. Wait a few seconds for the patching to start and note the location of the newly patched boot image named magisk_patched.img. Flashing this personalized boot image will allow you to install Magisk v20.4.
2. Now using adb and MTK-su again, start a root shell and find the magisk_patched.img file and copy it also in at least two places to make it easy to find and later transfer to your desktop. My experience was that I copied it to my sd card but couldn't find it when i left the root shell and tried to get it onto my desktop. The point is that you want the file in a directory that your desktop file manager can access. I'm a noob so I made a few copies of it.
At this point it might also be a good idea to review topjohnwu's Magisk boot-patching thread here to glean any information that may apply to the Voyager 3, although that tablet is not mentioned by name.
3. On your computer using adb fastboot:
adb reboot fastboot
fastboot flash boot /path/to/magisk_patched.img
fastboot reboot
4. Download Magisk.20.4.zip and install it from your tablet's recovery or via adb. You should now be rooted and the Manager app should show both Magisk_Manager and Magisk superuser installed. I know there's probably easier ways to do this, and lots of shortcuts, but this is what worked for me.
Click to expand...
Click to collapse
I know the above is not as clear as I would like to make it, and I invite others to refine the method so that people can easily follow it. But the fact is that it works. I've duplicated it after mistakenly factory-resetting my device. I tested it using Fx File Explorer which now has been granted superuser powers. I'll post photos soon to prove root status. Again please feel free to add to, detract from, or in any way help to make my explanation more accurate and concise. Of course all credit goes to the guys who made the tools I used, @topjohnwu and @diplomatic.
The overall thrust of what I've tried to describe is 1) patch your own boot.img file with Magisk_Manager and flash it to your bootloader and 2) load Magisk superuser app in the now friendlier boot environment to obtain root. That's it.

I've been doing taxes lately...years of taxes, but I finally read up on posting images so here. Not exactly like I wanted them to post, but it does the job.

Also it is very important that you do not upgrade MagiskSU within MagiskManager. Flash any updates through your recovery. If by chance you try updating through MagiskManager your root will be gone and if in bootloop you will have to wipe device and start again with the step of extracting your boot.img.

Also, remember to check which processor your tablet has before you try modifying it. RCA came out with many, many confusingly similar part numbers. Only some of them have MTK processors with others being (at the very least) Intel or Rockchip.