Announcement

Collapse
No announcement yet.

MXQ Pro 4k Bricked!! What pins to short for NAND.

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

    MXQ Pro 4k Bricked!! What pins to short for NAND.

    I need to correctly identify what pins on this specific board\NAND chip to short. I have seen other pics of nand chips but can not locate any that identifies the pins for this chip.

    See Pic for reference.

    After screwing with this box for a week it looks as though i may have to short out the nand pins to reinstall firmware unless someone knows another way of getting it starting again.

    Hostory of problem.
    Box was given to me as not working. Orginally the MBOX logo would come on screen but that doesnt even come up now. Just a black screen. After reading alot and trying different methods I came across a post that says there are known issues with reset button on some manufacturers of these boards. I am hoping that is my issue.
    SD card method does nothing
    USB method gets a Erase bootloader/Lowper/Identify/Error result" within seconds of starting.

    If anyone has other ideas or options please feel free to suggest them. Specific instructions for any other workaround is apprerciated.

    BOX details:
    Sold as a 2017 Model GooBang Doo Android 6.0 TV Box, MXQ Pro Android TV Box 64 Bits Amlogic S905X
    Only identification written on PC board is MXQ_S95X V2_0 and 20161020
    The NAND is stamped as:
    Sandisk C423105451
    SDTNRGAMA-008G
    WAE52501SA
    CHINA

    Seller sent me files named
    aml_sdc_burn.ini
    aml_upgrade_package.img
    u-boot.bin.sd.bin
    and instructions on doing the usb update method. I tried the usb and SD card method but nothing happened only error message as above. not sure if these files were for an upgrade or the correct ones for getting box started again.

    Thanks for any assistance.



    #2
    Different board but hard to total brixk 905x so what you need to do is look at wifi chip. Can point in right direction for firmware once you take photo close up so we can see written part of chip. I tried to blow up you photo but cant read it.

    Its the black chip next to wifi lead. Takes a angle and phone on zoom to normally get a good shot.
    Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

    Comment


      #3
      Hi Scooter,
      Thanks for reply. I looked at wifi chip It has following info on it.
      RMC (written within part of a logo. looks like wifi antenna coming out from top ends of the "M")
      8189ETV
      G816G32
      GG37

      Hope that helps.
      Cheers
      Don

      Comment


        #4
        Look in the 905x for firmware with that wifi there are a few out.
        Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

        Comment


          #5
          Thanks Scooter.

          I have searched but couldn't find a file specific to the S905X 8189etv wifi. I have located firmware for a S905 with 8189. but I guess it is important that it is for S905X. I posted a request for anyone who has the file in the firmware section.

          Thanks

          Comment


            #6
            http://freaktab.com/forum/tv-player-...atv-android-tv.

            You will need to download the wifi fix on same link dont worry about numbers i tried on you wifi worked.

            Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

            Comment


              #7
              thanks,

              Tried it but still get the following error:

              [14:35:13 597][HUB3-5][Inf]--Update device path
              [14:35:13 610][HUB3-1][Inf]--Connect path=Standard Enhanced PCI to USB Host Controller/P0/P0
              [14:35:13 610][HUB3-1][Inf]--Start burning...
              [14:35:13 701][HUB3-1][Inf]--------------ERASE BOOTLOADER------------
              [14:35:18 755][HUB3-1][Err]--IOCTL_IDENTIFY_HOST_Handler ret=-116 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.

              Thanks

              Comment


                #8
                Try running burn program as administrator it look like driver or usb stopping not device not taking firmware with that error.
                Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                Comment


                  #9
                  tried that still no luck. I noticed by accident that i can do exactly the same thing via loading through burn tool whether the reset button is pressed and held pressed or released. It is as though the reset button is not doing anything. I would of thought if button is pressed the program would not be able to start the load process. I have included the last part of the text file from latest load failure The only time i get a different result than the one reported above is if i start the load program then plug in USB. hope that may shed some light on problem

                  thanks

                  [17:15:02 730][HUB3-1][Inf]--------------ERASE BOOTLOADER------------
                  [17:15:02 755][HUB3-1][Inf]--2-2-0-0
                  [17:15:02 772][HUB3-1][Inf]-------------Download DDR.USB-----------
                  [17:15:02 772][HUB3-1][Inf]--Close device handle 0x0000081c
                  [17:15:02 823][HUB3-1][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#5&77e775c&0&1#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x0000081c
                  [17:15:02 874][HUB3-1][Inf]--2-2-0-0
                  [17:15:02 875][HUB3-1][Inf]--Control write pll reg1 0xd9000000:0x000000b1
                  [17:15:03 377][HUB3-1][Inf]--Control write pll reg1 0xd9000000:0x00005183
                  [17:15:03 879][HUB3-1][Inf]--Write initial succeed
                  [17:15:03 879][HUB3-1][Inf]--Upload encrypt at 0xc8100228
                  [17:15:03 880][HUB3-1][Inf]--ulValue = 0xadfc318c
                  [17:15:03 881][HUB3-1][Inf]--Read encrypt value succeed
                  [17:15:03 897][HUB3-1][Inf]--Transfer complete
                  [17:15:03 899][HUB3-1][Inf]--Run at address 0xd9000000
                  [17:15:03 901][HUB3-1][Inf]--RunInRam succeed
                  [17:15:03 924][HUB3-1][Inf]--2-2-0-0
                  [17:15:03 924][HUB3-1][Inf]--CheckFileRunState succeed
                  [17:15:03 925][HUB3-1][Inf]--runResult:0x 0,paraMagic:0x7856efab
                  [17:15:03 925][HUB3-1][Inf]--ddrCapacity:0x 800
                  [17:15:03 926][HUB3-1][Inf]-------------Download UBOOT.USB-----------
                  [17:15:03 928][HUB3-1][Inf]--2-2-0-0
                  [17:15:03 928][HUB3-1][Inf]--ulValue = 0xadfc318c
                  [17:15:03 928][HUB3-1][Inf]--Download DDR.USB buffer at 0xd9000000
                  [17:15:03 943][HUB3-1][Inf]--Transfer complete
                  [17:15:03 943][HUB3-1][Inf]--Download UBOOT.USB buffer at 0x0200c000
                  [17:15:04 242][HUB3-1][Inf]--Transfer complete
                  [17:15:04 250][HUB3-1][Inf]--DownCheckPara succeed
                  [17:15:04 250][HUB3-1][Inf]--Run at address 0xd9000000
                  [17:15:04 292][HUB3-1][Err]--generatedAddSum:0x8abfae59;srcAddSum:0x17b94557;ru nResult:0x e6;paraMagic:0x7856efab
                  [17:15:04 292][HUB3-1][Inf]--ReadCheckPara failed
                  [17:15:04 408][HUB3-1][Err]--[0x110f0902]Unknown
                  [17:15:04 410][HUB3-1][Inf]--Close device handle 0x0000081c

                  Comment


                    #10
                    I I found some info where someone else had to short the pins on same chip but different board. I tried it on mine. Got a little further on install (4%). then i got this error
                    0x10302001]Romcode/Switch status/Check connect/Enum device error
                    any ideas?
                    Thanks

                    Comment


                      #11
                      No one has device so you may have to crack open and take photos. Some come with wierd nan and memory even different chips for storage on same device.

                      If resetting and flashing firmware on tool not working now its dr detective to find out why other firmware not working. I cant remember if i ordered one of amazon or not but if i did its still a few weeks out from shipping snail mail...

                      Id say get supported devices but even that becoming crap shoot as they changing gutz as soon as stable roms made lol.... China gadget life
                      Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                      Comment


                        #12
                        See pics below. Let me know if you need any other info. Thanks for help. My OCD wont let me quit on this box.....LOL

                        Comment


                          #13
                          Here ya re ocd. try 7/8 from dot. Take photo of wifi chip too.
                          Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                          Comment


                            #14
                            see attached photo.

                            id on it says
                            8189ETV
                            G816G32
                            GG37

                            Comment


                              #15
                              Update
                              I am able to get the load process started for about 4 %. then it stops with the following.
                              On burn tool top screen where it shows usb it says Download Boot
                              Then i get error on bottom part of program that says
                              [0x10302001]Romcode/Switch status/Check connect/Enum device error.

                              Then everything stops.
                              I tried a few different firmware files.

                              Hope this gives some insight.
                              Last edited by Labrador; 04-18-2017, 17:32.

                              Comment

                              Working...
                              X