yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] typos1:
Sorry, but you really made a very, very silly decision - for far less than the cost of 2 SoMs [MENTION=4974080]marchnz[/MENTION] could have bought yours back to life, absolute madness.
[MTCD Hardware Development] marchnz:
Thanks mate, I get why he wants to buy a new when considering the lead times - purchasing a SOM might only be a few weeks to days if using expedited shipping vs the cost of expedited return shipping to/from NZ. All good here :)

The last one I did was for an Australian member, so not as costly freight wise and shipping times.

I do get a buzz out of helping and surprised so far that none of the units had hardware faults, these SOMs seem to be quite robust and generally forgiving.
[MTCD Hardware Development] typos1:
Postage to NZ for such a small package isnt that much and even if he wanted it quick he could send you his to repair and sell on to finance the new ones, just total madness, I really dont get it, especially when you offering to do it for free. :silly:
[MTCD Hardware Development] Al Ferro:
No offense to you, but that's my decision . :good:
[MTCD Hardware Development] Al Ferro:
I have some news, I was still playing with that problematic Som and since today I received in the mail a small USB male to male adapter, I wanted to test it out with one of my head units that did not have the single usb cable or port working on the back of the radio unit. So I plugged it in into my PC and after several attempts , it got connected and I properly installed the drivers, but now I have a warning message from android tools that the "Download Boot Failed"
[MTCD Hardware Development] Al Ferro:
:cool: Finally SUCCESS...... After trying and trying, I was able to make it work with my previous method above (I never gave up, it was complicated that the Som did not want to respond, but I still need those two new Soms that I bought, they are for other head units that need them, thanks marchnz).:D
[MTCD Hardware Development] marchnz:
Bewdy. What was the issue for the benefit of helping others...

There we go, still 100% SOMs recovered :)
[MTCD Hardware Development] milyczlowiek:
Who can help me? I am ready to send an integrated circuit for repair. Who will be kind to take it? Address please.
[MTCD Hardware Development] Al Ferro:
Never Quit trying (if you know what are you doing) if one way doesn't work, try a different approach. This Som was acting so weird with the short USB cable and resistors method, so I thought give it a try with the USB otg single cable from the back of the head unit, even though in the end I was able to recover the Som, it was still connecting and disconnecting at times.
[MTCD Hardware Development] typos1:
Youre correct, it totally is your decision and I havent taken offence, I just think you are mad for choosing to pay out 10x more to buy 2 new ones rather than the shipping only to have them repaired. :silly:
[MTCD Hardware Development] Al Ferro:
Why should I be mad? Just because you don't know the reasons why I had to buy new ones, buddy stay on topic , don't be a troll.
[MTCD Hardware Development] typos1:
I have already explained why, talking about whether someone should send their SoMs to [MENTION=4974080]marchnz[/MENTION] for repair or spend money on 2 new ones instead is very much "on topic", I have been following this thread since it started, in no way could I be described as a "troll".
[MTCD Hardware Development] scorillo_ro:
I had some spare time, so I used it to play a little with my old KLD PX5 unit. If you remember, that unit has a full OTG connector on the back, so I can play without pulling the SOM out of it.

I was able to switch from Android 8 to Android 10 so smooth that I wanted to share this with you.

put android in ADB mode using 'adbon' password for "Factory settings"

put SOM in LOADER mode using the 'Switch' button

put SOM in MASKROM mode using the 'Go Maskrom' button

use Upgrade Firmware

use usb stick to upgrade to the latest OTA

Doing all this using a Windows7 Virtual Machine running under my Kubuntu Linux laptop is another nice thing...

PS It looks like Android 10 won't connect to a WiFi network containing the '$' character in the password
[MTCD Hardware Development] janusz12561@gmail.com:
I repaired my tile, I live in Środa Śląska

Ja naprawiłem swoją płytkę, mieszkam w Środzie Śląskiej
[MTCD Hardware Development] ferenc1:
Hy. I bought an MIC AV8V4 PRO HU with PX5 SOM. Now i know that my car CAN-bus system was short circuit, and its broken my HU. First when i noticed the problem, the HU screen was black but the buttons light, and the 15sec press hold pwr button the buttons flashing. I try flashing SOM, i did an OTG cable, the operation was successfull, but the HU dont working same. I bought an ST-Link V2 programmer, and i try recover the MCU, the operation was succesfull but the HU dont working, but now the lights also dont working and dont flashing the buttons when i hold press 15s pwr button.

What can i do?

Thank you and sorry for my english.
[MTCD Hardware Development] alfondehesa:
Hard Bricked PX6

Hi! I hard bricked my new PX6 by installing custom firmware that was not meant for Px6s. Screen is black, can't access recovery or bootloader. Could this help me fix the brick? I apologize, but I am not well versed on flashing or anything related for that matter. I could solder up the USB, but I am unsure where to go from there. Could anyone help me flash system, boot, bootloader and recovery?

I already have the firmware (android 10 px6) on an update.zip, which I think comes with all .img but the system.img

Any help is greatly appreciated! Thank you!
[MTCD Hardware Development] alfondehesa:
Okay, I am at the point where I can upload firmware to the HCT PX6 using the cable, but I can't seem to find any full partition extracts for PX6, nor any separate working partitions to flash onto it. If I try flashing some updates I find here and there (they're update.img files), my unit ends up going on boot-loop with no access to recovery (stuck on the android multimedia system screen).

I looked in the drive and there was a PX6 update.zip file but I suspect it is not the full partition dump.

Would anyone that had the same problem be kind enough to share their partition dump or image file or backup that they used to bring their PX6 back to life?

Thank you! Any help greatly appreciated!
[MTCD Hardware Development] scorillo_ro:
https://yadi.sk/d/umCvHqCDzHccr/RockChip PX6 Android 10/CHS
[MTCD Hardware Development] alfondehesa:
Does that one also work for HCT devices? I saw on that drive they have a couple of HCT versions but when I try those, for some reason it stops flashing at 2% and says that it was successful :S
[MTCD Hardware Development] scorillo_ro:
extract update.img and flash it in maskrom mode

you can also find update.img for android 9 there

---------- Post added at 07:04 PM ---------- Previous post was at 06:59 PM ----------

When you regain access to the recovery menu you can use any of the OTA updates you like from any vendor
[MTCD Hardware Development] alfondehesa:
Okay I'll try tonight. The previous images I've flashed using AndroidTool didn't let me access recovery somehow. I tried every button combination on the radio but I wouldn't boot on recovery. :confused:
[MTCD Hardware Development] scorillo_ro:
If you manage to flash the image successfully and you are able to see the SOM in 'Loader Mode' in AndroidTool, then there should be no reason for being unable to access the recovery menu. Just try different key / reset combinations ...

Or you don't have connectivity for all the SOM pins when you put it back
[MTCD Hardware Development] alfondehesa:
I tried your suggestions:

When I try to flash Android 10, it only gets to 2% and then tells me it has been a success (I know it hasn't so I don't even bother re-installing the unit): https://ibb.co/gRRFXLj

When I try to flash Android 9, it gets to 100%. I install the whole thing in the car, and I get a quick screen saying Erasing (https://ibb.co/CzZGyrT) and then it gets stuck on this screen: https://ibb.co/MhmPHyt

Important note: After flashing the images (no matter which version), the unit always reboots in loader mode. I've also tried with many many versions of Android 10 and Android 9. Also, I've tried many combinations of reset/power to try to get into either recovery or bootloader, but none seem to work. The unit just reboots onto the Android P screen and stays like so forever.

Does that sound like a pin socket problem?? If so, what pin do you think it could be? I'm honestly ready to slap aluminum foils on all female pin sockets, I've been battling with this PX6 for two weeks now.

Thank you so much for your help!
[MTCD Hardware Development] guybaor:
rockusb not found

after a bad root process my px5 rk3368 died!

iv'e done everything as guided in first page.

no matter what i try - SOM not found!!!

i'm using win10 pro 64bit.

what am i doing wrong?

please help me

Guy
[MTCD Hardware Development] marchnz:
Force MASKROM as detailed in the thread
[MTCD Hardware Development] guybaor:
[/QUOTE]

When i plug the USB there is blue light coming from the SOM. So it is on but not recognized by pc.

Also, I don't know how to short circuit the SOM.

Where the twizzers should touch??
[MTCD Hardware Development] marchnz:
When i plug the USB there is blue light coming from the SOM. So it is on but not recognized by pc.

Also, I don't know how to short circuit the SOM.

Where the twizzers should touch??[/QUOTE]

Post pics. Crystal ball not working :)
[MTCD Hardware Development] guybaor:
Post pics. Crystal ball not working :)[/QUOTE]

https ://ibb.co/Z14pnRp

https ://ibb.co/dgmx3nv

https ://ibb.co/kDdPqf1

https ://ibb.co/BNF9YY3

https ://ibb.co/pf1Hr4Z

https ://ibb.co/xFm2SJp

https ://ibb.co/XF3ZFGJ

https ://ibb.co/r7nFM3c

remove the backspace after the "https".
[MTCD Hardware Development] scorillo_ro:
You must remove the radiator and look for the maskrom pads on the other side of the SOM ;)
[MTCD Hardware Development] guybaor:
how do i remove it? is there clips? or i just pull it out?
[MTCD Hardware Development] scorillo_ro:
Yours look different than what I've seen. Take a good picture...

Mine have some screws

---------- Post added at 09:21 AM ---------- Previous post was at 09:15 AM ----------

Oh, I see, you must have already unscrew them. Just try to pull the radiator, it must be the thermal paste that keeps it.

---------- Post added at 09:34 AM ---------- Previous post was at 09:21 AM ----------

Are you sure it is a MTC SOM? Mine don't have any lights on it

---------- Post added at 09:50 AM ---------- Previous post was at 09:34 AM ----------

clearly not MTC

take a look on page 53

https://xdaforums.com/android-auto/...eadunit-mod-recover-flash-som-t3766892/page53
[MTCD Hardware Development] guybaor:
What does it means? I need different connections?
[MTCD Hardware Development] scorillo_ro:
YES and we don't know them :(
[MTCD Hardware Development] guybaor:
There's no Post regarding my SOM?
[MTCD Hardware Development] typos1:
Probably not in an MTC forum, there have been occasional posters with non MTC SoMs looking for help here, try reading the entire thread and seeing if any of them had the same non MTC SoM as you .
[MTCD Hardware Development] guybaor:
i checked! my SOM is MTCE!

see attached picture!

https://ibb.co/hm1zd31
[MTCD Hardware Development] typos1:
Ok, all the info you need should be in this thread then.
[MTCD Hardware Development] guybaor:
do i need to paste it back after removal?
[MTCD Hardware Development] scorillo_ro:
If you have skills, you can try to trace the pins on your own and help the community with your findings.

You can find the power pins with the SOM connected to your powered on unit using a multimeter, but you probably already found them (you have that blue light on).

For the USB data pins you can try to trace the lines to the USB HUB chip starting from one of yorr USB ports, then you must track the lines from that USB chip (on the mainboard) to the android SOM (with the unit powered off).

In theory, if you know the power pins (+5v and -5v) and the USB data pins (data+ and data-), you can use the maskrom mode to access the rockusb device (the SOM).

I guess you can also try to enter the maskrom mode (short the maskrom pads while you power on the SOM - not connected to the unit - and release the maskrom pads after applying the power, keeping it powered on) and then try to connect the USB data wires to different SOM pins until your computer detects the device, but I guess this approach can be dangerous, as it can damage the SOM!

Anyway, even if you will be able to see the device in AndroidTool, you will need a full image of your android firmware, which we don't have...

Good luck!

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

Your first pictures matches the SOM on the page 53 identified as not a MTC one but S32F0_XinRc !!!
[MTCD Hardware Development] scorillo_ro:
Look at the attached pictures. MTC SOMs have the HCT_ prefix in their names.
[MTCD Hardware Development] guybaor:
Where does in says HCT?
[MTCD Hardware Development] scorillo_ro:
Look again, first time the picture size was too big and it was not uploaded
[MTCD Hardware Development] typos1:
If he has a GS MTCE MCU then he has an MTC/HCT SoM.
[MTCD Hardware Development] scorillo_ro:
I had a feeling that the last picture is downloaded, not taken by him, especially that he told his unit has died after a bad root.

But if the picture is real, from the past...
[MTCD Hardware Development] typos1:
I was going more by the fact that he said it was MTCE than the picture.
[MTCD Hardware Development] guybaor:
Let's make some order!

The last picture is taken from a video of hu exactly like mine!

https://www.isudar.com/products/car...or-vw-golf-tiguan-skoda-fabia-rapid-seat-leon

And it says on menu MTCE.

Anyways i removed the radiator from the SOM.

See attached picture.

https://drive.google.com/file/d/1PcRfDOX1ZroGkeR6K6QhCX2StStFGDb1/view?usp=drivesdk

With blue light:

https://drive.google.com/file/d/1Pjx6ENGUtRaiU-J4vbydesBrlmGVNbTc/view?usp=drivesdk

What's next?

Guy
[MTCD Hardware Development] alfondehesa:
If anyone is having the same problem, here's what I did to fix it: https://xdaforums.com/android-auto/...icked-hard-t4136897/post83117435#post83117435
[MTCD Hardware Development] guybaor:
Update, i tried maskrom and there was windows chime but driver not detected.
[MTCD Hardware Development] scorillo_ro:
Do you have the latest rockchip drivers installed?

Tried to switch usb data wires?
[MTCD Hardware Development] milyczlowiek:
I was able to upload android 9.0 from update.img via otg, Now the "N multi-media on vehicle navigation system" screen is constantly displayed and nothing else. Does that mean wrong android version? My device worked with android 8 by default, but nowhere in your links can I find udate.img version 8 for px5.

is it possible to change the folder from meta-inf and boot.img etc. in update.img? How?
[MTCD Hardware Development] marchnz:
Is unit an MTCD/E/P?
[MTCD Hardware Development] milyczlowiek:
I don't know anything about it. My device is: ND0572B. Originally, the manufacturer uploaded:

4.4.93+

Rocky@hctr930 #239

Fri apr 27

Px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180503.142728 twst-keys

Now after many attempts I managed to connect via otg, I uploaded some update.img with android 9 or 10 (i dont know, because on https://yadi.sk/d/umCvHqCDzHccr

it's a terrible mess). Then the "N multi-media on vehicle navigation system" screen was constantly displayed and nothing else, and I got a compatible package from the manufacturer, tried to update via micro sd from update.zip but signature verification was failed and error: 21

Now it's hard for me to figure out which, but I don't have an easy connection to the coreboard. the device is visible, it connects through the mask room, but in androidtool everything is at 00000 and errors pop up when loading, checking the device. I have the impression that it was so close, I probably made a short circuit ... F>>K
[MTCD Hardware Development] guybaor:
Yes, installed!

Question, i connected the SOM to the main board and to the pc (thru usb male to male), and there is a red light on the main board . *Attached.

What does is means?

https://drive.google.com/file/d/1PzksRqPMPlUlx1yT1lrvUo3ES_ogIcF2/view?usp=drivesdk

Thank you
[MTCD Hardware Development] marchnz:
As [MENTION=4768815]scorillo_ro[/MENTION] and [MENTION=456516]typos1[/MENTION] have correctly commented, your unit is not not an MTCD unit, the pin-outs and diagrams do not apply to your unit. Refer: https://xdaforums.com/showpost.php?p=81645565&postcount=527

Also see: https://4pda.ru/forum/index.php?showtopic=973677

MTCx units don't have a 'red light'.

There have been others with non-MTCD/E units post and have been successful using the general process for recovering non-MTCD/E (HCT) PX5 ROMs, perhaps have a read through.
[MTCD Hardware Development] guybaor:
hele are some pictures of the main board and the connections sceme on the HU!

help me find the USB data pins (data+ and data-) please,

https://drive.google.com/file/d/1Q8...9iCq6G7A8BGzs835sRnMBRzkt54u/view?usp=sharing

https://drive.google.com/file/d/1QBr9Nh-88WlTDrr5Q7vYKpAVaPM-8TMp/view?usp=sharing

thank you
[MTCD Hardware Development] scorillo_ro:
make the links public
[MTCD Hardware Development] guybaor:
Try now
[MTCD Hardware Development] scorillo_ro:
The connector labeled A (USB3) may be an OTG connector. Do you have an USB cable that fits it?
[MTCD Hardware Development] guybaor:
Yes. But i thing it is connector for 4G usb. is it possible it is also used as OTG usb?

https://drive.google.com/file/d/1QNC4IKizXGLjlpaqE_LUmcZsGAatbEtg/view?usp=sharing
[MTCD Hardware Development] scorillo_ro:
Maybe, you must try for yourself. As we told you, we are not familiar with other types of units.

This link is also not public
[MTCD Hardware Development] scorillo_ro:
If you want to find the USB pins of your SOM, you must do what I told you in that post. Use a multimeter to find the USB chip on the motherboard. It should look like the one that I highlighted in your picture with the red circle (that is not the one you are looking for, it is an audio one). One of its legs should be connected to one of the pins that I highlighted in your picture with green or white (green looks to be USB data+ and white USB data-).

After you find the USB chip, you must track and find two of its legs connected to two of the SOM pins. Those will be the ones you are looking for to use with [MENTION=4974080]marchnz[/MENTION] OTG cable in maskrom mode.

https://i.stack.imgur.com/gG80F.jpg
[MTCD Hardware Development] guybaor:
https://drive.google.com/file/d/18obzZi1BlM93Jaxv35F4QEyYDMjpi4e6/view?usp=sharing

the usb 1,2,3 sockets on the HU are marked with the yellow arrow, so i believe the orange/green are the connections to the USB chip (marked in white rectangle) and the two legs going to the SOM pins are in red arrow.

maybe it's correct?
[MTCD Hardware Development] scorillo_ro:
You found all this only by looking at the lines (visual only)? You should really use a multimeter.

What is written on that chip? Use that information to find (google search) if it is an USB hub for a minimal confirmation if you don't have a multimeter...
[MTCD Hardware Development] guybaor:
YES, Thats the one.

https://drive.google.com/file/d/1Q_YHVs1wVs6gckNxq-HgdWwflXKktfvy/view?usp=sharing

what about the two pins coming from the resistors? recovery and usb detect, how can i locate them ?
[MTCD Hardware Development] scorillo_ro:
I'm not sure (I'm guessing here) but those might not be required in maskrom mode.
[MTCD Hardware Development] guybaor:
Ahhh i gave up. Nothing seems to work.

The best i could achieve was windows chime.

Can i replace just the SOM? What are the chances the main board is damaged?

Thank you for all your help
[MTCD Hardware Development] marchnz:
You're leading this one :)
[MTCD Hardware Development] guybaor:
Than help me lead. I check with the company, they insist my mcu is MTCE v3.4

---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------

See attached conversation.

https://drive.google.com/file/d/1Qy9-PEVoadubG85GYGcYe3D9AxmreiYc/view?usp=drivesdk
[MTCD Hardware Development] scorillo_ro:
In this case, because they are responding to your questions, ask them for help.
[MTCD Hardware Development] guybaor:
Already did. They send me an update file. I'm trying to figure out with them how to use it since my hu is pretty much deceased!
[MTCD Hardware Development] typos1:
Isudar do sell MTCD/E units, the picture you posted yesterday of the mobo had what looked like an MTCD/E header, but strange long screw things that looked far to high for the SoM to fit.
[MTCD Hardware Development] guybaor:
Update, the supplier engineer says that the main board is faulty and not the SOM.
[MTCD Hardware Development] typos1:
How would they know ?
[MTCD Hardware Development] guybaor:
I have no idea. What are the chances that the main board is at fault? And not the som.
[MTCD Hardware Development] scorillo_ro:
If the only mistakes you did was on that root attempt, I would say ZERO
[MTCD Hardware Development] guybaor:
Is there any way to check which one is faulty?
[MTCD Hardware Development] typos1:
Get another unit, send your SoM to [MENTION=4974080]marchnz[/MENTION].

Have you actually posted any pics of your SoM out of the device ? I ve seen one of it and the mobo.

Does the SoM have 4 holes in it that those mounts go through ? Cos that does not look like any MTCD/E SoM I ve seen.

What revision version is it ? - Theres always a revision number on an MTC SoM.
[MTCD Hardware Development] guybaor:
The seller said it is MTCE v3.4

These are actual pictures of my main board and som.

https://ibb.co/x7GTDkj

https://ibb.co/8d0zgvW

https://ibb.co/TgGNmxd

https://ibb.co/ZKTgqCK

https://ibb.co/0hhcq2s

https://ibb.co/yYTNGhn

https://ibb.co/zPjJCw0

https://ibb.co/XDhy27H

https://ibb.co/wyjNnpw

https://ibb.co/3Bf15GS

https://ibb.co/ccjrNJz

https://ibb.co/tXPKzdY

https://ibb.co/8z6J1LT

https://ibb.co/WxCJ1gY

https://ibb.co/NTXDRFQ

https://ibb.co/QDwqQTc

https://ibb.co/NxKY0JQ
[MTCD Hardware Development] typos1:
As I thought, it has four holes right through it, not seen an MTCD/E SoM like that before, indeed, because of those holes it wouldn't fit any other MTCD/E device and ALL MTCD/E SoMs are interchangeable - MTCD/E SoMs have three screw holes (ie NOT large holes). Plus "HCT" does not appear anywhere on it and nor does "revision . . ."

So, although it looks very like an MTCD/E SoM with four holes drilled through it, I dont think it is. Many sellers sell several different unit types Isudar may have got mixed up.

Or this is a very new revision to MTCD/E units that no one here has heard of yet.
[MTCD Hardware Development] marchnz:
Not an MTCx/HCT SOM, see previous post with link to 4pda covering this variant:)
[MTCD Hardware Development] marchnz:
We have established with almost certainty that your unit is not an MTCx/HCT SOM.

Try asking seller for a schematic/circuit diagram, you never know your luck.

As per your PM, I don't have a jig for your SOM, so to figure out USB/connections I would need the entire unit. You can send that to me if you want.

If you don't want to send it, understand that the people replying to you here do not have your unit. This recovery solution is for MTCd/E HCT SOMs which are different to your unit and are very likely to have different connections.

The options I see you have are:

1. Convince seller to replace under warranty

2. Reverse engineer pin outs to your SOM and attempt to connect/recover.

3. Convince seller to send you schematic diagram. We can then try and give you advice from that.

4. Send me the entire unit and I can attempt from reverse engineering.

5. Find a local skilled in electronics and board level repair/reverse engineering to assist.