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

Root Ota?

Welp, you can try out zombiestomped if you're bored. I did. It's pretty good. :)


I know I tried it, it seemed pretty good, but I couldn't use BWC on it.....it was either the script that optimizes the apps at every boot causing issues, or I have to re-theme using the apks from ZS; there's no way I'm going to do that, too much work.
 
possible that an update has been pushed back because of the security flaw in 2.3.3???...update being pushed to 2.3.4 to fix the issue??

unfortunately...if that is the case...i think it hurts the X's chance of ever seeing official GB...
 
i hadn't seen that Google could push out that update...that is good to know...

And why would they scrap all the work put into a DX Gingerbread build now?

if the fix required the builds to be updated to 2.3.4 i could totally see them just pushing it out for the X2 and leaving the X behind
 
i hadn't seen that Google could push out that update...that is good to know...



if the fix required the builds to be updated to 2.3.4 i could totally see them just pushing it out for the X2 and leaving the X behind


I doubt that. With all the devices (DX is just one of many) out there the vulnerability do you think Google would accept the negative publicity, when they have the ability to update everyone to the "fixed" 2.3.4?
 
I doubt that. With all the devices (DX is just one of many) out there the vulnerability do you think Google would accept the negative publicity, when they have the ability to update everyone to the "fixed" 2.3.4?


they dont have the ability to update everyone to 2.3.4...if they did we already would be...


They are not pushing out any updates, they are fixing the issue on their server side.
that makes more sense..
 
One of the major factors to consider is these developers have big dreams and big mouths. They plan out this big new OS, work on it as fast as possible, and in the meantime they spout off at the mouth announcing it's release prematurely.

They get people all hyped up for a new release and it's NOWHERE near ready to be released. The board of directors in these companies spend too much time thinking about their upcoming profit instead of a working OS.

And lets not forget VZW's interference. They need an OS they can lock down before they approve anything to go out for their phones.
 
yes lol, his sis was either still on 2.1 or on 2.3.320 or something to that nature, luckily though she is now up to speed :)
 
be careful with assuming that its Froyo...the file that came through and ended up being .588 GB had the same name i believe...

from what i understand the update files are named after the previously installed OS...
 
Least they are prepping for it... when the Froyo update happened it was chaos because there were no instruction/support from verizon.
 
Back
Top Bottom