stuck in bootloader / sbf not taking

[jwewing]

I need some help SBFing my DX. Screen shows Bootloader 30.04 err.A5,69,35,00,27 I have been trying to SBF using RSD Lite 4.9 4.8 and 4.7, Linux, and also a Linux boot disc for SBF. The SBF file that I am using is VRZ_MB810_2.3.34_1FF_01.sbf. Each of these ways to SBF says that it completes without any problems but I am still stuck at the bootloader screen. I have tried different downloads and also rand MD5 checksum on the files. Battery is full power. When using RDSLite I get these in the log files:

FlashErrorLog
18:04:17, July 13, 2011
Line: 518
ERROR: AP Die ID: 11d001078f775d010000f8ff0100
18:04:17, July 13, 2011
Line: 525
ERROR: BP Die ID: 0000000000000000b55432890485
18:04:17, July 13, 2011
Line: 532
ERROR: AP Public ID: 6f7dbb9a1aee03fc4cfe0d0e8c8a2802377f8f14
18:04:17, July 13, 2011
Line: 539
ERROR: BP Public ID: 040000000500000002000000ffff00002d003289

SWDL Log
07/13/11 17:58:43 --------------------------------------------------------------------------------
07/13/11 17:58:43 New Log Started For Software Download.
07/13/11 17:59:57 The FlashLog key is turned off.
07/13/11 18:01:16 000013f0 Phone.cpp 450 0 ERROR Generic failure when sending command.
07/13/11 18:01:16 000013f0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
07/13/11 18:01:28 Multi upgrade started for 1 phones
07/13/11 18:01:29 [Device ID: 0] Flashing phone.
07/13/11 18:11:04 [Device ID: 0] Waiting for others to finish current operation.
07/13/11 18:11:05 The FlashLog key is turned off.
07/13/11 18:11:05 FlashLog file is turned off.
07/13/11 18:11:05 Multi upgrade finished.
07/13/11 18:11:05 000013f0 Phone.cpp 450 0 ERROR Generic failure when sending command.
07/13/11 18:11:05 000013f0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.

 

[PARick]

Have you tried a battery pull, and reboot?

 

[ABQNM]

That error message likely results from one of 2 things. One is bad drivers and the other is the actual phone is damaged not allowing the install. When you connect to RSD Lite and click show device does it show up all the correct info?

I would first try the battery pull and also a different USB cable before blaming the phone. Even a different USB port or computer may help.

 

[jwewing]

PARick, yes I have tried the battery pull including holding power and home to get into recovery. Doesnt work.
ABQNM, Drivers should be fine Ive downloaded them several times. What would the correct info be in RDS Lite? This is what I am getting when connected

IMEI/ESN/MEID: N/A
TECHNOLOGY: N/A
SOFTWARE VERSION: N/A
FLEX VERSION: N/A
BOOTLOADER VERSION: V0x003004
DRM VERSION: N/A
AP DIE ID: 11d001078f775d010000f8ff0100
BP DIE ID: 000000000000000055432890485
AP PUBLIC ID: 6f7dbb9a1aee03fc4cfe0d0e8c8a2802377f8f14
BP PUBLIC ID: 040000000500000002000000ffff00002d003289

I have tried other computers including ones running Linux and XP. Later today I will try a different usb port and different cable, I havent thought of that.

 

[jwewing]

Out of curiosity if it comes to it, if I took this to Verizon would they be able to tell it was rooted since I am only getting the M boot screen and the bootloader? I was reading somewhere they they are charging full phone price to fix/replace rooted phones?

 

[ldopa]

I would stay clear of VZW. If you can get into Bootloader mode and it says ok to program etc.. you can get it back. It would then be a usb, driver, rsd, pc system or sbf file issue which can be resolved.

Droid 2 Liberty GB v0.9

 

[ABQNM]

RSD seems to be seeing the phone correctly, and it has the correct bootloader. It could be a communication issue, ie the cable or usb, but it may be the phone itself is corrupted. As far as them telling if it was rooted, they likely will not look into it because if they can't even get to the stock recovery, their first course will be to SBF it. That will wipe traces of root. If they can't get it to take, they will likely not go further since it is a hardware issue at that point. The chance exists, but the effort involved to check would be more than it is worth.

 

[ldopa]

I had an issue once where the sbf just wouldn't take. I couldn't understand why. It turned out to be my usb port. I was using an old laptop with a 1.0 USB. I went to a friend's house and tried it on his 2.0 USB and it worked fine. So, just try everything before taking the potentially expensive risk of taking it to VZW

Droid 2 Liberty GB v0.9

 

[jwewing]

I tried a different cable and different usb port, still keeps going to the bootloader.
Idopa, I have tried everything I can think of: 3 different computers including one with Ubuntu and XP and also tried the live Linux boot with sbf, download all files from other places several times and ran md5 checksums on them, different usb ports and cables, diferent versions of the live cd and rsd lite, battery pulls and after putting battery back in I hold the power and home keys, made sure the battery was fully charged, run as admin, and even tried changing the the device id and flash/flex options in RSD Lite. I dont see what else I can try other than unfortunately going to Verizon unless you may have more ideas?

 

[ABQNM]

Unfortunately, I think Big Red is your only option here. And obviously, don't mention anything you did.

 

[ldopa]

Thats a first for me. I've seen people with corrupt bootloaders, but this is new. I was always taught that if you can access the bootloader and it isn't corrupt, there is a way out. I'm sorry, you may be boned.

Droid 2 Liberty GB v0.9

 

[jwewing]

Unfortunately, I think Big Red is your only option here. And obviously, don't mention anything you did.

I know not to tell them it was rooted. Do you think its best to tell them that I was getting non stop force closes so I decided to try the factory reset and thats when I started getting the bootloader screen or simply tell them I started getting the bootloader screen?

 

[ABQNM]

If you pull the battery and boot up, you just get the red M, right? Don't mention bootloader at all unless that is the only thing that comes up on screen.

 

[ABQNM]

One thing that could possibly work, but if the phone is definitely broken then it won't. You could try to use the gingerbread SBF first. It is not rooted, but it is a different file and may go through. If it works, then try to SBF back to froyo again so you can get root.

P.S. I sent you 2 private messages.

 

[jwewing]

When the phone starts it shows the M logo for about 10 seconds then goes straight to bootloader.
I did try the Gingerbread SBF. That changed the white or silver M logo to red but the problem still persisted. I then tried the Froyo SBF again, it went back to the white/silver logo and still only get bootloader.