Recent content by unforgiven512

KGW42Q --> LWX48P

KGW42Q --> LWX48P

So I tried flashing manually, ended up installing TWRP and all this ****, got annoyed and just went back to some stock images I found in another thread, flashed them using fastboot. Updated to KGW42Q on first boot. Ended up doing a full wipe a few times, and finally got the goods: KGW42Q -->...

I saw in another thread somewhere that someone got their AT&T one unlocked by saying it was an AT&T Moto X. Should be doable. Submit IMEI as an AT&T Moto X and try the unlock code. If I could find the other thread, I'd link it here. I'll look for it in a little bit.

Why not just select AT&T as the carrier when you purchase the unlock code? $9.99 isn't too bad, and all devices are one SKU, so I would be comfortable in saying it should work. Sent from my Nexus 6 using Tapatalk

You need to go to the menu, select "Root Settings", then menu, "Field Test". Sent from my Nexus 5 using Tapatalk

After updating SuperSU and its su binary to the latest version, FieldTestMode is now working again! It does not appear that any changes were made to the app between 4.4 and 5.0 NOTE: You must update the su binary in addition to the app from the Play Store!! Sent from my Nexus 5 using Tapatalk

Ended up returning mind and going with the WCP-300. Had little to no luck with these, zero issues with WCP-300. Sent from my Nexus 4 using Tapatalk 4

Hmm. Some interesting observations. Not sure why GLS needs the TAC, especially because it's not guaranteed to be static, as LACs are. I'm getting a network location with the "LAC", but no cell site location. I'm assuming it's just from data Google has collected from its users, rather than...

Nope. I'll divulge my secrets after a little more testing. I want to drive to an area with better rssi. EDIT: I'm also unsure of whether this will fix the Google Location Services issues. I honestly think it has to do with the fact all the new cell sites not being in the database. I'll try to...

I got LAC (actually TAC, but whatever) working! I'll post my custom-made modem shortly. I'm using a self-built cm-10.2 ROM from today. Notice how mTac=40961 40961 == a001 in hexadecimal. Sent from my Nexus 4 using Tapatalk 4 Beta

LAC (TAC) on cm-10.2 I got LAC (actually TAC, but whatever) working! I'll post my custom-made modem shortly. I'm using a self-built cm-10.2 ROM from today. Notice how mTac=40961 40961 == a001 in hexadecimal. EDIT: Perhaps I should redact my IMEI and phone number? I'll do it in a little...

It might be showing you the TAC where the LAC typically goes. And yes, that would probably be because that phone has "official" LTE support. Anyhow, with LTE, each Cell ID is unique (per-operator), whereas on GSM/UMTS, only the LAC+CID combo was unique. You could have CID 597 on LAC 654 and LAC...

You guys do realize that LTE does *NOT* use Location Area Codes (LACs) like GSM and UMTS? This is why it's being shown as "unknown". The closest thing might be the TAC (tracking area code). And the fact that GLS (Google Location Services) is not working probably has more to do with the fact...

I'm the one that got it working on the Nexus One. Our situation here is drastically different. I've been working on it my free time. I've made a decent amount of progress; I've been pulling apart frameworks and what not. I must say, IMS (in theory) should be less complicated than GAN, however...