PX5 stuck in bootloop

[marchnz]

Many questions comes to my mind:
By toggling do you mean I should first apply +3.3v on the CTL_WAKEUP then apply GND -0v or the other way around?
Should I do the same on CTL_RECOVERY?
When powering the SOM for the first time, should CTL_WAKEUP and/or CTL_RECOVERY have +3.3v applied or should them be applied later?

I think I did try some of the combinations but the toggling. Will try again this evening when I’ll return from work.

Hi,
Confirming ctl_wakeup (logic 0) should be pulled to ground and remain pulled low.
Ctl_recovery pulled 3.3v via resistor (logic 1) and stay 3.3v.

I measured all SOM pins today and can't see any reason why the suggested combination doesn't seem to work for you.
Ensure that the SOM is also grounded via 3 mounts.

Also load pX5 USB 'rockchip USB' driver. Even if USB DM and DP are transposed, you should see something happen in the windows device list (code 21 from memory.)

 

[scorillo_ro]

Hi,
Confirming ctl_wakeup (logic 0) should be pulled to ground and remain pulled low.
Ctl_recovery pulled 3.3v via resistor (logic 1) and stay 3.3v.

I measured all SOM pins today and can't see any reason why the suggested combination doesn't seem to work for you.
Ensure that the SOM is also grounded via 3 mounts.

Also load pX5 USB 'rockchip USB' driver. Even if USB DM and DP are transposed, you should see something happen in the windows device list (code 21 from memory.)

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

Did you actually had success using just the SOM or did you use it only on the modified MCU board?

 

[marchnz]

Did you actually had success using just the SOM or did you use it only on the modified MCU board?

Hi,
Only from modded board. There's no external clocks etc, so should work. I'm going to buy a header and test as very keen to see others get OTG.

 

[ikerg]

Hi,
Only from modded board. There's no external clocks etc, so should work. I'm going to buy a header and test as very keen to see others get OTG.

I would appreciate as I couldnt got to the coreboard be recognized be menans of direct connection to PC USB port and 5V/3.3V power sources

 

[scorillo_ro]

I would appreciate as I couldnt got to the coreboard be recognized be menans of direct connection to PC USB port and 5V/3.3V power sources

Last evening I also tried feeding CTL_RECOVERY with +3.3 volts from middle resistors connected to +5 volts / GND and CTL_WAKEUP to GND, still no luck.
The SOM's heat sink remains cold. If I connect it back to the MCU board it will get warm...

At this moment I'm not sure if the SOM is alive anymore. I start wondering if maybe by mistake I connected something wrong or did some short on it and fried it.
On the other side I still have +5 volts on the SOM test pads.

@marchnz
At my last two attempts to wake the SOM I also wanted to see if something comes up on the serial pins, but I had no luck there either (so again, maybe the board does not wake up or it is fried).
For this I used a CH340G USB to Serial adapter and connected its GND, TX and RX to SOM (pin 46 - ARM_RX and pin 48 - ARM_TX)
Maybe you want to try this also on your working mod to see if there is some feedback there.

And thank you again for your hard work on this!

 

[Cid6.7]

FWIW I tried the OTG mod by lifting the legs & successfully flashed/unbricked our Sophia unit. Then for sharts and giggles I seated and soldered the legs back with same results. Now I can just hook my male/male usb up to the unit and works every time... Not sure why tho lol

 

[marchnz]

FWIW I tried the OTG mod by lifting the legs & successfully flashed/unbricked our Sophia unit. Then for sharts and giggles I seated and soldered the legs back with same results. Now I can just hook my male/male usb up to the unit and works every time... Not sure why tho lol

Congrats. Can you post some detailed pics of your mainboard, guessing it is a GS, but would like to confirm.

 

[scorillo_ro]

FWIW I tried the OTG mod by lifting the legs & successfully flashed/unbricked our Sophia unit. Then for sharts and giggles I seated and soldered the legs back with same results. Now I can just hook my male/male usb up to the unit and works every time... Not sure why tho lol

For me Windows is detecting an "unknown device" connected for a very short time, too short to identify it. I have the rockchip drivers installed (version 4.4).
What I did was to solder wires CTL_RECOVERY to +3.3v and ARM-DM and ARM-DP to USB male connector on the SOM, with the SOM connected to the MCU board.
I've also tried with the legs lifted but same result, fast connect-disconnect in Windows... I have a Klyde unit.
--
LE. Also tried to inverse the order of USB wires, same result.

 

[cookie1338]

Unfortunately I cannot do this myself.
Please, would anyone in Europe be willing to receive my HU, recover it from bootloop and send it back? I will off course pay the return cost with paypal.

 

[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.

 

[scorillo_ro]

Some more details

Here are the proofs (attached pictures)

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

2) To connect to the Android via ADB shell, you must start the "Factory settings" using the "adbon" password instead of "126". During this mode your other USB devices (like USB memory stick, or 4G dongle) will be disconnected.
I think you also have to enable the "Developer mode" and enable the "USB debugging" first. I had those already on because I made the tests from Malaysk's rom.
To exit this mode you must start again "Factory settings" using the "adboff" password this time (your USB devices will be reconnected).

 

[ali20042004]

Here are the proofs (attached pictures)

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

2) To connect to the Android via ADB shell, you must start the "Factory settings" using the "adbon" password instead of "126". During this mode your other USB devices (like USB memory stick, or 4G dongle) will be disconnected.
I think you also have to enable the "Developer mode" and enable the "USB debugging" first. I had those already on because I made the tests from Malaysk's rom.
To exit this mode you must start again "Factory settings" using the "adboff" password this time (your USB devices will be reconnected).

Could you please attach the softwer and driver in this page

 

[typos1]

Here are the proofs (attached pictures)

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

2) To connect to the Android via ADB shell, you must start the "Factory settings" using the "adbon" password instead of "126". During this mode your other USB devices (like USB memory stick, or 4G dongle) will be disconnected.
I think you also have to enable the "Developer mode" and enable the "USB debugging" first. I had those already on because I made the tests from Malaysk's rom.
To exit this mode you must start again "Factory settings" using the "adboff" password this time (your USB devices will be reconnected).

Hmm, I wonder if other units can also do this.

 

[marchnz]

You have OTG! Do you have OTG Loader Mode? If so, you have all you need to wipe and reload RK SOMs. Did you do any mods? Note that your machine is a GS and that you are connected via USB1 which is the only USB supported for OTG and on GS hardware.

Use the tool [Androidtool.exe], boot as you described using recovery button - would you share a screenshot - it should look like my attachment.

Here are the proofs (attached pictures)

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

2) To connect to the Android via ADB shell, you must start the "Factory settings" using the "adbon" password instead of "126". During this mode your other USB devices (like USB memory stick, or 4G dongle) will be disconnected.
I think you also have to enable the "Developer mode" and enable the "USB debugging" first. I had those already on because I made the tests from Malaysk's rom.
To exit this mode you must start again "Factory settings" using the "adboff" password this time (your USB devices will be reconnected).

 

[marchnz]

Could you please attach the softwer and driver in this page

Download here

Has rkdevtool (android tool) and very latest version 4.5 driver.

 

[scorillo_ro]

You have OTG! Do you have OTG Loader Mode? If so, you have all you need to wipe and reload RK SOMs. Did you do any mods? Note that your machine is a GS and that you are connected via USB1 which is the only USB supported for OTG and on GS hardware.

Use the tool [Androidtool.exe], boot as you described using recovery button - would you share a screenshot - it should look like my attachment.


[/HIDE]

I will try Androidtool next days. I have a KLD (Klyde) unit, is not a GS and that's for sure.

I don't know if that matters or if it can be considered a mod, but at my previous attempts to recover my bricked 2GB SOM I lifted pins 27 and 28 of the USB HUB chip. But they are soldered back now and no other modifications were made. Actually this is how I found the connector... I traced the pins 27 and 28 using a multimeter by measuring all the unused pins on the back of the unit.

My new 4GB SOM has arrived so the OTG tests I made were done using this SOM. I still can't access my bricked 2GB SOM.

I am still using my old MTCB unit in my car because I have a new problem now on which I am focused: I don't have WiFi anymore
My KLD MCU has a Realtek 8188 Adapter, but android is expecting a 8723 one ...

[    2.370745]  [0:      swapper/0:    1] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    2.371090]  [0:      swapper/0:    1] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    2.371178]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = rtl8723bu
[    2.371193]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    2.371208]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: disable wifi io reference voltage control.
[    2.371222]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    2.371284]  [0:      swapper/0:    1] of_get_named_gpio_flags exited with status 29
[    2.371297]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,poweren_gpio = 29, flags = 0.
[    2.371311]  [0:      swapper/0:    1] of_get_named_gpio_flags: can't parse gpios property
[    2.371323]  [0:      swapper/0:    1] of_get_named_gpio_flags: can't parse gpios property
[    2.371335]  [0:      swapper/0:    1] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    2.371351]  [0:      swapper/0:    1] _gpio_request: gpio-29 (wlan_default_wlan_poweren) status -16
[    2.371362]  [0:      swapper/0:    1] [WLAN_RFKILL]: Failed to get wlan_default_wlan_poweren gpio.
[    2.371386]  [0:      swapper/0:    1] wlan-platdata: probe of wireless-wlan.25 failed with error -1

...

[    2.747627]  [0:          khubd:   64] --mtc ann 1-1 0bda
[    2.747659]  [0:          khubd:   64] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176
[    2.747676]  [0:          khubd:   64] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.747684]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747697]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747711]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747733]  [0:          khubd:   64] usb 1-1: Product: 802.11n WLAN Adapter
[    2.747740]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747752]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747764]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747806]  [0:          khubd:   64] usb 1-1: Manufacturer: Realtek
[    2.747840]  [0:          khubd:   64] usb 1-1: SerialNumber: 00e04c000001

I don't know how to resolve this issue, so I ordered this just in case I need to physically replace it...
https://www.aliexpress.com/item/F23...module-tablet-wifi-bt-module/32657946183.html

 

[scorillo_ro]

Use the tool [Androidtool.exe], boot as you described using recovery button - would you share a screenshot - it should look like my attachment.

This is how it looks

 

[marchnz]

This is how it looks

Congratulations, you have OTG and the ability to directly flash your SOM. You can now fearlessly flash ROMs, even the wrong ones without fear of bricking

 

[marchnz]

I will try Androidtool next days. I have a KLD (Klyde) unit, is not a GS and that's for sure.

I

don't know if that matters or if it can be considered a mod, but at my previous attempts to recover my bricked 2GB SOM I lifted pins 27 and 28 of the USB HUB chip. But they are soldered back now and no other modifications were made. Actually this is how I found the connector... I traced the pins 27 and 28 using a multimeter by measuring all the unused pins on the back of the unit.

My new 4GB SOM has arrived so the OTG tests I made were done using this SOM. I still can't access my bricked 2GB SOM.

I am still using my old MTCB unit in my car because I have a new problem now on which I am focused: I don't have WiFi anymore
My KLD MCU has a Realtek 8188 Adapter, but android is expecting a 8723 one ...

[    2.370745]  [0:      swapper/0:    1] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    2.371090]  [0:      swapper/0:    1] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    2.371178]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = rtl8723bu
[    2.371193]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    2.371208]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: disable wifi io reference voltage control.
[    2.371222]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    2.371284]  [0:      swapper/0:    1] of_get_named_gpio_flags exited with status 29
[    2.371297]  [0:      swapper/0:    1] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,poweren_gpio = 29, flags = 0.
[    2.371311]  [0:      swapper/0:    1] of_get_named_gpio_flags: can't parse gpios property
[    2.371323]  [0:      swapper/0:    1] of_get_named_gpio_flags: can't parse gpios property
[    2.371335]  [0:      swapper/0:    1] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    2.371351]  [0:      swapper/0:    1] _gpio_request: gpio-29 (wlan_default_wlan_poweren) status -16
[    2.371362]  [0:      swapper/0:    1] [WLAN_RFKILL]: Failed to get wlan_default_wlan_poweren gpio.
[    2.371386]  [0:      swapper/0:    1] wlan-platdata: probe of wireless-wlan.25 failed with error -1

...

[    2.747627]  [0:          khubd:   64] --mtc ann 1-1 0bda
[    2.747659]  [0:          khubd:   64] usb 1-1: New USB device found, idVendor=0bda, idProduct=8176
[    2.747676]  [0:          khubd:   64] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.747684]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747697]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747711]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747733]  [0:          khubd:   64] usb 1-1: Product: 802.11n WLAN Adapter
[    2.747740]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747752]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747764]  [1:         mkswap:  198] Buffer I/O error on device zram0, logical block 130227
[    2.747806]  [0:          khubd:   64] usb 1-1: Manufacturer: Realtek
[    2.747840]  [0:          khubd:   64] usb 1-1: SerialNumber: 00e04c000001

I don't know how to resolve this issue, so I ordered this just in case I need to physically replace it...
https://www.aliexpress.com/item/F23...module-tablet-wifi-bt-module/32657946183.html

Or consider ordering a comfast CF-WU725B USB- plug and play. Set factory settings Bluetooth to [MD725] and you're good to go.

 

[scorillo_ro]

Or consider ordering a comfast CF-WU725B USB- plug and play. Set factory settings Bluetooth to [MD725] and you're good to go.

Great idea!
The RTL8723BU module was already shipped, so I'll wait for it now and consider your suggestion as a backup solution.
Thank you for all your help!

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

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

Congratulations, you have OTG and the ability to directly flash your SOM. You can now fearlessly flash ROMs, even the wrong ones without fear of bricking

Why do the information in my screenshot looks different from yours?
I mean I have some loaders and boot stuff and you see the recovery, system, etc. ?

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

Set factory settings Bluetooth to [MD725] and you're good to go.

But my WQ_BC5 is working just fine now. Do you think it will be ignored and the MD725 one will be preferred?