MXQ OTT S805 Box Bricked- Red LED constantly ON

[viper76]

Any help guys, my box is dead only the red light it's on, can anybody assist me to the right way, do I need open the box? I really don't understand what ckeays mean because my English is weak..please guys if you know something do to me a easy step by step, show me where to begun, do I need open the box? I already have usb male to male

try this

http://mbox.co.za/forum/viewtopic.php?f=62&t=182

[Shadi86]

Any help guys, my box is dead only the red light it's on, can anybody assist me to the right way, do I need open the box? I really don't understand what ckeays mean because my English is weak..please guys if you know something do to me a easy step by step, show me where to begun, do I need open the box? I already have usb male to male

[Shadi86]

If any can assist my on the right way maybe with step by step video, it first time I have its so difficult to unbrick a box so please help to unbrick my box, I have mxq box

[Shadi86]

Any video or pitcure for us noob, it would be good

[ckeays]

BurnigTools no working for me, any idea for unbrick

Look at my post above. Nothing worked for me unless I joined the two pins on the nand. Then use the usb burning tool and load the image in the link above.

[macmanolo]

I have the same board and only the red light comes on, this is my report:

QA5:A;SVN:B72;POC:3FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0;
no sdio debug board detected
TE : 24849
BT : 11:44:45 Jan 12 2015
PMU:NONE
##### VDDEE voltage = 0x044c


CPU clock is 792MHz

Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [8040007f] retry...
Error loop 10times, error...

PUB init fail! Reset...
QA5:A;SVN:B72;POC:3FF;STS:6B730001;SKIP:0;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
no sdio debug board detected
TE : 569912
BT : 10:55:46 Oct 27 2014
PMU:NONE
##### VDDEE voltage = 0x041a


CPU clock is 792MHz

Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Aml log : DDR0 - PUB_PGSR0_QSGERR with [c040007f] retry...
Error loop 10times, error...

PUB init fail! Reset...
QA5:A;SVN:B72;POC:3FF;STS:6B730002;SKIP:1;USB:1;SERIAL:2;STS:6B730000;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0;
no sdio debug board detected
TE : 10016071

BurnigTools no working for me, any idea for unbrick

[bigifa]

Thanks for your help I like the push switch idea if I get this going again that will be getting fitted lol

I'll have a bash at the UART tonight I have lots of ttl cables from the good old days of cable "testing/hacking" lol

Thanks again

[ckeays]

hi buddy i have the same board (also dead) can you please point out the uart port is it the 4pin header near the back of usb 3 and 4.

tried shorting 17-18 but no joy wanted to check if there is any life in the old girl lol

There are four pins beside the ram, above the USB ports.
The square pad is GND, and the other two beside the square pad are TX and RX (I forgot which is which)

I used an USBtoTTL converter to see the results, but I did not fix the flash with this method. (Although I did determine that there was life left in my board)

FYI, the baud rate is 115 200.

To fix it, you have to short the two pins on the nand for as long as it takes until the computer discovers the new device on the USB port.
(be sure to use the OTG USB port when connecting to the PC.)
The OTG port is the one on its own, not the three ports together.

Then install the drivers and load the right image. It works. Once you install the right image, you can then use the SD card method to find the best image.

I managed to install a momentary push switch and mount it in the box to short the two pins so I don't have to solder to the very small pins every time!

Be careful. You can do more damage to the board if you short the wrong pins on the nand!!

I am not always checking my email, but I will respond eventually if someone needs help.

Good luck.

[bigifa]

hi buddy i have the same board (also dead) can you please point out the uart port is it the 4pin header near the back of usb 3 and 4.

tried shorting 17-18 but no joy wanted to check if there is any life in the old girl lol

[ckeays]

one more thing, the mac address has been changed to 00:11:22:33......
i woulld like to restore it somehow through the uart programming method.
If someone knows the address where this data is stored in the nand please let me know!!

The ethernet works well regardless. I actually didn't try the wifi.

Edit: that mac address was in one of the images I loaded. I have since loaded an image from the manufacturer and all is ok.

[ckeays]

OK I finally figured it out after three days!
Your box is not dead!!

I found the way IN using USB Burning Tool v2.0.4.3.

1. First join ALE and WE on the nand (on my nand (H27UCG8T) it's pin 17 & 18).
Look at the picture I posted.
Nothing works for me except that. No toothpick trick, nothing else.

You should trace where these two pins go on the board so it would be easier to solder
(and so you don't render the unit permanently useless).

One of the pins goes to a very small resistor on the side of the NAND and the other pin
goes to a small resistor footprint right beside the pin although there was no resistor installed there.

DO SO AT YOUR OWN RISK!
USE EXTREME CAUTION HERE! I am not responsible if you destroy your hardware!!


2. You need a male to male usb cable on USB PORT 4 (back of the unit)
This is the OTG port on this board. (the one that can be used to program with)

3. YOU DO NOT NEED TO CONNECT POWER in this mode! Power is taken from your usb port on your PC.

4. Once cable is connected to the PC, you should hear the sound when a USB device is discovered on your PC.
If you have installed USB Burning tool, then it will automatically find the driver. I used windows XP with USB 2.0 ports.
I found it wouldn't program unless I disconnected the wire joining the two nand pins once the device was discovered.
You can try leaving the pins shorted, I don't know.

You'll know it's connected because you will see the discovered device in the USB Burning Tool program on one of the ports.

5. Next you can load the image in USB Burning Tool. I suggest you look at a guide on how to use the program especially the part regarding preventing windows from allowing the ports to sleep!

Here is another major problem that I searched for two days and still had to figure out on my own. When loading an image in USB Burning Tool, I got the error message "Parse Burning Image fail".
No matter what image I loaded, this happened. I searched the net and found others with the same problem but no solution. Nowhere does the program mention the image requirements.

The image USB Burning Tool requires is one large , (one file) not the images that are designed for the SD card method.

I did not find the right image for my box but I did find an S85 image that worked (had a few bugs) but it was enough to unbrick my box
so that I could load the correct image using the SD card method afterwards.

Here are the images I used:
http://chinagadgetsreviews.blogspot....at-442_81.html

This one is the one used to revive the box with USB Burning Tool. You can leave this on your box, it worked on mine with a few minor bugs, at least it wasn't bricked!

I loaded this rom afterwards using the SD card method:
http://www.preupload.com/2015/04/hd1...r-ott-mxq.html

it works well so far and I like the design.

So there you have it. This should fix your bricked box.

[Devastator]

I'm also having the same identical problem with an identical board. I've tried everything I can and still no luck. Any help will be appreciated guys.

[ckeays]

Does anybody know the pin names (not number of pin) of the nand chip that need to be shorted in order for the device to be detected on the USB?
(i.e. Read Enable join to Ready/Busy)

[ckeays]

Hi Guys,

I got a new MXQ OTT S805 android box the other day.

I didn't like the stock rom so I decided to change the rom.

I was sure that it was the right one, based on the description in the file I downloaded.
Well long story short, it was not, and now the device is bricked real good.

It does not boot, can't use SD bootcard to restore boot, USB Burning tool doesn't work (PC does
not see the device). I tried everything. (toothpick method)

When unit is powered up, red LED stays ON.

I have been reading a lot the last few days and learning everything I can about this box.

I figured out there is a debug port that spits out a log of the bootup sequence to a terminal
program.

Here is what I got from the log:

Terminal log file
Date: 9/3/2015 - 1:42:26 PM
-----------------------------------------------
QA5:A;SVN:B72;POC:3FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0;
no sdio debug board detected
TE : 24850
BT : 13:49:38 Jan 14 2015
PMU:NONE
##### VDDEE voltage = 0x041a

CPU clock is 792MHz

DDR mode: 32 bit mode
DDR size: 1GB
DDR check: Pass!
DDR clock: 636MHz with 2T mode
DDR pll bypass: Disabled
DDR init use : 13240 us

HHH
ucl decompress...pass
0x12345678
Boot from internal device 1st NAND

TE : 210423

System Started


U-boot(m8b_m201_v1@953b5b96) (Jan 14 2015 - 13:49:29)

clr h-ram
DRAM:  1 GiB
relocation Offset is: 2fecc000
show partition table:
part: 0, name :       logo, size : 2000000
part: 1, name :   recovery, size : 2000000
part: 2, name :       misc, size : 2000000
part: 3, name :       boot, size : 2000000
part: 4, name :     system, size : 40000000
part: 5, name :      cache, size : 20000000
part: 6, name :       data, size : end
aml_card_type=0x100
MMC:   [mmc_register] add mmc dev_num=0, port=1, if_type=6
[mmc_register] add mmc dev_num=1, port=2, if_type=6
SDIO Port B: 0, SDIO Port C: 1
power init
out reg=c110804c,value=dfffffff
IR init done!
register usb cfg[0][1] = 3ff737cc
register usb cfg[2][0] = 3ff76350
NAND:  NAND BOOT: boot_device_flag 1
Nand PHY driver Version: 1.01.001.0003 (c) 2013 Amlogic Inc.
amlnf_phy_init : amlnf init flag 0
NAND device id: ad de 14 a7 42 4a ad de
detect NAND device: E revision 1Ynm NAND 8GiB H27UCG8T2E
AML_NAND_NEW_OOB : new oob
bus_cycle=5, bus_timing=7,system=3.9ns,flash->T_REA =16,flash->T_RHOH=15
hynix nand get default reg value at blk:8, page:2048
NAND CKECK  : arg nbbt: arg_valid= 1, valid_blk_addr = 5, valid_page_addr = 0
NAND CKECK  : arg ncnf: arg_valid= 1, valid_blk_addr = 7, valid_page_addr = 0
NAND CKECK  : arg nkey: arg_valid= 1, valid_blk_addr = 4, valid_page_addr = 0
i=0,register --- nand_key
NAND CKECK  : arg nenv: arg_valid= 1, valid_blk_addr = 9, valid_page_addr = 0
nfboot    : offset: 0x000000000000 -0x000001000000 : partitons 0 : single_chip single_plane
nfcache   : offset: 0x00000d000000 -0x000026000000 : partitons 1 : single_chip multi_plane
nfcode    : offset: 0x000033000000 -0x000052000000 : partitons 5 : single_chip multi_plane
nfdata    : offset: 0x000085000000 -0x00017b000000 : partitons 1 : single_chip multi_plane
bad block count = 0

bad block count = 0

bad block count = 0

bad block count = 0

amlnf_logic_init: START
aml_nftl_start:117,size_in_blk=76,tmp_block=65,part->free_block_num=11
aml_nftl_start:117,size_in_blk=164,tmp_block=145,part->free_block_num=19
amlnf_logic_init:  COMPLETE
get_boot_device_flag: init_ret 0
get_boot_device_flag NAND BOOT:
NAND BOOT,nand_env_relocate_spec : env_relocate_spec 49
uboot env amlnf_env_read : ####
check dts: FDT_ERR_BADMAGIC, load default vpu parameters
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
cvbs trimming.1.v5: 0xa0, 0x0
Hit Enter key to stop autoboot -- :  5  4  3  2  1  0
exit abortboot: 0
Amlogic Ethernet Init
Success: reset mac OK!(0)
ETH PHY hardware reset OK
find net phy id=0x2430c54, phyad=0
set_mac_mode(0)
final_addr[rx-tx]: 0x3ffee000-0x3ffee600
Ethernet reset OK
MAC address is 00:00:00:00:00:00 (changed to all 0's)
phy auto link failed
half duplex
10m
BOOTP broadcast 1
phy auto link failed
phy auto link failed
BOOTP broadcast 2
phy auto link failed
 
-----------------------------------------------
Date: 9/3/2015 - 1:42:53 PM
End log file

Here are some pictures of the board:





I have a USBtoTTL converter connected to the debug port.
I have TXD, RXD, and GND connected.

On another forum I read that
the nand can be reprogrammed from the debug port which would repair the device.
I just don't know what software to use.

I hope someone can shed some light.
I really want to fix this box.

Judging from all the other posts like mine, there are others who have the same problem with this box.

I would really appreciate some ideas/insight/advice.

I will post my results if I get it to work so others can also benefit.
After all, isn't that what these forums are for?


Cheers!