Develop Bugs

Upgraded to 5.1.1 now only see a Blank Screen - Music and volume works

Hi,
so I am kinda new to this and wanted to upgrade to 5.1.1 below is the initial information.
Its a Roadmaster AN-111 GMC (if it matters)
It was MTCB - KSP 2.86
upgraded to MTCB KSP 2.89(KSP_11-28-2016_1.99_dmcu.img)
Firmware was 4.4.4_11032016
I installed the KLD - 2.1.1 december update
now the system boots up but does not show any display, if i plug in a USB it starts to play songs. All hardware button BEEP when i click so does the buttons on steering. I
I can go into recovery but I continuously receive the no sd card - cant post a picture yet
any chance of recovery please?

Hello,
Are you sure the MCU upgrade you did was to KSP 2.89 ? The filename you gave says something else: KSP_11-28-2016_1.99_dmcu.img (notice the 1.99 in the filename).
That would mean you did a MCU downgrade. Try flashing the MCU back again (i have KSP mcu too, not sure which version, i may be able to help you).
Regarding 5.1.1 update, i have the same behavior. I do not see the "desktop" with all the icons, but i see toast messages, popups, the "preparing to shutdown" window, so, maybe display driver problem ?

Need MTCE_LS_v3.07_01 dmcu.cfg urgently pls, bricked unit.

//MTCE_LM not LS, can't edit the title anymore.
Changed customer version from 1 to 3 and after reboot, i have no screen and no buttons working.
Only after car power is cut off (5-10min), the unit comes back but shuts down within 10-15 sec, not enough to quickly go to mcu config and change back to "1". Then nothing works, as if it doesn't get power anymore. I unplugged it and tried to hook up a miniHDMI cable but there's no connector on this board....not sure i can even get to recovery, but i'll try again tomorrow.
I have an older v3.06 LM MCU but no working config, so i hope to get into recovery somehow and flash both.
I suppose any LM MCU version would do, along with a CFG file, as long as it's version 1 (recognizable from _1 after mcu version or check in factory settings-other-customer version "1")

does anyone have an idea where to change customer version in a dmcu.cfg using hex editor?
or is it possible to connect and edit the MCU values stored on the unit itself?
it's a PX5 MTCE LM unit, ultraslim format.
https://www.aliexpress.com/item/Eun...-Stereo-GPS-for-VW-Passat-B6/32866279122.html

Pls help! Installing software from scratch on MTCE Px3 2GB

Hi guys,
your help please! I have a Px3 2GB head unit with the following:
- MCU MTCE_KGL_V2.70_1
- Androd 7.1.2
I was trying to update to the latest Malaysk version 5 and somehow during installation an error message appeared and the unit is now unusable. When turned on only the initial screen (Navigation system) is visible and nothing else, so I can only switch it either off, or on and it stays on that screen. I have tried to install a new software through USB and microSD but nothing seems to work.
Do you know how I can install the software again so that I can use the unit?
Many thanks for your help!!

Problems with my Headunit - Bootloop

Hello,
I have very big problems with my car radio at the moment.
I bought this car radio.
Code:
amazon.de/gp/product/B07BFS29HZ/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1
1st OS: Android-8.0
2. CPU: Rockchip PX5 ,Cortex-A53, Octa-Core
3. RAM: SAMSUNG DDR3 4G
4th Flash: 32GB
5th Radio: NXP 6686S
6. GPS: SIRF III
Seventh screen: Capacitive and multi-touch screen
8. video decoder: 1080P HW
9th WIFI: Built-in
10th DVR: USB camera (PC standard)
I have already successfully used the car radio until the car radio has restarted and is now hanging in a boot loop.
It is no longer possible to start the car radio.
Please see the following video:
Code:
photos.app.goo.gl/cbKFMqfr5HDhDTc87
I then tried to reset the car radio to the factory settings using the reset button, but that didn't work either.
It reboots again and again.
Then I found out how to get into the recovery mode.
I made them a picture with the messages
Code:
photos.app.goo.gl/56SphjLcg2a5bwQb8
Apparently he can't find a file to successfully boot the car radio.
I suspect that if I put a correct kupdate.zip file on an SD card and boot the radio, it could work again.
Unfortunately I don't know enough to find the right file or I don't want to risk a brick of my radio if I use the wrong file.
Can you please help me get the car radio up and running again?
Many thanks
Best regards
mandragora

Help identify ST LINK points in old Joying?

Unit is a Joying JY-UQ124 PX3 - https://www.amazon.com/gp/product/B00XGEYU26
No idea what specific MCU and all that it is now as I bricked it several years ago when I accidentally put the wrong firmware on when attempting to go back to stock from a Malaysk ROM, and now only get black screen on power on with front panel lights on. Can't get into recovery, attempting to restore via SD card isn't working - never seems to start loading from the SD, screen just stays black.
Bought a new radio, put this one on the shelf, and now I'm trying to recover it again via the ST-LINK. Except that the only 5 holes empty on my board aren't marked, and I suspect it may actually be an unpopulated USB connector.
The PX3 SOM is a card edge RAM style connector, so I can't easily attach to header pins there either.
Do I have options here for recovery, or am I SOL with a paperweight on my hands?

SOM or MCU, photo show SOM. What is bricked, som or MCU

I'm _guessing_ it's the MCU? If the SOM gets bricked, wouldn't I still be seeing _something_ on the screen at boot?
It's been a while since I played with this one last, but I seem to recall that I accidentally tried to push the update image from my Sofia unit into this one, and didn't catch my mistake until after it was too late to do anything about it.
But honestly, I'm not really sure what exactly is wrong with it at this point, nor do I remember exactly what I did to it prior, other than trying to roll back to stock from a Malaysk ROM, and it didn't boot afterwards.