Do the PX3 Sofia's need anything special to use this method ? It is connected to pc thru the USB but as unknown device. And how do I actually short it to which pads ? I cant find a actual pic of a px3 only px5 and mine doesnt have the same pads. I can get to recovery and flash both update and mcu, but android wont actually boot all I get is the multimedia car audio screen then it either just reboots or it goes to a blank screen filled with garbled lines gets stuck for a few minutes & starts all over again..
Last edited:
Guys, I am sorry if this may have been repeated already but I have tried to read through as many pages as possible and haven't got the answer I need. I have a PX3 board that failed to install Hal9k, there is no physical buttons no reset buttons, nothing, so I have resorted to searching the XDA forums to find a solution when I came to this thread. I have read the instructions and mostly understand that part but my PX3 Board doesn't look like ones I have seen on here so far. It's blue and labelled HCT-PX3-REV8.1, can I insert the jumper pins and resistors to the same ports on my board? I have no idea what android version I can or should install or where to look for it. I just want to get the stereo back in working order as the journeys in the car is starting to get very boring. If there is anything else I need to add for someone to help/guide me please let me know
Nate
Nate
It's the second one. It has a Mini HDMI port or what looks like one
OTG SOM pins are the same. Getting Maskrom if you need it differs - if MASKROM is needed, you'll need to figure out which pins to short.
At a guess, second pic - those big copper lands on RHS of CPU which are close together.
Hello to all. Seems that this method isn't working for me (my brother's unit). Although i have HCT-PX5-REV12 board, i think i tried everything suggested but always return to same result: "Unknown USB Device (Device descriptor request failed)".
This message appears only in muskrom mode.
What i did:
The cables has been soldered at board not to break the connector and eliminate loose connections.
I am powering the unit by external PSU (PC PSU) 5V, 3.3V and ground. Of course common ground with usb.
I already checked pins 35-36 (76 pin header) goes to USB controller.
I can only get a "ding" sound on windows in muskrom mode.
I tried reverse the D+, D- usb but then no hardware detected by windows.
Also different USB ports, without usb cable extender.
I didn't try different pc. I did...
Any ideas or help?
Thank you all.
This message appears only in muskrom mode.
What i did:
The cables has been soldered at board not to break the connector and eliminate loose connections.
I am powering the unit by external PSU (PC PSU) 5V, 3.3V and ground. Of course common ground with usb.
I already checked pins 35-36 (76 pin header) goes to USB controller.
I can only get a "ding" sound on windows in muskrom mode.
I tried reverse the D+, D- usb but then no hardware detected by windows.
Also different USB ports, without usb cable extender.
Any ideas or help?
Thank you all.
Last edited:
hello all, after working 3 nights on my SOM I´m only left asking for help, as many here I tried to upgrade into A10 and now I have a non working device, I would even be happy with the stock rom now 
.
- PX5 Rev 10 76Pins, Manufacture is MX
- soldered JIG, the device shows up in windows as Rockusbdevice
- Driver assistant 5.1 installed
- using RKDevtool 2.71 it always shows up as MASKROm device, I dont need tweezer trick, even while only using Pins 1 +5v Pin 5 Ground and Data -/+ on 29/30, without 3.3v on Pin 20/28
- It is possible to erase flash, at any setup with or without 3.3v connected
- I cannot flash anything, it always ends with "IDB Fail" with or without 3.3v connected, trying to write single partitions results in "Test failed"
- I have stable 3.3v , I even tried connecting Pin 9/15 also as stated in #1, but nothing changes
- using different Versions of RKDev results in same error or it does abort even earlier with "test failed"
- using Rockchip factory tool1.8 delivers same results, Version 5.3 looks totally different and I don´t know how to use this version
I tried several images and just the bootloader or recovery images from the basic OTA´s but itts always the same.
The fight is not over, since the SOM responds my hopes are still up that this brick can be revived.
Maybe some of the experienced people have a few hints for me. I´m located in Germany , so maybe someone nearby is even willing to try to fix this brick?
regards Joe
.- PX5 Rev 10 76Pins, Manufacture is MX
- soldered JIG, the device shows up in windows as Rockusbdevice
- Driver assistant 5.1 installed
- using RKDevtool 2.71 it always shows up as MASKROm device, I dont need tweezer trick, even while only using Pins 1 +5v Pin 5 Ground and Data -/+ on 29/30, without 3.3v on Pin 20/28
- It is possible to erase flash, at any setup with or without 3.3v connected
- I cannot flash anything, it always ends with "IDB Fail" with or without 3.3v connected, trying to write single partitions results in "Test failed"
- I have stable 3.3v , I even tried connecting Pin 9/15 also as stated in #1, but nothing changes
- using different Versions of RKDev results in same error or it does abort even earlier with "test failed"
- using Rockchip factory tool1.8 delivers same results, Version 5.3 looks totally different and I don´t know how to use this version
I tried several images and just the bootloader or recovery images from the basic OTA´s but itts always the same.
The fight is not over, since the SOM responds my hopes are still up that this brick can be revived.
Maybe some of the experienced people have a few hints for me. I´m located in Germany , so maybe someone nearby is even willing to try to fix this brick?
regards Joe
Has anyone already found a method to flash the new boards without pins or is there already another method? Because my radio also has a brick, unfortunately.
I have an Xtrons Model ICE/HU/PQS1053BL and the vendor just sent me an update to Android 11 and after the update my HU is just stuck at the Android logo. I can't get into recovery. I am hoping they are going to do something about it, they are just giving me the basic steps to get into recovery buts not working.
This connection is a 204 Pin SODIMM connector. you can get the connector from link below and other electronics parts supply. https://www.digikey.com/en/products/detail/jae-electronics/MM80-204B1-1R/2447551
Good luck. If I'm SOL I may explore this route.
First, with SOM installed, have you tried connection via one of the headunit USB connectors to PC and enter recovery via buttons.
Try each USB. Some Boards support, some do not.
If that works, getting maskrom shouldn't be too hard.
I will try connecting to the USB with PC. There is no buttons on this HU. Just a RST reset button.
Would I need a special USB A to USB A cable to connect radio to PC?
Is there a way I can use an Android phone connected to radio and try to access a terminal console?
I can make it myself if there is a wiring diagram. Is it just rx and tx reversed, I can't imagine the power wires connecting from both devices. I see data transfer cables for usb-a to usb-a and others like this. https://www.amazon.com/UGREEN-Transfer-Enclosures-Printers-Cameras/dp/B00P0E3954/
and this
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
First, with SOM installed, have you tried connection via one of the headunit USB connectors to PC and enter recovery via buttons.
Try each USB. Some Boards support, some do not.
If that works, getting maskrom shouldn't be too hard.1I figured it out. \o/
Video display died on my Xtrons during OTA update.
Trying to fix one problem caused bigger...
forum.xda-developers.com
1
Hey @marchnz you'll enjoy this one. I posted in my own thread about an issue with dim display, and I figured that out with a different screen setting, screen:11. I was excited to get that fixed so then I proceeded to restore a backup image I took and then things went South again. Not sure why but at 99% complete with the userdata partition, it failed. The HU was totally bricked at this point. Restarting it did nothing, and I even notice the current draw on my power supply was low when booting. That told me something was wrong. I could no longer get the unit in loader mode with the reset button. I thought it was done there but I decided to take the module out and take the heat sink off and I noticed two pads on the board. I remembered pads mentioned in the threads here and I think another user was having similar issues where you were assisting and I followed your instructions to short the two pads with power off and then turn unit on and then let go. Sure enough she came up in maskrom mode. On first attempt, the driver dropped out after a few seconds. On second attempt it lasted longer, and I proceeded to install the image, I was blowing on the rock chip just in case it was getting hot. At 60% it failed but then rebooted and I got the splash screen back. I was then able to use the reset button and put the unit back in loader mode. The rest is history. I was able to install an image and then update with the OTA for my radio.
if anyone’s radio is totally bricked, that is using this new PX6 board with the 204 sodimm, the maskrom mode is totally an option.1
Thanks for taking the time to share your experience and progression to get it working. Especially since this is a new board variant and SOM Carrier. That new SOM socket reminds me of the old MTCB type SOM keyed edge connector.
The 60% failure is probably the MCU watchdog, which resets after some minutes. I wrote about that in my initial endeavors. Getting recovery and bootloader on is all that is needed as the rest can be done as you found - reset and use loader or SDCard recovery OTA.
To summarize, rockchip recovery connection was obtained through headunits USB - correct? Any specific USB?1
Correct, I left the module plugged into the unit and used the same usb i've been loading with. Its the usb that allows for carplay separate from the usb1 and 2 pair. -
20"Factory" Recovery for MTCx PX3, PX5 and PX6 SOM.
Finally - OTG for all without modifying your head-unit. With only basic electronic/soldering skills, get OTG and fearlessly flash or recover a 'bricked' MTCD/E (HCT printed on SOM) Rockchip PX3, PX5 SOM.
See attached pics for making an OTG cable from a USB cable and two resistors.
Resistors are 12K and 15k (22k is probably better) or anyone of the following. combinations. These resistors are necessary as 'voltage dividers', with a value between 1.8v and 3.3 OK. These simply place a logic '1' on recovery and USB-OTG to 'tell' the SOM to go into OTG recovery mode.
R1 | R2
-------------------
1K | 1.8K
2.2K | 3.3K
10K | 18K
12K | 22K
Get Windows Driver [Driver assistant - latest version] and [Android tool - latest version] for direct/OTG SOM flashing here.. Be sure to edit [android tool] .ini file to set English, otherwise tool will be rendered in Chinese.
This tool for dumping / getting full backup of SOM
Excellent tool, thanks @RedScorpioXDA
Note - all tools and driver have equivalent Linux versions.
PX5 Android 9 Update.img - suitable for flashing via rockchip tools - https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/YB
- The image is located in px5 android 9/yb. The file has "_img_" listed in the filename.
- Note Android 10 has an img file too - located in px5 android 10/chs.
PX5 Android 8 Oreo full Partition extract suitable for recovering SOM, flashing via rockchip tools - https://drive.google.com/drive/folders/1P703unZDA_TdRzl6fjkkb-YUB-KpTViW
Using the RockChip Android Tool:
- For OREO: Unzip and flash all partitions in the ZIP file [px5_OREO_Full_13032018-UseToRecoverOrCreateNew.7zip here
- For Android 6, flash the latest update.img file in android tool
There are guides to partition flashing found on the internet, would be great if anyone could contribute by posting step-by-step instructions or a video to assist others (there are now posts in this thread...)
A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.
Credit (thanks!) to @scorillo_ro for the detailed image/connections diagram.
Worst case - SOM doesn't respond - force 'maskrom' detailed here explaining what MaskRom is and here on how to for your PX5 (px3 is similar.) Steps are: Power Off SOM and disconnect USB to PC. Use Tweezers, apply power/connect USB. Hold until Windows Device chime is heard (within about 2 seconds of power on.) See attached pic.
Warning : Use thin pins for OTG cable in order to avoid the damage of the SOM connectors, although along the thread it has been noted many times that damage to the SOM socket is very likely to happen if thick pins are used...OR buy SOM header from Aliexpress, digikey etc.[/COLOR]
17/11/2019 - Edit: Corrected URL for Windows and Linux Rockchip tools
04/04/2020 - link to px5 android 9 full update.img14Nice work @marchnz !
A full step by step and pictures howto should be made now and all those PX5 users without sdcard slots will be able to use this method to get Android8!
LE. I drew a schema33
Yes, on the first page of the thread you will see PX5 boards, both the green one and the blue one.Many thanks
I take it the board in the first thread above is the one out of any PX5 android car radio ?
Both are PX5 boards, just different versions...
---------- Post added at 10:01 AM ---------- Previous post was at 09:49 AM ----------
No, you can cut and use any USB cable that have at least one male plugs at its ends.
If you don't have any spare USB cable to use and need to buy one, you can buy an male to male one just to cut it in two equal parts. Use one part to build the PX5 OTG cable and keep the other one for spare
I'll also recommend the cable to be not too long and not too thin.2Finally I succeeded! I rewrote the sdupdate on the som in maskrom mode, and finally my PX5 is back to work with oreo 8 of Malaysk. Thank you so much marchnz.
Also I have had several problems to recognize the SOM from the PC, in addition to what you have already suggested marchnz I add only to bring to gnd also the shielding of the usb cable and two cables gnd to the som.
I add photos that perhaps clarifies what I suggest
New posts
-
-
-
LineageOS 20.0 (Android 13) for Mi Pad 4 Plus- Latest: ichigo_kurosaki
