Hacking erroneous output of SBF Codec

Discussion in 'Droid Labs' started by MotoCache1, Sep 8, 2010.

  1. Jharmon12

    Jharmon12 Member

    Joined:
    May 4, 2010
    Messages:
    257
    Likes Received:
    0
    Trophy Points:
    16
    Ratings:
    +0
    I was working on my own custom logo sbf and i decided to look at the RDL3 file and i changed what it said when you install it. I changed the updating software to installing boot logo and changed update complete to Press up now. Heres the sbf if you want to look at it :) im thinking about changing it to say hold up now but I wanna see what everyone else thinks first.
     

    Attached Files:

  2. fish1552

    fish1552 Premium Member
    Rescue Squad Premium Member

    Joined:
    Mar 16, 2010
    Messages:
    653
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Savannah area of Coastal Georgia, USA
    Ratings:
    +17
    Guess I had to take care of some stuff offline at a very bad time. Coming back to this thread and seeing all the new updates is amazing.

    Good work guys!
     
  3. mcf517

    mcf517 New Member

    Joined:
    Mar 13, 2010
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Is this applicable to stock sbf flashing?

    I have been patiently and diligently perusing many forums and exhausted many avenues of possible solutions. My droid x currently is in a strange state that has not been typical for most rom flashers and I humbly ask for suggestions and advice.

    The system reads that I'm on gingerbread 4.5.573, which is the first leaked version of gb. The only way to get anywhere at that point is to sbf back to stock 340 froyo. I keep getting checksums errors on multiple tries on various computers including windows xp, 7, and even Linux.

    Here are the very peculiar symptoms my phone has exhibited that I don't see on any other forums. When I reboot, the system goes back to the way it was before I failed the first attempt on flashing back to 340. Apps installed go missing while uninstalled apps go back. Icon placement, ringtones, etc... All just go back to how I had it up until that point. It seems an image of the system was saved at a certain point and now is always being restored when i reboot, making my phone pretty crippled. I maintain root access, but using bootstrap only reboots my phone and never gets access to custom recovery. Factory reset also does nothing, including the ones inside the stock recovery. I have even wiped data and factory reset up to ten times each.

    My boot loader is version 3004 and I boot with a red m logo which is gb. The flashing process passes some checksums, which still manage to reset the activation status of my phone. I always have to deactivate via *228 when I ultimately fail to flash 100%.

    Here is my error log from Linux while attempting to flash the sbf....

    === VRZ_MB810_2.3.34_1FF_01.sbf ===
    00: RDL03 0x82000000-0x8204CFFF 4D63 AP
    01: RDL01 0x00150000-0x001FFFFF DEFA BP
    02: *CG03 0x00000000-0x008FA367 8A11 BP
    03: *CG31 0xB0280000-0xB02847FF 56E0 AP
    04: *CG33 0xB1900000-0xB24C07FF 4125 AP
    05: *CG34 0xB0700000-0xB07047FF 75F3 AP
    06: *CG35 0xB1000000-0xB13FFFFF A91B AP
    07: *CG39 0xB2A00000-0xC41C07FF 4432 AP
    08: *CG40 0xC4200000-0xC4200FFF FDFF AP
    09: *CG42 0xB0800000-0xB083FFFF 7479 AP
    10: *CG47 0xB1400000-0xB18FFFFF 0255 AP
    11: *CG61 0xB0B00000-0xB0B7FFFF 9804 AP
    12: *CG64 0xB0000000-0xB00047FF 1768 AP
    13: *CG65 0xB0180000-0xB01847FF 7167 AP
    14: *CG66 0xD0000000-0xD7BA87FF 021A AP

    waiting for phone: Connected.
    uploading RDL03: 100.0%
    -- OK
    verifying ramloader
    -- OK
    executing ramloader
    -- OK
    waiting for phone: Connected.
    sending erase
    -- OK
    uploading CG31: 100.0%
    -- OK
    uploading CG33: 100.0%
    -- OK
    uploading CG34: 100.0%
    -- OK
    uploading CG35: 100.0%
    -- OK
    uploading CG39: 100.0%
    -- OK
    uploading CG40: 100.0%
    -- OK
    uploading CG42: 100.0%
    -- OK
    uploading CG47: 100.0%
    -- OK
    uploading CG61: 100.0%
    -- OK
    uploading CG64: 100.0%
    -- OK
    uploading CG65: 100.0%
    -- OK
    uploading CG66: 100.0%
    -- OK
    verifying CG31
    Checksum error (Expected 0x56e0, Got 0xb9a8)
    !! failed
    verifying CG33
    Checksum error (Expected 0x4125, Got 0x48da)
    !! failed
    verifying CG34
    -- OK
    verifying CG35
    Checksum error (Expected 0xa91b, Got 0x63d9)
    !! failed
    verifying CG39
    Checksum error (Expected 0x4432, Got 0xea05)
    !! failed
    verifying CG40
    Checksum error (Expected 0xfdff, Got 0xaf0f)
    !! failed
    verifying CG42
    Checksum error (Expected 0x7479, Got 0xac60)
    !! failed
    verifying CG47
    Checksum error (Expected 0x255, Got 0xbf99)
    !! failed
    verifying CG61
    Checksum error (Expected 0x9804, Got 0x7bf4)
    !! failed
    verifying CG64
    -- OK
    verifying CG65
    -- OK
    verifying CG66
    Checksum error (Expected 0x21a, Got 0xa36a)
    !! failed
    rebooting

    I spent a good chunk of time reviewing the tutorial of finding bad checksums and replacing it with what the phone actually has, but I realized that since I only have one sbf file which does not flash correctly, I have no idea what the offset addresses are in order to try to replace the hex digits. Is my situation completely inapplicable to this tutorial? Even if it were possible to get the checksums correct, would the flash be successful considering the weird symptoms my phone is exhibiting?

    Thanks ahead of time for even reviewing this lengthy post as I tried to give as much detail context of my situation. I'm trying to stay patient, but this is growing quite frustrating. Thanks again, I'm crossing my fingers.
     
  4. tcandhatch

    tcandhatch New Member

    Joined:
    Jul 22, 2010
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    have you tried taking out the sd card and see how it runs kinda sounds like what mine was doing back a couple months ago and verizon just replaced it might work if you haven't tried yet just my two cents

    Sent from my DROIDX using DroidForums
     
  5. Shibbey

    Shibbey Member

    Joined:
    Dec 14, 2009
    Messages:
    272
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    NE Ohio
    Ratings:
    +0
    Looks to me like you have an issue with the SBF you are trying to use.
    I recently got a DX and flashed .340 on it. Ran into FAILED flashes left and right.
    I STRONGLY recommend looking at the following: Linux solution to your Windows/RSD lite problems
     
  6. kutothe

    kutothe New Member

    Joined:
    Nov 3, 2011
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    So, my Droid X is driving me nuts. For some reason whenever the phone is rebooted, it goes back to a state it was in a few weeks ago. All newly installed apps, settings, etc are gone. I can't get it to boot into Clockwork Recovery either, only the default android recovery. I decided to try and flash it with sbf_flash, but kept getting "Checksum error" messages for 3 items. I used a hex editor and put in the values it expected and got it to flash without any failed messaged. However, once I restarted the phone, it's right back to that state it was in previously, like the flash had no effect at all...

    I'm running CyanogenMod-7-09192011-NIGHTLY-DROIDX (i'm not sure if this nightly might have caused it?)

    The phone works perfectly fine, it's just stuck in time.... Any help would be greatly appreciated, thank you!
     
Search tags for this page
data[0]: checksum error sbf flash
,
error verifying code group 32
,
error verifying code group 32 checksums
,
error verifying code group 33 checks
,
error verifying code group 33 checksums defy plus
,
sbf editor
,
sbf-recalc swap file error
,

sbfcodec

,
symptoms for hacked droid razr
,
using c# 4.5 codegroup