Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

S805 bricked

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

    S805 bricked

    i managed to brick my S805 MXQ: i thought it was a s802, so i think i flsahed wrong firmware
    I flashed this one: http://freaktab.com/forum/tv-player-...253#post547253

    Now i cannot get anything anymore from this MXQ: pressing reset button and power up, nothing no image
    The same with SD card with default firmware also nothing
    USB burning tool doesn't recognize it

    What can i do?
    Strange thing was that, i think, it had no recovery.
    Pressing the reset and booting always booted it normally into android

    I only could enter recovery once, when i put TWRP recovery img on a SD card. With that it went into twrp recovery, and i could flash 115k4, but obviously that was the wrong firmware...

    #2
    Not tried this but came across this article in more than one place.

    You will need a working rom for your android, sd card for your device and the bootable software.

    Comment


      #3
      tried that also
      just connect a terminal

      this is what i get:

      QA5:A;SVN:B72;POC:3FF;STS:0;BOOT:0;INIT:0;READ:0;C HECK:0;PASS:0;
      no sdio debug board detected
      TE : 157649
      BT : 15:39:25 May 30 2015
      PMU:rn5t618
      i2c timeout
      i2c timeout
      i2c timeout
      i2c timeout
      i2c timeout
      i2c timeout
      DC01 v:1100, 0x[36]: 00 -> 28
      i2c timeout
      i2c timeout
      DC02 v:1150, 0x[37]: 00 -> 2c
      i2c timeout
      i2c timeout
      DC03 v:1500, 0x[38]: 00 -> 48
      i2c timeout
      i2c timeout
      i2c timeout
      i2c timeout
      LDO01 v:2900, 0x[4c]: 00 -> 50
      i2c timeout
      i2c timeout
      LDO02 v:1800, 0x[4d]: 00 -> 24
      i2c timeout
      i2c timeout
      LDO03 v:1800, 0x[4e]: 00 -> 30
      i2c timeout
      i2c timeout
      LDO04 v:2850, 0x[4f]: 00 -> 4e
      i2c timeout
      i2c timeout
      LDO05 v:1800, 0x[50]: 00 -> 24
      i2c timeout
      i2c timeout
      LDO0a v:2700, 0x[56]: 00 -> 28
      i2c timeout
      i2c timeout
      LDO0b v:900, 0x[57]: 00 -> 00
      i2c timeout

      CPU clock is 1200MHz

      CPU type: M8
      While loop 1000times, error...

      PUB init fail! Reset...

      Comment


        #4
        People have reported using the 'Amlogic BootcardMaker' method works if you have the correct firmware.
        Try some different firmware

        Comment


          #5
          doesn't work either...just tried with your link to FW

          Comment


            #6
            for amlogic bootcaqrdmaker i cannot find the right firmware that includes u-boot.bin

            Comment


              #7
              The ' u-boot.bin' is with the 'Amlogic_SDcardMaker_BootcardMaker_burnBootCard_v1 .0.1' rar file.

              Comment


                #8
                so, what should i put on the sd card?
                U-boot.bin from amlogic sdcardmaker and
                factory_update_param.aml
                recovery.img
                m201-ota-20141017.zip

                Comment


                  #9
                  what about nand pin shorting?

                  i have a different chip though, MT29F64G08CBABA

                  Comment


                    #10
                    Originally posted by sander815 View Post
                    so, what should i put on the sd card?
                    U-boot.bin from amlogic sdcardmaker and
                    factory_update_param.aml
                    recovery.img
                    m201-ota-20141017.zip
                    I could read the original blog for you, but it would involve typing the replay.
                    Read the instruction on the link : http://chinagadgetsreviews.com/how-t...n-minutes.html (wrong link corrected)
                    This is the safe option then opening you android box., but if you feel you follow instruction well (not sure you do following your posts), then open your android at your own risk.
                    Last edited by nick111; 01-02-2016, 16:38.

                    Comment


                      #11
                      its just not working like this, i tried several FW, and some other tips, but the only thing i see is the serial output and the blue led.
                      including tips from here: http://freaktab.com/forum/tv-player-...antly-on/page2

                      but i cannot get it to work. No signal on hdmi, nothing

                      Comment


                        #12
                        Have you seen the youtube video ?
                        Last edited by nick111; 01-02-2016, 17:26.

                        Comment


                          #13
                          managed to get it back to life by shortening ping 17 and 18. Shortening these pins, with sdcard in with FW and then power it up, and it began installing the firmware
                          only way to see that it was doing something was the serial connection

                          Comment


                            #14
                            Originally posted by sander815 View Post
                            managed to get it back to life by shortening ping 17 and 18. Shortening these pins, with sdcard in with FW and then power it up, and it began installing the firmware
                            only way to see that it was doing something was the serial connection
                            Hey mate, following all your story I have lived exactly the same problem. I've moved across all the different solutions with no success. I think I must do the same you did, but I'm not quite sure how to do it. It's more, I don't know the correct form to open my MXQ. Would you mind to explain how you make it? I'm pretty sure i can make it work if I can bring it back to life.

                            Cheers

                            Comment


                              #15
                              Im also in the same boat, have tried all i can think of, but can get no response out of the box. Could it truly be bricked?

                              Comment

                              Working...
                              X