yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] scorillo_ro:
Hi guys,

Yes, my Klyde unit has USB OTG connector on the back. As @marchnz (and me also) said in the"PX5 Stuck In Bootloop" thread , in MaskROM mode the MCU cuts the power to the Android SoM after about one minute and ten seconds. It seems to me that in Loader mode this will not happen, will remain connected until you reset the unit.

So for the Klyde users, both methods are available, the one discussed here being the most reliable for both MaskROM and Loader modes.

But I also admit that the method described by me in "PX5 Stuck In Bootloop" thread might be preferred in some situations.

For example, if Loader mode is still working, I can flash the entire firmware without even pulling my unit out from the car. My OTG USB male cable is now permanently connected and easily accessed in the car.

LE. Maybe offtopic. I tend to think that if the Loader mode is working, the SD card method will also work, and the other way around. I'm not 100% sure but I guess the SD card boot and OTG Loader modes are provided by the same piece of software on the SoM.

So if the boot from SD card has work for you in the past and at some point it does not work anymore, there are pretty much chances that OTG Loader mode to not work either and MaskROM being the only option.
[MTCD Hardware Development] Clandaries:
:good:
[MTCD Hardware Development] scorillo_ro:
Let's not mix the threads!

I've already added pictures on the "PX5 Stuck In Bootloop" thread here and here.
[MTCD Hardware Development] mike2587:
Hi all, I connected the modded cable to the SOM, and RKDevTool recognized it successfully with the "Found One LOADER Device" message. Can you tell me the best method to full recover NAND and restore one stock ROM? Actually I'm stack on Malaysk Rom and if I use SD Method to restore the stock ROM, using the included update.img in the SD firmware tool archive, the procedure seems to be successfull but after the reboot I always have the Malaysk ROM.

*EDIT: also the installation speed of applications from playstore is very very slow, and the settings in "Extra settings" or "Driving settings" return to default after the stereo remains turned off for a while, I have these strange behaviours*

Malaysk himself thinks that I can have a corrupted NAND. So I'm here trying this procedure. Hope that someone can give me some good info about the best procedure to follow (I already searched in the many threads without finding detailed info), because I really don't want to break anything...you know. Can I use "LowerFormat" option in Download Image Tab as first step, then flash the firmware in Upgrade Firmware Tab using a stock update.img firmware of my choice?
[MTCD Hardware Development] mike2587:
Up... Anyone? I think I have to figure it out myself...

EDIT: trying to use Android tool and Rk Batchtool, in loader mode to restore firmware but both give "Download IDB fail" message. Also tried in Maskrom mode but I got "IDB prepare fail" message. I did a Lowerformat in android tool too, but always have these errors.

I'm really tired and frustrated guys. Should I give up or there is something I can do to recover this headunit?

Inviato dal mio Z2 Pro utilizzando Tapatalk
[MTCD Hardware Development] marchnz:
Try q&a forum.
[MTCD Hardware Development] chargeable:
i wasnt lucky with soldered OTG cable, lucky that had this

What i did - took of radiator from PX5 board, and putted back to the unit without it. Connected male to male usb cable, from head units usb1 to pc. Opened RockChip_Batch_Tool_v1.8 as admin,

shortened MASKrom two pins with tweezers, kept it until switched on

And vualia, it was detected. Then just (NOTE I HAD android9 as stock) uploaded sdupdate.img from malaysk Create_Boot_SD_for_9_android_PX5 and after restarted i got into recovery. uploaded ROM update.zip to usb key, connected to headunits usb1 , updated and FIXED.

IT was so simple from the start, just needed time to understand. Hope it helps.
[MTCD Hardware Development] shtresatu:
Did you powered on the unit? How long did you short-circuit those two pins for maskrom?
[MTCD Hardware Development] shtresatu:
I've managed to enter from pc. For very short time, my unit entered recovery mode, but restarted. Every time. Is a bootloop. I can't install nothing from recovery
[MTCD Hardware Development] tisipl:
Px3, zxw_860b ver_5.1_180118

Hi all,

I have Tesla Style 10.4" Car Player with Android 6.0.4 KTU84Q (for Mitsubishi Outlander II/XL). Everything works (almost) w/o correct control of Rockford Fosgate CANBUS, wheel sterring & handsfree control. I would like to make full Flash memory backup using "RK Rom Dumper and Flasher" or "RKBatchTool" or "RK_Android_Tool" before any "deep" software manipulation, etc.

The case refers to USB OTG connection..... I can't get it. I made some research. Is there anybody who have an experience with this head unit maybe?

I found USB OTG port and I checked the connection to SOM (should be correct). Need to find the rest of required to move SOM to loader/maskrom.

Sorry, due to junior member I can't add pics...
[MTCD Hardware Development] marchnz:
This thread targets MTCD/E SOMs, if your unit is one, this thread applies. If your unit is something else, which the Chinese made up model number doesn't tell us, you'll have to figure it out.
[MTCD Hardware Development] tisipl:
that's fine... often the SOMs have a very similar design and some suggestion can resolve cases/issues... take care!
[MTCD Hardware Development] typos1:
Often its the same design, ie the 20+ manufacturers who make MTCD/E units that all use the same SoMs, so quote your MCU and people know what unit youre talking about.
[MTCD Hardware Development] tisipl:
Thanks for links... I will read material.

MCU: 860B_CHHWY_F128

I captured log via serial during boot, with removed OTG_ID resitor (10ohm):

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

· ŇRK310BŇDDR Version 1.04 20130830

In

DDR3

300MHz

Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=8 Size=2048MB

Memory OK

OUT

2.18 2

ChipType = 4

SdmmcInit=2 0

FwPartOffset=2000 , 400

StorageInit ok = 230693

chipEID = 33504b52

theLoader 60200000 252716

U-Boot 2014.01-g4270fe3 (Dec 30 2016 - 16:48:15)

CPU:	RK3188

Board:	RK30xx platform Board

LCD panel info: 1280 x 800, 16 bit/pix

lcd buffer size 10485760

Reserving 10240k for fb buffers at 675f0000

config buffer size 524288

Reserving 0k for fb buffers at 675f0000

total reserving memory(except stack) is :54m

DRAM: 128 MiB

arch_interrupt_init

DMAInit: OK

storage init OK!

Using default environment

In: serial

Out: serial

Err: serial

board_late_init

unsigned!

SecureBootEn = 0 0

##################################################

uboot version: U-Boot 2014.01-g4270fe3 (Dec 30 2016 - 16:48:15)

#Boot ver: 2014-12-10#0.02

##################################################

setup gpio int

GetParam

LBA:0, 2000, 80check parameter success

partition(uboot): offset=0x00002000, size=0x00002000

partition(misc): offset=0x00004000, size=0x00002000

partition(kernel): offset=0x00006000, size=0x00006000

partition(boot): offset=0x0000C000, size=0x00008000

partition(recovery): offset=0x00018000, size=0x00010000

partition(backup): offset=0x0002C000, size=0x0000E000

partition(config): offset=0x0003A000, size=0x00002000

partition(logo): offset=0x0003C000, size=0x00004000

partition(cache): offset=0x00040000, size=0x00040000

partition(metadata): offset=0x00080000, size=0x00002000

partition(kpanic): offset=0x00082000, size=0x00002000

partition(system): offset=0x00084000, size=0x00180000

partition(userdata): offset=0x00204000, size=0xFFFFFFFF

empty serial no.

checkKey

vbus = 1

lcd_bash = 0x675f0000lcd_ctrl_init [38]

i2c init OVER in board!

set_lcdc_dclk: lcdc_source_clk = 768, clk = 71, div = 11

rk30_load_screen for lcdc ok!

[LCD] Using LCD frambuffer at 675f0000

lcd data is helloworldlcd_enable [55]

lcd data is helloworldLBA:4020, 2000, 3LBA:c000, 2000, 4LBA:c000, 2000, 1LBA:c001, 2000, c48LBA:6000, 2000, 1LBA:6001, 2000, 4000LBA:a001, 2000, c98logo offset = 0x3c000,size = 8192LBA:3c000, 2000, 4000config_part offset = 0x3a000,size = 4096LBA:3a000, 2000, 400SecureBootCheckOK:0

booti: do_bootm_linux...

Starting kernel ...

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

and SOM board pics left on mediafire server please look: FQDN/folder/r313r82q4kwzf/xda (two files with checked pins & legend, selected colors black, green, white)
[MTCD Hardware Development] typos1:
I said quote your MCU . . .
[MTCD Hardware Development] tisipl:
ZF-1106S.... (ZhiFang, Shenzhen China) a bit complicated to find out correct in Hui Fei Type list
[MTCD Hardware Development] typos1:
Its not complicated in the slightest - theres no "MTC" at the beginning so you dont have an MTC unit.
[MTCD Hardware Development] Ammby:
Hi there. My PX6 (MTCE-HT) stucks in bootloop. OTG cable successfully soldered and SOM is recognized by my PC. So i have two update.zip files.. one from Pumpkin and the one from Hal9k (which was istalled before bootloop. So... can I flash with these files or do I need a update.img? And when... where can I get it? Thank you.
[MTCD Hardware Development] tisipl:
----

...I found by myself the way how to get recovery, bootloader mode for ZhiFeng models (rkpx3 & rk3399)..
[MTCD Hardware Development] typos1:
Well done.

I suggest you open a thread in the Android Head Units general section so anyone else with your type of unit can benefit from your experience.
[MTCD Hardware Development] wupperi:
I built the harness. I took some measurements, as the resistors and the resulting voltage seemed a bit unusal for me.

So, between the red wire in your drawing and GND I obviuosly have +5V. This is USB voltage.

Then I understand between the orange PINs (I understand this is for putting the SOM into recovery) that go into the sockets and GND I am supposed to have between 1,8V and 3,3V? Correct?

Or is it ment to be about 3,3V between orange and red and 1,8V between orange and GND?

In any case, I now used two almost identical resistors, so I have 2,5V between orange and GND and 2,5V between red and orange.

Could be so kind and adise?

Cheers,

wupperi
[MTCD Hardware Development] marchnz:
Hi, you will need full .img or partition extract. This can't be generated from an OTA zip.

Some options are:

0. Flash Hal or malysk recovery .img and then force recovery via switch to get into recovery . Flash hal or malysk OTA zip.

1. If your unit is still booting, add a physical recovery button switch. I've posted about how to do this and is basically the same as forcing recovery in OTG method. Flash the OTA in recovery.

To restore factory image:

2. Convince someone to create a partition extract of a working PX6 and share it with for for flashing your SOM via rockchip tools.

3. Convince someone to get root and extract each partition for flashing your SOM via rockchip tools
[MTCD Hardware Development] Ammby:
Thank you very much for your reply.

Two more questions:

1. The Hal9k Image can be downloaded anywhere?

2. Do you have a link to you discription how to add a recovery button?

Thanks again.
[MTCD Hardware Development] AMVPICA:
Good afternoon,

I have a problem when I connect the red + 5V cable and the Black GND, the usb is not recognized on the pc.

If you connect only the oranges + 3V USB Deteck and Recovery together with the usb data + and -.

The PC already recognizes the USB but reports that the USB drive has a problem.

Any idea ???

Thank you all

PS: Uni is HCT PX5 REV 8.0 LPDDR
[MTCD Hardware Development] marchnz:
Have you installed rockchip driver?

Triple check connections, test voltages are correct and lastly, try swapping USB data lines.
[MTCD Hardware Development] marchnz:
1 hal9k recovery image is in hal9k thread. Its the recovery, not full image. I think I've explained that in the previous post options what is needed to be done.

2. There are posts about this, you will need to either trace to find the right circuit locations using the mtcd schematic (again in my sig) OR cut the trace leading to the SOM pin (because the MCU sinks this line LOW/0v) and solder in a switch and resistor. You might need to find local expertise with this if unsure.

All else fails, package the som up and send it to me in NZ could be an option. BUT getting recovery is something you will need, if wanting to update and solve problems with your head unit.
[MTCD Hardware Development] Ammby:
Hi. Thank you for your effort. Okay that sounds not so easy.

The HU still boots as you can see in the clip but turn off after a minute. So I need a recovery button switch to boot in recovery mode. The manual to add one ist here in this thread?

[youtube]Fl4bUdbf3kY[/youtube]

This is really annoying me... Pumkin itself can't or won't help, my reseller will send me a new SOM but I am afraid this will take ages ? And I need my car every day.
[MTCD Hardware Development] AMVPICA:
Hy :)

Yes I install the rockchip driver,

The Voltage i get is:

Black " Graund"

Red "Positive 5V" Get 5.09V

Orange " Recovery and usb detect" get 3.01v

Gren " data+" get 0.45v

white "data-" get -045v

The voltage of the data cable is correct?

the error i get on the windows 10 or 7 is " A request for the USB device descriptor failed."

I allready try change the usb data but i get the same error
[MTCD Hardware Development] Ammby:
So.. Thanks to Hal9k who send me a full image my HU is back to life. Thanks for your help! If anybody needs it just ask me.
[MTCD Hardware Development] marchnz:
Might be helpful to others, are you able to share or send it to me to share?

EDIT: Uploaded PX6 HAL full image to Google Drive (see Post #1.)
[MTCD Hardware Development] Ammby:
Sure
[MTCD Hardware Development] wupperi:
I am trying to connect to a HCT-RK3399-REV08 (2019-03-18) board. Various Rockchip driver versions (4.4, 4.5 and 4.9) tried.

I am using a cable about 1ft long, supplied power in parallel to +5V and GND with a 2A power supply and also tested swapping the USB data cables around.

My voltages are ok (+5,1V and 2,75V)

The board has 2 more rows of connection points than the one in the original post, so I used an offset of two rows to connect the pins. I am using the professional manufactured cables with the metal needle at then end, so connections should be ok.

However, with the correct USB signal cabling I cannot get the device to be properly detected by WIN10. I fact I get an Error 43 (USB device was halted). Tried normal and MASKROM mode, same behaviour.

Has anybody been able to OTG connect to that board and can advise where to look at/what to try next?

EDIT:

I also now tried WIN7 on an old laptop with the O/S setup completly fresh. Same story. Device stopped.

I attach two pictures of the bl**dy device.

Also tried to supply 2,8V to USB detect through an external power source as voltag dropped to 1,77V using just USB power source. No change. I saw the unit actually not drawing any current on through the +3V leads, power supply stayed at 0,00A.
[MTCD Hardware Development] Ruzbynen:
Hello! I tried the method on PX30, but it seems to not be seen by the PC. I made the cable using 12K and 22K of the smallest resistors. When I check the cable, I have 4.96V on the 5V and 3.14V on the orange cables for the recovery and USB detect. Nothing on the data.I checked the data for continuity and there is connection to the USB male.I tried MaskROM also.

EDIT: For some reason, when it is connected I am getting 1.69V on the orange leads?

EDIT2: I tried on another PC and the only difference is that I am getting 5.12V on the +5V.Maybe I got the wrong resistors?I attached pics of my cable.I also have 2 more rows of pins.

EDIT3:I got it to get to MaskROM, I get to downloading firmware and reset device success.I install the SOM but it doesn't boot.
[MTCD Hardware Development] Ruzbynen:
Hello, I fixed my SOM and MCU.Unit booted and is up and running.The only two problems at the moment are the wi-fi and GPS are out.Any suggestions? I already tried the aluminium foil in the pins that are in this thread but the wi-fi still does not work.USBs work.Thanks in advance!
[MTCD Hardware Development] typos1:
Yeah sounds MCU related, did you get your mcu.cfg before flashing the MCU and what MCU did you flash ?
[MTCD Hardware Development] marchnz:
Post logcat so we can review that. First guess is a connection issue, because WIFI is USB not controlled by MCU, but bluetooth is dependent on Factory setting being correct. Suggest checking WIFI power and USB through to SOM against the MTCD schematic (in my sig.)
[MTCD Hardware Development] Ruzbynen:
I added foil in some pins and pushed the SOM really good back on the MCU and Wi-Fi is working now, GPS isn't but when I was disassembling the device I ripped of the cable, I tried to solder it back but it is still not working, I don't need it that much as I will be adding carplay.Thanks a lot [MENTION=4974080]marchnz[/MENTION] for the guide, if you didn't develop the USB OTG, for sure I'd be spending money to get a new unit back, you just saved me a lot of money! Thanks a lot!
[MTCD Hardware Development] typos1:
The GPS antenna has 2 wires, one for the signal and one for earth, they must be separate, maybe they were touching.
[MTCD Hardware Development] Ruzbynen:
I already assembled it and put it back in the car. I don't need the GPS as I will be installing CarPlay which is a lot better in terms of GPS signal and such. Anyway, thanks for the help, if it wasn't you guys my unit would be already in the bin. :)
[MTCD Hardware Development] mohanidno:
I can't find the " PX5 Android 9 Update.img " on yadisk, who can give me the direct link ?
[MTCD Hardware Development] marchnz:
I see what you mean. The link in the first page doesn't open the YB folder. Updated post#1, thanks.

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.
[MTCD Hardware Development] janusz12561@gmail.com:
Hello

After connecting the board to the computer, I only have the message "USB device not recognized" Rockchip driver, I installed, how to fix it?

Already gone, it turned out that I had too long USB cable

But now I have another problem, I can only see the SD card in the GPS socket, and in the other SD card I can not see or see the pen in the sockets USB. What could be the reason for this?

I have already read and everything works :)
[MTCD Hardware Development] Al Ferro:
Hi Marchnz, i am trying to bring back to life my px6 som that got stuck in a bootloop, i have creted a jig and my Computer doesn't recognize the som, i don't know exactly where to make the connections to force it into maskrom :confused:

EDIT: I tried to force it to go in maskrom mode, but nothing happens. (i am able to go into recovery and install the update zip, and supposedly everything gets installed ,but i get again and again a boot loop, i have done wiping data many times, by the way this is happening with android 10 px6 mtce)
[MTCD Hardware Development] Ruzbynen:
Are you sure you are getting enough voltage? Give us a pic with how you are connecting the wires to the board.
[MTCD Hardware Development] Al Ferro:
I think this Som is damaged , first I tried many times to power it with the resistors and I wasn't getting enough power especially the 3.3v. So what I did after that, I removed the resistors and I connected 5 V. from the PC through the short USB cable to the board, i got 3.3V from an external power supply ,then I heard my PC making the sound that it connected ,but in about one or two seconds disconnects giving me a warning message that the USB device that I connected is malfunctioning. (right now there is a problem uploading pics:confused:)
[MTCD Hardware Development] marchnz:
Have your tried forcing MASKROM, try and let us know result.
[MTCD Hardware Development] Al Ferro:
I already tried it many times, and there is no change ,nothing happens. I think this Som is trash now I am going to buy a new one.
[MTCD Hardware Development] marchnz:
I've never had one that bad its dead. You're welcome to sent it to me in NZ and I can try for you.
[MTCD Hardware Development] Al Ferro:
Thanks my friend for offering your help, the problem is that you are too far away (i wonder how much would it cost to send it to you :confused:) when i connect power to it , windows 10 sounds that has detected it ,but then right away it disconnects it because it is malfunctioning, some time ago when it was working good, the single usb wire that connects to the back of the head unit stopped working (isn't that the OTG usb port) so i contacted Dasaita about the problem, we ran some tests with a voltimeter and in end nothing came out positive, so they are going to send me a motherboard, but its taking them forever to do it. I also bought a short Male to Male usb cable to connect the head unit to the PC, the problem is that only two usb ports work (the ones that come with two cables connector) the PC did not recognized anything, i wanted to try this since i am able to get to the recovery screen.
[MTCD Hardware Development] typos1:
It costs nothing to get a shipping quote.
[MTCD Hardware Development] marchnz:
gummy bears

No worries. People from all around the world have sent me SOMs, with a record to date of 100% recovered - touch wood :) I dont charge anything, only ask for return freight.
[MTCD Hardware Development] typos1:
Yes, [MENTION=7757496]Al Ferro[/MENTION], [MENTION=4974080]marchnz[/MENTION] is well known for doing this for people on here, he has been doing it for several years.
[MTCD Hardware Development] Al Ferro:
Hi, what worries me about sending you the Som , is that it might be damaged to try to recover it because of the Warning message given by Windows. What do you think?
[MTCD Hardware Development] milyczlowiek:
I also have a connection problem. Please send a diagram of your method. Because I don't see exactly how the shielding of the usb should work.

---------- Post added at 01:36 AM ---------- Previous post was at 01:30 AM ----------

My motherboard is hct-px5-rev8.0 (lpddr) Maskrom don't work. In addition, none of my computers can see the device connected. I've already made two cables. Help...
[MTCD Hardware Development] marchnz:
Looks like driver issue to me. Is rockchip driver installed? [Rockchip_DriverAssistant_4.91] https://androidmtk.com/download-rockchip-driver-assistant

Official source: https://github.com/rockchip-linux/tools/tree/master/windows

Also dont use batch tool, use androidtool [AndroidTool_Release_v2.71.zip] found here: Official source: https://github.com/rockchip-linux/tools/tree/master/windows
[MTCD Hardware Development] Al Ferro:
Thanks marchnz, I have tried different versions of Driver assistant and android tools, and nothing seems to work. Also I have tried many, many times the bootable sd card, but all I get is a black screen, in the past this method worked fine on a different head unit with a px5 processor.
[MTCD Hardware Development] marchnz:
Ok, you mention trying an external power supply and short USB cable, so that should be OK.

The only time I have seen the device descriptor error is when the USB lines are transposed. Perhaps try swapping the USB data lines.
[MTCD Hardware Development] milyczlowiek:
Nothing works:crying:. In addition, during the test I mixed two connectors: red and green. I connected usb then. Did I completely destroy the disc in this way? Please reply. I live in poland. Can anyone from Europe save my radio? I am willing to send a plate.
[MTCD Hardware Development] Al Ferro:
Already done that many times, I have tried doing it one way or the other because I think I have idea of how this is supposed to work. last night while trying to make it work, I just let the Som connected to the PC and on its own it began to get connected and disconnected over and over again, kindda like if i was using a switch to power it on and off. Yeah, I think the Som has a hardware problem , I already made an order to get two new Soms, thanks again for being here providing us your help and knowledge.:good:
[MTCD Hardware Development] marchnz:
Just out of curiosity, where did you order from and what did they cost? Last I looked on aliexpress, sellers have these over an exorbitant $100usd each!

Any chance you would consider sending me your NG SOM, I'm still really curious as to what the problem is. Worst case you end up with two spares :)