Fortec star ultra stuck in boot loop

[Willo]

After upgrading my channels with gTools my Fortec Star Life time ultra refuses to boot into the menu or display any channels. (Dark Screen)
After switching power on at rear rocker switch, Bottom Dash flickers across the LED display, then “On” appears momentarily, Vbox lights up momentarily then LED display off for about 15 Seconds and the whole process repeats.
I have tried pulling power then restarting.
Also tried downloading latest Version 2.73 firmware (from Fortec site) to receiver. Download is successful but still gets stuck in this boot loop.
I have been unable to download any channel settings from gtools since.

Any ideas on how to fix?

Regards
Willo

[kyle]

Try using a earlyer version of the firmware. like 2.35

also check your settings in gtools are correct.

[bassett]

Try using a lower value Bootloader, Changing the software program will not help, as the current bootloader will not except it.. If all else fails, throw it in the bin..

Been there, done that..

[Willo]

Tried the lower version of firmware. Gave me the dreaded night ridder result. (bottom horizontal LED chasing right to left)

Basset what is the lowest version bootloader? I have 61 (040515) is this the lowest & how do you install? I used the STB installer software from Fortec web site & would not load. Or do I need a JTag to install a new bootloader?

As you say maybe it’s time it was used as a book case holder or something :)

Willo

[bassett]

This should get you out of trouble...
Just load in the normal way, but use the 3.20 loader, instead of the higher value one.
For some reason the file will not load here, comes up "invalid file type'
PM me a e-mail address, and I will send you the loader

Also have a read of the zip, on g-tools

[simmo]

Just zip the file Bassett, and it will up load.

[Willo]

All is fixed now! this is what I did
As explained in my second post I tried to load Ver 235, left me with Knight Rider display. Just before I was about to solder in the resistors for the JTag connection, thought I might try ALBar Ver 231, result was software loaded & I had a working receiver.
Tried to upgrade to a more recent software version but could not, until I reset to factory default (System Setting Menu). Now with version 273 software I set about downloading my saved channel settings using gtools. After downloading from gtools finished the receiver was locked up again & back in the endless loop thing.
End result was my saved settings from gtools was corrupt. Deleting all the channels & frequencies (leaving only the satellites) & downloading this to the fortec put everything right.
The original corruption may have been caused by bouncing from old to new Ver 273 firmware?? Then down loading the channel settings to gtools.
Willo

[bassett]

Glad your back and working,,

Thanks for the tip, Si' I never even thought about zipping the file, it's very small, but if that will allow it to excepted, by the forums software, i will remember that next time.

[WyrTwister]

All is fixed now! this is what I did
As explained in my second post I tried to load Ver 235, left me with Knight Rider display. Just before I was about to solder in the resistors for the JTag connection, thought I might try ALBar Ver 231, result was software loaded & I had a working receiver.
Tried to upgrade to a more recent software version but could not, until I reset to factory default (System Setting Menu). Now with version 273 software I set about downloading my saved channel settings using gtools. After downloading from gtools finished the receiver was locked up again & back in the endless loop thing.
End result was my saved settings from gtools was corrupt. Deleting all the channels & frequencies (leaving only the satellites) & downloading this to the fortec put everything right.
The original corruption may have been caused by bouncing from old to new Ver 273 firmware?? Then down loading the channel settings to gtools.
Willo




Probalt the majority of these kinds of problems are caused by messing with channel lists .

enough said .

Wyr

[happyhound]

What is a J-Tag and what does it do ? Just curious.

[simmo]

jtag enables you to directly access the prom and change things, or put things back to the way they were intended.
I 'spose it could be thought of as something like a format of C-Drive...(or prolly the bios!)

[WyrTwister]

What is a J-Tag and what does it do ? Just curious.



Last resort fix for a Set Top Box , when you REALLY mess up the box
and can not fix it with the RS-232 cable .

Been there , done that .

Wyr
.

[bassett]

I really can't understand why anyone would want to install a channel list, when you have a blind scan receiver.. It's counter productive.

Whats wrong with doing a BLIND scan on every satellite you can access.

Or am I missing something, ??????

[WyrTwister]

I really can't understand why anyone would want to install a channel list, when you have a blind scan receiver.. It's counter productive.

Whats wrong with doing a BLIND scan on every satellite you can access.

Or am I missing something, ??????


You are pretty much correct .

Wyr

[simmo]

Yeah, agreed, in a way... But there are some things the box wont pick up. So if you load the missing ones to your list, edit and load your channel list, a blind scan will simply add to it.

[Ocean]

I have to agree with the simmo bloke...I installed various channel lists from him and the receiver responded to several services NOT FOUND on a blind scan. Some of these signals gave solid reception, but a blindscan repeatedly ignored them.

[WyrTwister]

I have to agree with the simmo bloke...I installed various channel lists from him and the receiver responded to several services NOT FOUND on a blind scan. Some of these signals gave solid reception, but a blindscan repeatedly ignored them.


I have been told in North Amarica , it may be Digicypher channels , which a FTA receiver can not understand .

Is it possable that it might be something like that , on your side of the world ?

Wyr

[bassett]

No there are a few services that won't load, no matter what you do, But I really think it's a conflict thing emanating from different software versions, Some versions load just about everything, others are very "picky"