yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] Ingmar46:
Hi All,

So, I have a Wondefoo PX5 4gb ram 64gb rom radio which is bricked i guess.

Now after 2 months suddenly i have a black screen and only the buttons light up. I have had contact with the seller, and they send me the RockChip factory tool and the firmware image. When i load this firmware in the factory tool, it says in the tool that the image is:

Firmware ver: 9.0

Loader ver: 2.65

Chip: RK330A

When follow the procedure from the seller i get an error: test device fails, and the radio still doesn't work. The procedure is as follows:

1. connect laptop to radio via usb and male to male usb cable

2. hold power button

3. turn car on acc mode (turn key)

4. still hold power button for 5 seconds

5. rapidly push the button (on-off-on etc.)

6. now the radio should be in load mode (but i only see maskrom mode in the factory tool.)

7. load the image and reboot.

When I finish the above steps i get the test device error. I believe this comes either:

-the image is incorrect and for a RK330A chipset, and not A35 chipset as should be in a PX5 (correct?)

-I don’t access the right mode for the radio as i don’t see 'loader' mode in the factory tool. (the procedure with the power button doesn’t work?)

The seller is now advising me to buy a new PX5 board, but I’m not sure it is a hardware problem. Could anybody help me? Does anybody have the right image? When i search for the Firmware i only find downloadables for .zip files, and i need a .img file for the factory tool.

How do i acces the recovery mode on this radio? I've tried everything i've read now:

-holding the power and reset button, release reset after 10 sec while holding power button, releasing power button after 5 sec

-disconnect all power, hold power button, connect power while holding power button, press quickly on off after 5 sec

It seems the only thing getting a response is quickly press the reset button, then the button lights come on and thats it. Only when i connect both BAT + wire and ACC wire to 12v i get a response and get into Maskrom mode in the factory tool.

Greetings
[MTCD  Android Head Units Q&A] marchnz:
Is this an MTCD unit? If it is, try following the detailed recovery steps listed in the thread. If it's not, the concepts are the same when using the rockchip tool. It's all there.
[MTCD  Android Head Units Q&A] Ingmar46:
Looking at the specs I assume it it is : octacore PX5 4 gb ram 64gb rom. Is there anyway how to identify an MTCD unit on its hardware?

When I look at the opening post it talks about making the OTG cable, but since I can already recognize the radio unit via the USB in the Factory tool and see its in Maskrom, wouldn't this mean I have an OTG connection via the back side built in port? Or is this something different?

I want to make sure i've tried all the possible ways to restore the device without having to open it. For now i have tried to flash via the built in (OTG?) USB with this result:

Ive also made a Boot SD card with Rockchip Create Upgrade Disk Tool V1.53 but no response from the unit what so ever.

Is the procedure you wrote in the opening post, different from connecting to the USB outlet on the rear of the device?
[MTCD  Android Head Units Q&A] marchnz:
You dont own an MTCD. Souns like you might be struggling to understand the number of posts about this, can ID from the hardware and a wiki. You can try this non MTCD approach here, which appears to be your unit

https://xdaforums.com/showpost.php?p=81930477&postcount=100

I haven't validated I dont get the ADB steps, as a simple partition or .img recovery should work for any RK based unit. Suggest taking further queries into the above thread.

The article lists updating MCU - dont do that. You want to flash the Android Firmware. Rockchip tools can only flash full .img files or partition by partition images.
[MTCD  Android Head Units Q&A] Ingmar46:
Thanks for the reply, I will give it a try.
[MTCD  Android Head Units Q&A] bilodemir:
Px5 MTCE

I uploaded the image of android 6 "firmware new.img" with the px5 maskrom usb method androidtool. but there is still a black screen. In addition, when you hold down the power button for 10 seconds, the lights flash and reset takes place.

which roma maskrom method should blink.

Or what can I do differently.

Thanks.
[MTCD  Android Head Units Q&A] kauedg:
Have you had any luck making this work? My unit (Eonon GA2168SR, RK3399, PX6) is stuck in a blank screen after my car hit a pothole. Maybe some short erased the mmc's boot partition or something.
[MTCD  Android Head Units Q&A] kauedg:
My unit (PX6 RK3399) has the same back plate but I had no luck on connecting it to the pc.
[MTCD  Android Head Units Q&A] kauedg:
I've seen some tutorials where a OTG resistor is removed and my boards has one of those, I'm not sure if I should unsolder it.
[MTCD  Android Head Units Q&A] marchnz:
This thread is about MTCD units.
[MTCD  Android Head Units Q&A] rigattoni:
[MENTION=4974080]marchnz[/MENTION]

Hi,

I got a MTCD and try to get it back to live, but I always get an error message:

Any idea to fix that???

The unit was complete down, no recovery

Got it working now...

I used the RKDevTool v2.71 and was able to get it into MASKROM.
[MTCD  Android Head Units Q&A] marchnz:
Great result, well done. Any tips from your experience you might want to pass on to others?
[MTCD  Android Head Units Q&A] rigattoni:
Yes, sure... Took me some hours yesterday to find the way to get it knocked. Tried different RK-tools, but always the same result.

First of all I need to mention, that I use RKBatch tools since a couple of years for other devices now... but this PX5 almost drove me crazy... nothing worked as expected, the contacts for the tweezer big and available...

Even with RKDevTool 2.7.1, I first had the same issues

Hint:

Use pins with 0.5mm diameter, otherwise you will damage the contacts.

My experience:

In short: My fault was to not use the built-in button for activating the MASKROM in RKDevTool 2.71.

I needed to connect the SOC without using the tweezer in LOADER mode and then use the button "Go Maskrom".

That switched the SOC correctly.

Otherwise I always got the message "Found one MASKROM device", but that changed nothing, I always got the IDB failed message after a minute.

After connecting in LOADER MODE and using the MASKROM button I was able to flash the image with Android 9 to get it back to life and I could mount it back into the radio and was able to flash the firmware and MCU.
[MTCD  Android Head Units Q&A] Ruzbynen:
Hello guys.I attempted to flash a MCU with some kind of a sound patch everything was the same as mine it was a MTCE_LM.I flashed it and my unit stopped booting, but if I let it sit lets say 30 mins and I hook up power to it and press the power button it may boot.I got it to boot two times and the second time I got into settings and pressed MCU update it got me to recovery and I tried to re-flash MCU from the SDcard insted from a USB and I think that this was my mistake, because the MCU didn't get flashed and I am in the same thing now. I've been trying to get it to boot for the past day and nothing.I tried to make a SDboot card but I can't seem to find any files for it.I tried hooking up a USB keybord no success too.When I keep holding the power button the key backlight flashes three times and I let go and press again but nothing.Thanks, any help will be really appreciated! :)
[MTCD  Android Head Units Q&A] typos1:
Doesnt sound like an MCU problem, sounds like an Android problem, have you tried flashing a ROM ?
[MTCD  Android Head Units Q&A] Ruzbynen:
[MENTION=456516]typos1[/MENTION] Nope I didn’t.Why would it be the ROM? It is on the official ROM, it never gave me an issue till I flashed this MCU.
[MTCD  Android Head Units Q&A] typos1:
Well nothing youve said sounds like an MCU problem. But if it is an MCU problem youre in the wrong thread - this thread is for ROM problems.

Why dont you go into recovery manually and try another MCU ?
[MTCD  Android Head Units Q&A] Ruzbynen:
That's exactly what I want! I can't go into recovery, I've tried everything.One time out of 1000 it booted into Android and from the settings I attempted a MCU update.I got into recovery but I reflashed the MCU from the SDCard insted from a USB drive and the flash did not complete successfully I think. My unit is a Erisin one PX30 MTCE_LM. When I hold the power button for a 10 secs the key backlight starts flashing and I press one time, two times or three times, still nothing. I tried over ADB with the PC still nothing, I also tried with a USB keyboard with R ALT + Prnt Scr + E.

EDIT: I think I found out that the unit has a RESET button! I am gonna try to use it!Gonna keep you updated! :)

EDIT2: Still the same, I plug it into power, (ACC,12V and GND) hold the power and reset button together 5s, let off the reset and keep holding the power down and still nothing.Any help will be appreciated, my head is gonna blow up, for the last 2 days I spent all of my day to try to fix this thing.I tried SOM OTG but I think my cable is not correct.
[MTCD  Android Head Units Q&A] kon10:
Hi i have one problem with my 1 Din unit. it all froze up one day and wont power on. i have change the Px5 board with a older px3 board and it was working fine. The problem is when i try the OTG Flashing the device comes up in MASKROM state but when i try to flash the update.img file i get error message "download firmware fail"

What am i doing wrong? Sadly i dont know what version i get because of it being dead. but on the board it says HTC-PX5-REV13 and was shipped with android 9. Is the board completely gone?

Best regards.
[MTCD  Android Head Units Q&A] marchnz:
Try formatting flash first. Will need to specify the .IMG and then format. If that doesn't work out, try another version of Android tool. Their code is consistent (buggy!) with the headunit coders :)
[MTCD  Android Head Units Q&A] kon10:
I have formatting flash and that worked but same result when i try update.img. I have read your ”guide” and downloaded the img file you suggested. It starts download for 1% then error Message. But i Will try a few different versions.

When i flash the update.img file is that the full android system or do i need to do something with usb/sd cards or Will it just boot normally after this if i get it to work?
[MTCD  Android Head Units Q&A] kon10:
I have now tried 3 different versions of the android tool but on v2.3 and v2.35 i only get test device fail and nothing else, the same with Rockchip batch tool. i have remade my usb cable and tried it on 4 different computers with both windows 10 and 7 with the latest rockchip drivers. all the same, and on RKdev tool v2.74 i can Erase flash successfully and start upgrade but it will fail on Downloading 1%.

And i think maybe the bootloader is gone as it starts in maskrom mode immediately and not the loader mode.

I did get a zip file from the seller with firmware but it is not a .IMG file and i dont know if it is usable in this situation.

What can i try next?
[MTCD  Android Head Units Q&A] marchnz:
As a test, could you try taking a full backup via USB the redscorpio rom extract tool?

This will tell us if all is ok with your cable.

That said, I think the cable is probably ok, maybe you're unlucky and the nand is bad, but let's find out.
[MTCD  Android Head Units Q&A] kon10:
When i tried that i get "found maskrom Device (RK3368 2207:330A #10" Rockchip device not in MCS or LOADED mode.

I have now tried to flash Hal9k_Mod_3.x_upgrade_to_Android_9.0 sdupdate.img via RKDevTool_Release_v2.74 and it went successfully. but not with other versions as it will error on test device fail. it will still not do anything if i connect it to the headunit again. No recovery or signs of life. But if i can flash that .img file it cannot be totally dead? Am i using a wrong update.img file and that is the fault with download error?

Can you maybe upload a update.img file that you have used with success?

Can i try to flash a new bootloader and see if it will go back in LOADER mode again? If so how will i do that?

Sorry for all the questions but i am totally new to all this.
[MTCD  Android Head Units Q&A] giostark:
Some one else had the wifi broken after the unbrick ?

Could be really related to the lose pins . I used the arduino cables as many of those have made the OTG work.

Can really an aluminium foil solve the issue?

As stated by this other user the software ask for different hardware.

My USB cable work properly. I can update zip files or explore them after the firmware installation.

Is also worthy update the MTCE to the last version?

Did you found a solution for this issue? Me too seems to have the same behavior . After brick my Erisin MTCE_LM_V3.01c , I managed to OTG the chip and reinstall a stock Firmware , but now no more Wifi. Even putting on the same ROM as the original one.

Maybe Erisin have made some hardware change , and also the software is a little bit different.

So did you change the chip or have you modified the software?

Thanks for your time.
[MTCD  Android Head Units Q&A] marchnz:
Yes.

No.

Resolve the DIL header connection issue and your wifi will be restored. Trace pins with a digital ohm or continuity meter. Be sure, don't guess.
[MTCD  Android Head Units Q&A] giostark:
EDIT:

Hi Marc, thanks for the attention.

Now this is weird, I tried right now to flash the Malay_mod-3.2 that fail because a wrong signature and NOW after the reboot the wifi is on and working LOL .

Yesterday I managed to bend a little the pins for make them touch a little more against the insertion. But the wifi was dead.

Now I'll try to put on some other ROM for see what happen.

Technology !

I'll keep you informed ...
[MTCD  Android Head Units Q&A] giostark:
Boh, I flashed an other ROM and wifi still dead, so... I reset the unit and eureka the wifi is back again! So I missed the step of reset :/

Damn, this would be a mandatory attempt.

Thanks anyway Marc.
[MTCD  Android Head Units Q&A] woggles:
Hi all, I have the Dasaita MAX10 PX6 1280x720 model and to stop screen stuttering I was asked to upgrade and flash a DMCU.EXT with "screen:18" in the .EXT file.

That worked fine with their firmware, but it was still buggy so I used the OTG method to flash the HCT Android 10 firmware (planning to upgrade to Malaysk Rom). After flashing successfully the screen is now blank :(

Even in recovery mode.

https://youtu.be/bCUVQ8WM9tE

So I figure the HCT firmware doesn't support the screen:18 that is now programmed into the MCU. Is there anyway I can unbrick this thing? I can connect successfully using RTKDevTools.

Is it possible to flash an older MCU using RTKDevTools, or will I need to beg users to upload an .img of the latest Dasaita firmware that supports the "screen:18" MCU configuration?
[MTCD  Android Head Units Q&A] typos1:
HCT are the company who make the SoMs, so all MTCD/E units are "HCT", the HCT firmware is just a standard ROM with no modifications, other software like Dasaita's, is the same basic ROM with a few minor changes, so its not correct to say it isnt compatible with what you flashed.

What MCU are you on ?

Have you tried a bootable sdcard to get it into recovery ?

You say you flashed successfully, but the screen is now blank, what makes you think the flash was successful ?
[MTCD  Android Head Units Q&A] woggles:
I'm on MCU 2.62 which was flashed along with DCMU.EXT that contained "screen:18". I think that Dasaita added specific code that checks for that screen type and HCT one doesn't contain that code so fails to display anything. I think its a configuration value that it can't process (my theory anyway).

I will read up on using a bootable sdcard to get into recovery - I think recovery is loading but I cant do anything with it because the screen is also blank. See the YouTube video above - the LEDs behave exactly as they would when successfully booting into recovery.

I think the flash was successful because I got no errors when flashing (see screenshot). I have flashed the HCT image before when I was on MCU 2.58 (what the headunit came with).

More theory but I think the only way to get this working is

Flash the old MCU without the DMCU.EXT setting without the screen

Somehow change the screen:18 configuration without the screen

Install Update.zip to upgrade to the latest Dasaita firmware version (that worked with the screen:18 config) without the screen

Get hold of a full .IMG of the lastest Dasaita firmware (that worked with the screen:18 config) and flash it using RKDevToolkit
[MTCD  Android Head Units Q&A] typos1:
2.62 ? Thats a very old MCU, I d be wanting to flash a much much newer one than that, particularly if I was using Android 10.

The ROM doesnt have anything MCU related in it, the MCU just changes how it displays the screen - upside-down, rotated, different resolutions etc so I dont think, personally that that is the problem - any RK3399/PX6 MTCD/E ROM from any MTCD/E manufacturer will work on your device.

To test whether your theory is right, try an Android 8 or 9 bootable sdcard and see if you can get into 8 or 9 recovery, if recovery is actually working you could also flash a different MCU in recovery with the screen blank if you can remember which buttons to press and how many times.
[MTCD  Android Head Units Q&A] woggles:
Sorry MCU is v3.62 (latest). If I just insert a flash drive with the dmcu.img and not the dmcu.ext will it remove the custom screen setting? Can the ROM not read the screen settings off the MCU?

Edit. Good news is that when I take the sd card out after trying to upgrade the MCU it has a bunch of Android files on it so I'm pretty sure everything but the screen is working. Also, the radio works when I press mode a few times on the steering wheel.

Could someone please confirm the inputs in version 10 of recovery?

I have tried touch touch long touch (upgrade MCU) touch long touch (from usb) touch long touch (yes).

I put version 3.62 of the MCU image on the flash disk with dmcu.ext with contents screen:12. Still no luck but I'm feeling positive!
[MTCD  Android Head Units Q&A] woggles:
After sitting in the car pressing the reset switch blindly for over an hour with different dmcu.img and dmcu.ext I somehow managed to get a picture on the screen. I tried to update the firmware but it wouldn't boot so I stupidly flashed the HCT firmware again and I'm back to where I started. I can't get the recovery screen to show again.

Could someone please take a picture of the submenus of the HCT recovery? I have no idea how many times I need to scroll down to update from the USB drive and if there is a confirmation menu afterwards.

Does anyone know how I managed to get recovery to show?
[MTCD  Android Head Units Q&A] typos1:
Theres no such thing as an HCT recovery - Android 10 recovery on an MTCE unit is the same for all ROMs.

I guess you ll have to start all over again and make a note of what MCU .imgs and .exts you flashed, clearly flash a different 10 ROM next time. Although before doing that you should wipe data/format flash and see if it boots after that.

I told you in an earlier post how to get into recovery with a bootable sdcard, its the best way to do it, some other methods are attached.
[MTCD  Android Head Units Q&A] woggles:
Thanks for the help - I managed to blindly flash the MCU with a DMCU.EXT with "screen:10" after taking a screenshot of the recovery. For anyone who ends up with the blank screen, in android 10 recovery to flash new DMCU.IMG with DMCU.EXT, copy to USB drive. Then once in recovery with no screen press reset 4 times, then long press, press twice then long press. The lights should flash on and off while its updating MCU.

This screen configuration is a dangerous setting to mess with!

screen:10 works with the HCT4_rk3399_9.0_IMG(20191125) (in the wrong resolution for my unit), but doesn't work on the Dasaita rom after upgrading.

screen:12 is blank for the HCT4_rk3399_9.0_IMG(20191125)

screen:18 only seems to work with HA3_rk3399_10.0_ota(20200915)升级包 and later, blank screen on HCT4_rk3399_9.0_IMG(20191125)

One last question: is the screen configuration setting required? Is there a way that I can clear it to increase the chance of it working across different firmwares? I have tried to flash with "screen:" in DMCU.EXT but that failed.
[MTCD  Android Head Units Q&A] typos1:
Glad you sorted it.

This is the first time I ve ever heard of a screen setting being different for different ROMs, it may be something to do with your unit being the rare 1024x720 res, not sure, but I d settle on a decent custom ROM like Malaysk's or [MENTION=5092263]Hal9k_[/MENTION]'s (I recommend Hal9k's) and you shouldnt need it to worry about it again. Hopefully.
[MTCD  Android Head Units Q&A] woggles:
Thanks - it's 1280x720 which is relatively new, so it probably just wasn't supported on older roms. I'll wait for Hal9k to come out with an Android 10 version of his mod and then I'll def give it a try.
[MTCD  Android Head Units Q&A] typos1:
Sorry, I meant 1280x720.
[MTCD  Android Head Units Q&A] RayLen:
I had problems to boot my system after doing some **** to my system.

With the help of you guys here I managed to reflash my HU and it booted up and WORKED!

I had the PX5 model with the MTCE_LM MCU and the HCT PX5 V4.0 SOM... so I had the same hardware as some of you guys here.. luckily.. and it WORKED...

thanks a lot to all of you once again.

Especially to

marchnz and to scorillo_ro
[MTCD  Android Head Units Q&A] Akuma666:
Hi To The Android Guru's,

I have a Dasaita PX5 unit that got bricked when I tried a factory reset. Unable to get into Recovery Mode (RM) as the lights on the soft buttons blink but will not let me invoke RM. The unit does not have a SD-Card Slot. After a lot of searching and reading on this forum, found MarchNZ's OTG upgrade thread.

The unit was running MTCE_HA_V3.14_1 with Android Version 8.0.0 provided by Dasaita. It is an Octacore 64-bit CPU / 4 GB RAM / 32 GB Disk

Fabricated the OTG cable using

R1-2.2K

and

R2-3.3K

. Connected the SoM board to Windows-7 Professional machine after loading the drivers and the board got detected on the first try. Downloaded the following to flash the bricked PX5 unit.

1) Downloaded firmware: px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew.7z

2) Downloaded Tools: tools-master.zip

When I try to flash sdupdate-A8-Kumarai.img using the RK Tool, the process stops at "Wait For Loader Fail" step. Attached screen shot for better clarity. Tried this multiple times after "Reset Device" & "Erase Flash", but the process stoped every time at the same point.

Not sure what I am doing wrong but any help coming my way at this point will be much appreciated.

Unfortunately, due to the XDA upgrade, a few of the threads that I was going through are not accessible as of now.

Thanks in advance.
[MTCD  Android Head Units Q&A] marchnz:
Sounds like you've followed the process to the letter.

The device is in maskrom mode, did you force that, or did that happen by itself?

If self, try another version of the tool.

Also, just to try, try erasing using an Android 6 version first.
[MTCD  Android Head Units Q&A] Akuma666:
Answering your question - The device is in maskrom mode, did you force that, or did that happen by itself? - (The device was automatically detected as a MaskROM device)

You were spot on with your recommendations

. I was able to connect the SoM as a Loader Device with AndroidTool_Release_v2.43 (I was using v2.69 earlier). I then tried flashing sdupdate-A8-Kumarai.img but it failed at "Murex Reset Device" step.

Next I tried flashing it with Android 6.0 as per your second recommendation and the process succeeded 100%.

With Android 6.0, the SoM was recognised as a Loader Device. I then tried flashing it again with sdupdate-A8-Kumarai.img, hoping to get to Android 8.0 and it failed.

The SoM is now again stuck as a MaskROM device and none of the RKDev tool versions (tried with v2.43 / v2.58 / v2.69) are recognising it as a loader device.

Request your recommendation again to find a way out of this situation and get the SoM detected as a Loader Device.

Thanks in advance.
[MTCD  Android Head Units Q&A] marchnz:
Try partition by partition method after wipe via Android 6.