yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] hauckk@sfreserves.org:
Fastboot oem unlock is the normal command to unlock the bootloader for Fastboot devices i saw another reason tablet on xda developers I believe it was called rca viking or something similar there is a bootloader unlock and root thread for that device maybe worth looking at

Here is the paid site I have 2g so I can't check the website to see if it legitimate

http://www.sitelinks.info/notepad.p...ggYMAU&usg=AFQjCNE5BXp8BnP_V6-WI_RI7-1grLywDQ

---------- Post added at 09:02 AM ---------- Previous post was at 08:38 AM ----------

This website claims to http://www.srsroot.com/ have rooted the tablet but they are known for false root proclamations worth a check
[General Questions and Answers] fsebentley:
I tried the oem unlock command and it does not work, returns command fail...

The Viking uses the MT8127 SOC which would tend to have a different Firmware.. since that is a chinese SOC I expect the unlock to be

a bit easier typically i have found that on Tablets they often do not even lock the bootloader... the Sofia 3gr or Atom X3 is in the tab we have I have been looking into similar devices... so far I have not got much reading done on these... I will have a look at any info I can locate on here regarding the Viking .. but I have already read about some of the other Model # / versions of the Voyager on here and ours is not the same. The ones I have read up on so far do not seem to have a major problem rooting. This one is a bit of a pain as I cant use adb in root mode which when possible makes rooting much easier...

The link to the Paid site you posted seems to be dead...

I have tried SRSRoot which also does not work... actually i have attempted using Kingoroot, iroot, rootgenius, framaroot, towelroot, tunesgo

and OneClickRoot none have any success at all... they do indicate varying degrees of progress but in the end the most that any has accomplished is to push their app to the tab.

I will keep trying and looking... perhaps I will locate a firmware for these out there so i can examine the partitions and their contents more

closely...

Thanks
[General Questions and Answers] just a bird xo:
Were you ever able to gain root?
[General Questions and Answers] hauckk@sfreserves.org:
I haven't yet
[General Questions and Answers] fsebentley:
No I have still not got root access, I have unlocked the tablet and am exploring ways to load a recovery image from fastboot without flashing it. I have also inquired with RCA about getting a copy of the Firmware and I continue to search google etc. for the firmware. Once I have the firmware I am confident that I can root the Tablet fairly quickly.
[General Questions and Answers] hauckk@sfreserves.org:
How did you get bootloader unlock?
[General Questions and Answers] fsebentley:
fastboot flashing unlock while pressing vol + button on tab... if you simply enter the command while watching the screen you can see the display flash a message calling for input... if you press no buttons it auto enters a no answer... it goes by really fast so the only way I have been able to catch it is by pressing the + vol button then enter the fastboot flashing unlock

that does the trick.
[General Questions and Answers] hauckk@sfreserves.org:
Thanks
[General Questions and Answers] just a bird xo:
Which mode do I have to be booted in for this to work?

I've tried entering adb reboot bootloader as well as adb reboot fastboot & I can't seem to get it to unlock.
[General Questions and Answers] fsebentley:
I usually just go into adb shell, then do reboot fastboot.

The Tab will reboot with an apparent blank screen, if you look closely you will note that there is a faint backlight. Once in this mode your PC will have a new device in device manager, if it is unrecognized device you can manually assign a device driver. I have the intel drivers installed as well as the google drivers. Woth the intel drivers you can do an Update driver select Browse my computer for driver software, then Let me pick from a List of device drivers on my computer, then scroll down to the Intel Android Device in the list and select either the Intel Android Bootloader device or the Android Bootloader Device, Both seem to work fine.... If you do not install the intel drivers then you should be able to select the USB devices option then select theADB Device. This also seems to work fine...

When in fastboot mode you will havea blank screen however when you enter certain fastboot commands there will be a very brief flash of information/input needed on the screen, it seems the ui in this mode is inhibited in some way.

Also worth noting on this model almost all the commands previously done using oem [command] are now done with flashing [command].
[General Questions and Answers] fsebentley:
I have now located a firmware for this device and am downloading it. The file is on baidu so is going to take some time to get but once I have it I should be able to do something with the bootloader to allow rooting by most of the conventional apps... as well as make my own rooted version of the firmware and likely get started modding it...

Well the first one I found is a bust... the files contained in the .zip are not in a format that is directly usable or they are corrupted. It appears to contain files from an MTK scatter and has MTK info in the text based config files.. so either someone pulled these using the MTK tool incorrectly or they labeled the file incorrectly as rct6873w42 firmwares... or this could be something I am not aware of...

either way these are taking some time... baidu is slow...
[General Questions and Answers] fsebentley:
Well it seems that all the ones I have found and downloaded so far have turned out to be mislabeled firmwares for other models of the RCA devices. I will keep pulling them in hopes of finding one that works but meanwhile I will look into some other avenues as well.
[General Questions and Answers] JordanMoore1371:
So far I'm with you guys up to unlocking the bootloader. Have we made any progress with locating rootable firmware? I've rooted a phone before but never a tablet let alone such a pain in the neck tablet.

I have run

fastboot flashing unlock

and got all that squared away, is there anything else to do at this point? Is it safe to continue to use it in it's current state? You guys are awesome by the way I couldn't find anything anywhere else online for this model. Y'all are making history!
[General Questions and Answers] hauckk@sfreserves.org:
We need to port a custom recovery to this tablet a lots harder than it sounds
[General Questions and Answers] JordanMoore1371:
Anything we can do to help? Can't be too crazy can it?
[General Questions and Answers] rpk3:
Are you bricked-?
[General Questions and Answers] mrmazak:
no.

i just "fastboot boot recovery" to test, not flash. i try not to flash before i do some test
[General Questions and Answers] rpk3:
What are you doing about recent apps taking all memory...i think square gets you to the recent stuff.

Bloatware removal?
[General Questions and Answers] mrmazak:
I haven't really done anything else.

I've been playing around with other things lately.
[General Questions and Answers] rpk3:
I just cant seem to add the new string to the default usb drivers on my win7 machine.

Im just trying to modify the .inf files for adb drivers to detect this device. I need to have it so a noob can install at his workstation. Any thoughts....

=========

my personal string to allow windows to see the device.

;RCA 6873w42

\VID_8087&PID_0928&MI_01

%SingleAdbInterface%

USB_Install, USB =

USB\VID_8087&PID_0928&REV_????&MI_02

%SingleAdbInterface%

USB_Install, USB	=

USB\VID_8087&PID_0928&MI_02

%SingleAdbInterface%

USB_Install, USB	=

USB\VID_8087&PID_0928&REV_????&MI_04

%SingleAdbInterface%

USB_Install, USB	=

USB\VID_8087&PID_0928&MI_04

%SingleAdbInterface%

USB_Install, USB	=

USB\VID_8087&PID_0928&REV_????&MI_06

%SingleAdbInterface%

USB_Install, USB	=

USB\VID_8087&PID_0928&MI_06
[General Questions and Answers] mrmazak:
I dont know about that but I just installed the android intell drivers and the tablet is just recognized.

IntelAndroidDrvSetup1.10.0.zip

System Driver

8.9MB

from here
[General Questions and Answers] The Blind Squirrel:
Hey Everyone

I am new to the forum and new to rooting. I have been following this thread for a while not and i wanted to thank everyone for their hard work. If it would be ok, i was wondering if i can ask for the Noob help. I am trying to just gain root access to my RCA Voyager rct6873w42, but i can not seem to get that or get to bootloader mode. If it was previously posted I apologize in advance if i missed it but any help would be more than appreciated.
[General Questions and Answers] mrmazak:
we still do not have a real "full root"

only a root shell from adb while in clockwork recovery. I have made backups and restored with this recovery. But needed to format system before restore , or it would fail and lock up, forcing a need to format in fastboot before restore would work.

fastboot mode is accessed by typing "adb reboot fastboot" from command terminal.

The recovery olny has access to /data when phone is not encrypted. Can only have in not encrypted by using a modified boot.img

The "force-encrypt" flag is set in the fstab of stock boot.img.

It is also set to "force-encrypt" in stock recovery, so that needs to be changed as well.

I put up a "tool" that can be used to get you to this point, if you are interested.

Update for thread on my lack of progress:

All my attempts to get further have failed.

Tablet always boots into "enforcing" even with kernel command line set to permissive.

I have added "write /sys/fs/selinux/enforce 0" to the init.rc . This made no noticeable change.

When I added same line "write /sys/fs/selinux/enforce 0 to few more places in the init.rc, the tablet refused to boot, and only stayed on the boot anmation screen.

And when I try to load with "audit=0" in kernel command line , the same thing tablet refuses to boot.( I was thinking with out audit running kernel would not know when set to permissive and allow it to boot, but instead with out audit, kernel cannot get messages from "vold" so partitions do not get mounted.)

I think kernel is written with flag that prevents permissive mode from running

(EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true), so it appears that only way forward is with custom kernel.
[General Questions and Answers] jakfish:
I too have the same device and have been following this thread with great interest. Thank you for both your hard, hard work and for your most recent post summarizing all your efforts.

Jake
[General Questions and Answers] The Blind Squirrel:
I could not agree more!
[General Questions and Answers] cozzie37:
My custom kernel attempts have come to a complete standstill, partly because I now have no way to test/use them. It may be possible to use the Yocto BSP to generate a working kernel, but the documentation makes it sound like it's not intended for it. Possibly stripping the kernel for hardware support patches would work, but I don't have that kind of time, or a tablet to test on. Another option is to use the Android BSPs from AMI (https://marketplace.windriver.com/index.php?bsp) or Wind River (https://marketplace.windriver.com/index.php?bsp), but I don't know if they'll just hand them out to anyone, I haven't tried requesting them. There would also be more work needed aside from just getting the SoFIA 3GR kernel, the Yocto BSP is configured for a totally different board, and I imagine the AMI and Wind River ones are as well.

A third option, if you have tried to request source code for this or any other RCA or ALCO tablet, is to email compliance@sfconservancy.org and let them know what model you have and what your experience was. They will work to enforce GPL compliance with RCA/ALCO.
[General Questions and Answers] vampirefo:
I think I have you something to test, only test not install.

adb reboot fastboot

fastboot boot rca-boot_permissive.img

after boot up

adb remount

https://www.androidfilehost.com/?fid=673368273298938977
[General Questions and Answers] mrmazak:
It booted, but will connect to adb.
[General Questions and Answers] vampirefo:
Switch out adbd file for one that works, which everyone you use in recovery to get working adb.
[General Questions and Answers] mrmazak:
will try that, again, but last time it made it to fail boot(when tried to use the insecure adbd from cwm). update in few minutes

gonna use the stock adbd

booted with stock adbd, adb remount returns "not running as root"., "try adb root"

adb root returns "restarting as root" , but does not appear as root just restarts as user seems to be)

getenforce returns "enforcing"

will now try with adbd from "cwm"

***ding-ding-ding*** we have a winner

adb remount success

adb shell whoami ="root"

adb shell setenforce 0 return success

then adb shell getenforce = permissive

this is the image i used

.only booted with fastboot boot

not flashed

.
[General Questions and Answers] vampirefo:
Yes, this is what was suppose to happen, upload the adbd file that you are using, I need to look at it.

Never mind you have uploaded it, I didn't see the link first time.
[General Questions and Answers] mrmazak:
Is the only difference in this boot.img the sepolicy?
[General Questions and Answers] vampirefo:
Yes, I modified it to be permissive, and I changed all the data mount points, as well as default.prop, right now my electric is off so can't do anything til it comes back on.

---------- Post added at 11:17 AM ---------- Previous post was at 11:04 AM ----------

This is how I root my Intel, patch sepolicy to be permissive, then once boot.img is ready flash to phone, then download system only SuperSU and install it, then all is well.

Normal SuperSU would try to patch boot.img this would brick the tablet.

Installing system SuperSU without patching sepoliçy would brick tablet.

Still need some more work, but I have no electric, tree fell on power line so I can't finish your boot.img.

System mode SuperSU is here.

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[General Questions and Answers] mrmazak:
I will have to try this out tonight. I'm on The road today

My plan is to add a service to init.rc that calls a shell file with permissive 1.

That way it will boot permissive, now that sepolicy allows it.
[General Questions and Answers] vampirefo:
No that won't work, I am working on next stage right now, which does automate permissive on boot.

it's a two part system, one part goes is /sbin other in /data.
[General Questions and Answers] mrmazak:
i did make a one line change to init.rc and got a permissive boot

I added :

# root use permissive
write /sys/fs/selinux/enforce 0

to the init.rc and booted it. I got permissive on boot. Is this method ok?

here is first few lines on logcat showing ok .

--------- beginning of main

03-16 17:07:56.890 167 167 W auditd : type=2000 audit(0.0:1): initialized

03-16 17:08:01.700 167 167 I auditd : type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295

03-16 17:08:01.700 167 167 W auditd : type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295

03-16 17:08:02.670 167 167 W auditd : type=1404 audit(0.0:4): enforcing=0 old_enforcing=1 auid=4294967295 ses=4294967295

03-16 17:08:03.219 175 175 I /system/bin/tzdatacheck: tzdata file /data/misc/zoneinfo/current/tzdata does not exist. No action required.

---------
[General Questions and Answers] vampirefo:
[MENTION=5312578]mrmazak[/MENTION]

Below is how I rooted my tablet keep in mind I don't have your tablet, My info is based off of the files you provided and your feed back.

This should work, but it could brick your device, I just need you or anyone else testing this to realize, I have no backup files to fix your device if it gets bricked.

I have a root package ready for you to test the upload site isn't on line right now so I will post the readme so we can discuss it, so you know what to do.

adb shell

setenforce 0

adb remount

adb push su.img /data/su.img

adb reboot fastboot

fastboot boot rca-boot_permissive_on_boot.img

adb shell

getenforce

Your result should be Permissive

adb reboot fastboot

fastboot flash boot rca-boot_permissive_on_boot.img

fastboot boot recovery.img

install UPDATE-SuperSU-v2.79-SYSTEMMODE.zip

reboot system

select NO
[General Questions and Answers] mrmazak:
Thank you I think I understand the flow of this method. But I was able to get permissive on boot another way.

I am not experienced enough to know if it is a bad way to do it or not though.

I added a line to init.rc that writes to the selinux "enforce" file

"write /sys/fs/selinux/enforce 0"

in the init.rc made it boot into permissive
[General Questions and Answers] vampirefo:
You can try it your way, up to you.
[General Questions and Answers] mrmazak:
Because I know there are right ways to do things and then ways to do it but have side effects. Not sure where my ways fits into that analogy.
[General Questions and Answers] vampirefo:
I don't know either, I am posting how I root intels, I can't tell you what will happen if you do it your way as I never did it that way. I will provide you with what I have then you decide, best I can do.

Server still offline.

SYSTEM NOTICE: Devs: We are working on the upload server and syncing of files. Uploading of new files is disabled at this time. Some new files may show only one mirror until maintenance is finished.

if you wish to continue your method simply flash the boot.img you have then boot into cwm recovery, install UPDATE-SuperSU-v2.79-SYSTEMMODE.zip, reboot system, select NO.

either it will work or won't no guarantee my longer method will work either.

they are both the same, mine has more steps as I like to use caution, and I repeat stuff that works for me.
[General Questions and Answers] mrmazak:
Alright Update 1

I was able to flash my boot.img. It survived and boots ok. It gives me permissive at boot time.

I downloaded	SR3-SuperSU-v2.79-SYSTEMMODE.zip and tried to flash it.

It gave complete without any failed mssage, but superSu app was not installed. I installed from playstore , but it said no binary found. So i removed it.

I went back to cwm recovery and manually mounted data, then flashed the superSU update.

it worked. but now I am reminded how slow this tablet is.

summery;

with [MENTION=2472806]vampirefo[/MENTION]'s sepolicy and the adbd from the twrp we have from vampirefo also I have been able to get a reeot shell from adb while inside android.

And then with that sepolicy inside the boot.img flashed to tablet I was able to flash twrp "system mode" .

Possible problems I have seen already.

1. first boot after flashing superSU I could not get any wifi signal, this makes no sense to me, yet.

second reboot wifi came back

2. I had turned off the "click" from keyboard, after superSU it is back on again ...? dont know why,
[General Questions and Answers] vampirefo:
Yes, I would think the tablet is slow, the specs are similar to mine, anything less than 2GB ram is going to be slow.

---------- Post added at 10:03 PM ---------- Previous post was at 09:52 PM ----------

I recommend not using SR3, use update as it is stable, your problems might be due to using SR3.

I would get my root package uploaded soon, seeing you know yours now work, you could unroot your try my version and see if you have the same problems.

Or if someone else wants to try it,.
[General Questions and Answers] mrmazak:
oops, I just went straight to the bottom link as most recent. (Impatient). I usually choose stable versions over beta's. will try switching to stable now

---------- Post added at 10:48 PM ---------- Previous post was at 10:15 PM ----------

Here is the boot img that will give our tablet permissive at boot up.

Once tablet is able to boot in permissive mode, superSU can be flashed in CWM.

I can put these files into a V3 of the unlock tool. If requested.

===>LINK to permissive at boot.img
[General Questions and Answers] vampirefo:
Here is my root package.

Everything is included is this zip file, you need to extract it somewhere before you begin.

https://www.androidfilehost.com/?fid=673368273298939423

adb shell

setenforce 0

adb remount

adb push su.img /data/su.img

adb reboot fastboot

fastboot boot rca-boot_permissive_on_boot.img

adb shell

getenforce

Your result should be Permissive

adb reboot fastboot

fastboot flash boot rca-boot_permissive_on_boot.img

fastboot boot recovery.img

install UPDATE-SuperSU-v2.79-SYSTEMMODE.zip

reboot system

select NO
[General Questions and Answers] mrmazak:
was there supposed to have been a file at "/sbin/launch_daemonsu.sh" ?

the daemonsu is in the su.img, but the script that calls it isn't found.
[General Questions and Answers] vampirefo:
Correct, will upload again. the uploader seems to down again.

https://www.androidfilehost.com/?fid=673368273298939423
[General Questions and Answers] rpk3:
Gonna try this later. On road 4 work....
[General Questions and Answers] vampirefo:
well finally got around to changing compilers, TWRP 3.1 now builds and works on my intel, I just didn't want to change compilers as it takes a while, but all done now.

---------- Post added at 09:52 PM ---------- Previous post was at 09:40 PM ----------

[MENTION=5312578]mrmazak[/MENTION]

Here is one for you, you may need to unpack repack and so forth with your own files it boots as is, on my intel, touch is turned as you requested.

https://www.androidfilehost.com/?fid=457095661767145562
[General Questions and Answers] mrmazak:
thanks. Now I know what I'm gonna do next.

****FSTAB HAS FORCEENCRYPT****** on data
[General Questions and Answers] vampirefo:
No, it doesn't. # means it's ignored.

It says encryptable=footer but even that line is ignored. via #

/boot	emmc	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071	None;length=0 flags=display="boot";backup=1
/recovery	emmc	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121	none;length=0 flags=display="recovery";backup=1
#/misc	emmc	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID074	None;length=0
#/cache	ext4	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070	nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered;length=0
/system	ext4	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068	ro,noatime;length=0
/data	ext4	/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069	nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard;length=-16384
#/data ext4 /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069	nosuid,nodev,nodiratime,noatime,noauto_da_alloc,discard,journal_async_commit,data=ordered wait,check,encryptable=footer
#/sdcard datamedia /dev/null defaults;defaults
/external_sd auto /dev/block/mmcblk1p1 defaults;defaults
[General Questions and Answers] mrmazak:
not the ramdisk/etc/recovery.fstab

the ramdisk/fstab.sofiaboard_emmc and ramdisk/fstab.sofiaboard_nand

fstab.sofiaboard_nand

#
# Copyright (C) 2013 Intel Mobile Communications GmbH
#
# Sec Class: Intel Confidential (IC)
#
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#

/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 /system ext4 ro wait
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 /data ext4 nosuid,nodev,nodiratime,noatime,noauto_da_alloc,discard,journal_async_commit,data=ordered wait,check,forceencrypt=footer
/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070 /cache ext4 nosuid,nodev wait,check

/devices/soc0/e0000000.noc/ef010000.l2_noc/e1000000.ahb_per/e1400000.sd/mmc_host/mmc* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata
/devices/soc0/e0000000.noc/ef010000.l2_noc/e2000000.ahb_per/e2100000.usb/usb* auto auto defaults voldmanaged=usbdisk:auto
[General Questions and Answers] vampirefo:
Those mean nothing to TWRP.

TWRP can only read /etc/recovery.fstab
[General Questions and Answers] mrmazak:
oh, ok then
[General Questions and Answers] vampirefo:
You can remove them without any problems they mean nothing to TWRP.