yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] mrmazak:
First way I tried to use this was just like last time. Opened the img and used just the

ramdisk/sbin

And

ramdisk/twres

The result was diagonal lines on screen.

Maybe I'll take a step back and try it as is.

.. well as is it hangs on the RCA splash screen but allows adb as root from there.

I think that means I need my tablets kernel for display, and the that the swap may have caused the lines. I dont know.

... i need to keep going....
[General Questions and Answers] vampirefo:
I just switched your kernel and it still boots just fine for me on my device.
[General Questions and Answers] mrmazak:
.

.

I can get the screen to show one time.

when recovery boots I get the diagonal lines like I posted screenshot of. Then I command "adb shell /sbin/recovery" I get a stable screen . When I touch the screen , before I can tell if it was the expected touch point, the screen gets scrambled again. Now if I repeat the /sbin/recovery command it no longer recovers the display.

I don't know what else to do.
[General Questions and Answers] vampirefo:
upload the recovery you have let me see if I get figure it out.

---------- Post added at 02:07 AM ---------- Previous post was at 01:54 AM ----------

it sounds like to me you aren't replacing the second kernel it's called "recovery.img-second", this is the kernel that must be replaced, the first kernel isn't important "recovery.img-kernel" it's the same as mine.
[General Questions and Answers] mrmazak:
This is latest combination of files. Still same situation.

but I can sometimes toggle between normal screen and scrambled.

by tapping around the screen

I do see that the X Y swap sort of worked. It now shows that Y is also flipped. So now the side to side position of the touches is correct , But if I need to tap a button that 2 inches from the top I need to tap 2 inches from the bottom , to activate that button.

1. the second kernel from the rca tablet

2. /etc/recovery.fstab

3. fstab.zram from rca
[General Questions and Answers] vampirefo:
Ok, I flashed this recovery just got blank screen after intel splash screen, replaced only recovery.img-second and now it works as it should, touch is off of course.

I can't see a problem on my end, the only difference is recovery.img-second, which is the second kernel, it boots the recovery gui, using your recovery.img-second screen is blank using my own recovery.img-second gui is fine.
[General Questions and Answers] mrmazak:
Thanks.

I am using the second.img from recovery. Can I or should I use the one from android? i mean from "boot.img-second"

Ok using the boot.img-second did not help and didn't seem to hurt-- But using the boot.img-second did make twrp show the initial screen asking to swipe to allow modification to system. Using the original recovery.img-second did not give this screen.
[General Questions and Answers] vampirefo:
They should be the same, Mine are, I can't think of any reason they would be different.
[General Questions and Answers] mrmazak:
the ones from this rca are different.

The one from boot.img is almost double in size

If it is not too much to ask. Can you add both these build flags and build one more time. I think you did the one, already but still think it needs the second one added.

RECOVERY_TOUCHSCREEN_SWAP_XY := true

RECOVERY_TOUCHSCREEN_FLIP_Y := true
[General Questions and Answers] vampirefo:
hopefully it works as is.

https://www.androidfilehost.com/?fid=529152257862711743
[General Questions and Answers] mrmazak:
I think the touches are correct.

Based on:: I remember the info button was bottom right and if i touch bottom right i can tell the screen changes. But some reason adb would not connect.

and counld not relaunch with "adb shell /sbin/recovery" to get it into readable screen

ok I hacked it together with the the x y swap version and got adb back. At the least I noticed this newest one was missing the service to set permissive in the init.rc. the script was in the /sbin but not being imported

Being able to reload the recovery process I can confirm that touches are now matched up. I started a backup and the screen started out stable, then a few minutes in, it started "flickering" again.

Can it be a CPU limit issue or similar, running out of ram (unreasonable cap set by mfg to restrict custom recovery) or is that too much of a paranoid idea.?
[General Questions and Answers] vampirefo:
No ideal, my tablet has no problem backing up or restoring.

Your tablet has some limitation, does it do the same in CWM?
[General Questions and Answers] mrmazak:
I don't know if there is some limit I was just trying to "fill the whole" of not knowing why the screen does not render twrp now.

You know if I had to describe the way the screen is acting, it is reminding me of the way a TV will display diagonal "scamble" when it is set to "pal" instead of "ntsc"
[General Questions and Answers] vampirefo:
I don't know, the goal was to root the tablet, the tablet is rooted.

Anyway time to get back to my Max.
[General Questions and Answers] mrmazak:
thank you very much for that. Yes root was the goal.

Is there any work done on the max?

I was gonna order one.
[General Questions and Answers] vampirefo:
http://www.needrom.com/author/vampirefo/

I just got done uploading another rom for Max.

Life Max GPLUS F51 Port
[General Questions and Answers] icaruspony:
Wiki

Thanks to everyone who created root for this device.

This thread was kind of all over the place.

Could somebody please write a wiki with the steps/files to root this for those of us starting fresh from scratch?
[General Questions and Answers] mrmazak:
I did file compare between the X Y swap and Y flip versions of twrp that [MENTION=2472806]vampirefo[/MENTION] has built for this RCA. I found the file that is responsible for controlling the alignment (orientation) of the touchscreen.

I changed just that one file and made the X Y swap version have same touch points as the Y flip version.

/ramdisk/sbin/libminuitwrp.so

I did the obvious simple test, of placing that file into the older recovery that has normal working (rotated) screen. And it stopped the recovery from booting. But maybe with some more digging I can uncover why the current build makes screen scramble or merge the change in orientation into the older recovery.

..... edit:

,,, No luck with merging into older TWRP "libminuitwrp.so"completely different
[General Questions and Answers] Plasmastar:
Yes please. I have been following the thread from the very start, but it isn't very easy to distinguish what steps were used to produce what results. A tutorial or guide would be very much appreciated, if the goal of rooting the tablet has been achieved.
[General Questions and Answers] mrmazak:
I have put out a "tool" that will do the following

1: unlock bootloader

2: flash a modified stock style recovery needed in case problems (I have near bricked few times testing and this step was very necessary)

3: flash a modified boot.img that does not force encrypt the device (needed as the partly working recovery did not properly decrypt device when encrypted)

4: boot into a working version of CWM where you can (should) make a backup. (restoring is not straight forward process but works. I will need to make a write up for that too)

==>>LINK TO original TOOL

I will modify the tool to now flash the boot.img that is permissive. Once the permissive boot.img gets installed, you can boot into the CWM and install superSU.

just give me some time, I will get it modified soon.

you can also just download the original tool and replace the no-force-encrypt-recoveryboot.img in the /img folder with ==>>LINK permissive.boot . Rename the new image same as old one, or modify the script. Install boot.img with the "tool".

Then install the system mode superSU while in CWM

This is basicly the way I did it.

You can also use original tool as is . then follow Vampirefo's post and directions.

https://xdaforums.com/showpost.php?p=71460649&postcount=202 link to directions

https://xdaforums.com/showpost.php?p=71474679&postcount=212 link to corrected download

be aware unlocking bootloader needs to format the device. After unlocking bootloader device has a 30 second time out before booting, every time. Flashing from stock boot.img to modified non encrypted needs to format data also.

There is no button combination to boot into fastboot mode, so if problems occur need to boot into recovery to get access to adb and reboot to fastboot.
[General Questions and Answers] jakfish:
What incredible work and thank you for the latest post of clear instructions. Since there are so many sub-devices of the RCA Voyager Pro, I'd like to make certain that my device specs fit your software. I have the RCA Voyager Pro with accompanying keyboard:

1) Model number: RCT6873W42M

2) Android 6.0/Kernel ver. 3.18.22

3) Android security patch level: June 1, 2016

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

Are these specs close enough to yours?

Many thanks,

Jake
[General Questions and Answers] mrmazak:
I do not know. I think the biggest issue is the processor. RCA released same model number with an MTK processor and with an INTEL one.

this thread and these directions are for the INTEL version.

I think the M at the end of yours is the MTK version

I posted in another thread for that model and they have an easier method of root, I am looking for link now

here is one, but I recalled a longer thread , i'll keep looking

https://xdaforums.com/android/help/help-rooting-rca-voyager-tablet-model-t3515612

lol....thats so funny

I found the other thread i was looking for , and guess what. Your post was the one I was looking for.

https://xdaforums.com/general/help/help-rooting-rca-voyager-pro-t3275962/page3
[General Questions and Answers] jakfish:
Ah, I see. When I use DevCheck Pro, my Hardware reads: MediaTek MT8127. That would tie into what you're suggesting.

While it would appear the MTK version may be easier to root, I don't believe it has your neat trick of making a "modified stock style recovery."

Would it be safe to assume there is no clear way to make a stock ROM backup in case of a MTK post-root failure?

Jake
[General Questions and Answers] vampirefo:
You should install CPU-Z from playstore it will tell you what Soc you have, Intel or MediaTek
[General Questions and Answers] mrmazak:
i think mtk version might work with sp flash tool. It is a good tool that can image the device both ways, backup and flash
[General Questions and Answers] jakfish:
I didn't know that it was possible to backup a stock image. With my other Android devices--phones, etc--I was lucky to find an already-waiting way to root and a custom rom after that.

I'll explore sp flash tool right away.

Thanks,

Jake
[General Questions and Answers] Plasmastar:
I turned on "OEM Unlocking" and "USB Debugging", accepted authorization, ran mrmazak's Unlock tool, and it reboots it via ADB, but it is not finding anything with fastboot. What am I doing wrong?

Edit: Also, the OS (Windows 10) keeps flipping out and notifying me with sounds that mean "Device plugged in" "Device unplugged"

Edit: Apparently Windows isn't even recognizing the device in fastboot mode. Keeps flashing "Unknown Device" in device manager.
[General Questions and Answers] mrmazak:
The files on this site might not be correct but the directions on using sp flash are ok.

And it is a thread for an RCA tablet with (I think) same chip

https://xdaforums.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
[General Questions and Answers] mrmazak:
Yes that is what I get until you set the driver.
[General Questions and Answers] Plasmastar:
What driver? Where? Note: ADB DOES recognize this device, but FASTBOOT won't. I'm so confused.
[General Questions and Answers] mrmazak:
I thought it was discussed more in the beginning of this thread, but a search only showed really this one post

https://xdaforums.com/general/help/rca-voyager-rct6873w42-rooting-help-t3485625/post70208535
[General Questions and Answers] Plasmastar:
Thank you very much! I have Google's and Intel's USB Drivers installed, so I was confused about why it wasn't just, working out of the box. Had to slow myself down and read what's going on.
[General Questions and Answers] Plasmastar:
Currently not able to successfully root. Instructions need to be recompiled to be easier for less knowledgeable people to understand. I've unlocked the flasher, flashed the images mrmazak provided, then moved on to Vampirefo's directions. Problems start to arise at "setenforce 0" with some failure messages and not having permissions to push su.img to /data

Vamp's instructions also reference "recovery.img" and I had to guess that it was one of mrmazak's images. Also, using CWM to install the SuperSU zip did not seem to do anything at all.

As always. Help much appreciated.

---------- Post added at 01:18 AM ---------- Previous post was at 12:42 AM ----------

Looks like I've bricked it. It will only boot up to a black screen now.

"Recovery mode" A.K.A. Holding Volume Up + Power results in adb devices showing "unauthorized", meaning no booting into fastboot now.
[General Questions and Answers] dp35654@gmail.com:
What are the pros and cons root vs no root.I see some wanting no root.It seems to me but I don't really understand that if you're rooted you can't get your number released as easy? Because I was at the dollar store yesterday and they had smartphones​ for 20.00 and the most was like 39 but you had to get a plan like NET10 or TMobile in carrier so if it's rooted wouldn't a person have a heck of a time using this for a month and having a 600 phone to move?
[General Questions and Answers] mrmazak:
**

Alright. Details are important here.

Did you have tablet booted up into Android in-between all the steps?

Because each step except the recovery step needed to do formats.

If you did not boot in-between you might be able to do wipe from recovery , to revive.

And as long as recovery is booting the trick to get adb authorized is to select adb side load in recovery, then it tells you to send a file from "adb sideload *file-location*name*"

Choose a small file so it is quick, it will fail with message on tablet it failed and screen returns to normal recovery. And you will have adb access.

This is how it works for me. You may need to install my key , not sure, try that first.

---------- Post added at 07:09 AM ---------- Previous post was at 06:25 AM ----------

here are [MENTION=2472806]vampirefo[/MENTION] 's directions again , but I added numbers and notes.

!!!!Please!!!! If following a set of directions and first, second ...... steps fail , please, do not continue, there is something probably wrong and continuing may give undesired result.

must start with directions in this thread first to use this method

https://xdaforums.com/showpost.php?p=71452921&postcount=192for directions but img needed modified

https://xdaforums.com/showpost.php?p=71453760&postcount=195 has the modified image

once booted like above thread directions can continue below

files for method below are on this post https://xdaforums.com/showpost.php?p=71474679&postcount=212

****required before first step is to have booted fist permissive-boot.img****

1:adb shell

2:setenforce 0

3:adb remount

4:adb push su.img /data/su.img

5:adb reboot fastboot

6:fastboot boot rca-boot_permissive_on_boot.img

7:adb shell

8:getenforce

9:Your result should be Permissive *****If not this result do not continue****** if above adb push does not work,this step will not work

10:adb reboot fastboot

11:fastboot flash boot rca-boot_permissive_on_boot.img

12:fastboot boot recovery.img cwm recovery from mrmazak tool folder "img\rca-recovery-cwm-ramdisk.img"

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

14:reboot system

15:select NO

I have V3 ready. It will flash a permissive boot.img. When I did this I followed the install of my version of permissive boot with directly installing superSU in CWM.

Or you can go through the steps listed above. Your choose

==>>Unlock-TOOL_V3
[General Questions and Answers] vampirefo:
You aren't going to make phones calls on a rca tablet, anyway your question has been asked a million times.

Google pros and cons of rooting android, you will be able to read for months the responses.

To root or not to root is simply a personal choice.
[General Questions and Answers] icaruspony:
Can someone make a comprehensive step-by-step, from A to Z. It looks like the best we have is "do these threads first, then do this". Can me make a list that includes info from all threads compiled into one complete how-to?

Include how to first detect which processor you have, which drivers to install first, then go into what commands, reboots, etc?

It should be complete enough for someone to root the phone while having not read any other posts.
[General Questions and Answers] Plasmastar:
Your recovery images kept making the tablet boot up into black screens and one of them complained about bad font locales or something. Pressing Volume Up + Power literally does nothing now except bring up a black screen with an unauthorized ADB session.
[General Questions and Answers] mrmazak:
No, sorry but if you can't read 3 or 4 posts with the directions, what makes me think you will read one when I spend my time to cut and paste them together.

I know everybody is a noob at one point t bit if you need that level of hand holding to get it done, you will definitely break your device if it had root privileges.

---------- Post added at 01:11 PM ---------- Previous post was at 12:52 PM ----------

I am definitely confused over your situation

You already posted you finished the steps in the tool then started the next steps.

Which need adb access to start, so you must have had Android booted then, so my images did not cause your problem, there is some middle step you may be leaving out.

Besides the recovery image has nothing to do with device booting the boot image does.

Please try to be specific on what went where and what happened.
[General Questions and Answers] rpk3:
Newbies. I understand your frustration. Please don't be to direct to REQUEST mrmazak or vampirefo to set up a complete scripted apk OR TAR.Z package to help you root. If you have not been able to get the USB drivers to install its probably cause of the ESTO virus.

EQUIPMENT SMARTER THAN OPERATOR.

My pos winblows machine gave me issues for two weeks while trying to get my tablet to even see windows. Finally had to make my own .inf files to manually install the friggin driver. .... anyway. Yes. I bricked my ****. Like 2 times. Although was able to use the flash tool from Intel to load an OEM IMG file I accessed before I started to root the tablet with mrmazak's files.

Personally. I'm a Slackware man. Winxp and win7 for swap

I just wanted to use this tablet for a POV UAV purposes...although I think it needs another 1gb onboard ram. There are limits to what you can do with this tablet. Truthfully, been playing around with this tablet as interface for an old Garmin etrex for GPS viable access on a larger screen. Anything but google maps BS.

And yes... You can make calls from this tablet... as google hangouts has a micro PBX installed for this to happen. Although don't expect to receive calls. There is no way to tie into emei for access to make this happen.
[General Questions and Answers] vampirefo:
Yes, 2GB ram is really needed on any android, but 1GB, keeps people buying the next version. If it came with 2GB people would compile their own ROMs and use custom ROMs rather than buy the next upgraded RCA tablet.

These are cheap devices, same as the tablet I am typing on, good for web surfing, communication, few games, entertainment value.
[General Questions and Answers] mrmazak:
I admit, the directions are not complete, and hard to follow. I can see needing to document things better.

But to say you don't want to read any related posts and have an all in one click option is too much.

Besides that is the reason for the V3 unlock tool. It does 95% of the job for you.

But until I hear back from [MENTION=4786373]Plasmastar[/MENTION] on what happened to his tablet I don't want to release any updates to the tool until I can try prevent what ever happened there.

I have V4 almost ready.

It has a model check before opening, so if wrong model it should just close.

And I am including the SuperSU inside.

Just hung up on this line

adb shell recovery --update_package=/sdcard/0/Download/UPDATE-SuperSU-v2.79-SYSTEMMODE.zip

File gets pushed before hand and is present in the Download folder.

It starts the flash but stops with a message from recovery that it fails signature check. Then gives yes no option to continue anyway. When select yes it appears to continue but just hangs.

Can Anybody help?
[General Questions and Answers] Plasmastar:
I think I boned it when I got frustrated and tried to restore backups done with CWM. Restore seemed ok, but maybe it's because I forgot to wipe the partitions.

As for recovery, I followed this advice.

Using Volume Up+Power (which should be recovery mode) kept giving me black screens afterwards. I also don't know why CWM didn't restore the previous image.

I'm stuck with a device that boots with a 30 second timeout, black screen on normal boot (no adb), and black screen on recovery mode boot (adb, but no authorization)
[General Questions and Answers] mrmazak:
Yeah, that is a REAL big problem there.

I definitely made a typo.

You should never replace a recovery image with a boot image.

Sorry I have no advice for you. I need to find out from [MENTION=7931638]rpk3[/MENTION] , what flash tool he has. Because he said he restored his **** with it,

https://xdaforums.com/showpost.php?p=71513804&postcount=260

from above link

My pos winblows machine gave me issues for two weeks while trying to get my tablet to even see windows.
Finally had to make my own .inf files to manually install the friggin driver. .... anyway.
Yes. I bricked my ****. Like 2 times. Although was able to use the flash tool from Intel to load an
OEM IMG file I accessed before I started to root the tablet with mrmazak's files.

The restore process is not normal. In fact I bricked mi e there times trying to do restore. I found a long way around that does a restore.

Remember I posted in same post you quoted that restore process was not "straight forward"

1. I needed to format system in fastboot

2. Flash system in fastboot (it fails probably because I have a raw system did copy and it needs to be spares)

3. After the failed system flash , fastboot mode is broken

4. Force reboot to recovery, then adb reboot fastboot again

5. Now boot CWM

6. Format system

7. Then restore worked for me

That is process I had to do, because just doing a restore messes the system partition

. Second test I tried starting at #6, it worked that way 2 times when testing. I did it again the other day for more testing before I put out the permissive files. And needed to do the whole process 1-7.
[General Questions and Answers] Plasmastar:
Cool. I would love to get this tool. RCA Support is not being too supportive. They suggested wiping from recovery mode, then suggested sending the device to them for a factory reset after I mentioned the recovery mode being gone.
[General Questions and Answers] rpk3:
..my apologies. OEM terminology was confusing. No matter what device I trade or test for I always pull boot and system images first. Even saw this post and was reassured that others do the same for there own piece of mind. Kinda like a cheap xcopy command or IMG file from any manufacture.. Basically everything I did was within the limits of mr mazaks tools. If he warned of brick. I tried to replicate with inconclusive results or a black screen after fastboot. Rather than contact him I made several repeated attempt to access and replicate what he had done. I did not touch adb secure settings because I have bricked many a device with this option ....

Now. Between you and me. I made contact with a rep from rca.......that's all I'll say here.

Again. My purpose of joining this group was info on root. now we have it ? thx so much to this thread and especially vampirefo and mrmazak.