Anyone know if the 2.3.40 SBF file for OTA has been released yet? I own a very pretty DX brick. Verizon is sending me a new one - I told them my phone lost power during the OTA. They said they didn't have the file to flash it yet so they'd send me a new one. When they flash it, they'll find Superuser permissions, Z4 Root and Wireless Tether. Then the jig is up.
the .32 full sbf will work on the .34 system...they are compatable
Any ideas if it will work if my bootloader is 30.04?
gadgetmom88 said:
Any ideas if it will work if my bootloader is 30.04?
Click to expand...
Click to collapse
Yes the bootloader is the same for 2.3.320 & 340
All you need to do is flash the .320 full sbf and you wont have a brick anymore.
Flashed the SBF I got from here Droid Life. I'm new so I can't publish links. I finished and RSD Lite said passed, but it didn't reboot the phone, and I'm still stuck in the bootloader screen... BRICK.
http://www.droid-life.com/2010/12/09/droid-x-2-3-340-system-sbf-released-for-2-3-320-leak-users/
That's where I downloaded the file from. Ran it twice, no dice. Guess I'm bricked. New phone from Verizon arrived. Should I ship the brick back or hold out?
Head over to mydroidworld and get the FULL sbf for 2.3.32 and try flashing that.
Thank you! Thank You! Thank you! It worked. No more brick I promise not to flash ROMs at 3am anymore so that I don't do something stupid again...
Related
Alright, so I rooted my droid and couldn't figure out to unroot it, so I Googled it and found out how to get the 2.2.1 OTA. I followed the guide on Droid Life and now I'm stuck in the bootloader. I'm totally lost...But I can tell you exactly what the boot loader says:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
That's it...All I really want it to be completely unrooted with 2.2.1 on my Droid X. Can somebody please help me/point me to a guide that could help resolve these issues?
Thank you so much!!
Foreverrr said:
Alright, so I rooted my droid and couldn't figure out to unroot it, so I Googled it and found out how to get the 2.2.1 OTA. I followed the guide on Droid Life and now I'm stuck in the bootloader. I'm totally lost...But I can tell you exactly what the boot loader says:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
That's it...All I really want it to be completely unrooted with 2.2.1 on my Droid X. Can somebody please help me/point me to a guide that could help resolve these issues?
Thank you so much!!
Click to expand...
Click to collapse
well pull your batt and see if it will boot up if it will not it and you never flashed the leak or took the ota as of yet then you can still use the 2.2 sbf and then once you get going update with the .340 ota and you will be unrooted on 2.2.1,here is the 2.2 sbf with instructions if needed
http://www.mydroidworld.com/forums/...droid-x-2-2-full-sbf-leaked-download-now.html
now remember you can only use this if you never flashed the .320 leak or took the .340 ota yet and if you did then you need to use those sbf
gmenfan83 said:
well pull your batt and see if it will boot up if it will not it and you never flashed the leak or took the ota as of yet then you can still use the 2.2 sbf and then once you get going update with the .340 ota and you will be unrooted on 2.2.1,here is the 2.2 sbf with instructions if needed
http://www.mydroidworld.com/forums/...droid-x-2-2-full-sbf-leaked-download-now.html
now remember you can only use this if you never flashed the .320 leak or took the .340 ota yet and if you did then you need to use those sbf
Click to expand...
Click to collapse
where is that sbf do you know? the .340? cuz this happened to me too
The 2.3.32 sbf works on 2.3.34 and its on my droidworld.
mob87 said:
The 2.3.32 sbf works on 2.3.34 and its on my droidworld.
Click to expand...
Click to collapse
I figured it out lol I was using the wrong sbf
Sent from my DROIDX using XDA App
i had same problem that foreverrr has i got my phone stuck then upgrade ota to 2.2 rooted my phone to 2.2 with version 315.. then i wanted to take the upgrade of 340 so they told me to downgrade to 2.1 and im stack on same thing as Foreverr ... my question is can i fix it ?? with the right sbf file .. is it the 2.2 or witch one exacly.. .. please help ....
same problem
i originally did a sbf on my dx coming from encounterics beta 3 and i sbf to froyo. i upgraded to gingerbread and tried to root my phone again. the root didnt work so i tried to sbf again and im stuck at the same error screen. ive tried many different sbf files and it always brings me back to the same bootloader screen... i dont know what else to do is there even anything to do?
nval148 said:
i originally did a sbf on my dx coming from encounterics beta 3 and i sbf to froyo. i upgraded to gingerbread and tried to root my phone again. the root didnt work so i tried to sbf again and im stuck at the same error screen. ive tried many different sbf files and it always brings me back to the same bootloader screen... i dont know what else to do is there even anything to do?
Click to expand...
Click to collapse
I believe that you will have to SBF to .621.
Sent from my DROIDX using Tapatalk
nval148 said:
i originally did a sbf on my dx coming from encounterics beta 3 and i sbf to froyo. i upgraded to gingerbread and tried to root my phone again. the root didnt work so i tried to sbf again and im stuck at the same error screen. ive tried many different sbf files and it always brings me back to the same bootloader screen... i dont know what else to do is there even anything to do?
Click to expand...
Click to collapse
When you say you upgraded to gingerbread how exactly did you go about it...if you took the ota upgrade then you're most likely on .621 and you'll have to use the .621 SBF file but if you used on of the methods where you flashed a zip file or two in CWR then you should be able to just use 1KDS's Linux SBF method and you should be up and running again. But if you did do the ota and are running .621 then DO NOT by any means use any other SBF then the .621 SBF or you'll be back in the same spot you're in now.
Sent from my DROIDX using XDA
Please bear in mind, there are different SBFs for 30.03 and 30.04 bootloader version. Be aware of that when you download the .sbf file.
So I've been on rubix focused for a while and I didn't really want to update to 2.3.320 (leak) but now I heard we have 2.3.340 (official). Can someone explain how I can get to this from 2.3.15. And will I have to update the rom I'm using or would it work? Sorry I tried to figure this out myself and almost bricked my phone. So now I'm kinda stuck and need some help
Thanks!
I am in the same boat. I am on 2.3.20 . I'm not really sure how I got to this version in the first place. I'm on rubiX 1.8.6 . How do I update to the latest and greatest, and what version is that actually?
Thanks in advance.
There are going to be plenty of people here that will chime in to help...but I just got done (literally) doing this today. I was on 2.3.15 OTA (rooted) running ApeX and wasn't even going to go through the hassle. But...ever since the Gingerbread sdk was released and all of these fresh new roms & themes are popping up...I finally said F it and did it. The basics of it go like this:
1. Backup everything etc...
2. You need to find yourself a copy of 2.2 ota stock, download to pc and flash that to your phone using rsd lite 4.9
3. Then you can pull the update down from your phone (takes 5 minutes from beginning to end)
4. Use Z4root and root your phone (was able to get root on my first try in under a minute)
5. Create another backup and be sure to name it 2.2.1 stock so you now have a starting point to fall back on when you start tweaking your phone.
This is my personal fave go to page that I use as a guide to any and all of my X mods. It doesn't get much better than this if you ask me!
Roooler's Guide to All Things X
If you don't have a stock backup with all bloatware intact, it'll be easier to SBF. If you have a stock backup, flash it, ensure all bloat is there, and download update and install. I removed bootstrap to be on the safe side.
Droid-Xer said:
If you don't have a stock backup with all bloatware intact, it'll be easier to SBF. If you have a stock backup, flash it, ensure all bloat is there, and download update and install. I removed bootstrap to be on the safe side.
Click to expand...
Click to collapse
Am I correct in assuming that once weve updated to 2.3.34 we cannot flash back to a backup that we were running 2.3.15 on, nor can we SBF back to 2.3.15?
ElephantGlue said:
Am I correct in assuming that once weve updated to 2.3.34 we cannot flash back to a backup that we were running 2.3.15 on, nor can we SBF back to 2.3.15?
Click to expand...
Click to collapse
DO NOT GO BACK !!!
why would you anyways???
okay, after all the reading i've decided that i should sbf instead of trying to figure out all the bloat that may or may not have been removed from my wife's X. That being said, once in bootloader, is it possible to get out of the bootloader without flashing anything? I want to verify the bootloader version to make certain that i have to proper .sbf file.
yes, i do have a backup of the original 2.2.....does that help?
i made this process more difficult than i had anticipated by installing another rom before trying the .340 update. now it starts the install then reboots and says "update failed". anyway, any tips or pointers that can be given are greatly appreciated....thx
I have a question I'm running 2.3.15, rooted with rubix ROM+theme---- already at 2.2.1 / what are the benifits of updating to. 340, and I'm guessing i can't just flash the sbf without starting over, rooting, ROM etc. Just not sure what of a difference there is for going to. 340 when I'm already at 2.2.1 anyone? ?
Sent from my DROIDX using XDA App
How would I update from 2.3.13
Thanks Mike
I apologize if this has already been answered already elsewhere....I looked around in other threads and didn't see anything.
I've flashed my phone with the full 2.3.32 sbf available online (system version now reads Version.2.3.320.MB810.Verizon.en.US, all Verizon bloat is installed, etc). If I try and do an OTA system update to pull .340, I'm told the device is up to date. I was under the impression that from the full .32 sbf I would be back at stock and able to OTA to .34 -- is that not the case? If I want to get to .34 do I need to use the system-only .34 sbf over .32? And why is that?
Thanks for your help.
beigel said:
I apologize if this has already been answered already elsewhere....I looked around in other threads and didn't see anything.
I've flashed my phone with the full 2.3.32 sbf available online (system version now reads Version.2.3.320.MB810.Verizon.en.US, all Verizon bloat is installed, etc). If I try and do an OTA system update to pull .340, I'm told the device is up to date. I was under the impression that from the full .32 sbf I would be back at stock and able to OTA to .34 -- is that not the case? If I want to get to .34 do I need to use the system-only .34 sbf over .32? And why is that?
Thanks for your help.
Click to expand...
Click to collapse
I believe that .320 is a leak from TBH, and was not a public update from Verizon. So my guess would then be (based on this assumption) is that since you don't have a "verified" version release, Verizon is not showing your phone as needing an update. If you still have the bootloader version 30.03 (when you turn phone on, hold "volume down, camera button, and power), this will put phone in bootloader. If it says 30.03, you can use the 2.3.15 full sbf to go back to 2.3.15 and then do the update via OTA to 2.3.340. If it says 30.04, then yes, you will need to use the .340 system only sbf to update.
just an educated guess... The reason there is a 2.3.320 sbf is because people tbh saw people bricking their phones, and wanted a recovery method for devs and the public alike *(again another assumption).
Hope this helps
Yeah, I had seen some other information that indicated the .320 sbf was a leak, so what you say about it not being recognized by Verizon makes sense. Unfortunately I already had the 30.04 bootloader so that sbf seemed my best option. Hopefully the combination of .320 full + .340 system is enough to make the phone recognizable for future OTA updates.
Thanks for the help. I appreciate it.
beigel said:
Yeah, I had seen some other information that indicated the .320 sbf was a leak, so what you say about it not being recognized by Verizon makes sense. Unfortunately I already had the 30.04 bootloader so that sbf seemed my best option. Hopefully the combination of .320 full + .340 system is enough to make the phone recognizable for future OTA updates.
Thanks for the help. I appreciate it.
Click to expand...
Click to collapse
Yes sir.
.320 + .340 will get you completely stock.
A Verizon rep wouldn't even be able to tell.
Your phone will, indeed, receive updates.
I'm in the same boat, I have 2.3.320. I have a .sbf file (named SHADO_X6_2.3.34_SYSTEM-ONLY.sbf), am I correct believing that flashing to that file should bring up to the latest official version?
sfreemanoh said:
I'm in the same boat, I have 2.3.320. I have a .sbf file (named SHADO_X6_2.3.34_SYSTEM-ONLY.sbf), am I correct believing that flashing to that file should bring up to the latest official version?
Click to expand...
Click to collapse
Yes, just make sure and verify you have the correct sbf, im not sure of the exact file name
Sent from my DROIDX using XDA App
Hi all. Several months back, I rooted and flashed the very first leak of 2.2 on my friends DX and haven't done anything else to that phone since. Recently, I flashed Liberty 1.5 and now he can't play any type of media. I figured this is probably due to outdated software since he hasn't been able to receive any OTA updates. I'm confused on where to go from here.
He has bootloader 30.01 with which, to my understanding, we won't be able to SBF or MADERSTCOK "SBF". Any suggestions?
P.S. I did a nandroid backup prior to flashing Liberty 1.5
superyoungg said:
Hi all. Several months back, I rooted and flashed the very first leak of 2.2 on my friends DX and haven't done anything else to that phone since. Recently, I flashed Liberty 1.5 and now he can't play any type of media. I figured this is probably due to outdated software since he hasn't been able to receive any OTA updates. I'm confused on where to go from here.
He has bootloader 30.01 with which, to my understanding, we won't be able to SBF or MADERSTCOK "SBF". Any suggestions?
P.S. I did a nandroid backup prior to flashing Liberty 1.5
Click to expand...
Click to collapse
There is a full 2.3.340 SBF out there now. Maybe you should SBF to 2.3.340 and then install Liberty. Before you SBF there is a zip file that will update your bootloader to the current one so you can SBF to 2.3.340.
Here is the link to the full SBF:
http://www.mydroidworld.com/forums/droid-x-mods/6360-full-2-3-340-official-sbf.html
i'm running froyo, rooted and have unlocked bootloader. i downloaded the ota update as it said i had one available. so downloaded and clicked install. this did not work. sent me into some sort of bootloop.
so i got into recovery. wiped and restored. so now i have unrooted my phone and contemplating doing it over.
or.....going to the Atrix Firmwares superthread and flash via RSD.
and what i want to know is. can i use RSD to update even though i have an unlocked bootloader.
this question has been asked. but there has been no definitive answer.
Many Thanks
wow thats a tuff call Its deffently never a good idea to do ota on custom rom
you Will Brick soo it you can get to fast boot or use moto-fastboot and Wipe EveryThing
Use a fruitcake sbf and never accept ota again.
I would just flash a fruitcake so you could avoid most of the problems associated with hardbricking and RSDLite. Just check out this link to get you started.
Thanks anyway. I just took apart the new firmware and flashed through fastboot.
Do the fruitcakes work well with non AT&T phones I.e my uk retail ATRIX?
Sent from my MB860 using xda premium
glad to here ya got it fixed
the fruitcakes are the closest thing to stock that we have.
but yea fastboot doesnt like large files