Results 1 to 5 of 5
  1. Thread Author  Thread Author    #1  

    Default SBF Package and Restore Tool for Motorola Admiral

    Just in case the unthinkable happens, I would like to have in my toolkit the SBF Package and Restore Tood for my new Motorola Admiral.

    I can't seem to locate it and was hoping for some help and maybe a link.

    Best regards,
    -boggsie
  2. #2  

    Default Re: SBF Package and Restore Tool for Motorola Admiral

    Don't know what exactly you're referring to.

    There's an app called Titanium backup that can do backups and restores. It requires root. The free version make you back up apps one at a time. The paid version let's you do them all at once.
  3. Thread Author  Thread Author    #3  

    Default Re: SBF Package and Restore Tool for Motorola Admiral

    SBF Packages come from the phone manufacturer or vendor, in this case, either Motorola or Sprint. You trigger fastboot on the phone and then a specific utility on the PC can push the source image (*.SBF file) to the phone, via USB. The SBF presumably includes everything except for the bootloader.

    If, for example, I wanted to experiment with a custom recovery application, say CWMR, I would want to have a method to restore the phone back to stock, just in case my experimentation clobbers something.

    Basically a step towards being able to load and AOSP, CyanogenMOD or maybe even MIUI (now that it is open sourced) ROM.

    Best regards,
    -boggsie
  4. #4  

    Default Re: SBF Package and Restore Tool for Motorola Admiral

    I am also looking SBF for Motorola Admiral.
    Anybody can help me?
  5. #5  

    Default Re: SBF Package and Restore Tool for Motorola Admiral

    Hi! I continue to work with the phone.
    Now I have two devices Motorola Admiral, one fully working, and the second was the donor (since the brick itself - on the Motorola logo is not loaded). Online firmware on it is not present, so carefully study the working staff - I hope to restore the "brick."
    So, what was done:
    1. Defined sections (on working device):
    Code:
    cat /proc/partitions
    major minor  #blocks  name      alias
    179        0    3864576 mmcblk0
    179        1        512 mmcblk0p1      p1
    179        2        500 mmcblk0p2      p2
    179        3       1500 mmcblk0p3      p3
    179        4          1 mmcblk0p4      p4
    179        5      65024 mmcblk0p5      p5
    179        6      47000 mmcblk0p6      fat
    179        7       1024 mmcblk0p7      appsbl
    179        8       3072 mmcblk0p8      modem_bkp
    179        9       7000 mmcblk0p9      adsp
    179       10       3072 mmcblk0p10     modem_st1
    179       11       3072 mmcblk0p11     modem_st2
    179       12        768 mmcblk0p12     hob
    179       13       4096 mmcblk0p13     pds
    179       14        512 mmcblk0p14     dev_tree
    179       15       5120 mmcblk0p15     apps
    179       16     460800 mmcblk0p16     system
    179       17    1055744 mmcblk0p17     userdata
    179       18     406528 mmcblk0p18     cache
    179       19       7168 mmcblk0p19     recovery
    179       20        512 mmcblk0p20     misc
    179       21       1024 mmcblk0p21     logo
    179       22       2048 mmcblk0p22     kpanic
    179       23      20480 mmcblk0p23     cdrom
    179       24       2048 mmcblk0p24     bpanic
    179       25    1373184 mmcblk0p25     sdcard
    179       32   15558144 mmcblk1
    179       33   15554048 mmcblk1p1
    2. Made a backup via adb (on working device, write files to external SDCARD):

    Code:
    dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard-ext/recovery/pds_block13.ext3
    dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard-ext/recovery/boot_apps_block15.img
    dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard-ext/recovery/system_block16.ext3
    dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard-ext/recovery/userdata_block17.ext3
    dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard-ext/recovery/cache_block18.ext3
    dd if=/dev/block/mmcblk0p19 of=/mnt/sdcard-ext/recovery/recovery_block19.img
    3. "Brick" has translated into fastboot, it's OK

    4. "Brick" accept fastboot commands, but when trying to write system.ext3 an error (on different versions of fastboot different errors):
    These two versions immediately return errors:
    Code:
    C:\ADB\NEW\recovery>fastboot flash system system.ext3
    sending 'system' (460800 KB)...
    FAILED (remote:  ERROR: 0000000E 000004B6)
    finished. total time: 0.006s
    
    C:\ADB\NEW\recovery>mfastboot flash system system.ext3
    sending 'system' (460800 KB)...
    FAILED (remote:  ERROR: 0000000E 000004B6)
    finished. total time: 0.001s
    This version sends differrent file size and then after many minutes an error:
    Code:
    C:\ADB\NEW\recovery>moto-fastboot flash system system.ext3
      sending 'system' (262144 KB)... OKAY [ 33.650s]
    writing 'system'... FAILED (status read failed (Too many links))
    Here, when you send the whole file at once an error when trying to send chunks of 8MB gives another error and the phone screen falls message Err: 0x000A:
    Code:
    C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe flash system c:\adb
    \new\recovery\system.ext3
    sending 'system' (460800 KB)...
    FAILED (remote:  ERROR: 0000000E 000004B6)
    finished. total time: 0.005s
    C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe -S 8M flash system
    c:\adb\new\recovery\system.ext3
    Invalid sparse file format at header magi
    sending sparse 'system' (8180 KB)...
    OKAY [  0.765s]
    writing 'system'...
    FAILED (remote:  ERROR: 00000002 0000026A)
    finished. total time: 0.872s
    When lights logo, sometimes the phone a short time (a few seconds, on device manager windows) is put ADB (I still can not understand how this happens).

    Can anybody tell me why I can not burn the image via fastboot?

Posting Permissions

B