1. Check out our companion app, Forums for Android! Download from Google Play

Support MXQ S805 rev 2.0 faked internal memory?

Discussion in 'Android TV' started by Kodikiller, Nov 29, 2016.

  1. Kodikiller

    Kodikiller New Member
    Thread Starter
    16

    Nov 29, 2016
    4
    1
    16
    Male
    I have been buying android boxes in bulk and reselling them for some time now. I recently purchased from a seller on DHGATE. I tried repeatedly to install my (Gaming kodi build) onto the box but to no avail. The internal memory is showing i have 5gb available. Im trying to transfer only 2.0gb to it. Es file explorer repeatedly says task failed and when i check the capacity it says it is full (I checked before the transfer and only 11% of the memory had been used.) So i decided to try a different rom. When i installed it. All worked well until i checked the capacity of the internal memory. Now it is showing true capacity at only 1.81gb. So i then took the box apart and looked at the nand chip. The chips part number is MT29F32G08CBADAWP, Which basically boils down to a 32gb nand flash chip from micron technologies. My question is how in the world can i get the full capacity out of this nand?
     

    Attached Files:


    Advertisement

  2. Kodikiller

    Kodikiller New Member
    Thread Starter
    16

    Nov 29, 2016
    4
    1
    16
    Male
    Anyone every had this issue? I did some research and it appears that you can partition your nand through adb. problem is i cant get the damned thing to connect through the network while its in recovery. Plus i dont have a male to male usb. (i do have one but it only seems to give the box power and nothing else, pc cant see it etc,)
     
  3. mikedt

    mikedt 你好
    2,238

    Sep 22, 2010
    21,289
    11,043
    2,238
    Teachaaa
    Jinan, China
    Could be a faulty or buggy firmware and storage layout build. And frankly the only peeps who can really fix that is the whatever unknown Shenzhen OEM who made the thing.
     
  4. Andrew Cole

    Andrew Cole Well-Known Member
    108

    Jun 12, 2016
    463
    158
    108
    Male
    Enable USB debugging in the box settings...

    It's possible that the internal memory has been hacked to show that it is a higher capacity than what it really is... but I doubt it.

    It's more likely the media you are transferring from and the way it is formatted... or even the way the internal memory is formatted.

    I'm pretty sure you should be able to find a way out of this somehow.
     
  5. Kodikiller

    Kodikiller New Member
    Thread Starter
    16

    Nov 29, 2016
    4
    1
    16
    Male
    Progress (not much) Yesterday when fooling around with the box. I was actually able to get USB burning tool to connect to the box thrrough usb without a problem. Its the sequence that i used, that allowed that to happen. The sequence i used is as follows: Connect USB cable while holding down reset switch. (No power, or any other cable plugged in) It boots to the "Amlogic S805 logo" and stays there. Adb is still not connecting to the box unless through network. It will not connect unless the box is fully booted as well and i cant do any internal memory partitioning/formatting unless i am in recovery. I know its got to be a sequence of power/reset switch/usb that im just not getting right. I will stay updated here until i get it. I hope someone will find the info useful. Maybe i should be using a chop stick instead of a tooth pick to poke the reset switch lmao
     
  6. Kodikiller

    Kodikiller New Member
    Thread Starter
    16

    Nov 29, 2016
    4
    1
    16
    Male
    I couldnt agree more. As i said above, when i looked up the part number on the internal memory. It stated that it was a 32gb. There has got to be an egregious amount of space that is just unused there. This will be a good learning experience for me. Im familiar with adb, (moving files, rooting etc.) so once i get it to connect i will be in the home stretch. I have found an excellent tutorial online for re-partitioning the nand. One thing i did forget to mention was that the USB powers the device, with or without the pwr adapter in. Perhaps if i rewired my USB cord (homemade) and disconnected the power and ground wires, leaving only the info wires, i may be able to get it to boot properly. Thanks again for helping me bounce ideas. EDIT: i also forgot to mention that this box will not boot from the sd card. All activity of installing a custom rom, must be done from the recovery. If you try to boot the box with the card in place, it will hang on the Boot logo and never boot into anything (recovery, card, os etc) If you boot into recovery without the card then it works fine. I still have not figured out how to install a custom recovery on this yet. Can i install the img file from the stock recovery? Then just reboot?
     
    #6 Kodikiller, Dec 1, 2016
    Last edited: Dec 1, 2016
    Andrew Cole likes this.
  7. mikedt

    mikedt 你好
    2,238

    Sep 22, 2010
    21,289
    11,043
    2,238
    Teachaaa
    Jinan, China
    Sounds like it's probably a factory reject chip, that's not 100% functional, and the module and Android build was made up to use them. And if an attempt was made to make full use of it's stated capacity, it wouldn't work.

    There's a massive trade in B and C grade components in Shenzhen, which often end-up in the knock-off Apple iPhones and Samsung Galaxys, and the many off-brand things sold cheap from Ebay, DHgate, etc. These anonymous cheapo "MXQ" type devices are literally thrown together, like hurriedly assembled on a table a shopping mall backr0om or a shed somewhere.

    There's malls where you can walk around the booths, and buy A, B and C graded NAND, SRAM, etc. and just about anything else by the handful.
    https://en.wikipedia.org/wiki/SEG_Plaza :thumbsupdroid:
     
    #7 mikedt, Dec 4, 2016
    Last edited: Dec 4, 2016
    Andrew Cole likes this.

Share This Page

Loading...