yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] SkyLo420:
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
[General Questions and Answers] pr3dicament:
That's exactly why I said you cannot unlock the boot loader.. that's the only way to do it unless you use some dev's app around here that types the same command and tries no matter what.

Regarding it being rooted.. I've been trying for months now.. I'm actually trying again after giving up for a lil' bit.. SRSRoot said they picked it up but that just says it roots and then reboots.. and I see no sign of superuser/supersu or any sort of system apk to manage it, even if the damn app says "unmounting /system" and "remounting /system, rebooting.. Root success!" ... yeah even after that, I saw nothing when it booted back up. Tried Kingo only God knows how many times.. even tried other little exploits, tried to manually root it but unless you have r/w access to /system, which a custom recovery can give.. it won't happen unless someone literally takes what's on the RCA and they more or less just have a pre-rooted stock rom to start.. 5.0.1, whichever.. I haven't done any updates and I'm not gonna try. I'm gonna going to try and cycle through six-seven more times before I just eventually give up. I'm sure something will come along eventually, but right now I'm not getting ****, and not being able to unlock the boot loader isn't much of a help. I can't even load MTK Droid Tools with this, yet, it's got the same 8127 chipset as a rooted Lenovo that I have (running KitKat 4.4.2) .. i was able to install PhilZ with that.. but the boot loader is still locked.. I didn't even try to unlock it.. it's just like how FlashFire operates.. stay in Android but mount only what needs to be mounted.

If anyone see's something that really does root this thing or has a damn /system partition that they can friggin' send to someone (I'd be happy to at least try) to wipe everything and install a custom rom.. I don't know. I'd rather just manually root and then have this as a backup. This is what makes me regret grabbing some RCA even if it was 40 bucks with a keyboard. Useless without superuser permissions.

---------- Post added at 10:38 AM ---------- Previous post was at 10:33 AM ----------

Oh, and um.. Wondershare just adds a service.. at least under Windows 7 x64.. it's easy to remove so I'm not really worried and.. honestly.. I don't see a correlation between dead pixels and software unless it's immediate impact.
[General Questions and Answers] pr3dicament:
Still no dice with Wondershare, but it does do exactly as you said.. I'm wondering if you were thinking of the correct model and OS. This specific model never had KitKat (4.4.x) for it.. it's 5.0.1 only. Some people mistake this model for the other one with the same NAME but one different thing.. at the end of the model number, the ones that have actually a possibility of being rooted... they have a 22 at the end.

this is a 42. 42B. Now if he has that, then me trying this for the 12th time might have a shot at working. I might just do a factory reset.. like... as it was out of box.. aside from enabling USB debugging mode. I might try a few different drivers as well. It just fails and fails and fails and you know what it suggests to "manually" root? It recommends SuperOneClick which is no longer even used unless you have a really old device..

lol. I'll update you guys if I somehow find something. I'll try all the one-click tools a try but SuperOneClick? I actually have that in my archive but.. I don't really think it's necessary nowadays. If only I could get this damn boot loader unlocked.. I mean there's no way that they'll send anything anyway.. I'll try using MTK Droid Tools due to it having an MT8127 chipset.. every time it just says it can't load adb.. makes no sense to me. I have it installed system-wide with Environment Variables..

I know this thing can be rooted.. it's just gonna take longer, probably a year or more.. mostly because no one even gives a ****. I think it's pretty good if I just had the su binary in /system actually there, even temporarily.. I could easily make it permanent if we have even a glimmer of it for just a few minutes.. that's all I'd need. I'm not a dev but I know my way if I'm given at least SOME time.. Just run an sudaemon and what happens is you can actually remove what's considered "root" regarding the app.. this is actually well-instructed in a post that has to do with removing KingRoot and putting SuperSU on it to replace it. .. and I'm not talking about SuperSUme.. I mean it takes a little bit of knowledge... but not that much.
[General Questions and Answers] pr3dicament:
For the record.. Most don't care about a 30 dollar device with a damn keyboard unless they're literally sitting at a Command Line or using ADB for transfers etc instead of copy/paste. The reason that KitKat/4.4 works here is simple.. It doesn't have any way to patch PIE unless you're rooted already or if you've somehow got your tablet looked at as another device for unlocking the boot loader.. and I do remember, one time, I saw this first install the driver for an HTC One..

it's just an idea.. I'm not responsible if you **** anything up for your tablet. If you don't need root, then just don't worry about it or keep using stuff. PIE just stands for Position Integrated Executable.. and the error it gives every single 5.0+ tablet that has barely anybody looking at it.. well, that's why they're not working.. it literally gives the message when you attempt to root it manually.. "error: only position independent executables (PIE) are supported." ... now there are plenty of threads on here with this and ways to "bypass" it.. hell they even have something called "patch-pie" to flash in a custom recovery.. not the manufacturer. So if you somehow unlock the boot loader and you know what to put on it.. Then you're in. That's usually what happens here.. the methods are fine, they all work, it's just some firmware isn't ever really looked at with brands that have barely any purpose. Most of these types of tablets run 4.4.x on there and that gives them no errors... so it's really easy to root it if you get past it. I've seen it in SRS root right before my eyes and even doing so when trying other things not root-related in adb. Fix that and you'll be able to do it.
[General Questions and Answers] pr3dicament:
Disclaimer: If anything happens to any of your devices as a result of anything in this entire thread, post, or even the links from this entire thread and entire post.. doesn't fall on me, not my fault. If your wife or side girlfriend decides unlocking the boot loader with a hammer, I'm very sorry, but it is not of my doing. This is all for testing purposes. That being said.. I don't see how you screw this up. Don't try to unlock the bootloader, by the way. It's not happening.

The latest KingRoot works. I did a Factory reset prior, I had no clue it'd actually work. just.. clear cache and dalvik basically, install this:

http://xdaforums.com/devdb/project/dl/?id=18893

xda approved obviously... after that, either use Super-SUME or the following guide to remove and replace KingRoot. It's originally made for some Amazon Fire phone but the whole thing is perfect to replace KingRoot and furthermore the correct binaries; At times it'll say it's an incorrect command or that something does not exist.. don't worry about it. It's Ancient but works just fine.. I did this just two days ago. Copy/Paste it line by line, not all at once... or make a script. up to you:

http://xdaforums.com/fire-phone/general/root-fire-phone-supersu-t3105546
[General Questions and Answers] Bekel:
Need Custom Rom for custom rom rct6773w42b

Please where can I found a Custom Rom for RCA tablet 16 GB rct6773w42b, is bricked software for repair this.

Thank in Advance.

Bekel
[General Questions and Answers] electech_poc:
Anyone have the original rom file? I did a factory reset in recovery and it keeps boot looping back to recovery. Would like to update via sd card option or adb. Please Help!!! I couldn't find anything online, it is the RCT6773W42B.
[General Questions and Answers] ssand1984xx:
hey guys my bf found a way to unloclk the bootloader...once in recovery screen...when prompted ...go to bootloader but use the physical keys up/down and press enter to get it to work. volume keys dont work and it works . mines unlocked...just trying to find root solution now,. help??
[General Questions and Answers] MotoJunkie01:
Bootloader unlocked, full systemless root attained by using Kingoroot PC Version, SuperSU Me Pro to replace the Chinese binaries with proper SuperSU binaries. SuperSU 2.79-R3 installed on Android 6.0.1 Stock ROM. Bootloader is not encrypted. Only requires OEM Unlocking enabled in Developer options, connected to PC with micro USB syncing cable, rebooted into AP Fastboot Mode. Minimal ADB & Fastboot needs to be installed on PC (or the full Android SDK). Open a command prompt in the adb/Fastboot directory if using minimal adb & fastboot and simply type fastboot oem unlock and watch tablet screen for a prompt using the Volume buttons. Contrary to earlier statements this tablet is fully root ready out of the box, and bootloader is definitely not encrypted. Currently working on a TWRP port for this device as well as a deodexed and debloated stock ROM preinjected with root binaries, and optional insecure boot.img with init'd support running stock.
[General Questions and Answers] jakfish:
What wonderful work! And many thanks for your efforts. Do you think that your instructions and future ROMs would work with the RCT6873W42KC?

For more reference: https://www.amazon.com/gp/product/B01M7TSY16/ref=od_aui_detailpages00?ie=UTF8&psc=1

Well, well done,

Jake
[General Questions and Answers] MotoJunkie01:
Well, my objective is to modify a stock ROM that can be flashed on any RCA Voyager 7" variant running either Lollipop or Marshmallow. This includes the Voyager, Voyager II and the Voyager Pro. I would like to be able to offer both 5.1 and 6.0.1 ROMs. As long as the filesystem does not in anyway forbid a downgrade in firmware or OS, users running Marshmallow Builds would be able -- with an unlocked bootloader of course -- to flash either a Lollipop or Marshmallow Deodexed, Rooted, & Debloated Stock ROM. A Lollipop OS would offer the advantage of a System-Based Root versus the Systemless method required on the 6.x.x Builds.
[General Questions and Answers] Jinrandroid:
Use KingRoot Worked for mine. Looking for custom ROMs
[General Questions and Answers] MotoJunkie01:
That's great. What version Android were you running? Unfortunately custom ROMs seem nonexistent for this device. A ported CM build would be great. I'm capable of several aspects but I'd need help.
[General Questions and Answers] jakfish:
Without a stock rom available (I live-chatted with RCA and they said they hadn't released any), I'm hesitant to use MotoJunkie01's method since MotoJunkie01's machine is slightly different than mine (mine = RCT6873W42KC, though I have Marshmallow as well) and with no rom to fall back on...

Would love to hook up my usb modem via ppp widget.

Jake
[General Questions and Answers] MotoJunkie01:
Which Stock image do you need? Provide me with your exact version and build and I should be able to accommodate you.
[General Questions and Answers] jakfish:
What a kind offer and I would like to make a donation to you. Could you please pm your paypal email or address for check sending or any other way that works for you?

As for the specs:

1) RCA Voyager Pro

2) Model number: RCT6873W42M

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

One slightly confusing difference on Model number. In "About tablet," the model number is RCT6873W42M

But on the Amazon specs of my purchase, it reads: RCT6873W42KC M

I don't know if that discrepancy makes a difference in your calculations.

Again, this is a very generous offer and let me know about the donation and any other device information,

Jake
[General Questions and Answers] MotoJunkie01:
I find it very unsupportive that RCA does not offer firmware downloads for their line of tablets. Like you, I have went so far as to call customer support with the same question. There is an XDA thread that offers a couple of pre-rooted stock ROMs for a couple of the early releases of the RCA Voyager 7" tablet, along with a TWRP custom recovery, scatter files and the flashing tool itself. Unfortunately there has been little development for the newer versions of the Voyager. And I can certainly understand the rationale there. It is not like there is a shortage of 7" tablets running MediaTek processors. But there are a handful of us that would like to see some development for this --in my opinion -- better than average 7" budget tablet. And like you I am a bit perplexed with respect to the variations and alphanumeric addendums to some of these model numbers. For example, the RCT6873w42m would seem to indicate by its "m" suffix that the device was released with the "Marshmallow" OS. What might the "KC" denote in variants we see with those letters? You raise an excellent point in terms of these model numbers, and the question if which builds would be compatible with which models. I recall the initial release of the Voyager 7", which shipped with Android 4.4.2 if I am not mistaken. Then there was Voyager II, which shipped with Android 5.0 Lollipop. More recently, we saw release of the Voyager Pro, with 16GB internal storage and running the Android 6.0.1 Marshmallow OS. A few days ago, at Walmart I purchased a basic RCA Voyager for $35 which greatly resembles the original release, except mine is running Marshmallow OS and now has 16GB storage like the Pro variant. So in reality there seems to be possibly several variants of this tablet. Over the next couple of days I will make a dump of the Stock Marshmallow OS on my device discussed earlier in this thread and compile a debloated and rooted fastboot flashable ROM. I'm also going to research these variants a bit more to get a better knowledge of build compatibility along the Voyager variants. I deeply appreciate your offer of a donation. I would first like to ensure that what I am compiling will be compatible with minimal risk to your device. Thank you.
[General Questions and Answers] jakfish:
I'm ready to test whenever you are.

I was wondering if KC has something to do with the keyboard, but I can't be certain.

Please let me if you need any more information.

Jake
[General Questions and Answers] MotoJunkie01:
That's probably it ....perhaps KC is the nomenclature denoting that the device includes the folio/keyboard unit.
[General Questions and Answers] Jinrandroid:
Let me clarify it worked then didn't so I need to find another app can u help
[General Questions and Answers] ssand1984xx:
Any movement on rooting it and finding.a custom recovery?
[General Questions and Answers] MotoJunkie01:
I'm using TWRP's Easy Magic to compile a custom recovery. The problem faced with this tablet, like so many other tablets of today is the potluck nature of hardware variances among the same model number. My RCA Voyager Pro may have a MediaTek board platform, while your tablet may have an Intel under the hood. On a positive note, however, at least the bootloader in these tablets is not encrypted (at least not on the variances seen so far.)
[General Questions and Answers] ssand1984xx:
i attached my specs for my tablet let me know if similar mybe we can work together
[General Questions and Answers] MotoJunkie01:
As luck would have it, your specs are identical to my newest RCA Voyager Pro. I think working together on this would be a good idea, especially since you and I both own the same variant of this device.
[General Questions and Answers] ssand1984xx:
ok so faar on it ive got the bootloader unlocked and now looking to see what rooting process is best.
[General Questions and Answers] jakfish:
I'm not as versed in these things as you folk are, but I've got the exact same Voyager as yours, and I'm certainly willing to test and confirm. As of yesterday, my bootloader is unlocked.

Jake
[General Questions and Answers] MotoJunkie01:
The best avenue to root this device is simply to flash the SuperSU V2.79 binary script from recovery. Of course, with signature verification in stock recovery, this isn't an option. I saw in another thread that the guys working on development for the Intel variant of this tablet unlocked their bootloader, decompiled stock boot and stock recovery, recompiled an insecure boot image, reflashed them, and flashed SuperSU via stock recovery. We can do the same I'm pretty certain.
[General Questions and Answers] icaruspony:
I guess no one in this thread has the abilities to match what was done in the other version's thread?
[General Questions and Answers] MotoJunkie01:
Currently trying some TWRP builds for this tablet. Once a working TWRP build is implemented, systemless root will be attainable.
[General Questions and Answers] icaruspony:
I know my way around ADB and fastboot, but not for modifying recovery or boot images.
[General Questions and Answers] MotoJunkie01:
Since this tablet is equipped with the MediaTek mt8127, there are several devices with the same board platform that have fully functional TWRP recoveries. I'm currently experimenting with TWRP builds from similar devices to try and find one that will work.
[General Questions and Answers] jakfish:
Our breath is bated :)

Jake
[General Questions and Answers] MotoJunkie01:
Update -- I've had little luck in finding a TWRP recovery for this device that will actually boot. I've now changed strategies and using the Dirty Cow exploit to attain temp root, with which I can flash the SuperSU systemless root script to further a full superuser environment on the OS. Once an ADB shell is present, I can use a TWRP compilation utility to create a fully functional TWRP recovery.
[General Questions and Answers] jakfish:
Sounds promising, and also complicated. Good luck and thanks for the update.

Jake
[General Questions and Answers] MotoJunkie01:
Thank you for the encouragement. It isn't that the procedure is complicated, but it is certainly progressive, with each step depending solely on the step preceding. Dirty Cow has yielded great results on virtually all types of devices which have an Android Security Patch Level before 01/01/2017, on Android 6.0.1 and earlier versions. Temp root is all I'm hoping for initially, but that will pave the way for full superuser access.
[General Questions and Answers] MotoJunkie01:
Great work . ..

I have gained temp root of the device using ADB to push the Dirty Cow exploit files. Now, using ADB Shell, I'm using TWRP Easy Magic to try and compile & flash a working custom recovery.
[General Questions and Answers] Machine Improvement:
That is completely excellent news. I'm willing to arrange a donation on your behalf if you could let me know where to send it.

As it happens, I have a second identical RCT6873W42KC, never opened. Your TWRP port, once uploaded, would help me extract a completely pristine stock ROM. I imagine such would be useful for device returns and resale. Since new members can't upload files, is there another way I could get this file to you once the TWRP port is completed?
[General Questions and Answers] icaruspony:
Is this now dead?
[General Questions and Answers] SkyLo420:
I gained root once, I could probly do it again. I used one of the PC versions of king or kingo or oneclickroot, can't remember which one. Root checker said that it was rooted but the problem was that when I rebooted. It then wasn't rooted. Probably means it wasn't ever rooted, or temporary root. Idk I gave up.
[General Questions and Answers] TrevaG:
Please help with RCT6773W42B

I don't understand how to do the above. My daughter is crying because her tablet stuck on this recovery mode menu. I contacted RCA who will do nothing because I don't have a receipt (tablet was a gift) and there is no S/N on the actual device. Can you provide instructions in layman's terms, lol, or do you provide a service to fix it? I would be happy to make a donation.
[General Questions and Answers] MotoJunkie01:
There are several variants of this tablet I have come to learn. From your recovery menu, which model number is listed?
[General Questions and Answers] TrevaG:
Model

This is the model number at the top of the menu: RCT6773W42B-ANDROID5.0-V19-V1.12.50-KC-B

Thanks
[General Questions and Answers] MotoJunkie01:
Yet another variant it seems. Yours seems to have Android 5.0 Lollipop from the "ANDROID5.0" portion of your model number. Is this accurate?
[General Questions and Answers] TrevaG:
Lollipop

Yessir, you are correct. :good:
[General Questions and Answers] MotoJunkie01:
I will see if I can find any resources to help you recover your devuce. My device is a different model from yours and runs on 6.0 Marshmallow. However, I may know of some resources which can help. I will see what I can find for you this evening.

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

I no longer have my model Voyager like yours.
[General Questions and Answers] MotoJunkie01:
Have you seen this thread? https://xdaforums.com/general/general/stock-rom-twrp-root-oc-uv-rca-7-voyager-t3087075
[General Questions and Answers] godkingofcanada:
I got my hands on one of these cheap and bootlooped it. but since its nothing like any of my moto or Samsung droids I cant just flash the stock rom and revive it.... I'm kind of annoyed lol. rct6873w42m-android6.0-v37-v2.15.50 is the version that I'm running with recover v1.2, are you still around moto? do you have the stock marshmallow rom for this?
[General Questions and Answers] Azazel82:
Have achieved soft root with at least 2 apps on the Voyager Pro RCT6773W42B

. Kingroot version 5.0.1 and few older versions of the app and also using iRoot and believe the latest version of that one. Will reboot and you manually have to go back to Kingroot when the device reboots and will start ya off in the same place ya was when it rebooted. The WEIRD thing to me is will never get to 100% in the rooting cycle but instead I believe it said "Root Failed" at 85% but will still have root untill you reboot again which it apparently really likes to do anyway lol and no RW permissions or fully deleting any system apps but can use the Kingroot app uninstaller to basically freeze any apps or maybe does actually uninstall untill a reboot but that's as good as it gets though without a PC anyway.
[General Questions and Answers] daniboi99:
hello someone can help me
[General Questions and Answers] daniboi99:
3 years later...... i need some help 1 have 2 tablets like those buet another version

mine is ...RCT6873W42BMF8 ANDROID8 1-V15-V1.20.0-A02

Is there someone there can help me??, can yours contact me by email o telegram @daniboi99

thanks a lot
[Galaxy S III Q&A, Help & Troubleshooting] jkmg19:
Hello

Im having a hard time finding a ROM for my samsung galaxy s3 gt-i9300 in the Philippines. I have tried changing the CSC(ph csc) but still the phone can't read my simcard,nothing at all. So I downgrade my rom. I am currently using android version 4.0.4 "Icecream" because this is the only rom I found that works on my country (PH) from this site. By the way im using Odin to upgrade and also using a Globe Carrier.

Please help me find a good working rom (os) and network for my phone in my country

P.S. Please post the link below :) Thank you inadvance

- THANKS PROBLEM SOLVE