Vu Duo Clone V2 stuck on red light and starting...

[cs4me]

hi guys as the title says my Vu Duo Clone V2 is unfortunately stuck on red light and the LCD is showing "starting...". I have tried disconnecting the hard drive, but this hasn't made a difference. I know some people without thinking have tried to flash with a v3 image, hence bricking their box, so I thought I best ask what I should do.

How can I fix this? Do I simply reflash it with a v2 image? If so, is there a guide that I can follow?

Thanks.

[brione]

hi guys as the title says my Vu Duo Clone V2 is unfortunately stuck on red light and the LCD is showing "starting...". I have tried disconnecting the hard drive, but this hasn't made a difference. I know some people without thinking have tried to flash with a v3 image, hence bricking their box, so I thought I best ask what I should do.

How can I fix this? Do I simply reflash it with a v2 image? If so, is there a guide that I can follow?

Thanks.

JUst put a v2 image on a fat formated usb stick. Put it in the front usb port and switch box off and on. It should then work as you wish. Just wait till box tells you to reboot.

Putting a v3 image on a v2 box wont brick it just gets stuck on starting. If you were to flash box with a v3 chip patch that would brick it.

Cheers

[cs4me]

thanks for your reply brione. I have tried to flash this way on a fat32 usb stick (64gb). When I insert usb and switch box on, there is absolutely no activity from the usb...i.e. the box is not reading the usb stick. Could you please point me to a ready to go v2 image?

Also what is the file/directory layout on the usb stick?

[brione]

I will pm you

[geeman028]

I will pm you

Don't suppose you could PM me with info as mine is in a similar state.
Thanks.

[brione]

See you got it sorted according to another forum.

[the goat]

I get the red light starting on my vu+ dou v2, on most images, don't know why but I can only get 1 image to run vu, and pick up all the satelittes correctly
its a version of BH 1.7.5
I have pm you a link,
took me days to get my one to work, changing images and playing with dish

[smokey_jnr]

hi mate,

i have the same issue how do i tell if i have v2 or v3..?

[cs4me]

unfortunately mine still does not detect the usb stick(s) at the front. I'm sure a while ago I saw an rs232 method for duo v2 box, but I can't seem to find it.

@ smokey_jnr - look for a white sticker which is usually at the back of the box. It should simply say v2 or v3.

[manfred368]

unfortunately mine still does not detect the usb stick(s) at the front. I'm sure a while ago I saw an rs232 method for duo v2 box, but I can't seem to find it.

@ smokey_jnr - look for a white sticker which is usually at the back of the box. It should simply say v2 or v3.

try different make usb stick formatted to fat, some usb sticks are not detected by receiver

[cs4me]

no mate, i've got a more major issue....I managed to successfully flash the vu duo using DUO.BIN and the UPDATEALLFLASH utility. Unfortunately I still cannot use a usb stick to flash. I ran Hyperterminal and have the following log to show you:-

BCM73350010
012
BCM73350010
012
Shmoo Version=1.9

MEMC-00000000 RW=00000010 WW=00000047 G=00000001 R=00000008 W=0000001B
MEMC-00000001 RW=00000010 WW=00000051 G=00000001 R=00000009 W=00000004 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Wed Dec 9 17:23:18 2009 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd
!!!!! UNC read error occurred, while reading from NAND flash

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tec
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
**Exception 32: EPC=8701D8E8, Cause=0000801C, VAddr=00000000
RA=8701DB28, PRID=0002A044

0 ($00) = 00000000 AT ($01) = B0480000
v0 ($02) = 00000000 v1 ($03) = 87020000
a0 ($04) = B0480400 a1 ($05) = 87040000
a2 ($06) = B0480390 a3 ($07) = 00000000
t0 ($08) = 00000043 t1 ($09) = 00000055
t2 ($10) = 00000046 t3 ($11) = 8706957
t4 ($12) = 00000001 t5 ($13) = 870470E8
t6 ($14) = 00000000 t7 ($15) = 07600000
s0 ($16) = 8701D8CC s1 ($17) = B0480400
s2 ($18) = 8700A4B8 s3 ($19) = 38C00000
s4 ($20) = 00008000 s5 ($21) = 00000040
s6 ($22) = 00010000 s7 ($23) = 00000040
t8 ($24) = 00000000 t9 ($25) = 870471F4
k0 ($26) = 00000000 k1 ($27) = 00000000
gp ($28) = 8704E210 sp ($29) = 87148768
fp ($30) = BFC00AA0 ra ($31) = 8701DB


*** Waiting for system reset ***

BCM73350010
012
BCM73350010
012
Shmoo Version=1.9

MEMC-00000000 RW=00000010 WW=00000048 G=00000001 R=00000008 W=0000001C
MEMC-00000001 RW=00000010 WW=00000051 G=00000001 R=00000009 W=00000004 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Wed Dec 9 17:23:18 2009 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd
!!!!! UNC read error occurred, while reading from NAND flash

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
**Exception 32: EPC=8701D8E8, Cause=0000801C, VAddr=00000000
RA=8701DB28, PRID=0002A044

0 ($00) = 00000000 AT ($01) = B0480000
v0 ($02) = 00000000 v1 ($03) = 87020000
a0 ($04) = B0480400 a1 ($05) = 87040000
a2 ($06) = B0480390 a3 ($07) = 00000000
t0 ($08) = 00000043 t1 ($09) = 00000055
t2 ($10) = 00000046 t3 ($11) = 87069570
t4 ($12) = 00000001 t5 ($13) = 870470E8
t6 ($14) = 00000000 t7 ($15) = 07600000
s0 ($16) = 8701D8CC s1 ($17) = B0480400
s2 ($18) = 8700A4B8 s3 ($19) = 38C00000
s4 ($20) = 00008000 s5 ($21) = 00000040
s6 ($22) = 00010000 s7 ($23) = 00000040
t8 ($24) = 00000000 t9 ($25) = 870471F4
k0 ($26) = 00000000 k1 ($27) = 00000000
gp ($28) = 8704E210 sp ($29) = 871487
fp ($30) = BFC00AA0 ra ($31) = 8701DB28


*** Waiting for system reset ***

[zwarder]

I have this issue with a V3 box yet it will flash from usb but all i get is kernel panic.

I have tried updating security chip to v3.2 but it will not do it. The kernel flashes ok.

Maybe faulty security chip?

[zwarder]

For your info I replaced the security chip & have now sucessfully updated to v3.2 & the vu duo is booting however the hdmi & ethernet sockets do not work
Everything else is fine