Vu solo4k not bootable

Have you tried a different pen drive?
Your options are about limited to returning the receiver for warranty at this point.
 
Try disconnecting everything, including the LNB's, and internal hard drive, if you have one fitted, then try flashing the black hole image.
Did the other image load correctly, and work, or did this start the problem?
Do you get anything displayed, on your television, when you press the menu button?
 
Mick12334 said:
Try disconnecting everything, including the LNB's, and internal hard drive, if you have one fitted, then try flashing the black hole image.
Did the other image load correctly, and work, or did this start the problem?
Do you get anything displayed, on your television, when you press the menu button?
Click to expand...

I had disconnected everything and did try to flash with different pen drive and different images.. but it still does not recover.
 
Try loading the original image, from vuplus:
Code: 
http://code.vuplus.com/
Ensure you have deleted, or moved, any other vuplus folders, containing any previous images.

Have you had the receiver working?
Did it work after loading the opendroid-5.5 image?
Does anything happen when you press the menu button?
 
Mick12334 said:
Try loading the original image, from vuplus:
Code: 
http://code.vuplus.com/
Ensure you have deleted, or moved, any other vuplus folders, containing any previous images.

Have you had the receiver working?
Did it work after loading the opendroid-5.5 image?
Does anything happen when you press the menu button?
Click to expand...

yes, In the past it has worked for almost 4 months.. then since the last two days something went wrong.. so I had reflashed it with a lastest image of BH but nothing is happening.

So then i tried different images but still the same problem until when i try to use the opendroid 5.5. I can ping the device and so can I ftp and ssh to the device and that is all i can do. I still can not recover fully. Nothing is displayed on the OSD or the tv screen as i have mentioned before.

I want to know how to wipe the storage manually and then try to flash with a fresh image ? is it possible even ?
 
Don't even try, it's still under warranty so return it to your supplier.
I did notice that you had it seated on a DVD player, and didn't seem to have any blocks, under each corner, to allow full ventilation, so I don't know if over heating might have caused a problem.
 
Mick12334 said:
Don't even try, it's still under warranty so return it to your supplier.
I did notice that you had it seated on a DVD player, and didn't seem to have any blocks, under each corner, to allow full ventilation, so I don't know if over heating might have caused a problem.
Click to expand...

I hardly use the dvd player.. It is a mental box and there is a few cm gap between the vu and the dvd so it should be ok. it is open from the top for ventilation.
 
After taking a look at the video, it seems that the process updating rootfs is taking too short time and should take longer.
I would try another different 2GB USB stick 2.0.
Good Luck.
 
Wendy said:
After taking a look at the video, it seems that the process updating rootfs is taking too short time and should take longer.
I would try another different 2GB USB stick 2.0.
Good Luck.
Click to expand...

I have tried with different stick that i have from 8 / 16 USB 2 and 32 / 64 USB 3... I had used the 64 USB 3 from ADATA and it was working fine. still no luck..
 
On your video, the time it takes during the process rootfs is about 8 seconds only whereas on a youtube film that I have just seen, the same process takes about 1 min 45 sec. That's why I thought that it must be a suitably formatted usb stick that you need.
 
I guess only replacing the box is the solution.. I am surprised that VU did not create a special recover firmware to help resolve a boot failure or image corruption issues. Normally it is just linux OS running and now only a developer can help to recover this situation
 
Boot failures do not happen often. Your box boots, but is hanging for some reason. A total boot failure would not do this. Information on how to fix may or may not be in the rs232 information. It is possible that something is damaged, and would not be fixable with software.

IMO, the box is in warranty and should be returned.
 
Hi,

Finally received my box.. I was told that there was no hardware issue and vu+ repaired the software. I am trying to understand what was the issue and how were they able to fix this.

Regards,
 
As mentioned earlier, on the back of your receiver, there is a rj11 connector that contains a serial port . This port may also be referred to as a rs232. You can connect the receiver to a computer and use that port to see what is happening. I would guess that is what the repair shop did.
 
yes I know about that.. what is more interested is how did they fix it.. It will helpful if VU+ can provide us with a procedure to recover this.. if they have used any tools ? It would be very useful for a a future reference.

I have also prepared the console cable using RJ12.. during the time when i was troubleshooting. It goes work with serial null modem cable and putty.

RS232 RJ12

Pin 2 -white PIN 1 -white

PIN 3 - Black PIN 2 - Black

PIN 5 - Yellow PIN 5 - Yellow

Here is the small dump for this console output...

CPU 01
BCM73660020
PRID73760020
v9.99
RR:00000003
BFW
seclib-1.5
BBL v1.0.1
AVS init...
spare0/rmon_hz=01807672
spare1/rmon_vt=01807673
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 2a002b00
AVS load_code offset =00051000
LOADED
I2C @ f040a280.
BID: no ack!

single board
MEMSYS-STD
SHMOO 01010107 BLD:9286 HW:hpf0_b1p4 V:1.1.1.7
MCB: FLEX
AVS start:status=000000ff
STB: Current voltage=0000037d(893)
temperature=00009a09(39433)
PV=0000035b(859)
MV=0000037d(893)
AVS FW rev=30333078 [0.3.0.x]
OK
DDR0: !@ ffe0e780 <= ffe0dfc4 MEMSYS-0 @ f0500000 OK
DDR1: =@ ffe0e780 <= ffe0dfc4 MEMSYS-1 @ f0900000 OK
Sdram Scramble OTP = 0x00000001
Sdram Scramble OK
select_image: addr_offset: 00020000 part_offset: 00000000 bootStatus: 1b05252b
BFW load mode OTP = 0x0000000f
bfw_hash_locked = 0x00000000
BFW key3 OK, BFW load OK
BFW v2.1.0
COPY CODE... DONE
MICH: disable success
SSBL
PINMUX
CACHE FLUSH OK
MMU ON
CACHE FLUSH OK
_fbss 070771b0
_ebss 0708ec18
_end 0708ec38
HEAP @ 07100000
STACK @ 09200000
ARCH: CONFIG OK
CLR BSS 070771b0 to 0708ec18 OK
CLR SRAM OK
MARK XN: 07100000 to 09200000 size 02100000 OK
CACHE FLUSH OK
CPU CLKSET OK
GO!
 
You must log in or register to reply here.
Back
Top