PX5 stuck in bootloop

Search This thread
By:
Advanced…
Akuma666

Akuma666

Member
Nov 28, 2020
9
2
marchnz said:
Sounds like you've followed the process to the letter.

The device is in maskrom mode, did you force that, or did that happen by itself?

If self, try another version of the tool.
Also, just to try, try erasing using an Android 6 version first.
Click to expand...
Click to collapse

Answering your question - The device is in maskrom mode, did you force that, or did that happen by itself? - (The device was automatically detected as a MaskROM device)

You were spot on with your recommendations. I was able to connect the SoM as a Loader Device with AndroidTool_Release_v2.43 (I was using v2.69 earlier). I then tried flashing sdupdate-A8-Kumarai.img but it failed at "Murex Reset Device" step.

Next I tried flashing it with Android 6.0 as per your second recommendation and the process succeeded 100%.

With Android 6.0, the SoM was recognised as a Loader Device. I then tried flashing it again with sdupdate-A8-Kumarai.img, hoping to get to Android 8.0 and it failed.

The SoM is now again stuck as a MaskROM device and none of the RKDev tool versions (tried with v2.43 / v2.58 / v2.69) are recognising it as a loader device.

Request your recommendation again to find a way out of this situation and get the SoM detected as a Loader Device.

Thanks in advance.
 
M

marchnz

Senior Member
Nov 26, 2012
5,527
1,199
NZ
Akuma666 said:
Answering your question - The device is in maskrom mode, did you force that, or did that happen by itself? - (The device was automatically detected as a MaskROM device)

You were spot on with your recommendations. I was able to connect the SoM as a Loader Device with AndroidTool_Release_v2.43 (I was using v2.69 earlier). I then tried flashing sdupdate-A8-Kumarai.img but it failed at "Murex Reset Device" step.

Next I tried flashing it with Android 6.0 as per your second recommendation and the process succeeded 100%.

With Android 6.0, the SoM was recognised as a Loader Device. I then tried flashing it again with sdupdate-A8-Kumarai.img, hoping to get to Android 8.0 and it failed.

The SoM is now again stuck as a MaskROM device and none of the RKDev tool versions (tried with v2.43 / v2.58 / v2.69) are recognising it as a loader device.

Request your recommendation again to find a way out of this situation and get the SoM detected as a Loader Device.

Thanks in advance.
Click to expand...
Click to collapse

Try partition by partition method after wipe via Android 6.
 
Akuma666

Akuma666

Member
Nov 28, 2020
9
2
marchnz said:
Try partition by partition method after wipe via Android 6.
Click to expand...
Click to collapse

Wipe did not happen using Android-6 or Android-8

Was able to load images using the partition by partition method. However, was not sure what to load under the "Parameter" and "Base Parameter" partitions, because there are no specific images for these in px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew folder. Attaching a screen shot for clarity.

Load_1.png

The first partition "Loader" was not allowing any image load and kept throwing "Boot Fail" error.

Tried using Windows-10 (instead of Windows-7), but the result was the same.

Not sure of the next steps. The SoM still says "Firmware not found" after being detected, when trying to "Erase Flash".

Standing by for further instructions.

Thank you.
 
M

marchnz

Senior Member
Nov 26, 2012
5,527
1,199
NZ
Akuma666 said:
Wipe did not happen using Android-6 or Android-8

Was able to load images using the partition by partition method. However, was not sure what to load under the "Parameter" and "Base Parameter" partitions, because there are no specific images for these in px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew folder. Attaching a screen shot for clarity.

View attachment 5149327

The first partition "Loader" was not allowing any image load and kept throwing "Boot Fail" error.

Tried using Windows-10 (instead of Windows-7), but the result was the same.

Not sure of the next steps. The SoM still says "Firmware not found" after being detected, when trying to "Erase Flash".

Standing by for further instructions.

Thank you.
Click to expand...
Click to collapse

Suggest a read through this forum, specifically: [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.


Just re. "Standing by for further instructions." Let me know what you've read and tried, would suggest reading through these forums. If unable to recover, you're welcome to send the SOM to me in NZ.

Cheers.
 
M

marchnz

Senior Member
Nov 26, 2012
5,527
1,199
NZ
Akuma666 said:
Wipe did not happen using Android-6 or Android-8

Was able to load images using the partition by partition method. However, was not sure what to load under the "Parameter" and "Base Parameter" partitions, because there are no specific images for these in px5_OREO_Full_OTG_13032018-UseToRecoverOrCreateNew folder. Attaching a screen shot for clarity.

View attachment 5149327

The first partition "Loader" was not allowing any image load and kept throwing "Boot Fail" error.

Tried using Windows-10 (instead of Windows-7), but the result was the same.

Not sure of the next steps. The SoM still says "Firmware not found" after being detected, when trying to "Erase Flash".

Standing by for further instructions.

Thank you.
Click to expand...
Click to collapse

Suggest a read through this forum, specifically: [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.


Just re. "Standing by for further instructions." Let me know what you've read and tried, would suggest reading through these forums. If unable to recover, you're welcome to send the SOM to me in NZ.

Cheers.
 
Akuma666

Akuma666

Member
Nov 28, 2020
9
2
marchnz said:
Suggest a read through this forum, specifically: [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.


Just re. "Standing by for further instructions." Let me know what you've read and tried, would suggest reading through these forums. If unable to recover, you're welcome to send the SOM to me in NZ.

Cheers.
Click to expand...
Click to collapse

Thank you MarchNZ for sharing the links. I had gone through this thread before I started the exercise but the links were not accessible to me after the XDA Forum upgrade. I was able to access them again today through your shared links.

I feel the link you shared for the other thread is more relevant to what I am trying to do with your help. Hence I will post my queries on the other thread henceforth, if that is not a problem.

Thank you.
 
  • Like
Reactions: kkjb and marchnz
Akuma666

Akuma666

Member
Nov 28, 2020
9
2
Akuma666 said:
Thank you MarchNZ for sharing the links. I had gone through this thread before I started the exercise but the links were not accessible to me after the XDA Forum upgrade. I was able to access them again today through your shared links.

I feel the link you shared for the other thread is more relevant to what I am trying to do with your help. Hence I will post my queries on the other thread henceforth, if that is not a problem.

Thank you.
Click to expand...
Click to collapse


Hi MarchNZ, After the last stint, the SoM board was not being detected by Windows-7. Had to remove the heat sink and short the points on the PCB for the board to get detected.

Once the SoM got detected, followed your and blue1111's instructions to load image partition-by-partition and succeeded. Image attached for clarity. Thanks to you and blue1111.

Load_2.PNG

However, even after multiple tries, I was unable to "EraseFlash" before loading partition-by-partition. Always kept receiving the error "EraseFlash Failed". I even tried with multiple versions of the tool but did not succeed.

I then inserted the SoM back on the core board and plugged the system back, to get to recovery, but I still see a blank screen and the same behaviour as before I started the whole exercise - I am unable to get to Recovery.

Request you to let me know what else I can try.

Thank You
 
Akuma666

Akuma666

Member
Nov 28, 2020
9
2
marchnz said:
Suggest a read through this forum, specifically: [PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable | XDA Developers Forums (xda-developers.com)

A generic guide to the RockChip Android tool, flashing partitions or image files is here as previously posted.


Just re. "Standing by for further instructions." Let me know what you've read and tried, would suggest reading through these forums. If unable to recover, you're welcome to send the SOM to me in NZ.

Cheers.
Click to expand...
Click to collapse


Hi MarchNZ, After the last stint, the SoM board was not being detected by Windows-7. Had to remove the heat sink and short the points on the PCB for the board to get detected.

Once the SoM got detected, followed your and blue1111's instructions to load image partition-by-partition and succeeded. Image attached for clarity. Thanks to you and blue1111.

Load_2.PNG

However, even after multiple tries, I was unable to "EraseFlash" before loading partition-by-partition. Always kept receiving the error "EraseFlash Failed". I even tried with multiple versions of the tool but did not succeed.

I then inserted the SoM back on the core board and plugged the system back, to get to recovery, but I still see a blank screen and the same behaviour as before I started the whole exercise - I am unable to get to Recovery.

Request you to let me know what else I can try.

Sorry, I ended up replying to my own message previously.

Thank You
 
M

marchnz

Senior Member
Nov 26, 2012
5,527
1,199
NZ
Akuma666 said:
Hi MarchNZ, After the last stint, the SoM board was not being detected by Windows-7. Had to remove the heat sink and short the points on the PCB for the board to get detected.

Once the SoM got detected, followed your and blue1111's instructions to load image partition-by-partition and succeeded. Image attached for clarity. Thanks to you and blue1111.

Load_2.PNG

However, even after multiple tries, I was unable to "EraseFlash" before loading partition-by-partition. Always kept receiving the error "EraseFlash Failed". I even tried with multiple versions of the tool but did not succeed.

I then inserted the SoM back on the core board and plugged the system back, to get to recovery, but I still see a blank screen and the same behaviour as before I started the whole exercise - I am unable to get to Recovery.

Request you to let me know what else I can try.

Sorry, I ended up replying to my own message previously.

Thank You
Click to expand...
Click to collapse

Did you want to send the SOM to me
 
  • Like
Reactions: ohap
B

bebokoo

Member
Mar 31, 2015
17
2
Hi guys,

I got a Seicane HU that seems to be stuck in a bootloop.
I have a SOM here that I can not flash, no matter what I try.
Been trying a lot of different things in the past few weeks (including suggestions in this thread), but I can't get it to work.
It is a SOM PX5 4/64gb with Android 10 hal9k mod5, and it crashed.

I have attached some pictures, any help will be greatly appreciated.

Greetings from the Netherlands.

Ben
 

Attachments

  • IMG_20211028_152527.jpg
    IMG_20211028_152527.jpg
    6 MB · Views: 15
  • IMG_20211028_152544.jpg
    IMG_20211028_152544.jpg
    4.8 MB · Views: 15
  • IMG_20211108_111019.jpg
    IMG_20211108_111019.jpg
    3.1 MB · Views: 15
B

bebokoo

Member
Mar 31, 2015
17
2
this is what happens
 

Attachments

  • IMG_20220107_150857.jpg
    IMG_20220107_150857.jpg
    6.1 MB · Views: 27
  • IMG_20220107_185453.jpg
    IMG_20220107_185453.jpg
    2.9 MB · Views: 27
B

bebokoo

Member
Mar 31, 2015
17
2
I did it with android tool and everything seems to go well until I start the HU again Erase appears???
 
M

marchnz

Senior Member
Nov 26, 2012
5,527
1,199
NZ
bebokoo said:
can someone help me i don't know how to proceed
Click to expand...
Click to collapse

Please read this post and the thread.
Per our PM, you may send it to me, however I believe you are very close to a working unit.

forum.xda-developers.com

[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable

"Factory" Recovery for MTCx PX3, PX5 and PX6 SOM. Finally - OTG for all without modifying your head-unit. With only basic electronic/soldering skills, get OTG and fearlessly flash or recover a 'bricked' MTCD/E (HCT printed on SOM) Rockchip PX3...
forum.xda-developers.com forum.xda-developers.com
 
B

bebokoo

Member
Mar 31, 2015
17
2
this is what happens.
Or is there something wrong with the motherboard?
how can i go on now??
 

Attachments

  • IMG_20220110_101053.jpg
    IMG_20220110_101053.jpg
    4.7 MB · Views: 24
  • IMG_20220110_101129.jpg
    IMG_20220110_101129.jpg
    4.4 MB · Views: 24
  • IMG_20220110_101434_BURST001_COVER.jpg
    IMG_20220110_101434_BURST001_COVER.jpg
    969.8 KB · Views: 24
You must log in or register to reply here.

Similar threads

H
New Dasaita (hotaudio) Android 6.0.1 ready , PX5 Platform Octa-Core 32GB 2G RAM :D
Replies
508
Views
137K
I
ikerg
Pianoman144
PX5 MTCD_LM newest Stock Firmware
Replies
110
Views
57K
E
EXpierencE
D
PX5 USB Audio problems & finds discussion thread
Replies
238
Views
52K
B
Bob_Sanders
stanjkof
Vehicle.apk reworking px3 px5
Replies
83
Views
43K
X
x0101222
I
[PX5] Google maps hangs nearly unusable different roms
Replies
128
Views
34K
S
SoberXDA

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 11
    M
    marchnz
    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.
    View
    4
    S
    scorillo_ro
    PX5 SOM rev4.0 MaskROM

    Tracking the MaskROM pads on the rev8.0 SOM I found that exposing the tracks between the PX5 processor and the eMMC is not necessarily needed for the rev4.0 SOM. Take a look at the attached pictures.
    View
    3
    S
    scorillo_ro
    PX5 SOM rev8.0 MaskROM

    I have the confirmation that those round pads near the tracks between PX5 processor and the eMMC are for entering MaskROM!
    View
    3
    S
    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.
    View
    2
    M
    marchnz
    Malle355 said:
    Ok thanks. I first try it. If its not working I must wait if you guys can help with the maskrom mode right? Thank you guys for youre help :eek:


    Edit: Just tried the OTG Method but also not working for me. Windows not reconizing my device. @marchnz Can you please show us in this Picture what to do to get it working on our px5 device?
    Click to expand...
    Click to collapse

    Your connections look OK, but missing OTG_DET pin 28, which has +1.8v on it when connected to USB. (Detects when OTG USB is connected.)

    As I have a jig made from a working motherboard, I am awaiting a header to mock up like you guys. I'll try making one out of wires like you have over the weekend and let you know.

    I'm very keen to see more people get OTG so there's more people capable of helping out others that are that are stuck - others that are unable to make a jig might then have someone located closer and save on freight or having to replace their SOM :)
    View

New posts