yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] MTRX2010:
anything yet?? 8(

---------- Post added at 02:04 AM ---------- Previous post was at 01:39 AM ----------

just as a quick notei found this guys.

http://specdevice.com/showspec.php?id=7920-d3ef-0033-c5870033c587

it's an alco tablet with the same model # as the voyager 3 RCT6973W43.

weird thing is it appears to have a quadcore arm processor, and not an intel atom.

i heard there was a root for the alco from twitter profile [MENTION=6315476]srsr[/MENTION]OOT, but they haven't responded yet.

no clue if this will help at all. I would imagine if the alco has an arm proc, and the rca has an intel then we'd need a different su/sudo binary for the RCA because the RCA runs on a CISC processor, and the ARM is a RISC. hope there's some clues here. hit us back with any info you find. 8(
[Android Q&A, Help & Troubleshooting] Maxxvds:
look here

bump
[Android Q&A, Help & Troubleshooting] TimmyP:
Thought Id try bumping this. Sorry itll prolly be gone soon.

This tablet is begging for a root. I did a bunch of adb uninstalling and got rid of google play stuff. Battery is MUCH better. I suppose a custom rom would immensely improve battery.
[Android Q&A, Help & Troubleshooting] mrmazak:
Did you guys unlock the boot loader yet?

adb reboot fastboot
fastboot flashing unlock

If so, you can try and boot the cwm recovery I use on mine(RTC6873W42) to get a root shell. (if the kernel drivers were the same it would actually be full recovery enviroment) And with that root shell you could pull your boot.img . The expected result of the fastboot boot command is an attempted boot to cwm recovery except the screen will be blank, and adb will give root shell access.

fastboot boot v31-test-rca-recovery-cwm-ramdisk-20170709-2052.img

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

And with the pulled boot.img you can make the recovery fully boot by swapping the kernel, then manually change some rc files in the ramdisk folder of the boot.img the allow it to be rooted.

When you get that far, and if you need help, just ask.
[Android Q&A, Help & Troubleshooting] RobinHood16:
This doesn't work with an RCT6973W43, I'm afraid. I get the blank screen from "adb reboot fastboot", as is apparently expected, but while the RCT6973W43 is in this mode, Windows doesn't recognize the device at all, as there are no drivers available. Also, it keeps disconnecting and reconnecting, so that "fastboot flashing unlock" can't get a fix on the device -- it's stuck on "< waiting for any device >" forever, and can only be stopped with Ctrl-C. Otherwise, the only way to restore the device to working order is a hard restart.
[Android Q&A, Help & Troubleshooting] mrmazak:
That connect disconnect is expected when Intel drivers for fastboot not installed. I will link you to my write up on how to install

https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt

Read the document and follow directions in the driver install section. If trouble let me know
[Android Q&A, Help & Troubleshooting] RobinHood16:
Neither of these builds works for me. My build number is RCT6973W43-ANDROID6.0-V16-V1.18.0-M01. Also, even if I could find the correct files, the Intel drivers don't work with my device.
[Android Q&A, Help & Troubleshooting] mrmazak:
Sorry this is giving you such trouble,

but if you cant get the drivers to work, then you hae no way to know if these files will not work on your device.

If you are refering to the "tools" then, yes they will not work, as I coded them to not work if build numbers are not matched. But I never suggested tring the "tools". just the unlock and "fastboot boot" steps

again , If you cant get windows drivers to install then , thats as far as you can go.

I had a pictoral 'guide' for doing it, but cant find it right now.
[Android Q&A, Help & Troubleshooting] RobinHood16:
In that case, my only recourse is to give up. It seems to me that they have made this tablet absolutely unrootable.
[Android Q&A, Help & Troubleshooting] seasonednovice:
i managed to unlock bootloader

i used the method here https://raw.githubusercontent.com/m...ster/unlock_tool/manual root instructions.txt to unlock boot loader only difference is the fastboot screen flashes just input unlock command and keep taping up it works dont really know where to go from here
[Android Q&A, Help & Troubleshooting] mrmazak:
Did you attempt my directions at the end . To boot the modified cwm , to get adb root shell?
[Android Q&A, Help & Troubleshooting] MTRX2010:
well it's been quite a long time since we've started this thread. any word out there??

did anyone find the tools needed(su/sudo), and all that compiled for the atom, and such

to get the job done??

any luck on the boots??
[Android Q&A, Help & Troubleshooting] mrmazak:
I have tried to help several times. I have similar device and have made successful root.

Each time i ask if someone tried my suggestions , i get no response.

I will try again.

I have made an updated "patching" batch file tool.

1. codes the unlock process

2. Attempts boot of generic recovery(needed to get root shell for pulling device boot.img)

3. With pulled stock images it patches for allowing root.

4. Test boots patched images, to verify not gonna brick before flashing.

5. Flashes after successful test

Cwm recovery patched will not run when flashed back to device, only when fastboot booted.

Give a try and let me know how it goes please.

https://xdaforums.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
[Android Q&A, Help & Troubleshooting] MTRX2010:
will do. and you're sure it's the rct6973w43 with the atom processor?? there's several versions of this and if you try the rct6973w42 on the rct6973w43 it will brick the device. as mentioned earlier someone already bricked there's trying some of this stuff.
[Android Q&A, Help & Troubleshooting] mrmazak:
the thread is from rct6973w42 but the newly updated tool uses the files pulled from the device connected. Not pre-built ones. The pre-built images are the ones that could make bricks.

\

I did not receive any comments from any confirmed users who have tried to use my tool on voyager 3. And if anybody had a brick, then they did not follow directions. It was clearly marked to not flash anything while "testing".

The only feedback I received was one user who said that my method did not work. Problem with his claim is he did not even try my method. He was not able to install windows driver correctly, making it impossible for him to have even tried .

2nd to last post on page 2 on this thread has confirmed user of voyager 3 did unlock his bootloader with my directions, but no further comment from them on his status now.
[Android Q&A, Help & Troubleshooting] mrmazak:
next step is to see if "fastboot boot insert-recovery-image-name-here " works to give root shell.(display for recovery is not expected at this step, just blank screen, and an active adb root shell)
[Android Q&A, Help & Troubleshooting] DMon04:
Any update?
[Android Q&A, Help & Troubleshooting] mrmazak:
I have no idea. I don't have Voyager 111.

I was trying to help ,, but nobody with the device has responded, .
[Android Q&A, Help & Troubleshooting] DMon04:
I have the device here. Just bought one today and wondering how to root it lol. If boot unlock bootloader and flash a custom recovery
[Android Q&A, Help & Troubleshooting] DMon04:
Don't know if this helps out but here's some screenshots from the Voyager 3.
[Android Q&A, Help & Troubleshooting] mrmazak:
Don't flash anything yet. There are no recoveries for you model yet.

But I will share this same post from 2 month ago.

https://xdaforums.com/showpost.php?p=75827504&postcount=22
[Android Q&A, Help & Troubleshooting] DMon04:
So if I'm understanding this correctly...the bootloader was unlocked on the Voyager 3? If so...that means it can be rooted very easily. Once bootloader is unlocked,it should be able to be rooted with just the use of a rooting app or computer. Don't exactly HAVE to flash a custom recovery just to root it. Right?
[Android Q&A, Help & Troubleshooting] mrmazak:
Not quite.

The boot.img does not get properly detected and patched with rooting apps.

Rca does not call it boot.img

Off top of my head don't remember what it is called. But it is numbers, just like the other partitions.

So read my guide and try to do the patch. I made easy tool that does it.

If first part (fastboot boot cwm.img) does not work do not continue
[Android Q&A, Help & Troubleshooting] moriel5:
Hello, I was trying your tutorial, [MENTION=5312578]mrmazak[/MENTION], however I keep hitting a roadblock where the device has no permissions when booting into your generic CWM.

May I recieve some help here?

I am not using Windows, but rather Linux, so I could not use your script.

The bootloader is already unlocked here.

As to the model, it is the same as the OP's, and I can verify that it is running an Intel chip (a Sofia Atom, from the ones that were sold to Rockchip), and I had already unlocked the bootloader.
[Android Q&A, Help & Troubleshooting] mrmazak:
Yes, I can try. But it is blind help , as I don't have the same device.

Ok, to get started. You have unlocked bootloader, and restarted tablet. And it runs fine? It should.

Reboot to boooader , "fastboot boot generic-cwm.img"

This gives what.?

Does screen show, or is it just blank?

You said no permissions, so that means.

"Adb devices" returns "unathorized" ?
[Android Q&A, Help & Troubleshooting] moriel5:
The device runs perfectly fine.

I had extracted "CWM.img" from your multi-patcher's archive so "fastboot boot CWM.img", however the name has little importance, and it gets to a blank screen, as expected.

The computer recognizes it, but only if adb is runs as root, and the error is "unauthorized".

When running "sudo adb devices", the device shows up, with "NO_PERMISSIONS" instead of an RSA key.

ADB works fine from within the system.
[Android Q&A, Help & Troubleshooting] mrmazak:
did not see this "NO_PERMISSIONS" tag before.

I think maybe linux thing, not the device, I hope.

do:

sudo adb kill-server

sudo adb start-server

then try "adb devices" again

many more sugestions and claimed answers on this thread

https://stackoverflow.com/questions/9210152/set-up-device-for-development-no-permissions
[Android Q&A, Help & Troubleshooting] moriel5:
Nay, I have seen this with Windows as well, but only when ADB debugging was disabled, as well as with the stock recoveries on some devices.

And I had already tried restarting the ADB server.
[Android Q&A, Help & Troubleshooting] mrmazak:
Well this maybe the confirmation, that this path to root has been blocked by rca. The cmw.img included is eng build, so supposed to work adb by default.

please try to fastboot boot these images.

like there name one is cwm.img for build #31 and other is modified boot.img for build #31

neither of them are safe to "flash" . Boot should not be any problem.
[Android Q&A, Help & Troubleshooting] moriel5:
Firstly, I need to apologize, it turns out I was wrong, the error was not "NO_PERMISSIONS" (I am used to seeing errors like that, when they occur), but rather "no permissions", which also happens with this CWM (with or without "sudo").

The interesting thing is, that with this CWM, video as well as key input work without any issues, however mounting

either /data or /sdcard fails (although I wonder if mounting /external_sd will work, I haven't inserted a microSD card yet).

And regarding the modified boot.img, what am I supposed to look out for?
[Android Q&A, Help & Troubleshooting] mrmazak:
the boot.img, I sent it just to have you check if adb worked on that when booted.

yes mounting /data and /sdcard expected to fail because the device encryption.
[Android Q&A, Help & Troubleshooting] moriel5:
Something that can possibly be taken care of, if we manage to get to building and testing a stable TWRP, correct?

By the way, the CWM manages to read exernal storage without issues.

And I am not sure how clear I was before, but now my laptop recognizes the tablet in ADB without root privileges, although it cannot interact with it in the recovery (even with "sudo"), due to the "no permissions".

Here is CWM's log.
[Android Q&A, Help & Troubleshooting] mrmazak:
I have a twrp that have-ass works. but during boot need to issue "adb shell /sbin/recovery" to soft reboot twrp. And it has same problem as this cwm. It will not function at all when flashed to phone.

Because the cwm i sent does load , I still think the adb error is on your pc OS. any way to try other OS.

log shows "service.adb.root=1" so the adb server on device is reporting its up and good
[Android Q&A, Help & Troubleshooting] moriel5:
I'll try on Windows 10 then, since I have a spare hard drive in my desktop (I have around 10) running Windows 10, and with the tools at the ready, although I have no issues accessing other devices (running TWRP) via ADB from my laptop.

By the way, I just thought of an idea.

I have just written a simple script that can help me find the partition points, and I am writing a similar script to back them up to the microSD card, what do you think about running them inside "flashable" zips?

This may help out if I can't connect to the tablet at all.

To be clear, the scripts do not write anything to the device itself, so there should be no risk in running them from your CWM.
[Android Q&A, Help & Troubleshooting] mrmazak:
I use a script too to make backup. But it uses adb.

adb shell mount external_sd
adb shell mkdir /external_sd/RCA
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID001 of=/external_sd/RCA/mmcblk0p7-mobilevisor.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID010 of=/external_sd/RCA/mmcblk0p4.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID013 of=/external_sd/RCA/mmcblk0p11.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID022 of=/external_sd/RCA/mmcblk0p1.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID023 of=/external_sd/RCA/mmcblk0p2.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID024 of=/external_sd/RCA/mmcblk0p3.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID033 of=/external_sd/RCA/mmcblk0p14.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID034 of=/external_sd/RCA/mmcblk0p13-frp.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 of=/external_sd/RCA/mmcblk0p16-system.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 of=/external_sd/RCA/mmcblk0p17-data.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070 of=/external_sd/RCA/mmcblk0p15-cache.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 of=/external_sd/RCA/mmcblk0p9-boot.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID074 of=/external_sd/RCA/mmcblk0p18-misc.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID076 of=/external_sd/RCA/mmcblk0p5-nvm_fs_partition.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID115 of=/external_sd/RCA/mmcblk0p6-mvconfig.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID118 of=/external_sd/RCA/mmcblk0p8-secvm.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 of=/external_sd/RCA/mmcblk0p10-recovery.img
adb shell dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122 of=/external_sd/RCA/mmcblk0p12-fwu.img
pause

should work similar in edify-script install
[Android Q&A, Help & Troubleshooting] moriel5:
Pretty much the same, just through ADB, as you had said (except that I still do not know what it is called on my device).
[Android Q&A, Help & Troubleshooting] mrmazak:
true. But "sophia-soc" table should be same all around

this is what I think the script would be

#!/sbin/sh

OUTFD=$2
ZIP=$3

SYSTEMLIB=/system/lib

ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}

ui_print "*****************"
ui_print "Back-up Installer"
ui_print "*****************"

ui_print "- Backing-up..."
mount external_sd
mount /external_sd
mkdir /external_sd/RCA
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID001 of=/external_sd/RCA/mmcblk0p7-mobilevisor.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID010 of=/external_sd/RCA/mmcblk0p4.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID013 of=/external_sd/RCA/mmcblk0p11.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID022 of=/external_sd/RCA/mmcblk0p1.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID023 of=/external_sd/RCA/mmcblk0p2.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID024 of=/external_sd/RCA/mmcblk0p3.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID033 of=/external_sd/RCA/mmcblk0p14.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID034 of=/external_sd/RCA/mmcblk0p13-frp.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 of=/external_sd/RCA/mmcblk0p16-system.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 of=/external_sd/RCA/mmcblk0p17-data.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID070 of=/external_sd/RCA/mmcblk0p15-cache.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 of=/external_sd/RCA/mmcblk0p9-boot.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID074 of=/external_sd/RCA/mmcblk0p18-misc.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID076 of=/external_sd/RCA/mmcblk0p5-nvm_fs_partition.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID115 of=/external_sd/RCA/mmcblk0p6-mvconfig.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID118 of=/external_sd/RCA/mmcblk0p8-secvm.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID121 of=/external_sd/RCA/mmcblk0p10-recovery.img
dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID122 of=/external_sd/RCA/mmcblk0p12-fwu.img
[Android Q&A, Help & Troubleshooting] moriel5:
I have just discovered a few things.

1. Intel's ADB driver installer did not install all of the required drivers on my Windows installation.

2. Intel has something different when it comes to Fastboot mode, requiring changes to be made to the Linux fastboot binary (I'll notify about this over at the Solus Phabricator).

And 3. Your script is precisely what is needed.

I'll use your code (manually) to back up the partitions over to my microSD card.

Update: Aside from the /data partition (which was too large to copy to a FAT32 partition), everything has been backed up now.

Do you think that you can work with these files?

Here are, already, the kernel and recovery.

Boot: https://send.firefox.com/download/05f5451313/#8APzqf1n3BLZpNiPzzV0zQ

Recovery: https://send.firefox.com/download/6834d6ccbd/#4kbxZZu1ecCkVYBTf8ZN9w
[Android Q&A, Help & Troubleshooting] mrmazak:
If script is not working for you, yes upload the boot and recovery. I. Will patch. But I cannot add your adb key. Which makes it easier to recovery.

I had an sh version of the tool I was working on, didn't finish because at the time I found nobody interested in it, so it was waisted time

When I find my notes I will let know what fastboot package worked. I think that one from "apt-get adb tools" didn't work but "apt-get install fastboot" was better functioning.

The windows driver for device and adb worked bit I needed to manually assign it for bootloader-mode
[Android Q&A, Help & Troubleshooting] moriel5:
Actually, I enjoy manually running commands, so it's fine.

But what do you mean by the ADB key?

And thank you very much, that would be great, although I would like to help get TWRP working for everyone with the same model, if that's alright with you.
[Android Q&A, Help & Troubleshooting] mrmazak:
Adb key. Because there is no button combo to boot into fastboot mode. I modified the stock recovery to allow adb, but would get unauthorized after a factory reset. So I copy the key into recovery ramdisk , which makes adb authorized allways

So can do "adb reboot fastboot" from recovery, of needed to boot into recovery.

When I get back to my PC, I will share what I have for twrp.

I might have it on my got hub page already.

Uhmmm, nope

It used to be there. I need to synch back again. If I still have

https://github.com/mrmazakblu/RCA_RCT6873W42_bootloader-unlock_CWM_recovery_tethered-root
[Android Q&A, Help & Troubleshooting] moriel5:
Thanks for the information, is there anyway to improve the authorization issue?

As for TWRP's soft-reboot bug, I did not really understand what is the issue.

And I 'm sorry for missing this before, I was excited about the possibilities that have opened up, and that feeling had doubled, since I was also working on the NextBook Ares 10 at the same time, however I think that a .sh version of your tool would be awesome, even though I prefer doing things manually.
[Android Q&A, Help & Troubleshooting] mrmazak:
Been so long since I attempted anything with the twrp. I forgot about the fact that the touchscreen is inverted.

Works with otg adaptor and mouse good.

The one on this link has different kernel than the v31 cwm that works for you. So will need to swap kernel.img and second.img from your own recovery that you copied

https://www.androidfilehost.com/?fid=817550096634745161
[Android Q&A, Help & Troubleshooting] moriel5:
I am not sure whether I had done this properly, since this was my first time replacing parts of a recovery.

I had used the instructions over at http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images, and took "mkbootimg" from superr's kitchen.

The result: For a fraction of a second after booting the recovery (I am still not ready to flash it), I was greeted by a static "picture" of, well, static, and immediately afterwards I was thrown to the boot splash picture (not the bootanimation), and the device is not seen at all by ADB.
[Android Q&A, Help & Troubleshooting] mrmazak:
The tablet not being seen by abd again is troubleing. The splash of static sounds familiar. That might be the point where I was adding the command "adb shell /sbin/recovery" to get the display back.

As long as you swapped both images (kernel and second) should be ok. Or hopefully at same point I was at.
[Android Q&A, Help & Troubleshooting] moriel5:
I'll try taking a look tomorrow, currently I am falling asleep.

However thank you very much so far.
[Android Q&A, Help & Troubleshooting] mrmazak:
I patched your images with the script tool. But like I said the adb.key on your pc will need to be changed, if you need to take advantage of the pre-authorized adb for unbricking reasons. (if careful should be ok)

Caution theses are patched files from [MENTION=5358804]moriel5[/MENTION] specific build number (RCT6973W43-ANDROID6.0-V23-V1.17.80-DS-W03). Rca uses different hardware (lcd) on almost every build. So kernel is different and if you build number is different these files will give you trouble.

I see already 6 downloads of boot.img, so others are trying, please don't brick your tablets.

file folder on file host with root patched images

https://androidfilehost.com/?w=files&flid=270350
[Android Q&A, Help & Troubleshooting] moriel5:
Thanks, I didn't have time to check them in the morning, so I'll try them after I'll return from work.
[Android Q&A, Help & Troubleshooting] moriel5:
I'm really sorry I hadn't answered back to you, [MENTION=5312578]mrmazak[/MENTION], as I had been preoccupied with undervolting my Nexus 4, and PostMarketOS's latest announcements (including reading about the possibility of an open-source bootloader for MT6735P devices).

This is not fair towards you and others, however I was simply so excited that I had clean forgotten.

Hopefully, I'll be able to test it today, in a few hours.