PDA

View Full Version : Install E2 on USB and leave dom untouched



sattommy
28-10-2010, 09:07 AM
Ok Guys,

NOTE: Changing from opensat to e2 and the otherway around involves changing the kernel either with azup or opensat firmware upgrade method.

What do you need:
-1 usb of at lest 512mb (for e2, possible 256 will work)
-1 usb for putting patch bin

#####FIRST TIME FLASHING E2######
-Put e2 patch.bin in usb.
-Reboot your azbox and follow onscreen instructions to install upgrade. This will only install new kernel. When done reboot (leave usb stick in the slot)
-Once rebooted box will show rescue mode and IP. DO NOT USE AZUP NOW
-Attach usb stick for e2 now (521mb or larger).
-Telnet to your box and issue the following commands:

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
sfdisk -f -uM /dev/sdb < /patch/hda.out
mkfs.ext3 /dev/sdb1
mkfs.ext2 /dev/sdb2
mkdir /MMP
mount /dev/sdb1 /MMP
cd /patch
tar -cf - . | tar -C / -xpf -

-Now remove usb stick with patch.bin on it and issue the following command:

reboot -f

-This should boot e2 from usb stick.

#####GOING BACK TO OPENSAT SOFTWARE#####
-Remove usb stick with e2, and place usb stick with opensat firmware patch.bin
-reboot box
-Run azup on your pc, and enter rescuemode ip.
-Click update.
-When done, remove usb stick from receiver and reboot

#####Go from OPENSAT to E2 after going back to opensat software#####
-Put in usb stick with e2 patch.bin -> only this one
-Reboot and follow onscreen instructions to upgrade
-Switch usb stick for the one with E2 and reboot

This should be it!

Regards,

Tommy

moicas3004
28-10-2010, 09:28 AM
After installing E2, and swaping to original, do we need to reproduce all steps to revert from original to E2 again?

OK thanks, i see it.

Smudger
28-10-2010, 09:46 AM
I think upper slot = rear slot on premium

tul
28-10-2010, 09:47 AM
Ok Guys,

NOTE: Changing from opensat to e2 and the otherway around involves using AZUP everytime.

What do you need:
-1 usb of at lest 512mb (for e2, possible 256 will work)
-1 usb for putting patch bin

#####FIRST TIME FLASHING E2######
-Put e2 patch.bin on usb and put this in the upper usb slot
-Reboot your azbox and follow onscreen instructions to install upgrade. This will only install new kernel. When done reboot (leave usb stick in the slot)
-Once rebooted box will show rescue mode and IP. DO NOT USE AZUP NOW
-Attach usb stick for e2 now (521mb or larger).
-Telnet to your box and issue the following commands:

dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 =skip=1
mkdir /PATCH
mount -o loop patch_cramfs.bin /PATCH
sfdisk -f -uM /dev/sdb < /PATCH/hda.out
mkfs.ext3 /dev/sdb1
mkfs.ext2 /dev/sdb2
umount /MMP
mount /dev/sdb1 /MMP
cd /PATCH
tar -cf - . | tar -C / -xpf -

-Now remove usb stick with patch.bin on it and issue the following command:

reboot -f

-This should boot e2 from usb stick.

#####GOING BACK TO OPENSAT SOFTWARE#####
-Remove usb stick with e2, and place usb stick with opensat firmware patch.bin
-reboot box
-Run azup on your pc, and enter rescuemode ip.
-Click update.
-When done, remove usb stick from receiver and reboot

#####Go from OPENSAT to E2 after going back to opensat software#####
-Put in usb stick with e2 patch.bin -> only this one
-Reboot and follow onscreen instructions to upgrade
-Switch usb stick for the one with E2 and reboot

This should be it!

Regards,

Tommy

thnx for this, just a little question thought coz you didnt mention that.

every time we revert to other firmware we need patch.bin of destination in the slot? right?

sattommy
28-10-2010, 09:56 AM
thnx for this, just a little question thought coz you didnt mention that.

every time we revert to other firmware we need patch.bin of destination in the slot? right?

Yes

massimo1167
28-10-2010, 10:18 AM
Ok Guys,

NOTE: Changing from opensat to e2 and the otherway around involves using AZUP everytime.

What do you need:
-1 usb of at lest 512mb (for e2, possible 256 will work)
-1 usb for putting patch bin

both formatted fat32?


#####FIRST TIME FLASHING E2######
-Put e2 patch.bin on usb and put this in the upper usb slot

Thank You very much for this procedure.

In AzBox Premium HD, upper usb slot is the rear usb slot as mentioned by Smudger?

sattommy
28-10-2010, 10:21 AM
doesnt really matter which slot you put it in.

digihoe
28-10-2010, 10:21 AM
#####Go from OPENSAT to E2 after going back to opensat software#####
-Put in usb stick with e2 patch.bin -> only this one
-Reboot and follow onscreen instructions to upgrade
-Switch usb stick for the one with E2 and reboot


I have a question about the second step in this method. Is AzUp used or just the Opensat firmware loader? I'm just wondering since the NOTE in the start about AzUp...

I guess it's hard to have real USB firmware since they use different kernels.

Very good to have an alternative way to load the firmware.

Thank you and all the others and best regards!

sattommy
28-10-2010, 10:25 AM
You dont need AZUP in this step. You are right. i will take out the note ;-)

mounirmoune12
28-10-2010, 10:26 AM
i tried and didn't work


(none) login: root
Password:
# dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 =skip=1
BusyBox v1.16.1 (2010-05-23 13:26:55 CEST) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

Options:
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

# mkdir /PATCH
mkdir: can't create directory '/PATCH': File exists
# mount -o loop patch_cramfs.bin /PATCH
mount: mounting patch_cramfs.bin on /PATCH failed: No such file or directory
#

sattommy
28-10-2010, 10:30 AM
i tried and didn't work


(none) login: root
Password:
# dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 =skip=1
BusyBox v1.16.1 (2010-05-23 13:26:55 CEST) multi-call binary.

Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]

Copy a file with converting and formatting

Options:
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing

Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)

# mkdir /PATCH
mkdir: can't create directory '/PATCH': File exists
# mount -o loop patch_cramfs.bin /PATCH
mount: mounting patch_cramfs.bin on /PATCH failed: No such file or directory
#

fixed type and changed patch dir just to be sure

mounirmoune12
28-10-2010, 10:35 AM
Sattommy

can use original fw

thanks

4@@@@
28-10-2010, 11:01 AM
Try this # dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 skip=1
There was a typo =skip=1

It is also possible to do the thing with original software on the box. You need a tftp server for the E2 kernel to boot and also have to change two yamon variables.
But it is not adviced to do it without serial console access because typos like above will need a action over the console.

PaPiTo2
28-10-2010, 11:03 AM
Hi!

Thanks for the info Tommy.

Now a question, itīs possible to make this in the HDD?

BR
PaPiTo

antonis13
28-10-2010, 11:12 AM
I follow the instrucions & at the step:
-Telnet to your box and issue the following commands:
I cant Telnet; Why!

PaPiTo2
28-10-2010, 11:20 AM
I follow the instrucions & at the step:
-Telnet to your box and issue the following commands:
I cant Telnet; Why!

Check the IP

BR
PaPiTo

antonis13
28-10-2010, 11:45 AM
in DCC
root
dreambox

Telnet Connected
FTP Connected
Enigma2 not detected (Functionality limited)
Telnet login incorrect!
What am I doing wrong

PaPiTo2
28-10-2010, 11:52 AM
user/pass ?

leerock
28-10-2010, 11:53 AM
Root
Azbox

antonis13
28-10-2010, 11:53 AM
user: root
pass: dreambox

wrong!

antonis13
28-10-2010, 12:00 PM
with AzUp work, ftp o.k. with telnet no

leerock
28-10-2010, 12:01 PM
Ti di***o aoratos eimai vre antoni? :)
read my post above...

antonis13
28-10-2010, 12:08 PM
I try nothing

sattommy
28-10-2010, 12:27 PM
user: root
pass: dreambox

wrong!

user: root
pass: azbox

thnx papito

PaPiTo2
28-10-2010, 12:32 PM
@Tommy

Don't forget..

https://www.satpimps.co.uk/showpost.php?p=762532&postcount=14

BR
PaPiTo

antonis13
28-10-2010, 12:38 PM
aa

pippapeppa
28-10-2010, 12:54 PM
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

sattommy
28-10-2010, 01:00 PM
it work with putty but :

Powered by The Ripper, telesat && MickeySa ;)
Linux/mips 2.6.22.19-19-the_ripper

(none) login: root
Password:
# dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs
mkdir /patch
mount -o loop patch_cramfs.bin /patch
sfdisk -f -uM /dev/sdb < /patch/hda.out
mkfs.ext3 /dev/sdb1
mkfs.ext2 /dev/sdb2
umount /MMP
mount /dev/sdb1 /MMP
cd /patch
tar -cf - . | tar -C / -xpf -
826294+1 records in
826294+1 records out
46272512 bytes (44.1MB) copied, 56.612581 seconds, 79
# mkdir /patch
# mount -o loop patch_cramfs.bin /patch
mount: mounting patch_cramfs.bin on /patch failed: No
# sfdisk -f -uM /dev/sdb < /patch/hda.out
-sh: can't open /patch/hda.out: no such file
# mkfs.ext3 /dev/sdb1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
61568 inodes, 245944 blocks
12297 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=255852544
8 block groups
32768 blocks per group, 32768 fragments per group
7696 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting informa

This filesystem will be automatically checked every 3
180 days, whichever comes first. Use tune2fs -c or -
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.12 (17-May-2010)
mkfs.ext2: No such device or address while trying to
# umount /MMP
umount: can't umount /MMP: No such file or directory
# mount /dev/sdb1 /MMP
mount: mounting /dev/sdb1 on /MMP failed: No such fil
# cd /patch
# tar -cf - . | tar -C / -xpf -

but finaly again nothing, after reboot is rescue mode

You dont look wether commands are executed right or not?

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

PaPiTo2
28-10-2010, 04:03 PM
the device name is hda for HDD

BR
PaPiTo

PaPiTo2
28-10-2010, 04:20 PM
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 -

moicas3004
28-10-2010, 06:14 PM
Guys, here is booting from usb1, hehehehe

You must create the dir /MMP because it does not exist.

After that is working

4@@@@
28-10-2010, 06:16 PM
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.

4@@@@
28-10-2010, 06:32 PM
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 (http://kathif.vs120005.hl-users.com/test/files.rar) 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.

moicas3004
28-10-2010, 07:30 PM
Went back to original, and no problem.

Thanks Sattommy

gravatasufoca
30-10-2010, 12:12 PM
All steps done ok, but when I try to reboot it returns to the "rescue mode" and nothing else.

Any ideas?

gravatasufoca
30-10-2010, 12:26 PM
Now it's working...
I just have to wait a longer time.

Smudger
30-10-2010, 12:35 PM
Just a thought how do we handle an update to next release? when available.

moicas3004
31-10-2010, 11:19 PM
when new update comes, you have to repeat all steps to install again on the usb.

gravatasufoca
31-10-2010, 11:55 PM
lets dream....

maybe a liveCd booting from usb, without change the kernel....

yeah, it's a dream....

hfmls
01-11-2010, 06:13 AM
pff dual boot would be (flash original) enigma2 usb would be heaven (in test phase).
after that i would prefer in flash (DOM) :)

massimo1167
12-11-2010, 12:03 PM
I have a problem installing the latest version of E2 (DS 3.0 for distribution Azbox HD).

I successfully installed the version 1.0.29 by The_Ripper following the procedures in the first post, then went back to original firmware without any problems.

Now I would like to update the usb pendrive with the latest version of E2, so I followed the steps, starting from the first one.

Unfortunately, after the whole procedure, when azbox restart with enigma2 from usb pendrive, the decoder stops and the VFD display shows only "premium" with black screen.

Here is the telnet command log.


Powered by The Ripper, telesat && MickeySa ;)
Linux/mips 2.6.22.19-19-the_ripper

(none) login: root
Password:
# cd /
# dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 skip=1
dd: writing '/mnt/root/patch_cramfs.bin': No space left on device
604106+0 records in
604105+0 records out
33829880 bytes (32.3MB) copied, 41.833879 seconds, 789.7KB/s
# mkdir /patch
# mount -o loop /mnt/root/patch_cramfs.bin /patch
# sfdisk -f -uM /dev/sdb < /patch/hda.out
Checking that no-one is using this disk right now ...
OK

Disk /dev/sdb: 1017 cylinders, 33 heads, 61 sectors/track
Old situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System
/dev/sdb1 0+ 183- 184- 187632 83 Linux
/dev/sdb2 183+ 187- 4 4096 83 Linux
/dev/sdb3 187+ 244 58- 59136 82 Linux swap / Solaris
/dev/sdb4 0 - 0 0 0 Empty

sfdisk: long or incomplete input line - quitting
# mkfs.ext3 /dev/sdb1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
46920 inodes, 187632 blocks
9381 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
23 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=1
Maximum filesystem blocks=4194304
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkdir /MMP
# mount /dev/sdb1 /MMP
# cd /patch
# ls -l
drwxr-xr-x 1 root root 32 Jan 1 1970 FLASH
drwxr-xr-x 1 root root 284 Jan 1 1970 MMP
-rw-r--r-- 1 root root 248479 Jan 1 1970 Update.list
-rwxr-xr-x 1 root root 736 Jan 1 1970 command.seq
-rwxrw-rw- 1 root root 249 Jan 1 1970 hda.out
# tar -cf - . | tar -C / -xpf -
# reboot -f




dd: writing '/mnt/root/patch_cramfs.bin': No space left on device
I don't remember if first time I had the same message.


Maybe I need to repeat from the beginning the procedure again?
The Enigma2 usb pendrive must be reformatted before update with new E2 release or not?

Thanks

********************************* ********************************* *******************************
New update 13-11-2011:
I have flashed original firmware and I saw some problem with azup (wrong firmware), so I've decided to format the usb pendrive and the repeat the copy of the original firmware on it, then everithing went well.
I repeat the same operation with DS 3.0 enigma2 (format and copy patch.bin) so I've installed that one too.
This is the new telnet command log.



Powered by The Ripper, telesat && MickeySa ;)
Linux/mips 2.6.22.19-19-the_ripper

(none) login: root
Password:
# dd if=/mnt/root/patch.bin of=/mnt/root/patch_cramfs.bin bs=56 skip=1
847725+1 records in
847725+1 records out
47472640 bytes (45.3MB) copied, 61.343862 seconds, 755.7KB/s
# ls /mnt/root
patch.bin patch_cr.bin
# mkdir /patch
# mount -o loop /mnt/root/patch_cramfs.bin /patch
# sfdisk -f -uM /dev/sdb < /patch/hda.out
Checking that no-one is using this disk right now ...
OK

Disk /dev/sdb: 1017 cylinders, 33 heads, 61 sectors/track
Old situation:
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System
/dev/sdb1 0+ 999- 1000- 1023580 c W95 FAT32 (LBA)
/dev/sdb2 0 - 0 0 0 Empty
/dev/sdb3 0 - 0 0 0 Empty
/dev/sdb4 0 - 0 0 0 Empty
New situation:
Units = sectors of 512 bytes, counting from 0

Device Boot Start End #sectors Id System
/dev/sdb1 32 375295 375264 83 Linux
/dev/sdb2 375296 383487 8192 83 Linux
/dev/sdb3 383488 501759 118272 82 Linux swap / Solaris
/dev/sdb4 0 - 0 0 Empty
Warning: partition 1 does not end at a cylinder boundary
Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
# mkfs.ext3 /dev/sdb1
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
46920 inodes, 187632 blocks
9381 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67371008
23 block groups
8192 blocks per group, 8192 fragments per group
2040 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=1
Maximum filesystem blocks=4194304
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
# mkdir /MMP
# mount /dev/sdb1 /MMP
# cd /patch
# tar -cf - . | tar -C / -xpf -
# reboot -f