Non-rooted 4.5.588 to 4.5.602

[thegrizz51]

Back in May I got impatient waiting for Verizon to approve the Gingerbread update, so I went ahead and installed the .588 leaked version. Although it worked like a champ, I'd like to get the benefit of the .602 bug fixes and radio update.

I tried to update to the official .596 version, but since my phone is not rooted, there doesn't seem to be any easy way to do that. Honestly, I don't have any major objections to rooting, but if there is a way to get to the .602 update without rooting, I'd prefer to go that route.

Anyone know if there is some way to do this? From what I've read, the only way is to go back to stock Froyo, but it sounds like even that method is hit or miss.

This is my first post, so any help would be appreciated. Thanks!

[Ads]

[popcenator]

SBF and taking the OTA will get you there. You can also download the stock version and change it to update.zip and install through stock recovery.

on the move..

[thegrizz51]

I thought about downloading the update, but haven't been able to find the file. Any ideas where I can get it?

[popcenator]

You haven't modified anything system-wise have you?

on the move..

[thegrizz51]

Nope. Other than the fact I used the .588 leak, I am completely stock. If I could find a download location that has the official stock update file, I would try to apply the update through normal recovery, but all I can find is leaks and "pre-rooted" versions. Plus, it sounds like some people are saying using stock recovery won't work.

On a somewhat unrelated rant, I think it's ridiculous that Verizon doesn't just allow me to take the OTA (or even see it) just because I am on a leaked build. Seems like it should just see a new version number and allow me to update.

[Aerosport]

I am on the leaked version of 4.5.588 and was going to us the stock 6.02 update .zip, but can't seem to get into stock recovery mode to run the update zip. Same method I used to update to the leaked 4.5.588. When I power on with the home button pressed I get a quick flash of what looks like a box with open flaps and then t goes to the droid and triangle image with a yellow exclamation mark in the triangle but when I hit the search button it never moves off that screen. I can get into the boo tloader screen and it is bootloader 30.04 and if I do a battery pull and reboot it boots normally to my home screen. Any help or ideas would be appreciated as I am a rookie at this.

[popcenator]

When you get to the exclamation point, hit both volume keys at the same time instead of the search key. Then when you into recovery, the power button selects instead of the camera button.

on the move..

[popcenator]

Nope. Other than the fact I used the .588 leak, I am completely stock. If I could find a download location that has the official stock update file, I would try to apply the update through normal recovery, but all I can find is leaks and "pre-rooted" versions. Plus, it sounds like some people are saying using stock recovery won't work.

On a somewhat unrelated rant, I think it's ridiculous that Verizon doesn't just allow me to take the OTA (or even see it) just because I am on a leaked build. Seems like it should just see a new version number and allow me to update.

Here you go
Official Gingerbread .602 Update

You'll want the stock signed update (if you don't care to have root).

PS. I apologize for the delayed response

on the move..

[thegrizz51]

I found that thread before, but the first mirror for the stock image is down, and the second one links to the .596 update (even though it's only 11 MB, which makes me wonder if it's just mislabeled). Either way, it does not work in stock recovery. I get the "installation aborted" message (status 7) or something like that.

Could I be doing something wrong? Any chance someone out there has the update.zip on their SD card and can share?

Thanks.

[thegrizz51]

For the record, I ended up doing the SBF to .596 and it took the OTA update to .602 immediately. Sadly, I had to lose all my settings and for some reason, the market on the phone didn't recognize all the apps I had downloaded. I had to go to my computer and push the apps back to my phone...kind of weird, but it could have been worse.