yashsingh1/xdaforums huggingface dataset:
[General Topics] icaruspony:
I was rooting my tablet from "out of the box" according to the directions, and everything was fine up until the same point. After flashing the modified boot img, formatting userdata and cache, and issuing the fastboot reboot command, now all I get is a backlit screen. Volume down does turn the screen black for a moment then lights back up. The pc sees it as a flash drive, but adb devices doesn't see it at all (not even as an unauthorized device).

My tablet is the correct model. RCT6873W42

I haven't figured out how to get into the recovery. Holding volume up + power, etc doesn't do anything.

---------- Post added at 09:33 AM ---------- Previous post was at 09:17 AM ----------

I'm having the identical problem on the identical step you did, and I have the correct model/version.
[General Topics] mrmazak:
All I can think to do at this point is to add an md5 to verify the files downloaded are the ones intended to be used.
[General Topics] vampirefo:
It would seem before people try to root their device they should first know and be able to get into recovery before they attempt to root.

If you can't get into recovery via hardware keys, there is no point to continue trying to root your device until you figure that part out.

I don't have the exact tablet in this thread, Mine is close enough though.

to get into my recovery.

press and hold volume down and power until splash screen pops up, I get a splash screen just before count down screen, release and when 30 second count down finishes tablet boots into recovery.
[General Topics] icaruspony:
I have 49 more of these tablets, still in their boxes, to test with.
[General Topics] mrmazak:
adb supposed to connect while tablet is off.

Does it?
[General Topics] chris5204:
It sounds like it does but when I try adb reboot fastboot in command prompt it just says device not found.
[General Topics] mrmazak:
It could take a minute or so before it get recognized after connecting . Try plugging it in then wait 3 minutes then try "adb devices" see if it sees it

Also did you try volume button in both directions during power on to get to recovery? From powered off on mine it takes pushing the volume button that is closer to the power button(down) and power to get to recovery.
[General Topics] chris5204:
I did try both volume buttons. The one closer to the power button just turns the tablet off after the 30 second countdown. I will try your other suggestion when I get home. Thanks.
[General Topics] chris5204:
I tried this:

..and it worked. I went back and did this: type "fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img" and got it into recovery. I restored and the tablet booted up normally! Thank you. It isn't rooted but maybe I should just leave it alone now. Thanks again.
[General Topics] mrmazak:
Ok great.

You said you have v31.

That version I do not have on my tablet. So I could not verify 100%.

Some things I need to know.

You did flash the v31 boot right.?

Ok if not , that could be the reason for suerSU not working.

What are the output from these 2 commands.

"adb shell whoami"

And

"adb shell getenforce"

should be

C:\Users\Mr>adb shell whoami
root

C:\Users\Mr>adb shell getenforce
Permissive
[General Topics] chris5204:
Unfortunately, I'll have to get back to you on that. I screwed something up.
[General Topics] Habbit14:
Hey so like I have the Alco-RCT6873W42 and I have a different version than the ones listed. I have "RCT6873W42-ANDROID6.0-V30-V1.17.50-W00" also I am new to this whole forum and rooting thing so please excuse my lack of knowledge. Thanks <3

Also I unlocked the boot loader I don't know if that's important info but yea I did that thing.
[General Topics] mrmazak:
Well what we have found out about the different versions of this tablet is , each one needs different files to work.

There is chance during testing that you might end up bricking your tablet.

As long as you understand that we can try to help get root on your -v30- tablet.

Download both sets of files. (V19 and V31)

Keep them in separate folders. Don't want to get them mixed up.

Follow the posted directions up to step "B: 2-a:"

With both the v19 and V31. See if either one works.

If not will need to pull your stock boot.img to make modifications to that .

To pull your boot.img.

Skip forward in the directions to "D: " do 1 and 2.

I don't expect the screen to show the recovery screen but adb supposed to work, and it will have root access.

If recovery boots it may not be able to access /data so will need external sdcard to copy boot.img to.

if recovery boots or even if it just gives black screen try to connect with adb.

if connected pull the boot.img

adb shell mount external_sd
adb shell mkdir /external_sd/RCA
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 of=/external_sd/RCA/mmcblk0p9-boot.img
[General Topics] chris5204:
I should have left it alone mrmazak. I tried to root it using the tool. I skipped step 1 since I knew the bootloader was unlocked. When I did step 2 it bricked the tablet again. The problem is that I can't fix it this time like last time. No matter how long I have the tablet plugged in to the computer, whenever I try a commend in adb is says device not found.
[General Topics] mrmazak:
Step two is "test-boot", so if if did not boot then should be able to long press power to force power off and should be unchanged when turn back on. Unless you mean another step and not #2.
[General Topics] chris5204:
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.
[General Topics] niebaum:
mrmazak,

My tablet is showing this build: RCT6873W42-ANDROID6.0-V18-V1.16.20-E03. Since this particular build wasn't listed as being tested with your root method, I decided it would be safer to just do all the same steps you did to root yours, but with my tablet's original images.

Starting out, I just wanted to get a factory recovery image flashed that had ADB enabled. I made these changes to my build's recovery image, attempted booting (and flashing it), but it would not boot after making these changes. Any idea why? Or is there a way to see logs of some sort to try to get a clue? I'm new to Android hacking, but not that new at Linux-stuff. Here's the changes I made to try to get an ADB recovery:

diff -r factory/recovery/ramdisk/default.prop mrmazak/no-force-encrypt-recovery/ramdisk/default.prop
9c9
< ro.adb.secure=1
---
> ro.adb.secure=0
14c14
< ro.secure=1
---
> ro.secure=0
16c16
< ro.debuggable=0
---
> ro.debuggable=1
31c31
< persist.sys.usb.config=none
---
> #persist.sys.usb.config=none
95c95
< sys.rkadb.root=0
---
> sys.rkadb.root=1
169c169
< ro.adb.secure=1
---
> ro.adb.secure=0
198a199,202
>
> persist.service.adb.enable=1
> persist.service.debuggable=1
> persist.sys.usb.config=mtp,adb
\ No newline at end of file

I put my factory recovery image up on GitHub, but since my account is new, XDA won't let me link it. On GitHub, check out the repository rct6873w42/img.git

What am I missing? Thank you again for all you've done for this tablet!
[General Topics] mrmazak:
Off hand that looks almost same asthe way I did it.

But I also added My adb key to recovery ramdisk data/misc/adb . This way if factory reset is done on tablet I can still get autherized adb in stock recovery. (trick is need to get to adb sideload first to make recovery read the key. sideload will fail signature but adb autherized will remain if using your key)

my git hub on this , is a little bit of a mess. But youcan check out the file history to see thechanges I made.

https://github.com/mrmazakblu/RCA_RCT6873W42_bootloader-unlock_CWM_recovery_tethered-root

Almost forgot. Fastboot boot did fail to load my modified stock recovery. It also failed to load the unmodified recovery. So this step is the most nerve racking one, because testing needs actual flashing of the recovery. But as long as system remain bootable you should be ok.
[General Topics] mrmazak:
I looked through the changes and did not notice trouble. Maybe a problem with the repacked image. Try this test. Boot/ flash the stock image make sure that still works, then unpack the stock recovery, make no changes, just repack and flash it again.

Assume you are only working on the stock recovery for now. Because the "boot" changes are not on you git.

*/ramdisk/sbin/adbd gets swapped*

*/ramdisk/sepolicy gets changed*
[General Topics] Habbit14:
Hey so I unlocked the boot loader forever ago and now whenever I type "adb reboot fastboot" the screen goes blank and it keeps connecting and disconnecting, and it doesn't show up whenever I type "fastboot devices". I am just gonna see if I can go and pick up a micro sd card and pull the stock image. What size would you recommend?
[General Topics] mrmazak:
1. The blank screen is normal.

2. The connecting disconnecting, sounds like drivers are not installed for intel Android bootloader

3. Card does not need to be big. 4gb might be smallest you can get. To be a good useable size card for later use I would get at least 16 gb
[General Topics] Habbit14:
Ok thanks and I did install all the drivers and adb from the instructions but idk.
[General Topics] mrmazak:
Re-read step 5 in the directions. Make sure you did that.
[General Topics] buddhaja:
Ok so essentially I did everything I wasn't suppose to with this tablet lol. Sorta. Long story short Im in a bootloop. It boots to the Voyager logo and that's it. I flashed the cwm recovery which doesn't boot and a custom boot I was working on. So i am searching for other ways to restore my system. It looks as though the Intel flash utility is gonna be the best way. The utility recognizes the tab as an Intel USB Flash Loader Utility. Basically I have the stock boot, recovery and system and need a flash.xml to start the flash process. Any ideas?
[General Topics] mrmazak:
I wasn't able to get anything I tried in intel flash to work.

You might get lucky and even thought cwm recovery will not open ,it might have adb working?

Or

If you had adb enabled on the tablet, and didn't do a reset. Adb should work when in the off condition.

Of course that will depend on what changes you did to the boot.img.
[General Topics] JUNNO-S:
Rct6873w42-android6.0-v1.17.50-w00

I have this build which should use or can't root?
[General Topics] mrmazak:
Do not know. Your build number is in different format from the others.

RCT6873W42-ANDROID6.0-V19-V1.16.50-E04

RCT6873w42-ANDROID6.0-V31-V1.17.70-W01

yours is missing the section in red. Thats the determining portion of the build number

You might be able to test boot the CWM recovery like described in the directions. Without confirmed numbers, it is all just trial and error.
[General Topics] JUNNO-S:
I'll try, danm I try to root whith kingroot, kingroot pc, kingoroot pc, and kingoroot whith bootloader unlock enable in developer tools and just got kinda of lag even after factory reset, it even look less clear and the display look less quality or am I hallucinating? danmit.. too sad

if I boot the recovery will not change anything of system or could brick?
[General Topics] mrmazak:
correct. If you change anything while in CWM during this test, before having a modified boot.img installed, you could make a brick, so be cautious

your build number most closely matches the V31 format, so when/if you do try to boot CWM. Use the V31 version.
[General Topics] JUNNO-S:
A got a problem, when type "adb reboot fastboot" don't appears blank screen just black and recognize it like "Android ADB Interface"

Can you help me to wipe dalvik cache to delete the lag?

A last question, can used a different zip to root or just that u posted? I bought this tablet yesterday I'm afraid to brick it
[General Topics] mrmazak:
I do not know of any other zips for this device. And because the different build version, what I have posted will not work as is. Will need to be modified. And as for the lag I cannot help, the device is just slow
[General Topics] Kaiwaters:
[MENTION=5312578]mrmazak[/MENTION]

wait so i cant root my RCT6873W42-ANDROID6.0-V31-V1.17.80-W04 device?
[General Topics] mrmazak:
Should be able to ,yes.

The op has that version listed as one of the first to get bricked , when trying to use the v19 build files. Bit it should be ok on the v31 build files. Just make sure to carefully follow the directions and do "fastboot boot" on the modified boot.img and make sure it starts up the device before flashing it. If it boots ok and is in selinux permissive mode , then should be safe to flash it.

If you have questions , reread the directions beginning to end again. And then post questions if needed.
[General Topics] Kaiwaters:
crap i think i messed up on step 2b i used the recovery one instead of the the test. I didnt just brick this thing did i?
[General Topics] mrmazak:
So you flashed recovery to the boot partition?

If you can still boot to recovery then you may be ok. Boot to

But if not, then yes it will be bricked.
[General Topics] Kaiwaters:
it doesnt go past the bootloader is unlocked and the count down starts i think the buttons are disabled also guessing without those i cant go into recovery
[General Topics] mrmazak:
I have no advice for you. That sounds terminal.

Only maybe, turn off tablet and plug in USB cable to PC. If it turns back on turn it off. Wait about 2 minutes, then try adb commands. Example "adb devices" if listed as connected try "adb reboot fastboot" and flash the correct boot.img.
[General Topics] JPolaske:
Hey quick question. Is there a way to root this tablet when it is Google Account locked? I can't get into the settings page to the Developer Options, so is there a way to do it without being able to access that menu?
[General Topics] mrmazak:
No, if you do not have developer option enabled and oem unlock turned on as well as USB debugging turned on.

There will be no way to do this.

Unless factory reset removes account lock( it is not supposed to be able to)
[General Topics] tsgeog:
Stuck on Voyager boot screen

If Stuck on RCA Voyager boot screen i have figured out how to get back to recovery menu at least with my device. with tablet powered off press volume + and power till you get the RCA logo screen and its fast as soon as you see this let go of volume keep pressing power and it goes to count down screen warning keep pressing power until its done and wait the next screen will be recovery menu.
[General Topics] kj3:
my rca voyager 3 rct6973w43 is stuck on the voyager 3 logo every time i cut it on what do i do
[General Topics] mrmazak:
Gonna need more information.

Are you rooted.?

What was last thing done before this happened?
[General Topics] straysoul.lynch:
Looking to to root my RCT6873W42 Build 23 with Android 6.0.1 . Anyone with information on this particular build?
[General Topics] mrmazak:
You will have to try my manual method to try pull your stock recovery and boot images, in order to make working recovery for your build number.

read and re-read the directions untill you understand them clearly.

Too many times I have worked with people who skipped steps and did what they assumed was right , only to end up makeing a brick out of there device.

DO NOT FLASH ANYTHING

to your device during the manual process to pull recovery and boot images.
[General Topics] Josh8888:
Can someone test this on the rtc6873w42m v37-v2.15.50 Android 6.0

---------- Post added at 07:58 PM ---------- Previous post was at 07:38 PM ----------

Can someone test this on the rct 6783w42m Android 6.0 v37-v2.15.50
[General Topics] mrmazak:
There is very limited number of people with this device, so asking someone else to test before you try yourself will be a long waiting .

And I may be mistaken but I believe the "m" in your build number means that the device is "mediatec" chip not an Intel chip , which this process is for. Sorry.
[General Topics] Gnosis360:
Version Question

First thanks you obviously did alot of research, which means you spent some time on it....with that said I do not mind doing the leg work myself if you could maybe point me in right direction. I have a RCA Voyager 3 RCT697Voyager3-V27-V1.16.130-DS-E08 where would be the best place for me to find compatiblity info. Any information would be great.....Oh and I was in recovery mode and had a few linux.zip files on my sd so I tried to 'update from sd card' and....yes I know but I learned....it will still go to recovery but it is stuck in bootload whentry to reboot. Is there a solution? :confused:
[General Topics] mrmazak:
I have pointed few others with the Voyager 3 to this thread here. I suspect that the Voyager 3 with Intel chip should be able to semi-boot the same recovery used here.

At the end of the Manuel directions that I have linked tell steps to unlock bootloader and fastboot boot cmw-recovery.img

Others have failed to install the windows drivers for bootloader mode.

That covers your first question. As for the next question I am confusion as to your situation.

"Update from sdcard" should have failed signature verification, so would have made no changes.

Then not knowing what was on the linux zips , can't say if there is a way to fix tour bootloop

Now if you had adb enabled and authorized inside the stock rom you may be able to get adb shell to connect with tablet turned off.(turn off tablet ,and wait 1 - 1 1/2 minutes, )

Some more threads on rca tablets.

https://xdaforums.com/tags.php?tag=rca
[General Topics] Christopher12301:
Honestly im really new to all this and i had rooted my device. i had backups saved with the drivers and everything though. unfortunately when i go into the system recovery menu in the restore user data section all of the slots are empty. when i go into reboot to bootloader it wont allow me to access the command line at all. ive tried applying the update from an exterior sd card also because i think i named the two files the same in the same are or thought they were one and the same so when i wipe factory reset my device i think it wiped all my internal memory stuff. like i said new to all this just like rooting phones and playing with the system core files on all this shiz. any help would be wonderful. im to the point of almost taking it to and Rca place to get it fixed or something. the only thing i havent tried is applying update from ADB like you said but my bro has my laptop right now and i would have to do it from my other RCA vikingpro or my phone. if you could walk me through that it would be awesome
[General Topics] mrmazak:
From system recovery, the reboot to bootloader does not work. Because this device has the firmware modified to need a "reboot fastboot" command.

And you said you did factory reset, so yes all your internal memory gets wiped.

If you had device rooted by my method , then you should be able to get an adb shell from factory recovery mode.

But I can't tell from your post what your problem or question is
[General Topics] Dj27:
Hi I have a rca Voyager 3 how do I root it safely
[General Topics] mrmazak:
no body has confirmed any method that works.
[General Topics] TheNH813:
RCT6873W42, safe to flash permissive boot.img?

So, I'm wondering if it's safe to go ahead and flash the permissive boot image on my device. I'v tried using fastboot boot <filename> it it boots up fine until it reaches the lock pattern. It states you need to do a factory reset because encryption couldn't be enabled. Does this mean that flashing the boot image will brick the device, or just that I need for format afterwards? Is this normal, or not? The CWM recovery also boots just fine, but touch dosen't work in it. I'v rooted android devices with software before but never using a boot image and directly flashing SuperSU, so I have little experience here. I have successfully unlocked the bootlader (obviously because I can boot the files and use fastboot), and am just wondering if it's okay to proceed or not. My firmware is also V26, not V19 or V31.
[General Topics] TheNH813:
Success???

Well, I couldn't wait and went ahead and flashed it. Since it booted fine up to the format device warning as previously mentioned, I decided to take a shot. It works fine afterwards, except the touch screen. I plugged in a mouse and keyboard, then installed TeamViewer for remote access to solve that issue (can't use ADB and USB OTG at the same time obviously). I turned ADB back on and I guess I'm ready to boot the custom recovery image and flash SuperSU, but first I want touch working again, and advice incase I shouldn't proceed immediately. I will wait for the answer time time.

What I'v tried:

Booting (not flashing, of course), the v19 boot.img. It starts up fine, no hangs, bootloops or crashes, but the screen is very low resolution, letterboxed vertically in the horizontal resolution, has funny green waves running through it and is black and white color, the WiFi dosen't work, the sound dosen't work, the bluetooth dosen't work, ADB is dead but surprisingly, the touch screen works just fine. In other words, v19 file is a horrible idea. It appears I have a model just inbetween the hardware revisions with very minor changes, and it's very close to the v31 version.

Any suggestions on how to patch the touch drivers from the v19 boot.img into the v31 boot.img?

I'v run a diff on the two extracted .img files and it appears pretty much everything is the same except the zImage (actual kernel).

Should I try to convince RCA to provide kernel sources and drivers, and compile a kernel zImage to put in the boot.img file myself?
[General Topics] mrmazak:
Hello.

You are in a bad situation, at the moment.

Rca has not released sources, we have been asking for over a year, others have been asking longer.

Hope you saved your boot.img before flashing the new one.

That is the reason for all the warnings on the directions. Warnings like use only on **.** Version.

The kernels (drivers) are different, because of different touchscreen hardware.

You might be able to pull your stock recovery image and pull the kernel from it to use in the boot.img.

As long as you did not flash the modified version yet.

Let me know if you need help with that

Basic layout of steps I think will get you back working.

1. adb reboot fastboot

2. fastboot boot rca-recovery-cwm-ramdisk.img

3. wait for loading to finish

4. Must have external micro sd for next step

5. adb shell mount external_sd

6. adb shell mkdir /external_sd/RCA

7. adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 of=/external_sd/RCA/mmcblk0p10-recovery.img

8. adb pull /external_sd/RCA/mmcblk0p10-recovery.img \Desktop\RCA-recovery.img

Use an image unpack "tool" to open recovery and copy the "recovery.img-kernel" and "recovery.img-second"

use an image unpack "tool" to open the boot.img you downloaded , paste the copied files from recovery into the boot.img. Re-pack it, then test boot it with "fastboot boot test-boot.img"
[General Topics] mrmazak:
I have only used "tools" for packing un-packing the images, before. I realize the tools use "mkbootimg" behind the sceen but I am unfamiliar with it.

I use carliv image kitchen., I t is a batch program that makes packing un-packing easy.

https://xdaforums.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658

should be "kernel" and "second" both from your stock recovery. Added into the permissive boot.img from the root package download. You need to make sure you rename them from "recovery.img-kernel" to "boot.img-kernel"
[General Topics] TheNH813:
Thanks for the info. That tool is a lot easier to use, but it still hangs at the boot logo.

I have tried keeping the original second file in the v31 image, it boots properly, but touch still does not work.

The v31 second file is 523.4kB and the recovery version is 207.9kB.

The recovery file is 16.8MB and the v31 image is 10.2MB.

I think it might expect a specific size. Any suggestions what to do?