Thank you for the screenshot, it happened to be too low of resolution to read what rsd lite was displaying though. Would you mind doing another please?
Sent from my SAMSUNG-SGH-I897 using DroidForums App
I have read in forums that the greayed out issue happens in some machines if the .sbf is not in the root of the c:/ might wanna try that.
@pilotrose seems like that his phone details shows up on he phone. So if we can trick rsd lite some how to think that the phone is connected then may be it will be able to inject the .sbf in to the phone... Just a hopeful thought.. Don't even know if it is technically possible or not
I will say that when I load the sbf on there Rsd lite won't give me the option to start it is greyed out, so seems like the files are bad. Or just not for this phone.
Thanks for the updated pictures...
very interesting thing... that you have a 03.09 bootloader when both @pilotrose and mine are 03.08.... did you do the recent update?
Question. Does "download mode" on the pro lock it in the bootloader on boot? If not that's the problem, and if so then RSD Lite might need a patch or new version leak before it'll work for the Pro.
Don't really know what you exactly mean by "download mode"
We have been able to access the Bootloader by pressing Volume Up + Volume Down + Power Button. And it takes us to a screen that says
Bootloader
03.08
Battery OK
OK to Program
Connect to USB
Data Cable
Once connected the last to lines change to:
Transfer Mode:
USB
After running the SBF, it starts to create an image and then completes to 100% and then soon after see and error on the screen of the droid pro:
Critical Error:
FEBE
0047
and the RSD Lite 4.9 has a Error Reading like: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP (Error Code: e0020047)
And the ErrorLog shows this:
17:18:26, *December 25, 2010
Line: 527
ERROR: AP Die ID: 1470000c8e4e3a0aXXXXd8ff01X0
17:18:26, *December 25, 2010
Line: 534
ERROR: BP Die ID: 00000000000000002XXXX289fcX4
17:18:26, *December 25, 2010
Line: 541
ERROR: AP Public ID: ea0d237076b0777ed20d2396XXXX81714b4d0X4f
17:18:26, *December 25, 2010
Line: 548
ERROR: BP Public ID: 040000000500000002000000XXXX000009083X89
Okay, then it's either an issue with the SBF -- bootloader updated with new encryption keys -- not being for the latest software version or an issue with RSD Lite not being able to access the phone correctly. The latter will require a new release or a patch.
And sorry, the "download mode" must have been from the other thread I was looking at in regards to SBFs and the Pro.
It vrey well could be any of those conclusions:
as RSD Lite only shows this when the phone is connect:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000308
DRM Version: N / A
AP Die ID: 1470000c8e4e3a0aXXXd8ff01X0
BP Die ID: 000000000000000025603289fc84
AP Public ID: ea0d237076b0777ed20d2396XXXX81714b4d0X4f
BP Public ID: 040000000500000002000000XXXX0000090832X9
also could be that the SBF is not correct:
as some one on the XDA Developers forum tried to re-flash the device in Linux got an error like:
That would be my guess. Frankly, without seeing the IMEI or whatever I'm thinking it's RSD Lite not recognizing the phone properly so it can't program it.
Yeah i am also thinking the same thing.
as this other person with a completely working Droid Pro updated with the recent OTA sees this when connected to RSD Lite 4.9
So you know where we can seek some help regarding patch for the RSD Lite... for this kind of issue?
Hey guys I asked around and this is the wrong sbf, this one is for the R2D2 Droid 2. The model # for the Droid Pro is XT610 not A957. Whoever purchased the sbf needs to get his/her money back or ask for the right one.