I have 2 Galaxy notes that have been stock since day 1 with no modifications other than sim unlock via code. I waited patiently till the official ICS release came out to do my first ever phone update using Kies. After the update, 1 is running perfectly and the other has a notification stating that the sim card is not valid, contact customer care. I swapped sim cards and got the same error. Both Sim cards on other phone working properly.Restarting phone didn't resolve the problem. After a few seconds to minutes from time of reboot (in which phone recognizes network and I can make phone calls normally), the same error occurs sometimes with the code in place of the Service Provider name (63081)? I tried factory reset using phone menu and it wiped it clean but still same error. I tried reinstalling the ICS firmware/rom update provided via KIES and I'm still getting the same error.
I researched this plenty and noticed that others have had similar problems with sony phones after ICS update with no resolution.
Any suggestions?
is rooting possible yet to try another rom?
Can I go back to GB though I don't have a backup?
It sounds like a bad modem flash.
Why not make a nandroid of the good phone and restore it on the bad phone.
Thanks for your reply. I resolved it. Even though I had tried a different sim from the same company for a nother number and it hadn't worked, I still decided to make a new sim for my number and that seemed to resolve the problem. Still odd as to why ICS update would do that.
rangercaptain said:
It sounds like a bad modem flash.
Why not make a nandroid of the good phone and restore it on the bad phone.
Click to expand...
Click to collapse
Alright, so first of all, my Samsung Galaxy SIII got some damage, and then we brought it to a repair shop. They changed the motherboard, and then returned it to us and it was working fine. The only thing is, the Android version is still on 4.0.4, and whenever I boot the phone, a T-Mobile bootloading screen appears, and it annoys the hell out of me. So, I flashed Android 4.3 Jellybean using Odin. Yet, after the update finishes, the phone won't make a text or a call. It always says 'Not Registered On Network'. So here are some notes of the phone's status...
1. I tried to use Ariza Patch, yet it didn't work.
2. The IMEI's number is not changed to 0000 or anything, it's just a 15-digit number and has a '/01' at the end of it.
3. The signal is full.
How could this be fixed? Is there anyway to fix this? It would be very much appreciated. Thank you!
Take it back to the repair shop and tell them they botched the efs folder after their repair. You might be able to get a network by reading the sticky thread on efs, or the patch thread but you will always have problems with updates unless you get the efs folder sorted by a professional.
I did return the phone, then after that, they replaced the board again. After I tried to update it to 4.3 once again, the same thing happened, still not registered on network. :/
Its been a long slog but ive got the os - I thought id open a new thread. I cant seem to register on the phone network. Its not the sim as ive tried another on (another provider) and that's the same and its also been a problem across all (even the stock images) that ive tried. Ive read on another thread is there a folder that I could have formatted which holds network or radio information....?
Just a thought....
Cheers.
ok - I believe its something to do with me imei number being forgotten....found a tool called the ARIZA patch but for some reason my cm13 build isn't rooted. Ive installed superuser but I still don't get root access (needed for ARIZA to work) I assumed the cm13 build would already be rooted....and idea's - I'm probably missing something...
Edit: just found the root slider - ariza patch doesn't work though - error is "phone not proper"
ComfySofa said:
ok - I believe its something to do with me imei number being forgotten....found a tool called the ARIZA patch but for some reason my cm13 build isn't rooted. Ive installed superuser but I still don't get root access (needed for ARIZA to work) I assumed the cm13 build would already be rooted....and idea's - I'm probably missing something...
Edit: just found the root slider - ariza patch doesn't work though - error is "phone not proper"
Click to expand...
Click to collapse
You could try this guide
Yep - looks like that's what happened - my imei number currently is that....well, at least I know now how to get it to a custom rom so ill have to reflash back to stock first - thanks for the link, that's a great help....ill report back in a bit...thanks again.
Nope - no luck so far....but that's definitely the problem.....lost the imei....ive never had the issue before - ive flashed mine loads of times (Note 3) and never had a problem so I never thought to back it up....if anyone has any other option I can try that'd be great....
Cheers
Ive followed the walkthrough but its not 100% clear - I might run through it a few times....
Supersu does not work on CM13, yet.
You need to turn on developer options in settings.
Well, all the stuff ive tried so far hasn't worked....I think id be looking at a manual entry (the imei is under the phone) so will try to find something along those lines....
I did try going back to a stock rom but seemed fruitless. ive gone back to cm13 as it seems the system is more open (obviously). It looks like the imei changer programs will work if xposed framework is installed....which I'm currently trying to work out how to do....easier said than done...
I think I'm done - I cant see any way of getting the imei back on there....think the phone has had it....my first loss...the xposed framework does not support the s2's architecture (that I can see)
ComfySofa said:
I think I'm done - I cant see any way of getting the imei back on there....think the phone has had it....my first loss...the xposed framework does not support the s2's architecture (that I can see)
Click to expand...
Click to collapse
I had a similar problem when I switched from ICS to JB, tree years ago. My phone would not register on any network no matter the SIM I put in (I tried 3 different operators). The only way I could solve it was with an apk called "Galaxy S2 Sim Unlock" - I had to work with that a little but after a little headache I could solve the problem. Since then, everything is ok - I can register on any network. My personal lesson from that experience is: "Never do a Factory Reset when upgrading Android (eg. ICS to JB, JB to KK, KK to LP and so on)." But that's only my experience. Now I'm on MM 6.0.1 (Cyanogen 13).
Ok- ill go take a look now....thanks for the link - I was hoping that someone could offer (something like this) so ive got another way of tackling it...cheers.
Edit - just gone looking and I cant see an app with the exact description....do you have the authors name (to narrow it down a little??)
Just to add this phone wasn't actually sim locked in the first place...are you saying that the side affect of using the sim unlocking software will insert the imei back in??
ComfySofa said:
Just to add this phone wasn't actually sim locked in the first place...are you saying that the side affect of using the sim unlocking software will insert the imei back in??
Click to expand...
Click to collapse
I bought my phone unlocked in 2011 - brand new, official release, so on.
I rooted it right away and started experimenting, installed tons of unofficial/official ROMs, playing with kernels, tweaking and everything, upgrading as soon as a new unofficial version would show up, from Stock Android 2.3.3 to... to X ... to Y... up to MM 6.0.1 (CM13) now.
I had few bricks over the time but I solved them in few hours to two days. But this problem with network registering was the longest of all and the scariest - it happened as I described it in the previous post. My understanding on that time (as I remember) was that the Factory Reset wiped my EFS.
That (Galaxy S2 Sim Unlock) apk gave me few codes I could use. Below is a note I made on those days (pretty confusing for me now, but it might help you):
-- Introducing "SIM network unlock PIN" didn't help me. I restart the phone and when it asked me the "SIM network unlock PIN", I introduced first the "Unfreeze code" but the network didn't unblock and then I introduced "SIM network unlock PIN" and the network unblocked."
As I searched now on Google Play I could not find "Galaxy S2 Sim Unlock" anymore. There is something called "GalaxSim Unlock" (by Spocky) - updated on december 2015, with support for Android 6.0.
Strange as mine I believe is the same as yours....unlocked generic phone. Ive not had any messages atall regarding "sim unlock" - my issue is theres a dummy imei in there - that's it although ill go and look now....any more information you have would be great...
Its the little things that help sometimes....I couldn't get the partitioning done atall then petrolcan mentioned a user and his script...then from that little bit of info I had a flashable zip that did everything for me...so everything helps.
I'm just not sure on the correlation between the sim unlock software and the imei missing....
ComfySofa said:
I'm just not sure on the correlation between the sim unlock software and the imei missing....
Click to expand...
Click to collapse
Again, I'm not a specialist, but If I remember right, the EFS has to do with the IMEI, and on that time I have lost my EFS, and, I guess, my IMEI....
My S2 was usable (apks, games, wifi...) but not as a phone (for calling and receiving calls & SMS).
Or, you may want to try finding some ways of restoring EFS/IMEI....
yes, the efs folder holds the file which the imei is in (a bin file) but from what I read if you remove the efs folder completely the os will generate a new one....once you've got a new file then effectively you "should" be able to inject the imei into that thus renabling your phone (and therein lies the problem - getting the imeil back in) - yes, mines the same....everything works bar the phone access to the network...
ComfySofa said:
... inject the imei into that thus renabling your phone (and therein lies the problem - getting the imeil back in) .....
Click to expand...
Click to collapse
Just guessing: Maybe "GalaxySim Unlock" injects the IMEI??? Check the description on Google Play:
"Detects errors like lost imei / serial in nv_data caused by third party apps"
You can give it a try with the free version - see what it founds on your phone.
I did try it....just gave me an nv_data error....nothing more than that...
ComfySofa said:
I did try it....just gave me an nv_data error....nothing more than that...
Click to expand...
Click to collapse
I'll check about that tomorrow as I found few threads on XDA and I have to go now.... Hopefully you'll be "up and running" by the time I come back!
Heh - I hope so but I doubt it - spent about 5 hours Friday night, a good 12 yesterday and 12 the day before....any information you have would be great! thanks very much.
After looking around I think my best bet is the NV-items reader writer v1.0. but, I cant get it connected to the phone.....anyone got any clues on that one?? once connected it looks like you can edit the nv file and add the imei back in....
Okay,where do I start.
So I bought this phone off a friend of a friend(I was going to sell it on for profit as it was a good deal).
I noticed when trying to update that it was telling me it was an unauthorised software, so i took it the device was rooted.
I then factory reset the device to see would it go back to factory settings, but just stayed on the custom firmware.
I then decided to flash stock firmware onto the device from Sammobile (device boots up with Three logo so I assumed it was with Three Ireland network so that's the firmware I chose.
After flashing the device it boot up with a dm verity error and would only go as far as the Three logo. After some research I found a discussion and followed the steps in this, flashing a file called CF-Auto-Root-zerolte-zeroltexx-smg925f. After doing this the dm verity error had gone and the phone booted up fine.
I left the phone like this, as I was going to sell it at a later date. Before I sold it I had one last test of the device and noticed it would not connect to a mobile network (I don't think this issue was there when I first got the phone as I am nearly sure I tested my sim card in it, but cant be sure). I just kept getting 'not registered on network' error.
After some more research I downloaded the Samsung info app and ran it. I then noticed a few strange things.
1). The serial number of the device was just showing up as a string of 0's.
2). The imei number that was listed did not match the imei on the back of the phone.
3). The carrier was showing as O2 UK, but Im not sure if this is an issue as O2 and Three are basically the same network here in Ireland (Three took over O2 here).
After doing an imei check, I found the imei listed on the back of the phone to be fine and was showing all the right details, serial number etc. But the imei that was listed as the imei of the phone, in settings and using *#06# was showing up as not existing.
I found this very strange and I'm sure this has something to do with why it can't connect to a network.
Any suggestion on getting this device back working properly as it is just a paperweight now as it is, and after spending money to buy it so I could sell it on I don't want to have wasted that money for nothing.
Any help is appreciated.
Thanks
Nothing? ?
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
bornxawkward said:
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
Click to expand...
Click to collapse
Please check your voice mail settings in your phone app. See my screenshots.
There you should select the correct service provider and the Visible mailbox number.