Search results

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...

Where do you live? I experienced that in the Lehigh Valley (Bethlehem, PA). No LTE in Erie, PA, yet... Sent from my Nexus 4 using Tapatalk 4 Beta

If you're using an AOSP ROM, you can edit the paths directly in the source code and recompile. Sent from my Galaxy Nexus using Tapatalk 2

You could buy just the USB dongle for the tablet, and use that in lieu of the dock. It's a lot cheaper. Sent from my Transformer Pad Infinity TF700T using Tapatalk 2

If I am not mistaken (though, I could *totally* be wrong), I think it needs to be in BLOB format for fastboot. Anyone, please correct me if I am wrong. Sent from my Transformer Pad Infinity TF700T using Tapatalk 2

I am using the Logitech Android Tablet bluetooth keyboard (and tablet mouse) with my TF700. I must say, it is absolutely awesome. I was going to buy a dock, but I am kinda glad I didn't. But opinions on dock vs. BT keyboard aside, it functions very well. I am running CM10 on here, and I am not...

How did you accidentally flash the CDMA one in the first place? That might help in reverting... Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

I was just successful at getting an exchange at my local Best Buy. Unlocked, rooted, running a self-built CM10. I walked directly to customer service. I cited WiFi/GPS issues. I explained to them that I already contacted ASUS, who referred me to Best Buy, who I called and was told to "take it...

It could be similar to the way boot flags don't (I mean, are supposed to...) work on the tf201/tf300t models... You may have to dd away a few bytes on one of the partitions via adb. I don't own a N7, so I can't guarantee or confirm. Good luck! Sent from my Galaxy Nexus using Tapatalk 2

Mine did that the other day when I switched from rooted stock JB to CM10 preview builds. I don't believe there is any correlation there, or that it's a software issue at all. I blew out my USB port with compressed air at 90 psi; it works again. Sent from my Transformer Prime TF201 using...

For WiFi, check out build.prop, as well as ensure all the firmwares are in the appropriate paths. I haven't dug too deep on my GN, but it appears Google has made some path changes. I also didn't read the whole thread, so perhaps this was already mentioned. Sent from my Galaxy Nexus using...

Got my 2 dongles today, ordered roughly 1.5-2 weeks ago. Sent from my Transformer Prime TF201 using Tapatalk 2

I had this issue earlier. The /sdcard/ "folder" is actually a bind-mount type setup (I think it's done with fuse). Anyhow, it's designed to emulate an actual FAT32 SD card, which would not have file permissions. The actual path of the "sdcard" is /data/media, where files are stored with their...

I will be getting my GNex soon. I will investigate when I have it in my hands. Sent from my Nexus S using Tapatalk 2

Yeah bro, it's gotta be the colonel. Perhaps Colonel Sanders. Actually, I'm just messing with you; I have no idea. I didn't even read the thread. I know this is totally off-topic, but, you gotta have at least a few off-topic posts, right? But yeah, ICS is sweet. There were a lot of...

You might just want to do: rm -rf device/bn/encore/ and then repo sync again. Sent from my Nexus S using Tapatalk

Hey everyone: Sorry about the little snafu on my website, there. Seems there was a little issue in the way I had WordPress running. Should be stable now. Thanks for your patience.

You can download it here: http://goo.gl/vTTTA

I don't see why not, as long as it's compatible with your hardware. No problem dude, glad to hear you're enjoying it! Let me know how performance is for you.

I'm not sure. I'm not going to say "yes", as I have an i9020t, and have only tested it on that. But, if you want to go ahead and try it, that's on you. From what I understand, it should be OK. But as I said, I have not tested it in that configuration, so that's your call.

New radio I9020XXKI1 and bootloader I9020XXKL1 are ready. Download them here: http://goo.gl/vTTTA

Hello everyone, I've extracted and packaged the new radio and bootloader images from the ICS update that was released today. The new radio image is I9020XXKI1 and the new bootloader image is I9020XXKL1. I have packaged the new radio as both a .img for fastboot, and an update.zip for flashing...

I've got KI1 going, seems to be working well. Will release in a few, as an update.zip and a raw image for fastboot flashing. Sent from my Nexus S using Tapatalk

I would hope so. But on a positive note: This is exciting, 3.x is a decent upgrade from 2.6.35. I can't wait to see everything get integrated, and see this in CM9 :) Sent from my Nexus S using Tapatalk

This is wonderful. Sent from my Nexus S using Tapatalk

I'll just leave this here... http://goo.gl/NxZnH (It's Mms.apk, with the "Black Background" option in place. It's about 80-90% complete. It looks absolutely amazing. I just have a few small details to straighten out before I submit my code to the CM team.) Let me know how it works for you! $...

Anyone interested in "Black Background" for Mms.apk? Hey everyone, I'm working on adding "Black Background" to Mms.apk -- it's coming along somewhat well. Is anyone interested? Once I finish, I will definitely release it. Check it out (screenshot (not apk) attached to post)

Unfortunately, the Wallet issues will (pretty much) only be able to be fixed by a full data wipe. Good luck there. Anyhow, I've noticed that purchasing paid apps does not work. Upon clicking the price, it attempts to load the purchase screen, however, an error occurs. I've got a logcat of the...

Koush is a hero...and a meme, too, I guess. Thanks dude! Sent from my Nexus S using Tapatalk

If you guys are familiar with adb, you can help me out. Pastebin the output of `adb logcat` and `adb logcat -b radio` Start the commands while on your home screen. Open the app. Hit enable. Wait one minute. Send me the results. That'd help me out immensely. If not, I will try to get to...

Huh? We're talking about the GSM Nexus S here... Sent from my Nexus S using Tapatalk

I can fully host your project (web, public/private git, irc, whatever else you want) for a reasonable monthly price. Sent from my Nexus S using Tapatalk

Well, what areas specifically are you lacking in? Sent from my Nexus S using Tapatalk

Hey everyone, I may have a *possible* fix for the corrupt EFS/NV data issue. I need some testers. In order to qualify to test, you must meet these criteria: - WILLING TO RISK PERMANENTLY BRICKING YOUR NEXUS S - Advanced understanding of: -- Android itself -- Android's inner workings -- the...

I think compcache is useful. I'm hoping it'll get fixed, sooner or later. I mean, we do have more RAM than the older-generation devices, but, it's wonderful. Compcache (zram) gives about a 3:1 compression ratio. If we compress 18% of our 344MB of RAM, we're compressing about 62MB of RAM...

I guess that makes sense, because it (apparently) worked correctly on 207, failed on 211/212. Perhaps my memory isn't the greatest, but I really do remember there being compcache+JIT problems, at least initially. Perhaps it was fixed with time? Anyhow, at least on 211+, compcache + JIT royally...