Search results

  1. riclin

    Q+ TV Box Scam? - or just Unreasonably Suspicious!

    OK - having cracked the box I investigated further regarding the hardware, and contrary to my comment above, it does seem that the hardware is correct and that is is 4G/32G as advertised (apols for the unreasonable suspicion ). Instead, the problem seems to be caused by u-boot passing incorrect...
  2. riclin

    Q+ TV Box Scam? - or just Unreasonably Suspicious!

    I checked h/w - the RAM markings initially were inconclusive but the FBGA code of D9PSC printed on the RAM chips cross-references to a MT41K512M4DA-125 which as far as I can determine is a 2G chip. There are 8 of these chips (4 top & 4 bottom) so 8 * 2G = 16GB when I went to school. Not 32GB...
  3. riclin

    Q+ TV Box Scam? - or just Unreasonably Suspicious!

    Fair comment. Must confess that I'd not registered that these forums were facilitated as a support to a commercial organization's customers so apols if I have been seen to be taking advantage. Prob best if I back right out.
  4. riclin

    Q+ TV Box Scam? - or just Unreasonably Suspicious!

    I have previously posted regarding an issue where a Turewell (OTT) Q+ TV Box specced at 4/32GB reports 2/16GB after a firmware reflash. I have been unable to get a response from either the seller or from Turewell. At the expense of being unreasonably cynical, is it possible - or even likely -...
  5. riclin

    Q-Plus H6 4/32GB TV Box Reflash Problem

    Not confident about the likelihood of not losing data - the flash process clears all memory in my experience. Backup, backup, backup!
  6. riclin

    Q-Plus H6 4/32GB TV Box Reflash Problem

    I have written to Turewell asking for a link to the correct firmware. I will repost here if/when I get a reply.
  7. riclin

    Q-Plus H6 4/32GB TV Box Reflash Problem

    Hi all - I wonder whether somebody has a suggestion regarding a rather weird issue following a firmware reflash to this device? After inadvertently blowing away /system/bin/toybox which left the device unbootable (don't ask!!) I decided that reinstalling the firmware would be the quickest fix...