Their "code," or their hardware? I'm sure that many here are interested to know.
Sent from my Droid RAZR MAXX HD using Tapatalk 2
the way to fix delivery confirmations is as followspen your dialer and type in ##7764726. Next hit send and when prompted for a password type in 000000 and hit verify. scroll down to SMS/MMS settings and select it. Next scroll to the bottom, select MO SMS over IMS and disable it. Now your good delivery reports are back! With the recent update Verizon made the switch from sending tet messages over their 1 X network and moved them to their LTE (and possibly 3g network. Disabling the MO SMS over IMS switches texts back onto the old 1 x network. i discovered this on a message board. No one at Motorola could help...all levels of their tech support and no one at Verizon tech support of anyone at any of the stores could help either. I had been having problems for two weeks since the update I installed and had spent many many hours trying to get this fixed and came upon this solution on a message board. It works like a charm!
Boy this wifi thing is messed up... 4.1.2 flat out breaks wifi completely, won't enable at all. Frustrating
And I can't simply fastboot back since it's 4.1.2.
I do understand you had a problem and glad it was fixed.
But most that updated did not have any bugs at all it works perfect for
Most but not all.
Hope your good to go now.
Do it all now you may not be able to do it later
For what it's worth, if you can't get the wifi problem fixed, you can flash the 4.1.2 fastboot via rsdlite (or Matt's utility might have it - haven't looked in awhile), and that clears it up. So evidently it was some sort of problem when the OTA was patching files and not an inherent issue with 4.1.2 (also evidenced by the small percentage of users having the issue).
Obviously if you're rooted running 4.1.2, you'll lose root if you do this and there's currently no way to root 4.1.2, which is also necessary to unlock your bootloader. But I had to have wifi and I'll just hope for a 4.1.2 exploit in the future! If you decide to go this route, also know it wipes your phone completely.
PROBLEM FOUND: No Functional Fault Found
REPAIR ACTION: Reprogramming/Reflash/MR/MC
This is what I fully expected, since the behavior observed on the handset supported it as the likely cause, i.e. WiFi worked perfectly fine immediately before the OTA and would not work at all immediately following the OTA.
While it's not convenient to have gone through the hoops of sending the handset back to MoTo for the repair, I feel it's worthwhile so they get to see the problem firsthand and can hopefully work to avoid it in future updates.
This is a software bug.Remember back in the past when the Motorola V3M received a firmware update.It was buggy.Then when a software update was released everyone wanted the monster file for the phone.However people did not know that the file had problems flashing the phone.Eventually people bricked their phones.Anyway get ready for a software update coming in the future.
A few members over at droidrzr have confirmed that if you've already unlocked your bootloader, you can fastboot the 4.1.2 file and remain unlocked and flash the root zip in a custom recovery to get root back since you're BL is unlocked. I wasn't 100% sold on unlocking my bootloader yet which is the main reason I didn't go that route.
After the update I have several issues that are driving me nuts.
Missing texts messages
Sleep Mode gone
Auto space with browser not working
Gallery pics all disorganized
Phone and People apps not organized. Many duplicates and "(no name)" entries
Speed dial settings gone
Emergency contacts gone
Contact icons missing
Just to name a few.
Last edited by seove; 04-24-2013 at 09:09 AM.