Root A warning to those that upgraded to OTA 2.2

[Deleted User]

_mrbirdman_

Please retweet, everyones about to wake up! DO NOT DOWNGRADE TO 2.1 SBF FROM THE 2.2 OTA, YOU WILL BE BRICKED! UNTILL WE GET A 2.2 SBF LEAK

Be careful with you phone for the time being!!!

http://androidforums.com/droid-x-all-things-root/182238-bootloader-error-message.html#post1627939

http://www.droidforums.net/forum/droid-x-tech-issues/82593-froyo-ota-bricked-phone.html

 

[ericnail]

This NEEDS to be stickied temporarily!

 

[kushineris]

im pretty sure im screwed i sbfed back to 2.1 bc update kept failing. then i got it activated again and the 2.2 ota update installed. now when it started back up it just stays on an m logo and i almost sbfed it just now and stopped it what shold i do i cant even sleep

 

[whoozthaboss]

looks like ill be checking this thread cuz im stuck with the same problem. thats bull though the official update messed my phone up and I bet if i took it to a verizon store they would tell me some unhelpful bs

 

[ericnail]

Birdman is working on a fix. I will update this as soon as the fix hits.

 

[nicallen63]

Never mind.

 

[kushineris]

I know this is complete bs im going to take it into a store tomorrow and demand a new phone. i had no problems with the phone till i tried to install the ota

 

[jcage89]

now when it started back up it just stays on an m logo

That's exactly what happened to my Droid1 when Verizon pushed the 2.2 update OTA back in August. After update it would just boot to white Moto circle logo and nothing else. After a few days it wouldn't even do that. Verizon retail stores have tools to revive it and say they can fix it most of the time. But my Droid1 was a gonner. That is why I am waiting to see how it goes for everyone before I run the 2.2UD on my DX. I would bring it to the verizon store because there is nothing really you can do for it on your own.

 

[ericnail]

nvm

 

[Deleted User]

This should not have been moved...

It should be stuck and on the main page so it can stop as many people as possible from having this issue.

Im fairly certain this would constitute as a "Special Circumstance".

I debated on putting it here, but I thought it would get to a wider audience on the main page.

 

[whoozthaboss]

Does anyone think taking it to a Verizon store and demanding a new one would work? Not having a working phone kinda couldn't have come at a worst time.

 

[Slug]

I've "stuck" ericnail's thread in Support & Troubleshooting for now and added a link to this thread so as to keep discussion in one place.

 

[jcage89]

Does anyone think taking it to a Verizon store and demanding a new one would work? Not having a working phone kinda couldn't have come at a worst time.

IMHO, demands are rarely the best approach. I would just bring it in and tell them it became unresponsive after the update then kindly express concern over being without your phone and let them know you appreciate anything they are able to do to fix or replace your phone. You may find the person more willing to work with you taking that approach.

Also keep in mind (assuming you rooted your Dx and loaded the leaked 2.2), that basing a replacement demand on the OTA failure after you modified your phone with an unofficial OS is probably not reasonable. I am totally for being innovative with gadgets with hacks/tweaks, etc., but anyone making the decision to do this should understand that they are risking bricking it or rendering it incapable of reverting to the official SW. Assuming you did root your phone, you may agree that its not reasonable placing the blame on the official OTA for messing it up. Verizon probably can offer you a workable solution even if it isn't a new phone.

Good Luck!

 

[whoozthaboss]

I just got off the phone with Verizon, explained to them that the Froyo update made my phone completely unresponsive and that it wasnt even holding a charge anymore, was completely unresponsive... They will be shipping me a new Droid X preloaded with 2.2 tommorow since I called so early. I'd recommend this to those having the same problem. SN: My phone was not initially rooted

 

[ericnail]

IMHO, demands are rarely the best approach. I would just bring it in and tell them it became unresponsive after the update then kindly express concern over being without your phone and let them know you appreciate anything they are able to do to fix or replace your phone. You may find the person more willing to work with you taking that approach.

Also keep in mind (assuming you rooted your Dx and loaded the leaked 2.2), that basing a replacement demand on the OTA failure after you modified your phone with an unofficial OS is probably not reasonable. I am totally for being innovative with gadgets with hacks/tweaks, etc., but anyone making the decision to do this should understand that they are risking bricking it or rendering it incapable of reverting to the official SW. Assuming you did root your phone, you may agree that its not reasonable placing the blame on the official OTA for messing it up. Verizon probably can offer you a workable solution even if it isn't a new phone.

Good Luck!

+1

Lying FTW!

 

[akita]

Just for clarification as I see the thread title is regarding 2.2 OTA. For those that are not rooted and updated 2.2 leak, can we still use the current SBF?

 

[yawdapaah]

im pretty sure im screwed i sbfed back to 2.1 bc update kept failing. then i got it activated again and the 2.2 ota update installed. now when it started back up it just stays on an m logo and i almost sbfed it just now and stopped it what shold i do i cant even sleep

Have you tried to wipe data and cache? If not, boot whilst holding the menu button and try it. Good luck bro

Can anyone confirm that this applys to the OTA only!? What about those of us on the leaked 2.3.13 and 2.3.15 roms?

 

[anaphora68]

If you are on leaked 2.2, you should still be able to SBF back to 2.1. Why would you want to, though?

 

[akita]

I dont necessarily, but it would help to note that to reduce the over redundant threads that will pop up.

 

[yawdapaah]

If you are on leaked 2.2, you should still be able to SBF back to 2.1. Why would you want to, though?

Just in case I screw up the phone. Have you sbf'd from the leaks? I sbf'd from 2.3.9 but now I'm on 2.3.13 and scared to try.

 

[anaphora68]

I haven't SBF'd from 2.3.13...

Anyone tried this?

 

[ericnail]

I haven't SBF'd from 2.3.13...

Anyone tried this?

you can SBF from the leaked 2.3, NOT from the OTA 2.3

 

[cooley_l]

Was rooted sbf'd to original 2 weeks ago. Woke-up this morning and tried OTA , while downloading read birdman's post and freaked out, went thru the process and everything seems to be working fine, market ,youtube etc. Rebooted twice and still OK.

 

[OMJ]

Was rooted sbf'd to original 2 weeks ago. Woke-up this morning and tried OTA , while downloading read birdman's post and freaked out, went thru the process and everything seems to be working fine, market ,youtube etc. Rebooted twice and still OK.

using an sbf before you update is fine. Using the sbf after the OTA is where the problem arises.

 

[cooley_l]

Quadrant scores up from 1290's to 1400+ however stopping services seems slower after OTA?