• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Any reason not to update to 2.2?

as a former droid eris leak installer, i'd probably recomend not doing it.. we all assumed when the 2.1 update officially came ota for the eris that we could just install it and be fine...well that never happened. we were unable to recieve the ota update due to installing the leak... so just a word of caution don't think it'll be ok
 
Nope, no reason. I have been trying all day to find any bugs in the update and I haven't found any. Plus I have installed leaked updates on my Droid before I got my X and you can still get the OTA if there are any changes, but this leak seems ready for release to me.
 
There are a couple bugs.

-Battery manager force closes when you try to open it, sometimes it does open
-I have some apps organized in appsorganizer and I tried to open the folder and nothing opened, had to reboot.


That's all I can really think of. Not that big of a deal, to be honest. But it's not perfect---then again, what is?
 
I've had zero issues so far but sometimes I don't want the screen to rotate to the right since I'm not used to it but its not too bad. Other than that absolutely no issues! very surprised at how well it works
 
This might be an isolated glitch, but my home button ain't working anymore...so yeah, the only con I can think of.

EDIT: Looks like its been solved. So yeah, no reason not to.
 
I remember when I rooted and installed a custom rom on the droid the maps would not update from the market. Though it wasn't a big deal. The speed increase was tremendous but that is not so much the case with the X based on what I've read. I know what froyo does but I'm gonna wait this time around. It just not worth it IMO until the custom roms come down the pike and and the kinks have been worked out.
 
My question is, and I am asking it here because it was the newest of the 20 question threads about this leaked update... but anyway my question is... would it be better to do this on an freshly factory reset phone? I have launcher pro and all kinds of custom buttons and dock, etc. Will these ride through the update ok?
 
s... would it be better to do this on an freshly factory reset phone? I have launcher pro and all kinds of custom buttons and dock, etc. Will these ride through the update ok?

Have you installed any customized themes?

Have you removed any bloatware?

If you answered yes to any of these questions, I'd recommend not only a factory reset, but a factory reset, cache wipe, and a flashing of the phone.

Some people who have installed themes then uninstalled them still had update issues.

Some people who thought they reapplied the bloatware they removed still had update issues.

Instructions for flashing here: http://androidforums.com/all-things...leased-now-you-can-unbrick-5.html#post1419764
 
Have you installed any customized themes?

Have you removed any bloatware?

If you answered yes to any of these questions, I'd recommend not only a factory reset, but a factory reset, cache wipe, and a flashing of the phone.

Some people who have installed themes then uninstalled them still had update issues.

Some people who thought they reapplied the bloatware they removed still had update issues.

Instructions for flashing here: http://androidforums.com/all-things...leased-now-you-can-unbrick-5.html#post1419764

I had themes and I froze some bloatware through TiBu. I just unfroze it and followed Fabolous' post on how to return to stock theme using his Fabolous_Theme_Killer.zip via Bootstrap. Fairly easy and less intimidating than SBF.
 
Why are people worried about this? If you can't go from 2.2 leak to 2.2 official, just flash your damn phone back to 2.1 then check for updates again.

Flashing is ridiculously easy.

Any one know if you flash to 2.2 and then flash back to 2.1 does it do a reset of settings and apps?
 
Why are people worried about this? If you can't go from 2.2 leak to 2.2 official, just flash your damn phone back to 2.1 then check for updates again.

Flashing is ridiculously easy.

Since its so easy would you mind posting instructions and the files needed because most websites like android and me and droid life claim its not easy
 
with the ability to keep root and a new clockworkmod recovery for this 2.2 build, custom roms are just around the corner. So what ever updates Moto and Verizon add to future releases should and will be included to whatever roms are released. So I honestly see no reason to not install this leak. Its nothing like the situation like the eris. This leak doesn't change the bootloader at all.
 
Custom roms are still long to impossible. All we are doing is loading an official signed Motorola ROM. Anything custom won't be signed and won't work unless we find a way to sign them or make the bootloader not care and not brick.
 
Custom roms are still long to impossible. All we are doing is loading an official signed Motorola ROM. Anything custom won't be signed and won't work unless we find a way to sign them or make the bootloader not care and not brick.

I can't believe there are still people of this mindset. oooooo the dreaded efuse is brick our phones. please. they said this thing was locked tighter that fort knox. What happened? Within a week, we had root, just after a month we had a custom recovery. I'm not saying custom roms are gonna happen this week. But to say its next to impossible, after all that, just shows a lack of faith on your part. We will have Roms on this thing. Its just a matter of time. FWIW, goooo Koush!
 
I can't believe there are still people of this mindset. oooooo the dreaded efuse is brick our phones. please. they said this thing was locked tighter that fort knox. What happened? Within a week, we had root, just after a month we had a custom recovery. I'm not saying custom roms are gonna happen this week. But to say its next to impossible, after all that, just shows a lack of faith on your part. We will have Roms on this thing. Its just a matter of time. FWIW, goooo Koush!


So far history is proving this right. Signed bootloader means barring a lucky mistake on Motorola's part allowing a way around it, no custom ROM.

I have no idea why people like you keep insisting that there has to be a way. I will be pleasantly suprised if custom ROMs happen, but not holding my breath.
 
So far history is proving this right. Signed bootloader means barring a lucky mistake on Motorola's part allowing a way around it, no custom ROM.

I have no idea why people like you keep insisting that there has to be a way. I will be pleasantly suprised if custom ROMs happen, but not holding my breath.

LIKE I SAID, I'm not saying its going to happen any time soon (and if it does great). Why be a Debbie Downer about it?
 
Back
Top Bottom