Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

OTT MXQ PRO 4K s905x p212

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

    OTT MXQ PRO 4K s905x p212

    Couple questions .
    what is the difference between all the other S905X 1g/8G p212 boxes and our MXq pro 4K p212 version, meaning why won't TWRP for 905X and XannyTech's rom for these boxes work.

    is it possible that my boxes Android build is just screwed up or something
    before I tried TWRP even the stock recovery would give an error something about couldn't mount to /System.
    tried TWRP no dice don't know what I was thinking desperation maybe.
    I feel like USB and boot from SD are disabled is this even possible.

    as soon as I get a copy of the stock recovery file I will try to load from SD.

    it seems TWRP is working for all S905X
    but I can't even connect via USB to USB the AML USB tool.
    I feel like this box is locked from anything but OTA updates. is this possible or likely ?

    It shipped with root access ,any way some things can be fixed from root explorer.

    problems/ annoyances include.

    amcodec caused lockups and has to be disabled

    play store has to be rolled back to work

    enter key mapped to click on the onscreen keyboard and often gives a "q" when clicked rather than being mapped to "enter"

    no status or navbar.

    stock recovery when told to reboot to boot loader boots as normal.

    Toetje is working on this box but without USB connectivity or working twrp..........
    .
    Rashr does work which is how I got TWRP recovery installed (non working)

    I have spent a few hours a day working on various solutions /fixes and found I might be able to fix certain small things. But it looks like until someone comes up with a functional TWRP or I get the USB going "new factory shielded cable" I am stuck with the device as is, which is fine for the rest of the family.
    maybe slip the MXQ to the den and hope one day things get worked out for this one 905X device that doesn't follow suit. in the meantime buy a more easily modded box.

    anyhow once again any answers or solutions are appreciated I mainly am curious as to what or why this particular box is any different than other s905X boxes.



    Back before vista was windows 7 and when IP version 6 was in development ,I was fairly up to date on various things, but tablets weren't all that common and Android TV boxes we're unheard of.
    unfortunately I never picked up Linux ,script commands ,or even got fluent into C++.

    I guess I was afraid the bug would completely consume me and my social (sex) life.
    LMAO fast forward 'til now and I got a handful of offspring and not a marketable skill one in the tech sector. guess I would have been better off letting my 19" superbright CRT burn out my retina while debugging....hindsight is so painfully 20/20.







    #2
    Originally posted by deebee123 View Post
    Couple questions .
    what is the difference between all the other S905X 1g/8G p212 boxes and our MXq pro 4K p212 version, meaning why won't TWRP for 905X and XannyTech's rom for these boxes work.

    is it possible that my boxes Android build is just screwed up or something
    before I tried TWRP even the stock recovery would give an error something about couldn't mount to /System.
    tried TWRP no dice don't know what I was thinking desperation maybe.
    I feel like USB and boot from SD are disabled is this even possible.

    as soon as I get a copy of the stock recovery file I will try to load from SD.

    it seems TWRP is working for all S905X
    but I can't even connect via USB to USB the AML USB tool.
    I feel like this box is locked from anything but OTA updates. is this possible or likely ?

    It shipped with root access ,any way some things can be fixed from root explorer.

    problems/ annoyances include.

    amcodec caused lockups and has to be disabled

    play store has to be rolled back to work

    enter key mapped to click on the onscreen keyboard and often gives a "q" when clicked rather than being mapped to "enter"

    no status or navbar.

    stock recovery when told to reboot to boot loader boots as normal.

    Toetje is working on this box but without USB connectivity or working twrp..........
    .
    Rashr does work which is how I got TWRP recovery installed (non working)

    I have spent a few hours a day working on various solutions /fixes and found I might be able to fix certain small things. But it looks like until someone comes up with a functional TWRP or I get the USB going "new factory shielded cable" I am stuck with the device as is, which is fine for the rest of the family.
    maybe slip the MXQ to the den and hope one day things get worked out for this one 905X device that doesn't follow suit. in the meantime buy a more easily modded box.

    anyhow once again any answers or solutions are appreciated I mainly am curious as to what or why this particular box is any different than other s905X boxes.



    Back before vista was windows 7 and when IP version 6 was in development ,I was fairly up to date on various things, but tablets weren't all that common and Android TV boxes we're unheard of.
    unfortunately I never picked up Linux ,script commands ,or even got fluent into C++.

    I guess I was afraid the bug would completely consume me and my social (sex) life.
    LMAO fast forward 'til now and I got a handful of offspring and not a marketable skill one in the tech sector. guess I would have been better off letting my 19" superbright CRT burn out my retina while debugging....hindsight is so painfully 20/20.





    The USB Boot and even SDCard boot are working fine, However also Libreelec is not able to detect the internal storage while running the install script. As I was able to flash A ota zip trough stock Recovery I'm sure there is a way making this work. But my knowledge in TWRP is to small for that. I compared the fstab files and those where fine. So I hope someone can assist us

    Comment


      #3
      I picked up an s92 Aml912 which wasn't detected on my laptop's USB either so seems like it is the laptop that is the problem not the MXQ.
      I may try to make a bootable SD card from your rom and update that way.
      I just need to try and find out how the Remanufactured NAND chip effects things. I know that the small uboot code doesn't have the ability to detect and avoid bad blocks. Not sure if a nand chip has bad block addresses internally blocked or somehow skipped so that the chip can be burnt to by basic methods.
      I just don't want to get a bad burn then find out that I have to get a rework station and a new fully functional NAND chip.

      Comment


        #4
        Originally posted by deebee123 View Post
        I picked up an s92 Aml912 which wasn't detected on my laptop's USB either so seems like it is the laptop that is the problem not the MXQ.
        I may try to make a bootable SD card from your rom and update that way.
        I just need to try and find out how the Remanufactured NAND chip effects things. I know that the small uboot code doesn't have the ability to detect and avoid bad blocks. Not sure if a nand chip has bad block addresses internally blocked or somehow skipped so that the chip can be burnt to by basic methods.
        I just don't want to get a bad burn then find out that I have to get a rework station and a new fully functional NAND chip.
        How are you connecting the device to the PC and do you use the toolpick method?

        Comment

        Working...
        X