[Q] SGS3 - Error: “Not Registered on Network” - Galaxy S III Q&A, Help & Troubleshooting

Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur

Megneto said:
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Click to expand...
Click to collapse
Check your IMEI number.
Has it changed?

eggman89 said:
Check your IMEI number.
Has it changed?
Click to expand...
Click to collapse
No it hasn't changed.

The problem was the original "soft unlock"
Megneto said:
...
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
...
Click to expand...
Click to collapse
The problem was the original "soft unlock" - some of those (I believe even some early that were made by NSPro) are rather poor and are based on flashing a special modem binary. You will be able to fix it if you search around for the fix posted by Ariza (even if I believe something happened to the original post).

I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.

Hmm ...
Megneto said:
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Click to expand...
Click to collapse
The thread was this:
http://forum.xda-developers.com/showthread.php?t=1918601
(in a post towards end I have some of the stuff from the forum where you had to register in order to get the files, and you might still recover some of those links - apparently those are patched versions of the corresponding stock modems which no longer check some of the information from nv_data.bin; you will need to add that modem after each major ROM change).
If you only plan to use 4.1.1 and not upgrade then NsPro should be OK, otherwise you either need a "subscription" to the services of that guy

Thank you for the help. I will go through that thread soon.
I've have also looked at this thread http://forum.xda-developers.com/showthread.php?t=1705650 by UpInTheAir. I have installed android SDK for Winx64 and successfully extracted modem.bin (as a test). I think I'll get the phone back to that guy, so he can patch the modem with NSPro again, once that is done, I'll extract the modem, repackage it so I can install it with CWM and test whether that can eventually help me in experimenting with other ROMs.
I will keep you posted on my progress.
Again thank you for your valued help.
Kind regards.
Babur

Having tried the method mentioned in my previous post, I finally gave up and took the phone for repair.
What transpired from thereon is interesting and confusing. As according to Mr. Repair 'serial number and IMEI' were repaired, nothing more. In fact I extracted the modem and compared it with the one I have, they are exactly same no patch applied.
However, both IMEI and serial number were showing correctly prior to the repair, and even after repair they are same (I double checked those with the original invoice/phone box etc.). So I am not sure how they were damaged when they were showing correctly.

Update:
I've sold the unit question, as I felt not to take any more risks with it, and bought an factory unlocked SGS3. Hopefully I will not face any problems with playing around with custom ROMs from hereon in.
Thank you and kind regards to all.
Babur

Related

[Q] Long Story Anyone to make it short???

I bought GT-I9000M, Froyo, 4 days ago, brand new unlocked from store. I had a problem getting GPS to work. Searching for a fix on the web, I got inundated with all kind of info,. Not only on GPS fixes, but on comparing, updating, rooting, flashing, unlocking, APP's and other issues with my Galaxy s. So, after reading quite a bit, I decided to update or flash my phone to the latest (assuming that will solve GPS problem and all other issues). As a newbie to Android software which I was about to temper with, I selected androidadvices.com to guide me. I had read very carefully and I followed instructions meticulously to flash 2.3.4 XXJVP. but it did not work. then the phone did not start and I got the little mobile and pc with triangle in between sign. I still could get to download mode. I tried to repeat the process many times, but got same results. it halted after it started to load bin file. I consulted the so called expert at androidadvices if the I9000M differs from I9000 and if could that be the reason for what happened. HE did replied promptly "YES" and advised to take it to service center. I searched a little more on the web with other language and I found a tip about omitting pit file (using Odin). Tip worked fine and flashed to XXJVP. Please do not congratulate me yet. Now the phone starts showing I9000. I did not only lose M, but it is network locked. Getting back to the so called expert to ask him if it's a good idea to upgrade or rooting (as he described in his instructions) to 2.3.4 XXJVQ to solve the problem. Also I meant to publish what happened on his site to save other newbies from believing what he writes. And his answer was "YES" again. Now I know the trick how to use Odin by omitting pit file, I did flashed to XXJVQ. Unfortunately, the galaxy s still locked. By that time, with no search, I already know that XDA forum from their tens of Youtube videos and links on every galaxy s site for their unlocking techniques. I'm sorry I'm trying to make this story short, but I can't for I won't feel well if someone trying to help asks me "did you do that?". However I tried everything I could, using Generate Unlock and SIM less methods, on XDA to unlock, yet no luck. I logged on a site I do not recall the address and up loaded the nv_data.bin.orig and entered 8 digits twice for unlock and unfreeze. I got back the message "the file is smaller than it should". the file was 4MB. I paid for unlock code from unlock-freedom.com 2 days ago, which promised to send code within 12-24Hrs. Yes the store I bought it from is finally open today. I went there and he plugged it to laptop hooked to USB unlocking device. He tried many time and ending with the message unlocking successful on the unlocking app. Yes you got it, the Galaxy s I9000 previously I9000M still locked. On the bright side.I have Gingerbread 2.3.4 XXJPQ installed and if I dismiss unlocking screen I can log in my email. Any help from a real Expert!!!!! will the unlock code, if I receive it, solve the problem. will I ever have my new phone working again????
theothman said:
I bought GT-I9000M, Froyo, 4 days ago, brand new unlocked from store. I had a problem getting GPS to work. Searching for a fix on the web, I got inundated with all kind of info,. Not only on GPS fixes, but on comparing, updating, rooting, flashing, unlocking, APP's and other issues with my Galaxy s. So, after reading quite a bit, I decided to update or flash my phone to the latest (assuming that will solve GPS problem and all other issues). As a newbie to Android software which I was about to temper with, I selected androidadvices.com to guide me. I had read very carefully and I followed instructions meticulously to flash 2.3.4 XXJVP. but it did not work. then the phone did not start and I got the little mobile and pc with triangle in between sign. I still could get to download mode. I tried to repeat the process many times, but got same results. it halted after it started to load bin file. I consulted the so called expert at androidadvices if the I9000M differs from I9000 and if could that be the reason for what happened. HE did replied promptly "YES" and advised to take it to service center. I searched a little more on the web with other language and I found a tip about omitting pit file (using Odin). Tip worked fine and flashed to XXJVP. Please do not congratulate me yet. Now the phone starts showing I9000. I did not only lose M, but it is network locked. Getting back to the so called expert to ask him if it's a good idea to upgrade or rooting (as he described in his instructions) to 2.3.4 XXJVQ to solve the problem. Also I meant to publish what happened on his site to save other newbies from believing what he writes. And his answer was "YES" again. Now I know the trick how to use Odin by omitting pit file, I did flashed to XXJVQ. Unfortunately, the galaxy s still locked. By that time, with no search, I already know that XDA forum from their tens of Youtube videos and links on every galaxy s site for their unlocking techniques. I'm sorry I'm trying to make this story short, but I can't for I won't feel well if someone trying to help asks me "did you do that?". However I tried everything I could, using Generate Unlock and SIM less methods, on XDA to unlock, yet no luck. I logged on a site I do not recall the address and up loaded the nv_data.bin.orig and entered 8 digits twice for unlock and unfreeze. I got back the message "the file is smaller than it should". the file was 4MB. I paid for unlock code from unlock-freedom.com 2 days ago, which promised to send code within 12-24Hrs. Yes the store I bought it from is finally open today. I went there and he plugged it to laptop hooked to USB unlocking device. He tried many time and ending with the message unlocking successful on the unlocking app. Yes you got it, the Galaxy s I9000 previously I9000M still locked. On the bright side.I have Gingerbread 2.3.4 XXJPQ installed and if I dismiss unlocking screen I can log in my email. Any help from a real Expert!!!!! will the unlock code, if I receive it, solve the problem. will I ever have my new phone working again????
Click to expand...
Click to collapse
Ok that was pretty long and slightly confusing. But I think you lost your unlock yes? Have you tried Helroz's Galaxy S Unlock app from the market?
Thank you for replying, I'll be more than delighted to clear your confusion. The answer I coulld not try Helroz's for it's like some other methods require to gain access to efs folder. I don't have folder named efs. and the only file I found browsing internal sdcard whether through PC or Myfiles icon on mobile was nv_data.bin.org with another file called devicefriendlyname.txt with rest of regular folders like sovx and android. all under: /mnt/sdcard as it shows in the phone.
theothman said:
Thank you for replying, I'll be more than delighted to clear your confusion. The answer I coulld not try Helroz's for it's like some other methods require to gain access to efs folder. I don't have folder named efs. and the only file I found browsing internal sdcard whether through PC or Myfiles icon on mobile was nv_data.bin.org with another file called devicefriendlyname.txt with rest of regular folders like sovx and android. all under: /mnt/sdcard as it shows in the phone.
Click to expand...
Click to collapse
need root explorer to see efs files
could you please through a download link to root explorer
.....................
RE: Helroz
Ok I feel like we have real experts here. I installed Helroz smoothly and run it but I got the following message:
It's possible you have problem with busybox, please install it or fix it.
So, what's next great guy's? I guess I need a root explorer and busybox !!!
theothman said:
Ok I feel like we have real experts here. I installed Helroz smoothly and run it but I got the following message:
It's possible you have problem with busybox, please install it or fix it.
So, what's next great guy's? I guess I need a root explorer and busybox !!!
Click to expand...
Click to collapse
dont know anything about unlocking phones lol
can get busybox from market for free though i think, try that
Dear Kyle51
Thank you
I download the .apk file but I can't open it. what to do next?
theothman said:
Dear Kyle51
Thank you
I download the .apk file but I can't open it. what to do next?
Click to expand...
Click to collapse
should be able to go on to the app and pick what version to install, 1.17 or 1.18 i think show up
i tried changing TW launcher through sgs tools on simply honey but it said i didnt have busybox installed so i installed it and picked the newer version but still said i didnt have it, so dont know if i did something wrong
kyle51 said:
should be able to go on to the app and pick what version to install, 1.17 or 1.18 i think show up
i tried changing TW launcher through sgs tools on simply honey but it said i didnt have busybox installed so i installed it and picked the newer version but still said i didnt have it, so dont know if i did something wrong
Click to expand...
Click to collapse
No Way I think you chould replace your TW launcher with your TV guide and look for the cable guy movie
I have a problem here installed busybox and ran it to get the following;
Root not found!
the su binary was not found on your phone. this application will not work since your phone is not rooted
Then I press OK to get:
Status: looking for Busybox....
Your phone is not rooted
you used root explorer ?? so you must be rooted
i tried restoring app with titanium and it said i wasnt rooted so i rebooted and then it worked
try that and if not then try the super one click root method
Ready to donate and hit many thanks
Yes it's me again. still trying.
can anyone write happy ending to this endless story. but please consider I'm A NOOB not anything less than that. meaning I'm not familiar with most of terms and expressions you are using here.
However, if you are following this annoying story from beginning, I'm facing a dead end again, but i know there is great hope considering the following:
I have decided to start clean so I followed instruction in this thread (NOOB GUIDE: HOW TO ROOT/ODIN/FLASH/RECOVER ** 04/28/11 W/ Videos **).
I did every thing as it should be I believe, but I'm stock half way. Phone now flashed to stock T959UJFD (I'm glad now I can say that since I know what stock means) but shuts down as soon as I plug USB cable???????
I have update.zip file on internal SD not the 2GB external.
Also have the Rom of my choice zip file (Trigger 3.2) on internal SD.
Oh I also have SuperOneClick. And Odin 1.7
tried too many things like flashing without reparation or without reboot. tried also to flash some 2.3 Rom versions. and they do work well as I saw. Only one main problem I can't root the phone (meaning I can't see efs folder to unlock phone) which what I have to do since I locked it while trying to fix GPS, in case you are not following from the start.
I also have a very light nice functional stable Arabic Persian Rom. as a matter of fact, I do not know how, but with this version of Rom the phone was able to receive calls and sms. half locked
Thank you Kyle for trying and I believe I have to hit the thanks button for you
I'd really appreciate any help to end this rather entertaining story.
dont know why it goes off when usb gets plugged in :s
you cant root rooting means you can flash custom roms which you've done ?? so you must be rooted ??
and you dont need odin or super one click on your sd (if thats what you meant)
but trying to fix gps locked it as in only open to 1 network/carrier ?? (whatever it's called where you are)
kyle51 said:
dont know why it goes off when usb gets plugged in :s
you cant root rooting means you can flash custom roms which you've done ?? so you must be rooted ??
and you dont need odin or super one click on your sd (if thats what you meant)
but trying to fix gps locked it as in only open to 1 network/carrier ?? (whatever it's called where you are)
Click to expand...
Click to collapse
Come on man.... You are confusing me more than I do !!!!! I hit your thanks button and I did PM you. thanks for trying to help
I think we are all cornfused..... You might have a little more luck finding help in the I9000 forums, try posting your issue there. Good luck!

[Q} Reverting to stock rom/upgraded rom (modem worry)

Hi all
Recently I upgraded from Samsungs stock 4.1.2 firmware to CyanogenMod 10.2 Stable (based on 4.3.1) using their installer program. Since upgrading the Wifi has been unusable and I have not managed to get the problem resolved through their forums so I have decided to go back to the stock rom.
Now that Samsung have re-released 4.3 for the S3 in the UK (after the one from last month which was pulled for problems) I would like to use this one as it fixes a bluetooth streaming issue I have endured for a long time. I can't find this new firmware for download anywhere so wondered if it is feasible to download say the stock rom 4.1.2 and then upgrade somehow? I have a red line on the bootup screen which shows it has been modified (which triangle away won't remove due to custom rom/bootloader or something like that) so I believe this means I will be blocked from then upgrading from 4.3 OTA but able to do so with Kies?
Being a novice at this I am obviously worried about breaking my phone and I am not sure if having i9300XXEMG4 as a baseband version is an issue among other things after reading the forums. As much as I have read about EFS and the downgrading modem problems, none of it is making sense to me at the moment, even after reading all the documents. Brain freeze maybe!
The cyanogenMod also changed recovery and unlocked the bootloader going by what I have read, is this an issue I need to worry about?
Any advice that can take away some worries and get me on the right path would be muchly appreciated!
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thank you for your post. I did follow a link in the !!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!! sticky thread which took me to the Q&A forum where I thought I was posting. It is possible a confusion happened during the sign up process.
After reading those threads, two of which I had already read before posting, I have more understanding than I did before. Somehow I missed about the S3 not having a locked bootlader to begin with. I have backup up the EFS using Ktool but also understand it would have been more useful to do before flashing CM 10.2 as I now only have a EFS v2 backup rather than a version 1. What I am unsure of is what is my best action to take at the moment, going by the information I have. I can it is best not to go downgrade to earlier firmwares unless I wanted an added headache of the modem workarounds but do not see the best way to get back to a stock 4.3 firmware still.
I am on Three mobile (H3G) in the UK but don't think my phone is actually locked to them and don't know if that means the BTU is the option I should be choosing. Even so, when I check the firmwares on http://www.sammobile.com/firmwares/2/ I can only see a firmware added last month which I have to assume is the bad 4.3 update that hit the UK and was pulled after the problems it caused. If it was my best option for flashing, even with the problems it caused, how would I then go about getting the extra update that Samsung pushed out to fix the problem?
I saw the Korean factory flash in one of the threads too, not sure if this is too extreme (and potentially more dangerous) than the other options which may be available to me.
Obviously I would like to do this right the first time, rather than stumble backwards fixing all the mistakes I make at the time. So sorry if I am asking what may be simple to some. My knowledge of phones sucks and I wish I hadn't been tempted by the easy looking Cyanogenmod installer now!
Noticed after a few cache and devlik cleans and reboots that the wifi started working on the CM 10.2 mod but only for the main browser and hit and miss with google play. Every over app didn't work on wifi though, but did on cell. I googled all over to see many with similar problems, which suggested manually setting the time and date and static ip settings, clean davlik and updating play apps after deleting their cache.
None of them worked. So to potentially getting away from flashing, does anyone know any other ideas to resolve this? Wifi connects, stock google browser works, Play works flakey. Other installed browsers wont load any pages or connect to the net, such as speed testing app. The only unusual app that also works in a twitter app. Installed an app to see if there was a hidden proxy setting, but it found nothing, Really strange. All the apps work on cell.
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
boomboomer said:
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
Click to expand...
Click to collapse
Appreciate you giving me a direction to go. It seems the problem I had finding firmwares the last few days were due to Hotfile going offline and Sammobile rebuilding their index of firmwares. I found through the forums 4.3 BTU I9300XXUGMJ9_I9300OXAGMJ9_BTU.zip which contained a 1.5GB file called I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_HOME.tar.md5 which I think is the correct one which I will try and flash later using the guides. It's not the new fixed 4.3, it's the older broken one but I guess in time I can apply the fix that Samsung are pushing out. This was part of my original question and now i have seen from other posts in the last few days that there is no full copy of the 4.3 anywhere.
The timing of me doing this appears to have been bad for a few of the above reasons, making working it out more difficult to work out for someone who has not done this before.
I can see from your signature and also your post that you think questions such as mine are easily answered in the various threads and through search. Personally I did try all those options first but either my lack of understanding or the overwhelming amount of information meant I was unsure as to what I should actually be doing, let alone which guide to follow. Even googling for BTU or searching xda to try and find what it means was fruitless so trying to put the pieces together is not easy if you have no experience with phones. I have programmed a Pi to do many tasks, built mainframe>SAS gateways and various technical challenges but I still struggle with all the phone flashing info
Many thanks again. Even a few words have been helpful
If you flash the kernel from the Chinese ZCUBMK it will fix all the broken parts of the current uk rom, until the latest ota emerges on xda.
I don't mind helping people who have made a genuine attempt to help themselves, my signature is aimed at the those who flash anything they find then demand someone give them an instant fix.
Your only mistake seems to have been the depth of research before you started, which could have been fatal to your phone -many first time flashes end up with a new motherboard required.
Sent from my GT-I9300 using Tapatalk
If the ota doesn't work in the next few day's I will try that kernel, thanks for that info!
I managed to flash the older official 4.3 firmware just now, so progress has been made A quick check shows me that the power on/lock screen lag problem is present so I assume the other issues will be there too. The red line showing the flash counter has gone and I got no modified phone error when attempting an ota update, as well as device status saying official, so I assume I should be able to upgrade that way when they allow more upgrades on the rollout server.
In case anyone else needs to do the same, this is what I did:
1) Downloaded https://mega.co.nz/#!DVxVgZZb!LIxKGA2Q_KbBH9APo_slOCdZNGJgfn1O6fxOF4C OkHA which I found via a thread titled [Official Firmwares] I9300XXUGMJ9 (Android 4.3) - Ireland (VDI) [04-11-13]
2) Followed the flashing instructions on this page
3) After flashing I got stuck at the Samsung boot screen with the blue light on, even after reseting a few times. So I powered off, held down the home button, volume up and then the power button which took me to the recovery screen where I chose the factory default option. All worked fine after that.
Thanks once again for your help with this boomboomer. A bit of direction was enough to give me the confidence to try it. It's nice to be back to a familiar interface (although it has changed from the 4.1.2 I had before) but the initial setup reminded me of all the bloatware installed. It's a fair bit slower than CyanogenMod was but it all seems to work ok. Once I get the ota update i'll root and freeze some apps to sort that out. Now to install TSF shell

[Q] Emergency Calls Only?

Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
you will have to flash the stock rom via odin
PRESS THANKS IF I HELPED
SamuelGTeague said:
Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
Click to expand...
Click to collapse
I think you have damaged your efs partition. Your efs partition contains your IMEI number. Unless you have a backup of your efs, your only solution is to go to Samsung Service Centre. Here is a thread to know more about efs and IMEI,
IMEI / EFS - Know this stuff - including "no network"
Hope I Helped
I think I'm just calling it quits :/ I get a new phone next Monday, so I've just gone and bought a £15 Unlocked phone to tide me over 'till then. Thanks for all your help!
SamuelGTeague said:
I think I'm just calling it quits :/ I get a new phone next Monday, so I've just gone and bought a £15 Unlocked phone to tide me over 'till then. Thanks for all your help!
Click to expand...
Click to collapse
Flash custom kernel..then u can get your imei back...
Sent from my GT-S5830i using Tapatalk 2
SamuelGTeague said:
Hi, I rooted my Phone yesterday and installed TouchWiz Revolution, it installed ok, and is all working apart from the fact that I cannot make any calls or send any texts. Can anyone help me fix this?
I have tried to flash the stock firmware by using ODIN, but no matter what I do and how many drivers I install, it doesn't work. I also tried using the Busy Box and Azira patch method, but the .apk wouldn't install (yes I have unknown sources checked)
I'm very new to this territory, and feel that I am very out of my depth, any help would be greatly appreciated
(p.s I have my IMEI number written down somewhere, I don't know if that helps, as the box comes up blank on my phone)
Click to expand...
Click to collapse
Ok...don't worry you can flash "Rafael Kernal" and flash rom again and after that flash kernel's modules

[Q] Flashed Stock Rom 4.3 via ODIN, can't make/receive calls

Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Thanks tallman43! I'll try that. Also, I noticed now that the EFS folder is EMPTY :/. and the backup .tar I made with CWM says it's 0 bytes? wtf?
still, in phone info, imei and s/n are there. weird?
THANK YOU
Flash a patched modem and kernel from here >> https://drive.google.com/folderview?...kzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
rhrs1987 said:
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
Click to expand...
Click to collapse
Yes you will always need them.
tallman43 said:
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
tallman43 said:
Yes you will always need them.
Click to expand...
Click to collapse
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
rhrs1987 said:
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
Click to expand...
Click to collapse
There is nothing you can do without your original efs backup.Only a service repair can fix it.
tallman43 said:
There is nothing you can do without your original efs backup.Only a service repair can fix it.
Click to expand...
Click to collapse
Understood. I think I have the original EFS in my SD, though I tried replacing it once and it didn't work out... I suppose I'll have to make do. Thanks for everything man
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
I have never flashed the Ariza patch nor have I even mentioned it on my previous posts explaining the problem. Fixing the s/n issue is indeed adviseable, but paying to correct s/n using box here where I live is ASTRONOMICALLY expensive. They should answer for never having fixed it, but they won't. Here is a hell of a lot more than 5-10 dollars, unfortunately.
Believe me , I'm no happier in applying this sorry fix every time I want to factory reset or upgrade, etc; it's the only option I have left at the moment.
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
SirKunon said:
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
oh... well, that I didn't know :$ SirKunon. I understand and totally agree with you on everything. I'll see maybe if I can find some place cheaper for getting it repaired... Many thanks
hi i was wondering if you guys can help me,i have your problem but i have an efs backup,but i cant seem to be able to restore my imei,i tried Ktool,efs professional,nothing seems to work,i should mention that the efs backup was from a Samsung 4.1.2 stock now my phone is on CM11
thanks
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
I was on 4.2.2 leaked version ROM some guy installed at a repair service some time ago when the phone belonged to my mother. I was actually rooted using the CF AutoRoot method, with Philz CWM recovery. I decided to change to a custom 4.3 without having changed first to a stock 4.3.
The problem came when, within the custom ROM's aroma installer, I ticked an option to upgrade the modem to some build I can't remember now and my signal became screwed up. I informed this in the developer's custom rom discussion thread about the issue to which he replied that the problem was that the EFS folder tried to convert from v1 to v2 and failed (this was when I learned of the whole efs version folder change since build XXX (don't remember).
I download a stock unbranded 4.3 ROM and flashed it via ODIN, believing that would solve the issue; it didn't. Finally, I became desperate and took it to a repair service where they used box. Apparently, late did I notice s/n was not the same as the one in the back of phone. I'm guessing that would solve the problem? I don't know.
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
thewalekk said:
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
Click to expand...
Click to collapse
Well, actually, IMEI didn't get cloned; of that I'm certain. IMEI is just the same as it was before I took it for the first time to repair service. It was the S/N that got changed somehow. Should I get them to correct the S/N, and use the original EFS folder (I found it, i think), would that correct all problems?
S/N number is the same with imei number as when you dial *#06# . And as i said before you cant go back even if you have your original efs folder. Dial *#06# and check your imei number from an " imei check site " you can find on google search. That will tell you what i mean.
There are: IMEI, device serial number and Android serial number. First two numbers are on the sticker in battery Bay. They must be correct because are used to authorize IMEI certificate.
Samsung's IMEI begins from 35.....
Serial number usually from RF......
If you see serial number in HEX format in phone's info section, something like f1abcadef1.. than it is android not device serial number and this mean troubles with authorize SIM card in operator network, even if it shows proper signal power.
I don't know there is any secret code to display serial number but there is plenty of phone's info apps in playstore which displays this alphanumeric string.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2

Lenovo TB2-X30L Qualcomm 212 IMEI repair help (tablet's factory IMEI in possession)

I know all about the issues regarding the IMEI and changing it, but this is an honest plea for help.
I'm busy doing work for a client on his Lenovo Tab2 A10-30, which was very slow and unresponsive. I did the usual making-it-faster-tweaks like uninstalling bloatware, disabling apps that aren't needed (or are also bloatware that can't be removed) and trying to clean up the device as much as possible. It did make a difference, but not as much as I was hoping for. The tablet itself was bone stock and running 6.0.1, but the owner wanted it rooted so additional tweaks can be made. He did research ways of rooting it but he was too afriad of doing something wrong (which is very understandable now).
A failed rooting attempt later and I had to restore the device back to working condition by flashing it using the QcomDLoader that came with the firmware I found. Flash went well, but it downgraded it to 5.1.1, which is faster on the hardware and the security patch level is unchanged, so no real reason to update it back to 6.0.1. That is good and all, but the serial number is incorrect and the IMEI is 0. Drat! At least the WiFi and Bluetooth still work, as does everything else.
I proceeded to (successfully) root by flashing SuperSU 2.79 by booting TWRP via fastboot and also flashing Xposed because GravityBox. That went very well, at least. I thought that if I found a method that needed root, having root will help.
Right now, the device is miles better than it once was, but the IMEI and serial number are all I am facing and I want this thing gone. I've done a lot of research on changing the serial number and IMEI and went to too many shady websites to list but most focus on MTK-powered devices which is of no use to me. All I want is to restore the factory serial number and IMEI that the device was born with, and I do have the needed info for that. The factory sticker is still on the device listing the info I need, so that isn't the issue.
Any help will be massively appreciated, but please if you know how to fix this issue please PM me instead of posting it here. I want to make it difficult for malicious users to use the fix for the wrong reasons.
Bump.
hey bro can u give me the twrp image fle which u used then flashed supersu 2.79
D395267 said:
I know all about the issues regarding the IMEI and changing it, but this is an honest plea for help.
I'm busy doing work for a client on his Lenovo Tab2 A10-30, which was very slow and unresponsive. I did the usual making-it-faster-tweaks like uninstalling bloatware, disabling apps that aren't needed (or are also bloatware that can't be removed) and trying to clean up the device as much as possible. It did make a difference, but not as much as I was hoping for. The tablet itself was bone stock and running 6.0.1, but the owner wanted it rooted so additional tweaks can be made. He did research ways of rooting it but he was too afriad of doing something wrong (which is very understandable now).
A failed rooting attempt later and I had to restore the device back to working condition by flashing it using the QcomDLoader that came with the firmware I found. Flash went well, but it downgraded it to 5.1.1, which is faster on the hardware and the security patch level is unchanged, so no real reason to update it back to 6.0.1. That is good and all, but the serial number is incorrect and the IMEI is 0. Drat! At least the WiFi and Bluetooth still work, as does everything else.
I proceeded to (successfully) root by flashing SuperSU 2.79 by booting TWRP via fastboot and also flashing Xposed because GravityBox. That went very well, at least. I thought that if I found a method that needed root, having root will help.
Right now, the device is miles better than it once was, but the IMEI and serial number are all I am facing and I want this thing gone. I've done a lot of research on changing the serial number and IMEI and went to too many shady websites to list but most focus on MTK-powered devices which is of no use to me. All I want is to restore the factory serial number and IMEI that the device was born with, and I do have the needed info for that. The factory sticker is still on the device listing the info I need, so that isn't the issue.
Any help will be massively appreciated, but please if you know how to fix this issue please PM me instead of posting it here. I want to make it difficult for malicious users to use the fix for the wrong reasons.
Click to expand...
Click to collapse
bro i am also facing the exact issue but i found an way to fix it , i need the twrp image which u used ,give me it
I had same issue.
I flashed TWRP 3.0.2.0, I reassigned IMEI number, flashed RR Rom which is pretty good and fast but mobile data is not at all working. I'll update if I find a solution.

Categories

Resources