[Atrix 4G Q&A, Help & Troubleshooting] Mario1976:
Hello,

I'm a little bit at a dead end after trying so much things.

My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).

After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.

Then I send it in for the third time and now I have the third mainboard in my phone.

Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.

Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.

So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold ;)

So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.

GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...

Then I discovered the next problem...

Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...

I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.

Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.

RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.

RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".

I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf

Then I found hints, that others were in the same boat and were able to recover from this error flashing this image

1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf

But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.

Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.

Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...

After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...

I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?

I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...

Best Regards

Mario