yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] SkyBeam2048:
Not fully sure what you're trying to do and what you refer to with the term "autoload".

Do not mix up sdupdate.img and update.img. They are not the same format and cannot simply be renamed.

sdupdate.img: SD image for SD-card booting/firmware-upgrading during boot.

update.img: ROM upgrade applied on running Android 6. Your android unit will offer to upgrade when inserting an SD-card or USB pen drive with update.img found on it.

Do not use an sdupdate.img and rename it to update.img as applying the update will likely fail and might leave you with a broken Android installation. However entering recovery (press reset until lights go solid, release and re-press reset) should work. Make sure you do not have any SD cards in any slots while doing this. If it does not then you might try creating a bootable sd card from images provided by [MENTION=6738895]kumarai[/MENTION] or the ones I just posted. This should allow you to get a working Android 6 or 8 recovery back. Then enter recovery and apply a full system update (update.img for Android 6 or update.zip for Android 8).

It looks a bit like you're in the wrong thread here as your problem seems to be entirely Android 6 related.
[MTCD Software Development] sibeng:
Thanks for reply [MENTION=3556393]SkyBeam2048[/MENTION], I'm trying to update from android 6 to 8 as discussed in this thread. especially step by step as described [MENTION=6738895]kumarai[/MENTION], sorry if wrong thread

according step by step update [MENTION=6738895]kumarai[/MENTION], sdupdate.img file was in my SD card, and my HU has been restarted many times and there is no sign of file can run

I will try entering recovery (press reset until lights go solid, release and re-press reset again) and start over, Thanks
[MTCD Software Development] SkyBeam2048:
If it does not work try re-creating the recovery-upate sd card again using sd utility.

You might want to download my tools and instructions here to try them.

Read them carefully. Especially do not rename any files. Get an Android 8 ROM (update.zip ) from one of the sources listed in README.txt and place it on an SD card. Preferably not the one you prepared for SD booting before or you need to be very careful not to have the SD card in the reader when the unit reboots.
[MTCD Software Development] warata:
This movie may help.(How to enter recovery mode)

https://youtu.be/lPQgV_55Rkk
[MTCD Software Development] sibeng:
i have downloaded, i will learn more, thanks [MENTION=3556393]SkyBeam2048[/MENTION]

Yes, more than 10 times I've seen it, I'm practicing my finger skills to reset it :crying:
[MTCD Software Development] SkyBeam2048:
It's very simple actually. Just hold the reset button until the buttons start blinking and then turn on solid. This takes about 10 seconds. You can also simply keep the reset button pressed for 15-20 seconds. Then release it, press it again (momentary press).

No hurry in the momentary press. Just release reset from long press and then typ it again. You can also keep tapping the reset button after releasing from long press until the recovery menu appears.

If it doesn't you might have a broken recovery, then try to create the firmware upgrade SD card, insert it and turn on your unit. Then just wait for the upgrade process to finish. Then remove the sd card and re-try entering recovery.
[MTCD Software Development] sibeng:
Yes, various ways to reset as you say I tried, push reset button, 3 times blink, steady lamp, press again, and nothing happen, with different pressing options

Worst possibility, broken recovery. Is there any special way of creating the firmware upgrade SD card ?, or simply use SD_Firmware_Tool and grab from the original firmware of the HA thread link.

I have tried to copy and using SD Firmware tool to sd card (update.zip, update.img/6.0.1 or sdupdate.img), insert sd card to HU, restart HU, turn off ignition, unplug the power cord behind HU, reconnect, press reset button and nothing happens on screen :crying:
[MTCD Software Development] Al Ferro:
I just wanted to show you that i removed the dual sd card reader from my EONON head unit to see if the ribbon cable fits in those two empty connectors on the Hot Audio px3 and px5 front screen boards, well, it does fit, but i haven't powered on the head unit fearing that it might short circut the unit or something like that.
[MTCD Software Development] SkyBeam2048:
As replied to you already you cannot simply rename update.img (Android 6) to sdupdate.img. You need sdupdate.img to create a bootable firmware upgrade SD card using SD_Firmware_Tool. Please follow the link to my share here and download the android 8 upgrade archive. The archive also contains detailed step-by-step description (read README.txt) on how to create a bootable recovery update SD card.

I do recommend you to simply use the SD_Firmware_Tool included in the archive (it's pre-configured) and load the included Android 6 sdupdate.img. Then boot your unit using this SD card. The result should be a working Android 6 recovery.

If your recovery works again you might either get a full Android 6 update.img (e.g. the mentioned HA Android 6 ROM) and apply it via Android 6 recovery. Or you might replace sdupdate.img on your SD card with the Android 8 one, reboot your device and after Android 8 recovery is installed download and apply a full Android 8 ROM (update.zip).

I strongly recommend you first to try getting a working Android 6 again:

Use SD_Firmware_Tool with Android 6 sdupdate.img

Insert SD card to your unit and boot it, wait for the installation to complete

Put full update.img of latest Android 6 HA ROM on another SD card

Flash update.img from Android 6 recovery

You are obviously mixing many things here and you seem still to ignore the difference between sdupdate.img and update.img. You cannot simply put sdupdate.img on an SD card and expect it to do anything. You can use sdupdate.img only to load it in SD_Firmware_Tool in order to prepare an SD card and yes, it's doing more than just copying sdupdate.img onto the card. If you look at the partition layout it creates on the SD card you will see that the FAT32 partition containing sdupdate.img is preceded by an "empty" space of > 100MB. This area will be populated with boot information and images (boot, recovery...) which allows to device to boot from. So yes, you need to use the tool to prepare a bootable SD card.

Also note that restarting the HU via ignition does not help as the HU will go to standby only if it runs an OS. So make sure you either remove power entrely or you reset the HU (keep pressing reset until lights start flashing and become solid).

If you're unsure, create a bootable update SD card using SD_Firmware_Tool as described and then unplug the main plug from the back of the unit. Then insert the SD card and re-plug the unit and power it on (turn on ignition). This will for sure enforce a cold boot.

So again, please read the instructions and follow them precisely.

The only way your device could be broken where you potentially cannot recover from would be broken MCU firmware.

Try avoiding to copy any dmcu.img on SD cards while trying to recover your ROM.
[MTCD Software Development] typos1:
That looks like the board behind the tft, I d try any others on the mobo first if you can find any.
[MTCD Software Development] Al Ferro:
Those are the only ones that i think would take the sd card readers, there is only one more empty connector , but it is smaller with 6 pins same connector that the touch screen digitizer uses.
[MTCD Software Development] ikerg:
I don't think the partition sizes were the same for MM and O
[MTCD Software Development] typos1:
Theyre not, but MTCD ROM Builder makes one large partition if its in FUSE mode, which may get round the problem.

Have you read the thread I linked to earlier ?
[MTCD Software Development] marchnz:
Quite right, rom builder needs an input img file. You might be able to recreate with the zip, analysing the script which applies it - or - thanks to [MENTION=7329495]xdamember2[/MENTION], I hope to have extracted a full nand image within a couple of weeks.

Stay tuned.
[MTCD Software Development] PekeMM:
Based on my years of exp. and dealing with Chinese manufacturers I was just compiling all the info we have at the moment. eg. They said around that time that new 4GB SoMs will support Oreo (I guessed at time they tested it with Beta 2) but when RTM Oreo went out it is not the first time they changed last minute to rise requires for Oreo that broke Update support on Rev 8.0 SoMs and Nand needed to be fully re-fleshed due the partition issues and as we do not have full nand dump we can't make anything ATM, but this is going into right way, it will just take more time.

I guess all this would be evaded if we had access to SoM at time they found out that existing SoMs have issues with upgrade. I'm not in hurry anymore as from Pics I see UI for Oreo is ugly. So I will wait for custom UI. I'm currently playing with better iGO NextGen UI optimization and Loading speed.
[MTCD Software Development] KoTiX2:
have anybody tried to mount the system image in linux using mount loop command ?
[MTCD Software Development] ikerg:
I asked Dasaita to dump the Android 8 image by using rkDumper, as they have the "machine" (as they called it) to preload the Android image directly to the board

More info of rkDumper on:

https://xdaforums.com/general/rooting-roms/tool-rkdumper-utility-backup-firmware-t2915363
[MTCD Software Development] xdamember2:
I've determined with the USB Info app, the nic is a separate device but the other usb ports are on a single hub. Not sure about the other questions. The GS mainboard provides a solid 5V on the USBs.
[MTCD Software Development] typos1:
Yes, I meant take an MM ROM and try and make an image by using the separate images from the Oreo update.

Well your experience and compiling didnt help !- The ROM was in Beta 2 testing not the SoM.

We dont yet know if the Oreo SoMs are a different revision or not.

Even if they are, repartitioning the Oreo ROM will make it work on other RK3368/PX5 SoMs, just as repartitioning Nougat takes it work on all RK3188/PX3 SoMs.

All MM ROMs work on the 4Gb SoMs as well as the 2Gb ones.

Youre getting your manufactures confused - HCT make the SoMs and do the dev work, not the headunit manufacturers. No one has spoken to HCT, any headunit manufacturers saying Oreo would work was just repeating what HCT told them, as I ve said before.

Youve obviously only seen images from one manufacturer - several have made little or no changes in their UI for Oreo.

It isnt an image, it an update.zip, thats the problem.

What have HCT told Dasaita about Oreo ?
[MTCD Software Development] PekeMM:
That is what meant, pour wording on my side. That fact itself proves taht upgrade from MM -> Oreo should be possible.

Soon I'll need to take out the using from dashboard to connect reverse camera and then I'll open it to see where to put and how to connect my 10Band Hardware EQ on AMP Chip so I'll take pics of SoM and its revision due the fact I have 4GB PX5 from Dasaita.

Isn't that the point of what we are trying to archive here?

That is a fact, one of the reasons why I ordered 4GB SoM.

Exactly my point and exact place where we stand here and what we are trying to archive in order to make working that they initially stated it will work. No matter if it was just relay MSG from HCT.

Can you point me to other Oreo UI, I have not seen any screenshots other that one ugly where I would like to have the cleanest UI as possible.
[MTCD Software Development] dud89:
Any ideas on how to root? Tried Kingoroot and keeps getting an error. Would like to a backup through terminal emulator but need SU. Here's some pictures of the unit I received from Dasaita:
[MTCD Software Development] warata:
I also purchased oreo-PX5, but soc is overheating and it's in trouble.

https://www.aliexpress.com/item//32793688798.html

How's your unit?
[MTCD Software Development] KoTiX2:
I successfully converted the dat ROM files using sdat2img:

https://xdaforums.com/android/software-hacking/how-to-conver-lollipop-dat-files-to-t2978952

Then used the usual tools to extract the files from system.img.

I can see that the launcher is the one from android 6.0 hct ui with the 3 vertical hct widgets.

I installed some apks in my px5 unit to see if there are significant differences from android 6 versions but they crash when trying to run them.

;)
[MTCD Software Development] xdamember2:
Once the unit gets warm it slows down. I saw Antutu scores below 20k. Since then I added a fan and it is never below 40k. I surmise the temperatures you see are determined by the throttling of cpu frequency.
[MTCD Software Development] warata:
I guessed that.My unit also experienced frequency down so hard to open the settings.apk.

Is the fan you installed inside the unit?Can you show me pictures?

Anyway thank you for the reply.
[MTCD Software Development] xdamember2:
Here's a picture. I think I've uploaded it before. It's a Silenx 60mm fan attached to the heatsink with foam tape. There's still space for a DVD drive above it.
[MTCD Software Development] typos1:
You have made an Oreo ROM from the update.zip ?

EDIT: sorry, re-read your post - you mean you installed some Oreo apps on MM.
[MTCD Software Development] typos1:
I have seen one with a different UI, all the others I have seen have the same UI as MM - this is standard for MTCB/C/D/E manufactures when the Android version is updated - usually they keep the same launcher, with only minor changes to the UI (ie settings takes on the look of the new settings app in the Android update).
[MTCD Software Development] ArgonautPollux:
Hm, mine is MTCE_GS_V2.76b_3 with a December 25th build date
[MTCD Software Development] typos1:
OK and your point is ?
[MTCD Software Development] pedroof:
Has anyone tried installing the OREO rom using Flashfire?

I know that FlashFire has an option to flash OTA files, so thats why I am curious as to whether it would work.
[MTCD Software Development] SkyBeam2048:
I agree in general but my Klyde unit here also has the SD card reader soldered to the same board which also holds the touch button sensors and LEDs which is connected to the display controller board via single flat-flex cable.

But this also means that also in this case the flat flex connectors are not purely used for card readers. So I think it's possible that one of those connectors contain an SD cardreader interface but the pinout might be different. Moreover I can see on the pictures that the empty connector on top left might very likely not be populated as I see lots of components not equipped on the board (questionable why they even bothered equipping the connector then). Perhaps also the SD controller is completely unequipped.
[MTCD Software Development] sibeng:
thanks for your explanation, sorry i forgot to tell you, before my first post, i have downloaded and do what you and kumarai explain in readme.

but since my HU can not recovery update from that SD card, then it happened my mistake changed the file name. and I started posting on this thread for help

All the order of update commands before the HU recovery is broken I have done.

Exactly your readme, step by step no more and less, I know how that files should not be mixed in sd card

My actually problem is unable to boot from sd card, and now how to reset HU

But I will read your readme more deeply, thank you
[MTCD Software Development] typos1:
Ok, I ve seen 8 pin ones onthe board before.

Yes, thats precisely why I said trying anything on the mobo first would be a good idea - cos any connector there is more likely to be for sdreader only, rather than for it plus buttons/knobs. :)
[MTCD Software Development] scorillo_ro:
My impression is that there are circumstances when at least some units won't boot from sd card even after cold boot (complete power cut).

I'm now in such situation. I can't enter recovery anymore and the unit is not booting from sd card either.

From my memory the way my unit was booting from sd card was after selecting reboot option from recovery mode with the sd card already inserted in the reader.

I'm now following this thread trying to recover my unit:

https://xdaforums.com/android-auto/mtcd-discussion-questions-development/px5-stuck-bootloop-t3635412
[MTCD Software Development] SkyBeam2048:
OK. I wonder how such a situation is constructed. As of my understanding PX5 first seeks for a locally attached SD card. If found it will mount it and try to boot from it. So when there is a valid bootable SD card in the slot there is nothing which prevents the PX5 board from booting from it, not even a defective NAND flash.

I don't say it's impossible but I just can't construct such a scenario in my head right now to soft-brick PX5 with no way to recover from via SD boot.

Sure a bricked firmware on MCU is a different story but there is a separate thread on it and this should not prevent PX5 from booting from SD either.

The OTG thread from [MENTION=4974080]marchnz[/MENTION] is brilliant and very helpful for low-level recovery, development and/or dumping. It has been written way before we had known about a working SD firmware tool as of my knowledge. So up to then this was the only way to re-flash/recover a broken PX5 NAND flash.

I am just in preparation of a factory-clean SD card where I will try to use the SD firmware tool in the archive I provided to create a bootable Android 6 recovery upgrade card. It never happened to me yet that the device refused to boot from a valid SD upgrade card. So I am thinking about what could be the reason for it. But granted, if there is any possibility to push the PX5 SoM in a status where it does not boot from SD any more, then OTG is probably the correct way to go forward. I am personally thinking about constructing a raiser-board to be plugged on the SoM header between the MTCD board and PX5 SoM which provides OTG. This would simplify development and allow me to OTG-flash any board without further modification (neither MTCD board nor PX5 SoM modifications required).
[MTCD Software Development] scorillo_ro:
I've tried two different sd cards, one of them was the one from which I successfully upgraded from android 6 to 8.

Tried different sdupdate.img files using Kumarai's provided tools and steps to create the bootable sd card, including android6 stock and Malaysk's. Even tried using both sd readers of my unit.

I was unable to restore either version 6 or 8 of recovery, that's why I guessed the unit is not trying to boot from sd card anymore. Or it may boot, but I can't imagine why it can't restore the recovery partition...
[MTCD Software Development] SkyBeam2048:
Also [MENTION=4974080]marchnz[/MENTION] reported in his OTG thread that he was unable to recover a PX5 device from broken NAND (not sure in which way broken) by booting from SD which seem to have worked for PX3. So the only thing I could imagine is that RK3368 first reads some code from NAND (boot block?) and this one instructs it to check the SD card for bootloader information next and if it fails continue in NAND. So if the NAND is corrupted it might fail to check the SD card.

I wonder if it's possible to dump/log the boot process. Not sure if there is a way to do it via OTG or if there is some kind of JTAG interface to the RK3368 in order to get a serial interface to debug the boot process. Anyone knows?
[MTCD Software Development] typos1:
Attached is a pic of my GS main board with the sdcard connectors visible, just in front of the SoM. Specifically for [MENTION=5431613]jtheg[/MENTION], but for interest for anyone without an sdcard slot who wishes to update to Oreo. I m sure they ll work, I ll add an sdreader later and post results.
[MTCD Software Development] Al Ferro:
Yeah, same connector and ribbon cable from my EONON head unit that fits empty connectors on my Hot Audio head unit.
[MTCD Software Development] typos1:
There are no Eonon units, Eonon are a seller, they sell a lot of Klydes and I have an old Klyde unit with a similar connector, so I guess your other unit is a Klyde ?

I havent tried it yet, but it looked too big.
[MTCD Software Development] jtheg:
right i see them both now so where do we get an sd reader and ribbon from???
[MTCD Software Development] Al Ferro:
Thanks , good to know about Eonon head units. That's all i knew about them . By the way , where is ikerg with those pictures of the sofia motherboard's sd connectors:D?
[MTCD Software Development] typos1:
Ebay. I m making a custom unit for my car using this unit and I m going to separate the front from the rest of the unit, its connected with one ribbon cable and I bought a longer replacement to the same spec from a Chinese ebay seller, after I ve tested the sdreader slots later I ll upload thespecs of the cable and you can search for one.

Dunno, you should be able to find them without help though, theyre pretty easy to spot and even if you have none on the mainboard you should be able to use the ones on the front board.
[MTCD Software Development] jtheg:
Excellent cheers
[MTCD Software Development] Al Ferro:
I would like to go for this option Marchnz , since i connected the dual sd card reader from my other head unit to my Dasaita unit, and nothing worked or was detected by the android system.:good:
[MTCD Software Development] typos1:
You tried every connector on your unit ?
[MTCD Software Development] Al Ferro:
Every single one (there are not too many available).
[MTCD Software Development] 01grander:
So Bluetooth or Wi-Fi doesn’t work? Or just certain modules? How can I tell? My radio is a A-media auto(1024x600 s). It shows MTCD_kgl_v2.36_2 and the build begins with px5.

Sorry if I’m lost but I’ve never done anything major with Android, much less my stereo.
[MTCD Software Development] Conan_pg:
Also on my MX px5 2g after update In bluetooth oreo does not work, and today I do not work the voice of the Sygic navigator.
[MTCD Software Development] typos1:
Attached are pics of the cable type and number of pins (12).

Any pics ?
[MTCD Software Development] babak_1274:
Question

But, how can i make a bootable map from an update image?

I didn't understand this part.
[MTCD Software Development] janusz12561@gmail.com:
Here you have everything shown step by step.

https://xdaforums.com/showpost.php?p=75508634&postcount=156

Oreo update

It's dangerous, you can break the device

Extract the archive to the root directory of the disk

1. On the SD card Create bootable disk - CreateCD, selecting the image to create from the folder Android-6 / firmware_new.img

2. After creating the disk (SD card), delete sdupdate.img from the disk (SD card)

3. Copy to disk (SD card) from Androud-8-sdupdate / sdupdate.img

4. Insert the disc (SD card) into the SD slot in the DVD and restart

5. When installation is complete, remove the card

6. First download: Picture with an inscription on a gray screen, wait for Erase (1-5 min.)

7. Copy the update from Finish-UpdateZIP-recovery-Oreo / update.zip to a clean (different, new) drive (SD card)

8. Go to recovery and install the update

9. Restart

A little improved maybe it will be better understood. I apologize to the author.
[MTCD Software Development] sibeng:
Thank you [MENTION=4768815]scorillo_ro[/MENTION]. Now I have friends with the same problem. sorry yesterday I can not explain well this problem because I use google translate.

[MENTION=3556393]SkyBeam2048[/MENTION], so there is a possibility my unit can not update from sd card, I tried it, even when the unit condition has not been broken, sdupdate.img can not run after full restart, then I have wrongly tried to rename sdupdate.img to update. img for the system to recognize, and bricked it. my unit is Dasaita PX5 HA2106-V600, 4GB.

by the way, i was looking at the whole hardware in my head unit, and found a bit of confusion in sd card slot, as in the picture i added.

is it normal to connect 2 pins like a mark in the picture or maybe a residual solder error?

Thank you
[MTCD Software Development] typos1:
That doesnt look right to me, have you got a soldering iron ?
[MTCD Software Development] sibeng:
yes, I will try, it seems this is added a little iron connector, not just tin solder