[HELP] xgody 3gb 32g sS912
-
- Verified Member
- Posts: 19
- Joined: Wed Aug 07, 2019 2:06 pm
not sure, I mention khadas vim 2, but was armbian booting, armbian did 4 or more reboots and end up to booting, I installed the armbian and then I found that the /proc/model was displaying khadas vim 2.
I belive the firmaware that I had to install armbian had a multi dtb, or was somehow looping to get one working configuration. this was the one selected
I belive the firmaware that I had to install armbian had a multi dtb, or was somehow looping to get one working configuration. this was the one selected
-
- Verified Member
- Posts: 19
- Joined: Wed Aug 07, 2019 2:06 pm
-
- Administrator & Developer
- Posts: 1551
- Joined: Tue Oct 02, 2018 6:19 pm
- Has thanked: 211 times
- Been thanked: 334 times
this is a single dtb, not a multi dtb, it has nothing to do with your problem. A gxm_q201_v1 uboot does not run on a gxm_q200 device, I personally tested that and i can't help you without logs
-
- Verified Member
- Posts: 19
- Joined: Wed Aug 07, 2019 2:06 pm
I have usb to serial https://www.aliexpress.com/item/3304089 ... 4c4d2RHNpc
But I'm but lost due lack of information on the board to get this pluged, can anyone give a look to the pictures shared on this post to point where should I connect this?
But I'm but lost due lack of information on the board to get this pluged, can anyone give a look to the pictures shared on this post to point where should I connect this?
- em3ka
- Moderator
- Posts: 1835
- Joined: Sun Jul 15, 2018 11:43 am
- Has thanked: 108 times
- Been thanked: 374 times
UART pins are between reset switch and USB port on the edge of the PCB.
tutorial:
viewtopic.php?f=16&t=453
tutorial:
viewtopic.php?f=16&t=453
-
- Verified Member
- Posts: 19
- Joined: Wed Aug 07, 2019 2:06 pm
this box is the same as the r tv s10, ddr4.
I was checking the burning log:
[00:13:30 567][HUB3-4][Inf]--Write initial succeed
[00:13:30 567][HUB3-4][Inf]--Upload encrypt at 0xc8100228
[00:13:30 567][HUB3-4][Inf]--ulValue = 0xbdfc31bc
[00:13:30 567][HUB3-4][Inf]--File change to DDR_ENC.USB
[00:13:30 567][HUB3-4][Inf]--Read encrypt value succeed
[00:13:30 567][HUB3-4][Inf]--Download DDR_ENC.USB,size: 0!
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][HUB3-4][Err]--Read item data error, code -1
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 572][HUB3-4][Err]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
[00:13:30 572][HUB3-4][Inf]--Close device handle 0x000009c0
Unpacking the original and the atv firmware, I see a difference on the presence of DDR.USB and DDR_ENC.USB on the original firmware, the log seems looking form this DDR_ENC.USB and then complain about reading error.
I'm wondering if the device is not expecting to have a DDR_END.USB on the firmware.
I was checking the burning log:
[00:13:30 567][HUB3-4][Inf]--Write initial succeed
[00:13:30 567][HUB3-4][Inf]--Upload encrypt at 0xc8100228
[00:13:30 567][HUB3-4][Inf]--ulValue = 0xbdfc31bc
[00:13:30 567][HUB3-4][Inf]--File change to DDR_ENC.USB
[00:13:30 567][HUB3-4][Inf]--Read encrypt value succeed
[00:13:30 567][HUB3-4][Inf]--Download DDR_ENC.USB,size: 0!
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][HUB3-4][Err]--Read item data error, code -1
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 572][HUB3-4][Err]--[0x10103005]Romcode/Initialize DDR/Download buffer/Read item data failed
[00:13:30 572][HUB3-4][Inf]--Close device handle 0x000009c0
Unpacking the original and the atv firmware, I see a difference on the presence of DDR.USB and DDR_ENC.USB on the original firmware, the log seems looking form this DDR_ENC.USB and then complain about reading error.
I'm wondering if the device is not expecting to have a DDR_END.USB on the firmware.
-
- Administrator & Developer
- Posts: 1551
- Joined: Tue Oct 02, 2018 6:19 pm
- Has thanked: 211 times
- Been thanked: 334 times
nmocruz wrote: ↑Mon May 04, 2020 11:38 pm ulValue = 0xbdfc31bc
[00:13:30 567][HUB3-4][Inf]--File change to DDR_ENC.USB
[00:13:30 567][HUB3-4][Inf]--Read encrypt value succeed
[00:13:30 567][HUB3-4][Inf]--Download DDR_ENC.USB,size: 0!
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][Global][Err]--DDR_ENC.USB
[00:13:30 567][HUB3-4][Err]--Read item data error, code -1
BL1 (processor ROM) is programmed for a secure boot, you can only use original image from the manufacturer.ulValue = 0xbdfc31bc
-
- Verified Member
- Posts: 19
- Joined: Wed Aug 07, 2019 2:06 pm
Ok, makes sense, but one guy on freaktab was able to repack the original firmware with other system+logo partitions. Was the only way that I got this device rooted, is working fine with the custom from shared by that guy.
I was able to unpack with the linux toolkit, and repack with other system partition, in this way it writes the firmware, but may due compatibility issues it doesn't boot. I'm learning, so don't know yet what is failing, the kernel or some related with manifest.xml present in the original firmware.
I was able to unpack with the linux toolkit, and repack with other system partition, in this way it writes the firmware, but may due compatibility issues it doesn't boot. I'm learning, so don't know yet what is failing, the kernel or some related with manifest.xml present in the original firmware.