Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

(SOLVED)Need Help reviving my box.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    (SOLVED)Need Help reviving my box.

    Hello!

    I`ve an issue with my android tv box.

    WARINING : It will be a long detailed post.


    First of all, I got my box like a month ago from aliexpress. Its an Magicsee iron s905x 2/8 box. I plugged in the box everything was working but after close examination the box had a "modified" firmware. Its was contacting some random site and I didn`t like that at all. So I start searching for custom firmware. First one I tried was s905x_2G_atvXperience_v2FF.img. I copied the image on a micro sd and went in recovery with the thoothpick method.

    The image flashed but after like 10 minutes the display disapeared and the led on the board turned red. I did wait like 2 more hours in case something was going on in the background but nothing did happed. So i reseted the box and the 2 red light came back immediately and no display at all through hdmi. I did tryed to flash back the image with the thoothpick method but the reset button doesnt seems to do anything.

    After a bit of research I decided to hook up through UART port. I then saw this was happening :

    BL2 Built : 20:32:17, Sep 8 2017.
    gxl g6296b83 - xiaobo.gu@droid12

    set vcck to 1120 mv
    set vddee to 1000 mv
    Board ID = 3
    CPU clk: 1200MHz
    DQS-corr enabled
    DDR scramble enabled
    STICKY_REG0: 0x00000000
    STICKY_REG1: 0x00000000
    STICKY_REG9: 0x00000000
    DDR3 chl: Rank0+1 @ 792MHz - PASS
    Rank0: 1024MB(auto)-2T-11
    Rank1: 1024MB(auto)-2T-11
    DataBus test pass!
    AddrBus test pass!
    -s
    Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
    New fip structure!
    Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
    aml log : SIG CHK : 231 for address 0x01100000
    reset...
    this just keeps looping and looping. I even checked if the reset button had any impact on this and no. Nothing change. Im not an expert but I think the system doesnt boot far enough to consider the reset. Did some more researched to finally find the "short pin" method. I did that and some kind of progress :

    U-Boot 2015.01 (Jul 13 2018 - 13:52:51)

    DRAM: 2 GiB
    Relocation Offset is: 76eb3000
    register usb cfg[0][1] = 0000000077f5a928
    [CANVAS]canvas init
    vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
    vpu: clk_level = 7
    vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
    vpu: vpu_clk_gate_init_off
    vpp: vpp_init
    boot_device_flag : 1
    Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
    init bus_cycle=6, bus_timing=7, system=5.0ns
    reset failed
    get_chip_type and ret:fffffffe
    get_chip_type and ret:fffffffe
    chip detect failed and ret:fffffffe
    nandphy_init failed and ret=0xfffffff1
    MMC: aml_priv->desc_buf = 0x0000000073eb36b0
    aml_priv->desc_buf = 0x0000000073eb59d0
    SDIO Port B: 0, SDIO Port C: 1
    emmc/sd response timeout, cmd8, status=0x1ff2800
    emmc/sd response timeout, cmd55, status=0x1ff2800
    init_part() 293: PART_TYPE_AML
    [mmc_init] mmc init success
    dtb magic 5f4c4d41
    Amlogic multi-dtb tool
    Multi dtb detected
    Multi dtb tool version: v2 .
    Support 2 dtbs.
    aml_dt soc: gxl platform: p212 variant: 2g
    dtb 0 soc: gxl plat: p212 vari: 1g
    dtb 1 soc: gxl plat: p212 vari: 2g
    Find match dtb: 1
    start dts,buffer=0000000073eb8200,dt_addr=0000000073ec32 00
    Amlogic multi-dtb tool
    Multi dtb detected
    Multi dtb tool version: v2 .
    Support 2 dtbs.
    aml_dt soc: gxl platform: p212 variant: 2g
    dtb 0 soc: gxl plat: p212 vari: 1g
    dtb 1 soc: gxl plat: p212 vari: 2g
    Find match dtb: 1
    parts: 10
    00: logo 0000000002000000 1
    01: recovery 0000000002000000 1
    02: rsv 0000000000800000 1
    03: tee 0000000000800000 1
    04: crypt 0000000002000000 1
    05: misc 0000000002000000 1
    06: boot 0000000002000000 1
    07: system 0000000080000000 1
    08: cache 0000000020000000 2
    09: data ffffffffffffffff 4
    init_part() 293: PART_TYPE_AML
    eMMC/TSD partition table have been checked OK!
    check pattern success
    mmc env offset: 0x27400000
    In: serial
    Out: serial
    Err: serial
    reboot_mode=cold_boot
    hpd_state=0
    cvbs performance type = 7, table = 0
    [store]To run cmd[emmc dtb_read 0x1000000 0x40000]
    _verify_dtb_checksum()-917: calc 2a4873b0, store 2a4873b0
    _verify_dtb_checksum()-917: calc 2a4873b0, store 2a4873b0
    dtb_read()-1039: total valid 2
    dtb_read()-1106: do nothing
    Amlogic multi-dtb tool
    Multi dtb detected
    Multi dtb tool version: v2 .
    Support 2 dtbs.
    aml_dt soc: gxl platform: p212 variant: 2g
    dtb 0 soc: gxl plat: p212 vari: 1g
    dtb 1 soc: gxl plat: p212 vari: 2g
    Find match dtb: 1
    card in
    init_part() 278: PART_TYPE_DOS
    [mmc_init] mmc init success
    Device: SDIO Port B
    Manufacturer ID: 27
    OEM: 5048
    Name: SD16G
    Tran Speed: 50000000
    Rd Block Len: 512
    SD version 3.0
    High Capacity: Yes
    Capacity: 14.5 GiB
    mmc clock: 40000000
    Bus Width: 4-bit
    [MSG]ini sz 0x25eB
    [fat]Filesize is 0x25eB[0M]
    [fat]0x:leftSz 25e < BPS 8000, gotSz 25e
    ERR(../drivers/usb/gadget/v2_burning/v2_sdc_burn/optimus_ini_parser.c)L275:line 18 error: ini support at most 3 words, but 5
    ERR(../drivers/usb/gadget/v2_burning/v2_sdc_burn/optimus_ini__aml_sdc_burn.c)L423:Fail in get cfg from aml_sdc_burn.ini
    ERR(../drivers/usb/gadget/v2_burning/v2_sdc_burn/optimus_sdc_burn.c)L586:Fail to parse file aml_sdc_burn.ini
    [MSG]to close image
    [MSG]Reload bmps env.
    Err imgread(L587):Logo header err.
    osd not enabled
    bmp - manipulate BMP image data

    Usage:
    bmp info <imageAddr> - display image info
    bmp display <imageAddr> [x y] - display image at x,y
    bmp scale [imageAddr scaleAddr] - scale image

    ERR(../drivers/usb/gadget/v2_burning/v2_common/optimus_progress_ui.c)L143:Fail in run[bmp display 0xbe40ac0 ], bmpOffsetName=upgrade_fail_offset
    [MSG]=====Burn Failed!!!!!
    [MSG]PLS long-press power key to shut down
    this is with official firmware from magicsee website : IRON S905X 20180727 upgrade.img

    The 2 led turns blue but the box seems frozen that way. The remote button doesnt do anything. If I reboot the boot loops come back..

    With all the other img I tried I got errors like ( poison rom, AtvXperience and IRON_s905x_aml_upgrade_package_20170630_SN.img )

    BL2 Built : 13:48:56, Sep 23 2016.
    gxl g7459bd4 - jianxin.pan@droid06

    set vcck to 1120 mv
    set vddee to 1000 mv
    Board ID = 3
    CPU clk: 1200MHz
    DQS-corr enabled
    DDR scramble enabled
    DDR3 chl: Rank0+1 @ 912MHz - PASS
    Rank0: 1024MB(auto)-2T-13
    Rank1: 1024MB(auto)-2T-13
    DataBus test pass!
    AddrBus test pass!
    Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
    New fip structure!
    Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
    Load bl31 from SD, src: 0x00020200, des: 0x10100000, size: 0x00015400
    Load bl33 from SD, src: 0x00038200, des: 0x01000000, size: 0x000a8600
    NOTICE: BL3-1: v1.0(debug):2e39a99
    NOTICE: BL3-1: Built : 16:36:21, Sep 20 2016
    aml log : bl31 normal boot !
    [Image: gxl_v1.1.3154-065f772 2016-09-29 14:08:54 yan.wang@droid05]
    OPS=0xc4
    6 89 f4 a2 7b 2 9e 22 f3 37 bb 6f [2.020978 Inits done]
    Wrong chip c0
    GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0; EMMC:400;NAND:82;SD:0;READ:0;0.0;CHK:0;
    no sdio debug board detected
    TE: 1628523

    As for USB burner, I was never able to get my device decoded. I did my own cable. When I short the pins I got a detection for like 2 sec and then it disapeared.

    On my board I see MAGTV101-v2.2 2018-06-25.
    The only thing I haven`t done is removing the heatsink to check if its really a S905X.

    So anything else I haven`t tryed? As I said im not an expert but this isn`t my first time playing around with devices. Im pretty sure my box isn't dead I just dont understand what exactly is wrong.

    Thanks.
    Last edited by wolfien; 07-26-2019, 16:45.

    #2
    (SOLVED) If its happends to anyone.. I had to take my volmeter, plug 1 pin on the ground of the UART port. And sorted pins stated in the other trreade. Just shorting the 2 pints didnt worked.

    Comment

    Working...
    X