yashsingh1/xdaforums huggingface dataset:
[MTCD  Android Head Units Q&A] Kayhan 17#:
Hey guys,

i have a KGL board and its a bit different, i could track down a bit of the lanes from the left front panel and it has USB connections printed but not connected.

On the main board i also checked the lines and i think i connected the right ones on my USB connector. By inspecting my pictures i found out that i have to switch D- and D+, but still if anyone could take a look =)

I also lifted 27 and 28 of the 850G IC, what else do i have to connect? (ctl wire? and to which point?)

As for recovery mode i dont have a clue how to achieve that for now, i read that its enough to short D0 and GND on PX3 board?

Any further information for is highly appreaciated.

Thanks
[MTCD  Android Head Units Q&A] marchnz:
Note, must use USB 1/OTG - this is the direct connection to SOM USB [ARM-DP] and [ARM-DM]

Ok, you have lifted pins to U27 - do you also have USB Switch IC [FSUSB42]

If YES: Connect USB wires to external USB 1 pins on your main board

If NO:

1. You must remove Mainboard SOM Header PINs [ARM-DP] and [ARM-DM] (or ISOLATE these pins somehow)

2. Connect USB Male lead to [ARM-DP] and [ARM-DM]

3. Try connecting to computet while holding / pressing buttons applicable to your unit to trigger 'Recovery'.

Also....

What happens when you connect USB to your computer? Assume driver and rockchip batch tools are loaded?

When powering on the unit, with a voltmeter check you have voltage:

- MCU 3.3v

- VDD+3.3 (on MCU)

- M_RST and RESET - what is the status of this line at MCU

- Is MCU powered UP?

Try connecting, then powering unit on while trying to enter recovery by button method for your unit. If that does not work, thenthe 'force' recovery method which toggles the SOM recovery line is as follows:

Note, must use this method as the MCU sinks the [CTL-recovery line]

- On mainboard carefully remove SOM header pin [ctl_recovery] - see my signature for schematic (also attched non-watermark version here, happy holidays)

- Solder a wire to the SOM socket [ctl_recovery]

- held [ctl_recovery] wire to [mcu 3.3v test pad]

- Connect PC

- Power on Headunit

- Your PC should chime (new device) and RockChip batch tools indicate "Device Connected"
[MTCD  Android Head Units Q&A] magedkathom:
hi.

it is very useful thread. I will make a try.

but can you add a chart for more Clarification about wires connections.

thanks.
[MTCD  Android Head Units Q&A] ZeroZorro:
Device Satus: Black Screen, but Led's are on...

Problem started while flashing a new firmware, suddenly screen went pitch black

Flashed dozens of times, never had this before...

When trying to boot:

Power ON> LED's Touchpanel buttons are ON > After a while LED's go OFF

When touching power (touch panel) for a few secs LED's are going OFF too.

Sometimes i manage to get LED's back ON without powering OFF first... So i think i can manually sleep/wake that way?

Problem is i can't auto-update firmware and/or MCU with sdcard, usbstick or force a factory reset (or enter Recovery) with an USB-keyboard cause SDcard-slot and USB port(s) on device are not working.

My question: Is there any chance i will succeed if i follow the steps described in OP? Cause i am worried that now there is no juice on USB-ports while powered on there also won't when using OTG with a PC?
[MTCD  Android Head Units Q&A] marchnz:
From your post, doesn't seem like you have anything to lose. If nand is corrupt juice not present is the least concern.

Suggest before making any mods test for OTG first.

Also, If your PX5 SOM is corrupt I would be happy to attempt reload on my jig with return postage.
[MTCD  Android Head Units Q&A] ZeroZorro:
okay, thanks, i will go and search for my OTG-cable and try that and report back #fingerscrossed
[MTCD  Android Head Units Q&A] Clem_XDA:
Hi, I'm in the same situation but on the board it's written HCT-PX5-REV4.0.

Do you know if your method works too ?

Big thanks !
[MTCD  Android Head Units Q&A] Clem_XDA:
Hi,

Here are the pictures :

There is the GL850 chip so I think it's possible to do the mod.

Thanks for the help :)
[MTCD  Android Head Units Q&A] marchnz:
[MENTION=8079205]Clem_XDA[/MENTION] [MENTION=1369996]ZeroZorro[/MENTION] [MENTION=5037437]Cid6.7[/MENTION]

Hi,

Try new SDCARD tool for PX5, in this thread

If this is successful, OTG wont be necessary unless the SOM NAND bootloader is corrupt.
[MTCD  Android Head Units Q&A] ZeroZorro:
Thanks, but in my case i had to sent it back due to multiple issues (screen blank, reset button not working, USBports not working, LEDs reversed on-off behavior). They received it at 12:19 and at 13:51 I got message that a refurbished unit was sent my way. #fingerscrossed

So no possible way to test this approach but it did work before (with a slightly older version).
[MTCD  Android Head Units Q&A] Cid6.7:
I got mine workin again after I got the correct files

I'll check the link tho TY ?
[MTCD  Android Head Units Q&A] Clem_XDA:
Thanks for the answer !

Unfortunately it doesn't boot from the SD card. Maybe there's something to do with the reset button..

Anyway it's a great tool !

I'm hoping again to recover my unit :)

But maybe I didn't used the good files. I tried to use the update.img file from Malaysk ROM to convert it to sdupdate.img with the tool but same issue, no boot :(
[MTCD  Android Head Units Q&A] micdesa:
Hi Guys someone could help me? I'm looking for info about Intel Sofia s3g SoM
[MTCD  Android Head Units Q&A] marchnz:
Update 2/2018- NO mainboard required - updated OP. a gig can be made without a main board. From the work I've now done, Ive realised you don't need another mainboard. You could temporarily solder connections to SOM or make JIG from header pins.
[MTCD  Android Head Units Q&A] typos1:
Or just use the sdfirmware tools version that works with the RK3368/PX5 ! :)
[MTCD  Android Head Units Q&A] marchnz:
Indeed! This should only really be necessary if the SDCARD tool doesnt work for some unknown reason....or you want OTG flashing ability :)
[MTCD  Android Head Units Q&A] micdesa:
Intel Sofia 3grw

Hi Guys mny radio is bricked too.

Anyone have experiencing with intel sofia 3gr/3grw radio.

Can anyone tell me the pin for solder the usb wires?

thanks in advance.
[MTCD  Android Head Units Q&A] ikerg:
as the Mainboard is the same....(at least similar, as some menufacturers re-utilized MTCD Sofia Mainboards to mount PX5), and same 72pin interface....I think it will work (never tested before)

I did try on my PX5 Oreo (but i didn't succeed, but [MENTION=4974080]marchnz[/MENTION] did, so probalbly i did something wrong)

1) Cut a USB Wire and solder the wires to jumper wires:

a) Red Wire is +5V

b) Black Wire is Ground

c) Green Wire is Data+

d) White Wire is Data-

2) You will need a 5V Power Source & 3.3V Power Source. I recommend to recycle an old Powersource from a Desktop computer that outputs 3.3V, 5V & 12V

For the PX5 coreboard (i think is similar for a Intel Sofia):

Pin 1 --> +5V (or the Red Wire from USB)

Pin 4 --> Ground (or Black wire from USB)

PIn 9 --> +3.3V

Pin 20 --> +3.3V (this is the recovery Pin)

Pin 29 --> Data- (White wire from USB)

Pin 30 --> Data+ (Green wire from USB)

3) On the following link you have instructions (in Russian, but Gogole translate will help) about how a guy could come to life a MTCD intel sofia. [MENTION=4974080]marchnz[/MENTION] find a way of avoid using the main board and direct pin into the coreborad (as i described on Step 2) but the rest of the procedure once you get a USB signal into PC you must to get from there:

https://4pda.ru/forum/index.php?showtopic=778259&view=findpost&p=59139381
[MTCD  Android Head Units Q&A] micdesa:
thanks guys...

I'll try and let you know.
[MTCD  Android Head Units Q&A] micdesa:
Guy just an info.

How I know which is the PIN numbering order of the SOM?
[MTCD  Android Head Units Q&A] ali20042004:
Hi

wich software do I need to flash firmware to px5 MTCD ?

could you please help me to fix my head unite?
[MTCD  Android Head Units Q&A] ikerg:
https://androidmtk.com/download-rockchip-batch-tool
[MTCD  Android Head Units Q&A] ali20042004:
Update 2/2018 - anyone can make a gig without a main board. From the work I've now done, Ive realised you don't need another mainboard. You could temporarily solder connections to SOM or make JIG from header pins.

This method is more desirable, as MCU cuts power to SOM after a few minutes during OTG.( Theory is the MCU watchdog senses an unknown condition in SOM, so resets by power off.) This can be bypassed by another mod to board, but much easier to just make a simple jig.

Need:

Remove SOM from mainboard.

Header pins to fit SOM (or solder temporarily to SOM PCB header)

USB male cable, cut one end off for wires to attach to SOM.

5v and 3.3v power supply.

1. Using schematic as guide. Connect earth and +5v pins. Connect 3.3v to [rtc_3.3]

2. Connect USB wires to SOM [USB-OTG] connections

3. Connect wire to SOM [ctl_recovery] and wire that to 3.3v.

With USB connected, power on. Use tools/load driver as described in recovery thread.

Hi every one can you explane method 2 exactlly how i sold my wire to the board . iam confused .
[MTCD  Android Head Units Q&A] ali20042004:
this is my board .

which wire to be sold on the board
[MTCD  Android Head Units Q&A] ali20042004:
I Have like your problem. could you please help me to fix my head unit?

thank you
[MTCD  Android Head Units Q&A] scorillo_ro:
Is the attached picture correct?

If it is, then my board is dead for good, but at least may help others.

Windows did not detect any devices when I plugged the USB cable, nothing showed up in RkBachTool (drivers installed using DriverAssistant).

And I really think my board is bricked because I tried to load a firmware I made myself using the bootable sdcard method.

I changed some partitions addresses, includind the recovery one, I guess this is the main reason.

I had an "Installing system update" screen with a progress bar that got stuck at around 10% percent. After about 10 minutes the process (or unit) restarted, the "Installing system update" started again from zero to tern percent, restarted again but this time the unit was bricked. Does not boot and I can't enter recovery, probably because it is not there.

I hope that I and others will learn from my mistake.

My unit is a KLD one, do you think I can order this one for replacement or recommend other?

https://www.aliexpress.com/item/WIT...-Android-DVD-Android-5-1-can/32840635444.html
[MTCD  Android Head Units Q&A] typos1:
Sorry to hear that.

Yeah that one ll fit.
[MTCD  Android Head Units Q&A] marchnz:
Hi,

Sorry to hear. Dont worry - messing with partitons isn't known to fully brick these SOMs because they have a OTG loader based in ROM.

I'll review the schematic today, but initially looks like you need to connect more ground and power lines. When connected do you have a volt meter to check that there is +5 at that test pad?

You're welcome to send it to me to and I can try to reload on my known working Jig. I reside in New Zealand, so freight costs may or may not be a factor.

I'm doing just this for another member at the moment.
[MTCD  Android Head Units Q&A] marchnz:
Hi,

I have reviewed the schematic and attached a JPG containing the recommended connections.

Colour codes & Notes:

GREEN = PSU Earth [0v/(-)]

RED = +5v to PSU

BLUE = USB

YELLOW = +3.3 Via 3.3v supply OR use two resistors as a voltage divider 10K to 5v (R1 in image), 15k to earth (R2 in image), center = 3.3v

NOTE: SINK [CTL_WAKEUP) to GROUND (0v) if unit does not power ON

+5v	= 1,2,3

0v	= 4,5,6,71,72,73 and SOM Mounts

+3.3	= 20,28 (and possibly 9 & 15 - see note re. 15.)
[MTCD  Android Head Units Q&A] scorillo_ro:
Yes I have all I need, including multimeter, all I'm missing is experience and the fear of breaking things ?

---------- Post added at 11:20 AM ---------- Previous post was at 11:17 AM ----------

Will give it another try when I'll be back home.
[MTCD  Android Head Units Q&A] scorillo_ro:
[MENTION=4974080]marchnz[/MENTION] Had no luck

Just to be sure (and to better be seen in the picture) I used the colors from your schema for the wires.

So Green is GND, Red is +5v, Yellow is +3.3v, Blue is USB cable (a black cable with a blue tube over it) with standard Green and White data wires to a male connector.

Have used the voltmeter to check if the pins had connectivity on the back of the board. Found 5,09 volts and 3,36 volts respectively.

Tried different combinations regarding pins 9 and 15, no device was found. I even checked my computer's USB port with a stick and measured the green and white wires of the USB cable...

Any other suggestions?

By the way, there are only 72 pins on the board, so the last two ones must be 74 and 75 and 71 ,72, 73 corresponds to the mounting holes?

What about the pin 31 (OTG_DRV) ?
[MTCD  Android Head Units Q&A] marchnz:
Frustrating, it all looks correct. Have you tried toggling CTL_WAKEUP (I will have to confirm later this evening what my jig has on this pin.)
[MTCD  Android Head Units Q&A] scorillo_ro:
Many questions comes to my mind:

By toggling do you mean I should first apply +3.3v on the CTL_WAKEUP then apply GND -0v or the other way around?

Should I do the same on CTL_RECOVERY?

When powering the SOM for the first time, should CTL_WAKEUP and/or CTL_RECOVERY have +3.3v applied or should them be applied later?

I think I did try some of the combinations but the toggling. Will try again this evening when I’ll return from work.
[MTCD  Android Head Units Q&A] audisean:
not had a go at fixing my old unit since i got new radio - still want to fix it but been ill last few weeks so had no time - I see marchnz has done some interesting things - I know my mainboard is ok as I took a bit of a risk and put SOM from new radio into old unit and managed to update mainboard software (unit worked ok) but putting old SOM boards back unit stopped working again - will update when I try again
[MTCD  Android Head Units Q&A] marchnz:
Hi,

Confirming ctl_wakeup (logic 0) should be pulled to ground and remain pulled low.

Ctl_recovery pulled 3.3v via resistor (logic 1) and stay 3.3v.

I measured all SOM pins today and can't see any reason why the suggested combination doesn't seem to work for you.

Ensure that the SOM is also grounded via 3 mounts.

Also load pX5 USB 'rockchip USB' driver. Even if USB DM and DP are transposed, you should see something happen in the windows device list (code 21 from memory.)
[MTCD  Android Head Units Q&A] scorillo_ro:
I don’t know what to say. I already started to lose my hopes.

I have measured the 3 mounts and they seem to already have ground connectivity, but I will try. I also translated the Chinese text from the schematic and found something like “the lines sould not be under 0.8 mm”, so maybe my wires were too thin. Must buy some thicker ones.

Did you actually had success using just the SOM or did you use it only on the modified MCU board?
[MTCD  Android Head Units Q&A] marchnz:
Hi,

Only from modded board. There's no external clocks etc, so should work. I'm going to buy a header and test as very keen to see others get OTG.
[MTCD  Android Head Units Q&A] ikerg:
I would appreciate as I couldnt got to the coreboard be recognized be menans of direct connection to PC USB port and 5V/3.3V power sources
[MTCD  Android Head Units Q&A] scorillo_ro:
Last evening I also tried feeding CTL_RECOVERY with +3.3 volts from middle resistors connected to +5 volts / GND and CTL_WAKEUP to GND, still no luck.

The SOM's heat sink remains cold. If I connect it back to the MCU board it will get warm...

At this moment I'm not sure if the SOM is alive anymore. I start wondering if maybe by mistake I connected something wrong or did some short on it and fried it.

On the other side I still have +5 volts on the SOM test pads.

@marchnz

At my last two attempts to wake the SOM I also wanted to see if something comes up on the serial pins, but I had no luck there either (so again, maybe the board does not wake up or it is fried).

For this I used a CH340G USB to Serial adapter and connected its GND, TX and RX to SOM (pin 46 - ARM_RX and pin 48 - ARM_TX)

Maybe you want to try this also on your working mod to see if there is some feedback there.

And thank you again for your hard work on this!
[MTCD  Android Head Units Q&A] Cid6.7:
FWIW I tried the OTG mod by lifting the legs & successfully flashed/unbricked our Sophia unit. Then for sharts and giggles I seated and soldered the legs back with same results. Now I can just hook my male/male usb up to the unit and works every time... Not sure why tho lol
[MTCD  Android Head Units Q&A] marchnz:
Congrats. Can you post some detailed pics of your mainboard, guessing it is a GS, but would like to confirm.
[MTCD  Android Head Units Q&A] scorillo_ro:
For me Windows is detecting an "unknown device" connected for a very short time, too short to identify it. I have the rockchip drivers installed (version 4.4).

What I did was to solder wires CTL_RECOVERY to +3.3v and ARM-DM and ARM-DP to USB male connector on the SOM, with the SOM connected to the MCU board.

I've also tried with the legs lifted but same result, fast connect-disconnect in Windows... I have a Klyde unit.

--

LE. Also tried to inverse the order of USB wires, same result.
[MTCD  Android Head Units Q&A] cookie1338:
Unfortunately I cannot do this myself.

Please, would anyone in Europe be willing to receive my HU, recover it from bootloop and send it back? I will off course pay the return cost with paypal.
[MTCD  Android Head Units Q&A] scorillo_ro:
Klyde OTG

Good news, bad news.

Bad news first:

- My PX5 2GB RAM is still bricked (or fried), can't access it via OTG.

- New PX5 4GB RAM has arrived, all good but no WiFi (refuses to turn on, still looking for the reason).

Good news (at least for the Klyde users):

No hardware modification needed for OTG/ADB access on the MTCD units!

Just need to adapt an USB male cable to fit the highlighted port on the back of the unit like in the attached picture.
[MTCD  Android Head Units Q&A] scorillo_ro:
Some more details

Here are the proofs (attached pictures)

1) To connect the unit (via OTG) to the Rockchip Batch Tool, you must have the Rockchip Drivers installed (version 4.4), have the adapted cable connected to the PC, then enter recovery mode (for me long press power until leds start flashing, relese it and repeatedly pressing it again until the unit restarts).

Upon entering the recovery, the PC will detect the device and starts setting it (installing the drivers for the USB port on which you have the cable connected). If this takes long (and probably will for the first time) then the unit will give up waiting to enter in OTG mode and will boot into the recovery. Don't worry if WIndows tells the device was not installed correctly because it was removed. Try again without disconnecting the cable. Exit recovery and then enter again (reset, long press, etc.). This time, the PC (Windows) will detect the "Rockusb Device" and the unit will stay in OTG, the recovery mode will not show up on the unit and you will have one "green" connected device in Rockchip Batch Tool!

2) To connect to the Android via ADB shell, you must start the "Factory settings" using the "adbon" password instead of "126". During this mode your other USB devices (like USB memory stick, or 4G dongle) will be disconnected.

I think you also have to enable the "Developer mode" and enable the "USB debugging" first. I had those already on because I made the tests from Malaysk's rom.

To exit this mode you must start again "Factory settings" using the "adboff" password this time (your USB devices will be reconnected).
[MTCD  Android Head Units Q&A] ali20042004:
Could you please attach the softwer and driver in this page
[MTCD  Android Head Units Q&A] typos1:
Hmm, I wonder if other units can also do this.
[MTCD  Android Head Units Q&A] marchnz:
You have OTG! Do you have OTG Loader Mode? If so, you have all you need to wipe and reload RK SOMs. Did you do any mods? Note that your machine is a GS and that you are connected via USB1 which is the only USB supported for OTG and on GS hardware.

Use the tool [Androidtool.exe], boot as you described using recovery button - would you share a screenshot - it should look like my attachment.
[MTCD  Android Head Units Q&A] marchnz:
Download here

Has rkdevtool (android tool) and very latest version 4.5 driver.
[MTCD  Android Head Units Q&A] scorillo_ro:
This is how it looks
[MTCD  Android Head Units Q&A] marchnz:
Congratulations, you have OTG and the ability to directly flash your SOM. You can now fearlessly flash ROMs, even the wrong ones without fear of bricking :)
[MTCD  Android Head Units Q&A] marchnz:
Or consider ordering a comfast CF-WU725B USB- plug and play. Set factory settings Bluetooth to [MD725] and you're good to go.
[MTCD  Android Head Units Q&A] scorillo_ro:
Great idea!

The RTL8723BU module was already shipped, so I'll wait for it now and consider your suggestion as a backup solution.

Thank you for all your help!

Regarding my bricked 2GB SOM... I ordered some 2mm pitch headers and when I'll have them I will make some more tests on it. But I have very little hope.

---------- Post added at 02:36 PM ---------- Previous post was at 02:33 PM ----------

Why do the information in my screenshot looks different from yours?

I mean I have some loaders and boot stuff and you see the recovery, system, etc. ?

---------- Post added at 02:54 PM ---------- Previous post was at 02:36 PM ----------

But my WQ_BC5 is working just fine now. Do you think it will be ignored and the MD725 one will be preferred?
[MTCD  Android Head Units Q&A] Malle355:
Hi,

I just tried to update to Android 8. After flashing the new recovery I stuck on a black screen. I can't do anything at my device. When I press reset button for ~10sec buttons begin flashing but I cant get into the recovery. px5 - 2gb - mtce 2.80 (ha). Any suggestions?

Thanks
[MTCD  Android Head Units Q&A] marchnz:
Try booting from an PX5 recovery SDCARD. If it fails to boot, an OTG reload is your only hope.

Note, I've had one SOM sent to me from a failed upgrade that wasnt booting at all and required a minor mod to the SOM to force [MASKROM] mode - I then succeeded in fully recovering and then putting Oreo on it.

If you dont have any luck and dont want to attempt getting OTG, you're welcome to send the SOM to me with return freight - Im in NZ.

- M
[MTCD  Android Head Units Q&A] scorillo_ro:
Is this something different from what you already posted on this thread?

As far as I remember, you said you did not succeed to enter maskrom even if you tried to expose the obvious paths between the flash and px5 processor.

If this SOM mod is new, please share. Thanks!
[MTCD  Android Head Units Q&A] marchnz:
Just to clarify - OTG loader or maskrom are essentially the same for.our purposes. More here

Short answer is that I have found a way to get maskrom on PX5.

The procedure still uses OTG - all I did was 'mask' the emmc so that the PX5 runs its internal ROM - that internal ROM basically sets up the PX5 to receive instructions via OTG.

On px3, it's easy - there are two labelled pads to 'mask' / short.

On PX5 (which is what we are referring to) I couldn't identify any pads, so carefully scraped back a couple of the emmc lines, shorting to earth to prevent the PX5 from loading (corrupt) data. That corruption, I would assume is why I couldn't get [loader] mode without it.

Once tracks were exposed - with PX5 fitted to jig, USB connected, I simply shorted to ground (big pad) and the first tracks with tweezers, and powered on, releasing tweezers once the [windows] device connection sound was heard.

The device is then shown in android tool as 'found one maskrom device. From there, within android tool, I low level formatted emmc, reset then loaded firmware (android 6) update image file.
[MTCD  Android Head Units Q&A] scorillo_ro:
What do you mean by telling "first tracks"? More than one?

In your picture, the first is from top or from bottom?

Thank you very much!
[MTCD  Android Head Units Q&A] scorillo_ro:
My bricked SOM is pretty similar to yours!
[MTCD  Android Head Units Q&A] Malle355:
Just tried to boot with bootable sd card but nothing happening. So I think I have to OTG. Is this still ok?