Develop Bugs

[Q] Get 'Unauthorized' when trying to make calls, will not OTA

I am using the Jiminy V Rom on Cricket
I am unable to OTA or make calls on the Cricket network. when I try and make a call I get 'Unauthorized' and when I try to OTA (*228) the system says 'unable' at the very beginning. I have done many EVO's to cricket before, and I have checked and double checked all my PST settings, my MEID/MIN/MDN/PRL particularly.
Even when OTA doesnt work , I can always get voice/text working on virtually any other phone by manually programming the MDN/MIN/Home SID & PRL.
My cricket home SID is 4923 & I am using PRL 32200
I have even loaded a working evo's PST settings into this phone (via QPST, read from one phone, write to another), and get same results even after making sure the MDN/MIN & MEID are correct.
The symptoms are exactly the same as if my MEID is not in the cricket system, yet I have triple checked them (and I had someone else program another phone with my MEID and that phone OTA'd and made calls on Cricket with no problem).
Some other data for consideration Android 2.1, build Baseband 2.15.00……007.25 kernel 2.6., Radio 2.05.00.06.10, HBOOT 0.79.0000 SHIP S-OFF
I have also tried factory builds 2.2 (3.26.651.6) and 2.1, (Baseband 2.05.00.06.10,Build 1.41.651.1) with same result. Note: they did not change the PST.
Is there a factory build which will put everything back to Sprint or should I consider updating the HBoot and /or Radio?, I assume the programming for the OTA is done in the Radio?
I am stumped.

Bump, If anybody can help me with this, its been driving me up the wall for two weeks now.,

Have you tried flashing an RUU and updating everything from there? If it isn't the MEID then it might just be your phone having a glitch. Flash it using RUU and let me know.

how do you reset PST/NAM (SPC,MIN,MDN, Etc) to factory?
I have tried RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe , hboot goes from 0.92 to 0.79, radio from 2.15 to 1.39.00.04.26, and android from 2.2 to 2.1.
But the pst/nam settings remain unchanged, mdn,min, sip, nai, etc are all cricket. even the SPC is still unlocked at 000000. ANd the S-OFF flag is off, Shouldnt the RUU's re-root the phone?
Is there an alternate way to run the RUU, I have tried putting the phone in HBOOT usb mode, then run the RUU but with three different batteries it tells me they are too low (under 30%).
Should I be in Hboot mode to run RUU? (I have been running it from the PC with the phone booted up.

To answer a couple of my own questions, none of the RUU's reset the EPST whether they where loaded from the PC via the .exe method or from the SD card PB31IMG method.
I found a reference to ##786# and found that yes that does reset the EPST (including the SPC) back to factory.
So I figured maybe the problem would be solved, so I updated PST for cricket (MDN,MIN,SID,PRL) and tried again, still no OTA and still 'Unauthoriized; when I try to make calls.
I am starting to believe I have a hardware problem, but how can most of the phone work and yet it have (apparently) problems transmitting MEID?

Seems like no interest here or everybody stumped. I am willing to pay some one to help me resolve this. contact to my email or post here, I will certainly let the forum know when I resolve this. Thanks

GDEMI said:
Seems like no interest here or everybody stumped. I am willing to pay some one to help me resolve this. contact to my email or post here, I will certainly let the forum know when I resolve this. Thanks
Click to expand...
Click to collapse
No need to pay, I forgot about this thread lol. I think you may be right that this is a hardware problem or glitch and I am actually stumped on how to help you. :|

some help here
hi...
im trying to flash my phone and make it to worj for cricket carrier and i do everything ....i think correct but when i try to make a call it ask me if i whant to make a collect phone or buy some kind of card .
i already try the qpst configuration twice and even try many plr to and no luck
righ now i have a 45713hybryd plr
and i use this
http://forum.xda-developers.com/showthread.php?t=934417
i even take to a cricket store to chek for the s/n numbers and the min and they say that everything looks ok but i can do anything on the phone
any ideas, and help
thank

Very dirrerent problem
paulinaoza said:
hi...
im trying to flash my phone and make it to worj for cricket carrier and i do everything ....i think correct but when i try to make a call it ask me if i whant to make a collect phone or buy some kind of card .
i already try the qpst configuration twice and even try many plr to and no luck
righ now i have a 45713hybryd plr
and i use this
http://forum.xda-developers.com/showthread.php?t=934417
i even take to a cricket store to chek for the s/n numbers and the min and they say that everything looks ok but i can do anything on the phone
any ideas, and help
thank
Click to expand...
Click to collapse
Your problem has different symptoms from mine (the threadstarter), it sounds like your prl is incorrect. If you have a correct prl & sid (these can vary for the market you are in , in Phoenix the SID is 4923 and I use the old nationwide non EVDO PRL of 1040) when you dial 611 you will get Cricket, regardless of your ESN/MEID being registered with Cricket, if this doesnt work do not go further. Find a PRL/SID that works (sometimes changing CDMA connect from Auto to Home only can help) . Also make sure MNC/MNC are set to 310/0. Country code/Carrier I think.
Once you get 611 to connect to Cricket, *228 (OTA) will connect to cricket, if It disconnects you before the music starts playing and says 'Sorry....' it is most likely your MEID is not registered correctly with Cricket. In Phoenix *228 always works on EVo's as long as SID/PRL/MEID are correct,
The message you are getting about a credit card required means you are connnecting to some other carriers network (usually Verizon) which is transferring you to someplace to allow you to make a call even though you are
"not authorized" on the network. Go back and check 611 & *228.*228 will load the correct prl for your area and rate plan, check after it runs to see what was loaded. It will also most likely overwrite EVDO settings including MIP, Sip, NAI, etc.
At this point your phone should work, talk & text.

I had the same problem and I look all over. I wanted to unroot and remove jimmy v rom. I was think that if i update to the new update that it will fix it self and i was right. First I had to remove the jimmy v rom, so i got ruu to update the htboot and that let me update to the new 2.3.3. It fix it self and f***ing A.

avillal87 said:
I had the same problem and I look all over. I wanted to unroot and remove jimmy v rom. I was think that if i update to the new update that it will fix it self and i was right. First I had to remove the jimmy v rom, so i got ruu to update the htboot and that let me update to the new 2.3.3. It fix it self and f***ing A.
Click to expand...
Click to collapse
Can you be more specificwhat you loaded and what versions of hboot where involved? I downgraded to 2.1 (with RUU) and hboot .79 and it did not resolve problem.

[Q] My T999L's internal serial number does not match sticker Serial Number?

Hey all,
The tutorial I used to install the ADB prompted me to run "adb devices" when the device is connected to make sure it's working, and that the serial number of the device should show up. ADB definitely works, as I have rebooted my device and put it into recovery mode from adb; however, the serial number showing up does not match that behind the battery (have attached pics).
I tried doing "adb devices" on an old mytouch 3g slide which I have rooted and flashed CM onto, and the serial number that came up matched the one behind the mytouch 3g slide's battery.
So, questions are:
1.) Does the T999L specifically not show the serial number, but instead some other number related to the phone, when one runs "adb devices?"
2.) is it possible the previous owner of my phone did some sort of modding before returning it, effectively changing the Serial number? (i have also attached a picture of the recovery screen, which seems to be running a clockwork mod based recovery...still new to this, but don't think that comes standard on it?)
3.) If my serial number has been changed by a previous owner, is there a way to change it back, but more importantly, should I even worry about it? things seem to be working fine enough.
While I have used xda forums a couple times, this is my first post a registered user. I have watched the (very entertaining) noob video and looked for my answer, but having not found it, am posting my question in what I believe is the correct forum.
Background on the phone/situation:
I'm doing the research to flash a custom ROM onto my T999L, which I bought unlocked and used after for only a couple days for $300 bucks from a local phone shop near my apt in NYC. Currenly in India, and phone works perfectly using an Indian Carrier's Sim (vodaphone). Running the Stock ROM, which restricts using the phone as a hotspot unless you have T-mobile's stupid plan, so I want to flash to get around that.
Seems like the first step to flashing is to Root the phone, do a full Backup with a Nandroid, and then do the flash...to do this I need Android Debugging Bridge (ADB), which I have succesfully installed...just was curiously about this descrepancy I noticed though.
If anybody has suggestions on a Rom to try for the T999L, let me know! I'm thinking trying to flash the Energy HD 2.0 ROM if that works for the T999L, but the website I found out about that from is dated (top hit when you google best roms for galaxy s3, a cnet post from October 2012)
Thanks in advance!

New developments
So after further dectective work last night, i realized even though my phone was still network locked to Tmobile when I got it used (the shop I bought it unlocked it for me), it had already been rooted (it has the Super User app), even though it's running stock rom.
I suspect that some sort of modding had been done by the previous user that changed the Serial Number stored internally as the evidence points to above. Is it important to change it back to match the one on the sticker before I try flashing a custom ROM?

So no one has any thoughts on this? Have any other T999L users experienced what I describe above? Could someone try it quick on theirs and see what happens?
Sent from my SGH-T999L using xda app-developers app

IMEI null, Service Mode Blank, Baseband Unknown

Hey all!
I have a Canadian S4 (SGH-M919V) from WIND Mobile that my friend gave to me, broken.
I have already tried just about everything I can think of, and everything I read online to repair it.
It has a NULL IMEI (as verified by doing *#06#), and when I enter the Service Mode menu via *#0011#, the menu screen comes up but is just black and blank. The Baseband version displays as "Unknown".
I have tried flashing a few different stock roms (via Odin) for that particular phone, and have even tried AOSP roms (via TWRP), to no avail.
I have followed guides for restoring a blank IMEI, however, all the methods I tried required a working Service Mode, which I do not have.
At this point I'm thinking the problem is either hardware, or, it needs to have the IMEI reset via the JTAG, and I don't have the stuff to do that.
Any suggestions would be greatly appreciated!
Thanks in advance!

ess.boyer said:
Hey all!
I have a Canadian S4 (SGH-M919V) from WIND Mobile that my friend gave to me, broken.
I have already tried just about everything I can think of, and everything I read online to repair it.
It has a NULL IMEI (as verified by doing *#06#), and when I enter the Service Mode menu via *#0011#, the menu screen comes up but is just black and blank. The Baseband version displays as "Unknown".
I have tried flashing a few different stock roms (via Odin) for that particular phone, and have even tried AOSP roms (via TWRP), to no avail.
I have followed guides for restoring a blank IMEI, however, all the methods I tried required a working Service Mode, which I do not have.
At this point I'm thinking the problem is either hardware, or, it needs to have the IMEI reset via the JTAG, and I don't have the stuff to do that.
Any suggestions would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Unfortunately you are going to have to get your information on fixing this elsewhere.
Discussion about changing the IMEI (even from 0 to a working value) are forbidden on XDA as making changes to an IMEI is illegal in most places in the world. And people use that info to make it easier to steal phones, so we don't discuss it here.
The only thing that I can advise you on is to restore the EFS backup, which includes that devices original IMEI, if one was made and saved to the device. If not, that's no help at all.
I can say that you're on the right track though as far as fixing it. But you need to find your answers somewhere else.

Skipjacks said:
Unfortunately you are going to have to get your information on fixing this elsewhere.
Discussion about changing the IMEI (even from 0 to a working value) are forbidden on XDA as making changes to an IMEI is illegal in most places in the world. And people use that info to make it easier to steal phones, so we don't discuss it here.
The only thing that I can advise you on is to restore the EFS backup, which includes that devices original IMEI, if one was made and saved to the device. If not, that's no help at all.
I can say that you're on the right track though as far as fixing it. But you need to find your answers somewhere else.
Click to expand...
Click to collapse
Thanks for the reply. I realize the issues surrounding changing the IMEI, so I wasn't looking for help with that necessarily (though I would be open to doing so as the phone does have it's own perfectly legal and valid IMEI which I would be using).
I was hoping that perhaps all that was wrong was a corrupt modem, or something along those lines. I have tried to do an EFS restore, but to no avail. Some guides suggest doing a backup of the presumably corrupt EFS and then restoring it, but that didn't help either.
I am probably just going to have to chalk this up to "unfixable", as it most likely is indeed hardware damage.
So unless anyone else has any ideas...

ess.boyer said:
Thanks for the reply. I realize the issues surrounding changing the IMEI, so I wasn't looking for help with that necessarily (though I would be open to doing so as the phone does have it's own perfectly legal and valid IMEI which I would be using).
I was hoping that perhaps all that was wrong was a corrupt modem, or something along those lines. I have tried to do an EFS restore, but to no avail. Some guides suggest doing a backup of the presumably corrupt EFS and then restoring it, but that didn't help either.
I am probably just going to have to chalk this up to "unfixable", as it most likely is indeed hardware damage.
So unless anyone else has any ideas...
Click to expand...
Click to collapse
If you have the valid IMEI that is confirmed good it is fixable. But it just can't be discussed here. I wouldn't throw the phone out. (If nothing else it's a GREAT tiny tablet for wifi use.)
Google will help you out.

Skipjacks said:
If you have the valid IMEI that is confirmed good it is fixable. But it just can't be discussed here. I wouldn't throw the phone out. (If nothing else it's a GREAT tiny tablet for wifi use.)
Google will help you out.
Click to expand...
Click to collapse
Thanks again. I have an authorized Samsung repair place in town, so I will bring it by there first and see if they can handle it. If not, I'll ask my old buddy Google where to take it from there.

After plugging in a fan IMEI is now 0 (D855) Vodafone 16GB legal

Hello everyone and welcome to my sad and sorry story :crying:
Just over 2 years ago i bought the G3 16GB from Vodafone shop in the UK and i have owned it from new and it's never missed a beat and very happy with it until i bought a £2 fan from ebay (112244885955) and plugged it in and it has killed my phone by the look of it.
I plugged the phone into the bottom and screen flashed on once or twice and then shut off and fan worked fine, i just presumed the fan need alot of power and shut down the phone to power the fan, anyway unplugged the fan and power the phone back up and all seemed fine apart from now cell coverage, so i took out my normal sim (Three) and put in 2 others one was O2 and the other was Asda and O2 failed but Asda worked some of the time, so i was lost at this stage what was going on so done some digging in the phone and found out the IMEI number is coming up as 0 (Zero) and something called the IMEI SV was coming up as 81, and i'm lost on what the SV bit means and also how can i restore my normal IMEI number?
I have tried to do a software update to the phone as per normal but all it say is "Your phone is not registered" yet i still make calls when using the Asda sim, yet when i plug my normal Three sim in it will not even pick up a signal let alone make a call, however when i place that Three sim in my other Moto G 3rd Gen it works fine.
I presume my first step is to get the IMEI back up and running, i still have the sticker on the back of the phone which details the original IMEI number, but i have no idea what softeare is needed or the method involved.
I'm NOT and expert but have taken the Mrs Amazon Fire tablet and put a custom ROM on it so i'm not a total newbie, if anyone could help me i'd be in your debt that is for sure.
All1

When this happened to me, I got lucky and had a backup from flashing a custom ROM; if you don't have one, you'll either have to buy a new motherboard or a new phone unfortunately.

Allonewordinuk said:
Hello everyone and welcome to my sad and sorry story... and also how can i restore my normal IMEI number?
All1
Click to expand...
Click to collapse
No offense to the other poster, but you don't need a new mother board or phone. There are ways - which are not allowed to be discussed on XDA - to re-write your IMEI # if you have to. Google "QPST IMEI rewrite tool" and a lot comes up
In your situation though, I would TOT back to stock first and see what happens from there. Although you're reading a zero IMEI, it doesn't necessarily mean the # is actually erased, it may just be a corrupt partition and your phone can't "find" it or something like that. TOT will wipe and rewrite any corrupted partitions you may have and get you back to factory/out of the box. If you did have a bad partition or some other software glitch that was causing the zero IMEI - TOT will fix it. If you're not familiar with how to TOT back to stock firmware, just look around XDA and you can figure out what files you need and what to do for your specific variant.
But if you TOT back to stock and still have no IMEI: then it is time to read, read, read and(once you feel comfortable) give a manual IMEI rewrite with a QPST tool a try. I have never had to do it myself, so I can offer no help on that.
Good luck :good:

djzic said:
When this happened to me, I got lucky and had a backup from flashing a custom ROM; if you don't have one, you'll either have to buy a new motherboard or a new phone unfortunately.
Click to expand...
Click to collapse
Thanks for the post but i know that's not true as i have read on here about the G2 being done and the G3 will follow, I have not done that yet as a full factory reset is my last option which i will do on Wed or thursday.
startswithPendswithOOH said:
No offense to the other poster, but you don't need a new mother board or phone. There are ways - which are not allowed to be discussed on XDA - to re-write your IMEI # if you have to. Google "QPST IMEI rewrite tool" and a lot comes up
In your situation though, I would TOT back to stock first and see what happens from there. Although you're reading a zero IMEI, it doesn't necessarily mean the # is actually erased, it may just be a corrupt partition and your phone can't "find" it or something like that. TOT will wipe and rewrite any corrupted partitions you may have and get you back to factory/out of the box. If you did have a bad partition or some other software glitch that was causing the zero IMEI - TOT will fix it. If you're not familiar with how to TOT back to stock firmware, just look around XDA and you can figure out what files you need and what to do for your specific variant.
But if you TOT back to stock and still have no IMEI: then it is time to read, read, read and(once you feel comfortable) give a manual IMEI rewrite with a QPST tool a try. I have never had to do it myself, so I can offer no help on that.
Good luck :good:
Click to expand...
Click to collapse
Thanks for your reply startswithPendswithOOH, i do understand were limited on what we can discusss here, i'll head over to google and see what gives, i will come back and post when i have some info, one small point can you tell me what TOT stands for, sorry
All1

Just to update:
Done a full factory reset on the phone and nothing still coming up with Zero IMEI number, used reset mode in the os and from cold boot still nothing so going to have to bite the bullet and go for the nuclear option and try to change the IMEI myself
All1

I think i have a brick
Seems i have to get root to change my IMEI but i can't get root anymore, have tried iroot, this one click option and even tried purple drake which is funny as i was able to use purple drake 2 years ago to gain root now i can't, I'm lost
I don't know if the G3 can do it but when i put a custom ROM on my amazon tablet there was some kind of adb menu where you could sideload stuff, but can't seem to find anything on that, anyone got a gun
Anyone have any suggestions?
All1

Why there is no data about it but industry have solutions of it? imeiCertHack

my road started when my sm-a520f device got bricked. i just bought it and did not worry about it. i just download stock rom and before got EFS and special recoveries. installled every parts and finally got my device back from A to Z..
but
there was a problem with my cercullar data, i checked my imei number it was alive , checked sim card auth, but everything was normal. finally i had to go my old gsm worker friend. he just said there is CertAuth on some devices like old model of qualcom 'qcn' system. and even if you recover all of your device and personal data you get blocked by phone from gsm service, when you restore it same files as same files or other any ''changes''.
when you google about samsung imei cert bypass/patching there is not info/article how the system work, why and which algorithms used for it, where data stored or any classical questions. but there are tools like chimera,Z3box the solutions of them.
i reaaly wonder what is that and how it work, if you give me any info,articles,good things about it im gonna thankful to you guys.
footnote; if you have chimera license i really want to examine that guy.. please contact