PX5 stuck in bootloop - MTCD Android Head Units Q&A

This Post details how OTG/LOADER can be achieved to recover a corrupt PX5 or PX3 - any RockChip MTCx SOM
Update 2/2018 - anyone can make a gig without modifying their main board. BUT FIRST try a USB port, some have OTG out of the box.
From the work I've now done, Ive realised you don't need to hack your mainboard. You could temporarily solder connections to SOM or make JIG from header pins or make a simple cable from an old USB cable and two resistors: see: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Making a jig is necessary , 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.
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.)
With USB connected, power on. Use tools/load driver as described in recovery thread.
Q/Why hardware mods?
A/Mods were necessary because out-of-the-box (default) both my GS and JY boards would not enter USB OTG/Loader mode to connect it to a PC for recovery. We now know that a "jig" can be made without sacrificing your mainboard and simply wiring to header pins or buying a SOM header from say Digi-Key.
- Your MTCD may be different -so test first!
Q/My SOM won't appear in device manager or Rockchip Android tool
A/ If all connections are correct and power is Ok, force MASKROM as detailed here:
https://forum.xda-developers.com/sho...&postcount=128
https://forum.xda-developers.com/sho...&postcount=129
***Updated 08/Dec/2017 - Attach image showing USB Male cable connections to mainboard***
** Note - SD recovery boot card did not work for me on PX5 - probably due to version of [rockchip sdcard image create tool] - if anyone has a version that works, please post here.
Updated Feb 2018 - Android 6 SDCARD create tool is now available. Recommend SDCARD method and then OTG if SDCard method fails
Synopsis
My corrupt NAND was successfully reflashed using OTG "LOADER" mode as follows. It became corrupt , stuck in a bootloop and unable to enter recover following flashing a custom (bad) firmware image file.
- Using an MTCD GS board - which I have as a spare part - no display, only board.
+ Windows 10 x86 notebook with rockchip batchtools v1.8, rkimagerepack tool, latest PX5 image.
+ USB stick formatted fat32 with latest PX5 image
Do not do the below mainboard mods, this is completely unnecessary and posted for background on the journey to find a simple way of getting OTG.
1. Modified the board as follows:
A. Desolder and lift pins 27 & 28 of USB hub GL850 (thanks to xda user @ikerg and 4pda - for the lead)
B. Solder Male USB a cable to GS board USB 1 connections (See below attached image showing where USB male plug wires were soldered)
C. Remove pin to RK PX5 SOM [ctl_recovery]
D. Solder a wire directly on PX5 SOM header on [ctl_recovery]. This wire is used to trigger recovery.
Process
Initial recovery image: Because the PX5 firmware (OTG) "LOADER" process timeout appears to be approx 1 minute, it was necessary to create a recovery only image, as the 1.2gb PX5 firmware file exceeds the timeout, aborting the flash.
Using RKIMAGEREPACK, I created a image with a dummy zero byte system.img. This resulted in a 200mb image file.
- Loaded [rockchip batch tools] on notebook.
- Installed rockchip drivers
- connected USB cable to notebook
- held [ctl_recovery] wire to [mcu 3.3v test pad]
- Powered headunit on
- Notebook 'USB chime' was heard and board became connected, as indicated as highlighted '1' in rkbatchtools
- wiped flash
- selected firmware image without system created above and flashed to PX5
- powered off, removed PX5 SOM and refitted to JY headunit board
- On JY headunit, powered on, entered recovery via [holding powerbutton for approx 15sec - wait for 3 flashes of led] press once more.
Successful boot into recovery - started booting recovery and warned that system image was not valid. PX5 self-formatted system and awaited image.
- inserted USB stick with latest PX5 image and upgraded.
First boot waited for 5 minutes. Pressed reset and rebooted - successful recovery!
The warning here is that the PX3 SDCARD image create tool does not work for PX5 - even when using a PX5 image.
Why did I post this? Original Post:
I have a (JY) MTCD with HA 2..56 MCU PX5 stuck in a boot loop - "starting apps" appeared and then it reboots, looping. I was unable to access recovery via any of the standard recovery processes (e.g.holding the power button or boot into recovery via bootable SDCARD.
========================================
On SDCard boot - works OK on PX3 but on PX5, only a black screen is displayed without any text.
SDCard and button holding recovery methods worked OK on PX3 board, but not the PX5 Module when the SOM NAND was corrupt.

Ok - need to figure out how to force this PX3 board to 'maskrom' - this is the procedure where the NAND is suppressed by grounding the I/O or Oscillator to effectively stop the NAND. This then places the RockChip PX5 into Maskrom mode to then connect/reflash via USB.
Anyone tried this?
Feb 2018 - MASKROM methods have been identified for both PX3 and PX5 Modules. See posts later in thread.

You seem to think you have both a PX3 and a PX5 board....it is one or the other.

nixfu said:
You seem to think you have both a PX3 and a PX5 board....it is one or the other.
Click to expand...
Click to collapse
Thnaks for your reply - clarifying [I have a (JY) MTCD with HA 2..56 MCU PX5 stuck in a boot loop]
I have a PX3 Board that I have swapped back in to test - it is OK. The PX5 goes black screen if trying to boot from SDCARD recovery and I cannot seem to force it into [maskrom] to flash from PC either.
Would be interested to hear if other PX5 users who have swapped from PX3 to PX5 can access recovery OK.
Note that I foolishly screwed up and flashed a custom image thayt contained what I think may be the wrong achitecture of SUPERSU, hence the boot loop. BUT this doesnt explain why I can no-longer enter recovery, or does it?
Regards,

try holding the reset button for about a minute. it should auto restart into recovery. it will first go off, then it will either pop back on suddenly or start turning itself on and off. if it does the on and off thing i usually let it boot to recovery on the third one

Thanks for the info.
Ive done everything but holding the power/vol knob or reset for 1 minute.
Tried forcing the unit into mask rom by very carefully exposing some of the obviously IO tracks between the cpu and flash and shorting a pair (this is the method described elsewhere, but usually there are copper test pads (you'll see these on the px3 module but not px5))
No matter what I try, I cant get my pc to see the head unit via either usb sockets. I made a 1 to 1 usb A male cable which works with a nexbox OK but not these headunits. The HU is a JY UL124 orginally px 3. It has 2 sdcard slots and two usb.

After significant research and testing, I have a recovered PX5! See Post#1

Good.....clap clap clap
Your tutorial is very clear and useful for other people....No more bricked devices....

ikerg said:
Good.....clap clap clap
Your tutorial is very clear and useful for other people....No more bricked devices....
Click to expand...
Click to collapse
Thanks - updated op with a couple of images of my test/recovery jig and software.

marchnz said:
After significant research and testing, I have a recovered PX5! See Post#1
Click to expand...
Click to collapse
good work there - would like to check my px3 board so did you ground to GND or D0 for reset on px3 pads ? and if you could show which wires on usb lead you connected to pin 27 & 28 on GL850 chip that would be very useful thanks

audisean said:
good work there - would like to check my px3 board so did you ground to GND or D0 for reset on px3 pads ? and if you could show which wires on usb lead you connected to pin 27 & 28 on GL850 chip that would be very useful thanks
Click to expand...
Click to collapse
Great question and good spotting - on px3 its possible to force "maskrom" by shorting [gnd] & [d0] pads. Unfortunately px5 do not have these pads and can only be achieved on px5 via carefully exposing track insulation to NAND - fortunately px5 will enter "loader" mode on recovery. So, no I did not do this, I used a GS board I have as a spare part and modified it to force recovery, by removing the SOM header "recovery" pin and grounding that pin via a switch - to force the SOM into recovery.
Note that OTG USB connections are made to the USB switch IC (if fitted) U27 [fsusb42]. If this IC/USB switch is not fitted, more drastic mods would be needed to disconnect the usb connections to the usb hub IC (by disconnecting the SOM header pins.) If you have a GS, you have U27. If not you will need to check.
Happy to answer questions here, we can all benefit through sharing.

marchnz said:
Great question and good spotting - on px3 its possible to force "maskrom" by shorting [gnd] & [d0] pads. Unfortunately px5 do not have these pads and can only be achieved on px5 via carefully exposing track insulation to NAND - fortunately px5 will enter "loader" mode on recovery. So, no I did not do this, I used a GS board I have as a spare part and modified it to force recovery, by removing the SOM header "recovery" pin and grounding that pin via a switch - to force the SOM into recovery.
Note that OTG USB connections are made to the USB switch IC (if fitted) U27 [fsusb42]. If this IC/USB switch is not fitted, more drastic mods would be needed to disconnect the usb connections to the usb hub IC (by disconnecting the SOM header pins.) If you have a GS, you have U27. If not you will need to check.
Happy to answer questions here, we can all benefit through sharing.
Click to expand...
Click to collapse
Thanks for reply - my px3 board appears dead in unit thus far - think i've worked out how to solder usb A cable now just didn't want to cause any damage mixing tx/rx wires - i'll have to retest but i think I had 3.3 volts at GND & D0 pads - no time today but will have a go tomorrow (hoping this board is where Nand or fried chip fault lies) I have ordered a PX5 board so hopefully will get unit working

Had a try with px3 board - lifted pins 27 and 28 - put software and drivers on laptop - soldered usb lead to d+ and d- on px3 board and ground traced from u27 and ctl_recovery wire - nothing happens still - power at u27 is 3.3 volts

audisean said:
Had a try with px3 board - lifted pins 27 and 28 - put software and drivers on laptop - soldered usb lead to d+ and d- on px3 board and ground traced from u27 and ctl_recovery wire - nothing happens still - power at u27 is 3.3 volts
Click to expand...
Click to collapse
Good work! How have you isolated the header pins - if they are still all connected (ctl_recovery, d+,d-) to respective ICs, it wont work because of contention with the connected ICs. E.g. ctl_recovery is connected to MCU and is pulled up to +3.3v by MCU - my solution was to remove respective header pins by careful desolder - they can then be refitted.

Knew i'd missed something - header pins still connected so will try to isolate guessing I need only connection at SOM board only..

pins isolated but no luck yet.... think maybe my chip is faulty (others report some px3 chips come from faulty batch) so will wait px5 board delivery - if that works I might order a replacement px3 chip and try replacement

A bit over my head
Any chance I could get a hand ?
Maybe over Hangouts or something ?
Please Please Pretty Please lol
Here's what I'm workin with https://goo.gl/photos/uNTpFnUYJxZ3VwSJ7

Got the new PX5 board (12 days from China ) put into head unit and worked straight away - posting here as I had major trouble re-soldering pins 27 & 28 when I pulled a leg off GL850G usb chip - see attached pic of wire I had to solder in place... thinking if I did this again I would probably just make a break in circuit tracks and use conductive glue or nickel pen to remake circuit - PX3 board is still dead - never got usb to pc connection - as for Cid6.7 board - looks like you found the usb hub chip and switch chip (different boards to mine though) pin 27 & 28 are opposite dot on chip - usb switch chip should go +5v, sel, d+ , d-, and ground

Is all this done just for the pc to detect the unit..?
If so what if the pc already detects it BUT unable to write to it with 0 modifications done to it..?
https://goo.gl/photos/m7NGyrkD4ef2YydD7
audisean what did you pay for the PX5 board if I may ask..? I'm wondering if I am able to swap chips from Sofia to PX5 with no mods

Cid6.7 said:
Is all this done just for the pc to detect the unit..?
If so what if the pc already detects it BUT unable to write to it with 0 modifications done to it..?
https://goo.gl/photos/m7NGyrkD4ef2YydD7
audisean what did you pay for the PX5 board if I may ask..? I'm wondering if I am able to swap chips from Sofia to PX5 with no mods
Click to expand...
Click to collapse
I paid about £95 for the board with airmail dispatch - not sure if it would work on yours - fitment looks similar with pin header - Witson 32814450733 is what I bought - worked straight away and recognised settings from previous android system in unit. The PX3 mods were necessary for otg cable to link pc and flash - if you have recovery by SD card or front usb you won't need it. Sofia looks pretty different but if you can link pc did you try rockchip batch tool ?

Related

USB download mode working on Genbook108 need .img files

I've gotten the genbook 108 into Download mode by opening it up and holding down the s1 button next to the cpu board inside this unit. With the correct cable and drivers I can see the unit now inside windows. I want to get the images so I can start flashing and attempting to dev this without worrying about bricking the unit. Augen is AWOL (out of business) and the company selling them now is an asset recovery company.
I just bought one of these, and am disappointed in the Android 2.1 implementation the mfg used. If you get a linux version or higher than Android 2.1 working, I would be happy to be a beta tester.
I've also now relace the crappy internal wlan with a tenda .. its usb ftw littlesoldering
Sent from my SPH-D700 using XDA App
Progress?
Darkpoe, have you had any progress with your setup? I have the genbook and have been stuck without any luck. Could you maybe post some pictures of your setup?
darkpoe said:
I've gotten the genbook 108 into Download mode by opening it up and holding down the s1 button next to the cpu board inside this unit. With the correct cable and drivers I can see the unit now inside windows.
Click to expand...
Click to collapse
I drilled a hole in the bottom of my unit to expose S1 but I can't figure out how long to hold it down for. Hints?
When you say "Correct Cable" you mean an A-A USB cable?
genbook roms
Anyone attempting to reflash a genbook 10.2 beware if you flash wrong rom you will brick the netbook for sure,you must have correct fdwn files to restore the system as of this posting i have not been able to locate them since augen is now out of busniess.If you brick it you will have to open up the unit and short out the rom chip several times to get computer and fwdn program to see the netbook doing this too much with short out the pins which are very very soft material and will mash together causing a perment short circuit.You can only do this about 3 times before this will happen so make sure you have all the fwdn files ready to flash before using this program

[Resolved] [tutorial] usb otg for desire s (saga)

This tutorial is aimed to ones who wish to have USB OTG Capability within their
HTC Desire S ( Saga ).
1: what you need ( software )
A USB host capable kernel or your Android Must support USB Host APIs.
if you don’t have proper kernel you will not get USB OTG support, in my case
I flashed kernel 3.0.76 from Stefan on ics Final v2.0 ,Android version 4.0.4, sense 3.6, Now there is another kernel, I have Hboot 2.0******.
Available with USB Host capability the version is 3.0.89, I have not tried this kernel
Yet, you can if you wish, you can find both of these kernels at XDA.
If your rom or framework does support USB Host APIs then may be you don’t need to flash
The kernels.
With a linux patched kernel USB devices are detected under “ sys\bus\usb\*.* “.
If your android system and framework supports USB Host APIs, Android will detect USB devices
Under “dev\bus\usb\*.*”
Install USB Device info from google play store.
Install USB Host Diagnostics from Play Store.
Install USB OTG Helper from Play Store or any other software like Stick Mount to mount your USB STORAGE DEVICE.
You must have root access and super user installed.
Before flashing the kernel always make a backup of your current Rom.
As in my case when I flashed the kernel my wi-fi stoped working and then I had to manually push some wifi related files to system directory.
2: Hardware
You need a USB OTG Cable, unfortunately USB OTG cables available in Market are not suitable for Desire S, because Desire S does not Power the USB Bus within its own, to wake up USB Host Capability for Desire S we need to short Pin 4 and 5 at Micro B plug, Micro B female is incorporated within Desire S.
If a cable with shortened pin 4 and 5 is available then you don’t have to make a cable.
Its recommended not to short pin 4 and 5 at micro B plug, its good to sold a 10k resistor between pin 4 and 5. Get a standard charging cable for you Desire S with Micro B Plug, First of all check this cable by connecting it to your computer, if charge only and disk drive options appears at your phone the cable is good for our purpose.
Secondly get one Standard USB Extension cable, this cable has 4 pin Male at one end and 4 pin Female at the other end. Cut this cable from the center, remove the shielding plastic and uncover the wires.
You will find four wires,
Red = POWER ( Normally 5 Volts )
White = ( Data- )
Green = ( Data+)
Black = GND ( Reference Ground for 5 Volts )
Get a soldering iron and a piece of solder wire.
Now pick Male end, cut white and green wires ( we don’t need them because we only need power wires from this plug ).
Now pick Female one, uncover the wires from this also, Make a joint of Male “RED” with Female “RED”, and Also Make a Joint of Male “BLACK” to Female “Black”, don’t cut “WHITE” and “GREEN” wires.
Now cover “RED” and “Black” with some sort of Glue or Adhesive Tape, Glue is better choice because it will prevent the wires from getting short, or you can use heat shrinking sleeve.
Now pick your standard charging cable and cut it from the center and hold the end having small Micro B Plug, uncover plastic shielding, you shall find following wires,
RED
WHITE
GREEN
BLACK
Now get the cable you already mad having Standard Male and Female and Make joints as follows.
RED = RED
WHITE = WHITE
GREEN = GREEN
BLACK = BLACK
Double check all connections and now the important part comes
Gently remove the plastic from behind the Micro B plug with sharp knife or cutter, be careful and be patient here because in a hurry you can damage the plug or wires.
After you remove the covering Micro B plug you will find “ RED , WHITE , GREEN , BLACK “ wires soldered.
Notice that only one point at Micro B plug is Empty, There you go, it is pin No 4 of Micro B Plug.
You will also see “BLACK” wire there, Now get your 10 k resistor, sold one end of the resistor to where the “BLACK” wire is soldered and sold other end to pin No 4 which you have already found empty.
Be careful here not to short any pins, it may lead to a disapointment. Your USB OTG CABLE is ready, put some glue where you find its necessary to cover and also over the Micro B plug from where you remove the plastic.
Now run USB Host Diagnostics and when it says to plug in then plug your micro B connector to the phone, you don’t have to apply power through mail connector until. USB Host Diagnostics should show
As following picture, it will detect USB root hub of the phone, if it does not detect anything then
May be there your cable is not prepared properly, or just Restart your phone after installing USB HOST Diagnostics and check again, USB HOST Diagnostics needs root access if USB HOST APIs or framework is
Not supporting USB HOST MOD.
Now apply power through your charger to MALE connector, after 5 or 7 seconds your phone will indicate charging, means the cable is correct.
Put a USB stick in USB Female connector, open USB OTG Helper and hit MOUNT, it will mount your USB storage device and will create a directory at the root of your SD card named “UsbOtgDrives”.
You can brows the files and directories of your device in that folder.
Un mount USB Mass storage through USB OTG Helper and connect any USB mouse and you will see a small cursor, its very small and but you can locate it, if pointer does not appear remove the power plug and connect again, same way you can connect a USB keyboard, connect a USB keyboard and open any text editor in your phone and check by typing from keyboard or open your sms editor and check it there.
You can get your device info with “USB Device Info” if you installed it from play store.
Wow...now...
that is one of the great tutorials that were missed
in our forum
many thanks from saga community:good:
asgardr said:
Wow...now...
that is one of the great tutorials that were missed
in our forum
many thanks from saga community:good:
Click to expand...
Click to collapse
I wrote tutorial, but there was a question i did asked, "does viper saga supports USB OTG AND USB HOST API, BUT UNFORTUNATLY NOBODY REPLIED, SO I SPARED SOME TIME AND INSTALLED THIS ROM TO MY DESIRE S, IT WAS ACTIVATING CAR DOCK MOD AS SOON I PLUGGED USB OTG CABLE BUT WAS NOT DETECTING ANY USB DEVICES, I SPENT TOW HOURS ON THIS ROM AND NOW EVERRY THING IS WORKING " MASS STORAGE, CDC-ACM- PL2303 SERIAL CABLE, CH340, CH340, SERIAL CABLE AND ALL HID DEVICES. IF SOMEONE IS GETTING PROBLEM CONNNECTING THOSE DEVICES, PLEASE PM, I WILL TRY MY LEVEL BEST TO HELP.
Many Thanks
MNASWL said:
I wrote tutorial, but there was a question i did asked, "does viper saga supports USB OTG AND USB HOST API, BUT UNFORTUNATLY NOBODY REPLIED, SO I SPARED SOME TIME AND INSTALLED THIS ROM TO MY DESIRE S, IT WAS ACTIVATING CAR DOCK MOD AS SOON I PLUGGED USB OTG CABLE BUT WAS NOT DETECTING ANY USB DEVICES, I SPENT TOW HOURS ON THIS ROM AND NOW EVERRY THING IS WORKING " MASS STORAGE, CDC-ACM- PL2303 SERIAL CABLE, CH340, CH340, SERIAL CABLE AND ALL HID DEVICES. IF SOMEONE IS GETTING PROBLEM CONNNECTING THOSE DEVICES, PLEASE PM, I WILL TRY MY LEVEL BEST TO HELP.
Click to expand...
Click to collapse
I tried ur tutorial with SVHD 2.1.0 ROM on my HTC Desire S with kernel 3.0.76 and it is working superbly, my wifi stpped working after the kernel flash but after flashing the boot.img via fastboot solved the problem .. I did not try to make a usb cable as u narrated instead I am using Y cable for it which has a separate mini usb power adapter and USB slot for pen drives... Many thanks bro :laugh:
Is there any existing cable on the market now that I can buy? I'm low on time to make my own
cable
broucker said:
Is there any existing cable on the market now that I can buy? I'm low on time to make my own
Click to expand...
Click to collapse
no such cable is available in market for desire s,you can try y cable with standard usb to otg converter.
Please can some one get a video of his tutorial for me to take a close look at it to make my own. I really need it to work on ds. Thank u all. I would be very happy to see that video
Just try to closely see the pictures and read care fully what I have written, in case if you feel difficult let me know , will try to spare some time to make video. Any ways it's easy.
MNASWL said:
Just try to closely see the pictures and read care fully what I have written, in case if you feel difficult let me know , will try to spare some time to make video. Any ways it's easy.
Click to expand...
Click to collapse
I am using a custom viper saga Rom, i've install the Stefan kernel, and I have closely followed everything step as you said, but still can't mount any drive. My USB host diagnostic show exact as your in the picture, but my USB helper still can't mount drive..... Please I need help fixing the issue
This Rome will not work.
Install victims saga 2.0 rom.
That will work.
Sorry virtuous saga 2.0

A5X Max+ TV Box problem

Hi,
I found SuperSu in the applications part et open it.
The box asked me to update it.
I have updated my SuperSU et restart my box, but now I could not get past the splash screen!
Have you a process to solve this problem?
Thanks for your help.
Just flash the latest firmware https://drive.google.com/file/d/1PmksYJ-Aj4__m_4TEhYGaVVthNzbLtQK/view?usp=sharing
Unfortunately, flashing requires this strange Standard_A_USB_male to Standard_A_USB_male cable. You can buy it or you can cut two regular cables in half and solder together two pieces of cables (connect wires of the same color) to have two A male connectors.
Use USB-4 socket on the A5X to flash, others will not work.

Fairphone2 (FP2) how to use UART ?

Hi there
I own a fairphone wich suddenly dead a few weeks ago (won't boot, wont charge, black screen).
Since murphy is great, I relealize my backup procedure wasn't working for my internal storage (but worked great for my sd card wich I don't care .
So my goal is to find a way to dump the 32gb emmc internal chip to a card in the phone's sd card slot, or downloading a dump of this even by serial ..
My first attempt is to use the uart port inside the phone, to see if it's says something usefull.. It seems to do, but for weeks I can't have anything more than garbages (like parity errors or grounding defect).
I have by now:
- tried 3 differents pl2303 usb/serial adapters (working perfectly for beagleblackboard & olimex arm boards), 1 motG rs232 (real uart to rs232),
- tried putty (with serial settings) and differents terminal emulators (outport, coolterm, telix on dos)
- started with 115200bps/8/n speed settings and a bunch of variations ...
- soldered at first tx/rx & gnd directly on the FP2 board and since, bought the "real" connector from mouser.com....
The uart/bootloader say something but I definitevely can't read it... Can someone help me ?

Android 9.0, MTCE MX2 PX30 head unit bricked?

I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Timpuli said:
I
have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM
and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse
Good efforts made in trying to restore.
If your unit is an MTC(D/E) and the OTG cable is correct, with USB powering OK, forcing MASKROM should enable SOM connectivity via USB. To force MASKROM, typically there are two pads that must be shorted while powering on the SOM while connected to OTG.
Take a close look at the board for pads close to the eMMC/NAND. Attach a high res image here for further help.
Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Timpuli said:
Thank you for the comments so far. Yes, unit if MTCE and I think that OTG cable is fine also. I have even tried it with different resistors but SOM is not recognized by PC...
Here is some links for the pictures, it would be great if someone could help me find points where SOM can be forced to MASKROM mode.
https://drive.google.com/file/d/1WVujL00jDu6RYLzpD7xxoNL1gY_15R2-/view?usp=sharing
https://drive.google.com/file/d/1bF6Kxu1k3DtSquUenu508qXxL-CI2hGx/view?usp=sharing
https://drive.google.com/file/d/1ioM8vtH-zuU5seyLaBnt2qdzN02kNfNW/view?usp=sharing
Click to expand...
Click to collapse
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.
marchnz said:
Hi, excellent hi-res images. I have annotated one of the images I believe are the Maskrom pads.
Sounds like you've had a thorough read through OTG threads, which explain the sequence - basically short while device is being plugged in/powered on by USB. nice one. Let me know how you get on.
Click to expand...
Click to collapse
Success!!! Thank you so much to encourage me! MASKROM pads confirmed for PX30, after shorting those pads SOM went directly to MASKROM and I was able to restore my system. Only problem is that only FW image what I found was Android 8.1 and my "bricked" android was 9.0 But even this is much better than bricked unit
I made also some other modifications before trying to MASKROM-mode and I'm not sure were there other issues before. Anyway, I made new OTG cable with a little bit thicker wires. I also changed resistor values from 12k // 22k to 6k // 11k. And finally I made dedicated pliers to short MASKROM pads.
Is there anything else to do for upgrade to Android 9 than use ModInstallerPro by Hal9k?
Thank you so much marchnz!!! You are great!
HELLO
please give me the .img software you wrote through otg / maskroom for px30
Timpuli said:
I have Android head unit sold by Witson, processor PX30, MX, MTCE. I did a big mistake and give rw permissions (with ES explorer) for all folders for my rooted head unit... After restart the unit did not work anymore. There is booting image on the display for appox. 40 second, after this unit shut's down. At least it seem to do so because at same time usb ports lost their power. So unit is not totally dead/ bricked but it wont boot or I can't enter recovery mode anymore.
My unit do not have any buttons (no hard or soft buttons) and there is no RST button.
I have try to enter recovery mode several times by keyboard with different key combinations ( alt / right alt + print scr + E or I) but with no luck. I also tried to flash firmware with SD-card or with USB-stick but without success. I also removed MCU or SOM and tried to flash it by OTG method but my SOM did not respond (PC did not recognice it) and I do not know how PX30 can be forced to Maskrom -mode?
Is there anything to anymore? How I can save my PX30 board, any good comments, please?
Click to expand...
Click to collapse
Sorry for late answer, I haven't noticed this... I hope that you have already find a proper .img file for yourself, but if not, I just downloaded some Android 8 installation package from 4PDA site. And when you unzip this package, usually there is .img file also. I haven't found any .img file to Android 9, so can't help with that, sorry.
Hello! @Timpuli, I am in the same kind of a problem that you had.Can you help me? I made the OTG cable but the SOM in the thread has 2 more rows and I don't know how to connect it to my PX30.Here's how I tried.Thanks!
Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..
Timpuli said:
Look at SOM board picture in topic https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
In the third picture you can see that there is "two pins missing" at the left end of the socket... And if I remember right, in my PX30 SOM, there was socket all the way, like you wrote. So, you must take those missing pins into account, or start to calculate right pins starting from the pin 5...
Edit. Pin no. 1 is in top row/ left one pin. Pin. no 2 is in bottom row/ left one pin. And so on..
Click to expand...
Click to collapse
So, they are like that?
PIN1 | PIN3 |
PIN2 | PIN4 |
And so on? On my SOM. Also, can you take a look at my cable, is it okay? Here is how I tried, I also tried to move all connections two rows to the right, still nothing.Also when I connect the orange leads to the SOM voltage goes from 3.14 to 1.7V. Is this normal? Thanks a lot for the fast reply, gotta get you a beer!
Yes, pins goes like that.
And if you make connection like in the picture it is wrong. You have to move pins two rows to the right, thats correct.
Your cable looks fine to me. I can't remember voltage values anymore, sorry.
I have some difficulties also and that's why I have to change resistor values from 12k and 22k to 6k and 11k. Also it might take couple of tries to enable to maskrom-mode.
Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...
Timpuli said:
Look at thread
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
again. So, there is said that voltage should be between 1.8 to 3.3V to 'tell' the SOM to go into OTG recovery mode. So, maybe 1.7V is too low...
Click to expand...
Click to collapse
It is 3,14V when it is not plugged to the SOM. when I plugged in it drops.Anyway, I am gonna try again! Thanks, if I have more questions I will ask you! I really appreciate that you helped and replied really fast.
Ok, I hope for the success. I assume that you have installed drivers already? Sequence to enter masrom-mode is:
1. Short maskrom mode pads and keep those shorted.
2. Plug in OTG-cable to usb-port...
3. When windows detects SOM-board remove shorting from the pads.
It might take several tries to have success to enter maskrom-mode. Have you checked is SOM-board detected in Windows device manager?
Yes I did. I will try again with MASKROM and check voltages on orange leads.I will keep you updated.
@Timpuli, I got it in MaskROM mode!Successfully connected, now I am searching for a rom with a .img. Once I find I will flash it and see if it works!Thanks so much!
Question. On the core board does anyone know what pins are for UART? slightly off topic but I've managed to boot a Ubuntu kernel on my px30 but it's a bit glitchy so would like to work out what pins are for serial console
Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?
UKSFM99 said:
Does anyone know what's happening here?.
So I've tried to flash a custom OS using maskrom, but the device keeps cutting the connection anywhere from 40% to 60% complete - it's driving me insane having tried about 15 times now to get it to flash.
Attached is my current maskrom setup....I'm trying to flash a Ubuntu based OS based on the Firefly px30 system.
Should all that fail, does anyone have the necessary files to maskrom my way back to android?
Click to expand...
Click to collapse
MCU cuts power after a period.
Remove board from mainboard, use jig instead.
marchnz said:
MCU cuts power after a period.
Remove board from mainboard, use jig instead.
Click to expand...
Click to collapse
Ok will try.
I can't get it to work though, what pins should I use for the JIG.
Currently I have the following:
1 - 5V
3 - GND
20,28 - 15k resistor (1.2V)
29,30 - USB Rx, Tx

Categories

Resources