->error on dm800 oled display HELP!

A

alpa

Registered
Messages
49
I have problem, my original dreambox displays “->error” message on the oled display and I cannot flash it even with dreamup
Here is what happened:
-I restarted the box
-box started booting, but it took too long so I decided to disconnect from the electricity and to try again
-when I plugged in the electricity again there was the ->error message and it remain there ever since
-I tried to flash the image via dreamup 1.3.3.5 but it did not come to flash option, it said waiting acknolidgement from the box but there was showing -> error message on oled instead of response.
-I tried older versions of dreamup and those gave me option to flash but so far without luck
--here is what the dreamup log said:
Log: +++ 006 write failed, at 00000000: ff. Block will be marked as bad. <=====this is for many addresses
Flashing failed (!!! 005 too much data (or bad sectors) in partition 1 (end: 00040000, pos: 00040000)), box will be unusable now!!


I tried with the oldest cvs image and with the latest image but unsuccessfully
Also tried recovery of bad sectors also but that did not worked either.

Please help
 
Last edited:
J

janielsen

Registered
Messages
228
try this pull te power from the transformer nor the plug behind the box but from the transformer wait 1 min then put power bac on
 
B

busman

Donating Member
Messages
127
use dreamup or enforcer inside 2nd_stage_pack file
work every time on clone or original
 
A

alpa

Registered
Messages
49
xmen said:
plz here look

http://www.sat-universe.com/showthread.php?t=149798
Click to expand...

I cannot upload even secondstage:
heres log from dreamup:
104451 box type DM800
104715 Calculating checksum...
104717 Uploading file to box...
104731 box is flashing from its memory...
104732 Log +++ 006 write failed, at 00000000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00004000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00004000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00008000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00008000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 0000c000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 0000c000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00010000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00010000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00014000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00014000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00018000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00018000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 0001c000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 0001c000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00020000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00020000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00024000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00024000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00028000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00028000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 0002c000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 0002c000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00030000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00030000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00034000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00034000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 00038000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 00038000 ff. Block will be marked as bad.
104732 Log +++ 006 erase failed at 0003c000 ff. Block will be marked as bad.
104732 Log +++ 006 write failed, at 0003c000 ff. Block will be marked as bad.
104732 Flashing failed (!!! 005 too much data (or bad sectors) in partition 1 (end 00040000, pos 00040000)), box will be unusable now!!
 
A

alpa

Registered
Messages
49
busman said:
use dreamup or enforcer inside 2nd_stage_pack file
work every time on clone or original
Click to expand...

I'm using dreamup allthe time.No luck so far.
Can you please give me more details about enforcer, where to get it and how it works.
 
B

Brummie

Staff member
Administrator
Messages
5,794
have you tried to recover the bad sectors with dreamup, click on extra.
 
Ferret

Ferret

Marching On Together !
Staff member
Administrator
Messages
17,534
I does look to me as though the memory has had it.

You say your DM is a original, if so start a ticket with DMM they don't like to see this type of fault the may fix it FOC.

Ferret
 
B

busman

Donating Member
Messages
127
alpa said:
I'm using dreamup allthe time.No luck so far.
Can you please give me more details about enforcer, where to get it and how it works.
Click to expand...

here go mate h**p://rapidshare.com/files/359788835/2nd_stage_pack.rar.html
 
You must log in or register to reply here.
Top