[Guide] RCA Voyager RCT6873W42 Unlock Boot loader and root

[mrmazak]

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

I can't say. Mine had Android 6 only.

 

[Danny33452]

Could you downgrade

I can't say. Mine had Android 6 only.

Mine Has a unlocked bootloader so theoretically you could downgrade to a stock 6.0 rom

---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------

I cant boot Cwm It just gives me this error
Sending 'boot.img' (12604 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed

 

[mrmazak]

Mine Has a unlocked bootloader so theoretically you could downgrade to a stock 6.0 rom

---------- Post added at 02:12 AM ---------- Previous post was at 02:01 AM ----------

I cant boot Cwm It just gives me this error
Sending 'boot.img' (12604 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed

You cannot use the same files from this method. It is completely different devices. And os version. You will need to get copy. Of the boot.img from your version device.

Don't think downgrade is possible either.

 

[Danny33452]

You cannot use the same files from this method. It is completely different devices. And os version. You will need to get copy. Of the boot.img from your version device.

Don't think downgrade is possible either.

would you know where to find such files

 

[mrmazak]

would you know where to find such files

What is the full model number and build number for your tablet?

Should be shown in he " about phone " menu in settings

 

[Danny33452]

Sorry for not responding for so long but
Build Number: RCT6873W42BMF9E-ANDROID8.1-V12-V1.16.100-E16
Model Number: RCT6873W42BMF9E

 

[stusie]

What would it take to get this to work with the MTK chipset? I have a full image of the system ROM dumped from my device (Build RCT6873W42BMF9A-ANDROID8.1-V09-V1.25.101-A04), and can extract boot.img or anything else you might need from the stock firmware like that.

 

[MrsPeen]

I'm looking for help with rooting my RCA Voyager as well. Build number is RCT6873W42BMF8-ANDROID8.1-V15-V1.20.0-A02. I'm new to this as well. I was able to get my LG tablet rooted successfully but I'm lost with this one. Any help would be great appreciated!

 

[jjboo26]

Are you using this with correct drivers?
And with working voyager tablet, with an Intel soc. This does not work with an m version tablet(mtk soc)

I never had problems with volume key not recognized

Hello there can anyone help me bypass the FRP on this model RCT6703W12H1 Rca Atlas Pro 10,it is such a pain in the butt!!!

 

[xxMoon]

I discovered an unbrick solution for v23 Intel devices.

Unbrick Package: https://drive.google.com/file/d/1LFQqnJeRqpbK___HnKMvMPQJvEWPDIDz/view?usp=sharing

Prerequisites:
Win7 32bit (Wont work on x64)
A brain

1. Unpack archive to desktop
2. Install Intel Android Drivers
3. Open cmd as admin, enter "bcdedit /set testsigning on" and "bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS"
4. Restart PC
5. Open FlashTool_E2.exe as admin
6. Select file->usb map wizard
7. For type, select custom. for string Vid_8087&Pid_07f6 and the press next
8. With your device powered off, plug it into the pc. It should detect it and say something, just click done.
9. Power your device back off and unplug it from the pc.
10. Next to the add file box click the ... button and select boot.fls and system.fls from the Image-s3grt6w folder.
11. Click next
12. Plug in tablet to pc, it should automatically flash and reboot your device.
13. Profit

Now you can get back into fastboot.

 

[WeAreGod]

Having trouble finding intel drivers for this tablet. Link in post just leads to intel website..

 

[WeAreGod]

Found the drivers. Now when I run the Patch Tool and do the first step (Unlock Bootloader), the Tablet reboots to a black screen and stays there until I manually press the Hard Reset button.

 

[WeAreGod]

When I try the first option to unlock for intel.. Device reboots into fastboot black screen. Unknown device appears, I manually updated driver to CWM ADB Composite Interface. Still Black screen, then patch program says to press volume up. I press volume up while black screen. No reply, press any key. So then I assume it's a menu and I have to select using the power button to start unlock. Well this whole thing starts.

Found ADB

Waiting for 0 seconds, press a key to continue ...
Found FASTBOOT

---------- C:\USERS\WEAREGOD\DESKTOP\ANDROID\VOYAGER\BOOT-RECOVERY-PATCHER-FLASHER\\WORKING\GETVAR.TXT
Not Unlocked

---------- C:\USERS\WEAREGOD\DESKTOP\ANDROID\VOYAGER\BOOT-RECOVERY-PATCHER-FLASHER\\WORKING\UNLOCKABILITY.TXT
(bootloader) The device can be unlocked.
unlockable
Press any key to continue . . .
[*] ON YOUR PHONE YOU WILL SEE
[*] PRESS THE VOLUME UP/DOWN BUTTONS TO SELECT YES OR NO
[*] JUST PRESS VOLUME UP TO START THE UNLOCK PROCESS.
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Press any key to continue . . .
Press any key to continue . . .
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 4
(bootloader) EV_POWER received
FAILED (remote: 'couldn't change state!')
fastboot: error: Command failed

Waiting for 0 seconds, press a key to continue ...
(bootloader) userdata has-slot: no
(bootloader) userdata partition type: ext4
(bootloader) userdata partition size: 0x00000002a9b00000
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 2792192 4k blocks and 699008 inodes
Filesystem UUID: c5ed5ece-098c-11ec-8e52-53ce1be0454a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (124 KB) (bootloader) Ready to receive: 0x0001f16c size of data
OKAY [ 0.017s]
Writing 'userdata' (bootloader) Device is locked, cannot perform flash in fastboot
(bootloader) Please use the below command to unlock first:
(bootloader) > fastboot flashing unlock
FAILED (remote: '')
fastboot: error: Command failed

Waiting for 0 seconds, press a key to continue ...
(bootloader) cache has-slot: no
(bootloader) cache partition type: ext4
(bootloader) cache partition size: 0x000000001a900000
mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 108800 4k blocks and 108800 inodes
Filesystem UUID: c8e50bf4-098c-11ec-8990-357809afe795
Superblock backups stored on blocks:
32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'cache' (68 KB) (bootloader) Ready to receive: 0x000110ac size of data
OKAY [ 0.016s]
Writing 'cache' (bootloader) Device is locked, cannot perform flash in fastboot
(bootloader) Please use the below command to unlock first:
(bootloader) > fastboot flashing unlock
FAILED (remote: '')
fastboot: error: Command failed

Waiting for 0 seconds, press a key to continue ...
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
[*] MUST REMOVE USB CABLE AND LET COUNTDOWN TIMER ON SCREEN COTINUE
[*] IF DEVICE POWERS OFF JUST HOLD POWER BUTTON TO TURN BACK ON
[*] skip steps in setup then re-enable developer options and abd debugging
[*] press any button to continue
Press any key to continue . . .

 

[WeAreGod]

Continuation of last reply ...
Immediately after sending flashing unlock command, I held down + button and I saw the menu visibly flash on the tablet screen but it was too fast to read... Then PowerShell returned the following :

PS C:\Users\WeAreGod\Desktop\Android\Voyager\Boot-Recovery-Patcher-Flasher> ./fastboot flashing unlock
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 2
(bootloader) EV_UP received
(bootloader) got key event 4
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...

(bootloader) Ram clear required, this can take a while...

OKAY [ 48.044s]
Finished. Total time: 48.045s

Normally it would get stuck and return error 'couldn't change state' . So I discovered that one needs to hold Volume up + button immediately after sending fastboot flashing unlock command... Now onto the next part.

 

[WeAreGod]

Somewhat related question... I'm attempting to install custom ROM zips (Lineage OS 13 & omni9) I've tried installing both zip files in CWM using external_sd and also adb sideload...

"Installing update...
E: Error in /external_sd/lineage-13.zip
(status 255)"

Also during adb sideload:

"restarting adbd...
status 0
Finding update package
Opening update package
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
"

 

[mrmazak]

Somewhat related question... I'm attempting to install custom ROM zips (Lineage OS 13 & omni9) I've tried installing both zip files in CWM using external_sd and also adb sideload...

"Installing update...
E: Error in /external_sd/lineage-13.zip
(status 255)"

Also during adb sideload:

"restarting adbd...
status 0
Finding update package
Opening update package
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
"

well this is an uncommon device with no released builds of lieage nor Omni, so whatever files you are tring to flash install would likely not work. so its a good thing teh install is failing. sorry to say . but the best you can hope for on these intell tablets is simply to have root access. \

 

[WeAreGod]

well this is an uncommon device with no released builds of lieage nor Omni, so whatever files you are tring to flash install would likely not work. so its a good thing teh install is failing. sorry to say . but the best you can hope for on these intell tablets is simply to have root access. \

How can I create a custom ROM that will work on it? (or modify a stable build of Lineage OS so that it will work on here)

I would like to modify the stock ROM so that everything is in dark mode.

I assume that would involve just modifying the color settings of the UI.

Does anyone know of any good guides on how to do such a thing?

 

[terminal.insight]

If anyone has a copy of the unbrick package from a few posts up it would help me out a lot if they could send it my way. Thanks <3.