Stuck in bootloader on Droid X

SyNiK4L

Member
Joined
Mar 22, 2010
Messages
60
Reaction score
0
Location
Tennessee
So i rooted my roomies droid x. and then accidently flashed a rom and theme that didnt go together...so i tried to flash the rsd lite image and i get this error in the rsdlite log...

18:30:46, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

18:30:46, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

18:30:46, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

18:30:46, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

18:36:52, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

18:38:25, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

18:38:25, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

18:38:25, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

18:38:25, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

18:44:53, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

18:49:19, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

18:49:19, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

18:49:19, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

18:49:19, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

18:54:49, November 01, 2010
Line: 919
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR
File: D:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0

18:54:49, November 01, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

18:54:49, November 01, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

18:56:07, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

18:56:22, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

18:56:22, November 01, 2010
Line: 384
ERROR: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE003003F Command: RQHW
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp
Device ID: 0

18:56:22, November 01, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

18:56:22, November 01, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE003003F Command: RQHW (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=800000, Code Group Number=No Codegroup
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

18:57:35, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

18:57:35, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

18:57:35, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

18:57:35, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

19:06:26, November 01, 2010
Line: 919
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 Command: ADDR
File: D:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0

19:06:26, November 01, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

19:06:26, November 01, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

19:10:18, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

19:11:18, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

19:11:18, November 01, 2010
Line: 384
ERROR: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030009 Command: RQHW
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp
Device ID: 0

19:11:18, November 01, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

19:11:18, November 01, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030009 Command: RQHW (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=800000, Code Group Number=No Codegroup
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

19:17:33, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

19:17:33, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

19:17:33, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

19:17:33, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

19:23:40, November 01, 2010
Line: 378
ERROR: Error getting subscriber unit information.
File: D:\test_dev_usb\flash\code\flashdll\SUInfoOp.cpp

19:28:51, November 01, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

19:28:51, November 01, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

19:28:51, November 01, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

19:28:51, November 01, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

19:38:16, November 01, 2010
Line: 919
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR
File: D:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0

19:38:16, November 01, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

19:38:16, November 01, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0



other times it finishes and says success...rebooting...and then goes right back into the bootloaders and says this on the screen

ERR:A5,70,70,00,00
MEM_MAP Blank
Server Req'd


iv tried to flash it multiple times and it basically goes back and forth. any ideas?
 

Abe21599

Super Moderator
Rescue Squad
Joined
Dec 22, 2009
Messages
6,322
Reaction score
31
Location
Ohio
yea idk what you can do here. the bootloader message doesnt look too promising...

ur using the proper SBF, correct?
 
OP
S

SyNiK4L

Member
Joined
Mar 22, 2010
Messages
60
Reaction score
0
Location
Tennessee
VRZ_MB810_1.13.6.2_1FF_01


i was getting okay to program either way....and it would flash error at the very end...and it still shows that in the bootloader...but everytime i flash it, it just does that same error...or finishes with successful...rebooting and then says that same error.....

if i am bricked how would this have happened? iv only seen like 2 cases of this on here after hours of googling this and also he got this phone today and the only thing i did was flash rubix then bigdx's theme...got stuck in bootloop then i went to the bootloader said okay to program then flashed it...then got that error now it wont even get to the M logo.
with that said...if he goes back tomm should he just say he rebooted the phone and this is what happened? hes got insurance but im sure he doesnt wanna wait for them to mail him one....so would they just swap it out being that this happened the day he got it? he doesnt know anything about android so him going there would actually seem like he has no clue what happened.
 
OP
S

SyNiK4L

Member
Joined
Mar 22, 2010
Messages
60
Reaction score
0
Location
Tennessee
so this should work for sure? was that the completely wrong .sbf?
 

Abe21599

Super Moderator
Rescue Squad
Joined
Dec 22, 2009
Messages
6,322
Reaction score
31
Location
Ohio
not sure but if you took the over the air (OTA) update you need the new sbf.
 

Abe21599

Super Moderator
Rescue Squad
Joined
Dec 22, 2009
Messages
6,322
Reaction score
31
Location
Ohio
yea then you need the 2.2 sbf. pretty sure what you listed was the 2.1 one.
 
OP
S

SyNiK4L

Member
Joined
Mar 22, 2010
Messages
60
Reaction score
0
Location
Tennessee
okay well heres the deal now....when i flashed that file..it did save it from being bricked...it actually erased the phone how it should and started new....now thing is...i have a droid 1....and im really confused for some reason his contacts arent backing up to google like my droid 1 does. on top of that he has backup assistant which we sync'ed before...but once the sbf is flashed it doesnt say he has any contacts....so i loaded a clockwork backup i made before i almost bricked it...and went back and everything is fine contacts and all....but that .sbf i noticed has a newer version of 2.2 and had swype built in...and i would guess(but havent done much research)...has other features added too....but now when i try to flash it it fails at the end giving me almost the same error log

ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

00:48:50, November 03, 2010
Line: 589
ERROR: Flash failure: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030007 Command: RQHW (Error Code: e0030007),
Detailed Error Details: Direction of the Error=1000, Command Value=800000, Code Group Number=No Codegroup
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

00:56:50, November 03, 2010
Line: 518
ERROR: AP Die ID: 2b100105557f3a0a0000d8ff0100

00:56:50, November 03, 2010
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485

00:56:50, November 03, 2010
Line: 532
ERROR: AP Public ID: 580589d6422e298cbace44c0110cdb1639a9e179

00:56:50, November 03, 2010
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

01:05:35, November 03, 2010
Line: 960
ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 Command: ADDR
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\RDLOp.cpp
Device ID: 0

01:05:35, November 03, 2010
Line: 1185
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

01:05:35, November 03, 2010
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x150000 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

01:06:54, November 03, 2010
Line: 1497
ERROR: Error getting subscriber unit information.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp

01:07:54, November 03, 2010
Line: 1497
ERROR: Error getting subscriber unit information.
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp


only this time when it boots up....its exactly where his phone was before i flashed it...so i then tried wiping data 2-3 times in clockwork then flashing...same thing....errors at the end..with the same error
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F
but once it booted up...it started new this time with the older 2.2 instead of the newer version thats in the .sbf.

im confused anyone have any incite on this? i dont understand why when i flashed an old .sbf then flashed the new .sbf...it failed...but ended up flashing the newest version....but now that i reverted back to an old backup and tried to flash the newest .sbf that you posted it still fails and doesnt end up giving us the version that the .sbf includes



btw im using rsdlite 4.8 on windows 7 and if yall feel u need to move this to the main droid x support forum go ahead and do so. as this is no longer an emergency

 
Last edited:
Top