Database Users

PAM Enabling Directions?

While rooting the phone will allow for all sorts of stuff I am mostly interested in getting past the second NAI check Sprint has (which was easy to do with the Instinct.) I found some directions at http://www.insiderforums.com/forums/showthread.php?t=31642 but these aren't working right for me. Perhaps someone else can give them a try?
Also, when I bought my Hero from Best Buy I did get a sheet of paper with the phones "password" on it. I thought this was the MSL but it doesn't work to actually unlock the ##DATA# editing (though put in by itself it will show the ESN info.) If this isn't the true MSL what can I tell Sprint is the reason for giving it to me? (A factory reset use to be a good excuse but this is built-in command on the Hero.)
Thanks.

Hi, I finally got my MSL, so I'm going to try this now...will report back with the results.
Also, I got my MSL today by doing an ecare chat session, and told her that I was having problems with my voicemail, and that I'd like her to walk me through a manual provision so we could properly set up my number and MSID number. She didn't ask any suspicious questions, just helped me and immediately gave me my MSL.
EDITS:
-So far I have a different version of QPST, and it didn't recognize my hero, so I'm downloading his new version. will post back soon.
-I put the new build of QPST on my Vista machine, and it still doesn't recognize my phone model. I can add the USB port (on mine COM 8) but it still says unknown phone...crap. I'm going to try it at home on my XP Machine to see if that makes a difference. Will post back with results.
-Tried on an XP laptop we have here at the office. Still no go. It's not recognizing my phone model. I see that you posted exactly the same thing I'm seeing in that forum. Want to relay that to him? I don't have an account. Also, I COULD get into it on my other version of QPST, however, I just chose one of the umpteen models in there, none of which applied to my hero. They were all like "FFA-1330" and stuff like that. Nothing hero looking. I noticed when doing some more research that this can happen with older versions of QPST. Wondering if a newer version would make a difference, or maybe Chris is using a different version than 2.7.301.
-Found a newer version of QPST, version 2.7.323, downloading now at a painfully slow rate.

JACKPOT!
This version of QPST properly works and found my phone as a "FFA/SURF 7600" phone. I'm now following his guide to see if I can't get it to work.
Since this was a success, I felt it should be in another post
EDIT:
OK, so I followed his guide, copied my NAI into tethered NAI, and when choosing "Write to phone" I got a write error reported. It states under the NV Item column "NV_UE_IMEI_I" and under the Status column "NV_READONLY_S"
When I again chose to read from phone, it seems that the change is still in there. I'm going to do the all important test, and will report back as to if it actually works. I'm giddy like a schoolboy right now.
--Well, I still get the error 67 and error 65, so it appears it didn't work. Phooey. I'm still going to mess with it more to see what happened. I felt good about it, and maybe there's still some hope.

Same. I updated both Profile 0 and Profile 1. Same "read only" error but after a reboot, update profile, and rerunning QPST the changed values appeared to be there but still 65/67 errors.

Any one else try this yet?
Just wondering if any one has any luck with this now? I am downloading QPST now.

It would be great if someone who already has a grandfathered PAM ability for their Hero to try this and report what they are seeing. Also the output from ##DATA# to see what if anything there is different.

Same Thing
No Joy.
I just followed the same steps and had the same thing happen as kmartburrito.

I'll get this to work, I've enabled PAM on every sprint phone I've had since they introduced the unlimited data plan bout 5-6 years ago
we're going to get the MSL number and instead of writing to phone we'll just edit the settings in phone (safer than hard writing stuff that might screw with your MEID & ESN settings)
I'll post when I get it to work, just wanted to let yall know I'm hot on it.
**********************************************************
This is a modified guide I wrote for the instinct that will walk you through how to get your MSL code and what to do with it.
DISCLAIMER, I am ###NOT### responsible for any damage you do to your phone or your phone network with this information
**********************************************************
some uers still getting errors, if you fall into this catagory, you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]rs.co...U_Hero_C_Sprint_1.29.651.1_signed_release.exe
---- How to access programming and service menus---
On your phone go to the dialer, then dail in any one of these codes below and after the last # you should get the menu or it will ask for "current code" aka your MSL #
##data# (##3282#)
##debug#(##33284#)
##diag#(##3424#)
##svn#(##786#)
##prl#(##775#)
##prev#(##7738#)
##akey#(##2539#)
##vocoder# (##8626337#)
-------How to get your MSL code---------------
1) download required 3rd party apps
download demo version of CDMA WORKSHOP from
http://www.cdma-ware.com
newest version of qpst 2.7b323
http://rapidshare.com/files/297770360/qpst.zip
download of sprint's official phone as modem (PAM) software
Smartview for Windows
http://www4.sprint.com/pcsbusiness/down ... s_1.16.exe
Smartview for Macs
http://www4.sprint.com/pcsbusiness/down ... c.mpkg.zip
download HTC Sync
http://www.htc.com/us/SupportDownload.aspx?p_id=300&cat=3&dl_id=716
2) install the HTC HERO DIAG drivers
http://rs79.rapidshare.com/files/293529424/HTC_Hero_DIAG_Drivers.zip
3)connect your phone via usb cable
4)dial ##diag# (##3424#) on your phone for diag menu, when prompted direct windows to diag drivers listed above
5)run CDMA WORKSHOP, settings at main screen on the right are as follows
com settings (AT mode)
---------------
Port (com#) <--- click port and it should say "HTC DIAG COM PORT"
Baud rate (115200) <--- use this setting
com settings (DM mode)
---------------
Baud rate (115200) <--- use this setting
6) you should now be able to hit <connect> if it was successful you'll see in status bar <connected to com#>
7) now click <read> after a moment all your info will come up on left panel, phone # etc
8) click on security tab change the right panel setting and look for the following block
SPC/User Lock
----------------
Defualt (nv_read) <--- use this setting
9)now click read if done sucessfully you'll see the block below this option flash red and give you a number
10)note the 6 digit number under <SPC/USER LOCK> the one that flashed red, ****this is your MSL number***
***** just an additional warning***** you can REALLY and I mean REALLY screw up your phone if you change one of the settings in those menus if you don't know EXACTLY what you are doing. This isn't for the faint of heart or the random tinkerer.... just be warned

;;;;;;;;;;;;;;;;;;;;;;

So in reading your post, it seems the only thing I haven't done is modify my profile 0 in qpst, since I've already modified profile 1 per the guide on insiderforums in the original post by gilroykilroy. Does all that sound correct?
Thanks for writing up that guide Johnson!

If I understand the directions johnsongrantr posted you are replacing the profile 0 NAI with the profile 1 NAI. I tried that and after it initially seemed to work it gave me error 67 when I booted my phone and tried to connect to the network and/or trying Update Profile.
Also note that my phone has [email protected] (not mcs.sprintpcs.com).
I seem to have better luck leaving the settings along and using the race-condition method.
Alas still no luck getting my Mac to recognize the phone connection.

Updated profile 0 as described but still getting error 65/67. Is there some other step to turning on the PAM other than in the setting "Mobile network sharing"?
Update:
Just tried to update profile: cannot update profile and get Error 67.

redcloud said:
Updated profile 0 as described but still getting error 65/67. Is there some other step to turning on the PAM other than in the setting "Mobile network sharing"?
Update:
Just tried to update profile: cannot update profile and get Error 67.
Click to expand...
Click to collapse
it worked on mine, but it may be something to do with your account.... you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
UPDATE: the [email protected] is hcm, I wasn't paying attention, I'll try copying that over and see if I have the same results.... my [email protected] worked on my htc mogul as well... let me give it a shot though
UPDATE2:the number you deleted is your ESN in hex format you'll see it at the top right in service programming just replace it with "number"@hcm.sprintpcs.com and paste it in tethered NAI, sorry for any confusion

johnsongrantr said:
it worked on mine, but it may be something to do with your account.... you can recover via SPRINT RUU which will wipe your phone
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
UPDATE: the [email protected] is hcm, I wasn't paying attention, I'll try copying that over and see if I have the same results.... my [email protected] worked on my htc mogul as well... let me give it a shot though
UPDATE2:the number you deleted is your ESN in hex format you'll see it at the top right in service programming just replace it with "number"@hcm.sprintpcs.com and paste it in tethered NAI, sorry for any confusion
Click to expand...
Click to collapse
Nope, still 65/67 errors here with NAI and Tethered NAI of profile 0 being the same string:
[email protected]
There must be something else to change.

I've also tried this to no avail... tried a few different things:
1) tried replacing the Profile 0 NAI with the Profile 1 NAI
2) tried copying the Profile 1 NAI to the Profile 0 Tethered NAI
3) tried copying the Profile 1 NAI to the Profile 1 Tethered NAI
4) tried replacing all Profile 0 settings with Profile 1 settings
5) tried copying Profile 1 settings to Profile 2
Nothing seemed to help.... still errors.

Yep...same for me, I've updated the tethered NAI in both profile 0 and 1, reset the phone, waited for a half hour, and still get the error 67. Keep on brainstorming guys, we'll beat this thing

can anyone put the rapid share files up on a different server or sharing place, rapid share is terrible. plus i can't download. it says there are no more open slots to download from. i need the qspt and the drivers. thanks in adavance

WRMG3 said:
can anyone put the rapid share files up on a different server or sharing place, rapid share is terrible. plus i can't download. it says there are no more open slots to download from. i need the qspt and the drivers. thanks in adavance
Click to expand...
Click to collapse
Here you go man, this is to a zip file called "HTC Stuff" that has both QPST 2.47.323 and the HTC Diag Drivers.
http://www7.zippyshare.com/v/50608704/file.html

thanks man, i figured i would give this a try when i got home. rapid share for some reason wouldn't let me download it and kept telling me that i had to be a premium member to download the files.
have you had any luck getting this to work on your phone?

WRMG3 said:
thanks man, i figured i would give this a try when i got home. rapid share for some reason wouldn't let me download it and kept telling me that i had to be a premium member to download the files.
have you had any luck getting this to work on your phone?
Click to expand...
Click to collapse
Nope, no luck yet. I along with a few others have had the same resulting 65/67 errors after updating the NAI settings on both profiles, so still now it's a no-go. I don't know if it's working on anyone's CDMA Hero at this point, so we may have to wait until it is rooted, which I can only imagine when that will happen, although hopefully soon!

Cannot Connect to network after unlock (clean up) FIXED

Hurrah! this has been fixed WOO!.
see here.
well done guys, you have made me a happy g2 owner again!!
Hi Everyone,
i figured we might need to clean up the
http://forum.xda-developers.com/showthread.php?t=805024
conversation.
as i see it, there are 2 issues
1. people receive an unlock code, the phone accepts it but then it cannot find any network
2. people receive an unlock code, have troubles entering the code but eventually get it in ok.
please do not post anything "setting" related - apn's, bands etc as this has been tried and shown not to work (yet)
it might be helpful if people who have issue number 1 could post some answers to some questions.
as i am not at all smart enough to work out what we need to know from these people, id appreciate it if those in the know could pm me what they think could be useful, and ill make a template for people to follow
troubleshooting template
----
----
----
----
Current Theories: (please PM me if i have anything wrong here or if i need to add details.)
-------------
Theory #1
Ghul99: the code is accepted, but the phone is still locked?
http://forum.xda-developers.com/show...&postcount=121
------------
interesting information
this seems to support theory #1
1. i unlocked phone - code entered successfully, and i was no longer prompted to enter an unlock code
2. i perm-rooted my phone - all went to plan
3. i put the vision rom on my phone (http://forum.xda-developers.com/showthread.php?t=834450) loaded ok
4. i put a sim in my phone and now i am prompted for an unlock code.
5. i tried to re-enter my code but it would not accept it (it is the same code from step 1)

Nice idea for taking the initiative to clean up the thread which was getting excessilely long!
I'm hoping we can see some progress in a few days as I'm really missing being able to get any cell reception on a MOBILE PHONE!?
Regards.

I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App

guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's really exciting.
Thanks for bring up the good news!
Sent from my T-Mobile G2 using XDA App

guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Just to help guhl and catch up with some unnecessary posts.
Common solutions like Reboot, different sims to try, Hard reset, flash stock ROM or trigger the unlock window to reenter the code doesn't work

Summary of my knowledge so far
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
Which information could help us:
1. The output of the following AT-Command sequence from successful and unsuccessful unlocks
Code:
ATE1
ATV1
[email protected]?
[email protected]?AA
[email protected]?40
[email protected]?80
I will try to write a HowTo later for Windows.
For linux see the following posting from the old thread (http://forum.xda-developers.com/showpost.php?p=8750299&postcount=121)
2. The next thing that would help is a logcat from the first unlock process itself.
Howto:
Start the first logcat using the USB-cable and adb before you boot the phone with the foreign SIM.
Code:
adb logcat -b radio > lc_unlock.txt
leave the logcat running and complete the unlock procedure till the phone reboots (the logcat will end automatically)
As soon as the first logcat exits start a new one using:
Code:
adb logcat -b radio > lc_after_unlock.txt
leave it running for 1 minute and then stop it using <Ctrl>-C
3. The next thing that really would help is that you do not post anything in this thread (use the old one instead) that has to do with:
- the APN
- trying another SIM (you would be very lucky if you had one that fits the arbitrary SIMlock)
- reboot, factory reset, use a stock or non stock firmware
- use the hw/sw-keyboard, wait for the right outside temperature or other esoteric procedures
Finally I would like to ask moodecow to edit his original posting and incorporate or link everything that he finds important or helpful in his posting so that it will stay an top.

That is some very exciting news, thank you for the update!
One quick question, when we achieve radio-s off it esssentially would mean everyone could unlock their phones for free?
Thanks.
Sent from my T-Mobile G2 using XDA App

I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.

ms93 said:
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
Click to expand...
Click to collapse
Your first idea sounds reasonable and I would support it.
Your second idea is something that is worked on, but you do not only need the correct file (which is actually called DMCID.dat) but there also has to be some "magic number" (like on a gold card) on the micro-sd card.

an important piece of info to carryover from other thread:
1- No APNs are listed
2- if you try to define one, it doesnt save

No APNs being listed is related to the rom more or less, not the issue we're having.
APN is software issue, correct me if I'm wrong so either way it shouldn't pose as an issue to us.

im saying its a symptom that seems to go along with the problem in the title of this thread, so, worth noting.
ie: i think everyone who has the post-unlock no-connection problem, cannot save APNs. all others can.
if you are a counterexample please say so. that would help.

guhl99 said:
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
.
Click to expand...
Click to collapse
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect

kabir_del said:
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
Click to expand...
Click to collapse
Posting any further details and/or pictures would be much appreciated!

So if megasim has failed due to corruption I think that the only way to solve our issue is to write directly to emmc partition holding locking information. And I don't now how easy and plausible this is...

I think if we get S-Off for Radio, we'll be able to write to that partition. I hope

andrewklau said:
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
Click to expand...
Click to collapse
I am a little bit worried about writing this information directly because the partition will be encrypted.
And also copying the complete partition from a working phone or one that is still unlocked will not be an option because the IMEI will also be there and we would not want to overwrite that.
So my hopes are more that there is some kind of a restore procedure from a secure area (I know that Nokia phones can do this, but HTC ?) or that we can lock the phone again with the SIMLOCK option in hboot.
Sent from my T-Mobile G2 using XDA App

well I guess time will tell, does tmobile or htc do replacements (or has anyone tried) for phones no longer on a contract or that are now unlocked?
Sent from my T-Mobile G2 using XDA App

andrewklau said:
Posting any further details and/or pictures would be much appreciated!
Click to expand...
Click to collapse
here we go Pictures first Video coming soon
First Red colour is the error we get on when we try the command
1=clear s58 data
2ND IMAGE is the one when we press the DEVICE INFO
today is sunday not much time will upload the full clear video tommorow and still i have not tried to the all options of the diag maybe it can repair it but sure i will do some more things tomm.
88

I have tried to use my HTC vision G2 as I unlocked it but after that I am unable use as I am unable to find anything which would be hlpful for me as I have the first case problem. I just want to know that would it help me that if someone would flash my HTC Vision G2. I just want to know about that as now I am in Pakistan
Sent from my T-Mobile G2 using XDA App

[Q] Whats the CSC access code now? (ICS)

Hi Guys!
Anyone got any idea what the new dialler codes are for this baby? Old CSC access code doesn't work...

try the anycut app in play store, choose all activites-->custom activity, there should be a long list, find service mode, or personilization(to change CSC).
or are you referring to *#1234# ? that info should be accessible as well from service mode.
Also BE CAREFUL in there, try not to press anything you are not sure of.

Hmm. Nope. neither method works...

The *#1234# does not work
Sent from my GT-P6800 using xda premium

have a look at this post.. http://forum.xda-developers.com/showpost.php?p=27179257&postcount=12
enter *#*# (code) #*#* into dialer.
for example.. *#*#197328640#*#*, should enter service mode.
remember be careful.

Still no joy guys!
Tried everything you have said, but nada. Nothings happening... anyone figure out the new codes yet?
Thanks for the help people!

if your handy with adb commands you can run the command from that post should list something. I know where to find them in .smali code.
perhaps they did change things.
does the standard mmi codes work? *#06#?

zte n850 AAA & Ha keys

Do you have any idea how to get the ha and aaa passwords off a zte n850?
I have talk text and 1x.
3g shows up time to time but doesnt work.
Ive tried revol, revolwireless, secret
Im out of ideas.
I tried alogcat while being in ##data#
Tried dsf tools, cdma ws, qpst (nvm folders locked!), qdxm.
Ive managed to get it rooted on my own.
Wrote up a guide in my sig.
Is there anyway I can use root to allow me to get thoseS?

Did you ever figure out how to get your AAA Passwords?

you can get the "number of characters" of the password via QXDM Log view

Metro, T-Mobile SiM Configuration Questions

I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.

camdecoster said:
I'm trying to diagnose an issue I'm having with my Metro (MetroPCS) SIM card. If anyone is using their X Compact on Metro or T-Mobile, could you please run the following command and let me know what the output is?
adb shell getprop ro.semc.version.cust.active
The output should be 3 digits. Mine is currently blank, so I'm trying to determine if it's because of my SIM card.
Additionally, could you go into the service menu (*#*#7378423#*#*) > Service info > Software info, scroll to the bottom and post the Current Modem Config value (I'll also need to know if you're using T-Mobile or Metro)?
Knowing this information will help me figure out my problem. Thank you.
Click to expand...
Click to collapse
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.

xXxMemerxXx said:
/system/etc/customization/modem/amss_fsg_kugo_tar.mbn
Im on T-Mobile.
Click to expand...
Click to collapse
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.

camdecoster said:
Thanks. That's surprising because there's a T-Mobile specific modem binary file that should get loaded if the SIM is recognized. The one you mentioned is the default modem binary file. I'm interested to look at what other people are seeing.
Click to expand...
Click to collapse
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.

xXxMemerxXx said:
Would loading the T-Mobile one change anything? Like better service? Because I did not have service when camping when other on T-mobile did. Other than that its been working for over 2 years.
Click to expand...
Click to collapse
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids

camdecoster said:
Probably not, but I don't know for sure. Comparing the two files, the T-Mobile file is smaller and what is shown is not readable by me (encrypted or binary blob). I just thought that it would be loading. If you run the command I mentioned, I might be able figure out why it's not loading. Running the following command would also help me out:
adb shell getprop persist.sys.sim_config_ids
Click to expand...
Click to collapse
If I'm honest, I have no idea how to do any of that. I just use my phone lol.

xXxMemerxXx said:
If I'm honest, I have no idea how to do any of that. I just use my phone lol.
Click to expand...
Click to collapse
No worries. It would involve downloading the Android debug bridge (adb) and running the commands with USB debugging enabled.