yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] typos1:
Buy an RK3368/PX5 W211 unit and an RK3399/PX6 SoM, put the RK3399/PX6 SoM in the W211 unit then sell the RK3368/PX5 SoM ?
[MTCD Android Head Units General] myspac:
I m looking for SoM PX3 with HDMI output (2G I think it hte max.) for tests: someone know where can I buy one ?
[MTCD Android Head Units General] naghtan:
You are maquiaveliq
[MTCD Android Head Units General] typos1:
Look on Aliexpress.
[MTCD Android Head Units General] myspac:
I already saw but found nothing, have you a link ?
[MTCD Android Head Units General] typos1:
No, I have not seen any RK3188/PX3 Nougat SoMs on there I was just suggesting to look. you could buy a secondhand RK3188/PX3 2Gb unit, swap the SoMs over and sell it on.
[MTCD Android Head Units General] myspac:
(I only want to do some tests with hdmi output, not swap/sell my PX6. But yes, if I can find secondhand ...)
[MTCD Android Head Units General] typos1:
I see, what tests did you want to do ?
[MTCD Android Head Units General] myspac:
Compare fps on my hud between px3 hdmi and displaylink usb2 hdmi...
[MTCD Android Head Units General] myspac:
Ok, I found a solution for to reactivate wifi when it is disable after sleep, it is to disable usb parent and to enable it again, and after to start/stop the wifi service: something like that:

echo "0" > /sys/devices/platform/fe3c0000.usb/usb1/1-1/authorized

echo "0" > /sys/devices/platform/fe3c0000.usb/usb1/authorized

echo "1" > /sys/devices/platform/fe3c0000.usb/usb1/authorized

echo "1" > /sys/devices/platform/fe3c0000.usb/usb1/1-1/authorized

echo "1" > /sys/devices/platform/fe3c0000.usb/usb1/1-1/1-1.1/authorized

svc wifi disable

sleep 2

svc wifi enable

So, I m happy to not must reboot anymore the unit each morning !

But ...

- I don't know why after sleeping the USB driver is not activate (and why other driver are...).... ?

- someone knowns how can I launch a shell or an app at the startup and/or after sleeping ? for MTCD unit, there is a list or something like that ?
[MTCD Android Head Units General] Bose321:
Would installing a new coreboard also solve my USB/WiFi issues because of the ****ty USB chip? 80 euros for a new coreboard (the 2GB ones) sound great to me. Can I just replace the current board from my unit? I assume everything is lost because the data is also on it? No issue, but just wondering. I have a GS-unit right now, would it matter what I buy?
[MTCD Android Head Units General] typos1:
You certainly can replace the SoM with an RK3399/PX6 one (or an RK3188/PX3, or an Intel Sofia if you so wished - all MTCD/E mobos can take any MTCD/E SoM).

Cant see it solveing any USB/wifi problems though cos those chips are on the mobo.

What problems do you have ?
[MTCD Android Head Units General] Bose321:
Ah, I thought this coreboard would be the complete mobo.

My USB hub (and wifi) are not working 9/10 times. I'm aware of all the threads about this, and tried the shell script to reset it, and got the latest Malay ROM with the 'fix' integrated, but still no USB most of the times.

In this case my best bet is to try to solder a new USB chip, and maybe check if the mobo is not loosened or something (found that here: https://xdaforums.com/android-auto/...x5-mcte-low-temperature-fix-wifi-usb-t3868388). It started with cold weather, so that looks like most people describe it, but we had a few warmer days (10+ C) and it still didn't work. And it worked great a year ago on vacation for 2 weeks in below 0 C temps.
[MTCD Android Head Units General] typos1:
I see, I havent read any new threads for a while (just the ones I m subscribed to) so havent read anything about this yet, but it sounds like a new USB chip is what you need.
[MTCD Android Head Units General] myspac:
To be sure it is not the same problem as mine, when your wifi doesn't work, if you reboot the unit (changing logo for exemple ask to reboot), the wifi still doesn't work ?
[MTCD Android Head Units General] Bose321:
Wifi not sure, but my main problem is with the USB. That mostly works after a reboot, but sometimes doesn't anymore after a reboot. :eek:
[MTCD Android Head Units General] myspac:
If it works after reboot, it is not cold temperature no ?....
[MTCD Android Head Units General] Bose321:
It's not always working. Sometimes a reboot helps after a few minutes (when it's warmer I guess), but sometime when it's working a reboot may break it again. I'm really done with this hardware/software. If it works it's fine, but when things don't work properly it's such a nuisance.
[MTCD Android Head Units General] koutsouk:
Guys I follow the thread and I saw that you can interchange the processors. The firmware version running is irrelevant of the processor ?

A unit running 7,1 android and px3 can run with px6 ?

Or a unit with android 8 and px6 can run android 7.1 ?

Reason I ask these is because I have a unit BMW specific that after performing a factory reset it boots up always in recovery mode complaining that android is corrupt.

It saws two options

1) try again

2) factory reset

Since there are no physical buttons I can not choose anything.

I connect a usb keyboard but it is not recognized.

I connect a usb mouse and it is recognized, it mines between the two choices but I cannot select any of them.

I attach a photo to see what is happening

Do you have any idea how to revive this brand new unit without sending it back to China ?
[MTCD Android Head Units General] typos1:
Any MTCD/E SoM would work, but your SoM is probably recoverable ,its just finding out how to control it.

Have you tried holding the right button on the mouse to select , or another keyboard or mouse, or a different usb port, or using the reset button for selection ?
[MTCD Android Head Units General] koutsouk:
Thank you for your answer.

The mouse is recognized in both usb slots.

Keyboard not at all in any slot.

The mouse if I long press any button makes the selection green ( highlights) but if I long press it again does nothing.

Like there is no enter function but only selection.

The reset button every time I press it just resets the unit so only if I try a different keyboard.

I asked about the firmwares because I do not have the original 8.1 file but a have many from 7.1 from the some manufacturer but these unit had px3 processor.

Even if I had the firmware how could I install it since the unit is in recovery boot loop ??

Also I am unsure if the unit is MTCD/E

The unit that I have is this

https://4x4shop.ca/product/oem-fit-...ifibta2dpusb-multi-media-original-cic-system/

Not from this seller but from UGODE ALIBABA but it has the same specs.
[MTCD Android Head Units General] typos1:
That certainly doesnt look like an MTCD/E unit, although its possible they could have skinned it to look like the BMW OEM unit.

You cant flash 7.1 on an MTCD/E SoM that had 8.1 originally, you could change the SoM if its MTCD/E.
[MTCD Android Head Units General] koutsouk:
I could but the goal is to recover it since the only thing that I have done was factory reset it !
[MTCD Android Head Units General] typos1:
I was just answering your questions from earlier, I d try another keyboard or using the reset hole.
[MTCD Android Head Units General] koutsouk:
Of course !!!

Nothing bad with this.

Well the thing that it says that android is corrupted indicates that reflasing the firmware maybe with sd card tool can save the situation ?

All these if I cannot manage to exit this recover state, as I think that this is not real recovery as recovery have many other options m.
[MTCD Android Head Units General] typos1:
It looks like a real recovery. I think the best thing to do is to open a new thread for your problem.
[MTCD Android Head Units General] koutsouk:
This is how the board is inside.

I attach it if you have an idea !

i am trying to find C17 ic to do the sorting thing but unless i am blind i cannot find it !
[MTCD Android Head Units General] koutsouk:
is it possible to make a bootable sd card with Oreo OTA files inside to force the unit install the stock image again?

I mean without going to recovery .

Similar process to SD card Tool but without an .img file since OREO has only OTA files for update?
[MTCD Android Head Units General] typos1:
I can tell from the SoM thats its deffo not an MCTD/E unit, so youre best off looking in the Android Headunits general forum for help.
[MTCD Android Head Units General] koutsouk:
Thank you for your efforts friend.

Another person had the same problem as I had

https://xdaforums.com/android-auto/...nt/witson-px5-android-8-0-unit-stuck-t3773643

And managed to connect a usb keyboard to move in recovery.

I wasn’t lucky with my keyboard.

I’ll try tomorrow with another one and see.

That could be a solution !
[MTCD Android Head Units General] typos1:
Yes, but the one in the thread in your post is an MTCD/E unit, yours is not, so its likely you will require a different solution.
[MTCD Android Head Units General] koutsouk:
Correct but I think that the principal should be similar.

I mean when you are into recovery as I am the way to control it would be

By physical buttons

By keyboard

By mouse

By reset button

By shorting an ic on the board.

Something like this.

Cannot be much different I think

Correct me if I am wrong.
[MTCD Android Head Units General] koutsouk:
Does anyone know what does that Chinese mean in English???
[MTCD Android Head Units General] scorillo_ro:
PX6 goodies!

Hi @kumarai @Hal9k_ @marchnz

I have some new (afaik) things that deserve to be shared with the community.

- the first MCU file for YL units

- the first OTA update for PX6 Android 9.0

- the first firmware IMAGE of a newer than Android 6.0 version: PX6 Android 8.1

The good news is that PX6 Android 8.1 users will be able to upgrade to Android 9.0 the same way as PX5 from Android 6.0 to Android 8.0

I thought we would never see an update.img again, just update.zip OTA ones...

Guys... do your magic!

HERE

---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------

./img_unpack ../My_Work/update.img ../My_Work/update_unpacked.img
rom version: 8.1.0
build time: 2018-12-24 20:20:43
chip: 33333043
checking md5sum....OK

./afptool -unpack ../My_Work/update_unpacked.img ../My_Work/update
Check file...OK
------- UNPACK -------
package-file 0x00000800 0x000002F6
Image/MiniLoaderAll.bin 0x00001000 0x0004394E
Image/parameter.txt 0x00045000 0x00000392
Image/trust.img 0x00045800 0x00400000
Image/uboot.img 0x00446000 0x00400000
Image/misc.img 0x00846800 0x0000C000
Image/resource.img 0x00853000 0x000D0400
Image/kernel.img 0x00923800 0x011A6814
Image/boot.img 0x01ACA800 0x00178BC0
Image/recovery.img 0x01C43800 0x0180CAB4
Image/system.img 0x03450800 0x6A05710C
Image/vendor.img 0x6D4A8000 0x0DACD0A0
Image/oem.img 0x7AF75800 0x04B1A094
backupimage/backup.img 0x7FA90000 0x03380004
update-script 0x82E10800 0x000003A5
recover-script 0x82E11000 0x0000010A
UnPack OK!
[MTCD Android Head Units General] typos1:
So, there may soon be a [MENTION=5092263]Hal9k_[/MENTION] ROM for PX6 devices !!

Wonder why theyve gone back to images ?
[MTCD Android Head Units General] scorillo_ro:
I don't think they'll go back to img. I guess it always existed but this one was made available by mistake.
[MTCD Android Head Units General] typos1:
I took the move to zips for ROMs as aligning with most other Android devices.
[MTCD Android Head Units General] kumarai:
Thank!

Commercial copy received. Works, at the end of the work will be published.

РХ6 we expect in quantity of 10 pieces. PX6 2019 already with Android 9.

PX30 perfectly updated to 4 GB RAM.

РХ5 2019 is already coming out with Android 9.
[MTCD Android Head Units General] typos1:
Hey kumarai !

Where do you get your info from ?

"РХ6 we expect in quantity of 10 pieces" - are you selling these now ?
[MTCD Android Head Units General] scorillo_ro:
I already own a PX6 unit running Android 9.0
[MTCD Android Head Units General] scorillo_ro:
See the pictures
[MTCD Android Head Units General] 1kftlbs:
Looks like a standard double din 7". Did you switch the board?
[MTCD Android Head Units General] scorillo_ro:
It is 9" single din

The unit is new, I had problems with the touchscreen on my previous PX5 unit...
[MTCD Android Head Units General] Hal9k_:
Hi.

This is very interesting. Thank you for sharing. I will definitely look.
[MTCD Android Head Units General] typos1:
I ll upgrade to an RK3399, soon as you do a ROM for it :)
[MTCD Android Head Units General] scorillo_ro:
[MENTION=5092263]Hal9k_[/MENTION] I will also like to have a mod for Android9.

Did not had free time to play more with the unit. At this point I just used adbon password to be able to access the developer options and adjusted the dpi to fit my needs.

I will root it when I'll have more time.
[MTCD Android Head Units General] scorillo_ro:
Are these new features? I don't remember seeing them in 8.0.

Being able to use wheel key study to reassign actions for can keys and double actions.

It is very nice to use the same short pressed key for answering and ending calls and long press the same key for other action.
[MTCD Android Head Units General] zeyret:
The features in these pictures are also open in the new MCU_MX_3.06 in Android 8.0.

There are no options in previous version MCU.
[MTCD Android Head Units General] scorillo_ro:
Android9 ROOT

@kumarai @Hal9k_

I had a little time to play with Android9. It took me some time to figure out a way to root it but in the end I was able to do it.

I used the wifi adb method and the su binary from this archive to do it but the remounting of the filesystem in read-write mode was trickier.

This is how it is reported:

$ adb shell su 0 'df -h'
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.4G 1.6G 825M 68% /
tmpfs 1.8G 488K 1.8G 1% /dev
tmpfs 1.8G 0 1.8G 0% /mnt
/dev/block/mmcblk2p16 504M 174M 330M 35% /vendor
/dev/block/mmcblk2p17 504M 110M 394M 22% /oem
/dev/block/mmcblk2p15 11M 32K 11M 1% /mnt/vendor/metadata
/dev/block/mmcblk2p13 488M 508K 487M 1% /cache
/dev/block/dm-0 24G 1.1G 23G 5% /data
/data/media 24G 1.1G 23G 5% /mnt/runtime/default/emulated

$ adb shell su 0 'mount -o rw,remount /'
'/dev/root' is read-only

$ adb shell su 0 ls -al /dev/root
ls: /dev/root: No such file or directory

WTF??? no /dev/root ... so how I was supposed to remount it if it does not exist?

The solution:

$ adb shell su 0 sgdisk --print /dev/block/mmcblk2
Disk /dev/block/mmcblk2: 61341696 sectors, 29.3 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 594C0000-0000-443F-8000-749B00007BEC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61341662
Partitions will be aligned on 1024-sector boundaries
Total free space is 16350 sectors (8.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 16384 24575 4.0 MiB FFFF uboot
2 24576 32767 4.0 MiB FFFF trust
3 32768 40959 4.0 MiB FFFF misc
4 40960 73727 16.0 MiB FFFF resource
5 73728 139263 32.0 MiB FFFF kernel
6 139264 147455 4.0 MiB FFFF dtb
7 147456 155647 4.0 MiB FFFF dtbo
8 155648 157695 1024.0 KiB FFFF vbmeta
9 157696 223231 32.0 MiB FFFF boot
10 223232 354303 64.0 MiB FFFF recovery
11 354304 583679 112.0 MiB FFFF backup
12 583680 591871 4.0 MiB FFFF security
13 591872 1640447 512.0 MiB FFFF cache
[COLOR=Red][B] 14 1640448 6883327 2.5 GiB FFFF system[/B][/COLOR]
15 6883328 6916095 16.0 MiB FFFF metadata
16 6916096 7964671 512.0 MiB FFFF vendor
17 7964672 9013247 512.0 MiB FFFF oem
18 9013248 9014271 512.0 KiB FFFF frp
19 9014272 61341662 25.0 GiB FFFF userdata

$ adb shell su 0 ln -s /dev/block/mmcblk2p14 /dev/root

$ adb shell su 0 'mount -o rw,remount /'

Then pushed the su binary and all the next steps...

The symbolic link for /dev/root must persist after reboot or you will not be able to remount the filesystem in read-write when needed (e.g. Total Commander)

I did it this way.

I created a file named rootdev.sh as follows

#!/system/bin/sh

ln -sf /dev/block/mmcblk2p14 /dev/root

and a file rootdev.rc

service rootdev /system/xbin/rootdev.sh
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0

then I pushed them on the device

$ adb push rootdev.sh /system/xbin/rootdev.sh
[100%] /system/xbin/rootdev.sh
$ adb shell su 0 chmod 06755 /system/xbin/rootdev.sh
$ adb push rootdev.rc /system/etc/init/rootdev.rc
[100%] /system/etc/init/rootdev.rc

Maybe there are better ways but this is working for me
[MTCD Android Head Units General] okieeee:
android 9.0 Update for dasaita(HA) px6

Is there anybody have a android 9.0 Update for dasaita(HA) px6?
[MTCD Android Head Units General] okieeee:
android 9.0 Update for dasaita(HA) px6

Can you upload the ROM for dasaita RK3399 unit with android 9.0? There is a rom(HCT1_rk3399_9.0_OTA(20190320)) in "https://yadi.sk/d/umCvHqCDzHccr". But it is not compatible with Dasaita unit. I might need the "HA_rk3399_9.0_OTA(20190320)". Thanks,
[MTCD Android Head Units General] Tsumi:
Anyone know where to buy a PX6 SoM? My PX5 board died, tried the USB OTG method with no success (computer doesn't even recognize something was plugged in), so I'm looking for a replacement.
[MTCD Android Head Units General] Tsumi:
Tried Aliexpress, Alibaba, Ebay, and Google. Nothing for PX6 coreboard, PX6 board, PX6 SOM, RK3399 SOM, RK3399 coreboard, and I'm sure I'm forgetting a few other terms I tried searching as well.
[MTCD Android Head Units General] typos1:
I guess you ll jsut have to wait until some appear somewhere.
[MTCD Android Head Units General] Hal9k_:
Try maskrom.
[MTCD Android Head Units General] Tsumi:
Tried it, doesn't seem to work. Though not completely sure I'm doing it right, it's just bridging a resistor to ground, correct?

In any case, I don't even get the device connected chime. Device manager doesn't see anything.
[MTCD Android Head Units General] Hal9k_:
To enter the maskrom it is necessary to short-circuit the desired point on the ground.

Like this:

https://xdaforums.com/showpost.php?p=75931282&postcount=128

https://xdaforums.com/showpost.php?p=75931327&postcount=129

It is necessary to remove the processor board from HU, assemble the circuit for connecting the board to the PC, short-circuit the maskrom pins and connect the USB cable to the PC. If the board is not damaged, you should hear a connected sound.
[MTCD Android Head Units General] Tsumi:
Thanks, I was trying the Rev 4 method, didn't realize there was a separate method for the Rev 8. Got it working.
[MTCD Android Head Units General] marchnz:
Yes, [MENTION=4768815]scorillo_ro[/MENTION] did a great job documenting the process of obtaining maskrom. I have had four SOMs sent to me that all needed to be placed in MASKROM following an unsuccessful upgrade - appears sometimes the eMMC becomes corrupt during upgrade. OTG and maskrom becomes the only way to recover.

Good work hal9k.
[MTCD Android Head Units General] Tsumi:
Yeah, I was trying to go from Android 6 to Android 8, and that bricked it. I found the maskrom method and made the OTG cable as directed, but I was mistakenly trying the Rev 4 method instead of the Rev 8, and I had a Rev 8 board.
[MTCD Android Head Units General] marchnz:
Well done, great result. Cheers for sharing your experience too :)

For others, rev 8 looks like the attached, the two exposed copper pads close to the eMMC are the MASKROM points to short out.
[MTCD Android Head Units General] scorillo_ro:
Attached is a photo from [MENTION=6738895]kumarai[/MENTION] on the 4pda. It is just a guess, didn't had a chance to test it, but most likely those are the pads for maskrom mode on PX6...
[MTCD Android Head Units General] Disastermaster0:
Hello guy

I have got a question about the PX6. At Ali i found a version with and one without DSP. Is that right?

Here you can devide between those:

de.aliexpress.com/item/PX6-Android-9-0-2-din-6-Core-4-GB-RAM-32-GB-ROM-Navigator-Bluetooth/32997440251.html?spm=a2g0x.search0104.3.1.7c5286a65twjS8&ws_ab_test=searchweb0_0%2Csearchweb201602_5_10065_10068_10890_10547_319_10546_317_10548_10696_10084_453_454_10083_10618_10304_10307_10820_537_536_10059_10884_10887_321_322_10103%2Csearchweb201603_35%2CppcSwitch_0&algo_pvid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe&algo_expid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe-0"]https://de.aliexpress.com/item/PX6-Android-9-0-2-din-6-Core-4-GB-RAM-32-GB-ROM-Navigator-Bluetooth/32997440251.html?spm=a2g0x.search0104.3.1.7c5286a65twjS8&ws_ab_test=searchweb0_0%2Csearchweb201602_5_10065_10068_10890_10547_319_10546_317_10548_10696_10084_453_454_10083_10618_10304_10307_10820_537_536_10059_10884_10887_321_322_10103%2Csearchweb201603_35%2CppcSwitch_0&algo_pvid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe&algo_expid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe-0

and for this one, I do not know if it comes with the DSP:

de.aliexpress.com/item/Android-9-0-Core-PX6-A72-Ram-4G-Rom-64G-Auto-DVD-GPS-Multimedia-Player-Auto/32995388299.html?spm=a2g0x.search0104.3.13.7c5286a65twjS8&ws_ab_test=searchweb0_0%2Csearchweb201602_5_10065_10068_10890_10547_319_10546_317_10548_10696_10084_453_454_10083_10618_10304_10307_10820_537_536_10059_10884_10887_321_322_10103%2Csearchweb201603_35%2CppcSwitch_0&algo_pvid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe&algo_expid=b53575e5-6d69-4f9f-96c3-be09dd0aa4fe-2

(sorry for the links, as I'm not allowed to post them, because I'm new)

I would prefer the second one, because of the design, but would like to have a DSP, hoping to have a better sound.

Is there also a reason, except the price, to prefer a PX5 or PX30 instead of the PX6?

Thanks for the information

Kind regards
[MTCD Android Head Units General] thetodor:
Those pics/posts are for the PX5, not PX6. Also, can you explain what you mean by "assemble the circuit for connecting the board to the PC"? Do we need any additional hardware? Thanks.
[MTCD Android Head Units General] Hal9k_:
[MENTION=3632730]thetodor[/MENTION] Just search at the forum.

https://xdaforums.com/android-auto/mtcd-discussion-questions-development/px5-stuck-bootloop-t3635412
[MTCD Android Head Units General] Pipould:
Anyone tried to update a PX6 id7 unit to android 9 ?:)
[MTCD Android Head Units General] gn_ro:
How do you entered in this menu?

Hello,

I have a PX6 unit with Android 8.1 and is having many annoying "features" among them bad or no assigned keys. Can you, please tell me how you entered in to the menu from the first picture?

If it's of any interest the unit is https://www.aliexpress.com/store/pr...ml?spm=2114.12010612.8148356.1.51542fc28rMPlv and it arrived with no info or any paper other than the cardboard box and the vendor is not really responding to my questions.
[MTCD Android Head Units General] scorillo_ro:
Settings > Car settings > Factory settings (using password 126)
[MTCD Android Head Units General] okieeee:
"The good news is that PX6 Android 8.1 users will be able to upgrade to Android 9.0 the same way as PX5 from Android 6.0 to Android 8.0"

How can I update it? I have a px6 android 8.1 HU. I couldn't find a sdupdate.img (android 9.0)for px6. There is only for px5(android 9.0) by hals9.
[MTCD Android Head Units General] plbartie:
Would also like to know. All instructions i have seen is for px5. Here is my info.
[MTCD Android Head Units General] scorillo_ro:
I guess [MENTION=5092263]Hal9k_[/MENTION] will release this at some point.
[MTCD Android Head Units General] typos1:
You dont have an MTCD/E RK3368/PX5 device, youre in the wrong thread and wrong forum for your device, do not under any circumstances try any of [MENTION=233696]hal[/MENTION]89_'s ROMs on your device, you will brick it.
[MTCD Android Head Units General] plbartie:
I have a Rockchip PX6 rk3399 HU, and this thread title is for px6 units, A72 & A53?
[MTCD Android Head Units General] scorillo_ro:
this thread is under "mtcd-android-head-units-general"... maybe you have rk3399 cpu, but your unit is not mtcd/e
[MTCD Android Head Units General] typos1:
You may well have a head unit with an RK3399 processor, but you dont have an MTCE head unit with an RK3399 processor.

The Google Pixel 3 and the Samsung Galaxy S9 both use the Qualcomm Snapdragon 845 processor, but you cant use Galaxy S9 ROMs and software updates on the Google Pixel 3.

Similarly you cant use an MTCE RK3399 ROM on a non MTCE head unit with RK3399 processor.

Head units are no different to phones, you wouldnt choose a ROM for your phone based only on its processor, you choose it based on the manufacturer and model, the same applies to Android head units.