yashsingh1/xdaforums huggingface dataset:
[General Topics] avaricesyn:
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.
[General Topics] zamiel2112:
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.
[General Topics] chris5204:
No, sorry. I had to give up on it. It's gathering dust somewhere.
[General Topics] Danny33452:
Does this work with Android 8.1

I was wondering if it worked on 8.1 because mine came out of the box like that
[General Topics] mrmazak:
I can't say. Mine had Android 6 only.
[General Topics] Danny33452:
Could you downgrade

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
[General Topics] mrmazak:
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.
[General Topics] Danny33452:
would you know where to find such files
[General Topics] mrmazak:
What is the full model number and build number for your tablet?

Should be shown in he " about phone " menu in settings
[General Topics] Danny33452:
Sorry for not responding for so long but

Build Number: RCT6873W42BMF9E-ANDROID8.1-V12-V1.16.100-E16

Model Number: RCT6873W42BMF9E
[General Topics] 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.
[General Topics] 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!
[General Topics] jjboo26:
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!!!
[General Topics] 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.
[General Topics] WeAreGod:
Having trouble finding intel drivers for this tablet. Link in post just leads to intel website..
[General Topics] 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.
[General Topics] 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.
[General Topics] 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 :

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.
[General Topics] 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.

"
[General Topics] mrmazak:
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. \
[General Topics] WeAreGod:
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?
[General Topics] 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.
[General Topics] vampirefo:
Work out the booting into recovery combo before you attempt to root another one.
[General Topics] mrmazak:
Lol. Test. OK.

You make me laugh.

Seriously though don't test with all of them.

Just do the unlock. And reboot make sure that part works.

Just thought of it. I did not go from stock to the permissive boot. I had a different modified boot.img that only removed the encryption first then I did the permissive. That might be a needed step.

Before you flash any more try "fastboot boot permissive-boot.img"

To make sure it boots before committing to flashing it .
[General Topics] icaruspony:
10-4.

Mine are still in the Walmart return window, so I want to do this sooner rather than later.

The unlock part worked great... waited 30 seconds on warning, booted to a fresh Google set up, re-enabled USB debugging and OEM unlock.

The permissive boot img flash succeeded, as well as the two partition formats. Then the fastboot reboot killed it.

I will do a "fastboot boot" instead of "fastboot flash" next time. Which is permissive-boot.img? Is that the rca-boot_permissive-20170316-1706.img ?
[General Topics] mrmazak:
Yes that's the one. And so it would be "fastboot boot rca-boot_permissive-20170316-1706.img"

On the "boot" command you do not need to specify the partition it is for like you do on the flash command.
[General Topics] icaruspony:
Exactly... just like when doing a "one-time" boot of chainfire's systemless root on my Nexus.
[General Topics] Xsavi:
I have successfully rooted this tablet thanks to you and vampire! Thanks so much!

For some odd reason, for every device I buy, I can't go without root. :)

Okay, the next thing I'm gonna do is get the Xposed framework on this tablet. The FlashFire method won't work as the app crashes upon selecting a zip file to flash.

I tried the flashing it via the modified flash and CWM but I get the 255 error, it wouldn't flash.

Again, I can't thank you guys enough!
[General Topics] mrmazak:
There was an odd issue with the cwm and the way it mounts the device. And as you noticed from the directions , there is a needed adb remount before SuperSU would flash, maybe try that. But I am not sure if exposed will work or not.

Just for makeing a note in the op what was your build number.

And did you follow the order of steps "as is" or slightly different.

I ask because there have been problems.
[General Topics] Xsavi:
My build number is "RCT6873W42-ANDROID6.0-V19-V1.16.100-E07"

Yes I've followed your steps as is and I'm successfully rooted no problems.

To get Xposed on there, I followed the steps used to flash SuperSU and I got that error.
[General Topics] vampirefo:
As far as I know Xposed doesn't work on Intel device's, that aren't 100% Google compliant.

Unless that has changed, last time I talked to the Xposed developer he said it would never work, and he would never change his source to include any device not compliant with Google's​ source code.
[General Topics] Xsavi:
Yeah, Installing it through the app results in a bootloop.

I'm trying to get out of the bootloop.
[General Topics] vampirefo:
https://github.com/rovo89/Xposed/issues/77
[General Topics] Xsavi:
Thanks!

I had to sideload the uninstaller zip. I'm out of the bootloop now.

Sucks that Xposed doesn't work on this device, would've had a blast with that!

I'm gonna experiment with this tablet...
[General Topics] icaruspony:
Update:

New fresh tablet. RCT6873W42-ANDROID6.0-V19-V1.16.110-E05

OEM unlocked, USB debugging enabled. fastboot flashing unlock, it did automatic factory reset.

Not trusted 30 second countdown, boot up, re-enable USB debugging. Confirmed I am able to access recovery very easily.

Now, I did "fastboot boot rca-boot_permissive-20170316-1706.img". It booted successfully, and had message that decryption is unsuccessful (because of course userdata and cache weren't reformatted) and said to do a factory reset. I did not do a factory reset.

It looks like the boot img is bootable. I'm not sure why on the last tablet flashing that same boot img (which said it succeeded) caused no boot and no access to recovery. I am hesitant to re-do the same steps as the last one (fastboot flash) without knowing why the last one failed. Could it be because of the format of userdata and cache after flashing boot.img? Would it be better to flash the boot img and not format it and try to let the tablet do it through recovery?

I'm not sure if I am ready to re-try. I am hoping someone else can confirm that following the steps as outlined, exactly, has worked for them.
[General Topics] mrmazak:
Your version is ended with 110 the versions that confirmed so far are 50 and 100. Yours might doing extra check for encryption, and trying to to use factory recovery to format would possibly cause more problem. Because factory recovery also has the force-encrypt flag. The modified stock recovery does not.

So if your gonna try things. I would think that trying to flash both new images at same time .

But you would be first on 110,
[General Topics] icaruspony:
Update: Successfully rooted tablet #2. So you can add the "RCT6873W42-ANDROID6.0-V19-V1.16.110-E05" version to the list of confirmed working builds.

As for the first tablet... why it failed... bad USB transfer of the boot image? Perhaps it was a different build? No way to know, since I don't know what build it was and cannot boot it up. But I'll watch out for it on the next 48 tablets.

By the way... has anyone considered changing the kernel to bypass the 30 second warning message? Or to lessen the 30 seconds to 1 second?
[General Topics] KindleFireHD6:
What about the V1.17.80-W04?

Sad day. I bought mine on Black Friday and I haven't touched it since, following the original thread of these awesome guys working on rooting it. My build is:

RCT6873W42-ANDROID6.0-V31-V1.17.80-W04

Looks way too close to the build that bricks. Any suggestions?
[General Topics] mrmazak:
I don't want to make uneducated recommendations.

I don't know why the different build is giving trouble.

I would think that test booting the images instead of flashing "should" be safe.

Also booting the CWM recovery should be a safe test. If the cwm boots you should be able to "DD" the boot.img and then we could try to make the same modification to it that was done to this boot.img, used for the root.
[General Topics] KindleFireHD6:
Thank you for the quick response. I'm rather new to the rooting world. I did root my Kindle Fire HD 6 -- with the step-by-step guide provided on this site. But I'm not real familiar with how to perform the tasks you recommended. I understand it's a time vs value thing writing out instructions in layman terms, so I totally understand not having the time to hold my hand through the process. However, if anyone wishes to do so, I'm more than willing to participate.

Thank you again!
[General Topics] mrmazak:
I just modified the directions to include a test fastboot boot line. (2-a)

This is same advise I gave to icaruspony and for him it verified boot.img did boot and did not seem to have any side effect.

If that step fails I can write up steps needed to try and pull your boot.img.
[General Topics] KindleFireHD6:
Thank you so much. I won't be able to tackle this until the weekend at the earliest, but I will definitely give it a shot and get back with you.
[General Topics] Plasmastar:
I don't know if you still need my build number or not. But here it is: RCT6873W42-ANDROID6.0-V19-V1.16.110-E05

And yes, I successfully rooted it with your instructions.
[General Topics] mrmazak:
Yes I do, and thank you.
[General Topics] rpk3:
Your awesomeness!
[General Topics] KindleFireHD6:
Stupid ADB. :P My kindle still connects, but ADB isn't seeing this tablet. I'm using 1.0.32. I posted on the "[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3" thread about the best way to upgrade. As soon as I get ADB working, I'll try this out.

Thank you again.
[General Topics] mrmazak:
Please remember "DO NOT" FLASH ANY OF THE IMAGES on "your" tablet. You have the v31 build. It made 1 maybe 2 bricks already.

The test here is just to try and boot first the boot.img.

Then try to boot the cwm-recovery.img

Will need to copy the files from your tablet to try and make a version that "might" work on that build.

This works with an sd card. the boot and recovery are the ones to be modified to get root. The rest are for a complete backup.

Need to be booted into cwm recovery for this to work, because need root access.

#verify adb is root
adb shell whoami
#if response is "root" then can continue
adb shell mount external_sd
adb shell mkdir /external_sd/RCA
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID001 of=/external_sd/RCA/mmcblk0p7.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID010 of=/external_sd/RCA/mmcblk0p4.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID013 of=/external_sd/RCA/mmcblk0p11.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID022 of=/external_sd/RCA/mmcblk0p1.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID023 of=/external_sd/RCA/mmcblk0p2.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID024 of=/external_sd/RCA/mmcblk0p3.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID033 of=/external_sd/RCA/mmcblk0p14.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID034 of=/external_sd/RCA/mmcblk0p13.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 of=/external_sd/RCA/system.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 of=/external_sd/RCA/data.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070 of=/external_sd/RCA/cache.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 of=/external_sd/RCA/boot.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID074 of=/external_sd/RCA/mmcblk0p18.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID076 of=/external_sd/RCA/mmcblk0p5.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID115 of=/external_sd/RCA/mmcblk0p6.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID118 of=/external_sd/RCA/mmcblk0p8.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 of=/external_sd/RCA/recovery.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122 of=/external_sd/RCA/mmcblk0p12.img
[General Topics] KindleFireHD6:
Thank you for the clarification. I appreciate the help and look forward to being able to contribute information that could help others.
[General Topics] mrmazak:
Have you had a chance to do any test with this yet?
[General Topics] KindleFireHD6:
No. I still don't have ADB and I haven't been able to get help on the ADB forum with that problem.
[General Topics] mrmazak:
What's wrong with your adb. ?

I useed the 15 second installer and it works
[General Topics] KindleFireHD6:
I'm running version 1.0.32. My kindle connects just fine, but my RCA tablet doesn't show up when I list adb devices. I was going to upgrade to the latest, but I wanted to make sure I did the upgrade right. Do I uninstall 1.0.32 first? I figure updating my ADB is the simplest solution to try since it's not connecting. The computer sees the device and it charges over the USB cable.
[General Topics] mrmazak:
I know if it is done, this might be a simple question, but. Is adb debugging enabled in developer options?
[General Topics] KindleFireHD6:
Yes. It is. No such thing as a dumb question. My fault for not covering that base in my post.
[General Topics] spank_williams:
successful root

Successful root right out of the box. I followed the instructions but did not reboot fastboot every time. I just checked to make sure the permissive bootloader loaded then I flashed all three images via fastboot then booted into the cwm recovery without flashing it. Once there I made a backup then tried to push the supersu zip to the location given in the instructions but couldn't. I ended up pushing it to /sdcard/ and then I was able to find it and install it no problem. Other than that everything went great. Thanks for this root.
[General Topics] mrmazak:
Good. Can you please let me know your build version, so it can be added to the confirmed list.
[General Topics] spank_williams:
the build number is RCT6873W42-ANDROID6.0-V19-V1.16.50-E04
[General Topics] thesloth304:
6.0-v31-v1.17.80-w04

I was able to unlock the bootloader. I attempted to boot the boot img. but it just hung on the voyager logo. restarted it and it went immediately to the android logo and said erasing. After that, it must have restored itself. took me back to initial setup. Let me know what else I can do to help with getting a working root on this build. Could I try to boot cwm and pull a copy of the boot img?
[General Topics] mrmazak:
The erasing screen, did that come after the unlock part too? It should have. If you tried to boot the permissise-boot after the unlock without doing a reboot first, that

might

have been the reason for hanging.

If you don't mind attempting , go ahead and try the cwm boot, and pull the image. Remember the /data portion of tablet will not be able to be mounted because it is still encrypted, so will need external sd card to save to
[General Topics] jakfish:
I have a post-rooting question: does rooting the Voyager Pro take away the ability to download and watch Netflix video offline?

I've read, anecdotally, that rooting does remove this feature. You can stream, but not download.

Can anybody confirm this?

Jake
[General Topics] mrmazak:
I don't have Netflix but I did search Netflix root problem on Google. There have been many issues with Netflix and rooted phones (dates of results were from 2011-2014), so I assume you may be correct. But there is usually a fix or hack to get around it. Problem I see though is some of the fixes use exposed and that will not work on this tablet.
[General Topics] vampirefo:
Interested I have never heard of this, of course I decided to test and see for myself, I am typing on a tablet while my rooted Blu Life Max is downloading a movie called The Punisher.

Ok finished downloading now watching, so I am going to call BS on this.

So the real question is can your tablet right now unrooted download from Netflix? Probably not, if it can root won't stop it.
[General Topics] jakfish:
Wonderful, thanks for checking that out.

My unrooted Marshmallow RCA Voyager Pro (MTK, not Intel) downloads and runs Netflix video offline without problem.

But I have not found root for the RCT6873W42M, though I avidly follow this thread and admire all the hard work.

Jake
[General Topics] vampirefo:
MTK, yes Netflix, but this tablet is Intel, I doubt an Intel tablet can download, lacks HD which is required to download from Netflix.

My MTK phones Blu Life Max is rooted running custom ROM downloads from Netflix no problem.

My Intel's don't.
[General Topics] jakfish:
Interesting. I hadn't realized that the Voyagers had different screen capability as well as processors. I wonder why RCA would have so many hardware variations on same device.

Jake
[General Topics] ssand1984xx:
Doesnt anyone know about unlocking boot and rootnfor the mtk marshmallow version??
[General Topics] ssand1984xx:
funny enough i finally cracked it but for the non intel version....i will update info and screenshots shortly
[General Topics] jakfish:
Since I own a non-Intel version, I would be very interested to see how you did it.

Many thanks,

Jake
[General Topics] vampirefo:
I would really be surprised if it's not.

fastboot oem unlock

That has been common for MTK for years, perhaps RCA changed it.
[General Topics] jakfish:
That would make sense--I think I read the same command in another thread. The difficulty is the actual rooting; I've poked around quite a bit and haven't yet come across a user that has successfully rooted the RCT6873W42M.
[General Topics] vampirefo:
That would require a custom recovery, the root method would be same as this one.

A custom recovery, custom boot.img and SuperSU.
[General Topics] jakfish:
Addressing the Netflix download issue, I too can confirm that it's a no-go with Intel processors. I have an x-86 Marshmallow port for my Intel Asus Transformer T100TA and the Netflix app offers no download capability, despite the HD screen of T100TA.