recover E2 without AZUP

[MalMen]

Hello, i try to install E2 1.0.21 i think, but when i try to use it, only show "geeko :P"

If i put the pen in that show-me the ip address and i can login in into telnet...
i know to recover it i should use AZUP, but i dont have computers with M$ WINDOW$, so i just use ubuntu in my house, and wine cannt use sucessfull AZUP, can anyone post the manual to recover azbox to original FW with out AZUP ?
thanks

[buyukbang]

You can try live XP cd's. IE Hiren's Boot CD.

[4@@@@]

Telner to the box
You can mount patch_cramfs.bin which is build by
dd if=patch.bin of=patch_cramfs.bin bs=56 =skip=1
mkdir /tmp/tmp /tmp/hda1
mount -o loop patch_cramfs.bin /tmp/tmp
and mount also /dev/hda1
mount /dev/hda1 /tmp/hda1
Then you can copy the files with
cp -rd /tmp/tmp/MMP/* /tmp/hda1
sync
reboot the box without the stick
Maybe this is enough - I'm not 100% sure so
no quarantee for this.

[pr2]

Hello,

For me this is not enough because the DOM (/dev/hda) has 4 partitions with the official firmware and only 2 with E2 firmware and parition size are differents.

But for the time being, the 2nd partition foreseen by E2 is a swap partition that is not used.

So in the manual process, you need to delete all the existing partitions and create new ones.

If I remember well (I am not close to my Azbox with E2 now), partition for E2 are:
- partition 1: 192 MB for the system type Linux
- partition 2 : 64 MB is type Linux swap.

Pr2

P.S.: for people that replace the DOM by an adaptator SD or CF, be carefull to power off / power on your Azbox after changing the partition type because adaptator don't like the partition change and installation of files will be corrupted and your system will become unstable. Remember that adaptor specify that they are not plug and play and it seems that for them, changing the partition size is also a problem. Power off / Power On mandatory a reboot is not enough since the DOM is not resetted with a reboot.

[hperez]

i know to recover it i should use AZUP, but i dont have computers with M$ WINDOW$, so i just use ubuntu in my house, and wine cannt use sucessfull AZUP, can anyone post the manual to recover azbox to original FW with out AZUP ?

This is a little bit "funny". Azbox is based on linux, the enigma2 developers use linux for sure (don't you?), many azbox users use linux, but the tool to install enigma2 or return to the official firmware runs ONLY on windows :(

Don't you know there are toolkits that allow to create multiplatform applications? (qt, gtk...)

[pr2]

Hello,

Here is the result of fdisk -l on my Azbox with E2:

root@AZBox:~# fdisk -l

Disk /dev/hda: 4011 MB, 4011851776 bytes
16 heads, 63 sectors/track, 7773 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/hda1               1         373      187632  83 Linux
Partition 1 does not end on cylinder boundary
/dev/hda2             373         497       62720  82 Linux swap
Partition 2 does not end on cylinder boundary
root@AZBox:~#

Don't worry about the message "Partition x does not end on cylinder boundary" this is because my Azbox is no longer equipped with the original DOM. As you can see, I replace the original 256 MB DOM by a 4 GB SD card, this is not needed to install E2, it was just for fun. :-)

You can also use: sfdisk

root@AZBox:~# sfdisk -l

Disk /dev/hda: 7773 cylinders, 16 heads, 63 sectors/track
Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/hda1          0+    372-    373-    187632   83  Linux
/dev/hda2        372+    496-    125-     62720   82  Linux swap / Solaris

With this command, you can use the output provided has input to sfdisk so the partition will be created properly:

root@AZBox:~# sfdisk -d
# partition table of /dev/hda
unit: sectors

/dev/hda1 : start=       32, size=   375264, Id=83
/dev/hda2 : start=   375296, size=   125440, Id=82
/dev/hda3 : start=        0, size=        0, Id= 0
/dev/hda4 : start=        0, size=        0, Id= 0

May be someone with the official DOM in E2 can issue the same commands and put the output here, just to be sure that values remains the same.

Pr2

[arcibald]

May be someone with the official DOM in E2 can issue the same commands and put the output here, just to be sure that values remains the same.

Pr2

If no one answers first ... I try later on my DOM!

Ciao

AZBox PremiumHD with E2 - Test Partitions on DOM:

root@AZBox:~# df -k

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/hda1 181736 108688 63668 63% /

udev 2048 92 1956 4% /dev

tmpfs 50384 432 49952 1% /var

tmpfs 50384 4 50380 0% /tmp

root@AZBox:~# fdisk -l

Disk /dev/hda: 256 MB, 256901120 bytes

16 heads, 32 sectors/track, 980 cylinders

Units = cylinders of 512 * 512 = 262144 bytes

Device Boot Start End Blocks Id System

/dev/hda1 1 733 187632 83 Linux

/dev/hda2 734 978 62720 82 Linux swap

root@AZBox:~# sfdisk -l

Disk /dev/hda: 980 cylinders, 16 heads, 32 sectors/track

Units = cylinders of 262144 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System

/dev/hda1 0+ 732 733- 187632 83 Linux

/dev/hda2 733 977 245 62720 82 Linux swap / Solaris

/dev/hda3 0 - 0 0 0 Empty

/dev/hda4 0 - 0 0 0 Empty

root@AZBox:~# sfdisk -d

# partition table of /dev/hda

unit: sectors

/dev/hda1 : start= 32, size= 375264, Id=83

/dev/hda2 : start= 375296, size= 125440, Id=82

/dev/hda3 : start= 0, size= 0, Id= 0

/dev/hda4 : start= 0, size= 0, Id= 0

BR ... Arci

[MalMen]

hmm, i dont think that so easy, i replace my dom with another dom, from a azbox working, and the box still the same, i think i have to put a boot partition or something like that...

[4@@@@]

Sorry I thought you want to put E2 on it

The other way should work with serial access and the original Kernel from tftp server.
The original kernel (vmlinux) should be extracted from the patch.bin.
You'll need to have the usb fat stick in the box with the original software. Then boot over tftp the original kernel until update. Update the software as usual.
This should work.
If you have no serial console, you can try to setxenv the y.start to fetch the kernel from tftp server (see another thread here from me). You have to install the tftp server on your linux box which should be easy.

To set the right partitions, we must check with Azup what is done in case of restore. The file should be on the box before the update stopped. So if anybody could do the job an look for skripts on the /tmp or equal, we should find the restore script for partitions.

EDIT:

This is done by AzUp

dd if /mnt/root/patch.bin /mnt/root/patch.cra bs=56 skip=1
then will be the cramfs be mounted whith loop
mount -o loop /mnt/root/patch.cra /Patch
dd if /Patch/FLASH/loader.bin skip 512 of /dev/mtdblock4 bs 1024
and then reboot.
No change in Partition until now.
If you boot the new kernel then the old partition set will be build in and all will be copied as is.

So I think it shoud be OK to do the steps abouve and you will be able to get back.

EDIT2:

That the way the mtd block are in the kernel AZBox[~]$ cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00010000 "CS2: Physically mapped flash"
mtd1: 00020000 00010000 "CS2-Part1"
mtd2: 00020000 00010000 "CS2-Part2"
mtd3: 00040000 00010000 "CS2-Part3"
mtd4: 00680000 00010000 "CS2-Part4"
mtd5: 00100000 00010000 "CS2-Part5"

The trick with E2 is to NOT use this and format the /dev/hda1 as needed.

[pr2]

Hello,

Of course you cannot swith from E2 to official firmware and vice-versa just by replacing the DOM.

E2 installation change the whole boot procedure (and the DOM partition size).

If you want to swap between 2 OS and keep them on a DOM, you will need 3 DOM.

1) With official firmware
2) With E2
3) just to do the swap procedure between official firmware and E2 and vice-versa.

So you have DOM1 when working normally with you Azbox.
You replace with DOM3 and install official firmware to it.
You migrate to E2 on DOM3 (full process).
You install DOM2 and restart E2 migration from AZup.exe point, so DOM2 will be installed in E2 too.

So your working DOM will be DOM1 and DOM2, so both will keep all settings, and when you need to revert to another firmware you place DOM3 and follow the return to another firmware procedure.

If you use an CF or SD adaptator be carefull, you will need to power off / power on your Azbox and not reboot after the partition change (and sometimes even repeat twice the procedure).

Pr2

[The_Ripper]

Hmm problem with swaping DOMs is that I use 2.6.22 kernel while in FW it's used 2.6.15, so reflashing old kernel in flash must be done first with DD command on console on mtd partition, then poweroff Azbox, swap DOM with original FW, power on .

[MalMen]

hmm, i install winxp on virtualmachine to use AZup
But AZUp still not do the job xD
I press Update and that show
"patch.cramfs created"
And after that..
"File not found, unable to complete request"

Any sugest ?
I am using last official AZ FW

[arcibald]

Hi

... but you explain exactly what you did!

and ... verify if Your XP system fully recognizes the virtual network bridge to the host (router) ?

[pr2]

I guess that you didn't leave the USB stick with patch.bin (for E2) into your Azbox and you start Azup procedure... follow the process as described which means leave the USB stick into your Azbox until Azup ask you to remove it.

Pr2

[MalMen]

yes, and i leave....
But i have now patch.bin of original az Fw... thats not it ?
or i need the 2 patchs.bin ?
thats not on tut that i follow... i have only patch.bin of last azbox fw...

Yes, my virtual machine is sucessfull bridged and working, azup connect to azbox with out problems, but the porecess fail... like i said before...

[MalMen]

http://www.youtube.com/watch?v=QP6yqKT2yMc

saw ?

[arcibald]

Yeah, I saw?

This happens whether you try again to install the E2 kernel ... that... the original kernel of the fw 0.9.xxxx ?

[MalMen]

Yeah, I saw?

This happens whether you try again to install the E2 kernel ... that... the original kernel of the fw 0.9.xxxx ?

yes it is, im sure it is...

[georgiou.cr]

Hello,

Of course you cannot swith from E2 to official firmware and vice-versa just by replacing the DOM.

E2 installation change the whole boot procedure (and the DOM partition size).

If you want to swap between 2 OS and keep them on a DOM, you will need 3 DOM.

1) With official firmware
2) With E2
3) just to do the swap procedure between official firmware and E2 and vice-versa.

So you have DOM1 when working normally with you Azbox.
You replace with DOM3 and install official firmware to it.
You migrate to E2 on DOM3 (full process).
You install DOM2 and restart E2 migration from AZup.exe point, so DOM2 will be installed in E2 too.

So your working DOM will be DOM1 and DOM2, so both will keep all settings, and when you need to revert to another firmware you place DOM3 and follow the return to another firmware procedure.

If you use an CF or SD adaptator be carefull, you will need to power off / power on your Azbox and not reboot after the partition change (and sometimes even repeat twice the procedure).

Pr2

I recently purchased a 1GB Transcend DOM and i was looking forward to install E2 in it and have the original DOM as backup in case something happens to the receiver (elite + premium HD). Is this possible ? If i remove the original DOM and insert the Transcend , will i be able to format it and install E2 or OFW to it ? What will happen when i plug in the original DOM back? ISnt the kernel kept inside the DOM?

Please advise

[zeini]

Yes, this is possible.