View Full Version : Bricked Box any help appreciated
c_slater_1
30th March, 2012, 12:02 PM
Hi,
I have read all of the other threads and could not see any with the error message that I am getting so thought id ask to see if anyone has any new ideas.
I am 99.9% sure that I have bricked the box and is not a hardware issue because I loaded a new f/w that was not clone safe (idiot I know) but all the other boxes I have bought from the same supplier have been origional so I thought id be ok (my own for for having any faith), sods law this is the first clone I have received and I brick it.
I have tried using the bootloader program and am getting the error shown in the screen shot. "initialize STB rdram is failed."
I think im using the correct com port and have the corect settings but this is the only message I receive, any other settings dont display any text other than "synchronizing STBs" but this is displayed when nothing is connected.
I have read about letting it flash the box why it is turned off and then turning the box on but I dont understand how this can work so if anyone can explain that would be great? Also how to do it beacuse im unsure on this.
So has any one any ideas what I can try? Or is the box just dead?
Thanks for any help in advance
Manic01
30th March, 2012, 01:16 PM
http://www.digital-kaos.co.uk/forums/f184/openbox-s9-stuck-227099/
c_slater_1
30th March, 2012, 02:15 PM
Thanks for the link
I have had a look at that thread and am already using the version of the software that it suggests and I am also doing this on a PC so not using any USB adaptor.
As soon as I turn power on the error message appears instantly.
I have just looked at the port settings and they are 9600 and none - Do these need to be changed to 115200 and even?
Any other suggestions will be appreciated
Thanks.
Manic01
30th March, 2012, 02:47 PM
Com1 and 115200 I think.
Manic01
30th March, 2012, 02:54 PM
1. download the latest safe file.
2. dont use a usb to serial converter (use a machine with a native com port and a null modem cable).
3. launch the EpromUpgrade.exe file > Select the .abs' firmware file > tick 'Include Bootloader'4. the box should be switched 'off', the click 'Next'
5. switch it on and let it upgrade.
After displaying ON then Boot it should show 'NoCh'
This means its ok and channels can be scanned.
c_slater_1
30th March, 2012, 02:59 PM
Thanks for the reply.
I have changed the com port setting to match the ones in the loader program and have followed your instructions and I am still getting the same error as soon as the power is switched on.
How long should it take to flash the box or should it display some text where the error apears if it is going to work?
Manic01
30th March, 2012, 03:03 PM
Delete your com port setting s in device manager and let it find itself again.
c_slater_1
30th March, 2012, 03:28 PM
I will give that I go on Monday im away all weekend but I will let you know how I get on then.
Thanks for your help with this
mast
30th March, 2012, 08:20 PM
Delete your com port setting s in device manager and let it find itself again.
Hi
Thats a new suggestion although my com port flashes the dream 500s just fine but Il give this a try as I need to try and get 2 openboxes going.
Regards
mast
2nd April, 2012, 09:41 PM
Delete your com port setting s in device manager and let it find itself again.
Hi
Soz m8 didnt work for me, will keep trying. Any other suggestions keep them coming.
Regards
slugworth
3rd April, 2012, 01:46 AM
when you see synchronizing on screen then you turn the receiver on in the back.Some people turn it on too fast.
mast
3rd April, 2012, 10:40 AM
when you see synchronizing on screen then you turn the receiver on in the back.Some people turn it on too fast.
Hi
Im doing everything as I should with different timings but no joy
sometimes "done" come up instantly and then the errors.
One is the set stb error and one is opening of serial port failed.
I know the coms on the desktop work fine as I used a port monitoring software and also connected my dream and as soon as its switched on all the activity is logged and also did a backup of the dream using same cable and port.
Anyway slugworth you get around cos over the past few days while doing google searches for any info on this your name has popped up in a few places and Ive come across one of your uploads " really dead s10 fixer " which Im going to try.
Regards
slugworth
3rd April, 2012, 03:53 PM
I kill my receiver almost every day trying oddball firmware,and the 2.0.0c loader has never let me down.
I am always able to recover.
When I first bought the receiver I bought blank flash chips also just in case,but I never had to use them.
slugworth
3rd April, 2012, 04:01 PM
mentioned before,but on a good working receiver the secret diag menu has an rs232 test option.(info screen in menu then hit 11111) The rs232 test is used with a terminal program on the pc to test the rs232 port in the receiver & pc,and to make sure you are using the correct cable.After selecting the test you have about 20 seconds to type on the pc keyboard (in a terminal program) and the goods should show on the tv screen in that menu option.This makes sure the cable and comport are copasetic.
c_slater_1
16th April, 2012, 11:39 AM
Sorry for such a late reply to this but thanks everyone for all the suggestions.
I finally gave up on trying to rescue the box and sent it back to the supplier, lucky for me they where good enough to send me a replacement.
I think I will be sticking to clone safe firmware from now on.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.