Help with cyanogenmod issues

[Homerboy]

Phone: Samsung S3
Carrier: TMobile

I recently updated my CM install from 10.1.X to 10.2.1
Shortly (Immediately?) after doing this, I noticed my network connection speed “E” (edge) and horrendously slow as you know.

I tried everything I could think of but nothing was getting me back to 3G.
So I decided to revert to 10.1.X to see if the update was cause of the problem I had issues reverting back – bootup got stuck at spinning CM logo.
So I decided to just go back to 10.2.1 at that point and figure out the “E” issue on that build.
Successfully went back to 10.2.1 – including the update gapps package.

However, now my problem (besides still being stuck on “E”) is that none of my apps from Google Play are downloading. If I go to the Play Store on the phone and manually search for “XYZ App” I can install it that way.
If I go to Play Store on my PC, and go to “My Apps” it will tell me “XYZ App” is installed already on my device.
If I search for a new app and send it to my phone, the app never is sent to my phone.

It’s like my Google account is different or something… and yes, it’s the same google account/email address.

Totally confused on both issues at this point. I’m not expect on phones and apps and CM builds and everything, but I’m learning… I’m just really stuck right now with these 2 problems.

Help me AT!

Thanks in advance.

 

[Suspicious-Teach8788]

Are there baseband requirements for CM? I remember the GS3 on Verizon had a specific modem that had to be installed to run CM. Go check the official XDA thread for the T-Mobile GS3 regarding CM.

 

[Homerboy]

Update: the applications seem to be installing now. Dunno if it was some weird delay on the google servers updating what was and what was not installed on my registered device or what.

But now I'm still stuck with these god awful, unusable speeds.
I had no issues with getting 3G connections on this same phone when running 10.1.X -- I know that the phone is capable of 3G with CM in my area.

Maybe it's not a 10.2.X update issue. Maybe it's just coincidence. But either way I'm stuck on "E" and its entirely useless.

 

[s44]

You probably changed your Android ID number (so the Play Store recognizes it as a new device). If you use TiBu, it will automatically restore your old one to prevent this issue... too late now though.

As for the radio... what model S3 are you on? I'm guessing that since CM went to a unified Qualcomm S3 installer, it installed an i747 (AT&T) modem on your device. Go flash a T999 (T-Mo) or T999L (T-Mo model with LTE) modem to it.

You can go to Settings > About phone to check your baseband version.

edit - Also, you're better off asking this sort of super specific question on your device's XDA forum.

 

[Homerboy]

I guess I don't care too much about the Android apps themselves -- was just more of a headache than a showstopper.

How do I flash just the modem? I was pretty confident I grabbed the T-Mo version from http://download.cyanogenmod.org/?type=stable

I will check the baseband version in a few mins. What am I looking for?

Edit: I did register at XDA developers... waiting on confirmation email though.

 

[Homerboy]

Baseband: T999UVDLJA

I don't understand this problem at all. My phone is useless except on WiFi (and I guess to make calls with )

 

[Homerboy]

IEMI is set to 0.
On with support
Telling me not a T-Mobile phone... WTH

Have to call Samsung now.
How could this happen?

 

[Homerboy]

** sigh **

Samsung just told me to go back to T-Mobile. This blows.
ANyone have an S3 for sale

 

[sweenish]

factory reset was attempted?

 

[Suspicious-Teach8788]

I'm going off my 2 years with Samsung phones, but you have to be very careful with Samsung phones. Always make an /EFS folder backup. If your IMEI is 0 or unknown you might be SOL unless you have the backups.

With that said, I need to know more information to know your exact situation. Sorry I'm not as familiar with this stuff as I was back then, but you can check XDA to see if there are ways to restore your IMEI. I've had this happen to my Nexus S, but i was fortunate to have a backup.

Even though baseband flashing should be easy, I've had it go bad before. Be very careful.

Also anytime you go to a new ROM, whether it's CM or AOKP or stock, do a clean wipe. I'm not sure if this applies to the S3, but I typically wipe /boot /system /data /cache. I believe I have a script for my Nexus S and GS2 that do that. But everything I say, PLEASE double check. You don't wipe /boot on other phones or else you can get really messed up.