Null modem flash

[Shady]

Yeah i know right.. shady asking for help? weird..


BUT im having a hell of a game flashing the old s10 with a null after the "on" error.

Let me talk you through what ive tried.

Try 1: windows 8.. usb null modem.. result. hung at x %
Try 2: " " parity even on null modem and even on eerom.. result hung at x %
Try 3 : same as before but all reset to defaults and different firmware. result hung at x %

Try 4: windows 7 pc, proper built in serial, proper null modem cable, result hung at x %

try 5: win xp null modem cable.. hung at x %

Have tried different fw have tried different combinations of eerom upgrade and com port settings, different null modems, different os's and now im stuck...

help me dk, youre my only hope

[Shady]

oh yeah.. also tried different time lags between switching power on..

[mdt]

does the s10 do stb to stb transfere? if so you could try that if you have access to another s10,regards mdt

[slugworth]

try an old pc with win xp
use the default settings
I assume the pc has a real serial port,the loader won't work(in most cases) with a usb converter.

[Shady]

No access to second box, yeah the last PC tried was an old one with xp on. Its weird, the same problem of the download hanging, but its always at a different percentage. One time could hang at 20% second time will hang at 90% third time 56% . Its frustrating 3 diff pc s 3 diff is 2 diff cables. Multiple variations of time before switching box on...

Sent from my telegraph using Morse code

[slugworth]

the loader will give you many minutes to turn the receiver on.
The loader must be v2.0.0c,the one where you choose the file to load on the initial screen.
There are bogus v2.0.0b and v2.0.0c loaders out there that look like v2.0.0f and just have upgrade or data dump choices on the initial screen.You must tick include bootloader.

[Shady]

Used the loader from here its the correct one. Longest I left it before turning on was probably about 2 mins.. I'll give it a go with a much longer lag and report back
oh yeah.. i always have ticked "include bootloader"
Sent from my telegraph using Morse code

[Shady]

tried again today.
first time i got to 100% on download bar and got thru to the burn stage. it failed here, now im back to the same problem of the download freezing at different percentages and the display changing from "on" to "6000" when it does freeze. im about to f@@k the bassad up the wall

[Shady]

tried a different version of erom upgrade 2.0.0f ? or something, got error bootloader or main code version not compatable

got it to 100% again after leaving it for half hour before switching it on, but burn failed again

[Shady]

one last try and then its the bin for it. ill replace it with a dm 500.

[JapCarMad]

I know this is probably a long shot and gut feeling i'd say the box is probably eff'd but would there be a possibility it's your cable? Is it brand new or good quality?

[Shady]

the cables fine, reflashed a mates 500s with it

[digicon]

Shady i think what this needs is a night off from having a go with it, Leave it till tomorrow Clear your head and have another bash with a fresh perspective tomorrow.

Certainly worked for me in the past

[Shady]

Its sat there atm.. taunting me. Youre right, if i carry on tonight im going to slit my wrists

[mtv1]

the loader will give you many minutes to turn the receiver on.
The loader must be v2.0.0c,the one where you choose the file to load on the initial screen.
There are bogus v2.0.0b and v2.0.0c loaders out there that look like v2.0.0f and just have upgrade or data dump choices on the initial screen.You must tick include bootloader.

can i send my s9 to you mate i'll pay return post

i've tried all loaders all tricks mentioned no result

i'm with shady on this one there's a time to throw in the towel

put it in the attic till another fix comes on hopefully