Verizon Touch Pro2 MR2 Update includes Sense 2.5

[hypeo]

if you relock the phone and flash you can probably unlock it again after flashing as stated above.

Originally Posted by eddiecanuck

Well I did download again and the file(s) are fine. I did a task29, flashed and still no go. I'm flashing back to MR1 now, then will try to upgrade again (not too hopeful) and then I'm going to give up until smarter people than me figure it out. I'm leaning towards the fact that my phone is unlocked. The only people if heard from that have had it work are those that had a locked phone.
While this doesn't update the OS to 6.5.3, it does put the new Sense 2.5 on it which would be nice. I know lots of custom ROMs have it but I really haven't found one that seems to be stable enough for me while giving me the features I like and am used to. I'd hate to think I have to re-lock my phone to get this to work as I do like to try out custom ROMs from time to time.
Well if anyone that has an unlocked phone gets this working or has an idea how I can get mine going I'd be most appreciative.

[PPCFreak]

anyone care to publish the sense version numbers from MR2?

I just got in a new Refurb and am thinking I should flash the MR2 before I fully load my apps/contacts/appointments/etc....

But curious as to what the update really is updating.

Edit: According to PCDPHones site, the update is updating software (VZ Navigator, Contact Card and Time Stamp).

[NightRaven]

I also cannot boot the mr2 update. However, I dumped the rom, and rebuilt it using the boot.rgu from the MR1 update, and also removing the OEM_FLASHDRV_1.DLL module from the XIP. After flashing it did boot correctly.

I'm going to now try a straight dump and rebuild to see if it is just something in their updater thats causing the issue.

[mikenerd]

I have been using MR for a few months and its been a little buggy but I really want the 2.5 twitter tab. If this is 2.5 I'll give it a whirl. would rather not have to relock tho.

[OrlandoHatch]

I had the exact same experience. Reflashing to MR1, relocking, flashing MR2 cured it.

[NightRaven]

Originally Posted by NightRaven

I also cannot boot the mr2 update. However, I dumped the rom, and rebuilt it using the boot.rgu from the MR1 update, and also removing the OEM_FLASHDRV_1.DLL module from the XIP. After flashing it did boot correctly.

I'm going to now try a straight dump and rebuild to see if it is just something in their updater thats causing the issue.

Yep, It is the boot.rgu and the OEM_FLASHDRV_1.DLL that's causing the problem!

[NightRaven]

Originally Posted by OrlandoHatch

I had the exact same experience. Reflashing to MR1, relocking, flashing MR2 cured it.

If you unlock it again, and hard reset, It wont boot again.

[PPCFreak]

Originally Posted by mikenerd

I have been using MR for a few months and its been a little buggy but I really want the 2.5 twitter tab. If this is 2.5 I'll give it a whirl. would rather not have to relock tho.

Are you refering to MightyROM?

This is not MightyROM discussion, its Manufacturer ROM (MR). An update ROM from the manufacturer for the Carrier (ususally at the request of the carrier due to software updates and/or additions).

[kgb247]

for those that had to relock just to flash the update, did you notice any signifigant changes / improvements?

[mikenerd]

Originally Posted by PPCFreak

Are you refering to MightyROM?

This is not MightyROM discussion, its Manufacturer ROM (MR). An update ROM from the manufacturer for the Carrier (ususally at the request of the carrier due to software updates and/or additions).

ha! I mean mighty Rom. I do however want a carrier rom with 2.5 so... hope this works well.