yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] SilentO:
Finally had the time to attend this however I still got USB device not recognized.

Attached is my setup.

PX5 2GB 16GB from Dasaita.

Im trying to recover the unit after a successful download using Android Tool but the HU does not turn on.

15:34:34 785	Android Tool v2.3.9.0 for android start run

15:35:57 082	Layer<1-3>:Test Device Start

15:35:57 097	Layer<1-3>:Test Device Success

15:35:57 114	Layer<1-3>: Download parameter...

15:35:57 445	Layer<1-3>: Download uboot...

15:35:57 924	Layer<1-3>: Download trust...

15:35:58 409	Layer<1-3>: Download misc...

15:35:58 923	Layer<1-3>: Download resource...

15:35:59 205	Layer<1-3>: Download kernel...

15:36:01 355	Layer<1-3>: Download boot...

15:36:04 040	Layer<1-3>: Download recovery...

15:36:10 099	Layer<1-3>: Download backup...

15:36:16 898	Layer<1-3>: Download security...

15:36:17 473	Layer<1-3>: Download system...

15:40:31 871	Layer<1-3>: Download metadata...

15:40:34 107	Layer<1-3>: Download vendor...

15:41:54 790	Layer<1-3>: Download oem...

15:43:16 667	Layer<1-3>: Download frp...

15:43:16 893	Layer<1-3>: RunProc is ending, ret=1

15:49:30 258	Android Tool v2.3.9.0 for android start run

16:13:37 603	Android Tool v2.3.9.0 for android start run

Red wire is 5.0v and when connected it's 3.9v

Orange is 3.3v and when connected it's 3.2v

Black is ground

White and green is data and when connected it's 3.18v

Sorry can anyone help me see what I'm doing wrong?
[MTCD  Android Head Units Q&A] SilentO:
Screwed up big time. Wrong pins but still can't get it to recognize the SOM.

Please help
[MTCD  Android Head Units Q&A] marchnz:
Helpful detailed info, cheers.

Looks like the SOM successfully flashed, perhaps theres a problem with the headunit main board. SOM is looking good.

Once the SOM is back in place and all screws in, what voltages are seen at SOM supply and also ground points (continuity)?
[MTCD  Android Head Units Q&A] SilentO:
5V at pin 1,2,3 but no voltages at pin 20 or 28.

0.5V at pins 29 and 30.

pins 1,2,3 have 0 ohm

pins 4,5,6 have 0 ohm

sorry but is there anything else that i can look at?

or is this dead?
[MTCD  Android Head Units Q&A] SilentO:
installed the SOM back and reconnected to the car again.

pin 1,2,3 measured 5V

pin 4,5,6 is 0V =GND

pin 9 = 3.3V

really lost

if only i can get my computer to recognize the rockchip for me to flash the firmware.

appreciate any suggestions,
[MTCD  Android Head Units Q&A] Migueliyo85:
I have a rev8.0 SOM. How can I enter to maskrom Mode?

first I do the short as shown in the photo and then connect the usb cable to PC?
[MTCD  Android Head Units Q&A] tankgod82:
Will any of this work on an FYT 6026 Board. I bricked mine and am unable to boot into recovery. It is mounted to an S200 main board. The unit is made by Rupse. Sold by several other companies. The Witson Model number is W2-222. Any help would be appreciated.

Link to photos: h**ps://photos.app.goo.gl/C1YaYLiC7WLASAK17
[MTCD  Android Head Units Q&A] typos1:
I cant see anything that looks like an MTCD/E SoM inside your unit, so pretty certain its not an MTCD/E unit.

Deffo heard of FYT units, try searching the Android Headunits general forum fo FYT units.
[MTCD  Android Head Units Q&A] tankgod82:
Yeah I've been all over this forum trying to find it. I've also been trying to get the maker to help. They blocked me on Ebay, Blocked my emails and wont return phone calls. Yes, I've even called china.
[MTCD  Android Head Units Q&A] typos1:
How long have you had it ? Youve got 6 months paypal protection
[MTCD  Android Head Units Q&A] alt.d4c:
Hi. Can you confirm please that is the way to maskrom mode for this core board px5-rev4.0? Mine is identical same date even, but i don't see a short when i touch that point with the ground, nothing happens.
[MTCD  Android Head Units Q&A] scorillo_ro:
You must short those points with the board not connected to the PC and continue to keep them shorted when you plug the USB for a few seconds, then release the short. The chimes should be heard after approximately one second and see one maskrom device found.
[MTCD  Android Head Units Q&A] alt.d4c:
I tried with a rigid wire exatly to that points many times but is not entering in maskrom mode, first short the som than plug in the usb cable. Thank you.
[MTCD  Android Head Units Q&A] scorillo_ro:
This is the right procedure. Maybe you should just try different resistors combinations.
[MTCD  Android Head Units Q&A] alt.d4c:
Yes you right, i finally success to start the maskrom mode and unbrick my head unit. Thanks.
[MTCD  Android Head Units Q&A] scorillo_ro:
:good:
[MTCD  Android Head Units Q&A] radoslavsto:
BT problem

I changed the motherboard and Flat Connection - cables on Witson multimedia W-B5762.

Installed Android is 6.0.1 (HCT_PX5_6.0 - 20171227; MTCE_MX_V2.96).

Everything works just like BT except

BT is paired with the Andoid phone, it provides a phone book, but there is no sound when dialing, and the other phone meets.

On the other hand, the A2DP application normally works and reproduces sound, as well as EasyConnection.

What could be a solution?

greeting

Radoslav
[MTCD  Android Head Units Q&A] typos1:
What BT module ? Have you checked the BT volume level in factory settings ?
[MTCD  Android Head Units Q&A] radoslavsto:
BT module MD 725 type 2

The installed Android 6.0.1 and 8.0 update also behave.
[MTCD  Android Head Units Q&A] typos1:
MD725s can give problems on 8, there are 2 types 1 and 2, cant remember off hand which gives the problem, but both should be fine on Android 6 anyway, have you checked the BT volume level in factory settings ?
[MTCD  Android Head Units Q&A] radoslavsto:
If I tried the factory settings. Without success.

It's weird that the sound is easy to use and A2 DP

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

EasyConnection
[MTCD  Android Head Units Q&A] Pyr0ball:
Hey guys, thanks for all the work you've been doing thus far.

I've got a newer unit that's unfortunately bootlooped, but the module header is completely different from all of the pics I've seen on this forum, so I haven't been able to figure out where to plug in the OTG just yet. So far I've identified both of the USB input pins via multimeter probing (this HU has two usb connections) but not a whole lot else yet.

I've attached a pic with the pins for each of those circled.

I also have another thread going right now with more pics and info.

Sadly I don't have all the info I would need as it started bootlooping before I bothered to go and look at the about settings.

I can currently still get into the OEM recovery, but it only tries to look for "kupdate.zip" and gives no other options apart from wiping, reading logs, and reboot.

Here's what I do have:

Reseller: Pumpkin

SoM: PX5 MTCD/E 4GB + 32GB NAND

Recovery environment header output:

Android Recovery
rockchip/rk3368/rk3368
9/PQ2A.190205.003/ken05181222
userdebug/test-keys

I'd love to get some assistance on this if possible. I've got a whole lab full of testing equipment and I'm not afraid of soldering/desoldering. If more traces need to get probed, I can do that too, just need to know where to start.

Edit:

It looks like the header on the right side of that picture goes to that GL850G USB hub controller, while the one on the left does not. I'm assuming that means the usb input on the left is the one I'd need to use for OTG.
[MTCD  Android Head Units Q&A] marchnz:
HI,

Not an MTC(D/E) unit, how did you determine it to be MTCD/E?

Being Rockchip, OTG method will be the same, except you will need to reverse engineer connections and for recovery, obtain either a partition dump, or vendor Image and apply it.

Good luck.
[MTCD  Android Head Units Q&A] Pyr0ball:
Thankfully Pumpkin support came through with a kupdate.zip (Which I hope contains the vendor image), but it looks like my fumblings thinking it was an MTCE may have done some overwriting of required stuff, as it's bootlooping while trying to run the update

Is there a pinout of the PX5 itself? I may be able to follow traces to their relative positions to determine which pins are for recovery, etc. I'm sure I can probe to find out which pins need 3.3v and I already found the USB data lines. I think the recovery pin will be the only troublesome one, but with a general idea of location I could probably find it.

Edit:

Looks like the kupdate.zip does indeed include a vendor image.

Would it help for me to upload the update file for others to view?

Here's the update script from the zip for reference:

getprop("ro.product.device") == "rk3368" || abort("E3004: This package is for \"rk3368\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: rockchip/rk3368/rk3368:9/PQ2A.190205.003/ken05181222:userdebug/test-keys");
show_progress(0.550000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.100000, 0);
ui_print("Patching oem image unconditionally...");
block_image_update("/dev/block/by-name/oem", package_extract_file("oem.transfer.list"), "oem.new.dat.br", "oem.patch.dat") ||
abort("E2001: Failed to update oem image.");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing trust img...");
package_extract_file("trust.img", "/dev/block/by-name/trust");
ui_print("Writing uboot loader img...");
package_extract_file("uboot.img", "/dev/block/by-name/uboot");
set_progress(1.000000);
[MTCD  Android Head Units Q&A] scorillo_ro:
I guess the recovery pin is needed to enter the "loader mode" and may not be required for the "maskrom mode"...

Another guess, from just looking at your picture, is that you could achieve the maskrom by shorting the highlighted points in the attached picture.

We don't have such a device, so you are kind of your own here!
[MTCD  Android Head Units Q&A] Pyr0ball:
Not on my own as long as you guys can still post tips ;)

I'll do some reading on Maskrom and see what I can do with that
[MTCD  Android Head Units Q&A] Pyr0ball:
I made progress!

So first off, Pumpkin is sending me a replacement SOM, so I'll have a clean one I can pull an image from when that comes in.

I was able to identify the serial output console, and I also managed to get it into the u-boot terminal. I've got a friend here at work who's got some experience with u-boot so we're gonna play around with it a little bit.

[IMG="Serial Debug Pins"]https://i.imgur.com/NJJq1Yv.png[/IMG]

[IMG="Debug Serial Output 1"]https://i.imgur.com/y5UxGPL.png[/IMG]

[IMG="Debug Serial Output 2"]https://i.imgur.com/2IdyUAF.png[/IMG]

[IMG="u-boot terminal"]https://i.imgur.com/DVvqfuV.png[/IMG]

I was also able to capture some interesting serial data from what I assume is the GPS module. Appears to just be sending satellite data over plain old UART at 9600 baud.

[IMG="Serial TX pin for the GPS module"]https://i.imgur.com/7zqsqd2.png[/IMG]

[IMG="GPS serial data"]https://i.imgur.com/Mz5FLqF.png[/IMG]

---------- Post added at 10:13 PM ---------- Previous post was at 09:24 PM ----------

Looks like you were right about the pin to short, looking at this post

I'm currently working under the assumption that my fumbling loaded the wrong kernel onto this unit, so I'm trying to load the correct one now through u-boot
[MTCD  Android Head Units Q&A] Pyr0ball:
Well I got a new android module from the manufacturer, but it seems the module they sent has the wrong video output settings, so I'm still without a working unit sadly.

In good/notgood news, I think I figured out what happened to my old module. As you can see from the attached screenshot, the eMMC chip appears to have failed. So I think I was experiencing a gradual failure on that chip which explains the progressive nature of it's behavior getting worse.

I tried getting the new module into maskrom mode, and while it's detected by RKDevTool, if I try any of the read options under Advanced Function, they all fail, so I don't think I'll be able to pull a backup of the good firmware off this thing.

I'm halfway tempted to try swapping the eMMC chips to see if that would work. I've got the equipment I need to pull it off
[MTCD  Android Head Units Q&A] marchnz:
From experience on MTC units, maskrom mode will enable you to format eMMC, but not extract contents. To extract contents or flash firmware use Loader mode. Also from experience, MaskRom is usually needed where the bootloader is screwed and entering recovery or LOADER mode isnt possible..

So.

1 - Maskrom - Format eMMC

2 - reboot into loader mode

3 - flash firmware

Nice work on identifying the serial port connections.
[MTCD  Android Head Units Q&A] opengpl:
is this compatible with this coreboard

Hey everyone, i have this android MEKEDE unit Android 7.1 (fake its 6.0) CPU: Quad core ARM 53 1.3GHz RAM:2GB DDR3 ROM:16GB Platform：MT 3561 esolution: HD 1024*600

[IMG="coreboard"]https://i.ibb.co/p27YCf6/coreboard-front.jpg[/IMG]

for some reason, the core board has black screen loop and the unit does not start anymore, i bought a new core board from the seller but it comes installed with wrong firmware so not the whole screen

is working and cannot touch some part of it because of the wrong resolution, even with a mouse i cannot update it, i ask for the right firmware for it and the seller send me this one (cannot send link new-user)

i extract it, put in usb disk and push the reset button, nothing happen, i pushed reset again and try finger the screen many time, it try to load the update but it fails as shown on the picture

seller support is terrible, he only answer once per week with useless info like are you able to unzip files i sent and then next message on the next week loool ...

the head unit does not have any button nor sdcard, its fully touchscreen with usb only so my question is anyone here know how to update the right firmware for it or is the unit core board compatible with px5 and can be flashed with otg ?
[MTCD  Android Head Units Q&A] marchnz:
Hi cross-poster,

Unit isn't MTC(x) and SOM is not rockchip PX5.

Suggest searching forums for an appropriate thread for your device.
[MTCD  Android Head Units Q&A] Mikell33:
px5-rev4.0

Hi, I tried to access the Maskmode of my px5-rev4.0 .

You said you entered the mode with different Resistors !

I trie many kombinations but i only access the Loader Mode.

Can you help me?

Greets

Michael

I cant flash any img with Batch Tool or Android Tool. I tried different Images Android 6 - 9

Test Divice success, Lowerformat Devive success, IDB success, Reset Device success

It stop all at "Wait for maskrom fail". after 30 seconds.

I changed in config.ini to 120 seconds, same problem!

So i think i cant access Maskrom.

Greets

Michael
[MTCD  Android Head Units Q&A] Pyr0ball:
Any chance you could give me a bit more detail on those?

1: Maskrom - Format eMMC:

Is that done through the RKDevTool or some other utility? I don't see a "format emmc" button anywhere

2: reboot into loader mode

Loader mode is which? I can get into uboot by hitting keys while attached to the serial console on boot, but not sure if that's what you meant. If you mean the normal "recovery" environment, yeah that I can do pretty easily, but I'm unsure how to pull the flash while in loader mode. The recovery on this unit doesn't have a backup option
[MTCD  Android Head Units Q&A] SomebodySysop:
Solder GPS Antenna to CoreBoard

To solve my bricked unit problem, I ordered a new coreboard from Xtrons. I received the Android 9 px5 coreboard. It did not come with gps antenna.

I have not taken the unit apart yet, but from the pictures I have seen of this, I can't tell if there is one wire or two GPS antenna wires soldered to the px5 coreboards.

Can someone recommend video on how to solder px5 coreboard antenna?

Thanks!
[MTCD  Android Head Units Q&A] Pacote-san:
[MENTION=4974080]marchnz[/MENTION] Im running hal9k with latest OTA 3.1.2 Oreo

How can I do a full backuyp to be able to restore with android tools?

I already got OTG connection and flashed the full oreo from:

https://drive.google.com/drive/folders/1P703unZDA_TdRzl6fjkkb-YUB-KpTViW

I just wanted to do another full backup with the latest 3.1.2 installed.

Thanks!
[MTCD  Android Head Units Q&A] marchnz:
Hi [MENTION=913999]Pacote-san[/MENTION],

Recommend using [MENTION=4582467]RedScorpioXDA[/MENTION] great dumper/extractor tool [rkDumper] . Thread is here and direct link to updated tool is here
[MTCD  Android Head Units Q&A] paulstar82:
I got xtrons px5 an I'm stuck on bootload use sdcsrd way but when try use usb install ROM nothing works even with brand new usb card any help would b welcome
[MTCD  Android Head Units Q&A] marchnz:
OTG - refer links in my sig
[MTCD  Android Head Units Q&A] paulstar82:
Take it I gotta take unit apart as don't fancy it as still in warranty
[MTCD  Android Head Units Q&A] marchnz:
they dont care. What did the reseller suggest when you contacted them for support? What else did you try from this thread that lists the options to recover, or pehaps you didnt bother to read?

Unable to recover, looks like sending it back is the option.
[MTCD  Android Head Units Q&A] paulstar82:
Still waiting as the screen has dropped so when i use as card gotta move screen up to get it out.
[MTCD  Android Head Units Q&A] aphilgr1:
PLEASE what is the process of formating eMMC? Witch tool to use?
[MTCD  Android Head Units Q&A] marchnz:
Unless you can find someone with the same device as yours - which isn't like an MTCD - and has figured out which connections to make to get OTG, it's unlikely anyone here can help. Sorry, but your device is not HCT/ MTC variant for which we have the circuit (schematic) diagrams for, which enabled me to figure out how to get OTG.

Your device is probably a brick unless you can figure how to make the OTG connections by reverse engineering the circuit board or obtaining a schematic/circuit diagram for your unit AND the full partition dump or image file for your unit. That might be a long shot.

I can try if you send it to me, no promises though and any efforts would be at least over 4-5 weeks.

If none of that sounds achievable, consider buying a replacement, this time an MTCD/E unit - suggest Dasaita (HA) or GS type.
[MTCD  Android Head Units Q&A] aphilgr1:
Thanks for trying to help.

Does it makes any difference that I am already in MaskRom mode? I only need my firmware in update.img format to flash, or a way to make my unit boot from recovery and apply from there. Am I chasing dragons?

Being already in MaskRom mode, I have 2 questions:

1. Is it possible to repack a .zip format firmware to .img format, rename it to update.img and flash? If not I need to find stock firmware in .img format. Correct?

2. is there a way to format eMMC? If my MCU is still untouched, from what I understand it is the corrupt eMMC that does not allow the unit to enter recovery mode or boot from SD. Correct?
[MTCD  Android Head Units Q&A] aphilgr1:
Yoohoo! Halfway there!

I found an STM32 Firmware on a Russian forum in .img format however ir is 2.3 Gig!!! I took the bold step and flashed it with success. My unit came back to life fully working! Problem is that firmware is for 800X480 display. Went into recovery mode but there is no option to update from usb. Only from SD Card or ADB.
[MTCD  Android Head Units Q&A] aphilgr1:
Finally I flashed stock firmware by copying it as zip on a usb stick and renaming it update.zip. Now the problem is that previous firmware updated the MCU as well but with 800X480 resolution. Now I need to flash my mcu with stock firmware or at least with one made for 1024X600
[MTCD  Android Head Units Q&A] marchnz:
MTCD/E users ignore.

As I have advised a number of times now, your unit isn't an MTCD, therefore the steps and fix do not apply to MTCD users reading here.

MTCD/E owners note: where you have a low res screen, Only a change of MCU update from one vendor to another can result in incorrect display resolution. This is resolved by applying an MCU config file, detailed in wiki (my sig).
[MTCD  Android Head Units Q&A] marchnz:
Readers note; This device is NOT an MTCD/E, the MCU identifies as an STM32, with a rockchip based System On Module (SOM).

Thanks for posting.

How were you able to achieve OTG on this STM32 MCU unit?

Please screenshot full system screen, also any detailed pics of mainboard might help identity the manufacturer.
[MTCD  Android Head Units Q&A] aphilgr1:
Sorry for posting in the wrong section, however the process would be the same for any Rockchip unit that can enter MaskRom mode, as long as the correct firmware is used: MTCE firmware for MTCE units, STM32 firmware for STM32 units and so on.

My unit was totally bricked and SOM recovery via usb OTG was not an option since my implementation was SMB with SOM soldered on the mainboard and covered by metal shielding very hard to remove. So what was left was to FORCE MaskRom mode. I think all PX based units have this capability. The trick is to have the unit connected on the PC using a male to male usb cable and short circuit the eMMC before Powering ON so memory cannot be read on boot forcing MaskRom mode. This is done by bridging two pins on the mainboard (different location for every unit - check documentation or like me, #disclaimer# go bold by trial and error) until a few seconds later, the "found hardware" sound is heard on the PC. Then you release the bridge and voila: The unit goes either in Loader mode or MaskRom mode. Using Android tool in loader mode, first and third tabs are fully functional and in MaskRom mode, only the second tab is functional from where you are able to upgrade firmware. If you are in loader mode, use button "go MaskRom" in the third tab to switch. Select compatible firmware that can only be in .img format, wait for it to load and press upgrade. Took a couple of minutes and Lazarus was alive!

Full system screen you mean Android or PC?
[MTCD  Android Head Units Q&A] aphilgr1:
Here are 3 videos I took on the procedure:

1. Bridging the pins

2. Flashing firmware

3. Booting the device

Sorry for the low quality
[MTCD  Android Head Units Q&A] marchnz:
Quick question - how did you get OTG, was the USB port already configured to allow OTG or did you have to solder a connector/trigger recovery per my thread, but adapted to your unit?
[MTCD  Android Head Units Q&A] aphilgr1:
No, no soldering at all. I just used a male to male usb. I guess it is part of the design of the chip to switch to OTG while on Loader or Maskrom mode or maybe the driver installed in windows. I found some useful info for a similar design on firmware upgrade, bootmode and Maskrom mode (translated from Chinese).

As for this

would you be kind enough sharing a link? Couldn't find it.

Thanks
[MTCD  Android Head Units Q&A] aphilgr1:
Finally Success!!!