yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] fsebentley:
@ vampirefo

Not entirely sure what you mean here.. but here is the bootimg.cfg internal content that is generated with the linux abootimg -x command (standard android boot.img extraction) :

bootsize = 0x2000000

pagesize = 0x1000

kerneladdr = 0x2600000

ramdiskaddr = 0x500000

secondaddr = 0x2400010

tagsaddr = 0x100

name =

cmdline = idle=halt notsc androidboot.hardware=sofiaboard apic=sofia nolapic_pm firmware_class.path=/system/vendor/firmware androidboot.selinux=permissive nolapic_timer x86_intel_xgold_timer=soctimer_only vmalloc=512m slub_max_order=0 console=ttyFIQ0,115200n8

Ths is the info contained within my original recovery.img extracted from the tablet note the portion of the cmdline parameter which mrmazak was referencing "androidboot.selinux=permissive" .... this would tend to indicate that it is already permissive my assumption based on his enquiry was that he wanted to remove this ?

[MENTION=5312578]mrmazak[/MENTION]

I extract images using the standard android tools from the sdk , ie ones you can compile with an android build using the android sources. The boot.img or recovery.img files generated by android can be extracted using abootimg in linux. the package is in the repo's. This is what I use to build and extract images which I edit.

Recovery is available.

It is the unchanged one.. I had loaded the one I was working on through fastboot boot recovery.img
[General Questions and Answers] mrmazak:
Thank you . Yes that information is same as I have, I just have it in separate files because the tools I use. (Windows).

And I don't want to remove the "permissive" , i want the permissive to actually be permissive.

If I issue "getenforce" the response is all ways "enforcing"

So something else (sepolicy) is over-riding this setting.

I guess that in recovery , if you select mount /system, you get a fail message.

That is what happened to me. But, I had flashed a modified-stock recovery that had adb.

If yours is the stock -stock one, I think only hope is an official signature key leak or official update package.
[General Questions and Answers] fsebentley:
I expect I am now going to either have to get the original Firmware image, or build one if I can figure out the proper format and reflash the device in order to recover it... any idea what format the firmware files for these devices use ? I have the firmware flash utility from intel but have not got any actual firmware formatted files to test it with (Not flash but just to see the form the firmware files take) it appears the will be in a zipped form to use with it but the internals of that zipped form would be helpful... given a full partition extraction from one of our devices I should be able to rebuild one using the partitions provided I have an example of a firmware and tools to convert files to the proper form....

I have done this with other SOC devices, my prior Dev work has been done primarily on Allwinner based devices.

These Intel devices do have a Flash mode in addition to normal boot mode and fastboot and I have access to the flash mode on my device at least while the 30 second warning is given and if I can get the key combo I should be able to put it into flash mode. I am additionally hoping to be able to find a key combo that will place it into Fastboot mode, but so far no dice... occasionally this requires some odd interactions somtimes I have had to remove the covers on devices in order to push the proper buttons to activate some modes ( ie both volume buttons in sequence can be a bit difficult unless you seperate the toggle bar)
[General Questions and Answers] mrmazak:
[MENTION=5246104]fsebentley[/MENTION]

this is kind of what I was thinking of when I found the format inside the flash.xml

<?xml version="1.0" encoding="utf-8"?>
<flashfile>
<id>system</id>
<comments>COMMENTS</comments>
<code_groups>

<code_group name="RECOVERY">
<file TYPE="RECOVERY">
<name>rca-recovery-cwm-ramdisk.img</name>
<version></version>
<offset></offset>
<fixed_size></fixed_size>
<checksum></checksum>
</file>
</code_group>

</code_groups>
<commands>
<command>
<string>fastboot boot $recovery_file</string>
<timeout>60000</timeout>
<retry>6</retry>
<description>Boot to Recovery</description>
</command>

</commands>
</flashfile>

But I try loading it into the intel flash program and I get errors. So I try and load the xolo flash.xml and it also has same error.

I hope you can use this information to get this working, I am also hoping that I am not going in the wrong direction here.
[General Questions and Answers] mrmazak:
As far as progress on rebuilding sepoliy. I have not been able to. What I have tried was swap the sepolicy from the cwm and also some random "lax sepolicys" found on the web. THe results are all the same. Try to boot from fastboot rather than flashing it. and the boot hangs on the RCA logo screen for longer than normal , then tablet reboots into recovery mode. So that tells me the kernel needs to be redone not the policy.

I tried to stick the kernel part of the cwm recovery in but that just made tablet boot into recovery straight away without the hang on logo screen.

For now I am still at a stand still with just the tethered root shell.
[General Questions and Answers] mrmazak:
I found a similar issue to whT is holding me back. Issue of tablet booting to recovery when I try to set it to permissive mode. (Safe boot mode if you will)

https://xdaforums.com/nexus-6p/general/permissive-mode-android-n-npc56w-build-t3343573/page2

There method of bypass is basically to stop "logd" so kernel does not know it is permissive. I think I will spend some time and try this approach.

It does not seem like a final solution as logs do help so , ...... Any way it is an idea.
[General Questions and Answers] mrmazak:
Please everyone, contact rca support to ask for kernel sources.

http://rcaav.com/support/webform/
[General Questions and Answers] hauckk@sfreserves.org:
I sent in a form
[General Questions and Answers] rpk3:
Done. Thks for all the hard work in this.

==update

As usuall. The strongarm corporate stall tactic...

==begin paste /.

Paul Kaszap
[General Questions and Answers] mrmazak:
Almost have TWRP

I have been messing around with a twrp port, and I have it booting, but don't know how to fix a touch screen issue.

The touches do not match the display.

If I post the w.i.p. (work in progress), does anyone know how to adjust it?

this twrp has the touch screen overlay turned 90deg to the display.

I have been adjusting X and Y numbers in the ui.xml from in the ramdisk, but it seems to be moving both the displayed button and the touch area for that button at same time, so still don't know how to separate them to make alignment changes.

I have made a backup with this and will soon test the restore and install functions. Display should be fixed before using this though.
[General Questions and Answers] fsebentley:
Likely you have a ui.xml and icons for something other than 1024x600 .. if you do some searching on github and google you can located these designed for the proper screen resolution... I have had to do this for several TWRP variants that I ported for the Allwinner SOC's A13, A20, A23,A31 and A33 .. I used essentially the same TWRP for all simply changing the Kernels a few drivers and the changes to the res folder for the ui.xml and images for the associated screen resolution.
[General Questions and Answers] mrmazak:
This one is not 1024x600 But has built-in scaling so didn't think it mattered. The appearance is normal. And log shows x scaling 0.55555 and Y scaling 0.55555.

If you can picture this situation. The display is in portrait and the touch screen is in landscape. So the bottom left of display is home button and bottom right is back button, but to go home you touch bottom right and to go back you touch top right.

I attached photo showing the back button being registered and you can see where my finger it really touching.

I tried a few builds that are supposed to be portrait and a few that are supposed to be in landscape. They all display in portrait orientation.

Maybe has something to do with the display driver in kernel part of recovery IMG

Found a possible solution, but it requires building the recovery, and we dont have any tree to use as reference.

**keep getting closer
[General Questions and Answers] mrmazak:
I sent an email to RCA through the same link I posted last week. I did not expect much from it and, all I got so far is an automatic response stating that my message has been received and it may take 1-2 business days for a reply. To date it has been 8 business days and no further response.

---------- Post added at 11:03 AM ---------- Previous post was at 10:11 AM ----------

[MENTION=2472806]vampirefo[/MENTION] , can you lend another hand here.

I sort-of got twrp to load on this intel based tablet, but the recovery files I used are missing a boardconfig flag.

this one I believe,is what it needs "RECOVERY_TOUCHSCREEN_SWAP_XY := true"

I do not have a device tree. So adding it and recompiling is not an option.

I think I am using files you might have made at some point.

The history of getting twrp to boot.

1> your supplicated Intel_cwm51_recovery

2> this device recovery kernel img

3> this device fstab

4> the files from "IntelAndroid-FBRL-07-24-2015.zip /FB-RecoveryLauncher / twrp_hdpi_portrait.zip " added to ramdisk

The issue is touchscreen is rotated to display. I situation discussed on Dees_Troy guide https://xdaforums.com/showthread.php?t=1943625 , and simple solution is to add build flag in boardconfig.mk

thanks in addvance.
[General Questions and Answers] vampirefo:
Have you tried the I-700 version? probably closes to the size of this tablet.

twrp_i700_recovery.zip

https://xdaforums.com/dell-venue/general/linux-tethered-cwm-recovery-version-t2963104
[General Questions and Answers] mrmazak:
I will try, thanks, but the auto scaling of twrp seems to take care of the size. Because the display looks correct. And porportiantly the touch is correct,just rotated 90deg.

Edit.

Did not work. Tablet went to "safe-mode" and kernel panic made it reboot to installed recovery
[General Questions and Answers] vampirefo:
The i700 is rotated.

Have you tried a USB mouse on your device?

With my max, I had to build carliv new recovery as touch is disabled in recovery mode, mouse worked just fine though.

Carliv new recovery is pretty cool so far, both touch and manual mode.
[General Questions and Answers] fsebentley:
I submitted a similar request to RCA in Late Nov/Early Dec and get regular replies... identical to first reply saying they will respond in 1 to 2 buisiness days... no actual information is in these responses. I have a feeling they are either just automated replies to "Place Hold" requests that they either do not have a solution to or do not intend to respond to.
[General Questions and Answers] mrmazak:
When I use the whole folder from "i700" just like I did with the "twrp_hdpi_portrait" it just hung at the rca logo then rebooted. But when I use only the "recovery" binary from /sbin folder it boots and has same touchscreen/ display mismatch problem. And searching the binary with hex editor the flag "RECOVERY_TOUCHSCREEN_SWAP_XY := true" is not found.

when I also use the ui.xml, landscape.xml there are no working touch points and only display is the header (but it is still in portrait)

I am hoping that you have the source used to compile that i700 recovery and I can use it or you can make a build with it adding "RECOVERY_TOUCHSCREEN_SWAP_XY := true" to the boardconfig.mk.

No I did not try USB mouse yet, I don't have one with me.

There is currently no USB connection to pc at this time with the tablet either, that was next in my list.
[General Questions and Answers] vampirefo:
These are very old recoveries, I will check when I get home, l doubt I kept the source files, but will look when I can.

---------- Post added at 12:20 PM ---------- Previous post was at 12:09 PM ----------

Upload stock recovery and boot images, I will attempt to make you a permissive boot.img no way for me to test, I suggest only fastboot boot boot.img not install boot.img.

As well as this rotated twrp recovery.
[General Questions and Answers] mrmazak:
the image files are all here in my github repo.

https://github.com/mrmazakblu/RCA_RCT6873W42_bootloader-unlock_CWM_recovery_tethered-root

no-force-encrypt-boot.img is flashed onto device and 99.99% stock, just has change in fstab from "forceencrypt" to "encrypable"

no-force-encrypt-recovery.img is same fstab change made to stock recovery. Plus default prop change to allow adb, along with my add-key in /data/misc/adb

and this twrp is there called "rca-recovery-twrp-wrong-touch.img"
[General Questions and Answers] vampirefo:
OK, when I get home I will see what I can do, you are using no forced? No one should attempt to even boot the one I make on forced encryption.
[General Questions and Answers] mrmazak:
right. I already made change to mine to be not forced
[General Questions and Answers] Plasmastar:
I used a diversionary tactic and asked them about something else, like battery life, as well as if a stock rom was supplied. Honestly wanted to know about battery life, because it sucks, and certainly isn't the 6 hours mentioned on the box. They pretty much said they weren't providing a stock rom though.
[General Questions and Answers] mrmazak:
Update on touch points.

I went and got a mouse like you asked. The mouse works correctly.
[General Questions and Answers] vampirefo:
Will look at this tomorrow, I had some problems with needrom it appears fixed now.
[General Questions and Answers] vampirefo:
The old recoveries were build from cm11 source which I have since deleted, I still have cm13 source so going to try on it.

Ok I started twrp build with. RECOVERY_TOUCHSCREEN_SWAP_XY := true

# Recovery

TW_THEME := portrait_hdpi

RECOVERY_TOUCHSCREEN_SWAP_XY := true

RECOVERY_GRAPHICS_USE_LINELENGTH := true

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"

COMMON_GLOBAL_CFLAGS += -DNO_SECURE_DISCARD

#TW_MAX_BRIGHTNESS := 100

#TW_INPUT_BLACKLIST := lis3dh_acc

TARGET_RECOVERY_FSTAB := device/dell/yellowtail/etc/twrp.fstab

BOARD_UMS_LUNFILE := "/sys/class/android_usb/f_mass_storage/lun/file"

TW_CUSTOM_BATTERY_PATH := "/sys/class/power_supply/dollar_cove_battery"

TARGET_RECOVERY_INITRC := device/dell/yellowtail/etc/init.rc

TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID := true

RECOVERY_GRAPHICS_USE_LINELENGTH := true

BOARD_HAS_NO_REAL_SDCARD := true

RECOVERY_SDCARD_ON_DATA := true

RECOVERY_GRAPHICS_USE_LINELENGTH := true

TW_CUSTOM_POWER_BUTTON := 107

#TW_NO_SCREEN_BLANK := true

TW_NO_SCREEN_TIMEOUT := true

TW_EXCLUDE_SUPERSU := true

TW_FLASH_FROM_STORAGE := true

TW_HAS_MTP := true

#TW_OEM_BUILD := true

#TW_INCLUDE_CRYPTO := true

TW_NO_EXFAT_FUSE := true

TW_NO_EXFAT := true

TW_MAX_BRIGHTNESS := 255

#TW_DISABLE_DOUBLE_BUFFERING_CHECK := true

#TW_NO_REBOOT_BOOTLOADER := true

TW_INTERNAL_STORAGE_PATH := "/data/media/0"

TW_INTERNAL_STORAGE_MOUNT_POINT := "data"

TW_EXTERNAL_STORAGE_PATH := "/external_sd"

TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

TW_FLASH_FROM_STORAGE := true

BOARD_HAS_LARGE_FILESYSTEM := true

TARGET_USERIMAGES_USE_EXT4 := true

#TW_HAVE_X86_ACCELERATED_PIXELFLINGER := true

I have added the twrp files.
[General Questions and Answers] mrmazak:
Thank You , but did not boot.

I used all the folders and the repack time was 5 times longer. ?? mystery

and when booted =, it just went to blank screen, did not even show the device logo.

then i used just the recovery binary from /sbin.

this repacked normaly but hangs at the device logo screen.
[General Questions and Answers] vampirefo:
replace only recovery binary, boot while it's hung you should have adb.

adb push sbin /sbin/

adb shell

/sbin/recovery
[General Questions and Answers] mrmazak:
Unfortunatly, no, there is no adb connection. No usb device seen on pc at all
[General Questions and Answers] vampirefo:
Did you have adb before? Is so use that adbd binary file, and delete the one in the sbin file I gave you, or simply replace with one you had before.
[General Questions and Answers] Jerryvail924:
https://xdaforums.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158/page22
[General Questions and Answers] vampirefo:
Or just boot the working twrp and then once in twrp.

adb push sbin /sbin/

adb shell

/sbin/recovery
[General Questions and Answers] mrmazak:
went back a few steps to fix adb in what I was starting with. Now I have adb and trying to push new /sbin

after push new /sbin now I get permission denied 13 on shell commands

repacked again with the new recovery binary and working adb.

adb shell produces "missing DT_HASH" message

but comes to # prompt.

then /sbin/recovery has same "missing DT_HASH" message
[General Questions and Answers] vampirefo:
No ideal, it must not like the compiler, I don't have old compiler anymore.

Would have to start from scratch install Linux don't update kernel and so on.

---------- Post added at 12:25 PM ---------- Previous post was at 12:17 PM ----------

Well, I just bricked my Intel, needed to see if their software would restore a completely bricked tablet, apparently it does.
[General Questions and Answers] mrmazak:
so you used what software to restore.?
[General Questions and Answers] vampirefo:
I used the software Insignia sent me.

To restore my insignia tablet.
[General Questions and Answers] mrmazak:
And you bricked it just to restore it to test the restore. or the restore failed and now its bricked?

NVM

i reread it and it makes sense.

the restore does work for you.
[General Questions and Answers] vampirefo:
Yes, I paid $50 for tablet a while back, Today I decided to put their factory firmware to a test.

http://imgur.com/a/M2Ned

Not for sure what else can be done on your tablet, I tested the recovery on my intel exactly as I described to you works as should, touch not working cause I rotated screen for you, unrotated screen work just fine.

My tablet cant't boot any touch screen recoveries, but I can push them and get them running, that's why I am sticking to CWM on my devices.
[General Questions and Answers] mrmazak:
well I do appreciate the effort. and I still ended up further anyway.

I overlooked the missing adb and the ability to use a mouse. So now a few more adjustments to fstab and will try to install a zip, The CWM would install some but fail with error on others. I think that was also fstab related, too many factory flags to deal with maybe, not all compatible with the recovery. ??
[General Questions and Answers] fsebentley:
Where is this firmware tool available ?

Also the Firmware you used would be helpful in my own testing if you dont mind sharing the source for download ? If you already have elsewhere I have not been able to locate it. I am currently trying to unbrick my own tab using the tool from Intel but so far no luck due the security in Android 6 stock recovery. Cannot get into Fastboot mode which the Intel flash tool seems to rely on.
[General Questions and Answers] vampirefo:
You would need to get it from insignia, they will require a lot of information and require you not to share their firmware, they will send you two flash drives that when combined are around 26GB.

In that you will have the complete source code, it includes everything for your particular insignia device.
[General Questions and Answers] mrmazak:
I still have not made progress on official whole system root. But my biggest reason for wanting to root is always so I can ad "adaway" . So I ended up just adding the "adaway" hosts file to the system, Now no more ads. At least significantly less, same as using the app.

I added the the hosts file to my github and also updated the reboot to recovery script to make adding/ updating the hosts easy. If you want to use it it is available.

https://github.com/mrmazakblu/RCA_RCT6873W42_bootloader-unlock_CWM_recovery_tethered-root

to use it , easiest thing to do is "clone or download" the repo, unzip the downloaded file your local pc, and run the reboot to cwm batch file.

As with all downloaded batch files you should proof read it for your self before running it.
[General Questions and Answers] rpk3:
Fully test3d.?
[General Questions and Answers] mrmazak:
everything is w.i.p.

but i use the reboot to cwm recovery daily , in fact 10-12 times in the past hour , working on testing a different permisive script approach,.

as for the host file , I have not seen any negative effects.

I think You really should make install the modded recovery as a fall back , and you need to flash the modded boot in order to remove the encryption before you can even use the cwm recovery.

there is a scriprt and a new "tool" as well. Tool is available here

https://www.androidfilehost.com/?fid=817550096634747825
[General Questions and Answers] cozzie37:
Sorry, I'm a newb, especially with Rockchip/Intel SoCs and companies that don't provide source code. I bought this to use with an EasyCap, but it doesn't have uvc support built in. Easycap Viewer supposedly uses a usermode driver, but that crashes and burns as well, and the response I got to a crash report was "get a tablet with a different SoC". What are the odds of being able to build a custom kernel with UVC support without the sources from Alco?

BTW thanks for all your work on rooting this tablet :good: My brother and I both just bought them at WalMart for $25 on clearance, we were hoping to use them for FPV flying/recording.
[General Questions and Answers] supermaxkato:
cozzie37, I just bought one of these and my easycap worked right out of the box. Here is the Google play app I use: https://play.google.com/store/apps/details?id=com.shenyaocn.android.easycaprecorder

Will you reply back to confirm if this works for you?

Back to the main thread; I am also interested in root . But I have very little knowledge and so I can only hope those involved will make it happen. Thanks for your efforts!
[General Questions and Answers] cozzie37:
Sorry to be going off topic here. No, this app didn't work for me. I connected my FPV camera to the easycap and first verified it's working with a different app on my phone, then connected it to the tablet and opened Easycap Recorder, which is the only FPV app currently installed on it. The tablet/app notify me that they've found the usbtv007 device, but the screen remains black, no video. I tried various options in the developer options, enabling usb debugging and cycling the USB mode through all the available options, nothing worked.

Stupid question, is it possible this is the kernel source for this device, or closely enough related to it to build a replacement kernel?

https://github.com/crewrktablets/rk3x_kernel_3.10 EDIT: Nope, we're looking for 3.14 kernels, and probably different from normal rockchip, since this is x86 and most of their stuff is arm
[General Questions and Answers] cozzie37:
Just for kicks, I just opened mine up, I'm trying to determine if I could do a linux image with Yocto. The chips onboard are

Intel PMB8016.P20 - SoFIA 3GRW (main SoC)

Intel PMB9102.P11 (looks like WiFi chip)

Rockchip RK818-2 (power mgmt)

2xMicron D9SHD (512MB DDR3L)

Biwin BWCTGSC11G16G (16GB NAND)

Silead GSL1680 (touchscreen controller)

There are also serial port TX/RX pads on the mainboard, not sure if they're of any use.

EDIT: Forgot to mention, the battery is only 2000mah, and there's plenty of room for a longer/wider/thicker battery.