What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

OFFICIAL FRG22D OTA patch is here. DOWNLOAD NOW!

Haven't checked my 3G speeds but sitting in my office at home I normally would have 1-2 bars of cell service with and occasional jump to 3 bars. Since I installed 22B I have a rock steady 3 bars.
I also noticed at a buddies shop where I could get on the neighbors WiFi previously with just the dot or maybe an intermittent flash of the first arc today I has the dot and two arcs signal.
 
CAP201008271746.jpg
 
I Did exactly what you said word for word via no computer...it opened everything up and everything went perfect as planned but when I checked the build after I was done it said FRG01B ....should I try again?
 
Sorry if this has been posted, but when exactly is the OTA supposed to start distrobution?

Sent from my Droid using Tapatalk

In theory, it's happening now.

But in practice, I haven't seen a single (accurate) report that anyone has received it OTA.

(Mind you, I've seen plenty of confused people saying they got the "new" update, but invariably they mean FRG01B, not FRG22D).

And I'm not saying this is a real problem. As others have pointed out, this doesn't seem at all unusual for Verizon. But it's still annoying.
 
In fact though, FRG01B has been sent out from Verizon's servers in at least two different forms during the run of its OTA. I received them both multiple times over a period of two days. Functionally they may have been the same, but they were extremely different in size, contents and installation processes.

The point I'm trying to make is that until the actual FRG22D OTA send from Verizon's servers is offically completed, we won't know exactly what form(s) this OTA will be in. Currently we see it as a patch. We may also see it as a complete send, or in some other form that we haven't imagined yet.

From previous experience, Verizon has proven itself to be free to send its OTA builds out in whatever form they choose. So insisting that this OP's version of FRG22D is the only way that Verizon is going to send it is at least premature, and may prove to be totally wrong altogether.

That doesn't mean this isn't a good FRG22D build. It is available on Google's website, and as such it has some validity. It just means that we don't know if it's the only FRG22D build, or even if it is one of the FRG22D builds that Verizon will send out in the actual OTA send. There is no crystal ball that can read that future.
Why are you so resistant to this being the Official patch?

I'm going to assume because you REALLY believe that P3 received FRG22D via OTA?

There's no other way to say this, but it was a lie. FRG22D will be and is a small patch for FRG01B...it will NOT come out as a full build. This was established a while back and has not been changed.
 
Well, so far he's blasted me for saying Verizon could send out a locked bootloader (FRG01B anyone?) without warning people, and doing so in such a way that it wouldn't be noticed till a reboot (FRG01B anyone?) and that Verizon has no obligation to leave our bootloader alone (Ditto). Now he's complaining about this patch, and saying it's/we're all wrong, etc.

The fact is if we're wrong we're wrong. Nobody was hurt, everyone shook hands and went home at the end of the day. Some people just seem to have the urge to make trouble and have this overweening desire to be right, even if the point is so minor it only matters to them. This patch is ONLY updated drivers for two wireless systems and changes the market and the build fingerprint (oversimplifying, I know, don't really care) so Flash is available in the market.

What did you expect? Free cookies? :)

If I prove to be wrong, I'm wrong. If anyone actually got hurt by installing this patch (signed by Verizon/Motorola and therefore works with the stock recovery image -- which should matter to some people and apparently doesn't) I apologize. Please send your medical bills to Verizon who are ultimately responsible for not taking the sharp edges off the phone you just lost your eye to. :)
 
I'm scratching my head trying to remember me saying this to you, really. Can you point me to it? Then I'll apologize and admit I was wrong.

Well, so far he's blasted me for saying Verizon could send out a locked bootloader (FRG01B anyone?) without warning people, and doing so in such a way that it wouldn't be noticed till a reboot (FRG01B anyone?) and that Verizon has no obligation to leave our bootloader alone (Ditto).
...
:)
 
Why are you so resistant to this being the Official patch?

I'm not at all resistant to it being *an* official patch. Since we haven't seen anyone receive the actual OTA yet, and since that OTA isn't either started or completed yet, I'm resistant to calling this patch the "OFFICIAL FRG22D OTA patch is here. Download Now!"

I'm going to assume because you REALLY believe that P3 received FRG22D via OTA?

Bad assumption. I agree with everyone else that his wording was misleading and that this was a leak. I don't just read this forum. I suspect he used the earlier FRG22D leak that was C&D'ed to either patch FRG01B or FRG22 and to produce the working rooted deodexed full P3 version of FRG22D.

There's no other way to say this, but it was a lie. FRG22D will be and is a small patch for FRG01B...it will NOT come out as a full build. This was established a while back and has not been changed.

I guess we'll all just have to wait to see how this next OTA pans out to see what really happens, won't we? These same assertions were made about FRG01B, and low and behold, it came out as at least two different versions Over The Air. Can you blame me for being skeptical?
 
I have an OTA update sitting on my phone this morning. Have stock rooted FRG01B with SBRecovery. What should I do? If I let it install it will get rid of root, correct? Or is it automatically blocked?
 
Back
Top