I'm installing it now. I was on .904, but reverting a stock .904 system to .902 is simple - using moto-fastboot all you need to do is flash both boot.img and system.img from the stock .902 FXZ, and your stock phone is now .902 again.

Caveats:

1) Do not need to unroot.
2) *DO* need to make sure your stock system in pure stock - with bloat and all. Debloating *may* cause the update to fail.

I'm installing it now. I was on .904, but reverting a stock .904 system to .902 is simple - using moto-fastboot all you need to do is flash both boot.img and system.img from the stock .902 FXZ, and your stock phone is now .902 again.

Caveats:

1) Do not need to unroot.
2) *DO* need to make sure your stock system in pure stock - with bloat and all. Debloating *may* cause the update to fail.

Click to expand...

I'm really interested in how 905 performs and if it is improved over 904. I'm on the fence after the 904 mess...

Flashed 905 yesterday and so far so good. It seemed to fix a gps issue I was having, and otherwise seems pretty stable. It's a pretty small file and it doesn't wipe anything on the phone which made flashing easy.

I'm installing it now. I was on .904, but reverting a stock .904 system to .902 is simple - using moto-fastboot all you need to do is flash both boot.img and system.img from the stock .902 FXZ, and your stock phone is now .902 again.

Caveats:

1) Do not need to unroot.
2) *DO* need to make sure your stock system in pure stock - with bloat and all. Debloating *may* cause the update to fail.

Click to expand...

How do you flash just the boot.img and system.img and leave the rest as is if I'm on 5.9.904? I'm running stock rom but have bloatware frozen and have made changes to build.prop; I have the stock build.prop file. Do I need to be on stock build.prop and unfreeze bloat? When I installed the 5.9.904 I did have to use a stock build but I didn't unfreeze anything and all went as planned.

I went ahead and went back to 902 and installed it to, but the term OTA used in the article means Over The Air which would imply it is being pushed to users by Verizon or Motorola.

Click to expand...

Based on what we learned in the past with 5.9.901 and 5.9.902 you can speculate all you want and you will be either right or wrong.

In the case of 5.9.902 the people involved in the testing could only talk to non-testers about it if they violated the nondisclosure agreement they agreed to with Motorola.

There were three leaks before 5.9.901. Then 5.9.901 was sent OTA to some people and not others. Then 5.9.902 went into soak test. Two days later 5.9.902 was sent OTA to everyone. Six weeks later 5.9.902 was announced on the Verizon website.

Yep with a simple band unlock. Works on AT&T HSPA+, sometimes on T mobile but just edge. Straight talk, foreign sims etc. Verizon probably doesn't like that and neither does Motorola or FCC. The RAZR and D4 seem to work only overseas.

Flashed 905 yesterday and so far so good. It seemed to fix a gps issue I was having, and otherwise seems pretty stable. It's a pretty small file and it doesn't wipe anything on the phone which made flashing easy.

I am having serious problems with google maps navigation and/or my GPS, and wondering if anyone else is having the same problem. Whenever i start navigation with google maps, my GPS losses fix, and it says searching for GPS. If i switch to the GPS status app i get a fix, and it seems to stick with at least 5 or 6 of the sats and it doesn't seem to lose it. This sort of rules out a GPS issue in my mind, but google maps navigation is about useless.

I am rooted with .902, and this problem seems to have just started, because the .902 update actually seemed to fix a similar problem at least for awhile.

Thanks for any help!

Click to expand...

This is a copy of my original part and .905 seems to have corrected it.