I recently had some issues with my GPS so I used Odin to go back to stock firmware, everything was still ok after this and my GPS was back to working order. Then I used CF auto root to root my device again/use TWRP recovery. Then I flashed the latest PAC nightly and gapps with seemingly no problems. The phone worked fine for 2-3 days until one day when it was in my pocket I got a warning saying something along the likes of "SIM card has been removed. Reboot required." Rebooting would make the sim come back online momentarily until it would randomly come back up. There didn't seem to be any correlation with any new apps I had installed or things I did on my phone to cause this error. I thought perhaps it was the ROM so I tried reflashing (complete with factory wipe) and the problem still happened. I also tried wiping factory->system->cache&dalvik before reflashing..again it worked but only briefly. I tried going back to stock but it still happens. Right now I'm running task650s aokp and it still comes up..the sim works in other phones no problem. Any ideas on what might be going on/how to fix this issue?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Related
Just bought a new S4 GT-I9505, for some reason it just randomly reboots! It did it 5 times in 10 hours. I tried resetting it to factory in case the apps I had installed were causing it. I don't think they were because as soon as it switched on again after being reset it rebooted after about 5 minutes.
Any ideas?
Could it just be firmware related and I have to wait for an update? Or is it hardware?
Sent from my GT-I9505 using Tapatalk 2
Do you have a microSD card in the device? If so, what kind?
Are your SIM-card properly placed into the device?
It's a 8gb San disk ultra micro sd and I have just removed and inserted it and my sim. Both are fitted correctly.
Anyone?
I'm assuming you are running stock (not rooted etc). Are you using the latest firmware? Have you checked for a system update?
proctologist said:
I'm assuming you are running stock (not rooted etc). Are you using the latest firmware? Have you checked for a system update?
Click to expand...
Click to collapse
Stock, yes. I actually restored through kies so am fully up to date. Checked for an ota to be on the safe side though and nothing.
It has only rebooted once since 9am this morning so it's improved on yesterday!
I had the exact same problem with my s3.
New or of box it rebooted randomly and always when
i stayed the programs first time.
I returned it and got a new. That is what i recommend.
Same thing happens to me.
ParaLanche said:
Same thing happens to me.
Click to expand...
Click to collapse
Are you sending yours back?
if it stays on download mode try to flash a fresh stock firmware for i9505.. you can it from samfirmware.com.. it could help if it is due to a software issue,, otherwise its going to be a hardware issue..
did you try "wipe cache partition"?? sometimes it fixes some problem if it does not return, that s what i did with my reboot problem while playing video.
I'm having the same problem I cleaned cache several times and installed the cmw recovery again. Any ideas?
Thanks
Rooted devices
Have a read HERE - Maybe of some use for those with rooted devices :fingers-crossed:
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.
The Sim card has nothing to do with whether the phone boots up or not. You need to wipe the phone clean and flash the factory images. Report back after.
Sent from my Nexus 4 using Tapatalk
ragerino said:
I borrowed my Nexus4 to my sis for a couple of days. When I set it up for her (after Factory resetting it from the Settings Menu) everything was working fine. Now that she gave me the phone back it was stuck in the boot screen. I also realized that she forgot to give me the SIM Card Holder back which is now in her wallet. She told me that the guys at the mobile phone operator removed her SIM Card without turning the phone off.
I tried flashing Stock Android Firmware a couple of times. I tried it with 4.3.0 and 4.4.0. It always got stuck in the Boot Animation. The only Firmware that boots up to Android is 4.2.0. Even when i do a regular OTA update to 4.3.0 it gets stuck in the Boot Animation.
Is it possible that the Nexus4 is not booting up without a inserted SIM card. I know this sounds stupid, but it is the only explaination i have.
Did someone else experience the same issues?
Update1
I found out, that it's also booting up from 4.2.1. then i got a regular 4.2.2 OTA update which worked too. now was stuck with "Starting apps" after upgrading to 4.3 via ODA Update. Restarting the phone got me stuck in the Boot Animation again. I think I'm gonna wait until i can test it with a Sim Card.
Click to expand...
Click to collapse
Hey, I met the same problem, have you solved it? could you tell me how to solve that? that drive me crazy.
I have read some posts that anything newer than 4.2.2 won't boot if the imei is not being displayed properly by dialing *#06#.
Same issue
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks
tpc74 said:
Hi
How did you resolve this as I am having the same issue and nothing is working? thanks
Click to expand...
Click to collapse
See if your IMEI and your baseband is getting displayed. Otherwise you might have to flash the baseband of your android version.
i have the same problem, i just dont know what to do, i tried the cyanogenmod, 4.4.0 , 4.4.2 , 4.4.4 and i just tried 5.0 and nothing works, just 4.2 , and i have no problems with the baseband :crying:
__bump
any solution? I have the same problem
Y not root it and use a custom rom...Chroma 6.0 Marshmallow rom is one of the best out there...any specific reasons for sticking with stock rom??
Sent from my Nexus 4 using Tapatalk
When I had this a flash a new modem radio and I was fine...
I had a similar issue as you. Could not get past 4.2 version. Although I could get up to 4.3 by flashing an older modem radio after flashing the stock 4.3 image.
My issue was a broken proximity sensor. Any other version past 4.2 would not get past boot animation because the proximity sensor was not working (properly). I did a RMA and they changed the proximity sensor. After that, I could update all the way to 4.4 without issue. Still working today!
It's just a suggestion, but could you check if your proximity sensor is working on the 4.2 build? https://play.google.com/store/apps/details?id=ctsr.android.SensorTest&hl=en can help.
Or you could let someone call you and see if the screens turns off when you put the phone up to your ear and lights up again when you put it away from your ear.
Hey,
I am using the AllianceRom with safestrap, AllianceRom installed on stock rom slot. Recently, my phone would suddenly reboot while I am using it, making a call etc, then get stuck in a boot loop until I pulled out the battery, then sometimes it would start up well or get back in a loop.
What I have tried,
- Installing ROM to romslot1.
- Flashing stock verizon rom, phone worked normally for a while, I tried to get back to AllianceRom or RootDeOdex_NCG rom, but no reboots started again after like 2 happy hours.
Leaving phone alone for like 2 hours powered off, then when i turn it on, it works, for like a few hours, then bootloops...
Ideas?
fixticks said:
Hey,
I am using the AllianceRom with safestrap, AllianceRom installed on stock rom slot. Recently, my phone would suddenly reboot while I am using it, making a call etc, then get stuck in a boot loop until I pulled out the battery, then sometimes it would start up well or get back in a loop.
What I have tried,
- Installing ROM to romslot1.
- Flashing stock verizon rom, phone worked normally for a while, I tried to get back to AllianceRom or RootDeOdex_NCG rom, but no reboots started again after like 2 happy hours.
Leaving phone alone for like 2 hours powered off, then when i turn it on, it works, for like a few hours, then bootloops...
Ideas?
Click to expand...
Click to collapse
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
ldeveraux said:
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
Click to expand...
Click to collapse
Well yeah, I'd use WIFI after installing the rom to install my apps, and everything would go well, I'd even install apps and use the phone for a while. Then sudden boot loops.
Update: Just installed stock rom, and even re-partitioned using the
Code:
http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1
PIT file. It boot looped afterwards, then like 2 minutes later, it run, phone is working, holding breath.
ldeveraux said:
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
Click to expand...
Click to collapse
well if you updated to ni2 firmware on alliance rom thatd b your problem lol.. alliance rom is on ne9 still
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
well if you updated to ni2 firmware on alliance rom thatd b your problem lol.. alliance rom is on ne9 still
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
No I'm on stock ROM, just noting that I had the same problem and how I fixed it
So far:
only had one surprise reboot. Which I'm thinking is not so bad.
I am on stock verizon still, can't do a wireless hotspot. feel caged! Noticed I cannot send sms unless I use a third party SMS application, might be due to the fact that i'm not on verizon but I'm using Hello SMS (it rocks) so eff it.
- I rooted so I could get rid of the annoying "Sim card from unknown source" message, by uninstalling Setup Wizard. and restored some of my apps with Titanium.
Waiting till Sunday, if all goes well, I will install safestrap and it's back to customRom goodness...
Thanks guys for the help.
It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.
You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app
Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!