I've searched these forums for hours yesterday trying to find someone who has had a similar problem-maybe I am alone in this. Anyway, here goes:
I recently got my phone back from a repair shop-I suffered SDS. On return, the phone was running I9300XXEMA5 at the type-a Turkish variant. It seemed to be rooted-it had an SU program on there. Foolishly, I decided to move up to a BTU firmware that had XXEMG4. So, I moved to that stock firmware. While my IMEI and SN remain the same, I can only make emergency calls. I read about the changes that were brought about by XXEMG4 in terms of EFS. I neglected to make a backup beforehand, so I have since then been rolling forward-the last one I tried was a Chilean firmware with MH2. Doing this has brought about a slight improvement-my phone number was not registering before, but now it is. I still cannot make or receive calls though.
I am going to try a German Vodafone stock firmware with modem MJ1. I hope it works. Also, another thing: maybe it might be the SIM? I was using a full sized SIM from AT&T (my carrier) in my old phone when it was deactivated by the carrier when I went in to get a new micro SIM to put back in my S3. Could that cause a problem? I'm going to get another one from them today and see if that is the problem.
In the meantime, do any of you have any suggestions? The zuluman patch I hear does not work on firmware past July.
EDIT: I have read the sticky posted here: http://forum.xda-developers.com/showthread.php?t=2393289, but I don't see any info about "no network" that pertains to my case.
Hello.I had the same problem like yours and i try this custom rom http://forum.xda-developers.com/showthread.php?t=1663656 (the android 4.1.2 version )
Try this,you don't have nothong to lose.I hope this will help you too.
Edit.flash this in recovery and this should help you
http://www52.zippyshare.com/v/14169396/file.html
Ariza patch doesn't work past July. Zuluman is a rework that does but these are only for serial number 0000 problems
Can't really say a lot else on this. You say there's nothing about "no network" in the sticky but actually its all about "no network".
Lots of words in post 1 here but no details do can't really help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
@rootSU:
I see. Thank you for your help, though I think you misunderstood me-I said I did not see anything that seemed to cover my case (SN/IMEI ok->"no network"). But, maybe I missed something there.
@L0sT19: I'll give these a shot if the MJ1 update doesn't work.
Thanks all.
Oh ok. Apologies then
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
No problem.
UPDATE: Bumping up to the German Vodaphone with MJ1 didn't improve the situation. Also, the SIM works fine in another phone, so I don't think the SIM is suspect. I never had to unlock this phone (why would I need to do so? Moreover, it worked fine before SDS when I swapped between my regular AT&T and an international SIM I use for travelling)-maybe I need to do that now?
In the meantime, I am going to give L0St19's modem patch a go. If that does not work, I will try a custom ROM.
rootSU said:
Ariza patch doesn't work past July. Zuluman is a rework that does but these are only for serial number 0000 problems
Can't really say a lot else on this. You say there's nothing about "no network" in the sticky but actually its all about "no network".
Lots of words in post 1 here but no details do can't really help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
AFAIK there is a modded XXEMG4 modem somewhere that in fact fixes network problem if you can't connect to it even with proper IMEI and efs v1/v2.
My friend had such problem and I couldn't get what may caused that, efs is fine, IMEI is fine and no network at all. I just made a research and we're talking about same thing - patch from zuluman. Trust me @rootSU, it works even in such weird situations, not only 0000 problem.
However don't ask me why because even I have no idea. However if you run out of options with this problem try it -> http://forum.xda-developers.com/showpost.php?p=46585257&postcount=779
Firstly read carefully whole thread
JustArchi said:
AFAIK there is a modded XXEMG4 modem somewhere that in fact fixes network problem if you can't connect to it even with proper IMEI and efs v1/v2.
My friend had such problem and I couldn't get what may caused that, efs is fine, IMEI is fine and no network at all. I just made a research and we're talking about same thing - patch from zuluman. Trust me @rootSU, it works even in such weird situations, not only 0000 problem.
However don't ask me why because even I have no idea. However if you run out of options with this problem try it -> http://forum.xda-developers.com/showpost.php?p=46585257&postcount=779
Firstly read carefully whole thread
Click to expand...
Click to collapse
Hello JustArchi! I will take a look at that too. Thanks!
In the meantime, I have another update: I dropped back down to where it all started: a BTU I9300XXEMG4. After flashing, then doing a factory reset, it looks like things have improved again. However, this improvement is questionable: I consistently get a "Selected Network (AT&T) not available" message appearing. I thought it might be the SIM again, so I went to swap SIMs at the telco. No change-same result.
I'm beginning to think that the modem is not compatible for my part of the world (North America-US). I can't go back because I am no efs2 and I did not back up my efs1. My question now is: are there any modems past (or including) MG4 that will work here in the US?
Ok, JustArchi, I tried the patch, but when I applied it to modem.bin, and tried to flash with Odin, it fails. Going to try and fix that and try again.
Download my flashable .zip -> https://dl.dropboxusercontent.com/u/23869279/Temp/xxemg4.zip
Delete modem.bin from that, put your patched one. Now repack everything through 7-zip -> zip, deflate fastest compression. Now flash this .zip through (cwm) recovery, it will pass.
Maybe Odin doesn't like modified modems.
Ok, got it! I flashed this one. The flash was successful, but the problem remains. Thank you for your help though.
Modem.bin is fine with Odin, but there may have been something in the patch that it didn't like. I don't understand it-only two bytes changed.
Moreover, I've noticed that with this modem patch, the phone number becomes "Unknown". This seems to be a step down unfortunately.
Just flash my original xxemg4 then. Unfortunately I won't be able to help you further because honestly I don't know what may cause such issue.
Good luck tho.
JustArchi said:
Just flash my original xxemg4 then. Unfortunately I won't be able to help you further because honestly I don't know what may cause such issue.
Good luck tho.
Click to expand...
Click to collapse
Thank you for your help. I'm going to talk to mobiletechvideos.com about this. If I can't get help through them, this phone is going on eBay for spare parts. It's beginning to look like a lovely brick-it's a shame I'm not in the construction business.
The phone number always appear as unknown!!
L0sT19 said:
The phone number always appear as unknown!!
Click to expand...
Click to collapse
That is normal
Ok, I see. After swapping the SIM in and out, the phone number actually comes back. Does anyone know exactly when the new format appeared? If it is F6, I am thinking about going back to that-see if that changes anything.
XXEMG4+ EFS V2. Pre-XXEMG4 EFS V1.
Ah ok. So G4 is where it started.
Now, here's another question-is it possible this modem does not work at all in my part of the world? (North America-USA).
Possible? Yes.
There are EFS v2 modems in general > sticky roll-up thread > imei /efs
There's an aroma package containing mg2, mg4 and mh1
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I'll take a look at that sticky. I asked because someone had asked in a similar thread if that modem would work in the OP's country. I took this from a BTU (British Telecom), so I think it might not work. It's strange: before the SDS, I had a British firmware and ran it with no problem. Mind, I loaded this firmware almost a year ago to the month. A lot must have changed since-and for the worst apparently.
Related
My samsung galaxy II is constantly losing network but when I put my SIM into my old phone it works fine. I've tried everything I could find on here i.e roooting, upgrading to ICS but have had no luck.
I bought (well I paid out his contract) the phone from a friend who moved overseas and he was on a different network (Optus) and I'm on Vodafone but my SIM works (just not all the time! ) so I don't know if that has anything to do with it! Anyways I wont take it back to Optus because I wasn't their client to begin with and Vodafone wont help,
Any help is much appreciated as I'm really frustrated! Thanks for reading :laugh:
Safixia said:
My samsung galaxy II is constantly losing network but when I put my SIM into my old phone it works fine. I've tried everything I could find on here i.e roooting, upgrading to ICS but have had no luck.
I bought (well I paid out his contract) the phone from a friend who moved overseas and he was on a different network (Optus) and I'm on Vodafone but my SIM works (just not all the time! ) so I don't know if that has anything to do with it! Anyways I wont take it back to Optus because I wasn't their client to begin with and Vodafone wont help,
Any help is much appreciated as I'm really frustrated! Thanks for reading :laugh:
Click to expand...
Click to collapse
Is your phone rooted? If yes try flashing a new modem.. NELP3 works fine..
If not it's most probably a network issue
HElp?
arunreturns said:
Is your phone rooted? If yes try flashing a new modem.. NELP3 works fine..
If not it's most probably a network issue
Click to expand...
Click to collapse
Thanks, I do belive it is rooted, I didnt do it myself but it was done by the previous owner. Sorry to sound like a noob but how do I flash a new modem and where do I get NELP3 Thanks again
Safixia said:
Thanks, I do belive it is rooted, I didnt do it myself but it was done by the previous owner. Sorry to sound like a noob but how do I flash a new modem and where do I get NELP3 Thanks again
Click to expand...
Click to collapse
Even I had a similar problem a while back, any SIM card, would loose signal completely only on the SII turns out it was a hardware issue, I had to give in my phone to the service center.
To flash a modem if you have heimdall installed, open up the command prompt/terminal in the directory where you have downloaded the modem and extracted the modem.bin file, and type in
heimdall flash --modem modem.bin
or you can use the GUI it has an option for modem, but the modems aren't universally good for everyone, they are region specific, in my country [India] I use the DDKL1 modem, you should look for some modem that's native to your region.
OK. What you need to do is read the Stickies & brush up on Android/SGS2 basics.
Secondly, if the phone is rooted & you have CWRecovery (boot into recovery by turning the phone off, then holding power/volume up/home buttons), you can easily flash modem packages.
I'm also using Voda AU, so I'll get you started. The famous DUKJ1 modem has worked well for many people using Voda in Australia. Unfortunately, XDA doesn't seem to want to allow me to attach files to forum posts at the moment, or I would have attached a copy of KJ1 to this post. Sooo....Here's a link where you can get it
Also, if you do a Google search along the lines of "XDA SGS2 modems" or similar (use your imagination), you should find plenty of posts from here which have links to modems you can flash if KJ1 doesn't work well for you. If that is the case (it doesn't work well for you), then it's a matter of flashing as many modems as you have to in order to find one that works well for you.
The issue could also be caused by the gear/spectrum Voda is using in your area (hence your sim works well in another phone). I guess you're only going to find that out if you contact Voda & ask for support (after you've tried every solution you can find on here I guess).
Now, if your phone isn't rooted, the Stickies have all the information you need in order to root it.
Edit - Also, questions go in Q&A ;-)
Thanks guys, MistahBungle will try the DUKJ1
Also would anyone have an idea as to how I can delete all the optus(old carrier) stuff off my phone?? Ta
You need to have a rooted phone to get rid of the bloatware. You can use an app like Titanium Backup Pro (Look for it on Google Play) to uninstall or freeze (which I recommend) apps you don't want. This thread is a good starting point for working out what you can/can't remove/freeze.
To our friend who added the tag to the thread, we know that Captain Obvious, thanks very much. However for someone new/who currently has little Android/SGS2 knowledge & already has a pre-rooted phone, avoiding Odin (and the inevitable problems many n00bs have with it) & using CWRecovery if it's already on the phone sounds like a sensible WTG to me.
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
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
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
I am trying to repair my nephews i9300 with imei showing the fake 0049. I have been using smartphones for a decade now and it usually takes about 4hrs to 2days to solve a problem.
The first few things i read were the *#4636#* code which was not working on 4.3, so i flashed 4.0.4 but after flashing i realized it was not for reparing imei so i did not go through with it.
now the problem here is that 1), there is a galore of methods for fixing this 2), i dont wanna do anything too risky and brick the mobile of my nephew.
If it was my own phone i would have been done trying about everything by now but i am still reading around to see the surest and relative fix to my dev/prob.
Btw unlike from what i have read, his Imei got corrupted while he was asleep not flashing any custom roms etc.
Atm i am downloading the XXUGMK6 and will go through with flashing it before i install XXUGMK6 Modem.zip
XXUGMK6 Kernel.zip.
(i could not find the firmware for my country btw currently downloading one with OXA at the end.)
I hope it works out but any clear advise would really be helpful here.
Thanks.
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
rp158 said:
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
Click to expand...
Click to collapse
No backup, im currently flashing xxugmk6, let me get back to you.
.
Baseband is now i9300XXUGMK6. (thats the modem?)
Tried this method
http://www.androidveterans.com/solve-registered-network-galaxy-s3-i9300-issue-restore-imei/
First time with only PDA option, after ODIN was done, it gave me null/null IMEI, after flashing the patched Kernel and modem it went back to 0049. I checked CSC with *1234# and it was UNKNOWN.
Tried again with ODIN with PDA,CSC and Modem this time. After Odin the IMEI was 0049 instead of Null. After patched files flashing nothing chanded. (though CSC shows in *1234# menu).
Used this for flashing in Recovery.
CF-SGS3-CWM-v5.5-v1.2.zip
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
rp158 said:
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
Click to expand...
Click to collapse
I am at 4.3 currently will it update any further from Kies?
Btw 1 thing, He said he woke up in the morning it was saying "NOT REGISTERED ON NETWORK". He dint do any flashing or anything.
I think phone was working with the fake IMEI (0049) for more than a year and just stopped working when casue conflict between Wifi and Network radios etc.
What if i goo back to 404 and try the *#4636#* or similer methods?
Going back to 4.0 is worthless. IF there ever was a valid IMEI/efs-package, you messed it up in the meantime.
Either update-procedure repairs or service-center or going on without telephone-functions.
What about these methods?
http://www.sammobile.com/forum/showthread.php?t=15196
@the boy plunger: these are the witchy things. I only read about and didn't try, so go your way.
Maybe, the patched modem helps.