yashsingh1/xdaforums huggingface dataset:
[General Topics] mrmazak:
You are right, the second.img is different between recovery and boot. I just did a diff compare and , very different

your recovery.img file is bigger mostly due to because it is a dd copy of the whole partition that it was in. You will find if you repack the recovery , then it will be smaller.

The size of your boot.img shouldn't be causing the hang right now. (bootloader is unlocked)

I am running low on ideas at the moment. Hope someone else comes into the forum with your build version and gets the stock files pulled in order to fix yours.
[General Topics] TheNH813:
To be honest, it's less trouble to just get the thing replaced at this point. I learned my lesson.

I have a one time damaged/destroyed device replacement, I can either get a free replacement or some of the money it was worth.

Pretty much all inclusive and covers water damage, smashed screen, or anything that makes it unusable.

It's a terrible choice to have to make, and thinking about it just makes me feel bad, even though it's a sub $50 device.

I know, I know, doing that is a **** move from any perspective, but it's what I'v decided to do.

At the very least, here's a copy of the stock recovery if anyone wants it.

https://mega.nz/#!aMFQBJxI!q9ZuM0AoZbDo2Muqm61vEu7TQqYHxnpRd9m3sXZAnDA

I'l even just say, the REAL reason I wanted it rooted, wasn't even for root itself. It was to fix a problem it was having on day one. I just wanted to grant my file manager access so the SD card. I tried every SD card I had, formatted every one of them, both FAT16, FAT32 and various EXT versions and F2FS. It's always the same. It can usually see files on the card, but it can't write them. The cards work fine on my PC, camera, other tablet, etc. It even worked when I plugged the tablet into my PC to access the files with MTP. I'd grant privilages, but no, it wouldn't write. And yeah, I tried reinstalling the apps, I also made sure to click "Show SD Card" and selected the drive's root like you're supposed to. That always worked on my other tablet. I'l be d***ed that worked. Couldn't even use the pre-installed file manager that was on the device when I got it to do anything. You try to rename or move any file, either on internal or external storage, bang, it crashes, or "System UI Stopped Working". I spent since December 25th trying to avoid having to root it at all costs, and trying every method I read and knew about to fix the sd card permissions issue. Then I decided I'd just give rooting it a shot, because I was desperate to use it the way I intended to. I messed up in the process because I was in a hurry.

Gonna claim the money for a user damaged device, and get a different tablet. I. Give. Up. This would be a different story if I was just rooting it to root it, I'd spend more time and wait for someone to eventually post a image, but I had other motives to root it, and it's been a good week of a couple hours of annoyance per day. Not worth my time, not worth my money.

I'm truly sorry for wasting any of your time in the process.
[General Topics] mrmazak:
Sounds like there was issues with your tablet before. You should have had been able to use the sdcard.

And the recovery (cwm) was able to wright to the card, that's how you pulled the stock recovery. So as far as hardware goes, it was possible. Meaning some kind of hardware issue.

Or mounting issue,

I wonder if you can wright to card now with the modified boot image. Because mounting the partitions and cards is controlled with the boot.img.
[General Topics] TheNH813:
Tried that already and it still wouldn't write to the SD card even with the permissive image.

Didn't matter which file manager I was using either, whether it was the included one, ES File Explorer Pro or ZenUI File Manager.

I also know for sure it has faulty hardware. Went to turn it on today, and it's dead.

Plugged it in, pressed the reset button with a paperclip, pressed the power button, and nothing.

At the very least it should have come on in charge mode, that I know was working just the day before.

It just happens to be an unfortunate dud, it's definitely my luck to end up with something like that.

Might be able to return it to the store for a new one or refund as a defective product instead of having to claim a replacement.

Sorry if my last post seemed more like a rant, I was just really annoyed yesterday. Today, I'v accepted it's fate lol.

At least I know I wasn't crazy the SD card reader wasn't working properly.

It did take 10 minutes to write the recovery image to the SD card, but I'd never done that before so I assumed it was normal.

While MTP did work to access the card, it was also like 1MB/s transfer speeds, again, MTP is slow, I didn't think anything of it.

Either case, I'm taking it to Walmart soon.

I know I may have given it some problems, but not being able to power on isn't one of them.
[General Topics] Isrgish:
My build is RCT6873W42-ANDROID6.0-V21-V1.16.149-E10 did anyone try one of these roots on this build? Which one would you recommend I test with on my device?

Any advice would be helpful.

P.S. I'm totally new at this root thing but I'm willing to learn and test.

Thank You,

Israel
[General Topics] mrmazak:
I have no confirmed uses on that build. But I have included instructions for your situation. They are at the end of the Instruction sheet.

Just be sure you understand what you are doing before you try any steps. The rca tablet is so easy to turn into a brick.
[General Topics] Isrgish:
I will take a look and report back.

Thank You for all the work you did here.
[General Topics] Isrgish:
For pull stock images, does the SD card need to be a blank card?
[General Topics] Isrgish:
I have managed to pull the img put I cant figure out how to attach it here. the help says there should be a button "Manage Attachments" but I don't see it. So here is a link to the file.

https://drive.google.com/file/d/1c70dSu87t8F6at3Ku0fBsrcSvDXPdA1Y/view?usp=sharing

Thank You,

Isr
[General Topics] mrmazak:
Here is boot.img to TEST

only try to boot it.

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

Will need you to pull the stock recovery too in order to fix the CWM recovery too.

same method as you did for boot. Use this command instead for the recovery.

adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 of=/external_sd/RCA/mmcblk0p10-recovery.img
[General Topics] Isrgish:
I booted this file and it booted up to a message about encryption failed or something like that. I shut off the device and restarted and pulled the 2nd file you asked for. Here is the link to it.

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

Thanks again for all the hard work you put in and still putting in to make this work for all.
[General Topics] mrmazak:
here is cwm to try.

https://www.androidfilehost.com/?fid=962187416754456047
[General Topics] Isrgish:
This booted fine as well.
[General Topics] mrmazak:
that

should

mean that you can use those two files and follow steps same as v19 or 31. (useing the files made for V21 ,of course). And format /data to remove encryption (this version of cwm didn't work with encryption), flash the modified boot.img, then backup with cmw.

finally flash the superSU.
[General Topics] Isrgish:
Which file should I use to boot in with cwm? Is it the one from your instructions for V19? I do see that you have different versions for V19 and V31, this makes me think I need a special one for my device (V21).

Thank You,
[General Topics] mrmazak:
????

The second link I put for you was cwm for your v21.

You responded it booted.
[General Topics] Isrgish:
I'm a little mixed up here.

I have 2 files from you

1. rca-voyager-V21-boot.img

2. rca-voyager-V21-CWM-recovery.img

In your instructions I see I need a stock recovery img. I don't think I have that for my device version.

Thank You,
[General Topics] mrmazak:
Oh, you are right I did not make that part.

I was using the modified stock recovery to allow adb from recovery, so can reboot to fastboot (no button combo on tablet, and the reboot command in stock recovery do not work)

But found out later that adb works on tablet (as long as device has been authorized from within Android) with tablet turned off.

Still little bit "safer" with modified stock recovery though.

I'm not able to make this for you for few days. I will be without PC access.
[General Topics] Isrgish:
It's no problem.

I really appreciate the help.
[General Topics] mrmazak:
I was able to get this out before loading my flight. So try this recovery.

On my tablet, and others, the. Stock recovery didn't work when booted but does when flashed.

Make sure (modified) stock recovery has adb access first before flashing the modified boot. That way there is best chance to recover if problems happen

Steps:

1. Boot modified boot.img make sure it loads----done

2. Boot cmw, make sure it loads----done

3. Flash modified stock recovery, make sure it loads and has adb access.

4. Follow steps from original directions. --format /data with fastboot, flash modified boot.img.

5. at this point tablet should be able to boot, and have root access with adb. But not in apps.

6. Boot cwm and flash the superSU as described in direction sheet.

https://www.androidfilehost.com/?fid=818070582850488194
[General Topics] Isrgish:
Thanks.

How do I check if it has adb access if it doesn't work when booted?
[General Topics] mrmazak:
I should have worded it. Differently.

For the other files "modified boot" and "cwm" , I had you "fastboot boot" them first to test them out. The modified stock recovery does not work correctly this way.

So you need to "flash" it to try it.
[General Topics] Isrgish:
I will try this tomorrow.

Thanks
[General Topics] mrmazak:
I have added directions to pull and patch boot.img and recovery.img to the original direction page.

Also I put together a batch file "tool" that will walk you through it the patching process.

The tool uses carliv android image kitchen scripts
[General Topics] Isrgish:
It worked! :D I am Rooted! :D

Thank you very much.
[General Topics] Isrgish:
Stuck in bootloop

After rooting my device I have been using it for some time now. Today It was giving me some trouble (working very slow and restarted apps a few times) so I rebooted my device. Now it seems to be stuck in a bootloop.

It boots till it gets to "Starting Android apps and then it goes back to the Voyager logo.

Any help will be appreciated.

Thank You,
[General Topics] mrmazak:
can only assume some app is misbehaving. So perhaps start over and factory reset.
[General Topics] PoDurg:
RCT6873W42-ANDROID6.0-V19-V1.16.50-E04

worked perfectly after i updated ADB. would not work using adb setup 1.3, "fastboot flashing unlock" wouldn't do anything. updated to adb setup 1.4.3 and worked perfect.

however I wasn't thinking that the "device is now untrusted" 30 second timer was going to stay for some reason. :eek: so that part puts a snag in the application I had in mind for the tablet but I needed root anyway so I'm happy.

that message would go away if we could lock the bootloader again wouldn't it?
[General Topics] mrmazak:
it should, but you would have to also use the original boot.img, so no more root.
[General Topics] Isrgish:
This may be off topic, But I thought this may be my best bet.

It looks like I messed something up with my Google play store while using Titanium Backup. I tried to integrate the play store and the play services into the rom, This got stuck while it was trying and after a few hours I forced closed Titanium. . When doing this I lost my play store and play services. I went and downloaded them again from FreeAPK and installed them, but since then I can't download anything.

I tried a factory reset, but still no help.

I'm wondering if maybe I ruined the ROM version of these 2 apps. Is there some way to reinstall the ROM? Is there any other help you can suggest.
[General Topics] mrmazak:
Remember during the the steps I walked you through, when I said boot into cwm and make a backup?

That is what will help you, if you made that backup.

Other than that will need someone else with your same v21 to make a backup.
[General Topics] Isrgish:
Yes.

i thought of that after posting my question. This did help me,a even though there still seems to be something going on. i still have it sometimes take very long for a download to start. Sometimes it doesn't show notification after it installs a app.

but over all I'm back in business.

Thanks again for all your help.

Isr
[General Topics] Isrgish:
ADB device Unauthorized.

Hi,

I have previously rooted my device, But now ...

My device stopped booting. So I booted into CWM recovery and I factory reset the device but it still doesn't want to boot. But now when I try to access it through ADB to boot into CWM recovery to restore a backup I made when I rooted the device, I get the unauthorized device.

Is there anything to do now? I have seen in previous posts that people had this problem, but haven'rt seen a solution.

P.S. I can boot into regular recovery. I don't know if this helps.

Please help.

Thank You,
[General Topics] mrmazak:
did you try factory reset in stock recovery ?

any idea what made it stop booting?

should be able to get adb to authorize by trying to do an "adb sideload". I send a dummy file in "adb sideload" and of cource it fails, but then after that the adb is authorized.

then if that helps and gets you back in, please redo the process using the new tool i added to first post. One of the biggest changes I made was an improvement to prevent the unauthorized problem after a factory reset.
[General Topics] Isrgish:
I tried to sideload a file, but the device still shows as unauthorized after the sideload.

Is there anyway to make a package out of the backup I have and then apply it from recovery (apply from sdcard)?
[General Topics] mrmazak:
no, because the stock needs to have "signed" packages. Signed with rca key.

I will have to send you the private key used when i made the stock recovery for you, Then you put that key into your pc and try the side-load trick again.
[General Topics] Isrgish:
OK

---------- Post added at 01:05 PM ---------- Previous post was at 12:56 PM ----------

Yes I wiped from stock recovery as well.

I was having some weird problems with SuperUser app something about su being stolen (not the right word but can't remember). So I tried to reboot. It rebooted to blank screen. At that point I was still able to connect with ADB so I booted to CWM recovery and tried formating the Cache and System when that didn't help I wiped the data. After that I wasn't able to connect with ADB only as unauthorized device.
[General Topics] mrmazak:
I had to find the right key.

I put it into a batch file that swapps the key for you.

unzip the attachment, run the batch file , then try to connect to adb, and if not work , do the sideload trick again .
[General Topics] Isrgish:
Now when I did the sideload trick it shows device as recovery. Now I was able to boot into CWM recovery.

When I tried to restore I get an error that the MD% on system.ext4.tar.b mismatched. What can I do for this. Last time I needed to restore it worked fine. As far as I know no changed were made.

Thanks a Million, for your help till here

Isr

---------- Post added at 06:02 PM ---------- Previous post was at 05:59 PM ----------

Now when I try to restore my CWM backup I get an error that the file system.ext4.tar.b MD5 mismatched. Last time I restored from this backup it worked fine. As far as I remember I made no changes to the backup.

Please any help?

Thank You,
[General Topics] mrmazak:
not sure at the moment.

Is there an options menu, if so see if skip MD5 checking is available option.
[General Topics] Isrgish:
I went back to my computer and found I had copied the backup there I copied it back to my SD card and its in middle of restoring. If there is any problems I will report back here.

Thank You,

---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------

OK it finished restoring and it looks good.

By the way every time I reboot from CWM recovery it asks that Root access is missing if I want to Root. Should I do this or not?
[General Topics] mrmazak:
No, not from there.allways tell that no
[General Topics] lsr992:
So after watching this develop from a fat, and unable to get the firmware anywhere, my kid stumbles upon this site today. Scroll through until about the 4th or 5th time you click see more, and blam! RCA. Tons of other cool hard to find firmwares. And it has 4 different versions of this device. The one I downloaded was 100% legit the business.
[General Topics] mrmazak:
What?
[General Topics] Droidriven:
I found one of these tablets, I rooted it using your info. I had another Intel X86 tablet that had a BIOS but was android with a locked bootloader, I looked into installing Windows on it but the bootloader prevented that.

This RCA Intel x86 has an unlocked bootloader but has no BIOS that I can find. Do you know of a way to get this tablet to install 32Bit Windows from USB or maybe dualboot using grub2 somehow? In searching, I've ran across some tools that force a BIOS or similar in order to boot from USB to run the install but it was for Atom Z3736F I think, I wouldn't know how to do the same with this tablet though.

Also, I know it has probably been asked, but I also have a RCT 6973W43, I have them side by side with Aida64 open on both, they are both showing all the same information hardware-wise through every menu. I know other devices with exact same SoC can use the same recoveries. What prevents this from also working on it?

---------- Post added at 12:42 AM ---------- Previous post was at 12:27 AM ----------

I found one of these tablets, I rooted it using your info. I had another Intel X86 tablet that had a BIOS but was android with a locked bootloader, I looked into installing Windows on it but the bootloader prevented that.

This RCA Intel x86 has an unlocked bootloader but has no BIOS that I can find. Do you know of a way to get this tablet to install 32Bit Windows from USB or maybe dualboot using grub2 somehow? In searching, I've ran across some tools that force a BIOS or similar in order to boot from USB to run the install but it was for Atom Z3736F I think, I wouldn't know how to do the same with this tablet though.
[General Topics] mrmazak:
Don't really know.
[General Topics] strubedo:
I need adb key for v19 for pc my screen is cracked and have to use otg mouse i cant make the rsa key because of the broke screen.
[General Topics] jonthn41:
if you have access to a boot.img file you can push it to your device and have magisk-manager.apk root it.. I did this for a tablet i have, however I had to unpack the patched-boot.img and edit the default.prop a little bit to get it to boot.
[General Topics] CargoJacker:
question

i have a recent rca voyager 3 (w43MD) on android 7.0 intel proc

seeing the problems with the older voyager 3's i recogn it's gonna be nearly impossible to root?
[General Topics] jodieb:
Voyager not recognized by sdb

I have a Voyager module RCT6873W42. I have turned on OEM unlock and USB debugging in developer options. I have also installed adb fastbook and the intel driver. However, when I enter "fastboot devices" nothing is found even though the device does show up in my file manager.
[General Topics] Droidriven:
Sometimes you have to manually select the adb driver for the device in device manager.
[General Topics] Isrgish:
I'm getting a message that there is a critical update for my tablet from RCA. When I tried to upgrade I got an error that it found unexpected information.

Does anyone know if this is related to the device being rooted? Or how to go about upgrading the system?
[General Topics] Droidriven:
Boot to recovery and choose factory reset to reset the device, then choose wipe cache partition(this might remove the "unexpected information") then wait for the update notification to pop up again, then try the update.
[General Topics] Isrgish:
I'm trying to backup my device via CWM recovery. But I can't mount the external Sd card I get "Error mounting /external_sd!"

I know that the external SD card isn't at /external_sd.

How do I go about mounting the external SD card.

Thank You,
[General Topics] Droidriven:
Not all devices are the same, when using the temp recovery tool, some devices can use it to create a backup but not all can. The tool is designed to work with many different devices. Some are only compatible enough to boot the recovery session long enough to root, some are very compatible and can use all the features. The backup feature will work on some models but not on others.
[General Topics] Isrgish:
I have used the tool previously to make a backup and I'm almost sure I was able then to backup to an external SD card.

If anyone could help me with this it would be greatly appreciated.

Thank You,
[General Topics] Isrgish:
I finally got my device baked up and tried your suggestion. But no work. I still get the same message.

Here is the exact message I get (this is while its in recovery mode and installing the update)

"/system/bin/app_process32" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)

Installation aborted

Maybe I need to replace one of these files? If yes where can I get a better copy.

Is anyone else having this problem?

Thank You,
[General Topics] Droidriven:
Status 7 means that the file you are trying to flash is not compatible with your recovery or not compatible with your device.

Is the file you are trying to flash is a stock official update?

Are you trying to flash it using CWM/TWRP?

Is the update for your specific model?

If the answer to those questions is yes, that's your issue. You can't flash a stock update via custom recovery, flashing stock updates requires stock recovery and an unmodified system partition(meaning no root and no modified system files).

If this is what yours trying to do, you'll need stock recovery and you'll need to undo any modifications you have made to system and remove root.

Then, after the update is applied, then you can root the device again.
[General Topics] Isrgish:
How do I go about unrooting and returning my device to its original form to be able to install the update?

Thank You,
[General Topics] Droidriven:
If you have SuperSu, there is an option in the SuperSU in-app settings for removing root and uninstalling SuperSu.

If you have Magisk, there is a Magisk uninstaller zip in the Magisk thread that you flash via TWRP to remove root.

Or, if the update can be downloaded via the internet, you can download it and flash it via PC, flashing via PC will remove root during the flashing process, depending on what kind of update it is, the update would have to contain an update system.img, if it doesn't, it won't remove root during the flashing process, which could result in a soft-brick or bootloop.
[General Topics] Isrgish:
I just want to make sure its safe to use this option from SuperSU.

I rooted my device with the instructions on this thread.

Thank You,
[General Topics] Travisholt92:
Thank you for this guide. Twrp and lineage 14.1 are now on my to do list for this device. Stock is unbearable. Once I finish those projects they will b posted here on XDA