bricked s10

[Gaastra]

sorted mine thanks to all on this thread.

[slugworth]

ini

try this one on stubborn receivers.

that one had the same .ini and eromclient.abs as other loaders,but must have something different in the .exe that is more effective.
I have seen others that had to have manual selection of the .ini
and eromclient.abs,based on the receiver processor type and amount of ram installed.

[termiantor]

didnt work for me

[slugworth]

basket case

maybe he tried loading firmware from another brand of receiver?If the bootloader section in flash is wrong that would pose a big problem.

[slugworth]

boot

Actually the bootloader section makes no difference in recovery.I had one instance where the bootloader section was all garbage and I was still able to recover.The v2.0.0c lets you take a full dump of even a dead receiver,and looking at the dump with a hex editor I saw the corruption.If the loader doesn't work you either have the wrong cable,com port problem on the pc or the receiver has a bad power supply.
Since it is so easy to recover,I tried 4meg firmware from euro brands on it,but it wouldn't boot.

[cartwheelbob]

Thanks, needed this

[northern2012]

well just updated my channel list the ON was there turned box off dead nothing no lights check fuse all was ok tryed will pc no joy so tryed with laptop and its ALIVE once again so thanks goes to slugworth

[ziggycat]

Actually the bootloader section makes no difference in recovery.I had one instance where the bootloader section was all garbage and I was still able to recover.The v2.0.0c lets you take a full dump of even a dead receiver,and looking at the dump with a hex editor I saw the corruption.If the loader doesn't work you either have the wrong cable,com port problem on the pc or the receiver has a bad power supply.
Since it is so easy to recover,I tried 4meg firmware from euro brands on it,but it wouldn't boot.

Hiya mate, I've have a box that just won't recover from 'on', you name it and I've tried it. I've tried every bootloader out there and all available firmwares, I've swapped powers supply boards & com interface's from working boxes, and every single time get 'stb memory error'.

Other boxes connect fine on the same com port with a null modem cable.

If your the same member from sataid, did you ever have any success with replacing/reprogramming the u39 chip, as this looks like the only option left.

cheers.

[slugworth]

I never got a chance to use the blanks,since I never killed my receiver 100% yet.
Stb memory error usually means a mismatch between the eromclient.abs and your actual box guts.(memory or processor)You must use loader v2.0.0c with the eromclient.abs that was 56k size.You have to start the loader then casually turn the receiver on in the back.
If you turn the receiver on first or too fast,forget it.

[ziggycat]

Already tried the 2.0.0c loader with the eromclient.abs(56k). I have read elsewhere that it's an sdram problem, and I'm inclined to believe this to be the case.

Completely unrecoverable no matter what I try, other boxes work fine with several different bootloaders.

guess I'll just trash it as I've spent way too much time on a box that only costs ?60.

[mast]

Hi

Ive got 2 boxes with similar problem tried every loader going and different time combinations even tried a different desktop and a lappie too all with same results.

1) Set stb memory error.

2) Check serial port status, opening of serial port failed.

Cable is null cable that works fine and just to be sure backed up from my dream via dreamup. Also tried another null cable.

Have tried different psu but no joy, hoping to fix them eventually.

Regards

[slugworth]

sounds like a pc related problem,especially #2 mentioned.
Don't use a usb to serial converter,use a pc with a real comport.

[mast]

sounds like a pc related problem,especially #2 mentioned.
Don't use a usb to serial converter,use a pc with a real comport.

Hi

Not pc related as they are all with dedicated serial port and I have used them many times over the years. Also the fact that to verify com port is working did a backup of my dream with both desktops unless Im missing something. Even tried different settings in loader.

Actually what are good settings bit rate, parity etc. I want to try and dump from these boxes if I can so I can have a look.

Is there any particular loader you can recommend or a way to check com port rather than the way Im checking.

Regards

[slugworth]

in certain instances you can run a terminal program and you might see a response,like app init ok but on really dead ones you get nothing.I use the default settings of 115200 baud 8bit N parity 1 stop bit.

[imrani2003]

HDMI Cable was butchered

The HDMI cable was butchered on my box, and caused this same issue, initially I thought it was the fuse in the plug, which I obviously swapped out, then inspected the internal thermal fuse, which, sure enough was working fine. NOW I will try this, and all being well, I will be successful!!!


Thanks to you guys who have posted the software and all responses, they will be a real big help, I am sure!


Thanks

Jack Jack