Posts by u_r_no_1

    hi, it happened to me once too... the reason is certainly the kernel which is not compatible with the soft that you sent previously,


    1* you have to keep your thumb on the Red LED... and turn on the power ...you will have to do this several times until it works...a friend of mine confirmed that he was able to revive with my backup but he only sent the file...(rootfs.tar.bz2)...any will do doft with that file,


    2* you just have to press your thumb on the red LED and turn on the power, if not there is only another way (mini usb) as is done with 800se...but you have to download the driver for the mini usb.

    hi, Thank's for your attention


    the box is already goes to rescue mode by turning on the device

    but how can i send the (rootfs.tar.bz2) ?

    and where can i find or download this?

    1* what PC do you use...??


    2* the front lights up...only red LED,


    3* if you are near Milan I can give you a hand....and then if you can use DCC to enter the decoder to change the boot folder...I have I did a similar thing on Mutants 51 4k, I managed to restore it with the files that I posted on a forum that I changed in the decoder and it worked restored by installing soft with USB.

    1. i'm using a dell pc

    2. yes just red light and DREAMBOX logo on Pannel

    3. no i'm not near yo bro

    i found the problem :

    Code
    [*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery.sig'
    [*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery'
    [*] Verifying signature of 'recovery'
    gpgv: Signature made Mon Dec 11 21:41:43 2017 UTC using RSA key ID B3C5B1A3
    gpgv: Good signature from "Dreambox DM920 Recovery <dm920@recovery.dreambox.de>"
    [*] Running './recovery'
    [*] Options '-v'
    Fatal: Target device '/dev/mmcblk0p2' is not writable
    Fatal: Failed to execute './recovery'

    look, the default target device is /dev/mmcblk0p2 but in my device all addresses are something else (mtdblock0,1,2,3,4) :


    :thinking face: :thinking face: :thinking face:

    HOW IT CAN BE ???

    :hushed face: :hushed face: :hushed face:



    Disk /dev/mtdblock0: 2 MB, 2097152 bytes

    255 heads, 63 sectors/track, 0 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes


    Disk /dev/mtdblock0 doesn't contain a valid partition table


    Disk /dev/mtdblock1: 0 MB, 131072 bytes

    255 heads, 63 sectors/track, 0 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes


    Disk /dev/mtdblock1 doesn't contain a valid partition table


    Disk /dev/mtdblock2: 0 MB, 131072 bytes

    255 heads, 63 sectors/track, 0 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes


    Disk /dev/mtdblock2 doesn't contain a valid partition table


    Disk /dev/mtdblock3: 14 MB, 14417920 bytes

    255 heads, 63 sectors/track, 1 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes


    Disk /dev/mtdblock3 doesn't contain a valid partition table


    Disk /dev/mtdblock4: 33 MB, 33554432 bytes

    255 heads, 63 sectors/track, 4 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes


    Disk /dev/mtdblock4 doesn't contain a valid partition table

    fdisk: can't read from /dev/mmcblk0

    i already tried this :

    sgdisk /dev/mtdblock0 -z -n 1:2048:65535 -c 1:kernel -t 1:8301 -n

    2:65536:4194303 -c 2:rootfs -t 2:8307 -n 3:4194304: -c 3:data -t 3:8300


    but this is the output :


    root@dm920:~# sgdisk /dev/mtdblock0 -z -n 1:2048:65535 -c 1:kernel -t 1:8301 -n

    2:65536:4194303 -c 2:rootfs -t 2:8307 -n 3:4194304: -c 3:data -t 3:8300

    Creating new GPT entries.

    Warning: The kernel is still using the old partition table.

    The new table will be used at the next reboot or after you

    run partprobe(8) or kpartx(8)

    GPT data structures destroyed! You may now partition the disk using fdisk or

    other utilities.

    Could not create partition 1 from 2048 to 65535

    Setting name!

    partNum is 0

    REALLY setting name!

    Unable to set partition 1's name to 'kernel'!

    Could not change partition 1's type code to 8301!

    Could not create partition 2 from 65536 to 4194303

    Setting name!

    partNum is 1

    REALLY setting name!

    Unable to set partition 2's name to 'rootfs'!

    Could not change partition 2's type code to 8307!

    Could not create partition 3 from 4194304 to 4062

    Setting name!

    partNum is 2

    REALLY setting name!

    Unable to set partition 3's name to 'data'!

    Could not change partition 3's type code to 8300!

    Error encountered; not saving changes.

    hi

    i was flashing newnigma2 image on my dm920 but after reboot, red light on pannel is on and it's not working.

    i tried to flash it again but it seems the device is completely down :


    Console log :


    PLEASE HELP ME  :loudly crying face: :loudly crying face: :loudly crying face:


    output of : fdisk -lu is :


    root@dm920:~# fdisk -lu


    Disk /dev/mtdblock0: 2 MB, 2097152 bytes

    255 heads, 63 sectors/track, 0 cylinders, total 4096 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mtdblock0 doesn't contain a valid partition table


    Disk /dev/mtdblock1: 0 MB, 131072 bytes

    255 heads, 63 sectors/track, 0 cylinders, total 256 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mtdblock1 doesn't contain a valid partition table


    Disk /dev/mtdblock2: 0 MB, 131072 bytes

    255 heads, 63 sectors/track, 0 cylinders, total 256 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mtdblock2 doesn't contain a valid partition table


    Disk /dev/mtdblock3: 14 MB, 14417920 bytes

    255 heads, 63 sectors/track, 1 cylinders, total 28160 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mtdblock3 doesn't contain a valid partition table


    Disk /dev/mtdblock4: 33 MB, 33554432 bytes

    255 heads, 63 sectors/track, 4 cylinders, total 65536 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mtdblock4 doesn't contain a valid partition table

    Found valid GPT with protective MBR; using GPT


    Disk /dev/mmcblk0: 15269888 sectors, 3360M

    Logical sector size: 512

    Disk identifier (GUID): 0f0f33f9-4c5a-4efd-946a-9d281bb4426d

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 15269854


    Number Start (sector) End (sector) Size Code Name

    1 2048 65535 31.0M 0700 kernel

    2 65536 4194303 2016M 0700 rootfs

    3 4194304 15269854 5407M 0700 data


    Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes

    4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mmcblk0boot1 doesn't contain a valid partition table


    Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes

    4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors

    Units = sectors of 1 * 512 = 512 bytes


    Disk /dev/mmcblk0boot0 doesn't contain a valid partition table