Amiko Alien Boot Loader

The output you posted would suggest that the receiver can be accessed using ip address. I am sure there are exceptions, but all the receivers I have seen get that far would connect, providing the correct ip is used for the connection.

But...

I agree. The A2 is a bit dated and should be replaced if possible. I think it was released at the end of 2011.
 
sattech64 said:
My router here in the shop doesn't show the A2 connecting but both LED's are lighted on the LAN module. I dunno looks like I am going to be in the market fr a new receiver
Click to expand...

To be clear, you will need to access your router and find the ip that the A2 is using to connect to it. Another way of doing this would be to connect the A2 to router, restart the A2, and record the rs232 output. The ip the A2 is using to connect to the router should be in the rs232 output. My guess is the A2 is missing that .xml file that it is complaining about. But it is hard to say without ftp to the box and check.
 
I will look at the RS232 data because my router never shows the A2 to be connected. Only item connected is the PC I was using on the forum at the time.
This certainly is an odd one especially since I was using it most every day in the shop until I restored my A3 for the millionth time and decided to use it for a bit.
I plugged in the A2 when the A3 fell on it's nose again and BOOT was as far as I've gotten since LOL!

Thanks again for the suggestions!
 
None of those worked ..wonder if my STB having a 7105 processor instead of a 7111 or 7162 is causing this problem??

I have a backup if I could ever get far enough to use it LOL
 
I have the first image you suggested partly loaded but I think it is locked up. It is on the internet currently and I can see things with FZ now
 
Loading Images

I have tried several different E2 images and it seem they all get to around the area of video output methods and just hangs.
Trying OpenESI for kicks currently and it got to the point where it asks if I wanted to delete all the other languages, and I chose yes, so far it's stuck there.
Odd Ball Box !View attachment 14526
 
Which pkt image is that and where was it downloaded?
Telnet to the box and type init 4 followed by enigma2. Post the output.

For the most part, enigma2 images are junk in the A2. They will run, but they may freeze, and they do not have the full features you will find in dedicated enigma2 boxes.
 
Help!!!

I would really rather have Spark working on this box. I never could get the original E2 image to do what I wanted it to do.
I just can't see any good reason why Spark won't boot! I extracted the U-Boot file from the 1.2.52 Boot upgrade package and flashed it to the box via RS232 so I think I can safely eliminate the boot loader as a source of trouble. I'm not sure but this box may have been connected in the shop without a UPS when we had several power flickers,so that may be a cause of all this.I loaded the 2 files in the Spark Americas 7162 rescue image but strangely none of the IP addresses it shows allows me to connect and it won't pull an IP from my network so I cant FTP into it that way. If I could just somehow get it to boot the rescue image I would be golden I think! I could manage a network IP with OpenEsi once however. I will get that output you asked for as soon as I can get into the box again via network. RS232 is fine but I need a network IP for Telnet to do any good.

Here is the data Openesi 5.0 only one I can telnet into via RS232


View attachment openesi.txt Screenshot-2017-12-2 Open Webif.webp
 
Last edited:
el bandido said:
Download and install the Spark recovery image that is in post #6 of this thread:
https://linuxsat-support.com/thread/117775-help-with-spark-rescue-image/

For the enigma2, ftp into the box and get the settings file that is located in etc/enigma2. Zip the settings file and attach it here.
Click to expand...


I loaded the SPARK files but it still refuses to boot spark...just hangs on BOOT

Here is the settings file you ask for.. word wrap is a bit rough..

View attachment e2settings.txt
 
Please describe in great detail what you are doing to recover in Spark.

The enigma2 settings look OK, but it is not complete for the user. Looks like there was an attempt to set up 87 West, but it was not completed. Looks like the language has not been set either. The enigma2 side should run once the setup is completed.
 
What I have done in Spark is load numerous different rescue images via USB. It never completes the boot so it never pulls an IP from my network on the Spark side so I can't FTP,Telnet or anything to gain access to that partition to see what if any files exist. I did extract the boot loader from the AppPrg.tar file in the v1.2.51 (Enigma2 Boot Upgrade) package and it was updated via RS232. Other than this it's about all I can do. I have a complete backup but until I can get the Spark side to finish a boot I can't use that. Yeah I'm very slowly learning the OpenESI program and how it works as well as how it sets up. I agree that I believe E2 would run after I figure out the settings I need for North America and where to put them. If I didn't really like this box and seeing it as somewhat of a challenge I would have made it part of my spare parts box by now, but I do like it's performance and such.. just can't figure out this Spark deal! Seems to me it ought to work fine! I'm certainly open to any suggestions..

Thanks so much!


EDIT:

FWIW I came across the original E2 Image that was installed originally in this box and you guessed it.. it wouldn't boot from that either. The same as Spark hangs on boot.
Looks like Open ESI seems to be the image of choice for this box for some reason.
 
Last edited:
Thanks for the references. When I look for the weather.xml file telnet data reports it doesn't exist View attachment spark1.txt

On post 5 of the second link I'm guessing the writer is referring to connecting via telnet and RS232. When I try that putty won't let me paste, type or enter any commands at all.

Any ideas here?
 
Back
Top