Troubles after rooting - Verizon Samsung Galaxy S III

Hello!
While im not entirely new to rooting and can typically find an answer myself, i have found myself in a predicament that i cannot seem to get out of. When i was on the latest build for AOKP and CM 10.1 my phone would sometimes say i had an unknown number or omething along the lines of 000-000-0016. same with the imei and mei. i fixed the imei and mei using this guide rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/ but for whatever reason i cant send messages now or make phone calls.....even when i reverted back to a stock ICS rom using odin 3.07.... i tried updating my phone but still no luck. as soon as i send a message, it says it fails to send. I tried wiping the cache, dalvik cache, data, and factory resetting it. i need input

Related

[Q] No SMS on Roms other than Stock GB

Greetings, all. Long time reader, first time posting.
I had recently flashed the HFS and EB ICS roms, and both were running without issue. Then, out of the blue, I stopped receiving SMS. I could still send, but could not receive. I had read on the HFS thread that a few others had experienced this issue. After searching various threads and forums, I couldn't find a solution. After a re-flash of both HFS and EB didn’t fix the problem on either, I flashed a couple of GB roms, and was still unable to receive SMS. Finally, I restored back to Stock GB and SMS worked fine.
I am sometimes able to receive SMS on ICS when WIFI Calling is active, but it is inconsistent.
I’ve tried the following to remedy this issue, with no success:
CWM>Wipe Data, Cache, and Dalvik, Flash rom and Gapps.
CWM>Wipe Data, Cache, and Dalvik, Format Data, System, and Cache, Flash rom and Gapps.
Same steps as above, but with G2x Scrubber (sometimes scrubbing twice) thrown into the mix.
Re-downloading roms, in case of file corruption.
Fixing permissions before and after first boot.
Master reset before and after first boot.
GetRIL.
SMSC Update.
APN delete, restore, manually enter, etc.
Tried multiple SMS apps (Stock, GO, Handcent).
Flashing Gapps after first boot.
Skipping Google account setup on first boot.
I followed all rom installation instructions, including waiting ten minutes before touching the phone after first boot.
I suppose the only thing I haven’t tried is flashing a different Kernel after flashing the rom. My only other thought is to flash the Stock recovery, then re-flash CWM and try it all again.
If anyone has any suggestions, your assistance would be greatly appreciated.
Battery pull?
iArtisan said:
Battery pull?
Click to expand...
Click to collapse
If only it were that simple; but, no, I tried that as well.
Unfortunately I don't have anything to add other than I'm having the same issue with ICS and CM7 roms. I can receive SMS on MIUI and Bionix and have gone through the same troubleshooting steps. I'll add that I've tried a different SIM as well...no dice.
I saw someone post on another thread that they resolved this issue through T-mobile customer support, but I'm skeptical.
EDIT: Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
akelty said:
Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
Click to expand...
Click to collapse
Thanks. After reading that, I didn't bother trying. I'm happy to say I did a warranty excahnge and ICS is running beautifully on my new G2x, though I still wish I could've figured out what the issue was with the last one. Thanks again for your response and trying out that fix.
If anybody's still following this thread I found a solution for GB roms that cannot receive SMS. I had trouble with EaglesBlood and tried flashing the Trinity kernel...viola! Getting all my texts now.

[Q] NFC issue, tried everything.

The usually story, while flashing my NFC somehow managed to disappear, so I went back and flashed to ICS stock and it hasn't allowed me to turn it on either, did a complete lock and flashed complete stock, I have factory reset, wiped, flashed and re-flashed. Any sort of ideas? Anything would help seeing as this has been keeping me up and I feel like I have tried almost every fix NFC related.
Mexi7 said:
The usually story, while flashing my NFC somehow managed to disappear, so I went back and flashed to ICS stock and it hasn't allowed me to turn it on either, did a complete lock and flashed complete stock, I have factory reset, wiped, flashed and re-flashed. Any sort of ideas? Anything would help seeing as this has been keeping me up and I feel like I have tried almost every fix NFC related.
Click to expand...
Click to collapse
Have you tried reprovisioning? As far as I know most people use it to restore service after a bad flash that didn't wipe their IMEI but for some reason it still won't connect to the network. The only reason I bring it up is because that's not its only use, while using Odin to go back to stock works this is supposed to wipe everything and reset everything, not just data but the whole damn phone. I would just give it a try since you've done everything else. Like I said above. Its mainly used for getting data back when your IMEI isn't lost but it does way more than that. It sounds like faulty hardware but this can't hurt to try.
To reprovision you need to be on stock TW and then you need to dial*2767*3855# . Just note that this will wipe everything so get everything off your internal SD you wanna keep.
Sent from one of the many Anthropomorphic Personalities of the Disc

[Q] Problem with rom

I have recently installed DhdSation Rom v3.1 on my dhd. i found a problem that the touchwiz launcher in it get crash when you open call logs and even when you open messages and sometimes the back button gets hanged. Once i was operating my cell and got a call frrom someone, instead of showing me who it is calling my phone just was vibrating and than the call cutted.
waiting for ur reply thank you
vikramsoni01 said:
I have recently installed DhdSation Rom v3.1 on my dhd. i found a problem that the touchwiz launcher in it get crash when you open call logs and even when you open messages and sometimes the back button gets hanged. Once i was operating my cell and got a call frrom someone, instead of showing me who it is calling my phone just was vibrating and than the call cutted.
waiting for ur reply thank you
Click to expand...
Click to collapse
I have not seen any other users with the same issue. It seems very possible that something went wrong during the install. First of all, verify the MD5SUM of the ROM you downloaded to make sure it is not corrupt. If it is, redownload it, then wipe and reflash.
Did you wipe data & system before installing the ROM? While you do not need to wipe the sdcard portion of data, everything else needs to wiped when changing ROMS or major Android versions. Make sure you did this, if not try reflashing after a proper wipe.
Have you flashed anything else after the wipe, such as a kernel? If so try wiping then reflashing the ROM without anything extra.
Jedakiah said:
I have not seen any other users with the same issue. It seems very possible that something went wrong during the install. First of all, verify the MD5SUM of the ROM you downloaded to make sure it is not corrupt. If it is, redownload it, then wipe and reflash.
Did you wipe data & system before installing the ROM? While you do not need to wipe the sdcard portion of data, everything else needs to wiped when changing ROMS or major Android versions. Make sure you did this, if not try reflashing after a proper wipe.
Have you flashed anything else after the wipe, such as a kernel? If so try wiping then reflashing the ROM without anything extra.
Click to expand...
Click to collapse
During my installation nothing went wrong and yes i wiped my data before installing this rom. I haven't flashed anything after that.
I will try and reflashing again thanks
Please verify md5sum of file u installed.
Sent from my GT-I9100G using xda premium
vikramsoni01 said:
During my installation nothing went wrong and yes i wiped my data before installing this rom. I haven't flashed anything after that.
I will try and reflashing again thanks
Click to expand...
Click to collapse
While you might not have seen an error message, something could have still gone wrong. As a programmer myself, I can attest that it is impossible to detect every error. A zany example: solar flares can cause errors, corrupt data, and even crash applications in spectacular ways.
Definitely start with the MD5 check as that is a fairly common issue. Just today I had one fail to match up. If it matches, reflash, if not redownload then reflash.
Jedakiah said:
While you might not have seen an error message, something could have still gone wrong. As a programmer myself, I can attest that it is impossible to detect every error. A zany example: solar flares can cause errors, corrupt data, and even crash applications in spectacular ways.
Definitely start with the MD5 check as that is a fairly common issue. Just today I had one fail to match up. If it matches, reflash, if not redownload then reflash.
Click to expand...
Click to collapse
Thanks mate for your help.
i have solved the problem.

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

[HELP] Phone keeps rebooting, factory reset and odin flash fail

Hi,
My sister has a GT-P3100, since last week the phone keeps rebooting randomly after 3 - 5 minutes most often there are also an error message about Google Play Services or other services has stopped. The phone has Samsung stock Android 4.1.2 XSE and this is the latest firmware as per Samsung website. No root nor custom firmware.
I noticed something weird also, any change made to the settings or apps are reverted back upon reboot. For example, if I set up a WiFi setting, the setting will be gone after reboot. The phone has a number of unread SMS messages too, if I read these messages all of them will become unread again after reboot.
I tried to do factory reset from within the Android setting, it did not work . Everything still intact after reboot.
I tried to do factory reset from Recovery mode, it did not work too. Nothing gets wiped out.
I tried to flash the same firmware using Odin, the NAND write was going on till about 50-55% then it failed. When I rebooted the phone after this failed flash, the phone still has everything intact. No change at all as far as I can see.
Could somebody please help to fix this issue?
dvn2008 said:
Hi,
My sister has a GT-P3100, since last week the phone keeps rebooting randomly after 3 - 5 minutes most often there are also an error message about Google Play Services or other services has stopped. The phone has Samsung stock Android 4.1.2 XSE and this is the latest firmware as per Samsung website. No root nor custom firmware.
I noticed something weird also, any change made to the settings or apps are reverted back upon reboot. For example, if I set up a WiFi setting, the setting will be gone after reboot. The phone has a number of unread SMS messages too, if I read these messages all of them will become unread again after reboot.
I tried to do factory reset from within the Android setting, it did not work . Everything still intact after reboot.
I tried to do factory reset from Recovery mode, it did not work too. Nothing gets wiped out.
I tried to flash the same firmware using Odin, the NAND write was going on till about 50-55% then it failed. When I rebooted the phone after this failed flash, the phone still has everything intact. No change at all as far as I can see.
Could somebody please help to fix this issue?
Click to expand...
Click to collapse
Symptoms are of the emmc card bug. Will need hardware intervention. No flashing files will solve this. Get it to the repair shop, they will either replace the motherboard or will get a replacement of the emmc chip.
This is the reason no samsung tab 2 series is safe if they are on a stock rom.
I feel they have better chance on custom rom as with newer roms, this bug doesn't create a problem.
billysam said:
Symptoms are of the emmc card bug. Will need hardware intervention. No flashing files will solve this. Get it to the repair shop, they will either replace the motherboard or will get a replacement of the emmc chip.
This is the reason no samsung tab 2 series is safe if they are on a stock rom.
I feel they have better chance on custom rom as with newer roms, this bug doesn't create a problem.
Click to expand...
Click to collapse
tough luck, the warranty is no more
I had Samsung Galaxy Note 2 that bricked due to emmc bug too.. I did not know this bug affected other Samsung phones/tablets
If I managed to get the emmc chip replaced, will the bug reoccurs?
Thanks for the info

Categories

Resources