20 replies to this topic

[ksada2]

Hi guys

I decided to flash the latest nightly build on my VU+ Solo2 this afternoon, unfortunately it fails to boot properly since then

 

So I flashed yesterday's image, and the one from 2015/04/27, nevertheless I cannot get my box to work any more.

 

I have taken a photo of the green screen so I'll attach that here.

 

Please could someone help me out?

 

Thanks in advance.

 

Attached Files

•  IMG_20150505_175150.jpg   108.7KB   8 downloads

[ims]

could you post whole crashlog ?

[Frenske]

In case you have a back-up on harddisk, my suggestion would be to rename the backup directory, if possible. I assume you still can login with putty and do a telnet session.

[ksada2]

could you post whole crashlog ?

No, sorry, I can't retrieve it.

 

In case you have a back-up on harddisk, my suggestion would be to rename the backup directory, if possible. I assume you still can login with putty and do a telnet session.

 

I can mount the system in windows explorer, and see the Harddisk, but the only visible contents is an XMBC folder, I hope all my recordings haven't gone. I can telnet to it, and I do have a backup on the hdd, but if I navigate using putty to the hdd and type ls it shows only the xbmc folder.

I am not particularly good on unix commands either to be honest, but I can google things if you guide me a bit.

 

If it's any help, the box reboots after the green screen and stops at the splashscreen with the tree and all it says is "CPU Last 0.37"

[ksada2]

I just noticed another curious thing, the OpenWeb interface works, and it shows all my bouquets and settings, which ought to have been wiped during the flash.

[ksada2]

Actually, I'm talking rubbish here. 

I mixed up the IP address and connected to the old DM800 that I've plugged in as an emergency.

I cannot connect to the Vu+ box, it doesn't seem to be in the network.

[Frenske]

As you talked rubbish before we'll try a second time.
If you run explorer and type \\vusolo2 instead of the present directory, you should see the directory tree of the solo2. Then choose de harddisk and delete or rename the directory named 'backup'. I'm certain that there is a backup present on the harddisk or on the USBstick. Check both locations.

[ksada2]

Thanks Frenske.

Nope, there's no connection to the receiver unfortunately. My modem confirms that it isn't picking up an IP address.

If it's definitely caused by a backup on the HDD all I can do is open up the box and temporarily disconnect it. 

I'd like to understand why having a backup on the HDD causes imaging to fail though. Is it a bad idea to run backups?

[Frenske]

In case you made a backup from an image that has been changed at so many details, like a specific skin that isn't compatible with the present image, that could cause the loop. So disconnect the harddisk and flash the box again.

[Pr2]

When will OpenPLi prompt to ask to user if they want to restore backup or not this problem won't happens anymore since people can reflash and decide to not restore old stuff...

[ims]

You can do it ... It is challenge for you...

[ksada2]

In case you made a backup from an image that has been changed at so many details, like a specific skin that isn't compatible with the present image, that could cause the loop. So disconnect the harddisk and flash the box again.

Well, I disconnected the HDD this evening, and reflashed it with today's image. It now boots as far as the splashscreen, shows a blank green screen, goes back to the splashscreen and green screens again, repeat ad infinitum

I did read on the Build Status page that images newer than April 15 are a problem for a specific receiver, is it possible that this image is also faulty? Should I install an April 14 image and where can I find that?

Edited by ksada2, 6 May 2015 - 19:39.

[Frenske]

Another thought that crossed my mind. Are you 100% shure you bought an original VU+ Solo2. If the outside of the Solo2 is as good as a Solo clone, it could be that you have been hustled. It wouldn't be the first time.

Recently I was confronted with a VU+ solo. I was asked to renew the firmware. It took me several hours as the owner assured me it was an original, so I kept looking for a solution to flash a genuine OpenPLi image. Later that day I flashed a 'based on Pli image' which worked immediately.

And concerning to flash a special image. No need to do so.

[ksada2]

Another thought that crossed my mind. Are you 100% shure you bought an original VU+ Solo2. If the outside of the Solo2 is as good as a Solo clone, it could be that you have been hustled. It wouldn't be the first time.

Recently I was confronted with a VU+ solo. I was asked to renew the firmware. It took me several hours as the owner assured me it was an original, so I kept looking for a solution to flash a genuine OpenPLi image. Later that day I flashed a 'based on Pli image' which worked immediately.

And concerning to flash a special image. No need to do so.

 

 

As far as I'm aware it's a genuine box. It wasn't super cheap or anything. I don't know if I'm allowed to share the name of the vendor here so I'll PM that to you.

[Frenske]

Hi just read this posting on another board.

Exclamation Warning to anyone buying a VU+ Solo2, clones being sold as genuine at genuine prices
As the title, we're posting this to warn members and anyone thinking of buying a VU+ Solo2.

Theres some dealers who have sold genuine units in the past selling counterfeit clone VU+ Solo2 on ebay claiming that they are genuine and selling them close to genuine prices.

Beware where you purchase if you choose not to order from us.

[Erik Slagter]

Looks like a custimised skin setting and the skin can't be found (backup) or drivers that won't load (clone detection).

 

To know any further, it's absolutely essential to login to the receiver with telnet (putty/dcc/etc.) which very probably just works and then type a few commands for us.

[ksada2]

Looks like a custimised skin setting and the skin can't be found (backup) or drivers that won't load (clone detection).

 

To know any further, it's absolutely essential to login to the receiver with telnet (putty/dcc/etc.) which very probably just works and then type a few commands for us.

Time for an update!

As you know I tried flashing it without the HDD connected so that it couldn't try to restore any settings, and even then it greenscreened and got stuck in a booting loop.

I phoned the dealer and they asked me to send it back to them for a software update, so I thought I'd try a different image before sending it away. I found the BH 2.1.5 image and tried it, and low and behold it installed and it works!

I haven't tried PLI again since, I don't dare, but I can now access to the HDD and upload the crashlogs, there are hundreds of them.

 

Attached Files

•  enigma2_crash_107.log   16.98KB   9 downloads
•  enigma2_crash_26.log   16.98KB   8 downloads

[janejak]

i think u have to try another skin

 

Traceback (most recent call last):
  File "/usr/lib/enigma2/python/mytest.py", line 569, in <module>
    runScreenTest()
  File "/usr/lib/enigma2/python/mytest.py", line 459, in runScreenTest
    runNextScreen(session, screensToRun)
  File "/usr/lib/enigma2/python/mytest.py", line 453, in runNextScreen
    session.openWithCallback(boundFunction(runNextScreen, session, screensToRun[1:]), screen, *args)
  File "/usr/lib/enigma2/python/mytest.py", line 274, in openWithCallback
    dlg = self.open(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 284, in open
    dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 244, in doInstantiateDialog
    dlg = screen(self, *arguments, **kwargs)
  File "/usr/lib/enigma2/python/Screens/InfoBar.py", line 65, in __init__
  File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 567, in __init__
  File "/usr/lib/enigma2/python/mytest.py", line 228, in instantiateDialog
    return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
  File "/usr/lib/enigma2/python/mytest.py", line 251, in doInstantiateDialog
    dlg.applySkin()
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 112, in applySkin
  File "/usr/lib/enigma2/python/Components/GUISkin.py", line 30, in createGUIScreen
  File "/usr/lib/enigma2/python/Components/ServiceList.py", line 128, in applySkin
TypeError: 'NoneType' object is not iterable

[ksada2]

I can only try a different skin once PLI is installed though. I can't choose the skin before I flash the box!

[janejak]

i se u use Black_Blue_HD/skin.xml but try to use orginal skin PLi-HD1/skin.xml who it are after flashing and se of ur box is nomale?