yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] Akuma666:
Wipe did not happen using Android-6 or Android-8

Was able to load images using the partition by partition method. However, was not sure what to load under the "Parameter" and "Base Parameter" partitions, because there are no specific images for these in px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew folder. Attaching a screen shot for clarity.

The first partition "Loader" was not allowing any image load and kept throwing "Boot Fail" error.

Tried using Windows-10 (instead of Windows-7), but the result was the same.

Not sure of the next steps. The SoM still says "Firmware not found" after being detected, when trying to "Erase Flash".

Standing by for further instructions.

Thank you.
[MTCD  Android Head Units Q&A] marchnz:
Suggest a read through this forum, specifically: [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.

Just re. "Standing by for further instructions." Let me know what you've read and tried, would suggest reading through these forums. If unable to recover, you're welcome to send the SOM to me in NZ.

Cheers.
[MTCD  Android Head Units Q&A] Akuma666:
Thank you MarchNZ for sharing the links. I had gone through this thread before I started the exercise but the links were not accessible to me after the XDA Forum upgrade. I was able to access them again today through your shared links.

I feel the link you shared for the other thread is more relevant to what I am trying to do with your help. Hence I will post my queries on the other thread henceforth, if that is not a problem.

Thank you.
[MTCD  Android Head Units Q&A] Akuma666:
Hi MarchNZ, After the last stint, the SoM board was not being detected by Windows-7. Had to remove the heat sink and short the points on the PCB for the board to get detected.

Once the SoM got detected, followed your and blue1111's instructions to load image partition-by-partition and succeeded. Image attached for clarity. Thanks to you and blue1111.

However, even after multiple tries, I was unable to "EraseFlash" before loading partition-by-partition. Always kept receiving the error "EraseFlash Failed". I even tried with multiple versions of the tool but did not succeed.

I then inserted the SoM back on the core board and plugged the system back, to get to recovery, but I still see a blank screen and the same behaviour as before I started the whole exercise - I am unable to get to Recovery.

Request you to let me know what else I can try.

Thank You
[MTCD  Android Head Units Q&A] Akuma666:
Hi MarchNZ, After the last stint, the SoM board was not being detected by Windows-7. Had to remove the heat sink and short the points on the PCB for the board to get detected.

Once the SoM got detected, followed your and blue1111's instructions to load image partition-by-partition and succeeded. Image attached for clarity. Thanks to you and blue1111.

However, even after multiple tries, I was unable to "EraseFlash" before loading partition-by-partition. Always kept receiving the error "EraseFlash Failed". I even tried with multiple versions of the tool but did not succeed.

I then inserted the SoM back on the core board and plugged the system back, to get to recovery, but I still see a blank screen and the same behaviour as before I started the whole exercise - I am unable to get to Recovery.

Request you to let me know what else I can try.

Sorry, I ended up replying to my own message previously.

Thank You
[MTCD  Android Head Units Q&A] marchnz:
Did you want to send the SOM to me
[MTCD  Android Head Units Q&A] bebokoo:
Hi guys,

I got a Seicane HU that seems to be stuck in a bootloop.

I have a SOM here that I can not flash, no matter what I try.

Been trying a lot of different things in the past few weeks (including suggestions in this thread), but I can't get it to work.

It is a SOM PX5 4/64gb with Android 10 hal9k mod5, and it crashed.

I have attached some pictures, any help will be greatly appreciated.

Greetings from the Netherlands.

Ben
[MTCD  Android Head Units Q&A] bebokoo:
this is what happens
[MTCD  Android Head Units Q&A] marchnz:
Erase flash first
[MTCD  Android Head Units Q&A] bebokoo:
is it possible with android tool 2.84??
[MTCD  Android Head Units Q&A] bebokoo:
I did it with android tool and everything seems to go well until I start the HU again Erase appears???
[MTCD  Android Head Units Q&A] bebokoo:
which IMG can I use??
[MTCD  Android Head Units Q&A] bebokoo:
can someone help me i don't know how to proceed
[MTCD  Android Head Units Q&A] marchnz:
Please read this post and the thread.

Per our PM, you may send it to me, however I believe you are very close to a working unit.

https://xdaforums.com/t/px3-5-otg-n...with-a-simple-usb-cable.3766892/post-85430449
[MTCD  Android Head Units Q&A] bebokoo:
this is what happens.

Or is there something wrong with the motherboard?

how can i go on now??
[MTCD  Android Head Units Q&A] marchnz:
Looks OK to me? Wait for flash erase, say 20 mins?
[MTCD  Android Head Units Q&A] bebokoo:
ok i will try it
[MTCD  Android Head Units Q&A] bebokoo:
after 1 hour still no picture still the same

after 1 hour still no picture still the same black picture
[MTCD  Android Head Units Q&A] bebokoo:
who wants and can help me further I don't know how to continue stuck so far.
[MTCD  Android Head Units Q&A] bebokoo:
I have a HCT-PX5-Rev16(LPDDR) coreboard that came out of a Witson PX5 RVT Android 10 series radio. I tried to install the android 10 version of Hal9K on it and now the unit/radio wont boot up. I get the Hal9k logo, then an animated android logo and then it just stays there (animation keeps going so its not crashing).

I've been trying to use the otg cable method. Cut a USB cable, soldered the resistors and got the cable to work. Windows is seeing the board no problem.

Trouble starts when i try to use Androidtool V2.84 to flash the board. Androidtool gives me the "found one LOADER device" message at the bottom so it does see the board, however everything i try results in an error message. After selecting a new firmware the "EraseFlash" function under the upgrade firmware tab gives me "Test Device Fail" for example. Everything under Advanced functions gives me error messages. I'm hitting a wall and i cant seem to find a way around it. Any suggestions?

Edit1: This also happens in Maskrom.

Edit2: I found a .IMG file called PX5_A10_IGV.img . I'm able to flash that to the board and after that the board actually gives me no information using RKdevtool 2.84. When i plug the board back in to the radio the screen flashes white a couple of times and then goes black. I've flashed the coreboard with the android 10 image
[MTCD  Android Head Units Q&A] bebokoo:
it will not works.

can i the soM sent to you in NZ?
[MTCD  Android Head Units Q&A] bebokoo:
hello Marchnz

If you would like to fix it for me, would you please email me your address.
[MTCD  Android Head Units Q&A] RayRasanen:
Hi. I have a problem. px5 only starts in bootloader mode. and i can't find any information about that px5 EMCP v7.2.
[MTCD  Android Head Units Q&A] marchnz:
Post picture of mcu version
[MTCD  Android Head Units Q&A] giotses:
Hi i have a PX5 head unit with android 10 MTCE_MX RK3368.My question is if i can update to HTC_PX5_10 or HTC7_PX5_10?

Thanks.
[MTCD  Android Head Units Q&A] marchnz:
Is your device stuck in a bootloop
[MTCD  Android Head Units Q&A] giotses:
As you can understand i am a little confused about the updates.

I haven t tried yed.I want to know if it's ok to do this without any problem.Thanks
[MTCD  Android Head Units Q&A] typos1:
I ll spell out what @marchnz is trying to say - IF YOUR DEVICE IS NOT STUCK IN A BOOTLOOP A LA THE TITLE OF THIS THREAD, THEN DO NOT POST IN THIS THREAD, POST IN A RELEVANT THREAD OR START A NEW THREAD, simples.
[MTCD  Android Head Units Q&A] bebokoo:
Unfortunately I don't know what I'm doing wrong or what is wrong with my HU.

Tried factory reset several times but it won't boot.

Who has the solution for me??
[MTCD  Android Head Units Q&A] marchnz:
Check voltage on [Recovery] line to SOM. Suspect hardware issue or defective MCU is triggering SOM to go into Recovery. If that is the case, it is repairable.

I recognise my own scribbles :)
[MTCD  Android Head Units Q&A] iamhollywoodpro:
Good day I have had my Pumpkin Auto Head unit now since 2018 with a few headaches over the years that I can't ignore any longer. Mainly it freezes and crashes only option is to to a reset by powering off and back on and reconnect it to wifi and start my navigation again. Spotify and other apps just crash and shutdown along with a few other things like wifi not connecting sometimes and bluetooth working when it feels like it. I have contacted the manufacturer but all they do is recycle they're solutions by copying and pasting them to us customers. They ignore us current customers and just push newer models in frustrating, No new updates, no firmware update no Os updates. I was wondering if someone here can help me get something done as in updating this head unit so I can get a year or two more out of it as I will be purchasing a new car in that time. Until then id like to maximize the life if this head unit till then if possible. Thank you members in advance.

Processor Type: UltraOcta-T8

Android Version: 7.1.2

MCU Version: T8.3.19-11-00-453101-Universal

System version: V9.2._20180330.180B33_KED3-5 (last version provided by the manufacture
[MTCD  Android Head Units Q&A] marchnz:
Device is not an MTCD or even a PX5 CPU device, so wrong forum. Try Android Head units forum.

Suggest discarding your device and buying a genuine Android Auto device or an FYT based UIS7862 device (FYT forums)
[MTCD  Android Head Units Q&A] paljamp:
Hello marchnz,

I have a PX5 4G+64G head unit, MCU version MTCH_MX2_V3.84_1 jan 14 2022, after an update by mistake, the radio is dead, then I followed your guide to the letter, built a usb-otg cable, the windows 10 pc show rockchip in device manager, now I can flash in maskrom and now i can see recovery mode, but when i try to update with update.zip i always get the same error. What more can I do? Any reply is greatly appreciated, thanks
[MTCD  Android Head Units Q&A] paljamp:
Marchnz why don't you answer me? The HU is stuck in bootloop, maybe I wrote wrong in this post? Or maybe you don't like me? If I've done something wrong please tell me
[MTCD  Android Head Units Q&A] marchnz:
All answered in this and main OTG thread:

https://xdaforums.com/android-auto/...px3-5-headunit-mod-recover-flash-som-t3766892
[MTCD  Android Head Units Q&A] paljamp:
Thanks for the reply, I did that too, now I'm stuck on this error in the picture
[MTCD  Android Head Units Q&A] marchnz:
Flash a full firmware and not just a recovery.

First - with full firmware loaded in android tool, ERASE FLASH first.

Past that, read, try, read. If unable to resolve - you're welcome to send SOM to me in NZ.
[MTCD  Android Head Units Q&A] paljamp:
Nothing to do, any full firmware I try to install with AndroidTool, installation completed successfully but HU returns to recovery mode. I'm confused, maybe I'm doing something wrong.

P. S. how much would it cost me to send SOM to NZ
[MTCD  Android Head Units Q&A] marchnz:
Return freight only charged. Get an estimate from your local post/freight company to send to Christchurch, NZ 8061.
[MTCD  Android Head Units Q&A] paljamp:
Shipping from Italy to NZ costs €64.60, it is not convenient, I add another 30 euros and buy the SOM new, we can do this, I'll pay you a beer and explain to me how to recover the SOM. What do you say, can it be done? Thanks
[MTCD  Android Head Units Q&A] marchnz:
Sincerely, all the information that I have, is in the thread.There's no more magic or hidden information.

One a full MTCD Android .img is flashed via Android Tool, a .zip or OTA update is not necessary - the unit should boot to Android. That is unless wanting to flash an update to the same Android version update after the OTG recovery, which you would let Android boot and then update via recovery/OTA.
[MTCD  Android Head Units Q&A] paljamp:
Yes true and thank you for sharing your experience. At this point I have to give up and buy a new SOM, but it's very strange, I tried all the img updates compatible with my version of HU, AndroidTool writes without any errors but when HU restarts it returns to recovery mode screen 🤷🏻. Thanks anyway for your availability 👍
[MTCD  Android Head Units Q&A] marchnz:
Check that the recovery mode signal isn't being held by the mainboard.
[MTCD  Android Head Units Q&A] paljamp:
I don't think this happens, today my cousin brought me another similar HU but with SOM px6, I tried px6 instead of px5 and everything works, anyway, on which point should I check? Thanks
[MTCD  Android Head Units Q&A] marchnz:
Recovery pin. Should read 0v.
[MTCD  Android Head Units Q&A] paljamp:
I don't have the diagram, what is the pin recovery, you mean CTL_Recovery?
[MTCD  Android Head Units Q&A] paljamp:
I tried the oreo guide but nothing, even with oreo it returns to the recovery screen
[MTCD  Android Head Units Q&A] paljamp:
Hey guys, nobody has any other ideas to propose, I have read all the guides from marchnz and others with no success, in practice AndroidTool writes the full firmware but HU always shows the recovery mode. Is there anything else I can try?

Thank you all for the fantastic work you do
[MTCD  Android Head Units Q&A] paljamp:
Hi marchnz, problem solved, you were right, there was 2.8v on the Recovery pin, the cause was an invisible short circuit, it could only be seen under a microscope. Now everything works except the radio app, no scan and no audio.

Thank you very much, for the great work you have done (y)
[MTCD  Android Head Units Q&A] paljamp:
Radio problem solved, I tried to install various update.zip, none worked for FM radio, finally I installed this "telenav_vivid_px5_10.0_ota(20210322).zip" now FM radio works, and the interface is also very nice. But now, there is another small problem that I will solve later, it is the car logo, in the factory reset the items to select the new logo are missing. It doesn't matter at the moment, I'll think about it later. I will post the solution if I can fix it..
[MTCD  Android Head Units Q&A] IzentAlp:
Hello community,

first of all thanks to all of you for the great work and detailed tutorials so that beginners like me can access the subject of head units.

I tried to swop my Bluetooth module from MD725->RF210 to use Bluetooth on my head unit after upgrading to A10.

I upgraded my head unit to A10 and have had no Bluetooth connection any more (Bluetooth name and password blank).

So I flashed my device with different MCUs to get Bluetooth working.

In the process I changed my factory settings from 'VERSION = 1' to 'VERSION = 3' and bricked my head unit.

When I flash A10 to my SOM via OTG method and boot the system the first time in my head unit - It will boot up and I can navigate. After 1 minute the head unit shuts down and I can't restart the head unit anymore.

When I flash A9 to my SOM via OTG method I'm stuck in a bootloop with the android symbol.

I tried all version from A7 to A10 without success.

Is there a possibility to change factory settings of head unit without booting via OTG?

Any help is welcome.

I have a PX5 SOM. The previous MCU was MTCD1.98c. Now I flashed it with MTCD3.26 and can't change it.
[MTCD  Android Head Units Q&A] toldo311:
Hello All,

My Android has stuck on the logo screen, I tried to reset it with no success

Could you help me with how I can re-open it again?

System Version: TS10.1.2_20211020..104245_TW8-Theme

Thank you
[MTCD  Android Head Units Q&A] marchnz:
It's not an MTCD type unit.

Search forums for "ts10" or go to Android Head-Units forum for posts in there about TS10.

Failing that, use a hammerfor.
[MTCD  Android Head Units Q&A] Cid6.7:
I'm trying the batchtool now but unable to write to sd card as it just keeps saying failed..

Not sure if I'm using the right img file tho
[MTCD  Android Head Units Q&A] audisean:
have you tried " sd_firmare_tool " to create image on sd card ? i'd say batchtool is for pc to device flashing - sd card should hopefully be a decent quality (i got bitten by ebay fakes including usb sticks).....
[MTCD  Android Head Units Q&A] Cid6.7:
Yes I'm trying that as well but unable to find which kind of file needs to be written to it..

Is it just a "update.img" file or does it have to be the file that came loaded on the unit from new..? Every file I try just results with a "Opening firmware fail" error :(

So confusing, I have files upon files & have no clue which "should" work lol

I have a lot of flash drives from 2gb to 128gb all work 100% but still dont do any good if I dno what I'm doing LOL
[MTCD  Android Head Units Q&A] typos1:
Yes.

---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------

You just use a normal firmware image.

Malaysk has a post that says you should use the firmware that bricked it, but [MENTION=5092263]Hal9k_[/MENTION] says you can use any compatible firmware.
[MTCD  Android Head Units Q&A] audisean:
strange unless image is compressed (or corrupt) and needs unzipping etc - if it was unit not accepting then mcu.img might need rename to dmcu.img and update.img rename to dupdate.img - (mcu for system - update for android version)
[MTCD  Android Head Units Q&A] typos1:
If youre trying to recover a unit using SD firmware tool you should use the ROM ONLY, no MCU file, its the only time that you CANT flash both together.
[MTCD  Android Head Units Q&A] Cid6.7:
I run as admin choose the removable flash drive choose the firmware what else is there to do besides create..? Not sure what the Demo button does..
[MTCD  Android Head Units Q&A] typos1:
Nothing.
[MTCD  Android Head Units Q&A] Cid6.7:
Then I've got no clue why its not workin..

Is there a specific version of SD Firmware I need to use.. ?

The one I have is v1.4

I can write all day long using Rufus and ImageUSB

Its actually not even able to open the files
[MTCD  Android Head Units Q&A] audisean:
Kinda makes me think did program install correctly or did windows block some features or maybe anti-virus interfering..... try uninstall and turn off anti-virus - re-install and reboot pc
[MTCD  Android Head Units Q&A] Cid6.7:
Its weird, I've done all that PLUS used the laptop & both do the same thing.

Do you know where to get the correct .img I'm supposed to use ?

The program only accepts .img files

I've used this file

And this file

Both fail on 2 different machines..
[MTCD  Android Head Units Q&A] typos1:
Just read back through your old posts - have you got a Sofia SoM ?
[MTCD  Android Head Units Q&A] :
I have no clue what I have to be honest I've dled so many different files tryin to get this damn thing workin lol

I've got whatever are from those 2 links. Which I think are the original software & then a update to 6.0

And yes its a Sofia unit if thats what you mean.
[MTCD  Android Head Units Q&A] :
Right, well SD firmware tools will never work cos its for Rockchip devices not Intel Sofia devices.

There are 2 types of Sofia devices, MTCD MCU ones and "009" MCU ones, which do you have ?

You really need to pay more attention to things like that cos you could have made things worse and killed your unit, you also dont actually say what your problem is just "can I have a hand" and "heres what I m working with".

If you have MTCD Sofia then try the other Sofia threads in the MTCD forum, if you have an 009 Sofia then search the Android Headunits General section.
[MTCD  Android Head Units Q&A] Cid6.7:
Hahaha yeah sorry your right I guess I havent explained what happened I have a MTCD unit that I updated to the latest firmware (in the 2nd link I posted).

Flashed it fine everything workedwell, Like a dummy without even thinking I went to root it, the same way I rooted it on the previous firmware. :eek:

Well it didnt work & now I'm stuck with a unit that has no recovery & also wont boot up.

When I hit the reset button the screen flashes,lights turn on & it will connect to PC, if you let it be for a minute or 2 screen flashes again it reboots reconnects to pc lights come on & screen flashes let it be for about 2-3 minutes it just powers off.
[MTCD  Android Head Units Q&A] typos1:
Ok, as I said you need the MTCD Sofia threads, as you have a Sofia unit any threads relating to Rockchip SoMs will be useless to you.
[MTCD  Android Head Units Q&A] audisean:
Any chance you can show how you wired usb cable to U27 pin outs ? Also did you modify usb cable to make OTG cable ? My PX5 has also died and recovery is still impossible - tried usb keyboard and keys - no response. Also tried many reset and power button ways but only get 3 light flashes and screen remains dark. PX5 board worked straight away when installed so i'm guessing MCU firmware causing Android corruption - had hoped to update MCU to v1.98 but never had time (still LM_ v1.9.1)
[MTCD  Android Head Units Q&A] marchnz:
Thanks for the reminder, I have a post to update.

As my GS board was a spare, I didnt have the rear usb connector so I soldered a male cable from an old mouse (short) directly to the board, on the pins to the headunit USB connector (the GS is so much nicer than most as has lots of sockets for things like video in, TV module, TPM module etc.)

Is your board a GS with the USB switch chip? For my JY board I would have simply temporarily removed the USB pins at the SOM header and soldered the three pins required (usb -,+ and ground) to enable OTG mode cable.
[MTCD  Android Head Units Q&A] audisean:
My board has DU7085-M -1V5.0 - It has 4 usb ports at the back - last time I tried usb wiring I soldered onto som board d-,d+ and ground - removed header usb pins on board and lifted pins 27 & 28 on IC - laptop detected unknown device but that was as far as I got - drivers did not auto install.....
[MTCD  Android Head Units Q&A] marchnz:
I found guides on the internet for installing the drivers, assume you installed the driver? What was the device error code?
[MTCD  Android Head Units Q&A] audisean:
I used rockchip driverassistant v4.4 to try install drivers - don't remember seeing error codes only unkown device message - i'll have to set wires up again and look for error details tomorrow hopefully
[MTCD  Android Head Units Q&A] marchnz:
Could just be a matter of transposed USB (+,-). I had originally transposed and received a windows device code 21. Much joy when it finally connected though!
[MTCD  Android Head Units Q&A] audisean:
got wired up again - same as my last attempt - unknown device (code 43) will try another laptop tomorrow and see what happens.....
[MTCD  Android Head Units Q&A] audisean:
different laptop tried - same result - then I realised you said you connected usb to gs board and not px3 board so will resolder wires i'm guessing to usb connections coming out of U27 (d+,d- and ground) and try again.....

tried all usb connections (U27 and GL850 outputs) nothing is happening so i guess this board just don't want to play.
[MTCD  Android Head Units Q&A] audisean:
so i got my hands on a gs board ,,,, do you have a photo of usb 1 connection you did ? (I also upgraded the MCU to latest in my broken unit using px5 board from gs unit to boot unit up) (is it possible upgrading MCU would help when trying to access recovery - with working PX5 board I can find recovery screen easily in both units)
[MTCD  Android Head Units Q&A] marchnz:
Hi,

Post updated and includes USB Male cable connection points to mainboard.

Good luck.