1308 replies to this topic

[Pedro_Newbie]

I don't know for sure, that's what I was wondering in this post: http://forums.openpl...ndpost&p=462697

The Solo SE and Zero are build with the option force.update, the Duo2 and Solo2 with reboot.update.

 

Anyone who has a Zero who can tell if the force.update does do a flash without confirmation?

 

For the time being I shall revert the last commit

[Frenske]

Anyone who has a Zero who can tell if the force.update does do a flash without confirmation?

To be honest, the first time I flashed a Zero, I had no clue what to do but eventually it appeared that I flashed a new image. So I assume they actually do a flash without any confirmation.

[Rob van der Does]

Anyone who has a Zero who can tell if the force.update does do a flash without confirmation?

To be honest, the first time I flashed a Zero, I had no clue what to do but eventually it appeared that I flashed a new image. So I assume they actually do a flash without any confirmation.

That is correct, provided there is a file named "force.update".
So unfortunately back to the old DUO days.....

[Rob van der Does]

And hence virtually impossible to keep a copy of the image on an USB-stick that resides in the box (or better: it should not hold the file "force.update" at all, so users can manually change that when they do want to flash).

[Pedro_Newbie]

Made a new commit:

- For the Vu+ Solo SE and the Vu+ Zero the file noforce.update is added to the backup with the directions to rename it to force.update to be able to flash it;

- For the Vu+ Solo SE and the Vu+ Zero the directions to flash an image is added as message36;

Spoiler

Update is in progress when the white light becomes gradually bright and dark on the front panel.
Update is done when white light blinks on the front panel.

- Changed the lookuptable.txt accordingly

- Removed some obsolete messages

- Tided up a little in the language files (need still some work however such as add translations in most language files)

 

These changes should be available after the next update, normally tomorrow, as version git20+git 11)

[Dimitrij]

Pedro_Newbie

hd2400 and hd1100

where?

/proc/stb/info/boxtype or  /proc/stb/info/vumodel or ...

Edited by Dima73, 22 December 2014 - 18:35.

[Pedro_Newbie]

Hi Dima73

In /proc/stb/info/boxtype, names are indeed hd2400 and hd1100

[Dimitrij]

Hi Dima73

In /proc/stb/info/boxtype, names are indeed hd2400 and hd1100

Thank you very much.

[gerard0610]

With the next update (tomorrow) it will be fixed.

After an update today (14:00h) still the same problem occur.

Is it possible that your change is not yet processed in the Image?

[Pedro_Newbie]

Indeed, the changes are still not processed in the new images, why it isn't in the new images I don't know.

Maybe some Openpli dev knows why it isn't processed?

[Pedro_Newbie]

@gerard0610

 

If you update now you should get the last version, at least for the Solo2 and ET8000 this is the case.

[gerard0610]

@gerard0610

 

If you update now you should get the last version, at least for the Solo2 and ET8000 this is the case.

A short feedback:

I have upgraded the VU+Zero, made afterwards a backup (Backupsuite) and tried to flash the Backup without result. Still the old problem.

Attached Files

•  Backupsuite-VU+Zero-25-12-2014.JPG   20.65KB   10 downloads

[Pedro_Newbie]

You'll have to rename noforce.update to force.update otherwise it won't flash. This is done because you could otherwise unintentionally flash your Zero if you reboot your receiver with the USB stick still attached.

 

What happens if you reboot with the USB stick inserted but with the file noforce.update? Does the powerlight blinks at reboot?

With the Solo2 you have to push the powerbutton when the image is found.

 

Could you try to reboot your receiver with the USB-stick attached and observe the powerlight?

 

Better would be making a log while rebooting with the stick attached, I'm wondering if the bootloader waits for a key press or not.

 

So to recapture: to be able to flash rename noforce.update to force.update

 

Or to be complete as stated in the message-file:

 

To restore the image:
First rename the file 'noforce.update' on your USB-stick into 'force.update'.
Place USB stick in the USB slot and switch the receiver off and on with the powerswitch.
Update is in progress when the white light becomes gradually bright and dark on the front panel.
Update is done when white light blinks on the front panel.

Edited by Pedro_Newbie, 25 December 2014 - 16:55.

[Pedro_Newbie]

I see a putty log won't go, no RS232 interface anymore on the Zero, too bad.

 

edit: strange the specifications states there is a rs232

Edited by Pedro_Newbie, 25 December 2014 - 17:12.

[Rob van der Does]

There is, but you need a special cable (connector) for it.

[Micky]

Backup did not boot from all kind of USB sticks. Why? It is possible to make the backup on the stick, but it did not boot. I use a Vu+SOLO.

 

 

Micky

Edited by Micky, 26 December 2014 - 03:32.

[Pedro_Newbie]

What do you mean by: did not boot?

You can't flash your Solo with the  back-up from the USB-stick?

Try a different USB-stick, the smaller and older the better in most cases

 

You can try to flash it via the BackupSuite with the Blue button = Restore back-up

[gerard0610]

 

You'll have to rename noforce.update to force.update otherwise it won't flash. This is done because you could otherwise unintentionally flash your Zero if you reboot your receiver with the USB stick still attached.

 

What happens if you reboot with the USB stick inserted but with the file noforce.update? Does the powerlight blinks at reboot?

With the Solo2 you have to push the powerbutton when the image is found.

 

Could you try to reboot your receiver with the USB-stick attached and observe the powerlight?

 

Better would be making a log while rebooting with the stick attached, I'm wondering if the bootloader waits for a key press or not.

 

So to recapture: to be able to flash rename noforce.update to force.update

 

Or to be complete as stated in the message-file:

 

To restore the image:
First rename the file 'noforce.update' on your USB-stick into 'force.update'.
Place USB stick in the USB slot and switch the receiver off and on with the powerswitch.
Update is in progress when the white light becomes gradually bright and dark on the front panel.
Update is done when white light blinks on the front panel.

 

I have the Zero for test reasons. Normally I use the old VU+Duo.

 

With the VU+Duo I flash (the by the Backup suite made backup) without renaming a file on the USB stick. This is for me much easy and comfortable in my opinion.

 

I thought that you had renamed the file 'noforce.update' into 'force.update in the BackupSuite by default a couple of days ago.

 

Now I understand from you that I should each time  rename the file 'noforce.update' on my USB-stick into 'force.update.
I understand that you have introduced this because of safety reasons however for me it is uncomfortable and I prefer the situation as it is actually by the VU+Duo without renaming the file

[chafpa]

Totally agree with this way of doing !

[Rob van der Does]

With the VU+Duo I flash (the by the Backup suite made backup) without renaming a file on the USB stick. This is for me much easy and comfortable in my opinion.
 
I thought that you had renamed the file 'noforce.update' into 'force.update in the BackupSuite by default a couple of days ago.

The DUO & Zero2 have a different flash behaviour. This is dictated by the bootloader; there's nothing we can change in that area.
And it is as you say: the DUO flashes when it finds a valid image-folder during the first stage of the boot-process.

The Zero only flashes, when it finds the file 'force.update' in a valid image folder. The USB-backup copy is intended as a kind of safety copy, if it would hold the above named file the box would flash on every boot.
So: safety first: the file is named 'noforce.update' to prevent accidental flashes.


BTW: Most boxes require a dedicated button-press to accept a flash. This is the most convenient and safe method. For reasons we can only guess VU⁺ decided to go back in time and use this very user-unfriendly method.
Please try to convince VU⁺ that they should try to keep up with modern methods.

Edited by SatKiekerd, 26 December 2014 - 10:26.