yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] Hdevil56:
Device Descriptor request failed

i installed the USB cable OTG per the instructions, checked voltages and i wasnt getting the 3.3v so i used an external PS, this worked as Win 10 beeped and recognized the port, except that no matter what i do it keeps telling me "Device Descriptor request failed" i tried a different machine a Vista laptop and it gave me the same error.

Does that mean that my board is dead?

any help would be appreciated
[MTCD Hardware Development] Migueliyo85:
How have you done to feed the plate? you have a photo?
[MTCD Hardware Development] Migueliyo85:
I do not know why it is not detected by the computer. There is something wrong? I tried MASKROM but nothing...

Help, please!

[IMG="SOM"]https://drive.google.com/file/d/1-z8kS7rPncGvEWVajCCAqAgBcJE4acmt/view?usp=drivesdk[/IMG]

[IMG="SOM"]https://drive.google.com/file/d/1PlA3vNYNnRIF1yMzlHUuttFnS5gGqX9a/view?usp=drivesdk[/IMG]

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

https://drive.google.com/file/d/1-z8kS7rPncGvEWVajCCAqAgBcJE4acmt/view?usp=drivesdk
[MTCD Hardware Development] krzychunh:
WORK ;) 2x 12K 2 x 15k ;) windows 10 64 bit Rockchip detect

View attachment 4714662
[MTCD Hardware Development] krzychunh:
In case of problems with connectivity, I recommend that you follow my scheme;)

View attachment 4714664
[MTCD Hardware Development] Migueliyo85:
Thanks! I try It later
[MTCD Hardware Development] krzychunh:
How to flash step by step, where find files Android 6 to 8 ?
[MTCD Hardware Development] Migueliyo85:
I tried It but nothing... I am desesperated!
[MTCD Hardware Development] krzychunh:
send a photo of the connection, and the device manager after connecting or detects something
[MTCD Hardware Development] Migueliyo85:
This is what I did. When I plug on PC, nothing appears.

[IMG="PC"]https://i.ibb.co/6b0bLgr/Sin-t-tulo.png[/IMG]
[MTCD Hardware Development] krzychunh:
not load the photo
[MTCD Hardware Development] bjt2:
Mine wouldn't detect either, I tried everything imaginable, but absolutely dead. Ended up just buying another SoM.
[MTCD Hardware Development] marchnz:
As an option, send SOM to me for recovery (NZ)
[MTCD Hardware Development] bjt2:
I PM'ed you but you didn't respond, can I still send it?
[MTCD Hardware Development] marchnz:
Odd, I cant find a PM from you. Yes you are welcome to send it to me in NZ.

Try to PM me again.
[MTCD Hardware Development] Migueliyo85:
I edited message. Now you can see, thanks
[MENTION=4974080]marchnz[/MENTION], if I send you my som, how much its cost from Spain? Thanks!
[MTCD Hardware Development] maframan:
Hi, please help me because USB doen't recognized by PC so Android Tool tells me "No Device Found"

I trying to use Android Tool with Windows 10 64 Enterprise
[MTCD Hardware Development] marchnz:
I dont know your local postage rates in Spain to send to 8061 NZ. I dont charge for my work, a donation would be ok.

In the past, I have recovered the SOM and then got a return shipping cost from NZ Post, but you would need to find out how much it costs to send to me from your local postal/freight service.
[MTCD Hardware Development] krzychunh:
I already have Android 8;). Send photos of your circuit diagram again. Perhaps it's about resistivity, I soldered my cables to the SOM,

BT stopped working and USB connectivity, maybe you have loose on the socket try aluminum foil gently slip into the holes under the pins.

I recommend soldering the wires to the pins
[MTCD Hardware Development] maframan:
Thanks for your reply, I've attached photsos
[MTCD Hardware Development] krzychunh:
Android installation from 6 to 8

drivers

https://drive.google.com/drive/folders/1t2DZYS2TUabdbrB9LNcxThQCULmY0J0-?usp=sharing

files

RKDevTool

https://drive.google.com/drive/folders/1jzgX9wRaUAaTqS-HV9IF0U09acy90Grh?usp=sharing

-------------------------------------------

PX5 px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew

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

-------------------------------------------

Soft Malaysk ROM for PX5

https://xdaforums.com/android-auto/...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724

-------------------------------------------------- -------------------------------------------------- ----------------------

Opening RKDevTool - AndroidTool.exe "Download image tab" in RKDevtool folder must be copied image folder with PX5 files px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew

https://drive.google.com/drive/folders/1P703unZDA_TdRzl6fjkkb-YUB-KpTViW and copy the image folder from it.

a) Click the right mouse button on the list of partitions and select the load config we indicate "config_16.cfg" uncheck items 12 and 18 "cache" "userdata"

connect the SOM board after detection click "Run"

b) After uploading all files, go to the tab "Upgrade Firmware" click "Firmware" indicate sdupdate-A8-Kumarai.img and then click "Upgrade"

We connect the plate to the radio as well as the radio itself. After starting, the data will be cleared, the radio will restart and run with android 8.

Soft Malaysk ROM uploaded in version 3.2 with the ZIP extension to the SD card in the usb reader format of the FAT32 card

Installation from Recovery mode

-------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ---------

if the above instruction did not work, we add steps

(First clicking on the "Upgrade firmware" tab by clicking Firmware, I pointed to the MiniLoaderAll.bin file and then "EraseFlash" after cleaning I chose Upgrade after uploading

sdupdate-A8-Kumarai.img) and then repeat steps from a and b

View attachment 4715663
[MTCD Hardware Development] krzychunh:
Add after one resistor as shown in the picture

View attachment 4715633
[MTCD Hardware Development] maframan:
Thanks a lot, now Windows tells me Usb not recognized.... must I to invert data cable (green and white)?
[MTCD Hardware Development] krzychunh:
View attachment 4715655

;) You have the same version of the main board as me, You can try how the effect will be the same to leave the original scheme, look whether you do not have any short circuit, slack on the pins.

Look at whether the drivers are installed
[MTCD Hardware Development] maframan:
Thanks, now works but when try to flash I obtain error in attached photo

The firmware path is corret and is \\Mac\Home\Downloads\UnbrickHU\PX5-Oreo-Malaysk-Flash-ModdedWithUserDataForPartitionLoad\sdupdate.img
[MTCD Hardware Development] krzychunh:
I tested and this method works I spent 5 days to refine so trust me

step by step

https://xdaforums.com/showpost.php?p=79024651&postcount=317

if it did not work, try to load first sdupdate-A8-Kumarai.img / erase flash
[MTCD Hardware Development] maframan:
I've tried step by step procedure and load first sdupdate-A8-Kumarai.img / erase flash and obtain attached photo error
[MTCD Hardware Development] krzychunh:
Android installation from 6 to 8

drivers

https://drive.google.com/drive/folders/1t2DZYS2TUabdbrB9LNcxThQCULmY0J0-?usp=sharing

files

RKDevTool

https://drive.google.com/drive/folders/1jzgX9wRaUAaTqS-HV9IF0U09acy90Grh?usp=sharing

-------------------------------------------

PX5 px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew

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

-------------------------------------------

Soft Malaysk ROM for PX5

https://xdaforums.com/android-auto/...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724

-------------------------------------------------- -------------------------------------------------- ----------------------

Opening RKDevTool - AndroidTool.exe "Download image" in RKDevtool folder must be copy image folder with PX5 files px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew

https://drive.google.com/drive/folders/1P703unZDA_TdRzl6fjkkb-YUB-KpTViW and copy the image folder from it.

a) Click the right mouse button on the list of partitions and select the load config we indicate "config_16.cfg" uncheck items 12 and 18 "cache" "userdata"

connect the SOM board after detection click "Run"

b) After uploading all files, go to the tab "Upgrade Firmware" click "Firmware" indicate sdupdate-A8-Kumarai.img and then click "Upgrade"

We connect the plate to the radio as well as the radio itself. After starting, the data will be cleared, the radio will restart and run with android 8.

Soft Malaysk ROM uploaded in version 3.2 with the ZIP extension to the SD card in the usb reader format of the FAT32 card

Installation from Recovery mode

-------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ---------

if the above instruction did not work, we add steps

(First clicking on the "Upgrade firmware" tab by clicking Firmware, I pointed to the MiniLoaderAll.bin file and then "EraseFlash" after cleaning I chose Upgrade after uploading

sdupdate-A8-Kumarai.img) and then repeat steps from a and b
[MTCD Hardware Development] maframan:
another time windows do not discover the SOM

---------- Post added at 12:49 AM ---------- Previous post was at 12:09 AM ----------

Thanks a lot for your help, now I flashed but the HU do not start and screen remain black
[MTCD Hardware Development] maframan:
Now, I executed another time the procedure, attached the outcome screenshot, is all correct, right?
[MTCD Hardware Development] marchnz:
Perfect - well done!
[MTCD Hardware Development] marchnz:
pm sent - happy to help!
[MTCD Hardware Development] maframan:
Thanks a lot!!!

Now I restored the HU and I have one problem with USB reader because doesn't work, proceed I to install last Malaysk o Hal9k rom?
[MTCD Hardware Development] maframan:
I've solved the USB problem only for pen drive in one of two usb (when attach my usb pen drive in first female cable work well, in secondary female cable not). Help me for resolve my issue.

Thanks
[MTCD Hardware Development] krzychunh:
View attachment 4716318
[MTCD Hardware Development] maframan:
Thanks a lot for your support. I've filled the pin with the allumium but doesn't work the secondary usb female slot (only first usb female works fine).

I trying to connect my DAB+ stick in first and second usb female slot but doesn't work (I've Malaysk ROM 3.2 version).

Is it possible that ROM don't have a driver for my DAB+ stick? How to verify that?
[MTCD Hardware Development] krzychunh:
236/5000

Not all USB modems are compatible with px5 I have been modifying my modem for video on https://www.youtube.com/watch?v=EaOHIS2gadk , if there is a usb power supply, the port works well and if it does not detect the issue of
[MTCD Hardware Development] krzychunh:
Wifi Bt 100% working, new connector slot =)
[MTCD Hardware Development] bjornh:
Soooo, I guess none of you guys ever got hold of the actual images for PX6?

How did you do this? I'm in the same boat except to me it happened after a factory reset. I would like to do some logcat analysis to find out exactly why it isn't booting but I have no idea how to OTG into these devices. I found a set of instructions for the generic PX3/PX5 modules somewhere else, basically removing the SOM from the mobo and connecting usb to the pins directly. Is this what you did? Does this also work for PX6 SOM?
[MTCD Hardware Development] typos1:
In the RK3399/PX6 thread someone recently posted that an image was available.
[MTCD Hardware Development] scorillo_ro:
https://yadi.sk/d/3H06K_0GCl6hNg
[MTCD Hardware Development] bjornh:
Thank you. Although I now realize I was in the wrong thread - I thought I had posted this in the Avin F series thread. I believe those are slightly different beasts.
[MTCD Hardware Development] Basoda:
Did you find a solution for this issue?

I have the same problem. Flash Size: 0MB. Constant Prepare IDB Fail.
[MTCD Hardware Development] Harsesis:
Sorry no, I just bought a new unit. If you do get it working. Please post your method, I still have my broken unit.
[MTCD Hardware Development] Basoda:
Thank you, for replying.

I have tried everything.

Thinking that the NAND is dead.

I'm gonna buy a new one to.
[MTCD Hardware Development] marchnz:
The good news is that I have never had a SOM sent to me with dead storage. You're welcome to send the SOM to me in NZ to attempt recovery.
[MTCD Hardware Development] alt.d4c:
Hi, i can not unbrick my head unit, i made the otg-usb cable, all voltage seems to be fine but the pc never recognise the som, only when i use a usb port hub i got that connection sound (chime) but never show up in the system manager. I used many combinations of resistors from 6k to 22k, than i used an external 3.3v power supply. I tried even maskrom mode but nothing change, i hve hct px5 rev 4.0, so maskrom must be this way https://xdaforums.com/showpost.php?p=75931327&postcount=129 but i'm not sure.

The head unit is bricked when i tried to update to android 9, with the sd card upgrade, the hal9k mod recovery it was successfully installed, than the message to remove the card and thats it, i got black screen, can not enter anymore in recovery mode, with sd card upgrade is not starting. And now i tried the otg unbrick but no success. First of this brick i have upgrade/downgrade many times my unit, from android 6 to 8, then to malaysk mod, and now wanted to try the "pie" update. Thats it, bad luck.
[MTCD Hardware Development] marchnz:
As per above post#342 ;)
[MTCD Hardware Development] alt.d4c:
Yepp, it cost me 50 euros to send it from EU to NZ.

Strange or not the core board is identical with this one https://xdaforums.com/showpost.php?p=75974447&postcount=2 from [MENTION=4768815]scorillo_ro[/MENTION] user, PX5-REV4.0 same date 2016.11.18 only the hour or other number is different R 1713. Thanks anyway.
[MTCD Hardware Development] marchnz:
Just to clarify, the Chime is heard but no device "one loader mode found" or "one maskrom device found" is displayed in the Rockchip Android tool, similar to attached?

Have you tried the updated tool and driver on the Rockchip wiki, or another PC?
[MTCD Hardware Development] alt.d4c:
The chime is heard only when i use a usb hub 4 ports, directly to any usb pc ports nothing happens, and never show up in the device manager. I tried and a laptop but same story, i tried with windows 7, 10 and ubuntu. I installed the latest DriverAssitant_v4.7 after the v.4.4 and than AndroidTool_Release_v2.61. Maskrom i don't no if that is the way to activate it, because nothing is heard or loading.
[MTCD Hardware Development] marchnz:
Step me through to the process and timings of how you have tried maskrom and also attach an image of the board and points. Also your cable.

As an FYI, anytime I have had a SOM not appear, maskrom was the solution. Must short with the power OFF then power on/connect, hold short for a few seconds more then remove short. Chime / "maskrom device" appears a second after.
[MTCD Hardware Development] alt.d4c:
This is my som and the points what i tried. But the pads where are 5v and gnd is not the maskrom? Maybe ?
[MTCD Hardware Development] Kralizec2005:
Maybe this will help somebody.

First thanks to [MENTION=4974080]marchnz[/MENTION] for the nice work ;)

Second thanks to [MENTION=2754277]dottorniù[/MENTION] for the guide from here

I "broke" my PX5 (2Gb RAM 32 Gb ssd) by my mistake trying to update to Malaysk 3.2

I ended up by not be able to get into recovery.

I swap the PX5 with the old PX3 and the rest of the unit was ok.

What I did:

1) with the OTG and RKDevtool Androidtool v251 I upgraded firmware with sdupdate-A8-Kumarai.img

2) put the SOM in the unit and started. After ERASING step the unit entered in a endless loop were it was only displaying this:

View attachment 4751618

3) Ignored that and moved to the next step. I wrote on PX5 the sdupdate of Malaysk 3.2.

4) Put the SOM back in the unit and started. The Malaysk logo shown and the erasing process started. After that the logo shown again and than after 10 min of black screen logo again. I let it another cicle of logo black logo.

5) Reset the unit and entered recovery.

6) Inserted the sdcard with Malaysk update image and stated the update.

Update went smooth and now I have once again a working unit.
[MTCD Hardware Development] marchnz:
Points appear correct. What are the voltages when plugged in?
[MTCD Hardware Development] alt.d4c:
Success to enter in maskrom mode from windows 7, but i can not flash the sdupdate.img or any other firmware, is fail to erase flash or upgrade "download boot fail", every trying to read, erase, upgrade is fail. Can you please tell me what is the way to unbrick it from maskrom, what img to flash? I tried to flash MiniLoaderAll.bin from your image full oreo rom, than sdupdate-A8-Kumarai.img but everytime i get "download boot fail".

update

I tried again the maskrom mode and this time i was able to erase flash and than lower format, after that i flash the update.img from your zip archive and i get in loader mode. I finally unbrick my head unit. Thanks.
[MTCD Hardware Development] marchnz:
Great result, good on you for perseverance and figuring it out. Well done.
[MTCD Hardware Development] alt.d4c:
I have just noticed now, the wifi and usb is not working after flashing oreo rom.
[MTCD Hardware Development] scorillo_ro:
Hi [MENTION=4974080]marchnz[/MENTION], [MENTION=4582467]RedScorpioXDA[/MENTION]

I was trying to dump android9 from a PX6 SOM, but rkdumper does not work for this.

It detects the device as loader mode rk3399, but it fails to find the parameters information.

For PX5 it worked like a charm, you can see the attached logs.

RKDevTOOL (v2.51) is also complaining (see the attached screenshot).

P.S. One nice thing I noticed in version 2.51 of RKDevTOOL is that it can successfully switch the SOM to maskrom mode!
[MTCD Hardware Development] scorillo_ro:
Followup discussion here: https://xdaforums.com/general/rooti...-backup-firmware-t2915363/page10#post79535887

L.E. rkDumper doesn't work with PX6 SOM. I quit trying, sorry :(
[MTCD Hardware Development] scorillo_ro:
However, I can confirm that a PX6 SOM can be used to replace a PX5 one. I put it in my old KLD unit on which I have that OTG working out of the box.

PS. My new unit (LY MCU) also have an OTG connector on the back ("G" in the attached picture), but it seems it is working just for ADB, not for loader mode as the KLD one.
[MTCD Hardware Development] condi:
hi guys,

did anyone succeded to get working android 8 to 9 sdupdate img flashable via otg android tool?

tried already some combinations with hal's 9.0 sdupdate for sd - failed.
[MTCD Hardware Development] scorillo_ro:
did not had a chance to try it, but as far as the sdupdate.img was reported to work for the bootable sd method, it should work for otg too

keep in mind that in android 9 there are three new partitions, so the start of some partitions are different now

https://xdaforums.com/showpost.php?p=79410458&postcount=3078

https://xdaforums.com/showpost.php?p=79412263&postcount=3083

https://xdaforums.com/showpost.php?p=79320683&postcount=143

---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------

In the first two posts the partition start addresses are in hexadecimal, in the form of parameter.txt, where if I remember correctly you should add 0x00002000 to get the real start

In the third post the positions are in decimal
[MTCD Hardware Development] condi:
Hi scorillo,

I've tried many combinations, still no success. sdupdate.img from Hal's Android 9 update doesn't flash correctly. Only black screen after try.

I've flashes also bootcard.img successfully, headunit booted to recovery, but didn't mounted sd/USB. Mount errors and can't flash rkimage via none of 3 USB ports.

Even I tried to extract, and repack recovery img with sdupdate.img included in /data and symlink it as /mnt/external_sd/ but without success.

Maybe Hal could modify his recovery to search for sdupdate.img also on USB storage, and of course mount it correctly?

View attachment 4763865

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[MTCD Hardware Development] scorillo_ro:
Do you have recovery 9 now? I can't see this in your picture...

If yes, you should now use the update.zip from an android 9 OTA in the recovery, not sdupdate.img!

L.E.

"Apply update package" should use update.zip (from OTA)

"Apply system image" should use update.img (which is not available for android 9, I only got an android 8.1 one)
[MTCD Hardware Development] scorillo_ro:
It is a very interesting recovery the one in your picture.

On my PX6, recovery version 9 doesn't have those options:
[MTCD Hardware Development] typos1:
Has he got an MTCD/E unit I wonder ?

Whats your MCU [MENTION=422959]condi[/MENTION] ?
[MTCD Hardware Development] scorillo_ro:
Now at a second look at his post, he told he successfully used the bootcard.img, so that recovery is probably the one for android 6...
[MTCD Hardware Development] typos1:
Ok, but he doesnt say what unit he has and so many people on here dont check things out fully before they flash stuff, never seen an MTC unit with a green background in recovery.

The bootcard.img may work on non MTC headunits with this chip ?
[MTCD Hardware Development] scorillo_ro:
I don't know. I don't know if the OTG method discussed here will apply to other type of units.

I'm telling that the bootcard.img is intended to make a sd card bootable. The sdupdate.img that is used to replace the one on the sd card just after the bootable card creation it is supposed to contain the new recovery, that is why I assumed the version 6 in the picture.
[MTCD Hardware Development] SilentO:
Anyone from SoCal?

---------- Post added at 07:48 AM ---------- Previous post was at 07:24 AM ----------

I have a dead SOM that I can send.
[MTCD Hardware Development] marchnz:
Happy to try.... PM if wanting to send.
[MTCD Hardware Development] SilentO:
Sent
[MTCD Hardware Development] slaroni:
Killed Device could this help???

High,

i just killed my device.

After updating mcu to LM3.06 i tryed to reset Malaysk 3.51 by deleting data/cache.

An i was so silly to take out the key for shortly leaving the car. (maybe it was to hot in the car)

Now i can't get in to recovery anymore.

Booting with SDcard does nothing , it only shows the first screen without doing anything.

Now it starts with Logo and then ....... look at the image.

Could this OTG systems work to get back an image to the device ??
[MTCD Hardware Development] slaroni:
Thanks for the info,

i can take 18k resistor instead of 15k ?

Greetings Slaroni
[MTCD Hardware Development] typos1:
Have you tried reflashing the ROM from recovery ?
[MTCD Hardware Development] slaroni:
No recovery anymore.

Reboot yes .

Tried several times , with sd-Update out of Gps-slot , NOTHING worked.

There is only Logo MTCD/Malaysk/H9k but nothing happens.

6,8,9 does not matter.

still there is some rest of malaysk 3.51 trying to boot, and look at the pic. flashing several times.

Interrupting the deletion of cache (def. my fault ) did it.

After updating to LM-3.06 i was still able to get into recovery.
[MTCD Hardware Development] vegechuang:
Dear all,

this link only support linux,i didnt found windows driver.

where can i find windows driver?

Get Windows Driver [Driver assistant v4.5] and [Android tool 2.39] for direct/OTG SOM flashing here

https://github.com/rockchip-linux/rkbin/tree/master/tools
[MTCD Hardware Development] scorillo_ro:
https://github.com/rockchip-linux/tools/tree/master/windows
[MTCD Hardware Development] vegechuang:
Thank you so much.
[MTCD Hardware Development] scorillo_ro:
You're welcome. Don't be afraid to use the "Thanks" button ;)