I got a notification for the recently Software update. When i clicked the update, Phone restarted and a white screen with software update came with loading. . . But after that its not moving at all to the next step.. I left the phone for hours but its not doing anything on it.. Please let me know if some one has any solutions..
I would pull the battery out, put it back in, and then start the phone up and let us know what happens.
Is your phone rooted? the update wont work unless you follow certain steps.
I tried pulling the battery and restarted the phone, but again it went to the software update and stuck in the same place. My phone is not rooted, its brand new still with screen protector which came with phone..
Any fix? I am also experiencing the same thing. Thanks!
Also having this issue has anyone figured out a fix yet?
Possibly solved
Follow the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=1414341
We followed the instructions and the device is now recovered and back up and running.
We called TMO 2nd level tech support who was going to replace the device (she had only had is 12 hours when the wireless calling OTA hit). It looks like it needs to be reactivated on the TMO network.
I will post a followup message. We're headed to a corp. TMO store to get a new sim and get the device up and running again.
Related
OK guys i'm a complete noob here at XDA (registered yesterday) but i'm getting really desperate and confused and since i've seen XDA is such a great community i thought i'd give it a shot...
My GSII had been running BeastMOD ROM II v3.0 for about a month now and it worked like a dream but about 3 days ago i turned off my phone and then turned it back on a minute later and I HAD NO NETWORK!! Now, that i recall i didn't do anything to cause this. I called t-mobile and went through all their troubleshooting, no luck. I flashed BeastMOD ROM II v4.2, no luck. Re-flashed BMOD 3.0, no luck. I noticed i don't get ping to my network, I have no IMEI number(i get null/null), and no baseband version(unknown). I'm really worried and hopefully you guys can help me some suggestions ASAP as i haven't had network in three days.
restore a back up of your stock if you still have it.
and this will only get me back to stock and not undo root or will it? will try
Here's what happens. I try to do my first stock ROM restore and it says
"Checking MD5 sums...
MD5 mismatch!" <--Whats wrong? I'm currently doing a restore on a backup three hours after that one which i'm not sure which one it is (maybe the first backup after i installed BMOD 3.0) but hopefully it will do something.
http://forum.xda-developers.com/showthread.php?t=1325036
http://forum.xda-developers.com/showthread.php?t=1433819
http://forum.xda-developers.com/showthread.php?t=1336915
read up, they are different phones but might have common factor
to fix i think:
http://forum.xda-developers.com/showthread.php?t=1462870
mrpagercao said:
http://forum.xda-developers.com/showthread.php?t=1325036
http://forum.xda-developers.com/showthread.php?t=1433819
http://forum.xda-developers.com/showthread.php?t=1336915
read up, they are different phones but might have common factor
to fix i think:
http://forum.xda-developers.com/showthread.php?t=1462870
Click to expand...
Click to collapse
Hey thanx for that last link but the freakin person that made that method just bailed on me after his method screwed with my phone. I have stock now but i have a problem where my phone keeps rebooting until it gets network and even after it finds network and gets its IMEI and Baseband version back, that "fix" doesn't let me use data and for some actions the phone says the SIM card is not ready or available. and when i turn off the phone and back on it keeps rebooting until it finds network like i said. I don't know what the EFS is but that could be something that is making the phone malfunction. Please! Someone help!
i had almost the same problem.
My IMEI is still there, but it just won't connect to any network! All of a sudden, I woke up and it wont connect!
I'm getting a replacement sent to me from tmobile. weird.
Hello all first post here. I googled and searched this issue but came up empty.
I recently rooted my ATT Galaxy S3. using the Samsung Galaxy S3 Toolkit [SNAPDRAGON EDITION]. The root went fine and the phone was working great for a couple hours after the root. I restarted my phone one time and received an error stating "No Sim". I turned off the phone, pulled the battery, and ejected and reseated the SIM, turned the phone back on and got the same message. I have tried rebooting the phone numerous times and also did a factory reset. The phone displays the correct IMEI under the settings menu so that does not appear to be the issue.
I know the verizon S3's had some no SIM issues but it does not appear the ATT phones suffered from this. I also do not have another SIM to switch out but will be going to the ATT store tomorrow to switch SIMs to see if that is the issue.
Anyone have an tricks to try to see if I can get this working this evening?
Thanks
I've seen weirder things in the world of technology but i highly doubt the rooting had anything to do with the SIM failure, sounds like an unfortunate coincidence. Is this by chance a new SIM? Which root procedure did you use for curiosities sake?
Thanks for the reply!
The SIM is roughly 4 weeks old. I used the ALLINONE ( flash insecure boot, CWM, root phone, Install busybox) option in the toolkit.
I just hope the SIM went bad and not the phone its self.
That would be my guess, although i rooted manually the toolkit you used has all the same software/firmwares/kernels etc (at the time it was last compiled atleast)...it just automates the process. My guess would be for whatever reason the SIM just took a crap, AT&T should have you up and running on a new SIM in a few minutes assuming that is the case. Might recommend you do a full backup in recovery and flash back to full stock just in case there is some sort of hardware failure so they don't try to blame you for unofficial software. I don't advise people to try to get away with a free fix for something that is their fault, but in this case i seriously doubt it was anything user inflicted.
Actually I experienced a similar problem.
I'm using a Rogers SGH-I747M but had switched to the Bell ROM to try out the Jellybean OTA which I rooted. Worked fine for weeks, then out of the blue it started randomly saying my SIM card had been removed and forced me to reboot (which took a LOT longer than usual).
Got fed up and am back on stock rooted ROM and the issue is gone. Try reflashing stock and see if the problem continues.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Sorry about posting in the wrong spot.
I tried a co-workers SIM this morning and the phone still would not read it, so it appears the phone has gone bad.
HollidaySlim said:
Sorry about posting in the wrong spot.
I tried a co-workers SIM this morning and the phone still would not read it, so it appears the phone has gone bad.
Click to expand...
Click to collapse
I had this problem with my older S1 i9000.. the issue, wrong modem! not sure if it is the same problem here, but 100% had a very similar problem with flashing the wrong modem.
Flashing your carriers modem should fix it or go back to stock.
I flashed everything back to stock this morning and it was still having the issue.
I went to the ATT store and the CS rep tried a new SIM and lo and behold it worked like a champ. Not sure why my co-workers SIM did not work but all is good now!
I'll give you all the info I can as this has all happened since last night.
Yesterday I was bored, and decided to Root my SGH-I747M [Virgin Mobile, runs off Bell I believe] I used to jailbreak my apple products all this time, my S3 is getting old so I figured heck why not. I was curious about all the Kit Kat hubbub lol.
I Rooted it successfully, then installed the CyanogenMod 4.4 Nightly Custom Rom onto my phone.
That was also successful minus two things that happened, I don't like some of the features & I lost cell service [NOT due to and EFS/IMEI issues]
Decided to downgrade and unroot as the only reason for rooting was to install Kit Kat.
Unfortunately trying to Unroot something went wrong, after pushing start in Odin and my phone froze in Download Mode and Odin failed.
After rebooting my phone I got the typical "Firmware upgrade encountered a problem" so I hooked up to Kies, entered my phone model and s/n and did a full Firmware recovery.
Still had no cell service, could make calls but no SMS.
Found a post that said to take out battery, take out SIM card, boot, then take battery out, replace SIM and reboot.
I believe I have full service back with no issues.
But after the Kies recovery, I have this constant screen on my phone as picutred in the attachment!
I can use my phone, I can touch anything/everything it doesn't block anything thats behind it, but that screen stays. It goes away if I need to go into settings but it comes back shortly. My phone is also still set as "custom" in the info so I'm assuming it's still Rooted???
Update: A friend of mine suggest doing another Kies recovery. So I'm waiting for that now.
And I'm not sure if it's still rooted, Went to settings>More>About Device>Status> And Device Status reads Official.
Alrighty another update incase anyone reads this and can either help or point me to help lol, I am searching forums/google like crazy trying everything.... I figured out that the screenshot is showing me factory mode is on.
Turned it off, after re-rooting and installing SU/Root Explorer.
So factory mode is off, now my only problem is Mobile Network: Disconnected despite Service State: In Service and all the other stats seemingly normal?
It seems I can make calls, but I can not use data or send sms/mms.
I need help knowing how to proceed with my daughter's tablet. I got her a used Note 8 from e-bay. The seller said they could not keep the sim card in. That was not a problem because we don't plan on using it with AT&T, and the price was right.
So the tablet comes and my daughter uses it for the afternoon with no problems. When I got home I was playing with it and put in an inactive sim card to see if it would stay in. It did, so I took it out and gave it back to my daughter. Now evey couple hours it gives me a message saying sim card added, restart your device to access the mobile network. If I pull down the settings menu it says no sim card. I cannot do anything though, so I am forced to restart. I cannot figure out what to do.
First I am not sure if I caused the problem by putting in the sim card for a minute or it was already there.
So I have tried a few things. The last thing I did was a data wipe, followed by clear cache, then I did a force stop on any at&t app. We still get the message.
I tried to update android as it is running 4.1.2 But is says it is up to date.
While trying to figure out what to do I discovered it is apparently rooted. I noticed it had SuperSU v1.80 installed. To check root I installed root checker from google play store. It says root access is verified. So I assume that is why I cannot update android.
Anyone else have this problem? I searched and couldn't find any solutions.
Any ideas on solving it?
Currently I am debating undoing root and seeing if I can update over the air. And hopefully fix the problem. Or updating with a custom rom to try to fix it. But I am not sure how to do that. It has been a really long time since I rooted anything.
I appreciate any help. Thank you, Sherry
When the message comes up I cannot do anything but access the settings drag down menu. It still says no sim card, but the message on the home page says there is and to restart. Must restart device. So after I restarted it I clicked on the notification that says no sim card for app info. It says it is system UI. At first I was hesitant to disable it, but finally gave it a try. It worked. No more sim card messages forcing me to restart. And so far everything works properly except for the background image. It is just a black screen. Everything else seems to function properly. Good enough for now I guess.
My wife and I both have SM-A520W phones. I OTA upgraded mine while travelling in Europe (risky, I know) and didn't have any issues with it. I waited til we returned to upgrade hers, and since upgrading, she has been unable to maintain a WiFi connection beyond a number of minutes, e.g. 5-30 minutes.
I downgraded her phone to Nougat (A520WVLS2BRD2 / A520WOYA2BRD2) using Odin, and things returned to normal. When the July 1st patch (A520WVLU2CRF2 / A520WOYA2CRF2) for Oreo was released I tried upgrading it again over the air, and the WiFi issues returned. Unfortunately after upgrading to this version, I can no longer use Odin to downgrade to Nougat, as it results in a "kernel rev check fail device 1 binary 0" even if I don't load the bootrom. I tried doing a fresh load with Odin of the latest Oreo release as well, but the issue persists.
Any suggestions on either how to downgrade to Nougat, or resolve the WiFi issues on her phone? It seems surprising to me that one phone works fine, and the other one fails repeatedly on the same network and carrier (Freedom). Any suggestions would be appreciated.
Hi. I have the same problem. Were you able to resolve the issue?
Unfortunately not in any way that will be helpful. Took the device to an authorized Samsung repair place, they ran diagnostics, and then offered to swap the main board. They did that, and everything has been fine since.
mutantlog said:
Unfortunately not in any way that will be helpful. Took the device to an authorized Samsung repair place, they ran diagnostics, and then offered to swap the main board. They did that, and everything has been fine since.
Click to expand...
Click to collapse
Could have been a software bug. Personally, I would have got a new phone rather than getting a new motherboard.