PDA

View Full Version : [ET8x00] Boot loop on Apollo 21



twol
17-07-14, 11:11
Image manager - downloaded Apollo 21 and pressed restore - clean flash.
Following receiver initialisation and then boot, loop before final crash.... brings up ViX spinning icon about 3 times before stopping.

Re-flashed Apollo 15 - OK.

Also tried via update from Apollo 15 to 21, same problem.

Sicilian
17-07-14, 11:30
Can you post a RS232 bootlog please.

twol
17-07-14, 12:37
No serial port on the ET8000 (or ET10000) so is there another method?
- or is there a way of using one of the usb ports?

Sicilian
17-07-14, 12:55
Flash build 015.

Set network to DHCP on and make a note of the IP address.

Update to build 021.

Telnet 'init 4' to stop E2 -- let e2 full load i.e. wait 2 mins

'enigma2' to start E2 in console

'Control c' to stop the console

Please post output from enigma2 command.

twol
17-07-14, 14:53
Flash build 015.

Set network to DHCP on and make a note of the IP address.

Update to build 021.

Telnet 'init 4' to stop E2 -- let e2 full load i.e. wait 2 mins

'enigma2' to start E2 in console

'Control c' to stop the console

Please post output from enigma2 command.
You learn something every day!

36015

twol
17-07-14, 16:28
Thanks Sicilian....... The hardest part was finding the log, it wouldn't go where I specified it to be and ended up everytime in my user data folder... Wasted about an hour.

rossi2000
17-07-14, 16:35
you can copy/paste from putty window into a txt file heh :)

twol
17-07-14, 19:11
you can copy/paste from putty window into a txt file heh :)

True, but when you are using a utility like Putty and have chosen the location for a file and it doesn't go there, it leaves you(well me at least) wondering, where it has gone and why...... Didn,t solve the why but found the file... Still highly frustrated as to why it doesn,t save in the locaton you have chosen.

Also had chosen log everything ... So needed a proper log in case there were non text characters in the stream.

Rob van der Does
17-07-14, 19:45
Thanks for your log: it clearly shows the issue and we're looking into it.