DroidTV MX Linux XBMC Release Candidate 2 has been released!

Alpha release of the Buildroot Linux XBMC for DroidTV MX and Tronsmart Prometheus

Updated XBMC release for DroidTV MX & M3


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
My DoidTV MX has BRICK! :(
05-12-2013, 03:39 AM
Post: #11
Not Solved RE: My DoidTV MX has BRICK! :(
I got the files thank you ,i had to order a usb to ttl cable what i don't have so the procedure got to wait Sad but i am doing the G -box midnight now i will let you know how went
Thanks
Find all posts by this user
Quote this message in a reply
05-12-2013, 07:04 AM
Post: #12
Not Solved RE: My DoidTV MX has BRICK! :(
I tried the method unfortunately the same behavior blank screen no logo popping up i even vent to the extreme holding the reset button for 10 ten minutes :0 how stupid that sounds Smilei did try several files from the g-box midnight site ,anyway thanks for your effort but i think the g box midnight chip is m3 platform and this one is mx platform so that may be the reason
Thank you
Find all posts by this user
Quote this message in a reply
05-19-2013, 04:41 AM
Post: #13
Not Solved RE: My DoidTV MX has BRICK! :(
Hello,

I'm already irritated.

We need recovery method to manufactured state of DroidTV MX.
We have bricked DroidTV MX.
We have USB-Burning-Tool for Amlogic.
We know how connect our DroidTV MX to PC.
USB-Burning-Tool see our players via USB.

BUT. We no have good firmware to flash our nand!!!
Whats wrong.
I do not want to send my DroidTV to the factory.
It's too expensive.
I can flash my player alone in the house.
Need just the right firmware!
Please help!

Greetings
Find all posts by this user
Quote this message in a reply
05-19-2013, 08:22 AM
Post: #14
Not Solved RE: My DoidTV MX has BRICK! :(
Well if you find a way to do it count me in i have exactly the same problem as you saw from my posts!I am waiting for the usb to ttl cable to try that method but i don't put my hopes up because the lack of recovery software for the MX !
Find all posts by this user
Quote this message in a reply
05-19-2013, 09:27 AM
Post: #15
Not Solved RE: My DoidTV MX has BRICK! :(
Is it not possible to dump the entire nand of a good box via ttl and flash it? Is it protected?
Find all posts by this user
Quote this message in a reply
05-19-2013, 10:27 AM
Post: #16
Not Solved RE: My DoidTV MX has BRICK! :(
Guys, the M3 recovery won't work for the MX. it has different SoC.
I have already requested the recovery SD card from the MX manufacturer, but they still have not replied. Will ping them on Monday once again.
I have unsuccessfully tried to prepare the recovery SD card for the MX box using the M3 recovery SD card , but maybe I couldn't flash this, because my MX box wasn't bricked?
The recovery image was created using bootable SD card, thus I guess that if you flash it to the SD card, and then replace the old files with the new ones it should work for MX box.
Any way, if you want to give a try, the procedure should be straight forward:
  • extract the M3 recovery image using HDD Raw copy to the SD Card
  • you will get these files: f16ref-ota-eng.ubuntu.zip,factory_update_param.aml,uboot-wyst-a11.bin,uImage_recovery
  • download and extract latest firmware for the DroidTV MX 2013 04 19
  • copy the content of the extracted MX firmware to the newly created M3 recovery SD Card
  • turn off your device, insert the SD card and try to call the recovery console by holding the hidden reset button.

Let me know if that worked for you.

We are here to help you. AndroidGadget UK
Find all posts by this user
Quote this message in a reply
05-19-2013, 10:40 AM
Post: #17
Not Solved RE: My DoidTV MX has BRICK! :(
Androidgadget11 might I ask how you are connecting the Droid MX to your computer? What kind of cable are you using?

Thanks,

iamwally
Find all posts by this user
Quote this message in a reply
05-19-2013, 10:45 AM
Post: #18
Not Solved RE: My DoidTV MX has BRICK! :(
(05-19-2013 04:41 AM)androidgadget11 Wrote:  Hello,

I'm already irritated.

We need recovery method to manufactured state of DroidTV MX.
We have bricked DroidTV MX.
We have USB-Burning-Tool for Amlogic.
We know how connect our DroidTV MX to PC.
USB-Burning-Tool see our players via USB.

BUT. We no have good firmware to flash our nand!!!
Whats wrong.
I do not want to send my DroidTV to the factory.
It's too expensive.
I can flash my player alone in the house.
Need just the right firmware!
Please help!

Greetings

I just wonder how are you going to connect the TTL cable to the MX box?

We are here to help you. AndroidGadget UK
Find all posts by this user
Quote this message in a reply
05-19-2013, 01:42 PM
Post: #19
Not Solved RE: My DoidTV MX has BRICK! :(
I have hooked up my Droid MX and have added some more info to the pic I posted earlier in this thread.

[Image: GBox_Midnight_MX2_Zoom_SPI.jpg]

Here is the capture of boot process from Power on to the Uboot Command Prompt

wait pll-0x03 target is 0204 now it is 0x00000203

DDR clock is 516MHz with 1T mode

DX0DLLCR:40000000
DX0DQTR:ffffffff
DX0DQSTR:3db05001
DX1DLLCR:40000000
DX1DQTR:ffffffff
DX1DQSTR:3db05001
DX2DLLCR:40000000
DX2DQTR:ffffffff
DX2DQSTR:3db05001
DX3DLLCR:40000000
DX3DQTR:ffffffff
DX3DQSTR:3db05001
Stage 00 Result 00000000
Stage 01 Result 00000000
Stage 02 Result 00000000
Stage 03 Result 00000000
HHH
pages_in_block=0x00000100
0x12345678
Boot from internal device 1st NAND RB

System Started



U-boot(m6_mbx_v1@4dafb4dc) (May 11 2013 - 17:19:19)

aml_rtc_init
aml rtc init first time!
Clear HDMI KSV RAM
DRAM: 1 GiB
relocation Offset is: 10604000
NAND: Amlogic nand flash uboot driver, Version U1.05.016 © 2010 Amlogic Inc.
No NAND device found!!!
NAND device id: 2c 88 4 4b a9 0
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron C revision NAND 8GiB M T29F64G-C)
#####aml_nand_init, with RB pins and chip->chip_delay:20
bus_cycle=5, bus_timing=6, start_cycle=6, end_cycle=7,system=5.0ns
oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mo de: NAND_BCH30_1K_MODE
aml_chip->oob_fill_cnt =0,aml_chip->oob_size =448,bch_bytes =54
Creating 1 MTD partitions on "nandboot":
0x000000000000-0x000000800000 : "nandboot"
nandboot initialized ok
No NAND device found!!!
NAND device id: 2c 88 4 4b a9 0
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x2c (Micron C revision NAND 8GiB M T29F64G-C)
1 NAND chips detected
#####aml_nand_init, with RB pins and chip->chip_delay:20
bus_cycle=5, bus_timing=6, start_cycle=6, end_cycle=7,system=5.0ns
oob size is not enough for selected bch mode: NAND_BCH60_1K_MODE force bch to mo de: NAND_BCH30_1K_MODE
aml_chip->oob_fill_cnt =0,aml_chip->oob_size =448,bch_bytes =54
aml_nand_init:oobmul =2,chip->ecc.layout->oobfree[0].length=32,aml_chip->oob_siz e=448
aml nand env valid addr: 978000
NAND bbt detect factory Bad block at b400000
Creating 9 MTD partitions on "nandnormal":
0x000001000000-0x000001400000 : "ubootenv"
0x000001400000-0x000001c00000 : "logo"
0x000001c00000-0x000002400000 : "aml_logo"
0x000002400000-0x000002c00000 : "recovery"
0x000002c00000-0x000003400000 : "boot"
0x000003400000-0x000043800000 : "system"
NAND bbt detect factory Bad block at b400000
0x000043800000-0x000063800000 : "cache"
0x000063800000-0x000073800000 : "backup"
0x000073800000-0x000200000000 : "userdata"
nandnormal initialized ok
MMC: SDIO Port B: 0
In: serial
Out: serial
Err: serial
aml_i2c_init
register usb cfg[0] = 9fe89aa4
Net: Meson_Ethernet
init suspend firmware done. (ret:0)
reboot_mode=charging
SARADC open channel(4).
Hit any key to stop autoboot: 0
m6_mbx_v1#
m6_mbx_v1#
m6_mbx_v1#

This Command line is where we type the commands need to copy the boot image back to the NAND to unbrick. We just need to figure out exactly which boot.bin to write to it and to what offsets to write it to. It must be almost exactly like the process I have outlined for my Wepower Mediabox MX as it is the same dual core chipset. Those with brick hang tight we are almost there!

Evgeniy it would be easier and less risky with info from manufacturer but we may not need it.

Speedlaci did you ever get your usb to ttl cable? If you did then let me know and I might have a process to try but you will need to attach ttl end of cable to MX board. You can either solder direct or I would suggest cutting a chip socket in half and soldering that to the board so you can insert the bare wires from ttl cable into it and remove them easily when done till the next time you need to use it or hopefully never again but in case. Like this:

[Image: MX_SPI_Connection_1.jpg]

[Image: MX_SPI_Connection_2.jpg]

Thanks,

iamwally
Find all posts by this user
Quote this message in a reply
05-20-2013, 04:03 AM
Post: #20
Not Solved Wink RE: My DoidTV MX has BRICK! :(
Hi Iamwally
Thanks for the pictures ,no i didn't get the cable yet i am waiting patiently ,i had exactly the same idea you suggesting with the socket pins to solder them permanently so i don't have to worry removing them after the procedure ,don't forget before all this Android crazy we use to screw around with free to air receivers and i did brick couple of them and back to life (if worked Smile )was almost the same idea ,thanks for the suggestion though Smile
Sure i will let everybody know here if i can make it work ,and as you sad the right boot.bin will probably make it easy on us.
The cable is from Ebay so i might have to wait few weeks
Thanks
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)