Here's the error log:
01:48:11, March 31, 2011
Line: 340
ERROR: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020090 Address: 0x2000 Command: BIN
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
01:49:09, March 31, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
01:49:09, March 31, 2011
Line: 597
ERROR: Flash failure: Interface AP-OS: Error flashing subscriber unit. Device API Error: 0xE0020090 Address: 0x2000 Command: BIN (Error Code: e0020090),
Detailed Error Details: Direction of the Error=3000, Command Value=300000, Code Group Number=2
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
This was after installing Gingerblur. Tried to flash back to stock ROM to get the OTA update but couldn't complete it. Please help, thanks!
Related
Code:
11:38:56, January 31, 2011
Line: 518
ERROR: AP Die ID: 27d00206f4945d010000f8ff0100
11:38:56, January 31, 2011
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
11:38:56, January 31, 2011
Line: 532
ERROR: AP Public ID: d1d3e59d4534574906a67db5532dae884d0429ee
11:38:56, January 31, 2011
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
11:44:40, January 31, 2011
Line: 960
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x17F400 Command: ADDR
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
11:44:40, January 31, 2011
Line: 1185
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
11:44:40, January 31, 2011
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x17F400 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
11:53:09, January 31, 2011
Line: 518
ERROR: AP Die ID: 27d00206f4945d010000f8ff0100
11:53:09, January 31, 2011
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
11:53:09, January 31, 2011
Line: 532
ERROR: AP Public ID: d1d3e59d4534574906a67db5532dae884d0429ee
11:53:09, January 31, 2011
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
12:02:10, January 31, 2011
Line: 960
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x16F800 Command: ADDR
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
12:02:10, January 31, 2011
Line: 1185
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
12:02:10, January 31, 2011
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x16F800 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
12:07:38, January 31, 2011
Line: 518
ERROR: AP Die ID: 27d00206f4945d010000f8ff0100
12:07:38, January 31, 2011
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
12:07:38, January 31, 2011
Line: 532
ERROR: AP Public ID: d1d3e59d4534574906a67db5532dae884d0429ee
12:07:38, January 31, 2011
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
12:13:17, January 31, 2011
Line: 960
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command: ADDR
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
12:13:17, January 31, 2011
Line: 1185
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
12:13:17, January 31, 2011
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
12:17:09, January 31, 2011
Line: 518
ERROR: AP Die ID: 27d00206f4945d010000f8ff0100
12:17:09, January 31, 2011
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
12:17:09, January 31, 2011
Line: 532
ERROR: AP Public ID: d1d3e59d4534574906a67db5532dae884d0429ee
12:17:09, January 31, 2011
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
12:22:48, January 31, 2011
Line: 960
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x17F400 Command: ADDR
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0
12:22:48, January 31, 2011
Line: 1185
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
12:22:48, January 31, 2011
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x17F400 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Why? What can i do?
Im assuming this is a log from rsdlite. I used to get that error as well. Power off your phone. Then hold down the home button while pressing the power button. When the little android image shows up, press the search button. Then go down to wipe data/factory reset (move highlighted selection using volume up/down buttons) and select the factory reset option by pressing the camera button.
Then retry the sbf, I used to get the same thing... Now I get the sbf to finish completely.
Sent from my DROIDX using XDA App
My MS2 started acting weird over the weekend, with many force closes and 3G conectivity issues.
I received a call, and after it the phone crashed and on restart it got stuck on a loop at the blur animation.
After that I tried turning on with the X pressed, cleared cache + wipe.
Still on boot loop.
My next step was to flash another SBF file (Brazillian SBF) using the RDS 4.9 on my win7 x64
it wouldnt recognize my MS2 (turned on with up arrow)
I am now trying on a XP windows. It recognizes the phone, start flashing but I keep getting a Code 32 checksum error.
I tried downloading the SBF from another source, but I still get the same problem.
is there any hope?
why do I keep getting this checksum error?
I've turned on the logging now.
this is what I'm getting:
14:53:51, March 14, 2011
Line: 527
ERROR: AP Die ID: 237001055bf45e010000d8ff0100
14:53:51, March 14, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
14:53:51, March 14, 2011
Line: 541
ERROR: AP Public ID: 38607a9e7df8020ec7cca49460878683e6aaa390
14:53:51, March 14, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
14:57:43, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:57:44, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x4C1B, Phone: 0x4E1B
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0xA01, Phone: 0xC872
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 40 checksums. File: 0xFDFF, Phone: 0x4A65
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:08, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0x6C96, Phone: 0x6E96
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 66 checksums. File: 0x3C24, Phone: 0x2C0E
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 1190
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
14:58:20, March 14, 2011
Line: 597
ERROR: Flash failure: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x65A6, Phone: 0x67A6 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=32
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
I have the SBF I need and have tried RSD to go back to stock from the leaked GB but I get an error shown below. I followed the installation instructions to the letter, in admin mode, Anybody else seen this before and know how to get around it?
This is what I get :
10:49:11, March 28, 2011
Line: 235
ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file.
File: D:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0
10:49:11, March 28, 2011
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
Device ID: 0
10:49:11, March 28, 2011
Line: 587
ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
10:50:23, March 28, 2011
Line: 235
ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file.
File: D:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0
10:50:23, March 28, 2011
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
Device ID: 0
10:50:23, March 28, 2011
Line: 587
ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
This was my first time.
I did all what was required.
But when I started the flash through RSD lite after just 1 min it showed me FAIL
It went from 1% to 100% once, and then it showed FAIL
Now when I unplugged the USB and remove the battery and insert it back again it automaticaly goes into bootloader and then I tried to flash again which gave me same result.
This is my phone status.
The screen shows
Code Corrupt
Battery OK
OK to Program
Trasnfer Mode:
USB
This is what the Rsdlite Error log file has.
22:32:29, May 13, 2012
Line: 537
ERROR: AP Die ID: 1140010e560368010000dcff0200
22:32:29, May 13, 2012
Line: 544
ERROR: BP Die ID: 0000000000000000000000000000
22:32:29, May 13, 2012
Line: 551
ERROR: AP Public ID: 785fdd0a961a8e4b1e6a0497d703ee271d20c5c0
22:32:29, May 13, 2012
Line: 558
ERROR: BP Public ID: 0000000000000000000000000000000000000000
22:32:29, May 13, 2012
Line: 709
ERROR: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\ErasingOp.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 1195
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 610
ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=100000, Code Group Number=No Codegroup
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
Please someone reply asap.
use the recommened rsdlite version...i have seen many other version of rsdlite gives such errors..i actually dont remember the exact version ..haven't used it for a while..
do a search in this forum..
All the best
I have read few other places and it said to use RSDLITE 4.9, which I did.
try version 3.4.8 if m not wrong..
Which one do you used for flashing?
i think the above version only..i have recommended the same version to many people and it works like a charm in past..search this forum for rsdlite stable version by experience of people..
I did successfully flash my Defy+ with RSDLite v5.6 (search the forum or google)
Maybe there's something wrong with your sbf-file? Just a wild guess, don't know if the error message tells actually something different...
Thanks for your time guys. I was trying to flash on my Desktop with no avail.
Tried on my lappy and Bingo its all done perfectly.
Happy I have finally upgraded to CM7 its really nice and fast.
well here is my brick!
If I flash my phone nimporte what SBF says "flash error"
2012/05/07 13:45:13 | -- | ERROR: AP Die ID: 0ab0010b107660010000d8ff0100
2012/05/07 13:45:13 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/05/07 13:45:13 | -- | ERROR: AP Public ID: e53a8a292b0b38ade4b76e0e3be0cde12a8d02bd
2012/05/07 13:45:13 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/05/07 13:48:22 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0xB975, Phone: 0x9A68 ->(1557)FlashOp
2012/05/07 13:52:22 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/05/07 13:52:22 | 0 | ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0xFC1B, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 13:56:22 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/05/07 13:56:22 | 0 | ERROR: Phone[0000]: Error verifying Code Group 34 checksums. File: 0xAB80, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 13:57:22 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS ->(1511)FlashOp
2012/05/07 13:57:22 | 0 | ERROR: Phone[0000]: Error verifying Code Group 35 checksums. File: 0x41F4, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 13:58:22 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS ->(1511)FlashOp
2012/05/07 13:58:22 | 0 | ERROR: Phone[0000]: Error verifying Code Group 39 checksums. File: 0x830D, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 13:59:23 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS ->(1511)FlashOp
2012/05/07 13:59:23 | 0 | ERROR: Phone[0000]: Error verifying Code Group 42 checksums. File: 0x4BB7, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 14:00:23 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS ->(1511)FlashOp
2012/05/07 14:00:23 | 0 | ERROR: Phone[0000]: Error verifying Code Group 45 checksums. File: 0xA9B3, Phone: 0x4805 ->(1557)FlashOp
2012/05/07 14:01:23 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030009 Command: RQRCS ->(1511)FlashOp
2012/05/07 14:01:23 | 0 | ERROR: Phone[0000]: Error verifying Code Group 47 checksums. File: 0xDE21, Phone: 0x4805 ->(1557)FlashOp
and when I restart the "code corrupt"
1 i made an SBF with the GC32 and my phone but remains redemare Blocke sue the blue LED
2 i have access to stck recovery
"e: can not mount cache: recovery / command
e: can not mount cache: recovery / caller
e: can not mount cache: recovery / log "
even after a wipe such toujour "
3 i have access to bootmenu but nothing works
"error: busybox rootfs Was Not created
error: cp not found "
thank you for your help
which rom SBF did u use?
I tested: 3.4.2-179-2 cee deblur
3.4.2-177-5 nordic deblur
3.4.2-177-3 ITA Blur
3.4.2-177-3 GB Blur
3.4.2-164 France (NU, Orange, SFR)
without success
Have you renamed the SBF in short name like "ABC.sbf"?
Have you pushed this short named SBF in the main Folder of RSD Lite?
Maybe your data cable is damaged.
Have made a factoryreset before flashing?
RATTAR
1 dont work
2 yes
3 i m tested for 3 data cable by moto
4 yes of course
only cg31, cg32, cg34, cg53, cg61, cg64 and cg65 pass
I fear your Defy is really bricked, i have read a nearly similiar thread on german forum.
The only solution for this User was to put his Defy to SC.
In his case the motherboard (probably damaged flash-memory) of the Defy was changed by SC.
i feel sorry with you.
thank you
R.I.P my defy
I would take the Defy to the Service Center.
The user i told you, made it and AFAIK the Service Center repair his phone in warranty.
Give your SC a try, the only thing could happend is, that the SC will tell you the repair costs something.
Then you can decide if you want to repair it or not.
The costs for repair are among to 120€.
I defy have longer under warranty and I did not want to be paid € 120 for the repaired while it costed me 50 €.
I bought a new phone
Have you considered selling it for parts for example? 'Cause if the price is right, I might be interested...
Hi
Hi , plz i want to ask you, what you did to your phone with this problem, because this is happening to me now and i don't know what i should do