Identifying Bootloaders

[abu baniaz]

Is it possible to identify which bootloader a person is using? If so how? (Excluding the rs232 logging tool).

If not currently possible, is it theoretically possible to add some kind of description while it boots?

Thanks in advance.

[Larry-G]

Is it possible to identify which bootloader a person is using? If so how? (Excluding the rs232 logging tool).

If not currently possible, is it theoretically possible to add some kind of description while it boots?

Thanks in advance.

I dont beleive so, you would have to generate a bootlog with a rs232 cable and the putty program. I Could be wrong however.

Sent from my GT-I9300 using Tapatalk 2

[Rob van der Does]

Correct: a bootlog will show some info about the bootloader.

[abu baniaz]

I suppose when in doubt, install latest one.

It would be nice if someone in a position to do so could ask the Koreans if they can add some identifying code that could be picked up in debug/crash logs or even during bootup.

[Larry-G]

This is not a receiver specific problem it's the same among every STB. the only way to retrieve this info is via a bootlog generated using a RS232 cable and a putty session. as far as i know there is no other way to output this data while the box is actually running. again i could be wrong on that though.

[Rob van der Does]

You're again correct Pheonix

[Larry-G]

You're again correct Pheonix

~ insert expletive here ~ ,me being rite twice in a row in the same thread ? something wrong there somewhere LOL.

[Rob van der Does]

~ insert expletive here ~ ,me being rite twice in a row in the same thread ? something wrong there somewhere LOL.

Good to see we agree here

[Larry-G]

good to see we agree here :d

no comment.

[Mr. Mister]

~ insert expletive here ~ ,me being rite twice in a row in the same thread ? something wrong there somewhere LOL.

Some people would start to call you a smart arse.. lmao

[Larry-G]

Some people would start to call you a smart arse.. lmao

been called far worse LOL.


( waits for the telling off for taking this thread off topic again ).

[Rob van der Does]

Guys, can we please stay on topic

[scruff1963]

Having a way of identifying the bootloader would be a good idea.

The new 4d image has a bootloader with it which is a good idea now but a few months down the line it will be putting it on to boxes possibly overwriting what will be the current bootloader then.

It may seem a good idea now but it's not future proof and very short sighted.

It's the main reason I havn't bothered to try the 4d image, if they are not looking to the future then how much attention have they paid to the image itself.

[abu baniaz]

I'd like to disagree with the comments made so far about being unable to display details.

Reason being is that the text that appears before flashing an image has changed several times. It should therefore be possible to add some text during the boot stage. A simple version description is that is required. Such as "Boot v 2.56"

[Larry-G]

I'd like to disagree with the comments made so far about being unable to display details.

Reason being is that the text that appears before flashing an image has changed several times. It should therefore be possible to add some text during the boot stage. A simple version description is that is required. Such as "Boot v 2.56"

There is currently no way of reading from the bootloader to display bootloader details in any form while the receiver is running, this data can only be accessed during the initial bootup and only via a putty / rs232 bootlog via a connected computer. The text that displays before, during or after flashing a image has nothing to do with bootloader details.