I´ve tried to flash a new firmware on my tx3 pro tv box. After the update the box doesn´t start only the red led is burning. Is it bricked now and what can I do to unbrick it?
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
TX3 pro bricked
Collapse
X
-
I flash an image on mine, now i can't use usb burning tool. Seems to be broken "download mode" (like in smartphones). Every time i try to start pressing reset button i can't reach the screen that i can use usb burning tool. Usb burning tool recognize for a few seconds, so the device continue to boot an start the os.
Comment
-
Thank you! Worked!
Since the first day bluetooth (on stock firmware) not work, no matter firmware i flash, i try a lot of those firmware for p212 boards, none worked. Maybe the board lack of bluetooth chip? Mine is not TX3 exactly, but the board is the same layout of TX3 Pro and TX5 non pro.
Comment
-
I had another problem. I updated my tv box with the sd card and after the update the box rebooted, but I got a black screen and glowing red led. It did not turned on or responded to the remote. The computer also did not recognize it. I opened the tv box, short two contacts of the flash memory (i don´t remember which ones exactly that were), connected it to the computer and it worked. I updated the tv box with USB Burning Tool and took this firmware https://drive.google.com/file/d/1v2w...w?usp=drivesdk, because I have NANYA DDR. To find out what ddr you have, you can open the tv box or check the serial number. When the serial number include the letters NY, than you have NANYA DDR.
Last edited by besik; 09 May 2020, 06:55.
Comment
-
I always getting error when download UBOOT.
[17:04:18 186][HUB2-4][Inf]-------------Download UBOOT.USB-----------
[17:04:18 187][HUB2-4][Inf]--2-2-0-0
[17:04:18 187][HUB2-4][Inf]--ulValue = 0xadfc318c
[17:04:18 187][HUB2-4][Inf]--Download DDR.USB buffer at 0xd9000000
[17:04:18 200][HUB2-4][Inf]--Transfer complete
[17:04:18 200][HUB2-4][Inf]--Download UBOOT.USB buffer at 0x0200c000
[17:04:18 408][HUB2-4][Inf]--Transfer complete
[17:04:18 413][HUB2-4][Inf]--DownCheckPara succeed
[17:04:18 413][HUB2-4][Inf]--Run at address 0xd9000000
[17:04:18 457][HUB2-4][Err]--generatedAddSum:0x9a08fe06;srcAddSum:0xf32140ea;ru nResult:0x e6;paraMagic:0x7856efab
[17:04:18 457][HUB2-4][Inf]--ReadCheckPara failed
[17:04:18 538][HUB2-4][Err]--[0x19080902]Unknown
Or
[17:06:08 058][HUB2-4][Inf]-------------Download UBOOT.USB-----------
[17:06:08 060][HUB2-4][Inf]--2-2-0-0
[17:06:08 060][HUB2-4][Inf]--ulValue = 0xadfc318c
[17:06:08 060][HUB2-4][Inf]--Download DDR.USB buffer at 0xd9000000
[17:06:08 069][HUB2-4][Inf]--Transfer complete
[17:06:08 069][HUB2-4][Inf]--DownRunPara succeed
[17:06:08 069][HUB2-4][Inf]--Run at address 0xd9000000
[17:06:18 705][HUB2-4][Inf]--Detect Device remove timeout
[17:06:18 705][HUB2-4][Inf]--Device is connected
[17:06:18 705][HUB2-4][Inf]--Close device handle 0x00000408
[17:06:18 756][HUB2-4][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&223ddea8&0&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x000004bc
[17:06:23 812][HUB2-4][Inf]--2-2-0-0
[17:06:23 812][HUB2-4][Err]--CheckFileRunState failed
[17:06:23 812][HUB2-4][Inf]--Failure : 1, FailureMax : 3
[17:06:24 313][HUB2-4][Err]--[17:06:24 313][HUB2-4][Inf]--Failure : 2, FailureMax : 3
[17:06:24 817][HUB2-4][Err]--[17:06:24 817][HUB2-4][Inf]--Failure : 3, FailureMax : 3
[17:06:24 893][HUB2-4][Err]--[0x10303004]Romcode/Switch status/Identify/Error result
[17:06:24 893][HUB2-4][Inf]--Close device handle 0x000004bc
I still cannot turn the led blue.
Comment
-
herizo Does anybody know the number of pin of the nand chip that need to be shorted in order for the device to be detected on the USB?
Short pin 29 and 30.
besik. Thanks a lot for this info and pic but the red circle you showed is incorrect. need to short pin 29 and 30 ie I/O0 , I/O1. Tried it personally. Connect success on burning tool but the img file is giving parsing error.
Comment
-
Originally posted by abrar11 View Postherizo Does anybody know the number of pin of the nand chip that need to be shorted in order for the device to be detected on the USB?
Short pin 29 and 30.
besik. Thanks a lot for this info and pic but the red circle you showed is incorrect. need to short pin 29 and 30 ie I/O0 , I/O1. Tried it personally. Connect success on burning tool but the img file is giving parsing error.You may only view thumbnails in this gallery. This gallery has 1 photos.1 Photo
Comment
What's Going On
Collapse
There are currently 1965 users online. 0 members and 1965 guests.
Most users ever online was 37,478 at 04:14 on 26 June 2024.
Comment