Database Info

[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] "Package file is invalid" error on stock ROM & CleanROM Stand 3.0

I was lucky enough to get one of the earlier batches (pre import ban) of the AT&T HTC One XLs and I have enjoyed having it over the past 5-6 weeks. A few weeks back I decided to root my phone and unlock it as I wasn't having any luck upgrading via the OTA update. I believe that soon afterwards I started having a problem installing some larger files and updates, getting a "Package file is invalid" message via Google Play.
At first this only seemed to happen occasionally but a few days back, it started occurring with practically any update or install. I tried cleaning the dalvik and other caches, factory reset, and wiped the SD card without any improvement. Yesterday I decided to make the leap and install CleanROM, both out of curiosity and a hope to resolve my problem. I wiped the system via the recovery bootloader, wiped the cache, wiped the dalvik cache, and wiped the SD card and installed CleanROM. While the install went well and CleanROM is running perfectly, I still get the package invalid method with any install larger than 1mb or so. I am frustrated about this problem as I have enjoyed this phone up to this point. If anyone have any suggestions to resolve this repeated error I would be very grateful. Thanks.

I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
also check theses things. http://www.thespicygadgematics.com/2011/12/fix-android-package-file-is-invalid.html

Follow-up on suggestion
android addicts said:
I think you followed almost all the step. But i think there is a issue on your network connection. Try to download new apps over the WiFi. I think you can't use any other mobile network ( i think you have network locked phone).
Click to expand...
Click to collapse
Thanks for the suggestion but it turns out exactly the opposite is true. I have been trying to install programs over wifi and they keep failing with the invalid package file message. After reading your suggestion, I turned off the wifi and tried installing several larger programs via the mobile network - they all downloaded and installed without a hitch! Crazy.
So, it looks like my problem might have something more to do with either my wifi network/router or with some aspect of the wifi hardware or software on my phone. Tomorrow I am going to try accessing and installing files from a different network and will post my results then.

[DONE] Fix for "Preparing Sim Card..." Error for CleanROM

Hey,
Starting this thread up as a place to figure out the "Preparing Sim Card" problem.
Essentially, if you flash CleanROM 4.1 with CWM, you'll probably get this error. There were plethora of fixes out there, such as:
1. Clearing all cache (fastboot/recovery)
2. Clearing all data/force stopping problem apps (people/dialer/messaging)
3. RUUing back to stock
4. Flashing a new radio
5. Removing/Changing SIM cards
6. Trying dialer trick:
.....a. Go to Dialer (if you can't access it, clear the data in it first)
.....b. dial *#*#4636#*#*
.....c. Turn off the radio
.....d. Turn on the radio, and right as the toast appears, choose something from the drop down menu.
.....e. Run a ping test to make sure everything's alright.
7. Used TWRP to clear system/flash new ROM
8. Tried another ROM with GSM Patch
CURRENT STATUS: WORKING!!!! =D
The answer to all your problems issss........
Well, it's multi-step
1. Make sure to flash back via RUU (preferably 1.82 since 1.85 was a b**** for me to re-root T_T)
2. Make sure to unlock your bootloader again
3. Install back CWM (I know...wtf?!) <<THIS STEP IS IMPORTANT (believe it or not)
4. Go back and flash CleanMOD 3.1 or something (just anything below 4.1 should do the trick) [if just installing CleanMOD doesn't work, install the GSM Patch too!]
5. NOW install TWRP
6. Install CleanMOD 4.1
7. SUCCESS!!!
Also, thanks to tehdef, who also tried this method:
Here is what I did to break my phone.
I had the following MODS.
-AOKP 6.1
-CWM
Decided I wanted to test something on CleanROM 4.1
- Flashed CR4.1 in CWM
Got stuck in Boot Cycle and CWM would not load
1. Locked Bootloader
2. Installed 1.85 Evita RUU
3. Unlocked Bootloader
4. Installed TWRP
5. Flashed AOKP 6.1
At this point, I still had an issue. Instead of receiving the "Preparing SIM" Message, I had absolutely zero signal, and I could not "SAVE" an APN.
6. Rebooted to Bootloader
7. Reset to Factory while in AOKP
8. TWRP Loads
9. Reboot to System
My phone now has signal and full contacts and I can make calls and send Texts and MMS with no additional modifications. Please note that with AOKP Superuser comes installed and works just fine, so for whatever reason I did not have to root my device.
NOTE: YOU DO NOT NEED TO USE CLEANROM 3.1 IN ORDER TO GET BACK TO A WORKING STATE!!! Just any rom supporting the unofficial CWM should do. =] (at least I think so, but I'll confirm when someone get's back to me =D)
Thanks goes out to...
Scott for his awesome ROMs and his life lessons
kleeman7 for toughing it out and helping me through the entire thing
tehdef for helping me test out several of my theories
shackman716 for suggesting the idea that worked (it was so crazy it actually worked! XD)
and thanks goes out to anyone I forgot to mention. XD
Now, back to more ROM flashing

scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?

redpoint73 said:
scrosler specifically states not to use CWM to flash his ROM. Have you tried TWRP?
Click to expand...
Click to collapse
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.

Error 170 is a usb communication error and is fixable. Turn off HTC sync. Check for it in running processes. If you still get the error reboot to the bootloader make sure the phone says fastboot usb in red then start the ruu.

tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
thats a driver error do u have htc drivers installed? good usb cable? tried a diff slot?
if not install htc sync let the first portion install. when it comes time for htc sync inself to install cancel. and just the drivers will be installed

tehdef said:
We are well past that point, redpoint. We've already flashed, and now things aren't working correctly.
In my specific case, XDA Mobile didn't Bold/Red the text to use TWRP instead of CWM, so when I flashed and attempted to boot, I got stuck in a boot cycle. I went back to try to get into recovery, and it wouldn't even go there. So I re-locked, and flashed the 1.85 RUU.
Now I'm getting the same 'Preparing' issue only when I attempt to open up Phone, Contacts, Messaging, all on the stock RUU while being Locked.
I can't even attempt to re-flash the Stock RUU because I'm getting Error 170 on the RUU installer.
This majorly sucks.
Click to expand...
Click to collapse
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".

I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync

elsupermang said:
I had the same error. I believe I was able to reproduce it by adding my Google Play Account then adding my gmail account (with the same email address) using Activesync. Right after adding my gmail account I would get an application crash (cant recall which one) the phone would reboot and go into a reboot cycle when "Preparing Sim Card". To avoid the issue I did the following:
1. Wipe System, Wipe Data
2. Flash CleanROM 4.1 DE
3. Wipe Cache
4. Install Mods
5. Boot up, add Google Account from the setup wizard
6. Turn on Auto-Sync from Wizard
7. Go into Settings > Accounts > Uncheck sync Email,Contacts, Calendar
8. Clear Data for Email, Contacts, Calendar apps.
9. Add gmail via Activesync w/ Email/Contact/Calendar sync
Click to expand...
Click to collapse
Well, I tried emailing and stuff, and it seems anything regarding data seems to be alright. It just seems to be the issue with phone/sms data now. I believe it's something software related as it still reads my sim just fine, and it recognizes when it gets a call. Just when I get a call, it repeatedly FCs. I might give it a try though, so thanks!
redpoint73 said:
The OP never stated any of that, and it doesn't seem that he is stuck in the same way you are. So I was asking if he tried to flash TWRP, and then reflash the ROM. Which is not listed as one of his "possible fixes".
Click to expand...
Click to collapse
Sorry, I had to go out for lunch, so I didn't really go into much detail. I have tried using TWRP and is still using that atm, and also tried flashing a rom with GSM Patch, which I'll edit the OP to match. Both of these did not work and I'm going to try and pull a logcat or something. Will update when I get it

Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.

tehdef said:
Just got mine to flash. I noticed though that for whatever reason my current 1.85 had an _r2 at the end, and the one I'm flashing does not. Curious if ATT network is rejecting due to the RUU version.
Guess we will find out when it's done.
Edit: Nope, nada... Same issue.
Curious though why none of my contacts sync. seems like this is a contacts issue for me.
Click to expand...
Click to collapse
i feel like the dialer and the contacts are linked together. if we can solve one, we can probably solve both. I looked in my catlog and they stated that they couldnt find a particular file/db in the /data/data folder. ill look into this and see what happens

Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X

Well, hopefully that's it.
---------- Post added at 01:12 PM ---------- Previous post was at 01:06 PM ----------
kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
I haven't unlocked my BL again because I'm at home, and frankly, I'm not sure how the process is changed once I already ahve the Auth Key, and if I can do it quickly here from work.

kleeman7 said:
Did either of you try flashing a different rom like xi40, or sick sense, and do a system, cache, dalvik, factory reset, wipe from twrp before you flash a rom, and see how that goes
Sent from my HTC One X
Click to expand...
Click to collapse
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything

jojojohnson7410 said:
lol actually, i just came from Cobra ROM and yeah I cleared everything and flashed, but to no avail. I can always try again, but time's running out and I don't think it's going to work since Ive done it over 15 times in order to try everything
Click to expand...
Click to collapse
Try flashing AOKP + GApps to see if the People vs Contact system is diff?

tehdef said:
Try flashing AOKP + GApps to see if the People vs Contact system is diff?
Click to expand...
Click to collapse
That's a good idea, maybe once Scott reads his thread he will have some input for everyone.
Sent from my HTC One X

Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
...actually, tehdef, did you ever unlock your bootloader with the one-click without HTCDEV unlock at any point in time? This might help me out cause this might also be the problem. Thanks!

jojojohnson7410 said:
Found an interesting read in another forum, which would confirm what error I saw in the logcat:
http://forum.xda-developers.com/showpost.php?p=20892463&postcount=15
http://forum.xda-developers.com/showpost.php?p=27115182&postcount=16
tehdef, try these two for me and see where you get. I'm trying to get my phone into another rom so I can try this out cause 1.85 won't let me root (the problem we have specifically screws up that exploit, go figure!) so let me know how it works. I'll be trying it in a bit so i'll update back when i test it out
Click to expand...
Click to collapse
Clearing contacts seems to work. My list is now populating.
Attempted to send text. Prepairing SIM Card returns.
---------- Post added at 02:23 PM ---------- Previous post was at 02:12 PM ----------
Unfortunately the Android.acore process has stopped when I tried to sync my Gmail contacts after clearing everything.

I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?

Something is corrupt.
I want to put AOKP back on the phone, because I honestly think it's Sense related.

natediddydude said:
I'm having the exact same issues. I've usually been able to figure out all my own screw ups but just not this time. I too flashed cleanrom 4.1 using cwm because i failed at reading the directions. Got stuck at recovery and was able to install a 1.85 ruu and them proceeded to put twrp on it and flash cleanrom 4.1. Everything seemed fine but then i noticed that my xfinity email would open and and then quickly close. Didn't think much of it, but then i realized that also the phone and contacts do the same thing. I've tried everything but holy water to get this fixed including trying other roms, fixing permissions in recovery, clearing phone and contacts data, deleting db.journal file, and shaking the phone really hard....
Any ideas?
Click to expand...
Click to collapse
lol at the shaking your phone really hard XD
Anyways, I have a theory:
there are two ways we COULD possibly fix this:
1. obtain a rom that has root. Get root explorer or somehow get into /data/data/com.android.providers.contacts/databases/ and delete .db-journal if its in there. Do this in conjunction with clearing out the data of all the affected apps and their sister apps (i.e. Contacts, Contacts Storage, Contacts Sync) and force stopping all of them. Can't test this cause bootloader refuses to unlock atm)
2.lock the bootloader, RUU to 1.82 (NOTE: NOT 1.85!) and try to unlock using this: http://forum.xda-developers.com/showthread.php?t=1734558. REMEMBER take out your SIM card! but maybe this might help not 100% sure if this is what caused it for me, so it's best to consider it too. Can't test this right now because I am stuck without a BL unlock and i can't get root on this firmware
*EDIT* ahahhahahah i lied. no sim card needed, so why would it rely on mobile data? ahh im such a silly person alright here goes!
i'll let you know when i get out of my pickle, but it might be a while. That, or i might just get pissed off enough to just go to the store and look like an idiot cause i really do feel like one right now and I need to get the phone working T_T
Keep checking back!

[Q] Moto G (XT1031) cannot make/receive calls or text after flashing

I am a noob here. I am experiencing two main issues with a Boost Moto G (XT1031) that I am trying to flash to PP. It came with KK version 4.4.2. After I unlocked the bootloader and followed all the steps described on http://forum.xda-developers.com/showthread.php?t=2681166 to reset SPC to 000000, I flashed the stock US verizon firmware on it.
Problem-1:
The phone rebooted fine and even got upgraded to 4.4.4 over wifi. Even though the phone is showing that it is on verizon network (strong signal) and everything seems to be fine at the PP end, I cannot make or receive text or calls. I am totally lost. Any help will be appreciated.
Everything went fine till I flashed the CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip firmware. It gave me errors when I loaded the boot.img, recovery.img, mfastboot flash system system.img_sparsechunk1 and mfastboot flash system system.img_sparsechunk4. I followed the instructions for flashing 4.4.2. They were different errors and I was manually entering each command line (copy-pasted). I also checked the file names in the folder and they matched. I couldn't figure out why I was getting the error. The MD5 matched too, so that rules out the fact that the files were corrupted. After reboot, the system loaded up ok, but the OTA failed. I used the manual programming and *22890 to get it activated. I got the "congratulations, your device is active" message. However, any time I tried to make a call, I get the error saying, "your phone# is either not active or invalid". I called PP and they confirmed the MEID on my phone and the one in their system are the same and nothing is wrong at their end. They were even able to make a call from this number. One of the dealers at Kittywireless told me that it might be an issue with the authentication key. I saw no mention about this in the tutorial or in any of my searches on this forum. What am I doing wrong? Any help will be appreciated.
Problem-2:
Also my phone is an 8GB phone (shows that info on the fastboot menu on the phone & also in the bug report (attached)), but in the storage info section of the phone it is showing only 5.52 Gb as the total internal storage. When I flashed the phone, I also erased the userdata. Any safe way to wipe the phone and load up everything? How do I get back the lost space?
I am attaching a bug report that I generated using ADB tool. It seemed really long for a phone that was just activated. I am hoping that someone on this forum might have encountered the problems that I mentioned above before and figured out a way to fix them. I'd appreciate if you can share it. Thanks.

greenlantern2014 said:
I am a noob here. I am experiencing two main issues with a Boost Moto G (XT1031) that I am trying to flash to PP. It came with KK version 4.4.2. After I unlocked the bootloader and followed all the steps described on http://forum.xda-developers.com/showthread.php?t=2681166 to reset SPC to 000000, I flashed the stock US verizon firmware on it.
Problem-1:
The phone rebooted fine and even got upgraded to 4.4.4 over wifi. Even though the phone is showing that it is on verizon network (strong signal) and everything seems to be fine at the PP end, I cannot make or receive text or calls. I am totally lost. Any help will be appreciated.
Everything went fine till I flashed the CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip firmware. It gave me errors when I loaded the boot.img, recovery.img, mfastboot flash system system.img_sparsechunk1 and mfastboot flash system system.img_sparsechunk4. I followed the instructions for flashing 4.4.2. They were different errors and I was manually entering each command line (copy-pasted). I also checked the file names in the folder and they matched. I couldn't figure out why I was getting the error. The MD5 matched too, so that rules out the fact that the files were corrupted. After reboot, the system loaded up ok, but the OTA failed. I used the manual programming and *22890 to get it activated. I got the "congratulations, your device is active" message. However, any time I tried to make a call, I get the error saying, "your phone# is either not active or invalid". I called PP and they confirmed the MEID on my phone and the one in their system are the same and nothing is wrong at their end. They were even able to make a call from this number. One of the dealers at Kittywireless told me that it might be an issue with the authentication key. I saw no mention about this in the tutorial or in any of my searches on this forum. What am I doing wrong? Any help will be appreciated.
Problem-2:
Also my phone is an 8GB phone (shows that info on the fastboot menu on the phone & also in the bug report (attached)), but in the storage info section of the phone it is showing only 5.52 Gb as the total internal storage. When I flashed the phone, I also erased the userdata. Any safe way to wipe the phone and load up everything? How do I get back the lost space?
I am attaching a bug report that I generated using ADB tool. It seemed really long for a phone that was just activated. I am hoping that someone on this forum might have encountered the problems that I mentioned above before and figured out a way to fix them. I'd appreciate if you can share it. Thanks.
Click to expand...
Click to collapse
try flashing stock rom

com.android.phone has stopped; how to deal with this?

Hi everybody,
2 day ago, I got an error message on my Opo: "com.android.phone has stopped" and ever since it has been popping up every minute or so, or sometimes every 10 seconds when I'm on my phone. The most annoying thing is that sometimes when I get that error message I also loose my network, so I can't make any phonecalls/use my 3G.
I was looking at the Crash Report and I saw this message:
"[crash] com.android.mms.service threw java.lang.NullPointerException"
I remember the first time this error happened was when I was writing a message and suddenly the interface was stuttering and everything was going very slow. Rebooted and then I started getting those errors
I followed some instructions found here, on Opo forums and on android central:
1) go to apps and clear the cache/data from phone, sim-toolkit, messaging and messaging service and reboot
2) perform a soft reset (via the phone)
3) perform a hard reset (factory reset via the recovery menu)
4) install custom recovery, enable root and reflash the rom
None of these solved the problem. But I also don't have the feeling that a hard reset
Moreover, after a reset, I still see folders from apps I had before the reset. Including pictures in my picture folder that I had downloaded prior to the factory reset. This doesn't seem like a factory reset to me, is there any way to wipe everything clean?
*edit*
This is the log of the error report that I get:
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
*edit2*
When I had the error my settings were:
ROM: Cyanogen 12.0-YNG1TAS0YL
Kernel: 3.4.67-cyanogenmod-g1cbb9b0 build04cyanogenmod #1
No custom recovery
I've trying to fix the error, installing custom recovery, enabling root mode and reflashing the official cyanongen 12 rom. Still the problem persisted.
ROM: Cyanogen 12.0-YNG1TAS0YL
Kernel: 3.4.67-cyanogenmod-g1cbb9b0 build04cyanogenmod #1
Twrp recovery

ElGargamel said:
Hi everybody,
2 day ago, I got an error message on my Opo: "com.android.phone has stopped" and ever since it has been popping up every minute or so, or sometimes........
Click to expand...
Click to collapse
You forgot to provide details (ROM, Kernel, recovery, mods, etc.)
java.lang.NullPointerException usually means that the code calls for some value and it is not available.

davebugyi said:
You forgot to provide details (ROM, Kernel, recovery, mods, etc.)
java.lang.NullPointerException usually means that the code calls for some value and it is not available.
Click to expand...
Click to collapse
Sorry, I added details in the initial post under "edit2". In short, I started having the error with the Stock rom/recovery. Didn't fiddle with anything. Out of frustration I decided to install twrp, enable root and reflash the rom. Didn't work, problem happened again as soon as I booted up my phone. I feel it has to do something with the sim-toolkit? As soon as it access the network it starting to nuke the error, then loses network, then regains network, especially when I'm trying to write a message. In airplane mode it doesn't happen.

ElGargamel said:
Sorry, I added details in the initial post under "edit2". In short, I started having the error with the Stock rom/recovery. Didn't fiddle with anything. Out of frustration I decided to install twrp, enable root and reflash the rom. Didn't work, problem happened again as soon as I booted up my phone. I feel it has to do something with the sim-toolkit? As soon as it access the network it starting to nuke the error, then loses network, then regains network, especially when I'm trying to write a message. In airplane mode it doesn't happen.
Click to expand...
Click to collapse
It can be that or modem issue or something got corrupted on the /data partition.

davebugyi said:
It can be that or modem issue or something got corrupted on the /data partition.
Click to expand...
Click to collapse
Any way I can fix this from within twrp? How do I figure out what is exactly corrupted?

ElGargamel said:
Any way I can fix this from within twrp? How do I figure out what is exactly corrupted?
Click to expand...
Click to collapse
Trial and error. The easiest way is to wipe your device clean (system, cache, dalvik and data - storage not needed) and flash the ROM again. Also try to flash the latest available.

davebugyi said:
Trial and error. The easiest way is to wipe your device clean (system, cache, dalvik and data - storage not needed) and flash the ROM again. Also try to flash the latest available. [/URL]
Click to expand...
Click to collapse
Didn't work. Still get nuked by the error. I decided to flash OxygenOS (after system, cache, dalvik and data wipe). Now I don't have the error anymore, luckily.
But I still have problems with texting. I can receive texts from friends, but not from my girlfriend who has an iPhone. She can receive my texts and my MMS, but I don't receive anything from her. The problem is partly solved, but not completely. I feel it's still somewhat related to the original problem.

ElGargamel said:
Didn't work. Still get nuked by the error. I decided to flash OxygenOS (after system, cache, dalvik and data wipe). Now I don't have the error anymore, luckily.
But I still have problems with texting. I can receive texts from friends, but not from my girlfriend who has an iPhone. She can receive my texts and my MMS, but I don't receive anything from her. The problem is partly solved, but not completely. I feel it's still somewhat related to the original problem.
Click to expand...
Click to collapse
Well, then it must hardware related or problem with your carrier.

Flash a custom rom
Sent from my A0001 using Tapatalk