Develop Bugs

Unfortunately the process.com.android.phone has stopped

When I make a phone call I get "UNFORTUNATELY THE PROCESS.COM.ANDROID.PHONE HAS STOPPED".When I press ok it ends the call. The phone is a sprint variant on cm10 latest nightly. My att on the same cm10 nightly doesn't have this error. How can I fix it?

outkast22 said:
When I make a phone call I get "UNFORTUNATELY THE PROCESS.COM.ANDROID.PHONE HAS STOPPED".When I press ok it ends the call. The phone is a sprint variant on cm10 latest nightly. My att on the same cm10 nightly doesn't have this error. How can I fix it?
Click to expand...
Click to collapse
should be posted in correct thread of the ROM. But could as simple as a bad flash, check the md5 and do a clean install.

Sent from my SPH-L710 using xda premium

jcwxguy said:
should be posted in correct thread of the ROM. But could as simple as a bad flash, check the md5 and do a clean install.
Click to expand...
Click to collapse
Sorry, Im learning. Could you link me? I searched cm10 but I dont see a thread for the rom.

outkast22 said:
Sorry, Im learning. Could you link me? I searched cm10 but I dont see a thread for the rom.
Click to expand...
Click to collapse
Go to settings/more settings/mobile networks I think and there should be a sim option and something else make sure your not on sim. At leased thats what happend to me. And the correct thread fir this is in Q&A
Sent from my SPH-L710 using xda premium

outkast22 said:
Sorry, Im learning. Could you link me? I searched cm10 but I dont see a thread for the rom.
Click to expand...
Click to collapse
cm10 i believe is in sprint galaxy s3 original development
http://forum.xda-developers.com/showthread.php?t=1778266

Questions go in Q&A
Thread moved!
Sent from my SPH-L710 using xda premium

ok, I need more help please. I am trying to install cam from the above posted link. When I click install recovery from my current touch recovery, I get an error message. "cannot open /External_SD/recovery – clockwork touch.zip bad
Installation aborted....
How do install the correct cwm so I can flash cm10? thanks!

bump

Zip
re download the zip file and try again.

ive done that, same issue. Can someone post a link of a different file I can try?

jcwxguy said:
should be posted in correct thread of the ROM. But could as simple as a bad flash, check the md5 and do a clean install.
Click to expand...
Click to collapse
See - the thing is (if you read up on the issue) the problem happens on ANY phone - running ANY rom - and VARIOUS radios ... so doing the thread nazzi thing really doesn't help, as the issue is prevelant across the board. If that's not bad enough, god forbid you start a new thread because again ... the thread nazzis jump out of the woodwork and (seemingly gleefully) post all the different posts where it's already been discussed. Well yea, that's because there is no magic silver bullet. I've got the issue, and I'm not going to bother saying what rom or radio or kernel I'm using, or how many cashes I've wiped or permissions I've fixed, because I've already run thru all those gymnastics. So you see, it cam be just as frustrating having to keep reading about the problem again & again, as it is trying to walk on egg shells to find a cure, in the exact right thread, in the exact right forum. In the mean time, the only thing I've found that guarentees the issue doesn't happen to me is to go all the way back to the Sarum rom. How pathetic is that. But thanks for the help anyway ... presuming some day there comes a "one cure - cures all".
.

com.android.phone has stopped
outkast22 said:
When I make a phone call I get "UNFORTUNATELY THE PROCESS.COM.ANDROID.PHONE HAS STOPPED".When I press ok it ends the call. The phone is a sprint variant on cm10 latest nightly. My att on the same cm10 nightly doesn't have this error. How can I fix it?
Click to expand...
Click to collapse
I had the exact same problem with a reoccurring message that would flash on and off every second or so. I did both a data restart then a reboot of the android software by pushing the down volume button then holding the power button. When the LG logo appeared I released both buttons and followed the instructions for an android factory reboot. Apparently it is the SIM card. The android com.android.phone communicates with the SIM card and allows calls and texts to be sent and received using the android software. My SIM card got damaged somehow and could not receive the call from the android app com.android.phone. I had to buy a new SIM card for ten dollars and had my stored files on the SIM moved to the new one and no more problems. Telus and Bell move the files to the new SIM for free i'm sure other major service providers offer the same free service.

process com.android.phone has stopped on my at&t galaxy s4 1337
I keep getting the process com.android.phone has stopped on my at&t galaxy s4 1337. I tried everything that I know of. one thing I noticed tho is after every wipe and reset I never see the factory dialer on the phone. Can anyone help me with this???

Lifelover55 said:
I keep getting the process com.android.phone has stopped on my at&t galaxy s4 1337. I tried everything that I know of. one thing I noticed tho is after every wipe and reset I never see the factory dialer on the phone. Can anyone help me with this???
Click to expand...
Click to collapse
It may be too late, but.. I just had the same problem while installing some kitkat apps and spent hours trying everything to fix it. What ended up fixing it was: Settings>Application Manager> Menu > Reset app preference>Reboot.
Hope this helps!

Hands free activation with everey reboot

Can someone help me with this? I found that if you remove sprintandroidextension.apk it goes away but it didnt. I also found that by removing SprintOMADMConnMOPlugin.apk it goes away, but i cant find it on my Galaxy note 2. Any ideas? Thanks in advance.

If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.

Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak

digitallogik said:
If you let it go all the way through HFA once it won't return. Since you removed sprintandroidextension.apk I'm not sure it will succeed now. Try re-adding that first.
Click to expand...
Click to collapse
I tried doing that many times but it never worked, it just gave me an error.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
Thank you! it worked

interesting. found this thread buried, and there still seem to be many people with this issue... seemingly related to the chameleon FCs some are getting, somehow possibly related to the LK8 update and/or a return to an earlier stock version...
digitallogik said:
If you let it go all the way through HFA once it won't return.
Click to expand...
Click to collapse
I've let it complete (personally) aprox 20+ times, so no go.
trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
could the "fix" really be this simple? (at work, can't test this right now.)

kingdazy said:
could the "fix" really be this simple? (at work, can't test this right now.)
Click to expand...
Click to collapse
yes, and you can delete the activation.apk as well to stop it

trim81 said:
Under system/app, look for Sprintdm. Apk ///// change it to Sprintdm. Bak
Click to expand...
Click to collapse
thanks, stopped the HFA, still have the chameleon errors to deal with...
t3project said:
yes, and you can delete the activation.apk as well to stop it
Click to expand...
Click to collapse
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.

kingdazy said:
thanks, stopped the HFA, still have the chameleon errors to deal with...
and I suppose I could do that too.
but both of these workarounds are "dirty fixes", and not fixing the fundamental issue.
Click to expand...
Click to collapse
your solution is to thoroughly wipe and reflash whatever rom you are running.

t3project said:
your solution is to thoroughly wipe and reflash whatever rom you are running.
Click to expand...
Click to collapse
I would have thought so too. As I've been advised by other as well. But...
I have, at least five times, run a return to stock, both through ODIN and OneClicks.
I still have the issue. Baffles the mind. Makes little sense. But there it is. And I'm not the only one.
(Just so it's noted, and before you accuse me otherwise, I am not new at this, and I follow directions fastidiously. I've never once had a problem that I didn't cause myself, and I've always been able to fix them by further reading/researching.)
Just for SnG's I'll quote myself and others from a few other posts in other threads:
kingdazy said:
well, this is annoying. I seem to be stuck with the "hands free activation" and chameleon fc.
i'm assuming a nice total stock one click should fix it?
Click to expand...
Click to collapse
garwynn said:
Sure should! Please try the stock restore or rooted restore.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
kingdazy said:
interestingly, it didn't fix it... "preparing network", "hands free" and chameleon FC on every reboot. this is after the rooted full restore OC. what am I missing? weird.
(history: I was rooted stock w/ twrp from the mskip toolkit method of rooting, got rid of twrp using the mrRobinson stock w/ root, and flashed the sxtp update to lk8, got a wifi failbug and tried to get back to stock rooted using mrRobinson and started getting this issue. lol. ok. so... one-clicked your rooted full restore, still there. is that even possible?)
well, my phone seems to work, as long as I don't reboot.
but I find it worrisome.
have to sleep for work now, but if you had any advice for things to try when I wake up, let me know? thanks dood.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
kingdazy said:
Just my 2 cents, my experience with this error.
I'm getting the Chameleon FC, and the persistent HandsFree Activation on every reboot. All started when I lost wifi on the LK8 update zip (I was rooted, thanks to Voodoo OTA rootkeep), and tried to get back to LJC...
And this morning, I tried the following:
Installed TWRP with GooManage, restored a nandroid from my orig rooting using the toolkit, no luck, same two errors.
So then I OneClicked the Full Restore (SPH-L900_LJC_Stock_Restore.exe), and wtf, still there.
As I mentioned in my quote, it (the Note2) works, not broken, but I find the persistent error worrisome.
I am open to criticism, suggestions, whatever. What am I missing?
Click to expand...
Click to collapse
Itchiee said:
I'm having similar issues, I was on the release before LK8, then updated to LK8 but wanted to start over again.
Once i downgraded to LJ1? the hands free bug kept popping up every reboot, until I moved onto to LJC then LK8 update file which is fine.
I'm trying to figure out myself how to go back to the original firmware (pre any updates) without the issues... /subscribed.
Wonder if this is tied into it somehow...
I dunno, my head is exploding reading all these posts, replies.... 5 different versions of restore.
Click to expand...
Click to collapse
evilgenyus said:
I have tried the one click restores back to ljc and the original tar, and I still have the hands free activation issue and the chameleon error. And when I update to lk8 I get no wifi. I have tried returning to stock about 4 times and then updated to lk8 with the same results. I always go back to ljc bc I need wifi.
Click to expand...
Click to collapse
kingdazy said:
interestingly, even using a stock oneclick full restore (and even using a TAR in Odin), still have the handsfree repetition and chameleon FCs. (lol, I'm not complaining really, it's early in the dev life for this device I suppose. )
Also, I've been reading that re-flashing the LK8 update.zip (via sxtp?) while it seems to fix the HFA and ChameleonFC, it kills the wifi? (it killed my wifi after aprox 2 days use, when I orig updated...)
Click to expand...
Click to collapse
garwynn said:
I'm starting to wonder if the move to 4.1.2 changed something that isn't handled properly by older versions. Without a gn2 will be hard to confirm... but I may be resolving that soon as well!
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It would apear that something in the LK8 changes ... something. Permanently?
So, any new advice would be welcome...?

Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app

smooth703 said:
Would renaming the chameleon apk have the same result as hfa
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
fine question, but without knowing what the chameleon apk does, i'm reluctant to f**k with it.
anyone know? (a goog search gave me nothing...except this XDA rom w/ a fix...? I'm going to try n PM him...)
and again, my concern is the issue seems to be more significant, seeing as a Full Wipe to Stock doesn't fix it.

has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
sxtp site said:
If you need to clear NVRAM/Sprint data login info, perform a ##72786# reset from the Dialer and enter MSL.
Type getprop ril.MSL in adb shell or terminal to retrieve your MSL.
Click to expand...
Click to collapse

kingdazy said:
has anyone with our issue attempted to get their MSL, do a NVflash reset? (##786#)
I am (for some reason) unable to get my MSL, so can;t test this.
Click to expand...
Click to collapse
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile

shiftr182 said:
I tried it, it doesnt work. You have to go to settings and activate device to get your info back, and it still does handsfree on every boot and no way to update profile
Click to expand...
Click to collapse
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium

So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
kingdazy said:
it would seem that the factors that all of us with this issue have in common are: a) rooting w/ ToolKit ver2 b) flashing LK8 update zip c) trying to return to stock LJC/LJ1 because of a wifi problem... please chime in if you have the issue, but not one of those factors?
After everything, I just returned to stock LJC w/ Flash Counter @ 0 (no) w/ the errors still present, took it into Sprint store said, 'hey guys, this is weird, i've got a persistent error, won't go away after resetting my phone." (IE, acted dumb enough to not have rooted/flashed unofficial shtuff/etc, but smart enough to know that it's a real issue), they looked at it, asked a few obvious questions, replaced it, because obviously something was wrong in a permanent way. I want to a corp store, not a "repair center". I think it was a good thing that these guys were not super techie.
I told them as little as possible, that I had a "wifi issue after an update, tried full reset (through the android settings menu, of course), and the problem didn't go away, no matter what". Once they heard that I had done a full factory reset, and saw the problem/error happen, it was a no-brainer to swap out.
I'll be avoiding the LK8 leak for now, and frankly gun-shy about the toolkit.
Click to expand...
Click to collapse
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
kingdazy said:
ok, to get back to stock, first use this OneClick to get to Stock+Root, it will wipe ALL internal memory except SD card:
http://rwilco12.androidfilehost.com...sung Galaxy Note II (SPH-L900)/LJC/ROM/Rooted
Instructions are here:
http://www.sxtpdevelopers.com/showt...-TAR-SPH-L900-LJC-(LJC-Modem-Kernel-ROM-Stock)
then use TriangleAway, this will set your counter at 0 (reads as "no" in download mode). it should also say "Official" And "Samsung Official"
Then, if you want to get Total Stock unrooted, for returns to Sprint, or any other reason, use Odin (not mobile) to flash this:
http://www.androidfilehost.com/?fid=9390214368362234120
Instructions for flashing that are here:
http://www.sxtpdevelopers.com/showthread.php?76-TAR-STOCK-Full-L900VPALJC-quot-Back-to-Stock-quot
After I did those things, I was stock unrooted, no flash count.
Click to expand...
Click to collapse
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.

Yeah, I have to give it up to garwynn, he hooked me up with the pit file for our phone. Good people.

ProjectROM 2.1
Did a clean install and I get this as well =/

RussellAlan said:
Did a clean install and I get this as well =/
Click to expand...
Click to collapse
a clean install, coming from what? And what did you use to get back to stock? (Just asking so people will have a clear history of what is causing this. In case a dev wants to look closer at the problem, have clear ideas where to start)
Sent from my SPH-L900 using xda premium

ceabbott2 said:
Same here I tried it no luck.
Charles
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
+1
Sent from my galaxy note 2....

kingdazy said:
So I ended up returning my phone to Sprint, the swapped it out pretty easy, let them see the issue and error, they said "yeah, that ain't normal", got me a new one.
I had someone ask how I got it back to stock unrooted w/ no flash count, and while that might be abvois to some, just in case someone doesn;t want to hunt around, or ask this is what I did, with links:
Good luck to the people with this error, I feel for you, very frustrating. I am hoping that Samsung releases an official OTA soon similar to LK8, that you will be able to flash that will fix the error and the wifi.
And I hope the devs are reading these posts (even if they are not responding), are at least looking into it.
I know we have the attentions of garwynn, he's made the SxTp team at least aware that there might be an issue.
You'll be seeing me.
Click to expand...
Click to collapse
I try that method but mine still show 1 on the counter. Is there a way to get rid of that?

Flashed rooted ATT jellybean

This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now

doing the same thing right now. i'm in germany so i'm not sure if that's what's causing the slow download speed 500Mbps link @ a convention center, but i'm at 416MB out of 617MB and very very very patiently waiting.
it's good to hear that you only ran into that small issue. i'll keep an eye out for it. Thanks!

ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)

Maroon Mushroom said:
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)
Click to expand...
Click to collapse
First post here as well. I was rooted on stock, and this flashed flawlessly. Not 1 problem. Thanks!

ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?

Aww man. It figures, I just finished flashing another rom like, about 18 hours ago. Now with finals coming up, I don't have time to do this one! Oh well, I guess I have something to do AFTER finals then, hahaha.
bluemax189 said:
ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?
Click to expand...
Click to collapse
Is your power saving mode on? I've always found it makes so many things laggy, unfortunately. Might be enabled by default on the rom. Worth a look.

Great community here. Yesterday I was non-rooted ICS. Today I'm rooted JB with Wallet.
My phone just got 1000% better.

First of all, I appreciate all the Devs hard work bringing these Roms to us! :good:
I was running rooted UCALH9. Updated to this JB via Odin and all SEEMED good. Problems I had:
1) Play Store FC's - FIX - I went into Application Manager and removed updates for the Play Store app, which reverted it back to the default Play Store app. This fixed my problem. MAKE SURE YOU DO NOT UNINSTALL!
2) Rom Manager - I would get root user authentication error when trying to Fix Permissions. Everything else in Rom Manager worked. No fix at this time.
3) Gallery - None of my pictures were showing up. This is even after clearing caches. I am convinced it's because I can't Fix Permissions, but what do I know... No fix at this time.
Any help would be appreciated!

Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.

egyan said:
Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.
Click to expand...
Click to collapse
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!

Howl long was the flash?
I'm inside Odin on flashing system.img.ext4 right now and it stays there which looks like about 20% for last 10 minutes with no forward movement.
How long do I need to wait before I consider something is wrong with flash process?
Changing cable to Samsung one did the trick if you are in the same situation.

Can you do this AFTER upgrading to Jellybean?

questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?

questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
greystealth said:
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?
Click to expand...
Click to collapse
If you are talking about flashing the root injected JB i post, yes you can flash it after upgrading and no it won't wipe anything in data, everything should be preserved for you.

Weather here sux.... Hovering slightly above 0 degrees with 80 mph winds for the last week so add on the wind chill factor and u can only imagine... And no snow yet.
So far no other issues with this rom. Seems to run perfectly. Now just waiting for someone to write a power menu options and enable stock tethering script =P
Sent from my SAMSUNG-SGH-I747 using xda premium

You might try wiping data for gallery app and I think it's media storage app...see if that helps with gallery.
Toested said:
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!
Click to expand...
Click to collapse

Flashed this over stock and works flawless no lag no stutter. Thx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium

Anyone figure out how to enable stock jellybean lock screen?
Sent from my SAMSUNG-SGH-I747 using xda premium

Neflhiem said:
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I kinda miss the added features from the rom I was on frosty jb but I'm adding things here and there, wish we had multiview seems cool but I'm just waiting for the 4.2 roms to start coming out but so far not too bad, except the flash counter thing, but I'm happy with it so far just need someone to put out a hd theme like the one I had on my phone before but that to will come, also glad that the 4.2 camera with photosphere still works that feature is cool
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Cannot get wallet to work

Ok. I am really upset with Tmo for blocking Wallet. I used it ALL THE TIME on my Nexus S on AT&T and I LOVED it. I've been trying to get it installed since October when I bought the phone and I cannot for the life of me get it to work. Everything I try fails or screws up the phone and I have to re-flash, so I eventually just said screw it and went to AOKP because I felt like trying something new. My friend said that I would be able to just install wallet once I did, but that is not the case. the install fails when using an apk, wallet is hidden in the market, and once when I got it installed it says "not available on your device/carrier blah blah blah" and quits. So, what I want is a solution. I need to know how to make this work because I am starting to get really upset. No solutions I can find work, nothing I've tried is successful... I might just be doing it wrong or missing something but I am determined to get it to work. NFC is working fine, I used it several times already.
Phone info:
Model: SGH-T999
Android Version: 4.1.2
Baseband: T999UVDLJA
Kernel: 3.0.48-cyanogenmod-faux123-att-tmo-00041-ga2c7267
AOKP Version: aokp_d2tmo_jb_milestone1
Build: aokp_d2tmo_userdebug 4.1.2 JZ054K eng.sethyx.20121029.025840 test-keys

I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.

Pennycake said:
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Click to expand...
Click to collapse
I tried that the first time and it caused a failure to boot. second time, it was a program that was supposed to do it for me - same result.

If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
up until now I was using touchwiz. I screwed up the phone both times while using touchwiz. Now, I'm on AOKP and cannot find anything that works for that - everything seems like it's for touchwiz. What I tried was flashing wallet now on aokp, and it didn't harm the phone but the program will not work. If I load it, it just says "Unfortunately, Google Wallet is not yet available for your device or mobile network." and I want to know how to get around that on aokp, ignore touchwiz, I was just mentioning that because I ditched it in part due to the problems it had with wallet.

Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app

There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy

Pennycake said:
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok ok, I think I understand you now. You still have to mod build.prop even on aokp? just don't have to do all that other stuff that you do have to do for touchwiz?

osmosizzz said:
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2044362&highlight=wallet This thread?
I was using this exact app that it screwed up my touchwiz last time, and now it does not show an option for AOKP, just AOSP. Will the AOSP work?
Ok seriously. I didn't even run the app this time I just opened it and it screwed up my rom! God, why is this so infuriating! If someone had told me I would have to go through all this bull**** to get my stupid phone to work as well as my old, slow nexus s I would never have upgraded! BRB, time to reflash aokp.
*seeths with rage*

It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app

Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
IF I'm not mistaken aokp is rooted by default. Anyways, I'm in the process of reinstalling it... again.

Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
used an app from the market to edit my build.prop and it works perfectly now. Thanks!

Unfortunately settings has been stopped?

What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.

I'm sure I'm not the first one and only one who got this message. Could anybody please help?
Thank you very much!

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.

Irwenzhao said:
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Click to expand...
Click to collapse
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...

testrider said:
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
Click to expand...
Click to collapse
U could try reflashing stock rom if u don't want a custom one.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.

testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.

0.o said:
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
Click to expand...
Click to collapse
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM

testrider said:
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
Click to expand...
Click to collapse
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app

kintwofan said:
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?

testrider said:
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
Click to expand...
Click to collapse
Yep right after it happens. If there is something that triggers it. Reboot, to clear the log, then trigger the fc and pull log
Sent from my SGH-T889 using xda app-developers app