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.
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
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
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!
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
lilb3119 said:
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
Click to expand...
Click to collapse
I had to flash the FULL sbf and reroot and Install the 2 part zip to get back to GB. The FUll sbf should work, but if it fails try doing the system only after.
Can anyone help him out?
I refuse to believe he's the only one who's had this issue.
lilb3119 said:
Okay so as I was trying to put CM7 on my DX all was looking good until the reboot. After the reboot it goes right to the bootloader screen. I have tried resetting the phone multiple times. Still no joy. Below is what I have found, tried and errors that I am getting. Please help.
Errors on Bootloader Screen: A5, 69, 35, 00, 27
Tried to SBF back to stock GB and RSD doesn't work. Error: 0x7029
I did find a link link to remedy the issue but am unable to post it. I have tried literally everything that I can think of.
Which didn't work at all. Below is the error log in rsd.
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 50 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:52:50, June 15, 2011
Line: 1626
ERROR: Chipset type 43 is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 2187
ERROR: Device S Flash OMAP3630 MI is not supported.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 1024
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
16:53:52, June 15, 2011
Line: 523
ERROR: Unable to retrieve initialization values from INI file.
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Now to sum it all up. I have the latest drivers, I have tried reinstalling the drivers, I have tried reinstalling rsd lite three times, pulled battery, and looked around. If there is something I am missing please tell me. Any help is appreciated. Thanks XDA.
Click to expand...
Click to collapse
Use the full sbf. There's two flavors of sbf files, a system file and a full. Find the other one and you should be fine. I've had this problem and that's how I fixed it.
Save yourself some trouble and trying sbfing it was linux. sbf_flash works wonders.
Current Status: Brick
Hi,
I tried flashing stock SBF CEE 3.4.2-179-2 (retail central Europe) from here http://sbf.droid-developers.org/umts_jordan/list.php
I get IO and checksum errors resulting in FAIL. Now the phone does not boot.
Boot Loader
Code:
Bootloader
09.10
[B]Code Corrupt[/B]
Battery OK
OK to Program
Connect USB Data Cable
With RSD Lite 5.7 on Windows XP and MotoHelper drivers MotoHelper_2.0.40_Driver_4.9.0.exe
RSD Lite log::
2012/12/20 02:05:45 | -- | ERROR: AP Die ID: 1b10000791b963010000dcff0200
2012/12/20 02:05:45 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/12/20 02:05:45 | -- | ERROR: AP Public ID: 35bc21063d231f528e8ce8e9b9942dcd161967c5
2012/12/20 02:05:45 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 ->(1557)FlashOp
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:13:03 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2012/12/20 02:26:03 | 0 | ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 ->(625)FlashHdlr
Click to expand...
Click to collapse
Based on advice from skeevy420, I tried flashing with sbf_flash on linux.
sbf_flash:
Code:
Index[1]: Unexpected chip 32
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
It looks like writing (or reading) fails, resulting in checksum errors.
More Info:
Verified MD5 of all my downloads
Tried a couple of other SBF from the same version (3.4.2)
Phone is from T-Mobile USA
Can I do something to change brick status?
Do I need a different SBF version?
Does read/write error really means hardware problem, cannot be fixed by software?
Do those IO errors mean driver version problem?
New sbf not compatible with old (old was stock T-Mobile Froyo)?
Accept the fact that the phone is hopeless?
Any help appreciated!
Here's a basic tutorial to flash sbf's with Linux -- RSDLite quit recognizing my Bravo and the Linux sbf_flash tool was the only way to fix it. You may have to install the Linux adb drivers, not sure, but those instructions are on Kayant's Compile CM10 thread (first post).
After flashing, you might have to go to factory recovery and wipe data and cache in order for the phone to boot -- maybe even have to flash a 2nd or 3rd time. I once had to flash the sbf AND wipe data\cache 5 times in a row in order to get my Bravo to boot up after accidentally flashing a Defy boot.img (usually only 1 flash is needed, I do stupid things with my phones)
Thanks, I will give this a try.
Do you install linux on the drive (like dual boot) or boot from a CD? If you boot from a CD, how do you install motorola drivers?
Just did MD5 checksum of all my downloaded files and they are all good.
Tried it with linux, getting similar errors:
Code:
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Just a silly idea: is your USB cable/PC USB port OK? Try it on another PC and with another cable. Use a cable as short as possible and make sure that the phone is the only device connected to the PC via USB including the mouse.
Sent from my MB526 using xda app-developers app
thekguy said:
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, I think you are right.
I tried the omap option, did not help. Any other tweaks I can do to RSD light?
As far as USB, its the stock motorola cable. I disconnected everything from the computer, basically a laptop with nothing around it. I dont think its the problem, I tried over 10 sbfs and they all consistently show the same errors.
I am gonna hijack this thread...
So I believe I bricked the Defy I was supposed to be fixing.
It was acting up, the battery was sometimes showing a ? mark, and the rom it was flashed with was super buggy.
I decided to flash it with this sbf
Code:
T-Mobile_MB525_6.19.0_1FF
from here (Because I had read that it was the stock 2.1 Eclair from T-Mobile, the one the one was running originally.)
Now it won't boot.
Edit: The battery was dead. The cable was faulty so it cause a problem while flashing. Managed to get back at bootloader. Re-trying again but with:
Code:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
EDIT 2: The keyboard is not working so I can't logging into motoblur ._." Frustration... Going to keep flashing to see if its the screen of my phone or the actual program.
Edit 3: It appears it was the screen sensors being dirty. All solved.
-Defy MB525 GREEN LENS-
Any solution for this??
ChavitoArg said:
Any solution for this??
Click to expand...
Click to collapse
Try This
http://forum.xda-developers.com/showthread.php?t=1486731
I am having same problems flashing my defy. Tried different kinds of sbf using rsd lite but keep getting error verifying group code checksums from code 33 onwards...then flashing fails.
Any solutions??