SMS (text) problem on ATTS3 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I have an ATT Galaxy S3, running cyanogenmod 10.0 (10.0.0-datt), installed via clockworkmod recovery (ROM Manager). Everything works beautifully except that I can neither send nor receive text messages.
Now before you yell at me, yes, I checked the other threads, and I'm aware of the wiki entry over at cyanogenmod's site (can't post the URL on account of newness). I did try to update the SMSC number. I get update errors with the bare number and the PDU number. The only option that appears to work is to use the standard ATT smsc number in quotes. That doesn't yield an update error, but on refresh, I see "+13123149810",145 . I have no idea where the trailing comma and 145 come from. They just show up. Don't know if it means anything.
Anyway, I have also tried various combinations of removing the SIM/rebooting etc, though I have not yet tried a full reset. I have also checked the APN stuff, and it appears sound.
Here is another wrinkle. I did at one time run a CM nightly to 4.2, so I have that '0' directory on my SDCard. I haven't observed it to cause a problem otherwise, but...
So the symptom is that if I send a text, it appears to send but never arrives at the receiver's phone. If I send an MMS, it flat refuses to send, saying the service is not activated on the network, which is odd since I have an unlimited plan.
I'm now at a loss, but I don't want to go back to stock, or to do another full reset. Any ideas?

I've run cm10 for a bit it was whatever, but I've never run into these issues your having and I use cwm too. The only thing I can think of right now is maybe something to do with rom manager its just a crappy app its buggy and always gave me problems so I never ever use it! Try downloading it directly from cm and wipe everything and flash again
Sent from my SGH-I747M using xda premium

thatsupnow said:
I've run cm10 for a bit it was whatever, but I've never run into these issues your having and I use cwm too. The only thing I can think of right now is maybe something to do with rom manager its just a crappy app its buggy and always gave me problems so I never ever use it! Try downloading it directly from cm and wipe everything and flash again
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Well I tried the full deal again. I booted to CWM Recovery and did the wipe/reset, then loaded, respectively, CM10 and GApps. I did not load everything back on the phone or otherwise restore data. No themed Messenger. Still the same deal. Text messages go nowhere and I get 'service not activated on network' for MMS. No difference.
Do I need to get a new SIM? Would that help? Is there a way to debug what's happening when I try to send a text? I have ADB and the whole SDK and am reasonably comfortable at the command line. I just don't have the standard XDA tribal knowledge.

jgoodleaf said:
Do I need to get a new SIM?
Click to expand...
Click to collapse
No, that won't really do you any good, UNLESS your sim wasn't provided with the device when you got it.
I would say to ODIN back to Stock, and see if things change back to what they should be. While in stock go ahead and remove that pesky folder you found.
Again see if that changes things.
If things have returned to normal, make your nandroid and then reflash the ROM you were using and see if things are still the same or if you have the ability to send again. If still the same then it's an issue with the ROM, probably in the APN.

MasterDecker said:
No, that won't really do you any good, UNLESS your sim wasn't provided with the device when you got it.
I would say to ODIN back to Stock, and see if things change back to what they should be. While in stock go ahead and remove that pesky folder you found.
Again see if that changes things.
If things have returned to normal, make your nandroid and then reflash the ROM you were using and see if things are still the same or if you have the ability to send again. If still the same then it's an issue with the ROM, probably in the APN.
Click to expand...
Click to collapse
I think I'd have tried ODIN by now, thinking along the same lines, except that I don't have any Windows machines in the house, or any immediate access. I have VMWare, but don't trust that where flashing is concerned. I've been trying to figure out if I could use Heimdall, but that looks like a non-starter at the moment. Maybe I'll have to see if I can borrow someone's Windows computer... And just when I thought I was rid of it.

Related

[Q] Can't receive incoming SMS on my rooted Evo 4g

I just rooted my evo 4g using Revolutionary and now I can't receive text messages. I flashed Cyanogenmod 7.0.3.1 and it works great except for the lack of incoming SMS. Outgoing works fine. I restored back to my rooted stock ROM and am not able to receive SMS there either. Any Ideas?
Thanks!
If you're back on the stock ROM (or any Sense ROM), try updating your profile (Settings->System Update). That seems to help some people with the same problem.
scracker16 said:
I just rooted my evo 4g using Revolutionary and now I can't receive text messages. I flashed Cyanogenmod 7.0.3.1 and it works great except for the lack of incoming SMS. Outgoing works fine. I restored back to my rooted stock ROM and am not able to receive SMS there either. Any Ideas?
Thanks!
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice?
Tried it a couple of times... No luck. Sent one usin a web text service and this is the notification I received to my email account that sent it. Maybe it will help.
"myphone#"@messaging.sprintpcs.com
SMTP error from remote mail server after initial connection:
host mx.messaging.sprintpcs.com [68.28.217.6]:
554 lnxipc006-in.nmcc.sprintspectrum.com
Any other suggestions?
jesuspgt said:
Do you have your phone number integrated with Google Voice?
Click to expand...
Click to collapse
Not integrated with Google Voice...
Error 554 means the server rejected the message for some reason. Is there more of the error message you can provide (such as "Service Unavailable", etc)?
I Googled it as it relates to Sprint and saw that it could mean the server was too busy or the message was rejected because the provider (the web text service or your mail server) is on a watchlist. I was able to send one to my phone number @messaging.sprintpcs.com with no issues, using my Gmail account. Windows Live users have supposdly had this problem often.
There could be a temporary outage wherever you are -- but the only other thing you can try is "restoring" your profile.
Dial ##3282# from your phone, go to Edit Mode, put in your MSL (get it using MSL Reader from the Market if you don't already have the MSL), then click "Data Profile". Hit your Menu button and then select "Restore". It will do a few other things like update your PRL if needed, and then try to update the software. After that finishes, reboot and try again.
scracker16 said:
Tried it a couple of times... No luck. Sent one usin a web text service and this is the notification I received to my email account that sent it. Maybe it will help.
"myphone#"@messaging.sprintpcs.com
SMTP error from remote mail server after initial connection:
host mx.messaging.sprintpcs.com [68.28.217.6]:
554 lnxipc006-in.nmcc.sprintspectrum.com
Any other suggestions?
Click to expand...
Click to collapse
I did the data restore process at least three times with no luck...
I appreciate the help, thanks.
This is the entire e-mail notification...
"A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
SMTP error from remote mail server after initial connection:
host mx.messaging.sprintpcs.com [68.28.217.6]:
554 lnxipc006-in.nmcc.sprintspectrum.com
------ This is a copy of the message, including all the headers. ------
Return-path: <[email protected]>
Received: from nobody by web1.escalatemedia.com with local (Exim 4.69)
(envelope-from <[email protected]>)
id 1Qu8EA-00030d-89
for [email protected]; Thu, 18 Aug 2011 12:26:06 -0700
To: Some Recipient <[email protected]>
Subject: Sent From SprintUsers.com
From: Some Sender <[email protected]>
Date: Thu, 18 Aug 2011 12:26:05 -0700
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <[email protected]>"
Did you find a solution yet? I just helped my friend flash CM on his Evo and he's having the same problem.
Solved
I ran into this problem and was made aware that I wasn't receiving texts just last night after 3 days of friends thinking I was an ass. Anyway, after a ton of attempts I was finally able to solve the problem. Here's what I did:
1. Create a backup of your current rom using clockwork recovery (there's nothing wrong with it so if it's customized the way you want everything minus the SMS bug, you can still have it... this worked for me).
2. Download the 2.2 Froyo stock Ruu: RUU_Supersonic_S_Sprint_WWE_3.7.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe
3. Run the RUU yes, this un-roots your phone, but it kicks it back to Froyo 2.2 which is WAY more stable with the current Cyanogenmod rom.
4. Download Unrevoked 3 flash recovery & run to re-root your froyo HTC Evo, make sure you're patient because it will reboot your phone a couple times.
5. You now have a rooted, stock Evo running 2.2 with fully working SMS, just kick back into recovery mode and load up your original rom (the Cyanogenmod 7 that didn't have working SMS) and everything should work fine. I had a big flood of text messages show up so heads up on that.
It's a little time consuming, but I now have Cyanogenmod 7 running 2.3.3 on my phone with everything working fine now (as far as I can tell). Hope this helps!
BTW I didn't know if I was allowed to post links to the actual files, so just google them... they aren't too difficult to find.
sneakily1 said:
I ran into this problem and was made aware that I wasn't receiving texts just last night after 3 days of friends thinking I was an ass. Anyway, after a ton of attempts I was finally able to solve the problem. Here's what I did:
1. Create a backup of your current rom using clockwork recovery (there's nothing wrong with it so if it's customized the way you want everything minus the SMS bug, you can still have it... this worked for me).
2. Download the 2.2 Froyo stock Ruu: RUU_Supersonic_S_Sprint_WWE_3.7.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe
3. Run the RUU yes, this un-roots your phone, but it kicks it back to Froyo 2.2 which is WAY more stable with the current Cyanogenmod rom.
4. Download Unrevoked 3 flash recovery & run to re-root your froyo HTC Evo, make sure you're patient because it will reboot your phone a couple times.
5. You now have a rooted, stock Evo running 2.2 with fully working SMS, just kick back into recovery mode and load up your original rom (the Cyanogenmod 7 that didn't have working SMS) and everything should work fine. I had a big flood of text messages show up so heads up on that.
It's a little time consuming, but I now have Cyanogenmod 7 running 2.3.3 on my phone with everything working fine now (as far as I can tell). Hope this helps!
BTW I didn't know if I was allowed to post links to the actual files, so just google them... they aren't too difficult to find.
Click to expand...
Click to collapse
I could use a link to that stock froyo rom. The only results I get from Google lead me to rooted versions on xda. Thanks for all your help! Ready to fix this issue!
It won't let me post the link because I'm a n00b on this forum. Google search "unroot gingerbread evo" (minus quotes) and look for htcevohacks link and it's on step #4. That's where I snagged it from.
Found The RUU
Fixed the problem on the first try, now to root again!
Thanks for all the help!
Thanks for posting the problem... it made me bust ass to figure out a solution when I ran into the same issue. Glad I could help.
Here is a quick fix. Worked for me instantly.
http://www.evo4gforum.net/htc-evo-4g-general-discussion/sms-issue/
Same thing, but...
Ok... I know, I know, I am a noob. I have searched on xda, androidforums and just plain ol googled it and this seems to be the closest to what I need to do.
I have an HTC Evo 4g, sprint originally but it is flashed to Cricket. it was originally rooted and (flashed?) to CM 7 (not sure which 7.____) supersonic. I downloaded gosms and handcent while looking for something to type Emoji into a certain app I use. They weren't what I wanted so I uninstalled them and got Emoji Keyboard which was closer to what I wanted.
If it wasn't that, I did go into my file manager and on the SDcard only I deleted what appeared to be empty folders. the previous owner didn't wipe the sdcard when he sold me the phone, so I had a lot of app folders I don't use. I did not delete anything that said mms, sms, or anything outside of the SD card!
My phone has not received any sms for over a week and I use the phone for work, I am missing important texts from clients and friends and it's extremely annoying.
ok so I took it to the guy who flashed Cricket to it (the guy who rooted it is out of town) and he said it must have been deleted or overwritten somehow. He put another ROM on it - CM 9 - Deck - running ICS now. That did not fix the problem as I guess it must be in the basic application folder. so my question:
Since this was able to work for CM7, will it work for CM9 also?
I don't have google voice other than whatever came on the phone (or this version of CM9) and when I went to google voice website it said my carrier couldn't do the port. I was gonna see if getting google voice and then uninstalling it would work. so I disabled the google voice application but I'm not sure if that will mess with any other apps... didn't do anything with my problem.
I uninstalled the gosms and the handcent, but they still have folders on the SDcard visible at least.
I went to file manager and in the system/apps/mms.apk I reinstalled that but no visible difference. rebooted and now I have written this post.
also I do not have a backup of the original HTC Sense, or a backup of the CM7 I originally installed... I have a .exe of the CM9 I currently have.
I'm sorry to ramble. please help! I'm sick of searching through threads! :crying:
- Amber
Thanks for the help!!
sneakily1 said:
I ran into this problem and was made aware that I wasn't receiving texts just last night after 3 days of friends thinking I was an ass. Anyway, after a ton of attempts I was finally able to solve the problem. Here's what I did:
1. Create a backup of your current rom using clockwork recovery (there's nothing wrong with it so if it's customized the way you want everything minus the SMS bug, you can still have it... this worked for me).
2. Download the 2.2 Froyo stock Ruu: RUU_Supersonic_S_Sprint_WWE_3.7.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe
3. Run the RUU yes, this un-roots your phone, but it kicks it back to Froyo 2.2 which is WAY more stable with the current Cyanogenmod rom.
4. Download Unrevoked 3 flash recovery & run to re-root your froyo HTC Evo, make sure you're patient because it will reboot your phone a couple times.
5. You now have a rooted, stock Evo running 2.2 with fully working SMS, just kick back into recovery mode and load up your original rom (the Cyanogenmod 7 that didn't have working SMS) and everything should work fine. I had a big flood of text messages show up so heads up on that.
It's a little time consuming, but I now have Cyanogenmod 7 running 2.3.3 on my phone with everything working fine now (as far as I can tell). Hope this helps!
BTW I didn't know if I was allowed to post links to the actual files, so just google them... they aren't too difficult to find.
Click to expand...
Click to collapse
xDisso1vex said:
Ok... I know, I know, I am a noob. I have searched on xda, androidforums and just plain ol googled it and this seems to be the closest to what I need to do.
I have an HTC Evo 4g, sprint originally but it is flashed to Cricket. it was originally rooted and (flashed?) to CM 7 (not sure which 7.____) supersonic. I downloaded gosms and handcent while looking for something to type Emoji into a certain app I use. They weren't what I wanted so I uninstalled them and got Emoji Keyboard which was closer to what I wanted.
If it wasn't that, I did go into my file manager and on the SDcard only I deleted what appeared to be empty folders. the previous owner didn't wipe the sdcard when he sold me the phone, so I had a lot of app folders I don't use. I did not delete anything that said mms, sms, or anything outside of the SD card!
My phone has not received any sms for over a week and I use the phone for work, I am missing important texts from clients and friends and it's extremely annoying.
ok so I took it to the guy who flashed Cricket to it (the guy who rooted it is out of town) and he said it must have been deleted or overwritten somehow. He put another ROM on it - CM 9 - Deck - running ICS now. That did not fix the problem as I guess it must be in the basic application folder. so my question:
Since this was able to work for CM7, will it work for CM9 also?
I don't have google voice other than whatever came on the phone (or this version of CM9) and when I went to google voice website it said my carrier couldn't do the port. I was gonna see if getting google voice and then uninstalling it would work. so I disabled the google voice application but I'm not sure if that will mess with any other apps... didn't do anything with my problem.
I uninstalled the gosms and the handcent, but they still have folders on the SDcard visible at least.
I went to file manager and in the system/apps/mms.apk I reinstalled that but no visible difference. rebooted and now I have written this post.
also I do not have a backup of the original HTC Sense, or a backup of the CM7 I originally installed... I have a .exe of the CM9 I currently have.
I'm sorry to ramble. please help! I'm sick of searching through threads! :crying:
- Amber
Thanks for the help!!
Click to expand...
Click to collapse
You could wipe the entire fat side of your sd card and it wouldn't affect sms or mms so deleting that stuff is not the problem. Messing around in your root directory is never a good idea if your not really comfortable with it. That may be the issue. Or the Cricket flash wasn't done correctly. If I were you I'd do a nand back up and start over. Flash a stock rooted rom and update the radios. See if that helps. You could try clearing your caches in recovery first too.

Random Shutoff after custom rom, now No messaging after flashing to stock.

Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.

I'm an impatient idiot and now I could really use some help.

Ok. So bare with me. I'm an impatient idiot and I'd like a little assistance if possible.
I flashed CM10.1 yesterday. It's groovy. However, the vibrate on every email issue is going to make me insane. I decided to flash Task650's AOKP today. However, it got funky and wasn't working properly, so I tried to go back to CM10.1. I had a nandroid backup, but CWM couldn't find it, and my computer (win7) could not browse the GS3 properly. I ended up wiping the phone and reflashing CM10.1. From there, I was able to use ROM MANAGER to find my nandroid backup and reflash back to my backup from before I tried the AOKP rom.
Now my issue. I tried to look in the clockworkmod folder for the backup, but it's not there, even though it was found via ROM Manager. Using ES File Explorer, I was able to find it in mnt/shell/emulated/clockworkmod. I can't, however, see how big the file is. Also, using Airdroid, when I navigate to the mnt/shell/, the folder is totally empty.
Yes yes, I know I need to be more patient. I am going to sit with CM10.1 for at least a week or two to see how I like it. I have a nandroid backup stored on my computer of my original stock set up in case I want to go back to that (which, I'm assuming, I'll have to copy back into mnt/shell/emulated/clockworkmod somehow).
On top of all that, for some reason, when I receive a text or phone call (or anything, for that matter, that is supposed to make sound), no sound comes out. I've checked all my settings, and when I go in to assign a sound, I can hear it, meaning the speakers are working. Any thoughts on that one?
Aaaand.. it also seems that, even with it disabled in the settings, the notification light blinks when I am receiving a call. This wasn't happening before I went and got all impatient on it...
I'm a disaster. I'm sorry.
Thank you for your help in advance!
EDIT: besides the location of the CWM folder, I figured everything else out. Seems that the profiles were not set up correctly.
slicetwo said:
Ok. So bare with me. I'm an impatient idiot and I'd like a little assistance if possible.
I flashed CM10.1 yesterday. It's groovy. However, the vibrate on every email issue is going to make me insane. I decided to flash Task650's AOKP today. However, it got funky and wasn't working properly, so I tried to go back to CM10.1. I had a nandroid backup, but CWM couldn't find it, and my computer (win7) could not browse the GS3 properly. I ended up wiping the phone and reflashing CM10.1. From there, I was able to use ROM MANAGER to find my nandroid backup and reflash back to my backup from before I tried the AOKP rom.
Now my issue. I tried to look in the clockworkmod folder for the backup, but it's not there, even though it was found via ROM Manager. Using ES File Explorer, I was able to find it in mnt/shell/emulated/clockworkmod. I can't, however, see how big the file is. Also, using Airdroid, when I navigate to the mnt/shell/, the folder is totally empty.
Yes yes, I know I need to be more patient. I am going to sit with CM10.1 for at least a week or two to see how I like it. I have a nandroid backup stored on my computer of my original stock set up in case I want to go back to that (which, I'm assuming, I'll have to copy back into mnt/shell/emulated/clockworkmod somehow).
On top of all that, for some reason, when I receive a text or phone call (or anything, for that matter, that is supposed to make sound), no sound comes out. I've checked all my settings, and when I go in to assign a sound, I can hear it, meaning the speakers are working. Any thoughts on that one?
Aaaand.. it also seems that, even with it disabled in the settings, the notification light blinks when I am receiving a call. This wasn't happening before I went and got all impatient on it...
I'm a disaster. I'm sorry.
Thank you for your help in advance!
EDIT: besides the location of the CWM folder, I figured everything else out. Seems that the profiles were not set up correctly.
Click to expand...
Click to collapse
Did the speakers work when you were on stock?
Yeah. I figured it out. It was the profiles I set up not being done correctly.

Need some help after bad rom install/reset

I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Rawt said:
I attempted my first rooting and install of darthstalkers rom last night. the step by step instructions were well laid out, and the process was pretty smooth. however after completing the rom install, and began getting various errors such as 'gallery not responding', 'omacp has stopped working',etc. over a dozen different errors in total. kies wouldnt connect to restore my settings,etc.
i decided to flash back to stock, and followed the instructions perfectly, which again were very easy. kies connected instantly on stock, and everything seemed ok. however im still getting the same errors as i was with the darthstalker rom. now i bought my s3 outright (its not part of any package), so i have no warranty issues, however my phone is completely hosed now. i cant send texts, cant view email, nothing. i'm honestly regretting ever doing this.
any help/tips/suggestions so that i can go back to the way i was? ive tried everything that my googlefu has led me to, and nothing has worked.
Click to expand...
Click to collapse
have you tried booting into stock recovery, wiping data and cache?
xBeerdroiDx said:
have you tried booting into stock recovery, wiping data and cache?
Click to expand...
Click to collapse
I did it last night, but in my tired confusion, i may have fudged it up. going to do it now and ill update in a few minutes. Thanks for the help thus far.
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
hednik said:
when flashing to stock through Odin you retain the same cache and therefore you can have some issues of force closes..which is why a factory reset is always best....and mandatory when going from 4.1.1 to 4.0.4
That's a very stable ROM and I'm surprised at the issues you had. I have a feeling it wasn't the ROM or anything you did persay but bad flashes happen which it why most of us have a nandroid to fall back on just in case. Sometimes a re-flash does the trick to fix problems.
Click to expand...
Click to collapse
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
10 minutes later and its still sitting at restoring call log. should i abort this?
Rawt said:
10 minutes later and its still sitting at restoring call log. should i abort this?
Click to expand...
Click to collapse
you can if you want
since call logs aren't important as long as your contact list is restored
pcshano said:
you can if you want
since call logs aren't important as long as your contact list is restored
Click to expand...
Click to collapse
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Rawt said:
seems to have worked. all my contacts are there, and i can send/receive texts. only issue is, none of my apps, settings, layout, wifi,etc transferred over for some reason. so i guess im stuck manually entering in all of this data. what a ****ing hassle this was.
do any of you trusted members do this for a fee? i really liked what i saw with darthstalkers, but cannot be bothered to go through this again.
Click to expand...
Click to collapse
Settings, not much can be done about that. It's needed to wipe them when going to a custom ROM (same goes when updating to avoid issues).
Titanium Backup can save your Wifi, apps and apps data (requires root). Also can save your texts and call logs with it.
Rawt said:
Ok well i wiped cache/data in recovery mode and all seemed ok (not sure if its worth noting, but the recovery menu/screen was totally different from last night - the one last night was touch screen with ++++ before and after each menu choice, and the one today has me using the volume keys to move and power to select).
i went to do kies restore and it went smoothly, but is now sitting on the last option, 'restoring call log', for quite a while. So i guess ill update this again when kies finishes up.
Click to expand...
Click to collapse
Sounds like you booted into stock recovery which is what you wanted.
I used to think it was a pain restoring settings all the time but after 100 or so ROM's over various devices its takes 10-15 minutes to do that and install my apps form the market (I only use maybe 20 or so and maybe are one I have apk for already.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
hednik said:
.
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
This line is awesome!
Sent from my SGH-I747 using xda app-developers app
Rawt said:
So its possible it was just a bad install? This isnt a very technical or tough thing to do, but becomes a serious pain int he ass when things go awry. Would love to have the darthstalkers setup, though. I just hate to do it and have it all be FUBAR'd again.
Click to expand...
Click to collapse
Keep in mind that flashing a custom ROM also means flashing the updates (as it can always get better and there are bugs to fix), meaning that you will have to factory reset every time (which resets your settings, cleans your apps and such). So it's something you kinda have to get used to when flashing.
That's also why I suggested Titanium Backup, it saves a lot of time when it comes to apps, wifi, call logs, texts, etc. You'll still have to go through your settings, emails and accounts though.
If you wanna go ahead and give Darthstarkers another try, re-download it and make sure you follow their full instructions.
hednik said:
Everyone's first time is a bit awkward and messy... gets fun after you do it enough
Click to expand...
Click to collapse
its true. the first time around is always a little bumpy. as long as you are doing things correctly and installing the correct files, things will only go smoother with time.
this is just my preference, but once i've transcended stock (to aosp), i dont mess around with kies anymore. i know you had your things backed up via that route but ask around and you'll see, there are a lot of useful apps out there that can backup and seamlessly restore everything you want after flashing.
dont give up. everyone deserves the performance and style they want on their device. next time you're ready, let us know. between myself, hednik and a few others, we can get you the best way to do this right here in one thread versus 20 different sites/threads/opinions. cheers
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Rawt said:
I didnt think about the future and rom updates, etc. I think ill pass for now, my time for this is limited. I'd love to have something like darthstalker working, but i cannot afford to spend the time if it all goes to hell again.I do sincerely appreciate the help, and if theres some way i can say thanks other than clicking thanks for each of you (already done), please let me know.
Click to expand...
Click to collapse
It's basically the way to show your gratitude, you've said thanks and pressed the button, can't ask for much more :highfive: Especially from a new user.
I hope you find the time to enjoy one of those custom ROM at some point and we'll be here if you need help again. Good luck!

[Q] Crashing apps and loss of service?!

Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!

Categories

Resources