That's a good point...the experiences I've seen however have ranged from "its better" to "I think its better" to "no difference"
So to me that says it's clearing up some of the issues with the phones that were having them...and its status quo for those that were not having problems to begin with
That's a good point...the experiences I've seen however have ranged from "its better" to "I think its better" to "no difference"
So to me that says it's clearing up some of the issues with the phones that were having them...and its status quo for those that were not having problems to begin with
FWIW, I SBF'd twice and both times still had the .12p radio when going back to .340. So, I used the file here: Dropbox - Public - Simplify your life (1st one listed) that reverts the radio back to .7p so that it can be updated from there. I couldn't get the above .7p file to work within GB but in Froyo, it's fine. It might be the cause of why some people are having trouble getting the new ROM to install properly.
P3Droid said on twitter that you can recover the data from 596 to 602. I am SBFed out for tonight but I will try it tomorrow and see if it works. As far as getting it deodexed a vaguely remember Bo saying he would have a zip to deodex this build by tomorrow afternoon.
Because I am like talking to a stump, Let me see if I have this right. I am on TBH .596 Deodexed/rooted GB I have to (through TBH App) Download the .340 AIO and the .602 AIO, then go to CWM and flash .340 then flash .602 (without leaving CWM) and all should be good??????
Because I am like talking to a stump, Let me see if I have this right. I am on TBH .596 Deodexed/rooted GB I have to (through TBH App) Download the .340 AIO and the .602 AIO, then go to CWM and flash .340 then flash .602 (without leaving CWM) and all should be good??????
P3's build is the same, but it comes pre-rooted (as the official OTA Gingerbread has not been rooted).
However, I've also seen mention that P3's build was ultimately rejected by VZW and there were some minor tweaks made. I've also seen reference to another update coming yet, and this is only the radio fix.
P3's build is the same, but it comes pre-rooted (as the official OTA Gingerbread has not been rooted).
However, I've also seen mention that P3's build was ultimately rejected by VZW and there were some minor tweaks made. I've also seen reference to another update coming yet, and this is only the radio fix.
It would be really, really surprising to have two builds with the same version number differ in any way.
As someone who works for an R&D organization that builds software for our own proprietary embedded devices (so, very similar setup to what Moto has to accomplish), versioning is everything. Internally, we might have multiple builds of the same version, but if it got as far as submission to VZW, it's almost certain to be considered a "final" build of the version and subsequent changes will be made with a new version number.
P3's build is the same, but it comes pre-rooted (as the official OTA Gingerbread has not been rooted).
However, I've also seen mention that P3's build was ultimately rejected by VZW and there were some minor tweaks made. I've also seen reference to another update coming yet, and this is only the radio fix.
While I appreciate your reply, I am aware of what P3's build is. It appears that in Wally's post he knows that P3's build is not the same as the official release. Since the official build is the same build number as the leaked build I was curious as to what different between the two.
While I appreciate your reply, I am aware of what P3's build is. It appears that in Wally's post he knows that P3's build is not the same as the official release. Since the official build is the same build number as the leaked build I was curious as to what different between the two.
This is from Droid Life.
The 11MB update for your DROIDX that should fix a bundle of bugs that were introduced through Gingerbread, is now available for all users. Head into Settings>About phone>System updates to grab it! The new build will take your phone to Blur version 4.5.602.
How come there is such a difference in size but it is the same ver. number? and I wonder if you update over the 596 rooted from TBH will you loose root. I checked and it is not available for me yet.
None that I am aware of but I read Wally's post as the leak is only an updated radio an not bug fixes. As the official build is the same exact build number as the leak and obviously has some bug fixes Wally must then know the difference between the two builds.
This is from Droid Life.
The 11MB update for your DROIDX that should fix a bundle of bugs that were introduced through Gingerbread, is now available for all users. Head into Settings>About phone>System updates to grab it! The new build will take your phone to Blur version 4.5.602.
How come there is such a difference in size but it is the same ver. number? and I wonder if you update over the 596 rooted from TBH will you loose root. I checked and it is not available for me yet.
The reason the leak is so large is it's the entire build. In order to gain root P3 needs to root the entire build on his dev device which is not encumbered by the limits of the retail device. As the official build is completely stock on most devices ( not rooted etc.) It only needs the be a small update over top of the .596 build.
This makes no sense to me. If this is intended to fix bugs in .596 why do we have to be on Froyo to flash it?
EDIT: According to TBH you have to flash this from Froyo because that's the only way to get the radio working right.
And even worse, it's not deodexed. Not a BIG deal though. Looks to me like this is just a beta test for the final Moto update release. Oh, and i have to say, if the camera STILL isn't working after the official release of this update Moto is gonna have allot of pissed of peoples.
He probably just figured out how to package it up as a single install. I looked at the two-part install and I was never convinced it couldn't be done as a single package, but had no evidence for that other than just analyzing how the install process worked.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.