Root Coming Soon: Full 2.3.320 SBF file!!

[Deleted User]

for those of us who sbf'd to 2.2.1 will we be able to accept the upcoming ota?

Definitely not.

 

[digdug1]

so we're stuck with tbh for ever? i have tried a couple roms but i prefer stock roms!

 

[Steven58]

so we're stuck with tbh for ever? i have tried a couple roms but i prefer stock roms!

never stuck. we may have the update before it goes ota

 

[bouchigo]

never stuck. we may have the update before it goes ota

I don't know, supposedly the update goes OTA at midnight tonight.....

 

[digdug1]

i am having some upgraders remorse lol. since upgrading my x is chewing through my battery i have tried stock (ouch) apex and jrummy's rum x. i am sooo ready to move away from 320!

i am checking into rubiXblurry 2.3.20 now may give it a whirl

 

[digdug1]

never stuck. we may have the update before it goes ota

i fear that my batt problems come from either the updated kernel or the base band. what are the chances of the newer upgrade will revert these?

 

[zane!]

As usual, I'm holding out to see what the OTA brings compared to this SBF. I did download the SBF just to have it on hand though.

 

[colchiro]

I think the leaked 2.2.1 has developer debug code that decreases battery life. This means that installing the update.zip or roms that have the 2.2.1 files would all have the same problem. I know the Rubix Blurry rom I installed ran great, but had the same battery life problem.

 

[digdug1]

I think the leaked 2.2.1 has developer debug code that decreases battery life. This means that installing the update.zip or roms that have the 2.2.1 files would all have the same problem. I know the Rubix Blurry rom I installed ran great, but had the same battery life problem.

oh great! why didn't we hear about this BEFORE we flashed i knew something was up. i have had awful batt life post updating.

i hope tbh comes up with a solution and soon! preferably a way to revert to stock either with the new ota or the last. i dont care at this point.

 

[colchiro]

I expect the OTA system files will fix the issue, it'll just take a while for the roms to get updated.

Blurry 1.6.3 had this issue and 2.3.20 was pulled for a reason.

 

[digdug1]

as stated above i have tried a couple of roms all with dismal battery life. i looked for the newest blury but it was pulled due to a new version coming soon.

 

[colchiro]

I'm going to install Blurry 2.3.x when an updated version comes out that's safe with the update.

 

[digdug1]

i hope it has the batt fix. for now i am funning the stock 2.2.1 rom but i will flash to blurry as well.

 

[colchiro]

My fix for batt FC's is to charge to 100%, then clear batt stats in recovery (under advanced), boot back before unplugging the charge cable. I figure all that restoring backups and roms just confuses the battery controller. Not perfect but fixes it most of the time. FWIW, only had one FC in Blurry, and that was right after restoring a backup and the above fixed it.

 

[VoidedSaint]

i hope this hasnt been addressed, i am at work and didnt want to read through all the posts, my question is:
Should i SBF back to 2.1 do the OTA, to 2.3.320 and then try some roms? (if we know they are working)
or should i just go ahead and sbf to the 2.3.320 file itself? cause then i can reinstall APEX 1.2

again im sorry if this has been brought up, just looking for the answer to my question while skimming through these posts

 

[colchiro]

VS, if I were you, I'd check my bootloader version and go from there.

Power up your phone with the volume-dn and camera buttons pressed. You can let up when your screen briefly flashes.

• If it's 30.04, you have already installed the leaked update.zip and you can't get the OTA. You should flash with the 2.3.340 SBF when it's available, presumably later tonight (or 2.3.320 would work too). You also risk bricking if you flash the 2.2 SBF.

• If it's 30.03 (froyo), you can flash to the 2.2 SBF and grab the new OTA to update your bootloader. A better option would be to restore a 2.3.15 nandroid, if you have one with intact apps.

• If it's 30.02 or 30.01, you could flash to the 2.1 SBF and OTA to 2.2 and again to 2.3.340, but I believe I read where a few people skipped the 2.1 SBF, and just flashed to 2.2 and successfully got the OTA.

Bear in mind that apparently Verizon pulled the OTA for now. I suspect their servers were overloaded.

 

[VoidedSaint]

from all the reports of poor battery life on the 320 i wonder if i should, im on bootloader 30.01 lol so i may flash back and ota to 2.2 and then flash 2.3.320

 

[Deleted User]

colchiro, that isn't entirely accurate.

VS, read this:
http://androidforums.com/droid-x-all-things-root/227906-sbf-bootloader-versions.html

When you use SBFs to update your phone, the version number doesn't change in the bootloader so your bootloader may not accept an older SBF.

 

[colchiro]

colchiro, that isn't entirely accurate.

VS, read this:
http://androidforums.com/droid-x-all-things-root/227906-sbf-bootloader-versions.html

When you use SBFs to update your phone, the version number doesn't change in the bootloader so your bootloader may not accept an older SBF.

Sorry, what am I overlooking?

I thought I was suggesting flashing to the sbf that matches the boot loader and using OTA to update boot loader and get to current OTA version.

 

[VoidedSaint]

i cant OTA i sbf'd back to 2.1 update -1

 

[VoidedSaint]

i cant ota to 2.2 i may do it by rom manager, but would i b able to sbf to the 2.3.320?

 

[colchiro]

i cant OTA i sbf'd back to 2.1 update -1

I assume you mean you sbf'd back to 2.1 and the OTA isn't available?

Do you have a goofy icon on your taskbar that wasn't there before? (meaning you need to activate your phone *228, option 1)

 

[VoidedSaint]

nope activated before i tried to search for it

 

[colchiro]

What android version do you have installed? (Settings... about)

 

[VoidedSaint]

version 1.13.604.MB810.Verizon.en.US
2.1-update 1