PDA

View Full Version : Can I use the 2.3.320 SBF from 2.3.15?



armedmonkey
12-15-2010, 08:31 AM
edit: Typo in title 2.2.15 -> 2.3.15

So trying to update it OTA is failing and I don't really feel like figuring out why. (I've tried going back to my earliest nandroid). Can I use the new SBF to update instead of SBFing back to 2.3.15 stock and then going OTA?

Also, from 2.3.320, can I OTA to 340?
And as far as I can see, there's no SBF for 340 right now so I can't go straight to it, yeah?

Droid-Xer
12-15-2010, 08:57 AM
If you're having problems updating, you need to SBF to 2.2 and then apply update. It will take you to 2.3.340 system. There is a system only SBF I believe for the new update.

Abe21599
12-15-2010, 09:48 AM
fixed ur title for ya :)



If you're having problems updating, you need to SBF to 2.2 and then apply update. It will take you to 2.3.340 system. There is a system only SBF I believe for the new update.
theres system, baseband, and kernel over at mdw

Droid-Xer
12-15-2010, 09:50 AM
fixed ur title for ya :)



theres system, baseband, and kernel over at mdw

Oh sweet. Didn't know that. Although I hope I never have to worry about that!

armedmonkey
12-15-2010, 10:39 AM
I'm using RSD Lite 4.8 with this sbf image: VRZ_MB810_2.3.15_1FF_01.sbf

RSD Lite seems to find my phone and detect the proper bootloader version (30.03).

but when I hit start I get :
Model: S Flash OMAP3630 MI
Port: 1
Port Type: USB
IMEI/ESN/MEID: N/A
Status: Failed flashing process. (0x7100); phone connected
Progress: <blank>
Result: FAIL

I tried googling this, but there seems to be no conclusive answer.

I've done the 2.1 SBF before, but on an older version of RSD Lite (4.7), and I remember I had to replace the pst_flash.ini file. I wonder if I have to do that for the new version?

The reason I upgraded was because I was getting the error on 4.7 - same computer, same USB port, same OS, same install, same everything as before, but different SBF.

I'm just trying to put my phone back into stock state so I can get the OTA

armedmonkey
12-15-2010, 10:42 AM
I feel like those are all going to fail for me since I can't even get the 2.2 SBF to go right now. (http://www.droidxforums.com/forum/droid-x-rescue-squad/13496-2-3-15-sbf-fails-dx-2-3-15-error-0x7100-phone-connected.html). Thanks a lot for the info though guys.

Abe21599
12-15-2010, 10:45 AM
I feel like those are all going to fail for me since I can't even get the 2.2 SBF to go right now. (http://www.droidxforums.com/forum/droid-x-rescue-squad/13496-2-3-15-sbf-fails-dx-2-3-15-error-0x7100-phone-connected.html). Thanks a lot for the info though guys.

i merged ur two threads together. please try from posting another thread about the same thing.

armedmonkey
12-15-2010, 10:46 AM
Sorry. I figured a more relevant forum and title would be helpful to people looking to solve the same problem later on. (assuming I can find a resolution:P)

Abe21599
12-15-2010, 10:47 AM
how far in the flashing process does it get? or does it even start up?

armedmonkey
12-15-2010, 10:48 AM
I get the error immediately after I hit start.

Abe21599
12-15-2010, 10:50 AM
yea then id try moving the flash.ini file into the directory

armedmonkey
12-15-2010, 10:52 AM
I tried using the same one as I did for the old version, but it made no difference. I can't find any guide regarding the 2.3.15 SBF that mentions any such file replacement (I was thinking there might be a new version of it). To be honest, I don't have the foggiest idea what that file was supposed to do. I looked at it and it looked like it might add some definitions to help RSDLite find my phone, but it seems to be finding it regardless of which file I use.

Abe21599
12-15-2010, 10:55 AM
try 4.7 and moving the file. idk if it works with 4.8

armedmonkey
12-15-2010, 10:57 AM
That was the original way I tried because that's what I still had from when I SBF'd 2.1. If I do a search for that file on google, it seems to be connected to an error with initializing because of an ini file (didn't get the exact error, but that was the gist).

Abe21599
12-15-2010, 11:01 AM
well thats what ur fixing whem moving the flash.ini file into the directory of RSD.

armedmonkey
12-15-2010, 11:26 AM
Are you sure? according to the thread below, the problem was that if you don't copy pst_flash.ini you get this error: "I can connect to my phone but I get an error that it can not intialize because of the ini file."

Anyhow, I just tried it again. No dice
I'm using this sbf: Droid X Full 2.2 SBF (http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html)


edit: I'm trying it on Ubuntu 10.10 x64 with sbf_flash right now. seems to be going. please cross your fingers I don't brick it :)

edit2: so.. that worked, I guess. Strange thing is it kept all my apps and wallpapers, etc... but I was able to upgrade no problems. I thought this SBF was supposed to give you the pine-scented out-of-the-box experience?

Pensacola32526
12-15-2010, 05:27 PM
Yes, this is weird. I have flashed before and had the green Android guy at first. Now, it went straight to my homescreen, apps all intact; very odd. Trying it again to make sure...
Update 6pm: Light blue little triangle next to my signal bars, all apps on the phone, clicked on system updates and it's not highlighted, nothing happens...
Update 6:15pm: After 3rd SBF, phone still has all apps, little blue triangle by signal status and still unable to update software. Software update button will not highlight. Time to move on... :(
Update 7:50pm: Could not move on because I was determined to fix it. Did a factory reset, wipe data/cache and rebooted. Now my phone is back to stock. Let's see if I can do the OTA upgrade...
8:03pm - Downloading update, let's see if it installs with no hitches.
8:17pm: OTA update to phone a success. Goodnight.
p.s. All above times were Central Standard Time.