yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] SkyBeam2048:
Did anyone here try already use and verify the tools linked in initial post?

I just started some tests. Well as there is no Android 8 image available I decided to check if I can create a recovery/upgrade-disk using available Android 6 tools. So what I did:

Extract an existing Android 6 system image

Creating an Android 6 recovery structure using images from Android 6 (boot.img, kernel.img, misc.img, recovery.img, resource.img, system.img, trust.img, MiniLoader)

Created update.img and sdupdate.img using afptool and RKImageMaker

Then I used sdupdate.img in SD_Firmware_Tool creating a firmware upgrade sd-card.

After this I inserted the card to the GPS slot and fired up the head unit. It boots and applies all images.

Well, after the flash completed it was booting to recovery only. But from there I could also re-apply update.img to get a fully working system again.

I was brave enough then to try replacing the stock recovery.img with some RK3368 TWRP images I found online. Unfortunately none of them provided any screen output. I guess it would require some PX5 adaptations to get it working. The good news is I was always able to revert/recover my PX5 using a self-made recovery SD-card.

So I am still quite convinced that we could manage flashing PX5 Android 8 images using those tools.

But I am quite sure some of you did the same already playing with your units.
[MTCD Android Head Units General] marchnz:
This is what I hoped someone would validate as I haven't had time. Thanks, suggests that hardware mods to recover soft bricks/boot loops are no longer necessary thanks to having the updated tools.
[MTCD Android Head Units General] typos1:
Good news ! Well done, thanks.

Weeks back I suggested using MTCD ROM Builder and an MM imag/ Oreo images from the Oreo zip to try and make an Orea update.img. I didnt try it myself for reasons already discussed - no OTG for recovery and [MENTION=4974080]marchnz[/MENTION] has the set up for that.

Now, thanks to you I could try it myself, knowing I d be able to recover . . . but its probably pointless as an Oreo SoM is winging its way to New Zealand for [MENTION=4974080]marchnz[/MENTION].

As for custom recoveries, it was decided way back in 2014/15 that MTC units are best left with the standard recovery mainly cos MCUs wouldnt be able to be flashed without it if I remember correctly, but I think there were other reasons too -youd have to check the original MTCB megathread for the exact details. Of course if someone could modify TWRP or similar to be able flash MCUs that would be great.
[MTCD Android Head Units General] SkyBeam2048:
So yes, unless my device is somehow special we don't really have to be afraid about bricking our units. I forgot to mention what device I used (inc case this is important).

My tests were done on a Klyde "HKD-7800" with 1024x600 screen and PX5/2G/32GB/Revision 8.0 SoM. The unit has a GPS micro-SD slot but no second SD slot and soft-touch-buttons.

I guess you're right about Recovery. However as you said perhaps flashing MCU might be possible to integrate. If not then one could actually create a boot SD using the tools provided here which just boots to recovery in order to flash the MCU from USB. Or the other way around, use TWRP booted from Micro-SD.

I am not sure how many blobs would have to be included as binaries to build a completely custom ROM. Perhaps even some lineage based ROM would be possible. Using TWRP it would also support OTA upgrading more easily and comfortable recovery. But I guess this is still quite a long way to go. At least I am not much afraid any more now to brick my unit during testing/development.
[MTCD Android Head Units General] typos1:
It doesnt really matter about the device, only that its MTCD/E and Rk3368/PX5.

Good point about a bootable sd for flashing MCUs, think I d want to remind myself of what the other reasons were first though (if keeping TWRP as the main recovery).

Theres been talk of a "proper" custom ROM (no poffence MTCB/C/D/E ROM devs !) beore but nothings ever come of it (bootloader is locked I think), maybe cos of all the MTCapps and MCU integration ? OTA is already available though - RK3368/PX5 HA ROMs have OTA (you could use these on your unit, but dont think they have that Klyde button you like) and some custom ROMs for MTCB/C (booroondook's for instance) have had OTA for a few yeras.

BTW [MENTION=5092263]Hal9k_[/MENTION] has just released Nougat for ALL RK3188/PX3 MTCD/E units (all other N ORMS are for the 2Gb units only) and like his L ROM that Klyde screen button works on all units regardless of MCU, maybe you should contact him and ask him how he does it - what the code i, where it is etc ?
[MTCD Android Head Units General] Clandaries:
Is there another way to fix a px5? It seems like the nand is empty or there is missing something.

All i can do is update/install MCU. When i try to install update.img i get error I/O

If i change the board will it be fixed?

Maybe someone can help.

Regards

p.s. I have anew radio, it came with Android 8 and i successfully downgraded it to Android 6. And it is working very good.
[MTCD Android Head Units General] marchnz:
Hi,

You could try to obtain OTG or you're welcome to send the SOM to me to attempt recovery. I reside in New Zealand.
[MTCD Android Head Units General] supamicha:
Have you tried to flash unit new completely new ?

Take software from here : https://xdaforums.com/showpost.php?p=75508634&postcount=156

Use only step 1 and step 4. Flash takes about 15 min.
[MTCD Android Head Units General] marchnz:
Worth a try - Ive noted from a PX5 SOM sent to me that the SOM go into 'MASKROM' mode where the NAND has been erased or is corrupt. In this scenario, the PX5 will not attempt to boot SDCARD - the only way to recovery is via OTG.

Note, MASKROM is where the SOM goes into OTG mode to await reload/reflash via OTG.
[MTCD Android Head Units General] Clandaries:
Tried this for about 100 times now. Hope dies at last...

When i create boot-sd win10 or win7 (it does not matter) Then the little robot appears after 5-15 minutes. Then it takes 4-6 hours and then error.

I have tried everything. Recovery 6 and recovery 8. Nothing is working. So i really think it must be reanimated with otg, maybe.

Maybe buy another board? I think the price will be the same as shipment to New Zealand and back again :)

But io will have a loock :)

Regards
[MTCD Android Head Units General] Clandaries:
A package from Germany to New Zealand cost, one way, 63€.

So a new board is cheaper i think :)

Reghards
[MTCD Android Head Units General] marchnz:
Hi,

Unfortunately so. I wish more people had OTG :) Im working on simplifying OTG based on making a jig from readily obtainable parts...stay tuned :)
[MTCD Android Head Units General] typos1:
Really ? Have you searched for a better price ?

I can send to NZ from UK, fully insured for about 12GBP.
[MTCD Android Head Units General] marchnz:
Note - make simple OTG cable here without any headunit mods....
[MTCD Android Head Units General] Kyle M.:
Do any of those tools work on the FYT Units please?

thanks.
[MTCD Android Head Units General] marchnz:
The original zip downloaded was for JY FYT units and had all of the FYT equivalent MTC modules - so probably :) Unzip and take a look, if not sure where I mean, let me know.
[MTCD Android Head Units General] Kyle M.:
Hope you're right! Joying are not being very helpful with my issues and I still haven't found a custom ROM for my unit. (EU-JY-BO123P4). There was a dev making something but I think he's stopped after his unit got bricked. I'll rummage around with these tools a bit and I'll let you know if anything works.
[MTCD Android Head Units General] Kyle M.:
[MENTION=4974080]marchnz[/MENTION] I'm intending to pull my unit out and take it apart sometime next week after I receive a fan and heat sink for it. I'm gonna take pictures, do you guys need close-ups of anything in particular?
[MTCD Android Head Units General] Kyle M.:
Ok I've had a look at the files but I've never used this otg method before so it's going to be interesting. I'm planning to pull my unit out sometime betweeen this and next week to install a heat sink & fan, so that's when I'll try it out. What's the best combination of resistors in your experience?

I've started a thread specifically on my unit where i've put all its details. That's where i'll put the pics as well so feel free to let me know what you think when i'm working on it.

https://xdaforums.com/android-auto/android-head-units/px5-fyt-4-32gb-head-unit-joying-t3876469
[MTCD Android Head Units General] surfer63:
This is not correct. The first files were for an Joying STT unit, also known as the QD units.

An STT unit is different from a FYT unit and also needs to be flashed completely differently.

Actually: flashing a Joying STT unit with a custom rom is extremely simple. Flashing a Joying FYT unit requires a custom TWRP recovery, but maybe this SD-card approach might function as well, but not with the files from the first post.
[MTCD Android Head Units General] marchnz:
Quite right, thanks for the correction.
[MTCD Android Head Units General] kmlnvm:
My px5 unit turns screen to black, can you help me? When I insert sdcard.
[MTCD Android Head Units General] tankgod82:
I have a Rupse Head Unit. PX5 FYT 6026 with Android 8.0. I messed up somewhere and now it will boot. The unit has power. It is a vehicle specific unit. Witson, Rupse, AutoDVDGPS all make it. The Witson Model number is W2-222. When I apply power to the unit the red SRC Light comes on and thats is. I have tried several recovery SD Cards. I have tried reaching out to all the manufacturers. Nobody will help me. This forum is my last resort for recovering this unit. Can somebody please send me the files to boot this thing from the SD card.
[MTCD Android Head Units General] typos1:
What unit is it ? You need to quote your MCU.
[MTCD Android Head Units General] tankgod82:
Adding information

I have added pictures of all the information about my unit that I have. MCU is 2018-04-16 17:04:06 ZHAN_(NOR)__C9RD6686_CAN(A)PX5D1804160

Pics of Unit h**ps://photos.app.goo.gl/C1YaYLiC7WLASAK17
[MTCD Android Head Units General] typos1:
Yes, I ve seen the pics, pretty certain its not an MTCD/ unit, so cant really offer any help as its MTC units I know most about.
[MTCD Android Head Units General] polgoz:
Hi Guys, some place to buy a new SOM HCT PX5 Rev4 or better? on aliexpress there are just one.. and seller inform that could be not work for certain models..

Regards
[MTCD Android Head Units General] SomebodySysop:
px5 mtcd internal_sd error

I have px5 mtcd unit on which I flashed Malaysk 8 ROM. One day, when I tried to reboot, the screen went black and stayed black. Couldn't boot into recovery. So, created a recovery boot disk but when I tried to do factory reset realized that I've got an internal_sd error:

Using Recovery v 6.1.2 (from sd boot)

Failed to mount /mnt/internal_sd (no such device)

So, I tried to wipe data/factory reset

Cannot wipe data

E:failed tomount /metadata /dev/block/rknand_metadata (no such file or directory)

E:format_volume: make ext4 failed on /dev/block/rknand_metadata with 1(No such file or directory)

E:Failed to mount /metadata /dev/block/rknand_metadata (Blcok device required)

E:Can’t find misc

E:failed to mount /cache /dev/block/rknand_cache (Block device required)

Formatting /data

E:format_volume: make ext4 failed on /dev/block/rknand_userdata with 1 (Block device requied)

Data wipe failed

E:Can’t find misc

E:failed to mount /cache /dev/block/rknand_cache (Block device required)

Is there a tool I can use to fix this -- reformat / partition the internal_sd?
[MTCD Android Head Units General] marchnz:
What options have you considered from browsing the MTCD forums?
[MTCD Android Head Units General] SomebodySysop:
Well, there is AndroidTool_Release_v2.35-UseWithDriver44 which I downloaded, but there are no instructions and I don't know where to begin with it. If I could somehow use this to format/partition/create bootloader the internal_sd, seems that would solve my problem.

Then there is PX5 Upgrade Tool which appears to be essentially the Rockchip update create firmware tool I am running now, only it's all in chinese. I am creating my current sd boot card using this. It loads the recovery screen (from the card, I assume), but can not read the internal_sd.

I need a way to basically format and recreate the missing partitions -- I think. That's why I'm here: to see if someone can point me in the right direction to the right tool that will allow me to fix this.
[MTCD Android Head Units General] marchnz:
Are you booting recovery from SDCard or internal storage? Where I am going with this, if you are booting from SDcard and your internal storage is corrupt, OTG is likely your only chance.
[MTCD Android Head Units General] SomebodySysop:
Booting from sdcard. I did look at the otg thread. I'm thinking it will be more expensive, but easier, to simply replace the entire px5 core board. That should do it, right?
[MTCD Android Head Units General] marchnz:
Replacing the board might be cheaper for you, otherwise you're welcome to send just the SOM to me, I would be happy to attempt recovery at no charge, other than return freight (New Zealand 8061)
[MTCD Android Head Units General] SomebodySysop:
Thanks! I'm waiting to hear back from Xtrons to see if I they have a px5 board with double the ram and rom for my unit. If so, I'd like to do that. Otherwise, I guess trying to recover from the SOM would be the next step. Thanks much for the offer!
[MTCD Android Head Units General] SomebodySysop:
Received the new coreboard from Xtrons. It is Android 9, 4GB ram, 64GB rom.

Only problem: It did not come with GPS antenna . Can someone recommend video on how to solder px5 coreboard GPS antenna?
[MTCD Android Head Units General] typos1:
Dont think there are any videos of it, just find a pic of a SoM with the GPS antenna attached and solder it on the same way round.
[MTCD Android Head Units General] SomebodySysop:
If you have any ideas where I might find this pic, it would be much appreciated.
[MTCD Android Head Units General] typos1:
Any of the PX5 threads or google "MTCD PX5".
[MTCD Android Head Units General] marchnz:
The second image in your cross post is correct.

I.e. carefilly, with low heat/low wattage soldering iron, solder the shield/braid of the antenna lead to the big solder pad, and the second, inner signal lead to small round pad.

Note - be careful not to short out the lead. If still not sure, suggest contacting some local expertise.
[MTCD Android Head Units General] SomebodySysop:
Just as I suspected. There are two wires! I just wanted to have some idea of what to expect before I took the unit out the car and apart.

Thank you very much!
[MTCD Android Head Units General] SomebodySysop:
OK, finally took the unit out, took it apart (had to figure out how to remove dvd player) and got to coreboard. As I feared, I can't see the two wires soldered in the current coreboard (see images).

In addition, Xtrons sent me a video which shows just the one shielded wire being soldered to board: https://onedrive.live.com/?authkey=...46E!12714&parId=C8C0216FB487F46E!7099&o=OneUp

Help!!!!!

Edit: Scraped off some of the gunk and got (hopefully) somewhat better photos of current gps antenna solder.

Edit (2): Scraped away a bit of the insulation to see the actual wire(s). There only appears to be one braided wire. Am I wrong?
[MTCD Android Head Units General] typos1:
Looks like a standard GPS antenna wire to me - 2 wires, one at the core and one outer sheath.
[MTCD Android Head Units General] SomebodySysop:
Solder GPS Antenna to CoreBoard

Thank you for the reply. Sorry for all the posts on this subject, but no where on the Internet have I been able to find a clear example of what the two GPS wires look like, and where they go. None of this is readily apparent to the novice with zero documentation.

I have posted the relevant information on how to separate the px5 gps antenna wires and where they go in the coreboard in the two images below.
[MTCD Android Head Units General] typos1:
I m sorry but I dont understand your problem - there are 2 wires, one carries the signal and one is an earth you just solder on in the same way they are attached currently.
[MTCD Android Head Units General] SomebodySysop:
As it turns out, all my efforts came to naught. The coreboard I ordered from Xtrons, after I got the gps antenna correctly soldered on, turns out didn't even fit the motherboard -- it has two more pins in it than are on the board. Xtrons said put it in anyway and ignore the missing pins. Unit still wouldn't boot. So, I just bit the bullet and bought a new unit with the increased memory.

However, out of sheer honeryness, and because I've got the old headunit opened up now anyway, I want to try the SOM OTG method (that you recommended in the first darned place) to see if I can still get it working again.

My first question: Which one of the two methods below do you recommend I try in my situation? My unit will not boot or go into recovery. When I use a boot sdcard, the unit boots, but I can't wipe the partition or anything because the internal storage is corrupted.

Which OTG process do you recommend under the circumstances?:

1. PX3/PX5 NAND recovery - Bricked, Black Screen, BootLoop recovery thread

OTG/Loader Process

https://xdaforums.com/android-auto/mtcd-discussion-questions-development/px5-stuck-bootloop-t3635412

or

2. Factory Recovery

No Headunit Mod, Recover or flash SOM with a simple USB Cable

https://xdaforums.com/android-auto/...px3-5-headunit-mod-recover-flash-som-t3766892

Thanks!
[MTCD Android Head Units General] marchnz:
Use post 2, the first was my efforts in reverse reengineering OTG, the outcome being dthat the SOM can be directly connected for OTG via a usb cable.

Would suggest your SOM probably needs maskrom, but what happened/what did you do prior to it going brick?
[MTCD Android Head Units General] SomebodySysop:
I had been running Malaysk ROM v6 for nearly 2 years. Then, I upgraded to v8 and it was running fine for I guess a couple or 3 months. Then, one day, I clicked on the button to reboot the unit (Malaysk ROM has that button that you can put in your notification bar). It kind of stuck there for a long time, then the screen finally went black, and it never came back.
[MTCD Android Head Units General] marchnz:
If you get loader mode right away, it might be another problem. Cant hurt to try.
[MTCD Android Head Units General] Candanga:
Hello, I have an MTCE (MTCE_MX_V3.41) model from Witson which started to act funny after the first 2-3 weeks (froze on the Bootscreen, rebooted intermittently etc). Like 6 days ago, the unit got stuck at the Android Logo. I tried to reset it, remove battery power, etc. Nothing worked. Then I got it to boot to recovery.

The unit was unable to get back to factory settings, getting I/O errors. I tried then to prepare the unit using the 2 SD card method (SD_Firmware_Tool.exe) . When trying the first SD card (under the GPS SD), the unit booted and I didn’t see anything get installed nor asked me about installing anything, then it rebooted and the display is dead (no backlight). I now only get the LEDs to blink 3 times if I press the power button for some seconds and THAT’S IT. I removed the unit and the casing to inspect it, all seems fine.

FINALLY the seller gets back to me (after almost 2 weeks, because they fear they might get the flu) and send me the original MCU and updated ROM [hct4_PX5_9.0_ota(2020010x] useless if the unit is dead). I’m now reading the forums and looking for a proper way to flash this thing but the instructions are a little bit confusing.

Is there a simple SD card method I can try before the OTG? Thanks!
[MTCD Android Head Units General] marchnz:
Yes, an SDCARD create tool method is supported by Rockchip, which you could try. That said, Unless someone shares the px9 bootloader/recovery as an .img, you're out of luck, unless you want to try Hal9k ROM, that contains the android 9 loader for his ROM. You will be tied to that rom however.

As posted in my OTG thread, all tools downloadable from here: https://github.com/rockchip-linux/tools/tree/master/windows

Just for clarity; only android 6 updates were released as .img updates, which this tool uses. Android 8 and 9 are OTA .zips, which dont contain recovery img files. You need a boot loader image for SDCARD create tool.
[MTCD Android Head Units General] Candanga:
So the only way I can use the sd card tool is with the OEM img file? The OEM update.zip image the seller sent me is useless?

What about the tool used with yout OTG method, same story?

Thanks again m8
[MTCD Android Head Units General] marchnz:
From your post, you are unable to enter recovery; do I understand correctly?

If so, assuming your SoM has a corrupt recovery, you can try to flash an android 9 recovery using either Malaysk or Hal9k sdupdate.img to flash their Android 9 recovery via the sdcard tool. See their thread and follow the update from android 6 or android 8 steps (to get a working android 9 recovery.)

If able to flash the recovery (assume SOM is OK) you can then proceed to try flashing the update.zip directly on the head unit.
[MTCD Android Head Units General] Candanga:
Great, when I get back home I will try that.

Thanks again :)
[MTCD Android Head Units General] marchnz:
You're welcome. As an FYI - if the SDCard method fails, the next step is to flash the recovery [sdupdate.img] directly via OTG. If this is the case, I would hazard a guess that the SOM will need to be forced MASKROM.
[MTCD Android Head Units General] Candanga:
Well, I created the SD using Malaysk's SD_Firmware_Tool_For_PX5_android_6_0_1 method with no result. I used both, the MAP and SD slots (even gave it a shot at the back USBs, the card reader won't even get lit). I'm using a variable PSU and the output current is about 0.350 amps. The only thing I can see is that the current varies from 0.228 an briefly spikes to 0.380 and then gets stable at about 0.227, and it stays there.

At the beginning I had hope that the unit was processing the info, but I'm guessing its just random stuff that is doing on the background.

The seller was notified already, as this unit is barely 4 months old and had no modifications at all. The unit just died.

One thing I did noticed, is that the SoM is UNDER the DVD unit (literally touching it), and its separated only by a piece of brown cardboard (doesn't seem to be any kind of thermal pad). This cardboard sticker is obstructing every single ventilation port on the SoM. I haven't removed the SOM's heatsink yet, as it has red "faith" paint over the screw heads, and I don't know if "Mr. Chen" wants his SoM back for replacement.

I'm suspecting somehow, a possible cold solder scenario due to improper cooling, which can be easily fixed by my resoldering station (reminds me those Compaq laptops and AIOs with the shared heat sink for the CPU and GPU :silly: )

Anyways, moving on to remove the SoM and build the OTG interface.:eek:
[MTCD Android Head Units General] focccus:
Can I have your SD files?

Thx.

Edit:

I found here
[MTCD Android Head Units General] focccus:
I found here

Android-HU - Google Drive

drive.google.com
[MTCD Android Head Units General] bms888:
Hello, I have a PX5 Rev4.0 board with Android 6 in my head unit. It has been a MCU MTCE GS. After updating to the latest Android 6 version and MCU update (via USB) it is a MCU MTCD GS. I wanted to update to Android 9, but it doesn't recognise any SD card except my USB. Neither GPS nor SD. Can this be a software problem or is the hardware defective? Can I test this?

Thanks for help.
[MTCD Android Head Units General] typos1:
The latest GS MCU is MTCE, so the MCU update you used was not the latest, check my signature for the latest GS MCU.

Sounds like a hardware fault have you opened it up and checked the sdcard ribbon connectors havent come undone ?
[MTCD Android Head Units General] bms888:
OK. You´re right.

I now have the MTCE GS V3.56_1. But SD still not recognised.Is there a way to get to android 8 and then A 9 without the SD? Everything I found was only via the SD.

Sincerely
[MTCD Android Head Units General] marchnz:
Per post #1 - OTG.