RSDlite error logs

Discussion in 'Motorola Droid 2 Global Development' started by roezario, May 30, 2011.

  1. roezario

    roezario New Member

    Joined:
    May 28, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Keeps failing. So i thought i would post logs to see if anyone can sift out any helpful information.



    Thanks....max.



    08:34:07, May 29, 2011
    Line: 527
    ERROR: AP Die ID: 1c0001097c983a0a0000d8ff0100

    08:34:07, May 29, 2011
    Line: 534
    ERROR: BP Die ID: 0000000000000000cd6932890485

    08:34:07, May 29, 2011
    Line: 541
    ERROR: AP Public ID: 983b403cf4bbcb575553d830ab8976415a804d1b

    08:34:07, May 29, 2011
    Line: 548
    ERROR: BP Public ID: 040000000500000002000000ffff0000ed153289

    08:39:27, May 29, 2011
    Line: 1309
    ERROR: Interface AP-OS: Error verifying Code Group 39 checksums. File: 0xE9E1, Phone: 0x61E0
    File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
    Device ID: 0

    08:39:36, May 29, 2011
    Line: 1309
    ERROR: Interface AP-OS: Error verifying Code Group 66 checksums. File: 0x3730, Phone: 0x372F
    File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
    Device ID: 0

    08:40:17, May 29, 2011
    Line: 1190
    ERROR: Phone[0000]: Flash failed.
    File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
    Device ID: 0

    08:40:17, May 29, 2011
    Line: 597
    ERROR: Flash failure: Interface AP-OS: Error verifying Code Group 39 checksums. File: 0xE9E1, Phone: 0x61E0 (Error Code: 31),
    Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=39
    File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
    Device ID: 0
     
  2. brad92

    brad92 Silver Member

    Joined:
    Sep 29, 2010
    Messages:
    4,496
    Likes Received:
    17
    Trophy Points:
    153
    Location:
    TEXAS
    Ratings:
    +17
    First off, I would make sure you have a good sbf file

    sent from my ZombieStomped X
     
  3. chrisl20

    chrisl20 Member

    Joined:
    Feb 21, 2011
    Messages:
    175
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    wichita, ks
    Ratings:
    +0
    whole lot of checksum errors...did u unzip the sbf? And where did you get it from? ...and correct drivers, are they installed? Because(I could be wrong), but it looks like ur pc and phone arnt communicating correctly on@ least one of the errors...the rest make me think bad sbf file, whether its just a botched download, or isn't unzipped
     
  4. roezario

    roezario New Member

    Joined:
    May 28, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    From the two .sbf files listed in the D2G hacks forum the Top one (.rar) was completely broke for me. Winrar would say its corrupt. I downloaded the Second sticky sbf...a .zip file. Now i have to wait for my replacement phone to arrive (the touch screen was broke sbf'ing my phone for warranty purposes) so I can charge my battery :p



    The .zip sbf extracted without error so im sure it will work fine. Ill keep you updated as soon as I can get my battery charged. Until then...ill sit in peace with my bricked phone :p
     
Search tags for this page
error verifying code group 31 checksums
,
error verifying code group 32 checksums
,
error verifying code group 33 checksums
,
error: ap public id
,
phone[0000]: error verifying code group 31 checksums
,
rsd lite 2738
,
rsd lite error
,

rsd lite error 2738

,
rsd lite flashing code group 39
,
rsd lite interface ap-os error fix