Develop Bugs

[Q] Insert Sim to Access Network Service.. IMEI Null

Hey Guys,
I have an AT&T Model SGH-1317 Note 2. For use on other networks, I unlocked the phone using the *#197328640# menu option. However, the phone failed to start the hot spot stating Mobile data was unavailable or Invalid Sim. However, I am able to tether perfectly using the same sim on an another S3 so I was sure its nothing to do with the sim or network operator settings.
I looked up and found XDA website with tons of information. I assumed my phone was locked by AT&T. Hence, I rooted the phone using CF-Auto-Root, backed up complete data using Titanium and using Rom Manager I installed the Crash Aroma 4.1.2 Rom. I wiped the data and cache 3 times as suggested. However, after the boot I am unable to connect to any mobile network. A Click on Mobile Network says "Insert Sim Card to Access Network Services". Dialling for IMEI number prompt a Null.
During Installation I noticed the Crash ROM has overwritten the Radio.. and I am assuming this is were the problem lies. but I leave it you experts.. Request Help!
Sunil.

What carrier are you using the device on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
What carrier are you using the device on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Am currently on Du - A network in Dubai, UAE. I have been reading more forum information and some suggest that this may be related to the EFS folder getting corrupted which may cause the IMEI number to fail. Some suggest that there are software to rebuild this information by using the IMEI number behind the handset..
I also noted that my phone model has also changed to GT-7100 instead of SGH-1317, Wonder if the Crash ROM was apt?
Would you suggest installing a Jedi Rom specifically built for SGH-1317... or is the damage already done?

Back Online
Since I found no replies.. I had no choice but to give it to the Pros.. I handed my phone day to one of the Unlocking experts at a mobile store… He was confident that his technicians would resolve this. But after 2 Days, they have given up.. He suggested the phone would fetch me US$ 10 if someone used it as a demo unit at a mobile shop..
I was sure this was something to do with the Modem, IMEI and the all important NV folder. I was able to find a Stock ROM for the SGH-1317 and I also found a link at XDA about using EFS pro to change the IMEI.
Using Odin software, I flashed the phone with the stock rom. Unfortunately, there was one error when it tried to communicated on com1. Having no choice, I continued. Restarting got the AT&T style boot but it again froze on the Samsung screen. Dreading the communication error, I restarted several times with no results. Finally I realised if would be due to the cache and user data. I reset the phone to factor settings wiping out the user data and Whola.. The phone sprang back up..
Lessons learnt.. Backup your rom and data before playing with custom roms. Read Read Read and don’t flash in the middle of the night..
Since I am back online, I plan to stick to the stock and crappy 4.1.1 with all the AT&T dead weight. Will live without the ability to Tether until my fingers get warmer.. It won’t be long as I am already bit by the Custom Rom Devil..
Don't Give Up Easy..:good::victory:

Flashaholics anonymous will help.
Sent from my SGH-I317 using xda app-developers app

sunilgonsalves said:
Using Odin software, I flashed the phone with the stock rom. Unfortunately, there was one error when it tried to communicated on com1. Having no choice, I continued. Restarting got the AT&T style boot but it again froze on the Samsung screen. Dreading the communication error, I restarted several times with no results. Finally I realised if would be due to the cache and user data. I reset the phone to factor settings wiping out the user data and Whola.. The phone sprang back up..
Click to expand...
Click to collapse
Please I am having the very exact same issue and can't seem to have it fixed
Using CMW I also flashed it back to stock rom, didnt have any problem or errors doing it but im still getting No SIM Inserted. I have deleted cache and user data several times... Tried flashing CM10 and CrashRom see if they made a difference and still No Sim Inserted... tried 3 different kernels and still same issue

I have the exact same problem since yesterday. I've tried everything and anything to no avail. I'm very close to returning the phone.
I would really appreciate any input.

Same issue
I flashed crash rom 4.5, over the stock kernel and it gave me that same message. I've tried everything I could think of, which included everything in this thread to no avail... any further advice would be greatly appreciated.

imei null baseband unknown, {insert sim to access network error} PLEASEEEE HELPPP ME
i rooted using auto root and installed xposed framework and snapshare and snapprefs :crying:
after that i tried puttin off the airplaine mode and it didnt happen
then the error started to show insert sim to access network god i need help.

sukhraj kohli n7100 said:
i rooted using auto root and installed xposed framework and snapshare and snapprefs :crying:
after that i tried puttin off the airplaine mode and it didnt happen
then the error started to show insert sim to access network god i need help.
Click to expand...
Click to collapse
Your username suggests that you have the N7100 device ??
If so. ..you are in the wrong place for support. ..As this is the SGH-I317 section.
If you are showing IMEI NULL with no baseband you may have to restore your backup image to correct the problem. .
If no backup image exists. ..you will need to flash a factory N7100 image from your section.
Look for the return to stock thread for your specific device and that should fix you up...
The CF AUTO ROOT files are device specific. ..so I hope you haven't damaged the partitions.
Good luck. ..g
Edit:
This will help. ..and will place you in the right section. ..
Just go to page 1...good
http://forum.xda-developers.com/showthread.php?t=2230250

restoring efs with nvtools/qpst

hi guys, i flashed the lte modem on my phone and it seems that its wiped out my efs folders, ive been trying to restore my efs folder with nvtools and qpst, neither seems to work since somehow dm mode is not responding to them
any solns? ty in advance for any help
a couple of things:
ive already odin'd back to stock, no luck on restoring efs(perhaps im doing something wrong?) i dialed *#7284# and put it into the RNDIS+DM+MODEM mode, nvtools says phone failed to answer while QPST says that comm7(the samsung serial port) is not a phone
its pretty had to do this since the phone is rebooting itself every other minute

Questions and help issues go in Q&A
Thread moved
Thanks
FNM

Been there, sucks. For me to get out of the constant restarts I had to flash the lte modem again. Flash stock (odin) flashed cwm (odin), put the modem on my external sd card and flashed that.At least that way I could work on it a little. And below is basically what I did to finally get it to work. Hard to say all my steps as I was trying everything.
Well I dont really know how I got mine back to life, tried all the standard stuff from the threads,got my imei back but had no network,network type,service nothing helped. last resort I said whatever ill try anything now. Came across this
http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
whatever it did it restored everything (cold see carrier,network,etc)but corrupted imei, next i followed this guide
http://forum.xda-developers.com/showthread.php?t=1804117
If you need this is a complete no imei nv backup I used before flashing my imei with the generator
http://db.tt/4hunZ7qy
used the imei generator, then the writer (link on post does not work for the imei generator,so found it here
http://d-h.st/vVV
Wrote my imei back and presto, back in action. Fully functional again, including 4G
Like I said this was a last resort, but worked

AznDud333 said:
hi guys, i flashed the lte modem on my phone and it seems that its wiped out my efs folders, ive been trying to restore my efs folder with nvtools and qpst, neither seems to work since somehow dm mode is not responding to them
any solns? ty in advance for any help
a couple of things:
ive already odin'd back to stock, no luck on restoring efs(perhaps im doing something wrong?) i dialed *#7284# and put it into the RNDIS+DM+MODEM mode, nvtools says phone failed to answer while QPST says that comm7(the samsung serial port) is not a phone
its pretty had to do this since the phone is rebooting itself every other minute
Click to expand...
Click to collapse
Let me guess. You've git a Canadian phone
Sent from my Nexus 7 using Tapatalk 2

+1

got it fixed on friday, was so tired that i went to sleep
basically i followed someone's post on the forum(forgot name) and flashed the tmo modem, since the mct one always gave me the bootloop, then i enabled DM mode and finally got nv tools/qpst to recognize my phone, it appears that the issue was that the drivers does not recognize the new modems..
anyway, once i was done restoring nv, i flashed the tmo lte modem and paranoid android
now i have my imei back and i can use lte
although my bluetooth address still says unknown..not sure if normal

My bluetooth also says unavailable, I would think if you are not hooked up to bluetooth then it should say unavailable. Im to scared to flash the tmo lte modem again...

[Q] Band Handover/voice network issues

So I have been waiting patiently for the 4.3 update to roll out to me OTA with hopes that it would fix my issues but my phone has been saying download interrupted and so I have gone back to completely stock and triangle away to get my device status back to normal but it still wont let me download. When looking around for other possible causes I saw that my build number is JRO03L.I747UCDLK3 which comes up as a build number for a nexus 7, the correct build number for my att should be JRO03C. I have no idea how it got that way but I am wondering if the person who bricked it might have put the wrong version of the bootloader or some other part of the firmware on and it somehow didn't brick but is detecting a conflict and not letting me OTA. Or that is what is causing my cell network issues as well. Wanting input from a a few devs as I am not 100% sure what the first part of the build number represents.
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for tag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.

Bump
Bump!...not looking good.

madnesshero86 said:
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for Jtag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Click to expand...
Click to collapse
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail

Tried
View attachment 2362929
winosxbuntu said:
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Click to expand...
Click to collapse
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?

madnesshero86 said:
View attachment 2362929
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
Click to expand...
Click to collapse
I think I can help, I just need to pull up some files and I might get you the software or program I used to back -up and restore my EFS folder/files
Even fix it, so plz hang in there........will report back later on

Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
this is the software/programme i used to back-up, recover or even fix my EFS files (if they are corrupt and can be used) NV items reader writer
type it on google and pretty sure you will find something , try different links and again am sure you will find a download
have you tried flashing the new 4.3 stock firmware and modem follow this link for everything http://forum.xda-developers.com/showthread.php?t=2498233 or you can wait for AT&T to release the official 4.3 firmware and that will be 100% satified to be stable and will fix all your EFS/IMEI problems FOR GOOD :laugh:
i have the NV items reader writer software that can fix your problems but i dont know how i can share it with you without breaking any rules
ULTIMATE/final solution send it to MOBILETECHVIDEOS and will fix it like its nothing, take it to samsung and have to play some ball, or BUY A NEW PHONE
tried kernels (idont think it will make any difference) but its good to check

I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

madnesshero86 said:
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
NV items reader writer
type exactly as it is on google or here on XDA

New Info
See new info in OP Please, and before anyone says anything I have spent half the day searching with various keywords trying to find a fix so be kind if it seems obvious to you, I couldn't find it and I did try.

Bump

[Q] Mobile data suddenly dropped

I'm running CM-10.1.3 (stable) on my phone (T999) with the UVMD5 modem and last night I lost all signal for about 30mins. I rebooted a few times and toggled air plane mode on and off without any success. Eventually, I got signal again but no data. I can send and receive calls and SMS but I have no data connection (can't browse, no email notifications, etc.). I have tried all the options under the Network Mode settings without any success. Occasionally, I'll see the "E" sign for Edge/2G but there is no data available even then. I also tried updating the modem to UEMJ4 and UEMJC but observed no changes. WiFi works just fine. Could this be a hardware issue? Is the antenna somehow damaged? Is there anything else I could try?

Try another Kernel. If that does not help, Odin flash to Stock. If that too doesn't work then suspect tower issue.
Hardware is a possibility. But lets not get ahead of ourselves

Thanks, I'll give that a shot and report what I find. I doubt that it's tower related since I'm having the same issue at home and at work and my roommate, who has an original Galaxy and is also on Tmobile, is not having any problems.

I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?

EvilBoz said:
I flashed stock JB 4.1.2 (UVDMD5) using Odin since I had it laying around and I'm still seeing the same issue. What else can I try?
Click to expand...
Click to collapse
Check your APNs. Those are under Settings > Advanced > Network. Its called Access Point Names. It should be set to epc.t-mobile.com. See this thread for details.
Try UVDLJC or the prior version to MD5. If that too does not help then take to T-mo for antenna Repair.

Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).

DocHoliday77 said:
Check your IMEI number. If it is zeroed out PM me. Otherwise just let us know here, (but don't actually post it).
Click to expand...
Click to collapse
The IMEI is 0. I never backed up the EFS folder but I was able to get the number from tmobile.

I have been having the same issue since June 2013 after doing to 4.1.2 OTA update from T-Mobile, at the time I didn't realize the IMEI was listed as unknown. So for months I have not gotten a cellular data connection better than Edge. Also after that update trying to check for a software update on the phone resulted in an error, and Kies told me my firmware was not supported for upgrade. Looking in some support forums and talking to T-Mobile got me nowhere, so I have just been dealing with it.
Wanting to upgrade I recently used Odin to load the official T-Mobile 4.3 ROM on the phone, actually hoping that would fix my issue (still in the dark about IMEI) which it did not.
I had never backed up the EFS folder, since as a standard user I had no idea what it was and while performing an update from my provider I didn't realize anything would need to be backed up outside of Kies. Now that my warranty is expired and having to take matters into my own hands I am on a quest to find a fix, however I don't want to "brick" my phone in the process, at this point I know enough to be dangerous.
Currently;
Android 4.3 Official T-Mobile ROM
BASEBAND is good T999UVUEMJC
Kernel 3.0.31-1962493
IMEI is Unknown
Looking at some other posts here at xda-developers I tried to follow some instructions on repairing or restoring IMEI using NV reader/writer, however I cannot get NV reader/writer to connect to my phone.
I have noticed in 4.3 when using *#7284# in the dialer the QualComm settings are no longer present, only MODEM and PDA are available.
I have poked around in Service Mode *#197328640# and found a setting that I thought might help, but I have a feeling it is the same thing as 8#7284#
[1] UTMS > [6] COMMON > [4] DIAG CONFIG > [1] USB or [2] UART
So at this point I don't know how to proceed, again I am not thrilled about loading a custom ROM, or really any ROM for fear of making the issue worse or bricking the phone. I have read a lot of posts about no longer being able to make calls due to IMEI issues. Everything works right now except cellular Data.

[Q] Issue with flashing phone. Please help.

So I just got a used s3 from flebay (bad esn). Sprint Galaxy s3.
I dial ##3424# and I can get the phone to show up with a com port, connect with CDMA, but when I click read, it says ":: failed ::" next to ESN and number. So ok I thought maybe I got to send the SPC to it first, and since the old 16 digit pw does not work for 4.3 anymore, I flash it back to 4.1.1, connect via cdma to com port, but it says fail to send to phone.
- I've tried 4.1.1, 4.1.2, 4.3, and a couple diff modem. All give same result.
- I also tried to use QPST. In QPST configuration, the target port shows enabled, com19, no phone, usb. It does not want to recognize the phone as well.
Any ideas what it could be guys? I'm suspecting this phone cannot be flashed or even used.