hep with missed up flash for vu+ solo

aminechadli

Vu+ Newbie
i tried to upadate from 1.6.3 to 1.6.6
i followed a txt file and understood wrong the need to update the bootloader et used the bootloader for vu+ duo to flash my vu+ solo bootloader.
and now my solo is dead
i cant update trough usb, i tried also com port and nothing came out
the is only a red led in the front
best regards
 

a911

The BH Lover
i tried to upadate from 1.6.3 to 1.6.6
i followed a txt file and understood wrong the need to update the bootloader et used the bootloader for vu+ duo to flash my vu+ solo bootloader.
and now my solo is dead
i cant update trough usb, i tried also com port and nothing came out
the is only a red led in the front
best regards

Read about dead Vu+...here @ this thread!
http://www.vuplus-community.net/board/threads/vu-duo-is-dead.3616/page-2#post-30544
U may find few tips how to revive U'r Box!

RgdZ
a911
 

angelofsky1980

BlackHole Driver Specialist
i tried to upadate from 1.6.3 to 1.6.6
i followed a txt file and understood wrong the need to update the bootloader et used the bootloader for vu+ duo to flash my vu+ solo bootloader.
and now my solo is dead
i cant update trough usb, i tried also com port and nothing came out
the is only a red led in the front
best regards
You have bricked your box.
Duo updates are only for Duo, otherwise if the bootloader update was designed for any Vu+ box, this info was be published.
Contact your reseller to try to replace your box in warranty or repair the one you have.
 

aminechadli

Vu+ Newbie
You have bricked your box.
Duo updates are only for Duo, otherwise if the bootloader update was designed for any Vu+ box, this info was be published.
Contact your reseller to try to replace your box in warranty or repair the one you have.
mine is out of warranty
how can i repair it
is there any tuto to revive it
 

angelofsky1980

BlackHole Driver Specialist
mine is out of warranty
how can i repair it
is there any tuto to revive it
Your last chance is to write directly to Vu+ and ask a quotation about replacement part (mainboard).
Tutorials about recovery? Doesen't exist. You have deleted the BIOS of your box. The box doesen't know what they do when start.
 

jey18

Vu+ Newbie
I have the same problem here. I tried a Bootloader update on my vu+ duo. And now boot sequence stop before CFE. I will try to DUMP nand rom direct on chip and compare with the *.bin file.
It looks like the bootloader is on a K9f4g08u0c nand flash. When i will find time, i will solder wires on this chip and try something with a nand reader/writer.
If someone already tried this, or if someone has info about memory map of the rom. You are welcome to share... :)
 

angelofsky1980

BlackHole Driver Specialist
I have the same problem here. I tried a Bootloader update on my vu+ duo. And now boot sequence stop before CFE. I will try to DUMP nand rom direct on chip and compare with the *.bin file.
It looks like the bootloader is on a K9f4g08u0c nand flash. When i will find time, i will solder wires on this chip and try something with a nand reader/writer.
If someone already tried this, or if someone has info about memory map of the rom. You are welcome to share... :)
Please explain better what operation you have done.... Vu+Duo CFE upgrade on Duo box is safe. Is not ver safe (and desctructive!) if you flash CFE for Duno on other boxes like Solo or Uno.

You can also try (before remove the NAND) to find a JTAG connector on mainboard and verify if there is the possibility to interface the nand.
If you obtain some infos via JTAG, we can study toghether a solution.
My Duo and it's CFE works correctly and I can make a working dump of it to reflash as needed if you can write it to nand.
 

jey18

Vu+ Newbie
I know it should be safe. Maybe the problem is i forgot that i already did the 3.0 update of my bootloader.
I didn't find anything like JTAG connectors on the mainboard, and i don't know who i can ask to know it.
I connect a rs232 cable to spy boot process, and it stop just before CFE.
BCM73350010 012 Shmoo Version=1.9 MEMC-00000000 RW=00000010 WW=0000004F G=00000001 R=00000008 W=00000013 MEMC-00000001 RW=00000010 WW=00000051 G=00000001 R=00000009 W=00000006 #$ 3 COPY CODE A567

If you could make a real HEX dump of your rom, that could be really nice.
 

angelofsky1980

BlackHole Driver Specialist
I know it should be safe. Maybe the problem is i forgot that i already did the 3.0 update of my bootloader.
I didn't find anything like JTAG connectors on the mainboard, and i don't know who i can ask to know it.
I connect a rs232 cable to spy boot process, and it stop just before CFE.
BCM73350010 012 Shmoo Version=1.9 MEMC-00000000 RW=00000010 WW=0000004F G=00000001 R=00000008 W=00000013 MEMC-00000001 RW=00000010 WW=00000051 G=00000001 R=00000009 W=00000006 #$ 3 COPY CODE A567

If you could make a real HEX dump of your rom, that could be really nice.

A full NAND Backup? I can try ....
 
Top