Hello
Everytime I make a call since this morning, my phone just reboots after a few seconds, I was using the 25.10.2012 CM10 nightly.
After realizing this, I made a full wipe in CWM and restored the CM10-M1, where it worked for sure a few weeks ago (even a few days ago, I make a lot of phone calls for work) and it's still rebooting after a few seconds of calling.
So after wiping and making an old rom restore were it worked, could it be a hardware fault or what else could it be?
If there is more information needed, just tell me.
Thanks
Samwan said:
Hello
Everytime I make a call since this morning, my phone just reboots after a few seconds, I was using the 25.10.2012 CM10 nightly.
After realizing this, I made a full wipe in CWM and restored the CM10-M1, where it worked for sure a few weeks ago (even a few days ago, I make a lot of phone calls for work) and it's still rebooting after a few seconds of calling.
So after wiping and making an old rom restore were it worked, could it be a hardware fault or what else could it be?
If there is more information needed, just tell me.
Thanks
Click to expand...
Click to collapse
Does your baseband and radio match?
Swype'ed on my CM10 Galaxy Nexus
Related
Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App
Hey Everyone,
I am running the SGH-T989 with the latest Darkside (2.3) ROM and kernel. Though new to the forums I have been "trolling" here for years and rooting and moding every phone I have had since ... well I can't remember when.
Never had any serious troubles, but suddenly, about 2 days ago I stopped getting incoming calls. It acts as though the phone is off and all calls go straight to voice mail, this happens when I have full signal, and I can still make outgoing calls. I have done full wipes, charged fully, tried it plugged in, not plugged in, on WIFI calling, on cellular networks, different ROMs, and nothing seems to work.
Anyone have any suggestions?
check under settings --call--- call rejection---auto reject numbers---should be off or the ones you want rejected...may got switched to all calls
Thanks for the response Bobby. Unfortunately I checked that after posting and it is set to off.
However I retired again and I am receiving calls now over Wifi calling, just not over cellular networks.
This is herring frustrating and of course the missus blames me for routing and ROMing
Ok,actuakly I tried to type retried but you gotta love auto-correct.
Sent from my SGH-T989 using XDA App
What about call forwarding?
Just checked and Call forwarding is set to:
Always forward: Disabled
Forward when busy / unanswered / unreachable is all set to voicemail.
Could that be the culprit even if I show full signal and am able to make out going calls? Should I disable any of those?
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
myndsey said:
A few weeks back I had flashed a new rom and did a full app restore from Titanium backup. I had the same thing happen with call going directly to VM. I did a full wipe and re-flashed and then restored only missing apps and the problem went away. I assume it may have been a conflict with the restore. Might be worth a try. Good luck.
Click to expand...
Click to collapse
Yes if you restore system data that causes issues unless it's backed up and restored on the exact same rom.
Sent via Brain Drain
I am having the same exact problem on Jugs 5.0... very interesting. I did not do a Ti restore, but rather just upgraded from one iteration of Jugs (3.7) to the latest.
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
You beat me by seconds Poser. I tried Jugs 5.0 too and the problem still didn't go away.
Mystic_ said:
But what happens when you don't restore any apps / data? I tried a fresh ROM install and prior to installing any apps I was unable to get any incoming calls (except when on WIFI calling).
Thanks for the help everyone. I guess its time to break down and contact Tmo and see what's up.
Click to expand...
Click to collapse
By fresh install did you go into recovery and:
1. wipe data/factory reset
2. wipe cache
3. wipe davlik
4. mnt /system and wipe
5. flash ROM
I only ask, because I am wondering if "ghosting" is leading to mine and your problem?
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Mystic_ said:
Well, with the Darkside ROM has its own script to do a wipe ..... But, I'm a little OCD so, especially after having the problem I went through and wipe / re-wiped / wiped dalvik / re-wiped and factor reset.
Then after the flash (no matter what ROM that I have tried since having this problem) I fix permissions and then leave it for some time after boot to let it "settle in".
Hopefully the "ghosting" is your problem and the full wipes will help.
Click to expand...
Click to collapse
No dice, same problem. Wonder if it is an /efs problem?
Don't know but it is odd. I can still make outgoing calls, get data and everything else.
I have the same exact symptoms...exactly. It also just began a couple of days ago. Have you restored to bone stock via ODIN (I can't, my usb port is shot)?
Get a new sim card. If factory reset doesn't do it and you think its not network related and you don't think you accidentally blacklisted all your friends its probably the sim card.
Sent from my HTC Vision using xda premium
Android_Monsters hit the nail on the head. I took it to a T-Mobile store, they replaced the sim and all is golden (except that my wife can now call me again )
And in case you are worried, my phone was still rooted / ROMed and the Tmobile rep working the store was simply stunned to see the custom boot screen. They didn't care in the slightest that the phone was rooted and ROMed. In fact he was upset because he couldn't do that because of company regulations.
Same here.... new Sim did the trick
Huh?
This happened to me b4 I called t-mobile and they fixed it without going anywhere.
Sent from my SGH-T989 using xda premium
Hi, I have the Wildfire S with Cyanogen 7.2 (the release from july this year) and I had no problems so far, but since yesterday it started behaving strange.
Each time I make or receive a call after a few seconds the screen goes blank and and I get two vibrates. Then each time I move the phone the screen comes to life and two more vibrates. THis will continue through-out the call
It is very annoying... and I have no idea how to fix it...
I didn't make any changes or updates or whatever it just started happening...
Try wiping the rom once.....it might help.....But remember to backup
csoulr666 said:
Try wiping the rom once.....it might help.....But remember to backup
Click to expand...
Click to collapse
What do you mean by wiping? the dalvik cache? will every thing still be there, except the cache of course, cause I've only wiped before installing roms and am not sure what really happens...
EDIT: A Factory reset fixed it, sooo it's not broken... but it would be great if I can fix it without flashing and installing everything all over again...
Any suggestions?
Is there anybody out there that can help?
I've had a SGN for over two years and it seems like I have always had problems with it. I've been through mulitple SIMS, devices, ROMS, and various apps. Most recently, I had to get a new device. It took several steps of troubleshooting, but I finally rooted the phone. Got Rootchecker Pro and was able to confirm with no errors. For a while now, when I wipe, CWM skips over Android_Secure because it can't be found. About a month, after rooting the phone, I flashed the CRDroid (based on Cyanogenmod) ROM. It was then that I would get bootloops after checking on the Mobile Networks setting. It didn't always do it right away. When it didn't restart immediately, I wouldn't be able to make phone calls. Shortly after, I went through the Developer Options and updated to CM 10.2. The Mobile Network Bootloops stopped and I thought everything was great. But, there has been about three times that the phone will randomly restart and go into a bootloop at the CM splash screen. It's happened a couple times randomly and yesterday after taking about 45 pictures over a 45-minute span.
Luckily, I've been much better about making Nandroid backups and it hasn't been a big deal to restore. You can imagine, though that it is incredibly annoying and critical sometimes. I've been trying to rack my brain about what is consistent about the bootloops and can't figure it out.
It's a Toro with CM 10.2 on 4.3 Android. I flashed Golden Kernel and PA 4.0 GAPPS.
I would love to see what everybody thinks the problem could be. Thanks again.
I have 2 problems.
First since a month mine and my wife's phone started to have no connection after dialing some number. We both have the same issue. Let's say I hit to call my friend Tony. SO after pressing name I see connection sceen, I see time of conversation, I see bars but no voice. The person I call to hears me. I tried with different people. Same issue on both phones.
After restart calling is normal. Airplane mode off/on doesn't help.
On June 2014 we finally decided to switch roms. So since then we have Cyanogenmod 10.2.0-hercules (4.3.1). It was alright, beside problems with camera, 30% of photos and videos have defects /artefacts.
SO I thought maybe changing rom will help.
I spent whole day on searching stock roms but all files are deleted and i can't find neither one of last 4 versions.
So I thought I will change rom to earlier version of Cyanogemod. It didn't help.
Today I spent few hours too and finally decided to change rom to 4.4.2 | HellKat (first that succesfully wanted to download).
Something went wrong.
I thought I was doing everything right and there are no tricky parts but I guess I forgot to do something or... maybe something is wrong with my phone.
So I'm using TWRP. First I hit "factory reset", then "advanced wipe" and and wiped everything beside sdcard.
Then I installed my new rom, after few seconds, it shows "failed"
So I wiped everything again and tried to restore my backed up rom.
It showed "failed"
SO I wiped everything again and installed my current rom.
It shows "failed".
I started to worry and to think that I just want my old phone back, at least it works... sometimes.
I hit reboot, wipe, and install again my current rom.
Success. (Maybe reboot after wipe is needed? or maybe it's coincidense)
Finally.
I hit reboot and installed gapps.
So I was almost happy that i could go back to where I was.
Not quite...
I started to download my apps.
On second one screen went black.
Actually it powered off.
I tried to turn it on but it was only showing Samsung logo and black screen after that.
I went to TWRP, wipe, install current rom 3 times.
It seems that restart after installing makes phone bad and I can only see black screen without even booting. Ewentually I found out that now I have 60% chance that if I hit reboot I won't be able to come back to my system.
I will have just black screen and the only way to have working phone is install new rom again and not restarting.
Or maybe it's just coincidence but I don't have time to play and spend another hour on wiping, installing rom and the gapps and apps.
I hope you guys see some stupidity or some detail in what i did wrong.
I hope that maybe one of you will actually will be able toi help me with chagning rom the right way or to fix that connection issue.
same, sort of.
I have similar issue. I cant make calls unless i reboot. And it seems when i open an amount of apps, the calls just dont work. I dont know what to do.
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
DarkMatter_74 said:
Make sure you're on the latest TWRP, earlier versions will not successfully flash newer roms.
As for the voice thing, did you have snapchat installed? It's been reported to occur when you have snapchat installed.
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app
Click to expand...
Click to collapse
Funny fact, before you wrote we have been testing our phones and found out that it is actually snapchat who makes a problem wih calling. We uninstalled it from botrh phones and 3 days it is ok
I will install new TWRP , hopefully there is newer version.
Just a heads up, Google Hangouts Dialer has the same effect as Snapchat as well.
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
blackwing102 said:
Is there any way to avoid this? i use snapchat often, and removing it would be a loss :/
Click to expand...
Click to collapse
There's an older version of Snapchat that works without booking your audio. Search the threads for it. If I come across it anytime soon, I'll return with the link.
Edit:
http://forum.xda-developers.com/showthread.php?p=57344868
Sent from my SAMSUNG-SGH-T989 using XDA Free mobile app