Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

GT1 Ultimate bricked - need help to fix it

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

    GT1 Ultimate bricked - need help to fix it

    Hello everybody!
    Well, I'm just another GT1 Ultimate owner, who, without intention, become member of "Bricked GT1" club.
    Here are details:
    GT1 Ultimate S/No: AX12..., with AP6255 WiFi, nad 32GB eMMC Toshiba (153 pin FBGA).

    Box came with build 703NO, but I experienced some bugs (with portrait application display), so I updated it with build 704NO from the following link (http://freaktab.com/forum/tv-pla ... -3g-32g-a912-ap6255). Update was done by SD card method, and successfull.

    However, although improved, issue with portrait application display was not fully solved, so I went further. I installed ATV package (http://freaktab.com/forum/tv-pla ... 7-standard-ultimate). Instalation went fine, but I didn't like limited choice of applications on Play Store, so I decided to try something else.

    This time I selected Nano Nexus variant (http://freaktab.com/forum/tv-pla ... us-roms-android-7-1). I put SW on SD card, and tried to boot from it, while keeping reset button pushed. Since box booted from internal memory rather that from SD card, I restarted it several times, until one time box didn't boot.
    When plugged in, only white LED is lit, but no any picture is shown on TV via HDMI.

    I tried to recover device, both by booting it from bootable SD card, or via USB Burning Tool, but with no luck.
    Using USB Burning Tool, I can burn just some of the IMG files from various sources. For example, I can burn this image (http://freak-tab.de/luis/Beelink ... TV-GT1_Ultimate.zip) as per instructions from http://freaktab.com/forum/tv-pla ... tv-android-tv-ddr4. But after burning is successfully finished, box again is not working.

    Also, I can burn image Nexus_q201_Nano_NHG47L-20170825.img (from http://freaktab.com/forum/tv-pla ... us-roms-android-7-1), but box again is not working.

    If I try to burn "official" images GT1_704NO_AP6255 or GT1_704NO_AP6255, I get error in USB Burning Tool, around 4%, which I can not overcome ([0x10303004]Romcode/Switch status/Identify/Error result).

    Today I manage to get serial connection to the device, but now I'm even more confused, since I see no error in booting sequence - or am I missing something?
    Looks like device is booting fine, but nothing is shown after last line (Relocation Offset is: b6ec9000):
    GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0; EMMC:0;READ:0;0.0;CHK:0;
    TE: 54995

    BL2 Built : 13:18:48, Dec 21 2016.
    gxl g4fc4d4e - xiaobo.gu@droid05

    set vdd cpu_a to 1120 mv
    set vdd cpu_b to 1050 mv
    set vddee to 1000 mv
    Board ID = 6
    CPU clk: 1200MHz
    DQS-corr enabled
    DDR scramble enabled
    DDR4 chl: Rank0+1 @ 636MHz
    Rank0: 2048MB-2T-18
    Rank1: 1024MB-2T-18
    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
    Load bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00015400
    Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
    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=0x82

    c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.301803 Inits done]

    secure task start!
    high task start!
    low task start!
    INFO: BL3-1: Initializing runtime services
    WARNING: No OPTEE provided by BL2 boot loader
    ERROR: Error initializing runtime service opteed_fast
    INFO: BL3-1: Preparing for EL3 exit to normal world
    INFO: BL3-1: Next image address = 0x1000000
    INFO: BL3-1: Next image spsr = 0x3c9


    U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)

    DRAM: 3 GiB
    Relocation Offset is: b6ec9000
    Does someone has idea what can be wrong with my device and how to fix it?

    Also, how long boot sequence is displayed on serial console? Can someone attach here example of full boot - just to compare it with my logs?

    BR

    #2
    Originally posted by rafiki View Post
    Hello everybody!
    Well, I'm just another GT1 Ultimate owner, who, without intention, become member of "Bricked GT1" club.
    Here are details:
    GT1 Ultimate S/No: AX12..., with AP6255 WiFi, nad 32GB eMMC Toshiba (153 pin FBGA).

    Box came with build 703NO, but I experienced some bugs (with portrait application display), so I updated it with build 704NO from the following link (http://freaktab.com/forum/tv-pla ... -3g-32g-a912-ap6255). Update was done by SD card method, and successfull.

    However, although improved, issue with portrait application display was not fully solved, so I went further. I installed ATV package (http://freaktab.com/forum/tv-pla ... 7-standard-ultimate). Instalation went fine, but I didn't like limited choice of applications on Play Store, so I decided to try something else.

    This time I selected Nano Nexus variant (http://freaktab.com/forum/tv-pla ... us-roms-android-7-1). I put SW on SD card, and tried to boot from it, while keeping reset button pushed. Since box booted from internal memory rather that from SD card, I restarted it several times, until one time box didn't boot.
    When plugged in, only white LED is lit, but no any picture is shown on TV via HDMI.

    I tried to recover device, both by booting it from bootable SD card, or via USB Burning Tool, but with no luck.
    Using USB Burning Tool, I can burn just some of the IMG files from various sources. For example, I can burn this image (http://freak-tab.de/luis/Beelink ... TV-GT1_Ultimate.zip) as per instructions from http://freaktab.com/forum/tv-pla ... tv-android-tv-ddr4. But after burning is successfully finished, box again is not working.

    Also, I can burn image Nexus_q201_Nano_NHG47L-20170825.img (from http://freaktab.com/forum/tv-pla ... us-roms-android-7-1), but box again is not working.

    If I try to burn "official" images GT1_704NO_AP6255 or GT1_704NO_AP6255, I get error in USB Burning Tool, around 4%, which I can not overcome ([0x10303004]Romcode/Switch status/Identify/Error result).

    Today I manage to get serial connection to the device, but now I'm even more confused, since I see no error in booting sequence - or am I missing something?
    Looks like device is booting fine, but nothing is shown after last line (Relocation Offset is: b6ec9000):
    GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0; EMMC:0;READ:0;0.0;CHK:0;
    TE: 54995

    BL2 Built : 13:18:48, Dec 21 2016.
    gxl g4fc4d4e - xiaobo.gu@droid05

    set vdd cpu_a to 1120 mv
    set vdd cpu_b to 1050 mv
    set vddee to 1000 mv
    Board ID = 6
    CPU clk: 1200MHz
    DQS-corr enabled
    DDR scramble enabled
    DDR4 chl: Rank0+1 @ 636MHz
    Rank0: 2048MB-2T-18
    Rank1: 1024MB-2T-18
    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
    Load bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00015400
    Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
    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=0x82

    c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.301803 Inits done]

    secure task start!
    high task start!
    low task start!
    INFO: BL3-1: Initializing runtime services
    WARNING: No OPTEE provided by BL2 boot loader
    ERROR: Error initializing runtime service opteed_fast
    INFO: BL3-1: Preparing for EL3 exit to normal world
    INFO: BL3-1: Next image address = 0x1000000
    INFO: BL3-1: Next image spsr = 0x3c9


    U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)

    DRAM: 3 GiB
    Relocation Offset is: b6ec9000
    Does someone has idea what can be wrong with my device and how to fix it?

    Also, how long boot sequence is displayed on serial console? Can someone attach here example of full boot - just to compare it with my logs?

    BR
    Hi rafiki ,

    not sure if this can help :



    good luck / greetings / gefattern

    Comment


      #3
      Hi gefattern, thanks fot the help.

      I tried that SD card metod, but looks like box never tried to boot from the SD card. Here is log of boot with bootable card inside:
      Code:
      GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
      TE: 50305
      
      BL2 Built : 13:18:48, Dec 21 2016. 
      gxl g4fc4d4e - xiaobo.gu@droid05
      
      set vdd cpu_a to 1120 mv
      set vdd cpu_b to 1050 mv
      set vddee to 1000 mv
      Board ID = 6
      CPU clk: 1200MHz
      DQS-corr enabled
      DDR scramble enabled
      DDR4 chl: Rank0+1 @ 636MHz
      Rank0: 2048MB-2T-18
      Rank1: 1024MB-2T-18
      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
      Load bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00015400
      Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
      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=0x82
      c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.297113 Inits done]
      secure task start!
      high task start!
      low task start!
      INFO:    BL3-1: Initializing runtime services
      WARNING: No OPTEE provided by BL2 boot loader
      ERROR:   Error initializing runtime service opteed_fast
      INFO:    BL3-1: Preparing for EL3 exit to normal world
      INFO:    BL3-1: Next image address = 0x1000000
      INFO:    BL3-1: Next image spsr = 0x3c9
      
      
      U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)
      
      DRAM:  3 GiB
      Relocation Offset is: b6ec9000
      And here is one when I hold reset down for a some time:
      Code:
      GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
      TE: 54106
      
      BL2 Built : 13:18:48, Dec 21 2016. 
      gxl g4fc4d4e - xiaobo.gu@droid05
      
      set vdd cpu_a to 1120 mv
      set vdd cpu_b to 1050 mv
      set vddee to 1000 mv
      Board ID = 6
      CPU clk: 1200MHz
      DQS-corr enabled
      DDR scramble enabled
      DDR4 chl: Rank0+1 @ 636MHz
      Rank0: 2048MB-2T-18
      Rank1: 1024MB-2T-18
      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
      Load bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00015400
      Load bl33 from eMMC, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
      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=0x82
      c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.300928 Inits done]
      secure task start!
      high task start!
      low task start!
      INFO:    BL3-1: Initializing runtime services
      WARNING: No OPTEE provided by BL2 boot loader
      ERROR:   Error initializing runtime service opteed_fast
      INFO:    BL3-1: Preparing for EL3 exit to normal world
      INFO:    BL3-1: Next image address = 0x1000000
      INFO:    BL3-1: Next image spsr = 0x3c9
      
      
      U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)
      
      DRAM:  3 GiB
      Relocation Offset is: b6ec9000
      Looks like I can not force it to boot from SD card.

      BR

      Comment


        #4
        Hi rafiki ,

        look here at Post #9 maybe it helps , if you are connected with Terminal :



        good luck / gefattern

        Comment


          #5
          Thanks, I'll check that too, since I made some progress by myself, but still not enough



          First, I managed to flash (via USB Burning tool) GT1_704NO.img - the one supposed to be latest for GT1 Ultimate. Just don't ask me how I did it, realy have no idea. I've been pressing reset button together with shortcuting two pins in order to get device recognized by PC. At one moment, flashing proceeded beyond 4% - where I was always getting error: [0x10303004]Romcode/Switch status/Identify/Error result

          Alas, even after successful flashing, box didn't came back from dead. Here is the boot log:
          Code:
          GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
          TE: 55354
          
          BL2 Built : 11:58:42, May 27 2017. 
          gxl gc3c9a84 - xiaobo.gu@droid05
          
          set vdd cpu_a to 1120 mv
          set vdd cpu_b to 1050 mv
          set vddee to 1000 mv
          Board ID = 6
          CPU clk: 1200MHz
          DQS-corr enabled
          DDR scramble enabled
          DDR3 chl: Rank0+1 @ 912MHz - FAIL
          DDR3 chl: Rank0 @ 912MHz - FAIL
          DDR3 chl: Rank0 16bit @ 912MHz - FAIL
          DDR4 chl: Rank0+1 @ 912MHz - PASS
          Rank0: 2048MB(auto)-2T-18
          Rank1: 1024MB(auto)-2T-18
          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
          Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400
          Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x00065600
          NOTICE:  BL3-1: v1.0(release):3348978
          NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
          NOTICE:  BL3-1: BL33 decompress pass
          mpu_config_enable:ok
          [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
          OPS=0x82
          wdt: reset registers!
          c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.583898 Inits done]
          secure task start!
          high task start!
          low task start!
          ERROR:   Error initializing runtime service opteed_fast
          
          
          U-Boot 2015.01-gf771c6c (Aug 19 2017 - 11:48:44)
          
          DRAM:  3 GiB
          Relocation Offset is: b6eb4000
          register usb cfg[0][1] = 00000000b7f5ac58
          [CANVAS]canvas init
          vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
          vpu: clk_level = 7
          vđŕ _ERR_BADMAGIC, load default parameters
          vpu: clk_level = 7
          vpu _ERR_BADMAGIC, load default parameters
          vpu: clk
          Then decided to try again to boot from SD card, prepared by BootCardMaker 2.0.3. Now I manage to start booting from SD card, but again is stuck on "vpu: clk_level = 7"
          Code:
          GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;0.0;CHK:0;
          no sdio debug board detected 
          TE: 235293
          
          BL2 Built : 11:58:42, May 27 2017. 
          gxl gc3c9a84 - xiaobo.gu@droid05
          
          set vdd cpu_a to 1120 mv
          set vdd cpu_b to 1050 mv
          set vddee to 1000 mv
          Board ID = 6
          CPU clk: 1200MHz
          DQS-corr enabled
          DDR scramble enabled
          DDR3 chl: Rank0+1 @ 792MHz - FAIL
          DDR3 chl: Rank0 @ 792MHz - FAIL
          DDR3 chl: Rank0 16bit @ 792MHz - FAIL
          DDR4 chl: Rank0+1 @ 792MHz - PASS
          Rank0: 2048MB(auto)-2T-18
          Rank1: 1024MB(auto)-2T-18
          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: 0x05100000, size: 0x00018400
          Load bl33 from SD, src: 0x0003c200, des: 0x01000000, size: 0x00065e00
          NOTICE:  BL3-1: v1.0(release):3348978
          NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
          NOTICE:  BL3-1: BL33 decompress pass
          mpu_config_enable:ok
          [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
          OPS=0x82
          wdt: reset registers!
          c8 af f 5d 3e cb c7 69 33 f8 5c bf [0.865211 Inits done]
          secure task start!
          high task start!
          low task start!
          ERROR:   Error initializing runtime service opteed_fast
          
          
          U-Boot 2015.01-g9754c09 (Aug 05 2017 - 15:07:23)
          
          DRAM:  3 GiB
          Relocation Offset is: b6eb3000
          register usb cfg[0][1] = 00000000b7f5a8a0
          [CANVAS]canvas init
          vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
          vpu: clk_level = 7
          v
          Does this looks like HW error, or just wrong SW?

          BR

          Comment


            #6
            Hi rafiki
            You can unbrick GT1 Ultimate with 'USB Burning Tool' and a usb cable like this...


            Good luck!

            Comment


              #7
              Hi Albert,

              thank you for help.

              I have USB Burning Tool and USB A/M to A/M cable. and I'm able to flash ROM to my device. Problem is that even after successful flashing, device is not booting.
              It's only get up to the initialization of Video Processing Unit:
              Code:
              [CANVAS]canvas init
              vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
              vpu: clk_level = 7
              v
              So, now I believe, either my video chip is dead, either device specification data are wrong.

              Any ideas how to check is video chip working?

              BR

              Comment


                #8
                Sorry to hear that but I have no idea...

                Comment


                  #9
                  Hi rafiki, sorry to hear about your device. I read about this somewhere else. A guy trying to unbrick his GT1 but no luck. The key point he's missing is, he pulled of power cable at some point, he thinks it's not necessary, somebody advised him not to pull the power cable during the entire process. Maybe this will help you? I'll try to find that source.

                  Comment


                    #10
                    Hi Venomz, thank you for helping!
                    Well, while flashing via USB Burning tool, I keep power supply connected all the time.
                    In the mean time, I made no progress on reviving my box. I managed to flash couple of more ROMs, but all the time device stop at the same point in boot procedure.
                    Most probably, it's HW error, and device is faulty.
                    BR

                    Comment


                      #11
                      anything new? I think that im stuck in the same state :-(

                      Comment


                        #12
                        This box is big shit….no chance to return

                        Comment


                          #13
                          there are some guides to unbrick the device, did you try flash with sd card method?

                          Redmi Note 4 cihazımdan Tapatalk kullanılarak gönderildi

                          Comment


                            #14






                            first prepare and insert sd card, than power on device without pressing reset button and only wait if its boot, if not works, try pressing reset button when power on with toothpick (you have to restart tv after power on the box sometimes, some tvs cant detect the screen signals without reboot)

                            Comment


                              #15
                              The same thing happened to my device today. I TRIED everything, but to no avail.

                              Comment

                              Working...
                              X