Jump to content

H1H1

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @jockThe multitool-bad booted up fine, but it had the issue you mentioned, stops responding after a few seconds. The latest multitool isn't booting at all. From what I've been reading, there's no solution to this so far. Tthank you very much for everything again.
  2. @jock I finally managed to extract the firmware. Here's the trust partition https://drive.google.com/file/d/1E7mxBVE1lUshqdcjqTMfxKQMW2iLUvye/view?usp=drive_link. And here's the rest of the backup https://drive.google.com/drive/folders/165r4bV3jFj8Ptx4yY2sXmbmOUOBIMWaW?usp=drive_link. I've been trying to install Armbian via USB cable, but no luck so far, always getting Test device fail. Thanks
  3. It didn't work either, it gave the same error. I'll give that a try, and when I can extract the firmware, I'll share it. Thanks!
  4. @jockIt still doesn't boot with that multitool, but it's giving a different error this time. DDR Version V1.09 20190628 In ID:0xFFF 300MHz LPDDR3 Bus Width=32 Col=10 Bank=8 Row=14 CS=2 Die Bus-Width=32 Size=1024MB mach:14 OUT Boot1 Release Time: May 4 2018 15:21:31, version: 2.49 ChipType = 0xc, 341 No.1 FLASH ID:20 ff ff ff ff ff mmc2:cmd19,256 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 mmc0:cmd5,32 SdmmcInit=0 0 BootCapSize=0 UserCapSize=3780MB FwPartOffset=2000 , 0 StorageInit ok = 156398 SecureMode = 0 GPT signature is wrong LOADER Check OK! 0x61000000, 212161 TOS Check OK! 0x68400000, 244752 Enter Trust OS INF TEE-CORE:init_primary_helper:319: Initializing (1.0.1-65-gf1567d3-dev #22 Fri Mar 24 06:16:54 UTC 2017 arm) INF TEE-CORE:init_primary_helper:320: Release version: 1.9 ERR TEE-CORE:call_initcalls:53: Initial call 0x68400180 failed INF TEE-CORE:init_teecore:79: teecore inits done Thank you so much for the time you dedicate to this.
  5. @jockThere's no output at 115200bps. I attach the android boot log log boot android.txt
  6. @jock Yes, thanks, that was the port. It seems like my UART adapter isn't working correctly at 1.5mbps, so I used a logic analyzer and was able to see the console. DDR Version V1.09 20190628 In ID:0xFFF 300MHz LPDDR3 Bus Width=32 Col=10 Bank=8 Row=14 CS=2 Die Bus-Width=32 Size=1024MB mach:14 OUT Boot1 Release Time: May 4 2018 15:21:31, version: 2.49 ChipType = 0xc, 341 mmc2:cmd19,256 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 mmc0:cmd5,32 SdmmcInit=0 0 BootCapSize=0 UserCapSize=3780MB FwPartOffset=2000 , 0 StorageInit ok = 162069 SecureMode = 0 GPT signature is wrong LOADER Check OK! 0x61000000, 217834 TOS Check OK! 0x68400000, 285226 Enter Trust OS INF [0x0] TEE-CORE:init_primary_helper:377: Initializing (1.1.0-333-gc9d95d1 #2 2018\xE5\xB9\xB4 08\xE6\x9C\x88 17\xE6\x97\xA5 \xE6\x98\x9F\xE6\x9C\x9F\xE4\xBA\x94 03:32:22 UTC arm) INF [0x0] TEE-CORE:init_primary_helper:378: Release version: 2.0 INF [0x0] TEE-CORE:init_primary_helper:379: Next entry point address: 0x61000000 [9hjjNa:N\xDF\xC7\xDF\xC1\xD0\xC7\xDF\xC5l\xDF\xC2\xDF\xC3@NfN\xDF\xC0\xDF
  7. Hi! I've got this MXQPRO_V73 board here with an RK3229, an esp8089, 1GB of RAM, and 8GB of storage. When I insert the SD card with the Multitool, it doesn't boot. All I get is the red light, no blue light, and no HDMI output or IP connection. I've been trying to find the UART port, but no luck so far.Any idea where it might be? Thank you very much
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines