yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] moriel5:
Once again, I am sorry for the delay.

I did not have time to touch the device yesterday, due to my chores.

However, I tested it out today, right before going to work (hence the additional delay before I could post anything to the effect).

TWRP booted fine, and the hardware keys worked without any issues.

The display, while it worked, game me an odd density (the on-screen elements were overstretched horizontally), and some elements were a different color than expected (such as yellow highlights instead of blue), however I though that the colors may be due to your personal preferences, [MENTION=5312578]mrmazak[/MENTION].

Touch did not work at all, and the device was not found at all by ADB, whether it be in Linux or Windows, whether as a normal user, or as root/admin.
[Android Q&A, Help & Troubleshooting] mrmazak:
Yes i did not expect much from the twrp. I never got it to work properly either.

So perhaps you can make magic happen.

What about the patched boot, and cwm.?

I assume you had adb working on stock, as that is only way i know to get to fastboot mode and do bootloader unlock. Expected patched boot to give :" adb shell " returns "#" prompt. meaning root
[Android Q&A, Help & Troubleshooting] moriel5:
ADB works well on stock, and I did not have enough time to test anything other than TWRP.

Hopefully, I'll be able to test the patched kernel and CWM in the evening, after my sisters go to sleep.

Update: In the end I had managed to test out both images, I was just busy trying to restore data from customer's damaged hard drives and backing them up to the aforementioned customers' external hard drives (One has completed succesfully, another one has issues with accessing the data, so I may have to use TestDisk to access the data on the cylinder-level), prompting me to reboot my desktop several times.

CWM: Same exact situation as the generic one, everything works except for mounting /data and /sdcard (and perhaps also touch? This is the non touch CWM, so there isn't a way to know).

As such, I needed Windows to access the device through ADB.

Boot: Everything is fine, and I get a root shell from ADB (no issues from Solus here).
[Android Q&A, Help & Troubleshooting] mrmazak:
I think there may be issue with the adbd file used the patched images.

Because adb works for you on the stock system, and not on the initial cmw or twrp, so might need to use the stock versions of if from your device. But will not get default adb root capability, but don't worry will still work when superSU is installed.

I added an alternate patched boot.img and test-2 twrp. in the shared folder.

touch on the twrp is controlled by your kernel. so if it is not recognizing touch, not much can be done. AFAIK
[Android Q&A, Help & Troubleshooting] mrmazak:
the not mounting of /data is do to the encryption. And because the boot tested out ok. You can format /data and flash the test boot to keep it from getting encrypted again.

But please verify for me , which images you tested, so I can remove the unused ones , to prevent confusion.

Based on download count, you are referring to the first patched ones.
[Android Q&A, Help & Troubleshooting] mrmazak:
[MENTION=5358804]moriel5[/MENTION]

I looked fory notes on twrp for this tablet. I did not save them. I did dig up the thread I was working from, and that is here.

https://xdaforums.com/general/help/...oting-help-t3485625/post71497160#post71497160

First post on that page has a different build of twrp you can also try to use.

During my search for my old posts about it. I found where I made comments on how when I had twrp partly working, makeong a backup soft bricked the tablet, so be careful.
[Android Q&A, Help & Troubleshooting] moriel5:
Thanks, and sorry about my unavailability, work and family had taken up most of my time.

I have just thought of something, although it is not definitely going to help us.

After rooting this tablet, I want to try getting `lshw` running on the tablet, in an attempt to find more data about the tablet (I do not live in the U.S., and this tablet is intended for my sisters (we have no need for GAPPS, which is why I had "disabled" them via "adb pm hide"), which is why I cannot get another one (my father had accidentally bought it when he was in the U.S., since he couldn't contact me in advance), nor allow myself to disassemble it.

I shall be completely offline for the next ~50 hours or so, so I'll check out the thread after then.

As to the images, I do not understand what you mean, I had thought that you had only sent me one set of images, other than the TWRP.
[Android Q&A, Help & Troubleshooting] mrmazak:
Understand. In the same link I give before, to Android file host. I have added a second set of images. But I see now you did not know, so you are confirmed to work with only the original.
[Android Q&A, Help & Troubleshooting] DMon04:
So I've been reading every page of all the development with this tablet. You guys are far ahead. Has it been unlocked and a custom recovery ported now? If I'm reading it correctly,it seems there's now root?
[Android Q&A, Help & Troubleshooting] mrmazak:
Yes, same recovery and rooting process from my Voyager 2 worked on the 3. I ran the patching tool on the images supplied , and they worked as expected.

I do not have Voyager 3, so all verification has been from [MENTION=5358804]moriel5[/MENTION]
[Android Q&A, Help & Troubleshooting] moriel5:
Alright, I'm back.

I'm sorry it took so long, I had fallen asleep yesterday, so I did not have time today to log in either.

According to you, is it safe to flash the CWM, and also the modified kernel now?

I have been holding out on that, even though I had already backed up the partitions.

Also, how hard do you think it would be to port CoreBoot to these tablets? Perhaps MrChromebox's work on the chromebooks may help?

---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------

The tablet has had an unlock method since the beginning.

About the recovery, there is CWM which now appears to work without any issues, however I am waiting for [MENTION=5312578]mrmazak[/MENTION]'s affirmation as to the safety of flashing the images.
[Android Q&A, Help & Troubleshooting] mrmazak:
As long as the boot.img works normal when you fastboot boot it, then it can be flashed.

The cwm on the other hand, that can not be flashed. It only works when you fastboot boot it.

As far as final. App level root, need to flash system mode superSU. From cwm after formating /data to remove encryption.

Make sense, understand?
[Android Q&A, Help & Troubleshooting] moriel5:
Certainly, I personally prefer root to be in /system.

However, despite that, I had forgotten how to flash SuperSU in system-mode, since I am generally on CM/LOS ROMs.
[Android Q&A, Help & Troubleshooting] mrmazak:
I used superSU v2.82 from here

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

And you need to do mount from adb first. I will look at the script I used to verify the command exactly.
[Android Q&A, Help & Troubleshooting] moriel5:
Thanks, however mounting /system from CWM's GUI seems to work fine, so shouldn't it be alright to use that?
[Android Q&A, Help & Troubleshooting] mrmazak:
You of course can try. When I did it it looked like it installed, but when I rebooted it was not rooted. Second time I did "adb remount" when loaded in cwm and then the install worked.
[Android Q&A, Help & Troubleshooting] Droidriven:
Well, I wasn't gonna try it but I figured, what the heck, its wasting space in a drawer, it won't hurt if it bricks and can't be restored.

Based on the info in this thread and the other thread, I got the bootloader unlocked as others did in this thread, everything went as normal, it ran the unlock sequence, formatted userdata and cache but after fastboot reboot, it just bootloops at the Voyager III splash.

It won't boot to recovery, can't get to system to use the tool to get to fastboot, it connects to PC but not as ADB or fastboot device. I've tried booting various ways while running adb with ondemand.bat but it gets no response.

I have no clue what went wrong, I'm not unfamiliar with the process so I doubt it was user error, any ideas?
[Android Q&A, Help & Troubleshooting] mrmazak:
Try to do "pin hole reset"

There should be a pin sized hole on the back or side (not the mic hole) press it in for 3 to 5 seconds.

Outside of that I don't know.
[Android Q&A, Help & Troubleshooting] RobinHood16:
Aborted.

I absolutely CANNOT GET MY DEVICE to talk to the PC while in fastboot mode. I can install the Intel drivers, but they don't make any difference in my case. I'm guessing this must mean that my particular model does NOT have an Intel core.
[Android Q&A, Help & Troubleshooting] Jacube22:
Hi, I just bought this tablet, but it looks like I have the version with the quadcore ARM processor.

Could any of this custom recovery and stuff still work with my version? And if not, can anyone help me try to figure out how to at least root the damn thing? I have tried Kingroot/Kingoroot, dr fone, and one click root and all of them have failed.
[Android Q&A, Help & Troubleshooting] mrmazak:
The voyager111 is intel x86 (arm compatible through something called Houdini) quadcore chip.

there is also a voyager with mtk chip.

The device at botom of your post has a root thread here.

https://xdaforums.com/android/general/root-rct6303w87dk-5-0-lollipop-t3116016
[Android Q&A, Help & Troubleshooting] darkvoxels:
So I have compiled AOSP for my Pixel and actually bought this device just to mess with and learn more. I have unlocked the bootloader and can dump any partition via fastboot boot CWM recovery image from this post https://xdaforums.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973 thanks [MENTION=5312578]mrmazak[/MENTION]

SD Card mounting works in a fastboot boot CWM; seamed it didn't for others?

Can confirm mine is at least an x86 intel processor based off /proc/cpuinfo, it does have this Houdini application that translate arm code to run on x86

recovery.img and boot.img backed up fine via CWM but system failed, used dd to grab it manually

flashing the cwm recovery brakes the recovery, flashed back to stock

Tried android kitchen to modify the stock recovery to enable adb on the device but the rom didn't boot. (this was before i read this thread but also already made a backup of my recovery and new i would be able to re-flash), I didn't do every modification to defaults.prop from the link above though so will try again. Need to get adb working via recovery so if i screw up the system I still have a way to get to fastboot and can re-flash otherwise I will brick the device..

Would like to compile AOSP for this device but new to it and still trying to understand the propitiatory blobs, and device/vendor trees. Many tutorials show a /device under the system partition but there isn't one on this device, nor a proprietary-all.txt file. I will keep playing with this and hope to figure it out.
[Android Q&A, Help & Troubleshooting] mrmazak:
did you try my batch file to make patched stock recovery. It will;

1. boot cwm

2. pull stock images to pc

3. open images and make generic patches to make adb work in stock recovery.

and patch stock boot to give adb root

https://xdaforums.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
[Android Q&A, Help & Troubleshooting] darkvoxels:
I don't run windows so it will take me time to read through the script and see what its doing and do it manually.
[Android Q&A, Help & Troubleshooting] Jacube22:
So I assume that means that none of this will work with my device? that sucks.

And I know my other device has root, I Participated in that thread
[Android Q&A, Help & Troubleshooting] mrmazak:
this section is lines 307 - 316 of the "patch" batch file

mkdir stock-recovery\ramdisk\data\misc\adb
copy %userprofile%\.android\adbkey.pub stock-recovery\ramdisk\data\misc\adb\adb_keys
copy %userprofile%\.android\adbkey.pub stock-recovery\ramdisk\adb_keys
call jrepl "ro.secure=1" "ro.secure=0" /M /l /f "stock-recovery\ramdisk\default.prop" /o -
call jrepl "ro.debuggable=0" "ro.debuggable=1" /M /l /f "stock-recovery\ramdisk\default.prop" /o -
call jrepl "persist.sys.usb.config=mtp" "persist.sys.usb.config=mtp,adb" /M /l /f "stock-recovery\ramdisk\default.prop" /o -
call jrepl "persist.sys.usb.config=none" "persist.sys.usb.config=mtp,adb" /M /l /f "stock-recovery\ramdisk\default.prop" /o -
echo( >> stock-recovery\ramdisk\default.prop
echo persist.service.adb.enable=1 >> stock-recovery\ramdisk\default.prop
echo persist.service.debuggable=1 >> stock-recovery\ramdisk\default.prop

Translation

unpack stock recovery to folder, name folder "stock-recovery"
mkdir stock-recovery/ramdisk/data/misc/adb
cp ~/.android/adbkey.pub stock-recovery/ramdisk/data/misc/adb/adb_keys
cp ~/.android/adbkey.pub stock-recovery/ramdisk/adb_keys
replace "ro.secure=1" with "ro.secure=0" in "stock-recovery/ramdisk/default.prop"
replace "ro.debuggable=0" with "ro.debuggable=1" in "stock-recovery/ramdisk/default.prop"
replace "persist.sys.usb.config=mtp" with "persist.sys.usb.config=mtp,adb" in "stock-recovery/ramdisk/default.prop"
replace "persist.sys.usb.config=none" with "persist.sys.usb.config=mtp,adb" in "stock-recovery/ramdisk/default.prop"
echo new line to >> stock-recovery/ramdisk/default.prop
echo persist.service.adb.enable=1 >> stock-recovery/ramdisk/default.prop
echo persist.service.debuggable=1 >> stock-recovery/ramdisk/default.prop
[Android Q&A, Help & Troubleshooting] darkvoxels:
So I tried this with AIK tools in your other post on a similar device and with mktool to unpack and repack the recovery.img and I kept getting the error "unknown volume for path [/cache/recovery/last_locale]", I did a fastboot erase cache seen in another post around this error and bricked the device... now recovery and system dont boot as cache cannot be mounted didnt realize it would erase the file system and not just format it. Now I know woops. Will take it apart and see if i can find a pin out for the NAND/EMMC so i can solder some wires on and dd it to try and repair the cache partition. At least the tablet was pretty cheep.
[Android Q&A, Help & Troubleshooting] darkvoxels:
Took a look at the internals based off the FCCID https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=3232313, the EMMC is shielded and is a BGA so it would be difficult to identify what pins go to what pads. Im likely not going to try and flash the EMMC directly anymore so my tablet is pretty much a brick unless there is a button combo to get to fastboot.

Good luck to everyone on this thread, hopefully you guys can get an easy root and or roms soon.
[Android Q&A, Help & Troubleshooting] darkvoxels:
There might still be hope... found that while in bootloader mode the device connected via usb with the device id "Bus 001 Device 032: ID 8087:07f6 Intel Corp." looking this up there are drivers for an intel flash utility. andriodmtk.com had an intel flash utility, will look though the system to try and figure out the OTA stuff and pull the stock rom from the vendor, might be able to use that to recover... Will keep you guys posted...
[Android Q&A, Help & Troubleshooting] mrmazak:
you do know that adb should work with device powered off completely. As long as adb was autherized by system last time it was booted.

with device off, connect to usb cable. If this makes it power on, just turn it back off with long press power button.

after about 2 to 5 minutes you should see device in device manager. then can command "adb reboot fastboot"
[Android Q&A, Help & Troubleshooting] darkvoxels:
I did not flash the patched recovery.img only fastboot boot'ed it. right now everything is stock. plugging it in turns it on, turning off the device via volume down (bootloader unlock message warning, volume down power off) or via holding the power button while connected does not keep the device off. just turns back on my guess to show the charging animation. Hammering away at adb devices and fastboot devices during the whole boot process did not show any devices listed.

The intel platform flashing tool lite can see the device while the bootloader unlocked warning message is displayed but I takes a json, zip, xml, or tgz file. I took a look at other firmware made available by vendors like the intel edsion which can be flashed with this tool and json uses "tool" : "xfstkDownloader" to push "ifwi", "ifwi_dnx", "os", and "os_dnx" which are all .bin files that the vendor provided in a firmware download. I have seen forms where some asus tablets and zenphone users have used this to unbrick devices but RCA does not seam to provide the firmware anywhere.
[Android Q&A, Help & Troubleshooting] mrmazak:
yeah , i never got successfull fastboot boot of stock recovery. Only cwm or partial twrp.

maybe wrong advice about long press power.

how about volume down during bootloader warning. and just be patient.
[Android Q&A, Help & Troubleshooting] darkvoxels:
Pressing and holding VOL key down, (one marked with the + funny enough...) causes the bootloader screen to loop 3 time then the tablet turns off while plugged in to pc. No devices listed via lsusb.

After boot screen weather trying to boot into Recovery, System, and or charging animation it shows "Supported API: 3", "E:failed to mount /cache (Invalid Argument)" and on the next line "E:Can't mount /cache/recovery/last_locale"
[Android Q&A, Help & Troubleshooting] mrmazak:
did you check your shell history ? To double check the commands you sent. Because those messages do not make sense if all you did was "fastboot boot" a recovery, then "fastboot format cache".

I suppose as a next step, you could force stock recovery reset. By pushing in the pin-hole reset button.
[Android Q&A, Help & Troubleshooting] darkvoxels:
The problem is i didn't run fastboot format cache, i ran fastboot erase cache.
[Android Q&A, Help & Troubleshooting] Droidriven:
Intel Atom is x86, not ARM.

---------- Post added at 02:23 PM ---------- Previous post was at 02:23 PM ----------

Wrong thread, post in the Pixel forum.
[Android Q&A, Help & Troubleshooting] mrmazak:
Went back and changed it.

Did you get your tablet booting again?
[Android Q&A, Help & Troubleshooting] Droidriven:
Ah, I see, a typo or autocorrect got you?

To answer your question, no, I didn't. Still charges but only bootloop and makes no connection to PC.

I've considering trying to brick it further to put it in a different state that might allow some other means of "backdoor" connecting/flashing. Similar to forcing a device into qhs dload to use QPST or QFIL. But I can't get any interaction, it tries for just a second while booting but doesn't register anything other than the sound it makes in Windows. I've tried using adb echo script to see if I can get adb or adb shell commands to work. If I can connect in some manner, I can fix it, maybe.
[Android Q&A, Help & Troubleshooting] darkvoxels:
Mine is bricked as well, I noticed while its on the bootloader unlock warning screen with 30s count down mine does connect to the pc and can bee seen by intel platform flasher tool. I just dont know how to generate or obtain the files it needs. I was able to rip my boot, system, and recovery before bricking so will try and do some research to see if I can generate them.. Bought the huawie t3 8.0 to hack around with in the mean time.

Do you even get the bootloader unlocked warning screen?
[Android Q&A, Help & Troubleshooting] Droidriven:
Yes, I get the bootloader screen with the 30 sec countdown and also the connection sound in Windows. I've opened device manager while connecting the device, it doesn't even show for even a brief second in device manager when it makes the connection sound. Not sure if it's actually "making" the connection or just "detecting" the possibility of a connection before it actually connect and then the possibility is gone, ruining the chance of connecting.
[Android Q&A, Help & Troubleshooting] darkvoxels:
Also just to potentially benefit the thread below are the IC/chips and Info I found on the mobo:

MotherBoard Version:

* em3230-7126

** Found this page for the manufacture edong http://www.edongtech.com/en/index.php?c=product&a=type&tid=2

*** There is a pdf but I cannot seam to download... )=

IC's

PMB8016 - Intel Chip

PMB9102 - Intel Chip

BWCTASC21G16G - BIWIN NAND, could not find much online was hoping to find a breakout board where I could de-solder, backup, repair the image, flash, then resolder

RK818-2 - Rock Chip Power Managment

GSL1680 - Touch Display Driver Chip

---------- Post added at 09:26 PM ---------- Previous post was at 08:56 PM ----------

Sounds like it might be a driver issue? Windows detecting and trying to install driver? I run linux so via lsusb i can see the device show up during the whole 30s. You can try and get the drive via installing the intel platform flash tool lite. Its the same software intel uses to flash the intel edison dev boards. I cannot seam to find the software download on the intel site but there i did find it on this site:

https://androidmtk.com/download-intel-phone-flash-tool

The flasher tool takes in a json file that appears to use other programs, the one to flash the firmware is "xfstk downloader" and needs a FW DnX, IFWI, OS DNX, OS Image. If you want an example of what a firmware looks like you can download the intel edison firmware. http://downloadmirror.intel.com/25028/eng/edison-image-ww25.5-15.zip

When I have the chance I will spend some time trying to understand what each of these 4 files are and see if I can create them from the backups.

It should have the drivers you need but to be honest without the firmware files there’s not really much use.
[Android Q&A, Help & Troubleshooting] Droidriven:
I have a linux system, I haven't tried anything with it. I'll have to unpack it and set it all up, I'll give it a try and see what I come up with.
[Android Q&A, Help & Troubleshooting] darkvoxels:
Here is an example of an android based device getting flashed with these tools. Look under the "Last Resort Section"

https://www.asus.com/zentalk/thread-33800-1-1.html

---------- Post added at 10:18 PM ---------- Previous post was at 09:58 PM ----------

Think I found the Intel xFSTK Downloader source code, going to look through it and see what commands its able to send to the phone. DNX mode is intended to flash firmware but maybe It can tell the phone to boot a specific parathion and allow us to get into fastboot. Fingers Crossed.

https://sourceforge.net/projects/xfstk/
[Android Q&A, Help & Troubleshooting] RobinHood16:
I'm getting closer... There's an associated web page here which I had to follow to get my device working in fastboot mode. Now, when I type "fastboot devices" in a command prompt, I get "20D160A4C8E0 fastboot", meaning I am home free as far as flashing my device. Now, however, I have another problem... When I say "fastboot flashing unlock," my device gives me the "yes/no" option, but it only appears for about a second before it disappears, and the Windows command prompt returns "FAILED", as if the Android device is assuming "no." It's possible my volume down button is stuck, but before we assume that this is the actual problem, what else could be wrong?
[Android Q&A, Help & Troubleshooting] mrmazak:
It does usually only give short time to answer that yes, no.

O have seen few times people suggest holding volme button before hit enter on the command window,to beat the timer.

But maybe before you do that, remove your Google account and do factory reset. Because these last two users here in the thread have been stick in bootloop just from doing unlock(when tablet supposed to be doing factory reset)
[Android Q&A, Help & Troubleshooting] RobinHood16:
How long does it suggest to hold down the volume up button? Because the EXACT MOMENT I release it, fastboot says the power button was pressed (even though I never pressed it) and the operation fails. On the other hand, if I hold the volume up button for about 70 seconds, fastboot will report a timeout, and the operation still fails.