I just ran another transponder scan after changing to satellite from Astra 28.2E to Hotbird. After the scan completed I pressed ok and then I got a blank screen. After 10 minutes I restarted the box and all i get is the flashing image of Darkstar II. I could ping to box so using DCC I reflashed it with the image and same thing. Not loading and getting stuck on the image flashing. I tried another image but same thing image flashing of the new firmware image. Can someone help. Yes I have unplugged all the cables and waited for 10 minutes before trying again.
So I guess no one has an answer. I have fixed the issue now, so I will share it The issue was after a restart of the box it was not correctly booting up. It just got hung on the boot screen flashing the Darkstar image. Ofcourse the first thing to do is to reimage the box. I do not have a serial cable so I do the flashing over the network Two methods you can do this. Use DCC to flash it or FTP the firmware to the tmp folder and rename it to root.cramfs and restart the box. I tried to reflash the image with the same one which it had loaded (Nabilosat Darkstar II) but it did not resovle the issue. So I tried another Nabilosat V8 image and the same issue was there. Then I thought I really need dreamup to put the image on correctly but after doing some more research I found "Gemini Project 4.70 DM500 MaxVar" image so I loaded that via the network and my box was up and running again. I still cant figure out what went wrong with the two nabliosat images. After doing more research I now know some images are not clone safe or there is some kind of clone time bomb. Maybe someone could add more to that
had similar issues in the past. have used root.cramfs and nothing happens. and yet this same image will load via a serial cable. so i honestly can't say what the issue is. my only guess is that the image that did work had integrated bootloader that matched the image and that the other images did not have bootloader integrated. In such a case if the current bootloader is not compatible with the new image then the software wont start. in the case of the serial method the image gets directly written into flash memory and then the box reloads from this memory location. in the case of loading an image into /tmp the image still does not exist in flash. the root.cramfs method requires loader software to perform this task and if the loader does not match the image then it will fail. i won't swear to this but its the only thing that i can think makes any sense
