[Guide] RCA Voyager RCT6873W42 Unlock Boot loader and root

Search This thread

strubedo

Senior Member
Aug 13, 2014
62
5
I need adb key for v19 for pc my screen is cracked and have to use otg mouse i cant make the rsa key because of the broke screen.
 

jonthn41

Member
Oct 29, 2015
24
3
Bakersfield
That would require a custom recovery, the root method would be same as this one.

A custom recovery, custom boot.img and SuperSU.

Sent from my Life_Max using Tapatalk

if you have access to a boot.img file you can push it to your device and have magisk-manager.apk root it.. I did this for a tablet i have, however I had to unpack the patched-boot.img and edit the default.prop a little bit to get it to boot.
 

CargoJacker

Member
Nov 23, 2017
8
2
question

i have a recent rca voyager 3 (w43MD) on android 7.0 intel proc
seeing the problems with the older voyager 3's i recogn it's gonna be nearly impossible to root?
 

jodieb

New member
Sep 12, 2018
1
0
Voyager not recognized by sdb

I have a Voyager module RCT6873W42. I have turned on OEM unlock and USB debugging in developer options. I have also installed adb fastbook and the intel driver. However, when I enter "fastboot devices" nothing is found even though the device does show up in my file manager.
 

Droidriven

Senior Member
Jan 27, 2014
15,603
11
5,419
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I have a Voyager module RCT6873W42. I have turned on OEM unlock and USB debugging in developer options. I have also installed adb fastbook and the intel driver. However, when I enter "fastboot devices" nothing is found even though the device does show up in my file manager.
Sometimes you have to manually select the adb driver for the device in device manager.

Sent from my LGL84VL using Tapatalk
 

Isrgish

Senior Member
Jan 5, 2018
103
15
I'm getting a message that there is a critical update for my tablet from RCA. When I tried to upgrade I got an error that it found unexpected information.

Does anyone know if this is related to the device being rooted? Or how to go about upgrading the system?
 

Droidriven

Senior Member
Jan 27, 2014
15,603
11
5,419
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I'm getting a message that there is a critical update for my tablet from RCA. When I tried to upgrade I got an error that it found unexpected information.

Does anyone know if this is related to the device being rooted? Or how to go about upgrading the system?
Boot to recovery and choose factory reset to reset the device, then choose wipe cache partition(this might remove the "unexpected information") then wait for the update notification to pop up again, then try the update.

Sent from my LGL84VL using Tapatalk
 
Last edited:

Isrgish

Senior Member
Jan 5, 2018
103
15
I'm trying to backup my device via CWM recovery. But I can't mount the external Sd card I get "Error mounting /external_sd!"

I know that the external SD card isn't at /external_sd.

How do I go about mounting the external SD card.

Thank You,
 

Droidriven

Senior Member
Jan 27, 2014
15,603
11
5,419
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I'm trying to backup my device via CWM recovery. But I can't mount the external Sd card I get "Error mounting /external_sd!"

I know that the external SD card isn't at /external_sd.

How do I go about mounting the external SD card.

Thank You,
Not all devices are the same, when using the temp recovery tool, some devices can use it to create a backup but not all can. The tool is designed to work with many different devices. Some are only compatible enough to boot the recovery session long enough to root, some are very compatible and can use all the features. The backup feature will work on some models but not on others.

Sent from my LGL84VL using Tapatalk
 

Isrgish

Senior Member
Jan 5, 2018
103
15
Not all devices are the same, when using the temp recovery tool, some devices can use it to create a backup but not all can. The tool is designed to work with many different devices. Some are only compatible enough to boot the recovery session long enough to root, some are very compatible and can use all the features. The backup feature will work on some models but not on others.

Sent from my LGL84VL using Tapatalk

I have used the tool previously to make a backup and I'm almost sure I was able then to backup to an external SD card.

If anyone could help me with this it would be greatly appreciated.

Thank You,
 

Isrgish

Senior Member
Jan 5, 2018
103
15
Boot to recovery and choose factory reset to reset the device, then choose wipe cache partition(this might remove the "unexpected information") then wait for the update notification to pop up again, then try the update.

Sent from my LGL84VL using Tapatalk

I finally got my device baked up and tried your suggestion. But no work. I still get the same message.

Here is the exact message I get (this is while its in recovery mode and installing the update)
Code:
"/system/bin/app_process32" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)

Installation aborted

Maybe I need to replace one of these files? If yes where can I get a better copy.

Is anyone else having this problem?

Thank You,
 

Droidriven

Senior Member
Jan 27, 2014
15,603
11
5,419
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
I finally got my device baked up and tried your suggestion. But no work. I still get the same message.

Here is the exact message I get (this is while its in recovery mode and installing the update)
Code:
"/system/bin/app_process32" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)

Installation aborted

Maybe I need to replace one of these files? If yes where can I get a better copy.

Is anyone else having this problem?

Thank You,
Status 7 means that the file you are trying to flash is not compatible with your recovery or not compatible with your device.

Is the file you are trying to flash is a stock official update?

Are you trying to flash it using CWM/TWRP?

Is the update for your specific model?

If the answer to those questions is yes, that's your issue. You can't flash a stock update via custom recovery, flashing stock updates requires stock recovery and an unmodified system partition(meaning no root and no modified system files).

If this is what yours trying to do, you'll need stock recovery and you'll need to undo any modifications you have made to system and remove root.

Then, after the update is applied, then you can root the device again.

Sent from my LGL84VL using Tapatalk
 
  • Like
Reactions: Isrgish

Isrgish

Senior Member
Jan 5, 2018
103
15
Status 7 means that the file you are trying to flash is not compatible with your recovery or not compatible with your device.

Is the file you are trying to flash is a stock official update?

Are you trying to flash it using CWM/TWRP?

Is the update for your specific model?

If the answer to those questions is yes, that's your issue. You can't flash a stock update via custom recovery, flashing stock updates requires stock recovery and an unmodified system partition(meaning no root and no modified system files).

If this is what yours trying to do, you'll need stock recovery and you'll need to undo any modifications you have made to system and remove root.

Then, after the update is applied, then you can root the device again.

Sent from my LGL84VL using Tapatalk

How do I go about unrooting and returning my device to its original form to be able to install the update?

Thank You,
 

Droidriven

Senior Member
Jan 27, 2014
15,603
11
5,419
NC
Verizon Samsung Galaxy S III
HTC Thunderbolt
How do I go about unrooting and returning my device to its original form to be able to install the update?

Thank You,
If you have SuperSu, there is an option in the SuperSU in-app settings for removing root and uninstalling SuperSu.

If you have Magisk, there is a Magisk uninstaller zip in the Magisk thread that you flash via TWRP to remove root.

Or, if the update can be downloaded via the internet, you can download it and flash it via PC, flashing via PC will remove root during the flashing process, depending on what kind of update it is, the update would have to contain an update system.img, if it doesn't, it won't remove root during the flashing process, which could result in a soft-brick or bootloop.

Sent from my LGL84VL using Tapatalk
 
Last edited:

Isrgish

Senior Member
Jan 5, 2018
103
15
If you gave SuperSu, there is an option in the SuperSU in-app settings for removing root and uninstalling SuperSu.

If you have Magisk, there is a Magisk uninstaller zip in the Magisk thread that you flash via TWRP to remove root.

Sent from my LGL84VL using Tapatalk

I just want to make sure its safe to use this option from SuperSU.

I rooted my device with the instructions on this thread.

Thank You,
 

avaricesyn

Member
Dec 17, 2014
9
0
Thank you for this, appreciate the care and dedication especially that has gone into your script ^_^

It took me a few hours, but for anyone else who might have picked up this tablet or is just now getting around to rooting it (and like me have very little experience), the steps are as follows:

1. Download the files in the first post. On the SuperSu thread, SRs are betas. I used v.2.82 (not SR)
2. Install the Intel driver, reboot pc for good measure
3. run "patch.bat" in the Boot-Recovery-Patcher-Flasher folder, just go down the list and make sure you're not getting errors.
4. I had to run adb from the newest official build to get it to initially allow for fastboot flashing because there is a very short window in which you can hit the volume up button to allow permission, so I had to almost simultaneously run the command and press the up arrow when it came to that step
5. You can switch back over to the patch script for the rest of the steps
6. If you're using SuperSu v2.82 you're going to have to manually install it from the CWM boot because the script is set to look for 2.79 (make sure that you transfer it as a zip from your computer into the root directory of the device, which is the first menu that appears when you click on "Internal Storage")

Don't interrupt your tablet when it's on the black screen w/ the yellow text that says "Your device is not safe... blah, blah, blah, rebooting." Just let it do its thing.

There were multiple times where my tablet was factory reset during this process. Each time just skip as many of the steps as you can and go straight back into settings, enable developer mode, oem bootloader unlock, and adb usb debugging, and carry on with the patch on your PC where you left off.
 

zamiel2112

Member
Nov 25, 2017
35
1
49
Las Vegas, NV
I can't see the steps in the unlock tool since I can't get the tablet connected with adb. It was whatever I was supposed to do after unlocking the bootloader. I can turn the tablet off and on but can't get to recovery and it's stuck on Voyager screen.

Chris. Hello. Were you ever able to get past this bricked state of the tablet? I have the exact thing as you going on and looking for some help.
 

Danny33452

Member
Feb 2, 2020
16
1
Does this work with Android 8.1

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://forum.xda-developers.com/showthread.php?t=2588979
Download intel drivers == https://software.intel.com/en-us/protected-download/385047/494732
Download SuperSu.zip == https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120


Thanks:
@vampirefo for most of the needed parts to make this work. CWM, permissive su-policy, without that this would not be possible

@bluefirebird 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.




History of this root method started in this thread.
https://forum.xda-developers.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625

I was wondering if it worked on 8.1 because mine came out of the box like that
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    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://forum.xda-developers.com/showthread.php?t=2588979
    Download intel drivers == https://software.intel.com/en-us/protected-download/385047/494732
    Download SuperSu.zip == https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120


    Thanks:
    @vampirefo for most of the needed parts to make this work. CWM, permissive su-policy, without that this would not be possible

    @bluefirebird 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.




    History of this root method started in this thread.
    https://forum.xda-developers.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625
    2
    Many thanks, mrmazak. Anyone would know your heart's in the right place and your help is first-rate.

    Jake
    2
    I had a dream that it was an SD card holding me back. Sure enough, there was an SD card installed in the tablet which was preventing me from unlocking the bootloader. So as of now, it is unlocked and I will proceed with your directions and post an update shortly.
    2
    power down tablet and go into recovery mode by pressing power and up button. make sure to insert a blank micro card big enough for the backup. nothing on it . once in then select backup user and this can take up to 45 min so be patient. when done. take out card and replace orginal and select reboot to system and ur done. pics below hope they help

    You might be able to use this thread to make twrp for the mtk version.
    https://forum.xda-developers.com/showthread.php?t=2798257

    The thread is long and comments suggest it is still working method takes very little for it to work. There is good AIO script tool .

    Now bootloader is unlocked. I did not suggest before because it needs to be unlocked
    2
    Yeah, Installing it through the app results in a bootloop.

    I'm trying to get out of the bootloop.
    https://github.com/rovo89/Xposed/issues/77

    Sent from my Life_Max using Tapatalk