Lost and restored IMEI, still only on EDGE - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hey everyone, so somehow, by flashing a kernel, I lost my IMEI/EFS folder. Of course, I didn't have it backed up to begin with. I restored my IMEI using QPST, but I still only manage to connect to EDGE. I restored an old stock rooted nandroid and tried again, to no avail.
In settings, I am still missing my ERI version, and, as I said before, I can connect to EDGE, make phone calls, receive texts, etc. but no data, so something is definitely missing.
Could somebody give me the definitive method to repair this problem? Thanks!

Ok....tried to Odin back to Stock rooted (Root69) and I'm hung at the Samsung boot screen. Can anyone lend a hand?
EDIT: Fixed with factory reset. Still stuck on EDGE...

Can you clear the imei number with this tool?
Sent from my SAMSUNG-SGH-I337 using xda premium

I would suggest warranty replacement as the best option. I ran into the same issue, and that is what I had to do. Apparently, the NV items carry a lot of configuration information. After I did the warranty replacement, I did a difference between the NV backup from my old corrupted GSIII and the new one before I returned it. There were some substantial differences, much more than just the missing IMEI!

Related

No service after reflashing to stock [Solved]

Had my nexus rooted since day 1 and never had any issues. Lately i've been trying to use Barclay's Pingit app which doesn't work on rooted devices. So i reflashed to stock through the galaxy nexus toolkit. I did get service on the stock rom, but i've since tried a nandroid restore of my CM10 and it appears to have screwed something up. First off, the restore completed in 4 seconds, so it obviously didn't work. I'm using TWRP if that makes any difference.
So i tried a wipe and flash other roms, but still no service. Even after going back to stock, still no service. I'm assuming the botched nandroid restore has possibly damaged my radio somehow? I did try to flash another radio, and it flashes ok, but still no service.
APN settings are fine. All i get though when i try to connect to a network is "Can't connect to this network at the moment, please try again later".
I'm on 3 UK. Tried connecting to other networks, but still the same issue
Just tried flashing a new radio through fastboot, flashes fine and shows up in baseband version, but still no service...
Have you tried getril app? If your radio interface layer doesn't match it can fix it.
Sent from my Galaxy Nexus using Tapatalk 2
eqjunkie829 said:
Have you tried getril app? If your radio interface layer doesn't match it can fix it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah i tried it earlier, no luck.
Just tried again to make sure, still nothing
I have had some bad flashes with twrp. If I were you I would try cwm and then flash a new ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Op, do you still have your imei? Try another simcard have you?
Sent from my i9250
Yeah i've tried several new rom flashes through CWM.
@bk201doesntexist - Yeah the phone has an IMEI in the status menu. I'm wondering if it's blocked since my provider accidentally cancelled my contract a few months ago, and i didn't say a word
Scrap that actually, apparently Three UK can't block IMEI's for some reason...
Funnily enough, i tried a sim card from another carrier and not only did it not connect to any network, but now when i go to search networks it just says "Error while searching for networks".
Edit - Called my network provider, they said my IMEI was wrong. At the minute it starts with 0049, which it shouldn't apparently. I dunno how this got changed in the first place.
Ok, so i've looked into the imei 0049 issue and it's starting to make sense. I looked in the /factory folder and it's empty, well apart from lost+found but it's empty. I assume the only option is to send it off for repairs? I do still have a nandroid backup on my computer and it has efs.ext4.win on there. Gonna give that a shot.
Edit 2 - Ok so I updated TWRP as my version was 2.2. Attempted the nandroid restore again and success! Got my voice and data back!
Thanks for the suggestions, its been a stressful day and hope this can help somebody else in a similar position
Yeah i forgot mentioning the fake imei thing. I was thinking about the /factory partition being null, thats why i spoke of imei.
Please edit the thread title to include tag [SOLVED]. Thanks.
Sent from my i9250

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] Initially lost signal, ended up with unrecoverable boot loop

Hey guys,
This thread stems from this post: http://forum.xda-developers.com/showpost.php?p=39594591&postcount=18
I'm gonna spare you the trouble of having to read that thread by summing it up for you:
- T-889V, running Jedi x12, had to pop out the sim to try it on another phone.
- Once popped back in, my phone lost all carrier connectivity. At first the signal icon looked like a "forbidden" sign. Then, after a little while, I get service bars, but no connectivity indicator.
- IMEI used to show up, but I still didn't get connected. Used my sim in a different phone as well as a different sim in my phone to rule those 2 out. As expected a different sim in mine didn't work.
- I go back to stock using mobile odin. My IMEI is now unknown, obviously I can't connect to anything and on top of that the phone reboots every 1 minute or so.
- I flashed some other rom I had lying around. My IMEI is back, bootlooping stopped, however I was still unable to get any service.
- Try a different version of stock with mobile odin the and I'm boot looping. This time I can't get into recovery at all.
- Finally I try desktop odin with a couple of different stock images, and I'm still bootlooping (reboots right after the Samsung logo). Recovery works fine.
I would send it back but I'm worried about my flash counter being 1, and my system status being "custom". I am completely stumped. Absolutely any ideas are appreciated.
Sometimes after flashing stock you have to wipe data factory reset to get it to boot. Just a thought.
Thanks for the idea. I have tried that
Have you tried flashing back whatever modem came with that Jedi ROM, along with either the stock T889V or an N7105 ROM?
Still getting bootloops?
In other words, get to a no service and no bootloop situation, and look into restoring NV items with the appropriate Qualcomm compatible programs.
Sent from my SGH-T889V using xda app-developers app
But do you think it's possible to escape the constant bootloop? Right now I'm a little worried about flashing anything that will increase the counter, as I don't know if I'll get to run triangleaway ever again...
By qualcomm compatible programs you mean those 2 little tools that let you extract/write an IMEI as well as generate it as a text file?
The solution should be the same as the one I used for fixing my phone: using NV reader writer to rewrite correct stock settings along with your IMEI.
Warranty centres don't care about your exact counter, only if it's 0 or not, so flash away until you fix this. My counter was well over 30 when I finally did.
Sent from my SGH-T889V using xda app-developers app

[Q] I messed up with Titanium Backup and now it says 4g, but data doesn't work

So I had to get a replacement Note 2 from T-mobile because my first one had messed up sensors or something. When I got the new one I wanted to backup and restore all my apps from the original.I used Odin to flash CF auto root and do a app and system backup. Then I rooted to the new one the same way and did a restore. I apparently didn't read enough about Titanium backup and restored everything including the system stuff.
Now my data doesn't work most of the time. Specifically when my phone says 4g, no matter how many bars, nothing has network access. I can make and receive calls and text messages although calls have been very spotty with reception. However if I have 4g LTE signal then everything works great. Can anyone suggest a fix? I flashed the stock rom again and reset APN settings to default, nothing is different. Side note, I was able to reset flash, unroot and return the old phone to T-mobile. Any help is greatly appreciated.
Update:
I noticed that I can get text messages when mobile data is turned off. Not sure if that means anything.
Do factory reset and wipe data. May be solve you problem.
May sure you have flashed stock rom with same phone model.
Sent from my GT-N7100 using Tapatalk 4
MBariya said:
Do factory reset and wipe data. May be solve you problem.
May sure you have flashed stock rom with same phone model.
Sent from my GT-N7100 using Tapatalk 4
Click to expand...
Click to collapse
I did that and it is still the same. Someone has to have seen this issue before. I can't be the only one who has messed up with titanium backup.

[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

Categories

Resources