yashsingh1/xdaforums huggingface dataset:
[Android General] MishterKirby:
Can someone help me?

This is what I get when compiling for my tablet:

make: *** No rule to make target `/home/MishterKirby/Android/CyanogenMod/out/host/linux-x86/obj32/STATIC_LIBRARIES/libbase_intermediates/export_includes', needed by `/home/MishterKirby/Android/CyanogenMod/out/host/linux-x86/obj32/EXECUTABLES/aapt_intermediates/import_includes'. Stop.

Anyone know how to fix it, or if it's anything I'm missing?
[Android General] MishterKirby:
Bump

Bump?
[Android General] Viva La Android R.I.P.:
I've just discovered a root solution for the RCA Viking Pro (RCT6303W87M7) with the MediaTek 8127 and running on stock Android 6.0, by using the SP Flash Tool and a patched boot image created by the Magisk Manager. I have full systemless root with Magisk v20.3 with a fully locked bootloader. If any members have this variant of the Viking Pro, but if so and you want instructions for rooting, leave a comment.
[Android General] NepoRood:
While messing about with the predecessor of this device (see OP, lol) I found out that the bootloader wasn't really locked. Even though the device says that it is, maybe the same case for the M7 variant...
[Android General] Viva La Android R.I.P.:
Ahhh. I'd bet you're correct on that. That theory makes perfect sense. And I thank you for the info. I was not aware of the predecessor Viking Pro's bootloader status. On the M7 model, I've used the latest Magisk Manager to patch the M7's stock boot image for systemless root (via Magisk 20.3-stable). I then used the SP Flash Tool to push the magisk_patched.img to the /boot partition. I should mention that, when patching the stock boot image with Magisk, I did go to advanced options and opted to preserve force encryption and dm-verity/AVB 2.0. I'm not certain that this was necessary, but since I am wanting to disable dm-verity/force-encrypt, I'm going to experiment with a patched boot image without any preservation enabled. Do you have any input on this? Thanks for your time.
[Android General] MishterKirby:
Excuse me, but has anyone tried compiling a ROM for this tablet?
[Android General] Viva La Android R.I.P.:
[MENTION=4666511]smartmanvartan[/MENTION] has made some amazing progress on the Viking Pro in terms of breaking ground for development. This tablet is definitely in its early stages of development and, unfortunately, is not a device that has attracted a lot of interest from the dev community. I know of no custom ROM development in the works for this tablet. As it stands, I'm presently trying to compile TWRP for the M7 variant. Once I can get /userdata decrypted -- hopefully with the default key -- I'll have the major obstacle tackled and hopefully get a stable build.
[Android General] MishterKirby:
I tried compiling CyanogenMod 12, but couldn't produce any flashables. :( Good luck with your attempt! :)
[Android General] Viva La Android R.I.P.:
If you want to pass me along your base files and port files for CM 12, I'll look them over and try to contribute. Two heads are always better than one.
[Android General] NepoRood:
I don't think we had an option to use Magisk at the time, lol and I'm pretty sure AVB wasn't a thing till Oreo, so you should be OK on that. These Meditek devices are pretty had to keep down, as long as you have working fimware that you can flash.
[Android General] Viva La Android R.I.P.:
Yeah, these newer members don't realize the hoops we had to jump through before we had tools like Magisk and systemless root. Yeah with a stock firmware package and the SP Flash Tool, pretty much any MediaTek device can be brought back from the dead. Thanks for the encouragement and the info on AVB.
[Android General] MishterKirby:
I was compiling from source, and my hard drive died, so I can't really share anything, ATM.

Now, I was thinking, what if I compile AOSP instead of CM?

I was also wondering if we could port Marshmallow to the Lollipop model, and if it would work, because they both use the MT8127
[Android General] Viva La Android R.I.P.:
I don't see any reason why it would not work. Most likely, the M7 Viking Pro is nothing more than the predecessor tablet with Marshmallow firmware. If somebody could send me the fstab from the Lollipop model, I could check the partition map for any changes that might hinder porting MM to the Lollipop model.
[Android General] MishterKirby:
Here's an fstab:

https://pastebin.com/C8XH4bPa
[Android General] NepoRood:
Wish you guys the best of luck, I certainly didn't have any, lol. The fstab on the device is trash, look at the one in my tree:

https://github.com/neporood/device_rca_viking

Granted I haven't updated in a while...
[Android General] wrenhal:
I'm not in the mood for root quite now but I do have this unit and am interested that it's listed by someone in this thread. I started reading at page 1 and saw the v1.9 or v1.12 comments for versions and was disappointed to not see v1.15.80 listed... which is the 87M7 apparently.

I'm currently using mine with HUR (Head Unit Replacement) in my car with my phone connected to the USB port. It's great to have an Android Auto display in my older car that doesn't even have a stock CD radio. :p
[Android General] Viva La Android R.I.P.:
:svetius:

That seems like a great way to use the Viking Pro. You're the first person I've heard mention using this device for an Android Auto display. Although you're not interested in the prospect of root, I will be posting a thread for restoring the Viking Pro (87M7) using the official firmware package and the SP Flash Tool with PC or laptop. Hopefully, you'll never have need for restoring your device, but the resource will be available in the event you need it. I'm also in hopes that I'll have a stable TWRP for our model tablet as well. Thanks for chiming in with your feedback. :svetius: [MENTION=4666511]smartmanvartan[/MENTION], I wanted to ask your input: can we incorporate the 87M7 variant of the Viking Pro into this thread, or would you rather that the 87M7 be designated to another thread? The reason I ask is that I don't want to be disrespectful by posting off-topic in your thread. Thanks.
[Android General] Viva La Android R.I.P.:
For any members who have the RCA Viking Pro (RCT6303W87M7), this is a direct link to the latest official firmware, Android 6.0 Marshmallow. This firmware can be installed using the SP Flash Tool.

https://mega.nz/#!9UFlhIRA!BpPreRJN0xAyIL0RjelXqQcE0nwHp0WvsYCf6udHudA

Very handy for restoring both soft and hard bricked devices, or for simply reverting to a stock factory state. I'll be writing up a restoration thread soon with complete instructions and links for the requisite tools and drivers.

For members of this model that want root, simply push this patched boot image with the SP Flash Tool. Upon reboot you'll have systemless root via Magisk v20.3-stable.

https://mega.nz/#!JdV3QAJa!rtFgNmxoppBvpz5i27UpCRMyx90WADlkSPXAXAijHAk Until I get a stable TWRP build ported, decrypting /data would need to be done manually via editing the fstab file. Even then, the /userdata partition would need to be formatted to disable encryption.
[Android General] Casper Young:
My Build Number is RCT6303W87M-ANDROID6.0-V15-V1.15.30 I'd like to know how different your's is from mine. And I have a copy of my firmware if you want or need it. I think I left a note here some time ago that the logic board of the RCA Viking Pro was the same one used in the Acer Icona 10.1 which runs with Android version 8. If you two are considering building a new ROM for this device I commend your efforts. I have the (RCA) Maven Pro, Viking Pro and the Galileo Pro and so far no-one has come up with or built any firmware usable to update these devices, let alone a simpler way to flash in the firmware. I think the one thing that stopped development for the RCA tablets was a lack of available firmware to use. Good luck guys, I'll be paying attention.
[Android General] Viva La Android R.I.P.:
Greetings [MENTION=4386539]Casper Young[/MENTION]. It looks as though you have the same Viking Pro as mine. I've been looking at custom ROMs built specifically for the MT8127 SoC, but I was not aware of the Acer Iconia 10.1. Thanks for the info on that. When work slows down a bit I'm hoping to finish my TWRP build for the Viking Pro. Like yourself, I think these RCA tablets should have more development support. Even Walmart's Onn series tablets have gained dev support and unofficial TWRP builds. Hopefully these RCA tablets will continue to gain interest and support from the Android community. Thanks for your information and interest in development.
[Android General] Casper Young:
I was reaserching the logic board for the RCA and found out the Acer Icona (which has Android 8) had the same board, processor and components. In theory they should accept programing from each other that already fits. But I have yet to test that theory. If you're compiling could you single out the serials that are locking out USB?
[Android General] montsamu:
Another go on the 1.10.31?

OK, here's what I have:

RCA Viking Pro

RCT6303W87DK

Android 5.0 v25 v1.10.31

Mediatek 8127

I can boot into this menu:

And then to 'fastboot' and so on, reboot back to normal, etc. I have a male-to-male USB cable, my Windows 10 laptop makes the friendly 'up-beep' (and immediate 'down-beep') when I connect and disconnect the mini-USB power cable, and I end up with a disabled entry in device manager:

But I'm not savvy enough to know exactly what to do from here to help this project, despite reading and re-reading 4 years worth of this amazing thread. Any help would be appreciated.
[Android General] NepoRood:
I'll knock the dust off mine and see if I can help you guys out, I also know a MediaTek guru...
[Android General] snowman222:
Is anyone facing this problem?

This is the error when i flash patched magisk boot img

My USB cable is good

to [MENTION=10059830]@viva La Android[/MENTION]: It would be great if you can give some suggestions in my case
[Android General] Viva La Android R.I.P.:
Hi friend. Sorry I've been off on another tangeant with the whole pandemic occurrence. I looked at the error you are getting on SPFT and a couple of things come to mind. Even though you are using a "good USB cable," try another one. Nobody really knows why, but sometimes these cables are temperamental when it comes to transferring data via SPFT. I've used brand new, OEM cables before and still gotten errors when flashing. Another possibility is the version of your SPFT. Are you 100% certain you are using the latest build version? Also, if you are using a USB 3.0 port on your PC, it can sometimes cause errors. I've found that USB 2.0 ports are always the best when it comes to SPFT. If none of these recommendations helps, I will research the error in depth and try to assist you in troubleshooting. Good luck.
[Android General] snowman222:
Good to see you. It is weird that my tablet was actually RCT6603W47M7, not RCT6303w87m7.

I found out that after bricked it and failed to flash RCT6603W47M7 rom in attempting of unbricking.

I tried RCT6603W47M7 rom and then it back to work now. The system information show that it is RCT6603W47M7 instead of RCT6303w87m7 like before.

However, i'm still struggling with flashing the patched magisk bootimg. After created my own bootimg with magisk manager, i faced this error when flashing it.

Is it required extra step to make it work?

Update: sflash tool V5.1532 give me a successful flash but after that the tablet stuck at bootloop
[Android General] Viva La Android R.I.P.:
Your boot loop is likely a dm-verity issue. When patching your boot image from within Magisk Manager, first select Advanced Settings, then check the box for Preserve AVB 2.0/dm-verity. Then patch the boot image. Magisk will sign the boot image using the stock AVB key. When you use SPFT to flash magisk_patched.img, it should boot up for you.
[Android General] snowman222:
Thanks for your suggestion. I tried but no luck
[Android General] Viva La Android R.I.P.:
Hmmmm. Are you getting any type of error when flashing the patched boot image with SPFT, or is the installation normal but with a boot loop?
[Android General] snowman222:
I got the BROM ERROR with latest version of SPFT (v5.1952)

V5.1532 give me a successful flash with green tick mark, no error prompt, just bootloop.

However, when stuck, i have to use the latest version to flash stock bootimg to escape bootloop.

Using V5.1532 to flash stock bootimg give me a green tick but still stuck in bootloop

Quite strange
[Android General] Viva La Android R.I.P.:
Strange indeed. Another root strategy for these RCA tablets is to pull your system.img, use an image kitchen to inject system-wide root (SuperSU for example), repack the system.img and push it back to your device using SPFT. Once booted up and rooted, it may be possible to use Magisk Manager and install Magisk systemless root using the direct install option.
[Android General] Jacube22:
Only way I know is to use Ultimate Dynamic Navbar and hide the real one. (Must be rooted and have xposed)

(Don't worry, the app can create a new one for you.)
[Android General] nannycrick:
Smartmanvartan, I went back to the drawing board with my 6203. I was able to flash that firmware labeled rct6203w46 you loaded in your repository. I chose formatted+download in SPFT, and it flashed the original firmware 4.4.2 for this tablet. Everything working, wifi, Google Account Login Service. Got it doing app updates before rooting. I'll let you know about unlocking the bootloader. It seems to the box stock firmware. I'll let all the crashed folks know. Thanks buddy!
[Android General] smartmanvartan:
In your wifi networks, do you have a nvram error in the selection menu?
[Android General] smartmanvartan:
Where you having bugs with the lollipop?
[Android General] nannycrick:
Yes. How do I fix that?

---------- Post added at 08:49 PM ---------- Previous post was at 08:41 PM ----------

I had a few issues with Google Login Service. Because I couldn't manage to unlock the bootloader, I couldn't run TWRP recovery, and couldn't flash MinimalGapps 5.0 to fix the login issue. I'll try the boot loader patch fix and see if I get twrp into it. I'll let you know
[Android General] smartmanvartan:
the problem is that our firmware packages don't have all the partitions that are on our tablets. so when you picked the format option, you erased the nvram partition. there are two ways to fix it. that i know of...

1- http://www.trishtech.com/2015/02/fixing-nvram-warning-err0x10-in-android-wifi/ (there is a hex editor in the play store...fyi)

2- if you have a recovery that backs up and restores nvram, you can back up the nvram partition from a friends 6203 and restore it onto yours. alternatively, i am pretty sure you could use a root explorer to do something similar.

i have done this in the past and i used the first method to fix it and it worked... however on my 6303 there is more than the wifi in that nvram partition and i lost HDMI functionality. always avoid the format option unless you really don't have a choice.
[Android General] nannycrick:
I believe I have a nvram backup in my original backups for this device. I'll check on it & see if I can fix it. Thanks!

---------- Post added at 09:19 PM ---------- Previous post was at 09:04 PM ----------

Now I have rooted this 6203, I have one question....how to unlock the bootloader? I downloaded the unlock patcher, but how to run it?

Or...what patched bootloader should I use?

Sent by my rooted rct6203.
[Android General] smartmanvartan:
its a widows application. run it on your computer use the lk.bin from the surf1000. put it in the same folder and run... read the readme it's pretty straight forward
[Android General] nannycrick:
Well...all the app updates went okay. Replaced kingroot with SuperSU. Installed Busybox. I'll give unlocking the boot loader a try as soon as I get home.

---------- Post added at 10:11 PM ---------- Previous post was at 09:59 PM ----------

I want to share this discussion on Android Forums. They have rct6203 users that are crashed. It's good stuff. Better than I ever got from RCA! They just gave me a run around!
[Android General] smartmanvartan:
Shoot me a link to the thread..I'll pop in
[Android General] nannycrick:
I just posted those folks a link to your OP, here's your link to there....

http://androidforums.com/threads/rca-pro-10-tablet.875260/
[Android General] nannycrick:
Just got TWRP recovery installed. Used the MTK TWRP Utility. It works to push twrp recovery to your device. I've used it to install twrp on my old n9106v. Doing a nandroid backup now.
[Android General] smartmanvartan:
Did you unlock the boot loader?
[Android General] smartmanvartan:
If you didn't unlock your bootloader, then your bootloader is already unlocked. what you can do is make a backup with twrp. then in your backup, grab the recovery and rename it recovery.img. then you can re-flash the lollipop. then root, go into system folder and delete the recovery-from-boot.p file and whatever else you want to remove in the apps....now with sp flash tools, you can flash the twrp that you backed up. No reason why that shouldn't work.
[Android General] nannycrick:
I found out how & unlocked it. Got twrp & a nandroid backup done. I had to flash that Surf1000 ROM back into it. My son wanted the most current stuff. I gave him Lollipop! He works construction and can use it on site with him.

I told him NOT to sell it or give it away until I return it to stock. I don't sell rooted devices as a personal policy....and I hid all the rooted apps in the app drawer from him! (Apex Launcher Settings>Drawer>Hidden Apps). Es File Explorer has the root option unchecked. It's almost "caveman" proof now! My old man's LG F3 phone is the same way. hehehe!
[Android General] James101:
How do you get the mtk usb drivers to install? I tried every which way possible, within 5 seconds, and it won't install. RCA won't even respond. I can't believe theres no mtp for this table.
[Android General] smartmanvartan:
the device has to be off and unpluged. open the device manager. plug the male to male usb cable then plug the micro usb or power cable(the micro usb is for power only). at that point, the device should be detected and you basically have five seconds to right click on the new device and click on update driver. from that point on, you don't have to rush. what version of windows are you running? if you have windows 7, there is a automatic driver installer... it's just that the drivers aren't signed so anything newer it doesn't work...
[Android General] James101:
I'm on win10 x64. I do see it in the device manager. Its always there, just says error 43. I tried to force it but then I get unsigned driver error. Guess I'll have to find a win7 pc.
[Android General] smartmanvartan:
are you using the drivers from the guide? they are supposed to be signed...
[Android General] James101:
I tried the ones here, but its says its not for my hardware, it won't install. I tried some other mtk drivers, but they wouldn't install neither.
[Android General] snowman222:
System-wide root is fine in my case, no need for systemless. This approach really makes me excited, especially when desperate with bootloop.

Do you have any guides for injecting SuperSU ini to system.img? Seem like i haven't found the correct keyword for googling.
[Android General] Viva La Android R.I.P.:
The best method I've found is to use a Windows/Mac/Linux compatible Android kitchen such as [MENTION=673068]dsixda[/MENTION]'s Android kitchen w/Cygwin. This tool will also unpack and repack your system.img, add BusyBox, deodex, zipalign, etc. Here is a link for a reference point.

https://xdaforums.com/galaxy-s2/themes-apps/guide-dsixdas-android-kitchen-sgs2-t1227549/page34
[Android General] snowman222:
Thanks for the link.

I will study step by step.

Currently, it seem like far beyond my understanding.
[Android General] snowman222:
Hi there, need your help more.

I am having a really hard time extracting system.img.

Ext2explorer refuse to open the system.img

It does not appear any message box or error, just blank windows after choosing img file.

Explore2fs can open it, but quits with error: could not find valid superblock

Might these softs not support RCA rom? Have you experienced this issue?
[Android General] Viva La Android R.I.P.:
I've never extracted an RCA system image for injection of system-wide root. But I've done it quite a bit on various LG devices. Where did you get the system.img you are trying to extract? It sounds as though you are performing only one step in a multi-step process. Here is a link that will provide guidance. Ext2Explore unpacks images that have already been converted from img to ext4. This link will explain fully.

https://www-theandroidsoul-com.cdn....ndroidsoul.com/extract-system-img-windows-pc/
[Android General] snowman222:
In my case, system.img is the file that created after unsigning System-sign.img

These steps i'm currently following are:

1. Locate the firmware folder to find System-sign.img. This system-sign.img is the file that can be flashed directly with SFtool

2. Unsign system-sign.img with this tool https://forum.hovatek.com/thread-26890.html

3. Perform unpack newly created system.img

4. Add root and repack but I've never gone this far

The problem seem to be in the process unsign system-sign.img.

I've looked in to the step two and tried another tool but it all give error. Only the mentioned tool generated no error.
[Android General] Viva La Android R.I.P.:
Can you use MTK Droid Tools/SPFT to pull a system image directly from your device? It can be done without root on the Onn Surf series of Walmart's MediaTek tablets. I'm assuming it'll work on any MediaTek based device, but I'm assuming.and not certain
[Android General] snowman222:
I think i've nearly done it.

I managed to pull the system.img from device, add supersu.apk and repack it with android kitchen.

Howerver, the brom error of SPFT prevent me from flashing it back. Same error from this post

Is there a way to edit preloader.bin to allow flash an unsigned image?
[Android General] Viva La Android R.I.P.:
I'm trying to research your error. I've never encountered it so I'll see what info I can find.
[Android General] snowman222:
Here's few more information you might find useful.

The very first time, when i haven't flash the original firmware to unbrick device, i was able to flash your boot.img without error.

My guess is something in stock firmware prevent flashing unsigned img

Update: I noticed the firmware in the guide is not signed firmware.

Mine was all signed. The reason might be the stock bootloader only allow signed img

Therefore i can not flash any unsigned one include patched lk.bin.

Do you think there is another possible approach?

[IMG="signed img"]https://upanh.vn/images/2020/05/06/tes4232416a9029249d.png[/IMG]
[Android General] Viva La Android R.I.P.:
I agree, it seems that your bootloader is preventing unsigned firmware images from being flashed. I'm currently stumped for a solution but I've reached out to a MediaTek ROM developer for his input and guidance. I'm hoping I'll hear back sometime today. You are very close, it seems, to having a rooted device. I'm hoping this is merely a simple matter. And, [MENTION=4666511]smartmanvartan[/MENTION], I apologize if this discourse is off-topic to your thread. I'm hoping to get a universal root strategy together for this particular RCA tablet variant. Accordingly, I will start a thread for topic discussion.
[Android General] Viva La Android R.I.P.:
[MENTION=9585999]snowman222[/MENTION], I just ran across this MediaTek root exploit which should be applicable to our device. This exploit gives you temp root, which then enables escalated privileges to attain permanent root. https://xdaforums.com/android/development/amazing-temp-root-mediatek-armv8-t3922213

Until we can hopefully resolve your SPFT issues, this may be a feasible root method.
[Android General] snowman222:
It will be the best approach but I'm still wonder if we could use adb connection.

As i know, we need to edit build.prop to enable connection via mirco-usb port, which is only possible when rooted.