Related
After having the phone nearly a week I'm still having problems with the WiFi.
Fine for day one, then noticed when I took it out of my pocket a day later or so that WiFi stated "Error" and couldn't initialize, This happens continously now and sporadically at random intervals (Reboot does not appear to fix it but keep trying does seem to)
Anyone know of this or how to fix it? Or is it just a dodgy handset? (I've still got a couple weeks to swap it over luckily)
I've searched the forums and found something about the same issue after a flashed kernel but I am COMPLETE STOCK, EXCEPT For Root and S-OFF and even restoring to a compeltely basic almost "Out of the box" image does not appear to fix it.
I flashed my Radio today to see if it helps but it doesn't look like it currently.
Any help appreciated (Hope this is in the right forum.
daniluvsuall said:
After having the phone nearly a week I'm still having problems with the WiFi.
Fine for day one, then noticed when I took it out of my pocket a day later or so that WiFi stated "Error" and couldn't initialize, This happens continously now and sporadically at random intervals (Reboot does not appear to fix it but keep trying does seem to)
Anyone know of this or how to fix it? Or is it just a dodgy handset? (I've still got a couple weeks to swap it over luckily)
I've searched the forums and found something about the same issue after a flashed kernel but I am COMPLETE STOCK, EXCEPT For Root and S-OFF and even restoring to a compeltely basic almost "Out of the box" image does not appear to fix it.
I flashed my Radio today to see if it helps but it doesn't look like it currently.
Any help appreciated (Hope this is in the right forum.
Click to expand...
Click to collapse
this error is generally caused by a mismatch between the loaded kernel and the loaded wifi module.
the loaded wifi module must be compiled with and match the loaded kernel. flashing a kernel and then loading a custom rom (which loads its own modules overwriting the modules from the kernel) is generally the way this error occurs.
how you rooted the device could lead to the above wifi error i.e. custom ROM with root, which could result in the above situation, or just flashing superuser.apk which wouldn't result in the above situation.
the part of your comments which stands out to me is that the issue appears to be intermittent. i think the best suggestion and approach, at this point, would be to load a completely stock system.
if the wifi issue still persists, even though it is intermittent, it should be hardware related as my device has never had this type of wifi issue and i'm on a stock ROM. if you're on stock and still have this issue, i would def take it back as it would appear to be hardware related. hopefully the wifi issue will occur while you're at the store making it easy to demonstrate the issue.
hope that helps, good luck!
Hey,
I've been experiencing data connection loss on CM7-14/29, latest VGB, and PP (all MTD/AOSP GB ROMs).
Issue: Randomly, during the day, my internet dies, SMS/Voice appears unaffected.
This results in no connectivity on any apps, the 3G symbol is still there, but is white.
Turning it into airplane mode for 15s or so and then turning it back seems to fix the problem.
Attempted resolutions:
- Wifi sleep policy set to "never"
- Wifi sleep policy in spare parts set to "never"
- ESN swapped twice.
Anybody have any idea on what the hell I can do? BTW: My wifi is almost never on, so I don't think it's related to the WIFI handing off to 3G issue, because I RARELY use WIFI, and this happens (just happened again like 10 minutes ago), and there's no networks here it can even connect to, AND it's disabled.
I'm completely getting killed by this connection issue, b/c it stops randomly, then I don't get e-mail until I take notice that I'm not getting e-mail .
Pretty sure I'd take the SD card corruption issue AND the voice issue over this problem... :'(.
Problem resembles the invalild key issue that happens when switching ROMs, but the ESN swap twice (after two different ROMs were installed) seems to have ruled that out...or maybe I'm not doing something right about the ESN swap? Does the OTHER phone have to be activated during its time?
Anybody have any other fixes I can try?
EDIT:
Problem persists on all MTD AOSP GB ROMs, but right now I'm on CM7-29 with the EC09 modem, ESN swapped after modem flash.
Syndacate said:
Hey,
I've been experiencing data connection loss on CM7-14/29, latest VGB, and PP (all MTD/AOSP GB ROMs).
Issue: Randomly, during the day, my internet dies, SMS/Voice appears unaffected.
This results in no connectivity on any apps, the 3G symbol is still there, but is white.
Turning it into airplane mode for 15s or so and then turning it back seems to fix the problem.
Attempted resolutions:
- Wifi sleep policy set to "never"
- Wifi sleep policy in spare parts set to "never"
- ESN swapped twice.
Anybody have any idea on what the hell I can do? BTW: My wifi is almost never on, so I don't think it's related to the WIFI handing off to 3G issue, because I RARELY use WIFI, and this happens (just happened again like 10 minutes ago), and there's no networks here it can even connect to, AND it's disabled.
I'm completely getting killed by this connection issue, b/c it stops randomly, then I don't get e-mail until I take notice that I'm not getting e-mail .
Pretty sure I'd take the SD card corruption issue AND the voice issue over this problem... :'(.
Problem resembles the invalild key issue that happens when switching ROMs, but the ESN swap twice (after two different ROMs were installed) seems to have ruled that out...or maybe I'm not doing something right about the ESN swap? Does the OTHER phone have to be activated during its time?
Anybody have any other fixes I can try?
EDIT:
Problem persists on all MTD AOSP GB ROMs, but right now I'm on CM7-29 with the EC09 modem, ESN swapped after modem flash.
Click to expand...
Click to collapse
I had the same problem try flashing back to a VZW rom (dl09,eb01, or ed05) and run it for a day and see if you have the same problem...I did and brought it into Verizon none the less with eb01...(not an official Verizon release) and they confirmed my modem was hosed...they over night'd me a new one and I sent the old one back with eb01 on it and they never gave me a problem!
Sent from my SCH-I500 using XDA App
efan450 said:
I had the same problem try flashing back to a VZW rom (dl09,eb01, or ed05) and run it for a day and see if you have the same problem...I did and brought it into Verizon none the less with eb01...(not an official Verizon release) and they confirmed my modem was hosed...they over night'd me a new one and I sent the old one back with eb01 on it and they never gave me a problem!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I ran UKB 2.1 for like a week, last week. Not a hiccup. I don't think this is a HW issue, had no problems on UKB, nor OEM Froyo, nor OEM Eclair.
This is the second one (first one's camera HW was dead after like 2 weeks of use, verified by VZW), I really think the modem HW is fine, that's an issue with my setup or my process of flashing or something along those lines, still possibly key related for the authentication keys with Verizon if I'm not doing something right in the ESN swap process.
Maybe I'll try pushing a non-EC09 modem tonight (like ED05) and see if that fixes the issue, any other modems I should try? This problem sucks, just went to lunch, came back, no data *sigh*. Posted this right before I left for lunch (about 1.5 hours ago), right after it happened earlier...
Syndacate said:
I ran UKB 2.1 for like a week, last week. Not a hiccup. I don't think this is a HW issue, had no problems on UKB, nor OEM Froyo, nor OEM Eclair.
This is the second one (first one's camera HW was dead after like 2 weeks of use, verified by VZW), I really think the modem HW is fine, that's an issue with my setup or my process of flashing or something along those lines, still possibly key related for the authentication keys with Verizon if I'm not doing something right in the ESN swap process.
Maybe I'll try pushing a non-EC09 modem tonight (like ED05) and see if that fixes the issue, any other modems I should try? This problem sucks, just went to lunch, came back, no data *sigh*. Posted this right before I left for lunch (about 1.5 hours ago), right after it happened earlier...
Click to expand...
Click to collapse
idk man doesn't sound good. I am getting a replacement for mine (i somehow fried my modem/data or something?), but I just may never flash a rom again because ever since I started flashing my modem has become worse and worse... and now it is completely fried.
I have tried flashing a million modems before without a change, so I doubt that will help you. I would just recommend going BACK to what worked, and sticking with it, or you could fry your **** like I did.
i'm on miui 8.19 and every once in awhile i get a force close for android.phone and my 3g disappears too
I always had very weird data problems on 2.3 MIUI/CM7. The market would hang constantly or the browser would. I'd have to turn on airplane mode etc to get it back to normal.
Elluzion said:
idk man doesn't sound good. I am getting a replacement for mine (i somehow fried my modem/data or something?), but I just may never flash a rom again because ever since I started flashing my modem has become worse and worse... and now it is completely fried.
I have tried flashing a million modems before without a change, so I doubt that will help you. I would just recommend going BACK to what worked, and sticking with it, or you could fry your **** like I did.
Click to expand...
Click to collapse
Umm...ok.
Not trying to be a **** here but flashing the modem software has no impact on the modem hardware itself. Now, it is possible for modem firmware with an issue to cause damage, however, this is unlikely. The modem images are proprietary blobs swiped from OEMs, they're not tweaked by hackers in the Android community. I'm sure some OEM could figure out how to cause damage with one, but realistically they should be fine, even if the OEM was trying to kill it.
If your modem is getting worse and worse, regardless of what you did, it sounds like you had a hardware issue from the start. If that's the case, I'd suggest getting your phone replaced by VZW.
I would be extremely surprised if our problems are related. I'll keep it in mind, though.
T Nigs said:
i'm on miui 8.19 and every once in awhile i get a force close for android.phone and my 3g disappears too
Click to expand...
Click to collapse
Force close on what?
I don't get any force close, 3G just silently fades (not completely, goes from green to white). It still shows 1x or 3G accordingly, though. It's just white, hence, useless. Airplane mode for 10s fixes it.
Does this only happen on MIUI? Mine is pretty bad, happens like once an hour.
DevinLeFevere said:
I always had very weird data problems on 2.3 MIUI/CM7. The market would hang constantly or the browser would. I'd have to turn on airplane mode etc to get it back to normal.
Click to expand...
Click to collapse
Yeah, I expect either of them to glitch or hang if there's no network connection present, I have no issues with that. I have an issue with the fact that there is no network connection present .
Hi guys,
Lately I've been having problems with the WiFi and BT.
I know it has been like that for a while but I only noticed it yesterday.
The BT on the phone doesnt work - when I try to turn in on it just doesnt... I press the button and it stays the same way.
The WiFi doesnt work - when I try turning it on it says ERROR. and stays like that... not on and not of.
And not only that, another thing is that my phone started crushing A LOT.
I have no idea what's going on... it can crash at any moment without worning... not always coming back (sometimes I have to pull the battery out).
it can happen after 1 minute or after 3 hours...
the 2 things that changed on the phone lately are:
1. swiched from neutrino 2.8EE to 2.9EE.
2. I was in a vecation and when I tried to charge the battery it got only upto 82%. didn't cross it no matter how long it was in...(it was like that for a week).
I have to phone for like a year and a half.
help? anybody?
This is a known problem and it's been reported countless times already. Unfortunately the most likely reason is that your wifi/bt chip is fried. This is a hardware issue (more specifically, a design flaw) and there is no workaround. It has affected many others and they are just as pissed off about it as I'm sure you are. Some even say all Atrixes will sooner or later end up this way because of this design flaw.
Not sure about the crashing, but it could be related to broken wifi/bt.
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
rain91x said:
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
Click to expand...
Click to collapse
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Alonleibo said:
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Click to expand...
Click to collapse
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.
edit: i tryd it, but still not good. Other solutions?
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.
Sent from my Motorola Atrix 4G
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
It is frequent bug on Android phones. (wifi - error)
https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
MdX MaxX said:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
Click to expand...
Click to collapse
I did turn it off... eventually.
but my phone still crashes... at the same frequency...
*added alogcat files of 2 of the crashes... if anybody can understand it...
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
Greetings all. Long time lurker and first time poster just for this dilemma.
I have a MB 860 that was given to me to be my new ForeverPhone. WiFi is stuck at a perpetual grayed out "On" where it is instructing me to connect with WiFi to see networks. Sounds typical and you are about to yell at me for not using the search function, right?
But here's the kicker: Bluetooth works and works well. It connects. It disconnects. It is glorious.
All the other threads are about a combined WiFi/Bluetooth failure. I don't have that combination. And none of the threads solve my problem.
Here is what I did before the WiFi borked on me:
Unlocked the boot loader.
Installed the KitKat ROM for the phone based unofficially on CM 11. (Works a treat, too!)
Requested and received an unlock code from ATT so that I could travel internationally.
Attempted (thrice) to unlock the carrier lock while inside a Rooted non-stock ROM. (I didn't know better.)
Carrier unlock code failed ... but so suddenly did WiFi.
WiFi now not working, I then went on to:
Reverted to Stock so as to carrier unlock. Stock revert worked.
Carrier unlock then worked.
Stock's WiFi said "Error" instead of OFF/ON.
Stock started randomly rebooting.
Returned to KitKat of Gloriousness. Returned to a still non-functioning WiFi but at least without the random reboots. Enjoying my carrier unlock freedom.
So, now I ask you all ... what happens if WiFi is borked but Bluetooth still works. What then? Likely not a hardware problem, right?
So what do I need to flash/fix? What bit of code in what place got corrupted from me trying to carrier unlock from a rooted ROM? And where can I find the correct bit of code to replace it with?
Thank you ever so kindly!!!!
PS: Not that you need it, but I got you some pictures of the non-functional WiFi so you can see what I am perpetually stuck with. (Again, Bluetooth works!)
theinfamousj said:
Greetings all. Long time lurker and first time poster just for this dilemma.
I have a MB 860 that was given to me to be my new ForeverPhone. WiFi is stuck at a perpetual grayed out "On" where it is instructing me to connect with WiFi to see networks. Sounds typical and you are about to yell at me for not using the search function, right?
But here's the kicker: Bluetooth works and works well. It connects. It disconnects. It is glorious.
All the other threads are about a combined WiFi/Bluetooth failure. I don't have that combination. And none of the threads solve my problem.
Here is what I did before the WiFi borked on me:
Unlocked the boot loader.
Installed the KitKat ROM for the phone based unofficially on CM 11. (Works a treat, too!)
Requested and received an unlock code from ATT so that I could travel internationally.
Attempted (thrice) to unlock the carrier lock while inside a Rooted non-stock ROM. (I didn't know better.)
Carrier unlock code failed ... but so suddenly did WiFi.
WiFi now not working, I then went on to:
Reverted to Stock so as to carrier unlock. Stock revert worked.
Carrier unlock then worked.
Stock's WiFi said "Error" instead of OFF/ON.
Stock started randomly rebooting.
Returned to KitKat of Gloriousness. Returned to a still non-functioning WiFi but at least without the random reboots. Enjoying my carrier unlock freedom.
So, now I ask you all ... what happens if WiFi is borked but Bluetooth still works. What then? Likely not a hardware problem, right?
So what do I need to flash/fix? What bit of code in what place got corrupted from me trying to carrier unlock from a rooted ROM? And where can I find the correct bit of code to replace it with?
Thank you ever so kindly!!!!
PS: Not that you need it, but I got you some pictures of the non-functional WiFi so you can see what I am perpetually stuck with. (Again, Bluetooth works!)
Click to expand...
Click to collapse
What stock version are you using? Have you tried flashing an sbf?
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
What stock version are you using? Have you tried flashing an sbf?
Click to expand...
Click to collapse
I rolled back to the nandroid backup that I made of whatever stock version ATT had put on the phone. Gingerbread, I think.
As for flashing an sbf, I cannot find any online that are still at good hosting links. I looked and looked and looked. Will that do more than a nandroid backup of stock?
theinfamousj said:
I rolled back to the nandroid backup that I made of whatever stock version ATT had put on the phone. Gingerbread, I think.
As for flashing an sbf, I cannot find any online that are still at good hosting links. I looked and looked and looked. Will that do more than a nandroid backup of stock?
Click to expand...
Click to collapse
An sbf hits every partition available, a backup only hits select ones. Now if wifi will not turn on at all, even after a backup is restored, then your wifi chip is dead, time for a replacement
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
An sbf hits every partition available, a backup only hits select ones. Now if wifi will not turn on at all, even after a backup is restored, then your wifi chip is dead, time for a replacement
Click to expand...
Click to collapse
The problem with the "the wifi chip is dead" argument is that it is an integrated chip with Bluetooth so if the chip is dead, both should be nonfunctional. And Bluetooth works.
But I'm game to try to sbf. Do you have a link to a working, reputable sbf for the MB860?
theinfamousj said:
The problem with the "the wifi chip is dead" argument is that it is an integrated chip with Bluetooth so if the chip is dead, both should be nonfunctional. And Bluetooth works.
But I'm game to try to sbf. Do you have a link to a working, reputable sbf for the MB860?
Click to expand...
Click to collapse
The results you are experiencing is normal. I'll post the sbf in a few mins on my G Drive and will provide the link.
https://drive.google.com/file/d/0B52pkPIFU2dRQ1BMZk5fVmc2OVE/view?usp=sharing
Many thanks. Unfortunately, that didn't fix it.
However, I purchased a few other Atrix 4Gs from eBay and was able to confirm that trying to unlock while inside a CM rom does, indeed, kill WiFi consistently. So it cannot be a hardware issue.
Then I used the last one to be my permanent phone and unlocked it properly, before doing anything snazzy to it.
So for those people who still have Atrix 4Gs, now we know a new thing: SIM unlocks need to be done on a stock ROM or else!