yashsingh1/xdaforums huggingface dataset:
[General Topics] ssand1984xx:
bootloader unlocked

this for only the following version of the rca voyager tablet, confirmed attached photo

i followed the instructions below:

1. install abd and fastboot on pc with drivers

http://downloadmirror.co/29Xn/adb-setup-1.4.3.exe

Download the adb-setup-1.4.3.exe file from the download link above.

Double-click/Run the adb-setup-1.4.3.exe file.

You will see a command prompt window with blue background. Say YES to all the prompts on this screen.

└ To say YES, just type Y and hit enter.

Once ADB, Fastboot and Drivers are installed, the setup window will automatically close and

you’ll have a working ADB and Fastboot setup throughout your system

2. if you havent already unlock developer mode and enable usb debugging and oem unlock on tablet.

3 connect your tablet o your pc with a usb cable and the otg charger as well.

4. open a command window on your pc (windows button + r and type cmd and press enter)

5. boot your device into bootloader mode using following command

adb reboot bootloader

6. once in mode, issue following command to unlock

fastboot oem unlock

7. once unlocked your device will reboot into bootloader mode. you need to boot into system now using

fastboot reboot

8. ****factory reset will occur***** during reboot it will factory erase and reboot into system.

done.
[General Topics] jakfish:
This is great news and thank you especially for the clear instructions.

I'm going to do it (and I already understand that you are not responsible for any damage, etc, etc).

A couple of questions before I start:

1) Did you make a backup stock ROM before you rooted? And if so, could you point me to the tutorial?

2) is this root persistent after a factory reset?

I'm less worried about screwing up the rooting and more worried about not being able to fix things post-root (i.e. bad app, deleted system file, etc).

Again, thank you for figuring all this out.

Jake
[General Topics] mrmazak:
He has not described root. Just unlocked bootloader
[General Topics] jakfish:
Ah, I hadn't grasped that. In his previous post, ssand1984xx said he had found a way to root.
[General Topics] ssand1984xx:
Jake. I did not make a backup stock rom bc i did not root it yet. Im sorry if my mesagemis communicated that. But in the recovery mode you can make a backup to your pc. Save thst off tablet in caseyou make a mistake. Ill try and post some imsges of it
[General Topics] jakfish:
That'd be great. Thanks.
[General Topics] ssand1984xx:
backup through recovery

power down tablet and go into recovery mode by pressing power and up button. make sure to insert a blank micro card big enough for the backup. nothing on it . once in then select backup user and this can take up to 45 min so be patient. when done. take out card and replace orginal and select reboot to system and ur done. pics below hope they help
[General Topics] mrmazak:
You might be able to use this thread to make twrp for the mtk version.

https://xdaforums.com/showthread.php?t=2798257

The thread is long and comments suggest it is still working method takes very little for it to work. There is good AIO script tool .

Now bootloader is unlocked. I did not suggest before because it needs to be unlocked
[General Topics] jakfish:
[MENTION=7662116]ssand1984xx[/MENTION]: Thank you, thank you for another set of clear instructions. Especially important is realizing the wait time. As your picture shows, there's no discernible sign of process of the backup, so amateur users (like me) might abort things.

For the record, it seems one needs at least a 4gb card. My backup weighed in at 3.03gb.

[MENTION=5312578]mrmazak[/MENTION]: thanks for the Easy Magic link. I've yet to try unlocking the bootloader. Once I do that, I'll explore a second backup. Offhand, do you think there's a difference in the final product (RCA's homegrown version vs Easy Magic)?
[General Topics] mrmazak:
As far as I can tell, the easy magic version is only for mtk.
[General Topics] ssand1984xx:
you are welcome. sorry the pictures were a bit vague...just make sure to put in new sd card reboot into recovery and select backup user..wait the time....take out card....put old one back and reboot back ino system. need help hmu. now lets figure the root or makin custom recovery.
[General Topics] jakfish:
https://xdaforums.com/general/help/help-rooting-rca-voyager-pro-t3275962/page2

[MENTION=7662116]ssand1984xx[/MENTION]--Just after your post, MotoJunkie01 found root, but it's unclear about the actual device.

Do you have an opinion about that? Also, there seems to be a dilemma between choosing Kingroot and Kingoroot...
[General Topics] ssand1984xx:
Yeh ive begun to read about it. Its unclear which device.but the processer matches and.mentions its some old.kindle fire device. Let me take a look and.see if we.can crack it today.

---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------

Thank you so?much for your support. Ill get to reading and see if we cant.crack it today and.obtain root
[General Topics] ssand1984xx:
im thinking kingo might be better but im gonna trry both ill updatelater today
[General Topics] jakfish:
I seem to be stuck in the process of unlocking the bootloader. With the adb download, I couldn't get my Voyager recognized in either Win 8.1 or XP. I have a Win10 that I'll try.

But a more pressing problem is the Voyager is stuck in "=> FASTBOOT mode..." Holding down the power button for extended periods of time doesn't work and I can't get the device recognized, I can't send any command from the PC's.

At this point, I'm going to let the battery run out--that seems to be the only way to see if it's bricked.

I looked up the take-apart of the Voyager and the battery appears soldered, so no easy way to disconnect.
[General Topics] mrmazak:
It could sometimes take 20-30 seconds holding power button to release fastboot mode.
[General Topics] jakfish:
I've held it down for 120 seconds and I'm still in FASTBOOT mode...

Trouble is, I started out with 100% battery. With no wifi and other power-drainers, this device could be stuck for a while.
[General Topics] mrmazak:
Should be a pin hole on back for reset
[General Topics] jakfish:
Your advice was correct. I saw the pinhole on the side, that was mic, and I ended up down a rabbit hole of googling for reset. None of the hits talked what you suggested: that the reset hole is simply at the back, not on the side.

At any rate, I've reset, successfully unlocked the bootloader (seems to work on Win10), and we'll see about rooting in the near future (hopefully).

Thanks again,

Jake
[General Topics] ssand1984xx:
damn jake. im so sorry about that. i forgot to mention windows 10 version but im glad you got it corrected with [MENTION=5312578]mrmazak[/MENTION] help. my bad. can you send me your device info so i can compare the build models so we can get this figured out TODAY. thats my goal anyway. sleep be damned.
[General Topics] jakfish:
Hey, not to worry. We know we're taking chances. My specs:

1) RCA Voyager Pro

2) Model number: RCT6873W42M/Hardware MT8127/CPU Cortex-A7

3) Android 6.0/Kernel ver. 3.18.22

4) Android security patch level: June 1, 2016

5) Build number: RCT6873W42KC-ANDROID6.0-V26-V1.13.30

Let me know what else I can do.

Jake
[General Topics] mrmazak:
I read in the magic twrp thread (on PG 7) that this chip should be compatible with the builder. Although it is a 3 year old thread. And there is built recoveries on the thread for mt8127. They probably need to be modified some (mount points, etc).

If you can't build with the AIO tool from ==>link this thread(twrp), or ==> this thread (PhilZ recovery),

Oops, just realized the download section of those threads are removed.

you could try to "fastboot boot recovery.img" with one of the posted builds

Or build from scratch as the dev who made the tool states ==> here.

****Disclaimer*******

I cannot ensure this will work,

I cannot be certain this is safe to try

I cannot etc, ETC

All you do to your device is at your own risk.
[General Topics] jakfish:
Many thanks, mrmazak. Anyone would know your heart's in the right place and your help is first-rate.

Jake
[General Topics] hauckk@sfreserves.org:
i have a rct6873w42-ANDROID6.0-v17-v1.16.60-E00

the v8 tool doesn't work for me

has this build number been tested I want try the manual version is it safe?
[General Topics] mrmazak:
I wish I knew for sure.

I only got a few reports of success , and posted them all.

I am fairly confident that if you try "fastboot boot rca-boot_permissive-20170316-1706.img" should be sufficient test to see if it will work.

There maybe a message about /data not able to be de-crypted and a suggestion to do a factory reset. DO NOT DO THAT ON THE TEST BOOT

Also should be safe to "fastboot boot rca-recovery-cwm-ramdisk.img" should be safe to test.
[General Topics] MENTD:
I've been waiting for this to get rooted forever!

I just came here excited as ever as soon as I realized it finally appears this has happened!

But wouldn't you know it?!!??! My luck sucks!

I have BUILD NUMBER: RCT6873W42-ANDROID6.0-V31-V1.17.80-W04 which is even higher than the

V1.17.70-W01 listed as not working so I assume mine won't work either.

Is there any progress being made towards the build I have???

The only reason I bought the thing is because I assumed it could be rooted, there are posts

around that I've found which claim to root it but they are all non working.

It's pretty useless unless it's rooted. (At least, for many of the things I need to do!)

MANY TIA FOR HELP AND INFO! 8)

Here are my full specs:

MODEL: RCT6873W42

FCC ID: A2HRCT6773W22

IC: 9903A-RCT6773W22

ANDROID VERSION: 6.0.1

KERNEL VERSION: 3.14.0 TUE. AUG. 23 19:36:00 CST 2016

BUILD NUMBER: RCT6873W42-ANDROID6.0-V31-V1.17.80-W04

ANDROID SECURITY PATCH LEVEL: JUNE 1, 2016
[General Topics] mrmazak:
The bootloader unlock was the same for that build. It was the boot.img that made trouble.

I have been waiting to hear from anybody with the V31 build. To see if the cwm boots. Even if screen is not shown , it might still have adb connection.

Without flashing any images.

If it does boot you should be able to pull the boot image and I can try to make it work
[General Topics] MENTD:
AWESOME! So if I understand correctly, you've been waiting for me?!?! 8)

Anyhow... I haven't tried any of this yet as I was waiting to get confirmation that it would be

worth it on my build. However, I have been using ADB since the beginning and have uploaded

many things to it which work, just haven't been able to get it rooted. Is the ADB connection you're

mentioning at a later part in the root? Anyhow just give the word and point me to what to do and

I'll start testing for you on my V31 build! 8) Thank you!
[General Topics] mrmazak:
**WARNING***

I in NO WAY can be sure any of this will be safe. It is how I did my own ,but Y.M.M.V.

So what I am asking for is to see if

1. your bootloader is unlocked - previously confirmed boot loader will unlock

A. developer options, enable oem unlock

B. do "adb reboot fastboot"

C. do "fastboot flashing unlock"

D. confirm unlock command by pressing volume up. (message on phone screen)

E. Unplug usb , reboot tablet (fastboot reboot might work, if not long press power button)

Should see warning message and a 30 second countdown sreen, this will happen at every boot up after

unlocking boot loader. This first time rebooting should see android / stock recovery doing factory reset.

2. try to "boot"the cwm recovery. (even on tablet that this root method does work for the cwm recovery can only be booted, it does not install to local internal storage)

A. boot to fastboot mode. = "adb reboot fastboot"

B. "fastboot boot rca-recovery-cwm-ramdisk.img"

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] MENTD:
RE:

mrmazak: Developer mode has been enabled since I first started messing with the tablet.

Under developer options, I've also had OEM unlocking enabled since the beginning as well. 8)

I did: "adb reboot fastboot".

Device reboots to black screen.

I then entered: "fastboot flashing unlock"

... And got stuck at that part. 8( Here's what happens:

H:\RCT6873W42\adb-setup-1.4.3\adb>fastboot.exe flashing unlock

...

(bootloader) Please confirm the device state action using the UI.

(bootloader) got key event 4

(bootloader) EV_POWER received

FAILED (remote: couldn't change state!)

finished. total time: 1.969s

H:\RCT6873W42\adb-setup-1.4.3\adb>

At this point, I can't send any more fastboot commands and when I reboot, it just comes up

as normal, there is no warning message/30 sec contdown but I suppose that's to be expected

as the "fastboot flashing unlock" command is not working.
[General Topics] mrmazak:
This sounded familiar ,so i went back and re-read this forum. The first user with a V31 version was having same problem unlocking boot loader. He said that when he took sd card out , that the volume keys worked and he was able to unlock bootloader.'

its on page one of thread if you want to review it first.and try
[General Topics] mrmazak:
Yeah. You bricked it

Not supposed to flash any thing
[General Topics] MENTD:
Well, the initial documentation says to flash but it isn't the one I was supposed to follow.

I dunno how I screwed up ! Damn! I was just so excited when I got the damn thing to unlock I

had the original txt up and I started reading from that instead, thinking it was your instructions. 8(

ANYHOW - As I mentioned, ADB works. I can talk to it with ADB, I can generate a new key...

But I can't do anything else really as it keeps saying "$ADB_VENDOR_KEYS is not set".

Is this an environment variable within the tablet? Is there any way to set it?

As I said, I can use adb keygen <filename> and it will produce new keys.

Just grasping at straws... Obviously, something is there else I wouldn't be able to adb into it.

Are you positive it's bricked and unfixable?
[General Topics] mrmazak:
Not 100% sure but so far nobody else has done it.

But with no known way to authorize adb .....
[General Topics] MENTD:
IC, so there's no way to set vendor keys? Well, I'm sorry I messed up! I can't believe I made such a bonehead move!

I will keep watching to see if any progress is made and I'll put my bricked unit on a shelf somewhere to collect dust. 8(

Thankyou for all the help.
[General Topics] THCJunkified:
Unlocks just fine on my tablet's build but the images would certainly brick it. After test booting the permissive boot image I get the unlocked warning followed by a blank screen with back light.

It does boot but the screen remains black with the back light on, power cycling returns the tablet to usable, good call on the test boot portion of the instructions. Saved me a brick at least :D

To inform you and others with the same build # that this currently does not work and flashing would brick your device.

The build of my tab is: RCT6873W42-ANDROID6.0-V31-V1.17.80-W04
[General Topics] mrmazak:
I added the build number to the not working list in OP.

I do not have this in the directions on op but, you can test boot the recovery image the same way. The CWM recovery never works when flashed it only works when booted.
[General Topics] kal250:
Has anyone tried anything with the current RCT6973W43 models... Local Wal-Mart has a whole mess of these clearanced out for $25.00. Have not done a ton of research but for that price I can think of a few happy toddlers I know. Plus I can experiment with interfacing android auto to my $20 bluetooth car stereo from wally world.... It hurts to be as cheap as I try to be....
[General Topics] mrmazak:
I have not, but for 20 bucks might be a short project to keep my A.D.D. focused
[General Topics] kal250:
I may take you up on that, I bought one last night, have not had time to turn it on, so not sure what I'm going to do yet, my 4 year old was with me so she already assumes it's hers :p
[General Topics] jmacie:
I got bricked flashing on step 2. That was my bad. I got anxious, like a few other early adopters, didn't see the warning cause I went to the gethub to copy/paste and didn't see the boot before flash step 2a.. I wonder, when you brick ,and the pc still sees your internal storage, your cmd prompt sees the tablet, although unauthorized, what does that mean? How can the pc see the internal storage and sd card if it's bricked/soft bricked? I might try to get another, it was handy for bluetooth. Thanks for the root potential anyway. Wish it was a reversable problem...
[General Topics] mrmazak:
THAT IS UNFORTUNATE.

I do have a warning on the op to check build number, before continuing.

I have made the warning bigger now. And updated the github directions
[General Topics] Xsavi:
I removed the Google app because I got annoyed of it always popping up when I did not trigger it.

Now, it's sort of in a boot loop. It starts up all the way (optimising apps), then goes back to the boot animation. I tried the recovery method, but ADB wouldn't detect it. I don't think there's anything else I can do. I'm going to see if I can get into Fastboot with a button combination. I just need to reinstall the Google app.

EDIT: I just need to find a way to get to fastboot.

Question: Can you flash GApps from the stock recovery (modified) if you remount ADB? I'm thinking it's the same case as CWM. I'm going to try all this out when I get home.
[General Topics] jmacie:
Still wanna know how a bricked/softbricked device when connected to pc, is in pc's device manager, is seen as unauthorised in adb devices in cmd prompt, and you can see the internal storage . This is going to bug me til I understand that
[General Topics] hauckk@sfreserves.org:
Deleted wrong thread
[General Topics] Xsavi:
Okay, so I fixed my issue I had. What I did was:

1. Boot to stock recovery, so I can have basic access to ADB.

2. Used ADB to boot into fastboot.

3. Used the fastboot boot command to boot the recovery image.

4. Flashed Open GApps (Pico)

5. Powered off the device, then boot into stock recovery again to do the factory reset.

After that it booted into Android fully. I think the problem was the use of a conflicting app (Titanium Backup) to uninstall the Google App.

The button combination to access fastboot does not work (Power + VolDown). It boots normally.
[General Topics] Gracie1985:
will this work for RCT6873W42KC -Android6.0-V37-V1.15.30
[General Topics] mrmazak:
I don't think so.

this root "as is" only worked on "-V19-" builds

But if the cwm recovery boots (even if only to a blank screen) it should have the ability to pull the boot.img and make a root package that might work.
[General Topics] SoundZombie:
Has there been any progress on the RCT6873W42-ANDROID6.0-V31-V1.17.80-W04 build? I've been checking the other thread for months and was so excited to see root was attained, but sadly my firmware build was one of the ones that didn't work.
[General Topics] mrmazak:
the only way for development to move forward here is for someone with that build to try. I cannot do anything on my end without that build , or files pulled from that build.

Three times now i thought someone was able to to try, but all have made mistakes and bricked there tabs because they did not read all instructions.
[General Topics] SoundZombie:
Well what do you need? I have that build and while I am out of the game, I'm sure I know how to read directions.
[General Topics] mrmazak:
So far it seems like each software version out can be bootloader unlocked. The question that hasn't been answered yet is: if once the bootloader has been unlocked, will it Boot into the custom CWM recovery.

it is basicly two comands to see if it works.

"fastboot flashing unlock" == to unlock the bootloader. There are few steps to prepare for this.

1. need adb and fastboot for pc.

2. need adb and fastboot drivers

3. need to enable adb debugging in developer settings

4. then need to reboot to fastboot mode "adb reboot fastboot"

5. now the "fastboot flashing unlock"

6. this will pop up a message on tablet screen. press volume up to allow.

7. now reboot "fastboot reboot"

Unplug tablet and let it do its countdown warning timer. It may need to reboot 2-3 times.

Tablet supposed to reboot to recovery and do full factory reset. (erases all data so save and pictures and files before)

After done resetting, enable developer options again. enable usb debugging

then try to boot into CWM

1. "adb reboot fastboot"

2. "fastboot boot c:\Users\*\Downloads\rca-recovery-cwm-ramdisk.img" replace with actual path to your downloaded recovery location

once the tablet has been booted to recovery DO NOT TRY TO USE ANY BACKUP OR FLASH OPERATION

the idea here is only to be able to get a root adb shell in order copy the boot.img from your tablet to try make root.
[General Topics] SoundZombie:
Lost me after I boot into CWM. How do copy the boot img from the device? I assume an adb command but I've never used adb so I need a little more information before I try anything. Sorry for being adb stupid. haha
[General Topics] mrmazak:
Yes copying boot image will be done with adb shell with "dd" command.

Will need micro SD card to copy to , because will not be able to use the /data partition on tablet for this , due to it is encrypted.

Posted commands on an earlier post. Here is link.

Just do not do the boot boot.img part.

https://xdaforums.com/showpost.php?p=71771134&postcount=46
[General Topics] SoundZombie:
I'll start the process once I can get to a Windows machine and the stuff is downloaded. Will update.
[General Topics] lgally80:
I have two RCA Voyager III's not yet mentioned.

Hey guys, I'm going to see this project through til the end. The RCA Voyager III is a little weak in the knees performance-wise however at the $35 and less price range it sells for here, it has incredible potential. Attached are images containing in depth hard/firm/software details about my device, and a .pdf file created with DroidInfo. It is not on either of the OP lists, but for sake of public safety please add it to the "do not try" list. I will be poking around my 2 Voyagers dilligently and will update when I move forward, or have a release, may the best man (or woman :P) win! :highfive:
[General Topics] mrmazak:
sounds good. Wish you luck. and waiting to see update.
[General Topics] ezdi:
RCT6873W42-ANDROID6.0-V31-V1.17.30-W03 reporting in...

I have images of all partitions (except data). Unfortunately I don't seem to be able to do any further testing unless it's in an adb sideload/update.zip format. I can throw it up on a google drive if someone convinces me they can do something useful with it.

----- Story:

After fastboot unlock, I IMMEDIATELY booted into CWM (nothing flashed). The screen was blank, but I had ADB root. I copied all the partitions except data, which wasn't mountable anyway (encrypted? clobbered by the unlock?). On reboot, stock recovery did the reset and the tablet seems to work fine, but I can't get into the bootloader any more...

adb reboot bootloader now functions as a regular reboot. Maybe that was happening before unlock though, and I had to use a button combination. I got into fastboot originally before leaving for several hours and didn't bother remembering how I got in. Now pwr+volUp gives stock recovery, pwr+volDn is stock recovery or normal boot depending on when/how long the buttons are held, and pwr+both vol buttons is stock recovery. All of those flash the regular splash screen, and then the unlock warning (briefly with a 5 second countdown, which changes to 30 on cold boots). VolDn will not power off during the countdown. If I have it in charging mode and power on or reboot from recovery while holding volDn, it's just the 5 second countdown. Releasing volDn changes it to 30.