Reason why UCode_001A won't work on a Sagem Dbox, but will work on a different Sagem?

trbd

Banned
Joined
Apr 19, 2007
Messages
146
Reaction score
1
As title really, I have 3 x Sagem dboxes in the house, and have created my own tweaked image. I have restored this image onto the other two boxes (so all 3 have the same image) but one of the boxes will refuse to pick up a signal using 001A (just get waiting for time / channel not available). The other two boxes work fine on 001A and are identical hardware (as far as I know).

I have uploaded 0014 onto the troublesome box and it fixes the issue, but I find 0014 stutters more than 001A.

Is there a logical reason for this?
 
They are all 1X Sagem boxes. What do you mean by Bmon version exactly?
 
They are all 1X Sagem boxes. What do you mean by Bmon version exactly?



when it first boots and your on the dataresearch screen on the LCD one of the lines says BMON with a number after it, like 1.10 (afaik it is the firmware for the boot loader or something) what does it say on yours
 
I'll have a look when I get home mate. Is it a hardware or a software setting in the bootloader I can change?
 
Arkward box is BMon 1.2
Working box is BMon 1.3

Any more input? Can I update the 1.2 box to 1.3 via flash with bootloader?

Is it a case of "Read full image" from a working box then "Write full image" on the troublesome box?


Edit - Just tried that. Image came off the working box fine, but when I went to the dodgy box I get "Can't Open MTD Device".

Do I need to use IFA?

Edit - Just tried with IFA and tells me that the image is a 2x version and the box is 1x. The image came from an identical 1x box, so I'm stumped. If I open the supposed 2x image in ImageWorks it tells me that its a 1x with bootloader...
 
Last edited:
Back
Top