[General Topics] mrmazak:
Root has been achieved for rca tablet, With the intel atom chip

Basic steps are Just like many android devices.

1. Unlock boot loader

2. Flash modified stock recovery

3. Test boot a permissive boot.img

4. Flash permissive boot.img (if test boot was ok)

5. Boot into Custom recovery and flash superSu.

The modified recovery has adb active. This is needed to get back into bootloader mode if flashing goes wrong.

Because on the RCA tablet there is no button combination for bootloader boot mode.

Steps that the included tool performs:

First step tool does is ask soc type. (intel or MTK) for this guide it needs to be intel.

1. Guides user through the bootloader unlock steps.

adb reboot fastboot

verifies the status of unlocked or not

verifies the ability to do unlock in not already unlocked

fastboot flashing unlock

fastboot format userdata

fastboot format cache

fastboot reboot

2. Fastboot boot generic CWM recovery. To use its root shell for copying devices boot.img and recovery.img

3. Use Carliv Android Image kitchen tools to unpack the pulled boot.img and recovery.img

RECOVERY

4. copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\data\misc\adb\adb_keys

copy adbkey.pub from pc running the patch to stock-recovery\ramdisk\adb_keys

this s done to ensure an authorized adb connection to device even after factory reset and data format

5. Edit recovery\ramdisk\default.prop as follows:

"ro.secure=1" to "ro.secure=0"

"ro.debuggable=0" to "ro.debuggable=1"

"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"

add line: persist.service.adb.enable=1

add line: persist.service.debuggable=1

6. Use Carliv Android Image kitchen tools to re-pack recovery

BOOT

7. copy adbkey.pub from pc running the patch to stock-boot\ramdisk\data\misc\adb\adb_keys

copy adbkey.pub from pc running the patch to stock-boot\ramdisk\adb_keys

this s done to ensure an authorized adb connection to device even after factory reset and data format

8. Edit boot\ramdisk\default.prop as follows:

"ro.secure=1" to "ro.secure=0"

"ro.debuggable=0" to "ro.debuggable=1"

"persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb"

add line: persist.service.adb.enable=1

add line: persist.service.debuggable=1

9. Edit boot\ramdisk\*fstab* as follows:

"forceencrypt" to "encryptable"

10. Add these lines to boot/ramdisk/init.rc after the line that starts: "on init"

# root use Permissive

write /sys/fs/selinux/enforce 0

11. Swap sepolicy and /sbin/adbd with permissive (insecure) versions included in tool "/img" folder

12. Use Carliv Android Image kitchen tools to re-pack boot

CWM

13. Use Carliv Android Image kitchen tools to unpack the generic CWM

14. copy stock-recovery\recovery.img-kernel to unpacked generic CWM folder (replacing file that is there)

copy stock-recovery\recovery.img-second to unpacked generic CWM folder (replacing file that is there)

15. Use Carliv Android Image kitchen tools to re-pack CWM

SECOND / FLASH MENU

16. fastboot boot patched boot.img

used to verify patched image does not cause device to brick

17. fastboot flash boot patched-boot.img

flashes patched-boot (user must have verified boot image works in previous step)

then formats /data to remove encryption

18. fastboot flash recovery patched-recovery

stock recovery does not seem to work when booted, so test booting pached image not done

this modified recovery is needed to be able to get back to bootloader mode if trouble occurs.

19. Load patched CWM

loads patched recovery to be used to flash SuperSu and also to make device "back-ups"

Updated 2-4-2018 Multi-platform-patch-tool

==>>

Multi-platform-patch-tool

Downloads Needed:

Download adb=fastboot 15 second instal == https://xdaforums.com/showthread.php?t=2588979

Download intel drivers == https://software.intel.com/en-us/protected-download/385047/494732

Download SuperSu.zip == https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

Thanks:

[MENTION=2472806]vampirefo[/MENTION] for most of the needed parts to make this work. CWM, permissive su-policy, without that this would not be possible

[MENTION=5186178]bluefirebird[/MENTION] For the image unpack tool

Youtube video I found , of someone explaining how he used the files to root his device.

Video is from before patch tool written. Video was from when individual build files were available.

New method of patching individual device files , removes possibility of flashing files from wrong device.

[YOUTUBE]fU-z1JlUKjI[/YOUTUBE]

History of this root method started in this thread.

https://xdaforums.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625