with AzUp work, ftp o.k. with telnet no
Printable View
with AzUp work, ftp o.k. with telnet no
Ti di***o aoratos eimai vre antoni? :)
read my post above...
I try nothing
user: rootQuote:
Originally Posted by antonis13
pass: azbox
thnx papito
@Tommy
Don't forget..
https://www.satpimps.co.uk/showpost....2&postcount=14
BR
PaPiTo
aa
If I would put on usb original fw is is possible ? In this way a change the USB (E2, Original) to switch S.O., only reboot should be performed.
To procedure to apply it is the same of
"#####FIRST TIME FLASHING E2######" but the the patch.bin in USB must be Original and not e2 ?
Thanks
Pippapeppa
You dont look wether commands are executed right or not?Quote:
Originally Posted by antonis13
mount -o loop patch_cramfs.bin /patch --> should be --> mount -o loop /mnt/root/patch_cramfs.bin /patch
@papito
Should be possible but i dont know the device name of the harddisk, and you will loose all data
the device name is hda for HDD
BR
PaPiTo
Could this work? for HDD
dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 skip=1
mkdir /patch
mount -o loop /mnt/root/patch_cramfs.bin /patch
umount /MMP
mount /dev/hda /MMP
cd /patch
tar -cf - . | tar -C / -xpf -
Guys, here is booting from usb1, hehehehe
You must create the dir /MMP because it does not exist.
After that is working
The error is here
@antonis13
dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs
you missed bs=56 skip=1
So use
dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs bs=56 skip=1
@PaPiTo2:
The internal HDD is /dev/hdb
hda is the DOM.
For those of you with console access - AND ONLY FOR THOSE!
Put the patch.bin to your HDD or usb stick as described here. Or do the whole thing on a linux box (Windows User can use WUBI - Ubuntu on Windows).
Fetch this with right click and save as - it is a rar archive.
Put setxenv to /bin on your Original and E2 device.
Put vme2hdd.bin to your tftp directory
192.168.1.2 is the IP of your tftp server.
With telnet on the original booted box
# For E2 from HDD
setxenv -f /dev/mtdblock0 -k y.start -v "net init;net initpci;net up; load -b tftp://192.168.1.2/vme2hdd.bin 0x90020000; go 0x90020000"
setxenv -f /dev/mtdblock0 -k a.linux_cmd -v "console=ttyS0,115200 root=/dev/hdb1 rw rootdelay=5 mem=108m"
If the extracted patch.bin is on the /dev/sda1 change hdb1 to sdb1.
Reboot
If bootet in E2 you should put setxenv to /bin and now to go back use this
setxenv -f /dev/mtdblock0 -k y.start -v "xrpc 0xac080090; load zbf 0xb3000000; go"
setxenv -f /dev/mtdblock0 -k a.linux_cmd -v "console=ttyS0,115200 root=/dev/hda1 rw rootdelay=5 mem=108m"
There is some work to be done, that the kernel (vme2hdd.bin) can be loaded from devices like HDD.
There is also the command "disk" in yamon which could be used to boot from the first partition of the internal disk, if it is divided in two partition. I haven't tryed this yet.
The_Ripper will implement kexec into the kernel which will makes things easyer. But this is another story and will be shown when done.
Went back to original, and no problem.
Thanks Sattommy
All steps done ok, but when I try to reboot it returns to the "rescue mode" and nothing else.
Any ideas?
Now it's working...
I just have to wait a longer time.
Just a thought how do we handle an update to next release? when available.
when new update comes, you have to repeat all steps to install again on the usb.
lets dream....
maybe a liveCd booting from usb, without change the kernel....
yeah, it's a dream....
pff dual boot would be (flash original) enigma2 usb would be heaven (in test phase).
after that i would prefer in flash (DOM) :)