New images OpenPLi HomeBuild DM 900/920
Download DM 900 : https://mega.nz/file/ioUkDapQ#…ysoDZloe-OfePOfpm0V69vQ08
Download DM 920 : https://mega.nz/file/b00xTC6B#…LAOVSitOcANpweMsnpo3EH-CA
- samba included
- feeds are working
New images OpenPLi HomeBuild DM 900/920
Download DM 900 : https://mega.nz/file/ioUkDapQ#…ysoDZloe-OfePOfpm0V69vQ08
Download DM 920 : https://mega.nz/file/b00xTC6B#…LAOVSitOcANpweMsnpo3EH-CA
- samba included
- feeds are working
The commands you've done have no impact on your hdd !
they just mount mmc partitions into /data and /boot and
enable you to select the next multiboot destination !
Well ... you went into a wrong direction ! you're restored
Mahdy Multiboot V40 witch destroys an essential information
for V30 ! your STB will never play live video and audio !!!
This was the point I've started to find a recovery method !
the package I've sent to you is the result ... that can be
restored via HiTool or use the usb_upgrade.bin ! and
your STB will become again a normal V30 ! but you'll
never play live video and audio for now on !
You can see the signal , you can scan it , but never play it !
but ... you can stream it from WebIF and play it on PC from VLC !
I've made at the time the same mistakes ! you should read and
conform to my warning ... "do not use Mahdy Multiboot " !
From this point I cannot help you in any way ! sorry !
If you used once sf8008 that explain what's happen !
is like Viper Combo 4k ! you bricked the internal boot !
and if you had a power failure ... that could be the end !!!
Tring to load "fastboot" is specific to STB's witch support
"recovery" images ... is not the case of Viper V30 ! this
looks as sometime the internal boot was rewrite with
with one from sf8008 or Viper 4K Combo ! I don't know
how !!!
https://mega.nz/file/fstHSZAB#pEIdNR35wjfq1vdscypSX1d60Squ_3A0U0z8xqhLmaE
This is shown after you power-up with GREEN pressed ?
- first is trying to load a fastboot.bin from USB
- not finding fastboot.bin on it is trying to load it from EMMC
....
Looking for fastboot.bin on USB means to me he is searching
for a "recovery" image .... witch is not the case of Viper V30 !!!
there is not such a thing for V30 ! could be OK for Viper Combo
4K ... but not for V30 !!!
What's the story behind this V30 ! how come you need to
recover it ? what was the "experiment" you've done ?
You could put on USB all the files I've sent ! and will see
on the console log what he is trying to do with them !
I've never used HiTool console window !
The usb_update.bin is a replacing for HiTool in some conditions !
... if you still can activate the internal bootloader by pressing GREEN !
Sometimes ... GREEN cannot be recognized ! so the only way remains
HiToll witch connects and restore Fastboot !
If you tried to install a different image than Amiko Viper ... or
Dinobot TWIN ! your RC could be not recognized , so even you
are pressing GREEN you will not get the attention of bootloader !
I was aware of this issue with RC ! so I have a Dinobot replacement
RC witch is recognized even if the Amiko RC is not ! But ... if you
restore with HiTool my files ! your V30 should see GREEN from
Amiko RC and enable you to restore from USB e.g. OpenATV !
usb_update.bin !!! not update.bin !!!
This must activate internal bootloader and
you will see on the screen the update progress !
The second step is to load the desired image !!!
But ! if you previous load some strange SW , internal
Bootloader could not be activated from your native RC
on GREEN ! so ... only HiTool procedure with the
archive I've sent could solve the problem !!!
If you restore with HiTool ... there is no Enigma2 restored !
so you must install OpenATV using the classic method with
GREEN button pressed during power-up !
Exactly the same thing happen if you are recovering with
usb_update.bin !!! just read carefully my indications !
Updates interval is configurable from menu ! you can stop the process forever !
Will be a new version by the end of the week !
You need the XML and the pieces referred in it ...
Download the archive : https://mega.nz/file/fstHSZAB#…pSX1d60Squ_3A0U0z8xqhLmaE
Read this !!!
Not me ... raed ! he included networking support at
build time into some recipe , this installs by default
samba ! I just build a new OpenPLi Homebuild image !
OpenPLi HomeBuild dm900



What's new :
- official version name is HomeBuild
- networking support is active
- internal HDD can be accessed from Windows
- feeds are functional but not in sync ! are older !!!



Do not "Software Update" ... feeds are functional but out of sync !
Download : https://mega.nz/file/msk3XSqJ#…4_DvYu3ql_9aYMHYzAUeYLCcg
Unfortunately , complex "samba" installation , introduce
some hidden bug ! the host name is visible ... but that's all !
Both @Raed's images , OpenBH and OpenTS have the same
issue !
You need to install "samba" ...
opkg install samba
the name from /etc/hostname (dm900)
will appear in Network after STB reboot !!!
You can try to define by yourself ! editting :
/etc/hostname

OK ! error reported !
Thats happen because the HDD was declared in other images like
a network location ! I'm not home right now ! but I'll try to see
how to solve ! Network paths are not OK !
I've made a test here on other STB under OpenATV ...





First time when accessing Network it requires user/passwd
from the STB then remember that and access it very fast !
Please confirm you are using the same procedure to
build Network Shortcuts !
On DM 920 UHD ... please discard the offer to update ! there
are 484 new modules ! too much and even ends with success
will block the Boot ! You can disable the offer tot update from
the Menu !!!
Yes ! but you can disable it from Menu !