yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] polgoz:
Hi all, a year ago, I lost my PX5 trying to solve a problem of contacts in some where of mobo. Recently, a guy offers me an PX3 as donate. I put this px3 in my mobo (MTCD) and it don't boot. But shows fabricant logo, and if you try to reach recovery page by pressing buttons it get into a Lollypop android auto logo and thats all.

I try to re flash it with the method of sd formated in SD_Firmware_Tool.exe but nothing happens. Is this SOM Bricked and a candidate to OTG?

I remember that I use OTG method on my px5 successfully but the situation of this PX5 was that it dont boot anymore and didnt show any logo at all. now is not the same case.

Any help is appreciated.

Best
[MTCD Hardware Development] polgoz:
Hi mate, thanks for you description and helpful post. Im in the same situation as you. Px5 burnt and Px3 (MTC-RK3188-Rev0.3) to replace. but my 5 attempts to put ROM from Hal9k (7.1.2) didn't work. Black screen for long minutes. Auto re boot and black screen again. No erase message.

can you clarify some points?

1) as first step did you just use the upgrade tab on RKDevtool for only apply Kumarai to the som? or you RUN all the data?

3) Did you work over Px5 or Px3? Are you using OTG again at this point right?

Any bump is appreciated.

Best
[MTCD Hardware Development] marchnz:
USB device not recognised is one of these issues:

1. RockChip USB driver not installed. Install from Driver_Assist_v4.5

2. Transposed USB Data (+) = white and Data (-) Green.

3. Insufficient USB power.

4. USB cable length - Use a SHORT length of USB cable

If you get any kind of device activity, even if the device shows up as "USB device not recognised".

The good news is that the RockChip SOM is in LOADER or MASKROM mode. You just need to resolve one last problem.
[MTCD Hardware Development] PekeMM:
Would not that fail to work on 2/16GB devices as user partition is 25GB?
[MTCD Hardware Development] marchnz:
Would it be cunning to try resize the [user] partition :)
[MTCD Hardware Development] typos1:
This is just designed as a temp mod for recovery rather than a permanently attached mod then [MENTION=4974080]marchnz[/MENTION] ?

Any idea what app to use if you use Linux not windows ?
[MTCD Hardware Development] marchnz:
Definitely not permanently attached. The idea is to remove the SOM from the mainboard and connect to recover/flash - use a proper 2mm pitch header pins or stiff wire/cut offs from 1/4watt resistors to connect per the diagram. The wire ends just temporarily plug into the SOM female header.

There are Linux tools in the RockChip link and a Linux version of rkdumper.
[MTCD Hardware Development] PekeMM:
That means someone with successful update on 2/16 Device needs to dump whole NAND?
[MTCD Hardware Development] Harsesis:
I've made the jig and can get the device to show up in maskrom but flashing on Linux I get errors.

I can get into recovery mode but there are errors saying no such file or directory regarding the nand. please see attached.
[MTCD Hardware Development] scorillo_ro:
Try to low level format it first:

sudo ./upgrade_tool lf

( lf = Lowlevel Format )

This should erase everything on nand...

---------- Post added at 05:03 PM ---------- Previous post was at 04:51 PM ----------

If the device remains connected and showed as Unknown device in Windows Device Manager, then you can try to right-click on it and use Update Driver Software, then Browse my computer for driver software, navigate to the folder containing the Driver Assistant 4.5 and try to select one of the win7 or win8 versions.

I have no other idea...
[MTCD Hardware Development] Harsesis:
LF works alright I then try uf sdupdate.img. this errors out saying wait for loader fail

I have connected the 5v to a power supply so I know it's got enough current.

These issues have occurred since I tried to update to android 8. I did not see the erase message.
[MTCD Hardware Development] dottorniù:
Finally 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
[MTCD Hardware Development] marchnz:
I am truely thrilled to hear more OTG success stories.

Well done.
[MTCD Hardware Development] djtriso:
Have i erese nand first to update ?
[MTCD Hardware Development] Clandaries:
We need a really good howto with all news. My resitors will arrrive tomorrow, i hope. Then i will try my best to get my board to live again :)

Regards
[MTCD Hardware Development] djtriso:
How update firmware update.zip oreo with android tool

In android tool the firmware has to be .img and oreo 8 is .zip

how can i do it
[MTCD Hardware Development] marchnz:
Full guide here. Covers both update.img update and partition by partition (if you have the files).

Flashing Oreo:

1. The latter flashing by partiton is most reliable method for Oreo (I need to upload files somewhere - within the next few days.)

OR

2. use the update image created by kumarai to first flash the Android 8 recovery, then put update on a SDcard or USB stick and flash the update from recovery.

Again, for those where recovery doesn't recognise SDCard or USB stick, I will upload full partiton files and create an upgrade process summary in the next few days.

For Android 6, use the update image method.
[MTCD Hardware Development] Clandaries:
So it is possible to flash Oreo recovery from Kumarai or Malaysk and then install the zip-file (ROM)

But it is also possible to flah the Android 6 image file and then after that go the way to flash Oreo? Maybe i stay at Android 6 for some time until Oreo is very stable.

Prefer to install Android 6.

Regards
[MTCD Hardware Development] Harsesis:
What is the correct order to flash the files?
[MTCD Hardware Development] Harsesis:
I've tried using rkflashtool. I get the following:

$ rkflashtool p >file

rkflashtool: info: rkflashtool v5.2

rkflashtool: info: Detected RK3368...

rkflashtool: info: interface claimed

rkflashtool: info: reading parameters at offset 0x00000000

rkflashtool: info: size: 0x555554d5

rkflashtool: fatal: Bad parameter length!

$ rkflashtool n

rkflashtool: info: rkflashtool v5.2

rkflashtool: info: Detected RK3368...

rkflashtool: info: interface claimed

rkflashtool: info: Flash ID: 45 4d 4d 43 20

rkflashtool: info: Flash Info:

Manufacturer: Samsung (0)

Flash Size: 0MB

Block Size: 512KB

Page Size: 2KB

ECC Bits: 0

Access Time: 40

Flash CS:

Any help?
[MTCD Hardware Development] Clandaries:
My PC says the USB needs more energy, so i have to buy a active USB hub?

Regards
[MTCD Hardware Development] Harsesis:
Could someone please backup their bootloader? I think it might be something to do with this. The flash isn't being recognised by my SOM. I keep getting the following when I try to check my flash info using rkflashtool

rkflashtool: info: rkflashtool v5.2

rkflashtool: info: Detected RK3368...

rkflashtool: info: interface claimed

rkflashtool: info: Flash ID: 45 4d 4d 43 20

rkflashtool: info: Flash Info:

Manufacturer: Samsung (0)

Flash Size: 0MB

Block Size: 512KB

Page Size: 2KB

ECC Bits: 0

Access Time: 40

Flash CS:

When I try to use upgrade_tool using "UF update.img" I get the following in the log:

18:37:56 Upgrade Tool ver 1.21

18:38:07 Test Device Start

18:38:07 Test Device Success

18:38:07 Check Chip Start

18:38:07 Check Chip Success

18:38:07 Get FlashInfo Start

18:38:07 <LAYER 2-46> INFO:FlashInfo: 0 0 0 0 0 4 4 0 28 0 0

18:38:07 Get FlashInfo Success

18:38:07 Prepare IDB Start

18:38:07 <LAYER 2-46> ERROR:PrepareIDB-->No Found 1st Flash CS

18:38:07 Prepare IDB Fail

I've been reading that bootloader version needs to be specific for the flash on the device. Please find attached a picture of my board.
[MTCD Hardware Development] desidude2000:
Anyone here in So. cal willing to let me borrow their OTG jig/cable ? I would be forever indebted. I have bricked my PX5 and have the SOM out but don’t have the right resistor. Would a ratio of 1k|2k work (instead of the 1.8k) ?

I am in Tustin. Thanks so much for considering n
[MTCD Hardware Development] vegechuang:
Dear all,

Install the driver,and execute androidTool.exe.

i try to connect my pc,but nothing detect.
[MTCD Hardware Development] marchnz:
If all connections are correct, suggest forcing MASKROM. See thread for details
[MTCD Hardware Development] vegechuang:
Please help me to confirm my circuit.It it right?
[MTCD Hardware Development] marchnz:
Looks ok, but I can't tell if the physical connections are ok. Did you try maskrom or not?
[MTCD Hardware Development] vegechuang:
No,I have not read the thread in detail.

I even dont know what is maskrom.
[MTCD Hardware Development] typos1:
Youve not read the thread in detail ?! Surely thats the first thing youd do before attempting to recover your SoM ?
[MTCD Hardware Development] vegechuang:
I lost my original recovery when i flash malask's recovery.img by WIFI.

Is that possible to save my recovery by the method of the thread?

I read this thread in google tranlastor and very slow.
[MTCD Hardware Development] typos1:
Cant you flash using Malaysk's recovery ?
[MTCD Hardware Development] vegechuang:
No,it cant!

In below thread,i use method 3 to update oreo.

https://xdaforums.com/showpost.php?p=78177976&postcount=2270

I dont know why it always show "No Space Left on device"

After i flash recovery fail,i cant reboot into recovery right now.

And that's why i reserach this thread.

My MCU is MTCE_CZ_V2.77
[MTCD Hardware Development] typos1:
If you have an Oreo recovery then AFAIK you should be able to flash any Oreo ROM.

Your MCU is not relevant.
[MTCD Hardware Development] vegechuang:
First,i know if i flash oreo recovery success,i could flash different mcu's rom.

2.I haven’t seen anyone have CZ MCU like me.

Do you mean that malay's oreo recovery is not suitable for my CZ MCU??

Somebody help support me the CZ recovery of oreo....

I will be very grateful.
[MTCD Hardware Development] typos1:
The MCU is not relevant to recovery, it only changes for each version of Android.
[MTCD Hardware Development] vegechuang:
If MCU is not relevant to recovery,why i can not flash malay's recovery?
[MTCD Hardware Development] vegechuang:
Hi!

I try it today and still cant detect rom.

I try it on two computer.

win7 USB2.0 voltage 4.88V.

win10 1803 USB2.0/USB3.0 voltage 4.90V.

I have maskrom but still nothing.

androidtool show static.

Steps are: Power Off SOM and disconnect USB to PC. Short circuit 2 points , apply power/connect USB
[MTCD Hardware Development] desidude2000:
ok, so i made progress. i'm using 8.8k|15k resistors. I can get windows to recognize and it makes the jingle sound, but couple of odd things are going on:

1. i can only get the SOM to be recognized by the computer if i swap GND with 5V. not sure if the USB able is somehow switching the voltage.

2. once recognized by the computer, i get: "Device Descriptor request failed" on the driver.

Please kindly help. Any pointers would be greatly appreciated.
[MTCD Hardware Development] vegechuang:
Do not use DuPont terminals, the holes will become loose, and USB will not be read.
[MTCD Hardware Development] desidude2000:
Could someone please help ? I am get 5volts and 2.2volts with the resistors but only way I get windows to recognize anything is switch red with black and red in pin5 while black in pin1. Is this normal? Once I do that , I get device descriptor not found in windows device manager but the device does show up! Help please.
[MTCD Hardware Development] marchnz:
Hi, if unable to resolve, you're welcome to send it to me in NZ to attempt recovery. All I would ask for is return freight.
[MTCD Hardware Development] d5stick:
I have searched this thread for a work instruction and files to do so but i can only find the github but no drivers or exe files to restore my bricked unit.

Could someone help me forward?

I got a PX5 module 2g, android 8. The MCU and latest GS ROM are already downloaded.

Thank you!
[MTCD Hardware Development] silo:
Ok, I'm having hard times trying to recognize board bu Windows.

Instead of using power from USB, I've used external power supply with +5v and +3,3V.

The only cables from usb I've connected was Green and White (and combinations with/without common GND)

Windows never recognized any device and I never heard any chime sound.

More over I have PX5 rev 4.0 board, same as here:

https://xdaforums.com/showpost.php?p=75931327&postcount=129

Is there any person form Europe that would like to bring back my board to live?

Thanks
[MTCD Hardware Development] marchnz:
Gnd is a must. Force maskrom.
[MTCD Hardware Development] silo:
So I need to be able to put pins and turn over board to "do" maskrom? and this will help with "recognizing" device under Windows?
[MTCD Hardware Development] silo:
Ok, I finally was able to recover my SOM :D

First problem was Maskrom - without this connection my computer didn't recognized any USB device! [MENTION=4974080]marchnz[/MENTION] I think this should be highlighted in first post

Second problem was "Unrecognized device"

This was probably caused long data+/- lines. I used "crocodile wires" from USB cable to small pins that was connected to board.

I solved it by connecting directly green and white wires to board.

Thanks again all for help

Good luck for next one :)
[MTCD Hardware Development] marchnz:
Good result.

Re. Highlight. Perhaps you missed first post Worst case - SOM doesn't respond - force 'maskrom' ] with links to detailed images. Then there are all the other times I mention {maskrom} in responses to questions.
[MTCD Hardware Development] kholshin.i:
Hi guys!

I arranged OTG with 12k and 15k resistors. I measured voltage on pins 5v and 2,8v. When I get this cable connected to SOM it shows 5v and 1,36v. Why? 1,36v is not sufficient to be detected by PC. Please help.
[MTCD Hardware Development] silo:
The problem is that when you connect SOM it "takes" some voltage and lower it from 2,8 to 1,36

It's just a normal case - SOM is acting like a huge resistor, that's why.

you can read quite good answer here:

https://electronics.stackexchange.c...sb-cable-with-a-voltage-divider-to-provide-3v

In my case I used external 5V and 3V power supply.
[MTCD Hardware Development] Andy Alias:
I have a PX5 Rev 10 board, it’s stuck in a loop, my supplier is sending me a new one so I thought I would have a go at this. I can’t get it on the pc at all not even maskrom. Stuck trying on windows 10, I can see voltage going to the board through various pins (with multimeter) but it doesn’t pull any amps (with usb tester).

I bet I'm missing something or doing something wrong but cant figure it out.
[MTCD Hardware Development] fashion2891:
Recovery

Ciao,mi potresti dire quali sono i file che mi devo scaricare e come poi li devo scompattare per metterli poi successivamente sulla som tramite la procedura usb
[MTCD Hardware Development] Clandaries:
Maybe someone can help when you write in english??
[MTCD Hardware Development] fashion2891:
Recovery tramite som

[QUOT=Clandaries;80530445]Maybe someone can help when you write in english??[/QUOTE]

Hi, could you tell me what are the files that I have to download and how then I have to unpack them to put them then later on the som via the usb
[MTCD Hardware Development] marchnz:
English please - refer XDA rules
[MTCD Hardware Development] fashion2891:
Recovery tramite som

Hi I was able to recover through som, I put the firmware, everything is ok, I left the installation, I disconnected everything, I reassembled the som in the car radio, what happens, that I get smoke from the radio car, yes an apartment burned , because? Was I wrong to do something? Help, thanks.
[MTCD Hardware Development] fashion2891:
Recovery tramite som

Hi good morning, I did everything as it was predicted to do through som, I unmount the som usb, I connect it to the car radio unit, I turn it on and I see smoke coming out of the radio, flat burned,

never me? Was I wrong to do something?
[MTCD Hardware Development] fashion2891:
Recovery tramite som

Hi good morning, I did everything as expected from Som, I disassembled Som USB, I connect it to the car radio, I turn it on and I see smoke coming out of the radio, flat burned,

never me Was I wrong to do something?
[MTCD Hardware Development] nic2k:
When you re-installed the SoM you probably bent a pin and/or caused a short circuit. Take it apart again and look the boards over with a magnifier find the short and try again if you're lucky it still works.
[MTCD Hardware Development] robi4o2:
to Andy Alias - you have wrong connection. First 4 pins this is I2S. You must start from

pin.5 (pin.1 - 5V)

pin.9 (pin.5 - GND)

etc ...
[MTCD Hardware Development] fashion2891:
Recovery tramite som

I put on a new flat, it also burned out, how come?

sometimes of a pin farther away, not the same, at

lego image.

https://postimg.cc/dhcWjzfL/704b7d9e
[MTCD Hardware Development] fashion2891:
Recovery tramite som

I saw, the pins are perfect and intact, I attach image

https://postimg.cc/87Jsb0qf/86e19622
[MTCD Hardware Development] nic2k:
What is that flat cable connected to? Are you sure you connected it in the right place and aligned it correctly? It's not easy to help you if you only provide bits of information. Maybe more pictures of everything would help.
[MTCD Hardware Development] fashion2891:
Recovery tramite som

I sent you the photos to show you that no foot of the som is bent. How can I check if there is a short one? Because in this way I can't see anything, but some problems are sure, because I constantly burn the flat.
[MTCD Hardware Development] nic2k:
Are all the case screws the same length? Make sure that no screw can touch the circuit board when you reassemble it. Also check that nothing is touching the case on the bottom side.
[MTCD Hardware Development] marchnz:
Might be best to contact a local electronics repairer.
[MTCD Hardware Development] robi4o2:
PX5 RK3368 Android 9 - black screen

Hi

MTCE_HF_V3.07_1

PX5 Rev.10 4GB + 32GB Android 9

rk3368-userdebug 9 PQ2A.190305.002.20190628.103151 test-keys

I had failed upgrade software at my SOM, now I have black screen. Radio every 70 second restarted.

I have OTG cable, and connction with compuer.

Question - which software and how upgrade my SOM?
[MTCD Hardware Development] marchnz:
It's all in the first post, highlighted red, but I havent created a partition extract for android 9 (I am running 8); so unless someone else does, you will might need to use the Android 8 partition extract and then upgrade to 9 (via the various paid "donation" options from Hal/Malaysk.)

Im happy to extract/Dump an Android 9 SOM if someone loans / sends me a working Android 9 SOM.
[MTCD Hardware Development] typos1:
[MENTION=5092263]Hal9k_[/MENTION] does Android 9 ? I ve not seen it on his site.
[MTCD Hardware Development] robi4o2:
This is problem. I can't find img Android 9
[MTCD Hardware Development] marchnz:
Quite right, I meant upgrade tool - Hal has an paid option.
[MTCD Hardware Development] typos1:
Ah yeah I know about that. I ve been looking out for 9 from him for a while.
[MTCD Hardware Development] marchnz:
That's what I said in my post - there is no .img, you need partition files :)

Because there is no ".img" file, the only way to flash via the Rockchip tool is by partition. An option is for you to flash the original Android 8 upgrade IMG (andoroid 6), which contains a Android 8 recovery. From there you can upgrade to 8 and then 9 via Malaysk or Hal tool.

A much easier way would be to simply flash Android 9 partition files via OTG+Rockchip Android Tool, but no-one seems to want to do the work or provide me with a Android 9 SOM, or donate hardware to enable me to provide the community with updated partition images.
[MTCD Hardware Development] nic2k:
There's nothing on those pictures that would explain your problem but look back at this picture. Why is the edges of the original cable so ragged? It's possible you might have inserted the cable offset by one pin and caused something to blow and burn the cable. That would explain why when you inserted the new cable in the right position the next line burned. That also means something is blown and it could be at either end of the cable.

There's a slim possibility that a pin inside the J18 connector is bent. You can check for it with a magnifier and a mirror.
[MTCD Hardware Development] fl4r3:
Does anyone know what points to use to force a PX6 core board into MASKROM mode?
[MTCD Hardware Development] scorillo_ro:
I'm not sure, but you can try the pins in the attached picture
[MTCD Hardware Development] fl4r3:
I've been trying those two points but not had luck. Hence wanted to check what the known working method was in case I've completed busted the board or connection points.

Will keep trying tho :good:

Edit: after leaving the board to sit this morning it is automatically connecting as MASKROM again which is good (but means I can't confirm if the two points pictured do indeed work). However, I get the error "Download Boot Fail" if I try anything, even ReadFlashID or ReadChipID fails. Is this a sign that the board is unrecoverable?

Edit 2: The two circular points do work to make the board go into MASKROM mode. Still having trouble with "Download Boot Failure" :(

Edit 3: Managed to solve my issues. Detailing here in case anyone encounters it in the future.

There's a Rockchip linux upgrade_tool so decided to try that (used a USB bootable version of Ubuntu). This time, I was getting either "Download Boot Fail" or "Creating Comm Object failed". The latter error was interesting as I read there can be issues with USB 3.0 ports and my laptop only has USB 3.0 ports. So I tried Ubuntu on another laptop with USB 2.0 ports and this time it worked! For some reason MASKROM mode was more sensitive and I had to use a laptop with USB 2.0 ports.
[MTCD Hardware Development] fashion2891:
Recovery tramite som

I think that no pin has been bent, because now that I've put the new flat back in without inserting the som, the flat hasn't burned out
[MTCD Hardware Development] nic2k:
Ok then if it burns again when you reinstall the SoM then you know there's a problem with it. I don't know if you'll be able to find a replacement SoM there doesn't seem to be any PX5 available anymore.
[MTCD Hardware Development] fashion2891:
if indeed there is the problem on it only after I reinstalled over the operating system, how can I check if there is the problem above?
[MTCD Hardware Development] alma359:
Is it possible to access adb via OTG? I need to flash update.zip file again, bacause i have broken my rom by uninstalling the radio system app.

I tried entering recovery with physical buttons but it's not working on my device.
[MTCD Hardware Development] Matt Devo:
big thanks to the info in this thread. Bricked my PX6 HU by making a 3rd party launcher a system app, and was unable to enter recovery. Managed to get it into OTG/loader mode (the pin offset on the header threw me off at first, and used a ch341a flasher for 5v/3.3v) and reload update.img, good as new. cheers!
[MTCD Hardware Development] Matt Devo:
guess I spoke too soon. While unit is no longer bricked, it seems I managed to kill USB - so wifi and USB ports are all non-functional. Pulled the SoM out and am able to connect to it still via OTG (and even re-flashed it), but still no luck. Any ideas? I cleaned up all soldering on the header so everything should be good there. Pins on the main board are straight and firmly seated into the SoM header.
[MTCD Hardware Development] typos1:
Several people have had this before, youve probably been a bit rough when inserting the pins, try putting some rolled up some aluminium foil (aluminum in US speak lol) in the relevant holes.
[MTCD Hardware Development] Matt Devo:
interesting, and worth a try. just the USB data ones (29/30)?
[MTCD Hardware Development] typos1:
Yeah any that are relevant to usb, maybe do a thread search to find out exactly which ones if youre having trouble.