[Q] process com.android.phone has stopped - RAZR HD Q&A, Help & Troubleshooting

I have a Motorola razr m xt907. It's rooted and I used cellZealot's instructions to unlock the GSM. It's been working fine on Straight talk using an AT&T SIM card I got on ebay. Today a buddy showed me an XT912. Just for the hell of it, I put my SIM card in it. As I expected, it didn't work. When I put the SIM back in mine, I'm get this: "unfortunately the process com.android.phone has stopped" I've got bars with red x on them. I tried the *#*#INFO#*#* Radio Info menu and get the same message. If I attempt a call, it says Contacts not working. I tried to look at the APN settings and it says service not working. Can someone point me to some instructions to get everything needed to flash this thing back or whatever I need to do? I don't have a lot of experience at this, but I can follow instructions.

I reset it back to factory and it working now. Still don't have a clue what happened, but this thread can be closed

Related

[Q] Nexus S no network service! What do I do?

Hi guys I have a 2 month old Nexus S and for no apparent reason all of a sudden today I noticed I am not getting any network service (australia vodafone).
I've tried removing and trying other sim cards which are known to work. My sim card works in other phones so it's nothing wrong with the sim card. Wifi still works perfectly. I've tried going in and out of airplane mode to restart the antenna and I've tried to turn it off and on again. I've also done a factory reset and erased all data through the android menu as well as the bootloader separately to no avail.
However what I also noticed is even though I did factory resets it doesn't seem to completely reset it as the android version still shows 2.3.3 which I applied using a manual update. The phone had 2.3.1 when I bought it. How do I do a full reset to send it back to 2.3.1?
The phone is still under warranty however if it is a software issue I would rather fix it myself then send it away.
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Additionnal bit of info.
Someone on Cyanogen forums asked me to try to flash the radio through fastboot instead of clockwork recovery..
If I do that, it is able to send the file but it seems unable to write. It gets stuck here:
fastboot flash radio XXKB1-GRI40-radio-nexuss-unsigned.zip
sending 'radio' (4126 KB)... OKAY
writing 'radio'...
(I've tried flashing both KB1 and KB3 through flashboot, same results)
Hello everyone,
I have the same issue. I turned my phone on this morning and it said "no service, emergency call only".
I used wifi to apply the OTA 2.3.4 with hope that it'd fix the issue as I read from my google searches. But it does not.
I tried flashing back to KB3 to run with 2.3.4 as well but that doesn't help.
If the phone can still do emergency call, it means the hardware is OK, right?
any suggestion? Thank you very much.
Opteron.
Did anyone ever find a solution?
you could try dialing *#*#4636#*#*, going to phone information, and looking at your preferred network type (might be the wrong one). you could also go to phone information, push menu, go to select radio band, and try a few different ones. hopefully that solves it, or you might have to flash a different radio/rom
edit: make sure you write down the original preferred network type before you change it. it could screw with what kind of service you get if you set it to the wrong one
Hi,
I am having the similar problem with my Nexus S
Tried the *#*#4636#*#* settings to EURO and GSM only but with no success.
Did anyone ever find a solution?
hi, im just wondering what type of root did you use for the AU nexus s. im not sure what root method to use for the SCLCD :S
thanks
fooraide said:
I'm having the same issue. I've posted in the cyanogen forums but I'll share the issue here as well.
I'm pretty scare the radio is damaged or something...
I've rebooted my Nexus S with Cyanogen RC4 to show a friend of mine the boot animation. From that point on, I'd get messages that the application "com.android.phone" force crashed all the time.
I noticed at that point that I had no signal/radio/service.
Wifi worked properly and still works fine.
I've tried updating Cyanogen to the stable release, still no service but I stopped getting the phone crashing errors.
Tried flashing a new radio (KB3) through clockwork recovery, didn't fix the problem.
Tried flashing stock back (2.3.3 Deodexed unrooted) didn't work.
Made sure data and cache was wiped, didn't fix the issue.
I've also tried relocking and re-unlocking the device (oem lock, oem unlock), to no avail.
As a last resort, attempted to enable and disable airplane mode but no go either.
I'm pretty scared that the radio might be damaged (how would it have been damaged by a simple reboot ?) How can I tell and what further steps can I take to diagnose this ?
Right now, I'm trying to reflash cyanogen so that I try and get a dmesg on the device.
Thanks,
Click to expand...
Click to collapse
Hello! did you find any solution or you repaired your nexus s? Im having the same problem. when i try to back to stock from Cyanogen..Any suggestion? Regards
found a solution
hi guys ! I recently had the same trouble that no signals were being received after updating to 4.1.2 but then i dialed *#*#4636#*#* and turned off the radio and turned it on again and now its all fine

[Q] Issue with sim card after using GTG's_Ultimate_Unbrick

I went back to original stock rom because one of my co workers wanted to buy my Infuse to give to his wife. He did not want it to be rooted or have anything on it. I followed the directions in GTG's_Ultimate_Unbrick thread and it worked perfectly. Everything was completely stock like I just opened the box except for one thing...the sim card is not recognized. It says " NO SIM CARD IN PHONE AFTER YOU INSERT THE CARD, PLEASE REBOOT. EMERGENCY CALLS CAN BE USED."
I work for ATT so I know its not because the sim card is bad (I think I tried five new ones today trying to get it to work) plus I used working sim cards from working devices but it still says the same thing.
I tried running through GTG's_Ultimate_Unbrick again but to no prevail. Has any one encountered this or can any one please point me in the right direction on how to fix this issue?
Thank you in advance!!!
seanj1982 said:
I went back to original stock rom because one of my co workers wanted to buy my Infuse to give to his wife. He did not want it to be rooted or have anything on it. I followed the directions in GTG's_Ultimate_Unbrick thread and it worked perfectly. Everything was completely stock like I just opened the box except for one thing...the sim card is not recognized. It says " NO SIM CARD IN PHONE AFTER YOU INSERT THE CARD, PLEASE REBOOT. EMERGENCY CALLS CAN BE USED."
I work for ATT so I know its not because the sim card is bad (I think I tried five new ones today trying to get it to work) plus I used working sim cards from working devices but it still says the same thing.
I tried running through GTG's_Ultimate_Unbrick again but to no prevail. Has any one encountered this or can any one please point me in the right direction on how to fix this issue?
Thank you in advance!!!
Click to expand...
Click to collapse
Did you wipe data/factory reset after unbricking?
If not, try that.
Today around 4:00pm I just had the same problem; however, the problem didn't arise when I used GTG's Ultimate Unbrick... The problem arose when I tried sending an MMS, I sent the first one, it worked, then I had to resend the same MMS to another person, it never sent it, so I tried restarting my phone, and that's when it popped up as "Sim Card Not Found" Ugh!!.. I just tried Flashing it back to stock using Odin GTG's Ultimate Unbrick. I was hoping it was just an ICS random bug, or maybe a just a ROM specific bug. So any help at all would be awesome.
Anyone have any ideas?
sledgeharvy said:
Anyone have any ideas?
Click to expand...
Click to collapse
bump?
did you fix it?

[Q] S3 Won't activate, make calls, or get past activation screen.

I've figured out how to fix it! First, I went to Section 5 of this http://forum.xda-developers.com/showthread.php?t=1762709 thread and odin-ed back to stock. Next I fixed my IMEI using a guide I found on xda. It was the second part of thishttp://forum.xda-developers.com/showthread.php?t=1804117 thread that says "IMEI is already corrupt".
Next, I did a bunch of things that I don't think I should have done and I ended up with a soft brick phone so I went and flashed back to stock via odin by following this http://forum.xda-developers.com/showthread.php?t=1840030 guide. I don't really know if it was necessary and I ended up getting stuck on the activation screen. If at any time you can not get past the activation screen, the third post down from here shows how to get past it so you could go to your settings and check them out or unlock your bootloader or whatever it is you need to do. But this whole part may not be necessary.
This is the part that I think completely fixed the phone. Probably the most important part of this whole guide. You have to dial *2767*3855# from a completely stock rom (root66 or others). It factory reset my phone and somehow the calls work, although it always says I'm roaming
A couple days ago I rooted my s3 and flashed the CM10.1 ROM. It had problems with mobile data and connecting to 4G and phone calls, so I tried out a bunch of different ROMs before deciding it had to be something else.
I figured out that my IMEI had been erased and since I didn't have it backed up (and I have no idea where my nandroid backup is or what happened to it) I had to manually restore it using some NV items reader writer tool and some other similar tool. It worked but there was something else, I think it was called ERI, was set to none. I kept trying stuff and ended up doing a factory reset. I attempted to unroot my S3, I have no idea if I succeeded in unrooting.
What I just did was soft brick my s3, not completely sure how, but I did then re flash root66 using odin successfully and now I'm back to the activation screen. Now it is stuck trying to activate the phone, but it fails every-time, and I can't do anything but restart the phone. So I restart the phone and have to go through the set up screen again and it tries to re-activate but fails and goes through the whole thing again.
Could someone please help me?
According to the Verizon website the phone is activated.
Update 8:24 PM EST: I have gotten past the activation screen but it says that the phone is out of service and when I try to call someone it says that the "mobile network is not available". Please help.
Since nobody is here to answer me, I will post the answer once I figure out what to do, just in case somebody in the future has the same problem.
I'm going to start by re-rooting my phone. I'll let you know how that goes and if anybody else could help me out that would be great. Thanks.
UPDATE 7:45PM EST:
I successfully re rooted the phone via odin and tried to start it up to no avail. Next I tried to flash a ROM, but I must have forgotten to unlock the bootloader since I couldn't even get the phone to boot completely. Right now I'm flashing back to the vzw root66 rom and then I'm going to re root and try to unlock the boot loader.
UPDATE 8:07PM EST:
I finally figured out how to get past the activation screen and I unlocked my bootloader. Before I flash AOKP I'm going to see if I could fix everything else. I think I'm pretty close to a solution. If anybody else is having the same problem send me a message or reply here, I'll try to answer your questions if you let me know what you've done.
I really just need a way past the activation screen. After that I think I could figure out what to do.
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
defkult said:
http://forum.xda-developers.com/showpost.php?p=30182790&postcount=1
Have you tried this?
Click to expand...
Click to collapse
Yes, I managed to bypass the activation screen but now I still can not make any calls.
mikeman45 said:
Sorry your having problems. I wish I could help but never ran into that problem so everything you said went over my head otherwise I would of fine a lot of research. At least now you are learning more and more.I just figured I would respond since no one else did.Good luck.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks.
Well I suppose it is hard for a phone to make calls when it isn't activated.
Goodluck on your quest though.
Thanks for the help, I finally got it working.
myoussef0 said:
Thanks for the help, I finally got it working.
Click to expand...
Click to collapse
What was the main problem?
Sent from my SCH-I535 using xda premium
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
No mobile network found
jmarch said:
In case someone else has this problem...When I flashed pure 4.2.1, I couldnt get past activation and then found out how to bypass the screen. Tap once in each corner of the screen to bypass activation screen. Then once at home screen go to settings>more(right below WiFi/Bluetooth/data)>mobile networks>CDMA subscription. NV will be selected, change it to RUIM/SIM. Reboot phone. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for this post. I ran into the same problem (flashing CM 10.1) with my first S3 phone but did not know how to fix it (wish I saw your post ahead of time). I returned phone to stock via Odin and was able to exchange for a second S3 phone via Verizon (since I have phone insurance). I flashed AOKP ms 1 (jb 4.1.2) on second S3 phone and noticed it was hanging on activation and also said no mobile network when trying to make a call. Luckily, the phone spontaneously rebooted on its own and then started working. Previous to my first S3 phone, I had a Galaxy Nexus. Never ran into any problems with the Galaxy Nexus and almost tempted to go back to it since the S3 seems buggy when flashing a new rom. I am afraid I'm going to brick yet another S3 and be out $400 since I don't think phone insurance will allow me to exchange a second time since this probably alert them to the fact that I'm flashing custom roms.
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
jmarch said:
Also, under mobile networks>system select be sure to change from home to automatic. Reboot.
Click to expand...
Click to collapse
All was working fine until I tried to do this. At first nothing was selected and everything was working, but when I tried selecting automatic and rebooted it selected home for me and it is impossible to change back to automatic without it automatically changing it back to home against my will.

Please help with a flashing mess

I had previously rooted, unlocked and put a custom bootloader on my S3. I was enjoying Beans 10, but wanted to try Slimbeans. I got the initial .zip of Slimbeans installed, but the AIO .zip kept failing, so I had a useless device. Interestingly, I could not boot to recovery. My computer wasn't recognizing my stock Verizon ROMs. I was able to eventually download root66 and Odin that onto my phone, but when it starts up, it gets stuck at the Verizon 4G/LTE screen and never gets passed it. I have pulled the battery and turned the phone on several times, but get the same result. I thought I'd try another Odin attempt, but when I hold down the vol. down/power/home keys and then select the vol. up, I very briefly see the android guy and then then phone reboots. Please help, I'm stuck!
Well, I downloaded a different stock ROM and got that installed. In the meantime, I had to use my iPhone 4 as a backup. When I contacted Verizon to switch me back to the S3, it shows me as roaming. The tech was no help. Anyone with an idea?
Check network settings. Make sure you are on SIM and not NV
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
So, am I asking retarded questions, or is there really no answer?
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
lvgdgts said:
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
Click to expand...
Click to collapse
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Roninrc51 said:
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
Click to expand...
Click to collapse
That sounded interesting, but didn't work.
x714x said:
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Click to expand...
Click to collapse
I'll give this a go at home tonight.

[Q] Bricked phone "System Software not authorized by Verizon Wireless"

Hello guys, I have a Samsung S3 that was purchased "unlocked" to work on T-Mobiles network. After that failed attempt, we switched over to Verizon. 3 weeks later the phone read a message "System Software not authorized". I tried the steps detailed: http://forum.xda-developers.com/showthread.php?t=1840030&highlight=system+software+not+authorized with no errors. However, the phone will not boot. I get infinite boot loop. Honestly, I dont know where to go next. The phone still shows a "unlocked" icon when booted also. All I want to do is get the phone back to its original VZW supported state. Thoughts?
.
Interesting enough, after another wipe of the cache the phone booted up. How can I remove the 'custom' icon and lock this phone back up? I don't want to be denied service at VZW in the future if possible.
You could flash a stock ICS ROM and then update using OTA and it would remove the root, unless its not activated on Verizon. If not, I'll help from there. Let me ask some people to see if my method would work first though.
Sent from my SCH-I535 using xda app-developers app

Categories

Resources