Develop Bugs

[ODIN] Stock DJ20

This should help a few people out. Thanks to dfgged, we now have stock Odin files. There has been minimal testing of these, but they do in fact work to help recover. It won't fix everything, but if you had to go back to stock for warranty reasons, this would be better than having a really messed up ROM. Currently, I only have the System and Kernel. Both are untouched, minus the System dump being rooted, which was required to get the dump. Flash in Odin via the PDA button. I will also work on getting the rest of the usable images posted, and will post a CWM flashable package for stock, stock deodexed, and debloated then as well for DJ20.
System
Kernel

So I flashed dl09 followed by both above and I'm still stuck at the Samsung screen...wtf?

If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?

imnuts said:
If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?
Click to expand...
Click to collapse
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...

jenisiz said:
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...
Click to expand...
Click to collapse
so you flashed verizon odin files on your continuum? that wasnt going to end well

nitsuj17 said:
so you flashed verizon odin files on your continuum? that wasnt going to end well
Click to expand...
Click to collapse
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
By confirmed do you mean "not at all confirmed"?

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
where was it confirmed? i dont recall ever seeing that

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
The only thing that is confirmed to work as far as going from the Fascinate to the Continuum are the radios. If you get a botched up baseband, you can flash a Fascinate radio to a Continuum (and probably the other way if we had Continuum radios, but we don't), but that is the only thing that is cross-compatible that I've seen. Maybe you could get most of a ROM to work as well, but you'd loose your softkeys as well as the ticker functionality if you didn't have the proper framework files.

nitsuj17 said:
where was it confirmed? i dont recall ever seeing that
Click to expand...
Click to collapse
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?

jenisiz said:
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?
Click to expand...
Click to collapse
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.

imnuts said:
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.
Click to expand...
Click to collapse
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.

Flashing the modem doesn't cause the phone to stop booting, so something else is likely the problem.

jenisiz said:
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.
Click to expand...
Click to collapse
you made it sound like you flashed the dl09 rom, thats where i was coming from on my comments

Nope...not the rom lol. I was going off of a convo in pm with nuts. I wish it was that obvious though...

hi everyone..
having an issue with this recovery...i have used this file twice before to recover the wife's continuum.. however last night it wouldn't work.. meaning, it flashes in ODIN just fine, gives me "success" however when the phone reboots, nothing has flashed and it is exactly the same as before flashing..
i have red cwm on the phone, and have tried clearing everything (cache, dalvik, data/factory reset, mounted all partitions and wiped those) i also tried flashing the kernel which seemed to work.. however it still will not reset to factory.. i used the same file i have on my computer that worked 2x before, and even re-downloaded the one posted here and tried that as well.. nothing..
it appears for some reason the phone accepts the connection and/or files, but won't "run" them if that makes any sense...
i also have 2 nandroid backups that i tried to restore, which is the factory setup..and it hangs at the samsung logo (i gave up after 20 mins and pulled battery) .. and the second nandroid takes me to the deodexed/basic rom that was built here.. which works but has issues..
im trying to get back to complete stock.. i have also tried using superoneclick to unroot, but the program gives me an "error 22" when pushing rage, and locks up..
i have tested adb, and it will connect to phone, but NOTHING can be pushed or pulled using the commands..
im lost here.. anyone have any ideas?

Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App

trailblazer101 said:
Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
thanks for the reply sir..
i did not convert to voodoo...however i will check that in the voodoo section just to be certain its not toggled..im very familiar with voodoo, as i ran it on my fascinate for a long time .. i am using factory cable as well.. i will edit the post if it comes to fruition that it did..i never flashed a kernel - unless the one with the ROM here was voodoo..but i dont remember hearing sexy lady telling me anything when i flashed it
this is SO frustrating..it worked 2x before.. im assuming something is borked with r/w somewhere..but i havent a clue where to look to change it..
it boots to blue recovery, run update.zip to red..
under mounts and storage (that i cleared all on before) it currently reads all mounted except /dbdata which is unmounted..

Lmao, sexy lady...
When I get home, log into the Continuum irc channel, and lets see if we can't straighten you out
Sent from my SCH-I400 using XDA Premium App

any chance we can have the OP links updated, please, i tried downloading the files but links are broken

[Guide]Oops, I flash something in Odin on "Phone" instead of "PDA"[ACS]EG30 AVAILABLE

[Guide]Oops, I flash something in Odin on "Phone" instead of "PDA"[ACS]EG30 AVAILABLE
DISCLAIMER
This is a guide for people who want to fix a mistake they made and NOT for people who want to experiment with their modems. Therefore, I am not responsible for any damage you do to your phone using this guide or these files.​
Hello ladies and gents, AbsolutZeroGI here.
So, you've flashed something in Odin on "Phone" instead of "PDA". It happens to everyone. By that I mean I've done it enough times to cover everyone who didn't.
Thankfully it's an easy fix.
Before we begin, I'd like to thank Hacre for obtaining and uploading the stock modem.bin file. Also, thanks to the guy who pulled it to begin with (when I can remember his name, it will go here). I've tested this method personally (on purpose AND by accident), and I know that it works.
First, what happens when you flash something over "Phone" when you shouldn't? Well, it attempts to replace the modem.bin file with whatever it was you were trying to flash. If you unplug the phone and pull the battery, your phone will actually reboot. The worst consequence of this action is that your data will be DEAD. No signal, no data, no wifi. This is not nearly as big of a deal as it sounds. So take a deep breathe and ask yourself: what is the solution?
The solution is, of course, to flash the modem.bin file back to where it belongs. Here we go!
Okay, if you've flashed something on "Phone" instead of "PDA", you'll notice that Odin never finishes out and the phone never automatically reboots (like it usually does when you flash on Odin). This is normal and nothing to be alarmed about.
First thing is first, you need a modem.bin file. You can find one here: ACS Forums
**update** I now have ALL modems over at the ACS Forums (EG12, EG30, EG31 and EK02). So you can pick and choose which one you want
Next, pull the battery and unplug your phone (if you haven't done so already).
Then, you're going to put your battery back in and hit vol-down + power to get back into Download (Odin) Mode. Press up for yes when it prompts you.
Now open up Odin and plug your phone back in. It should connect just as it always does and be prepared to flash. If you don't know what I mean by that, check out the tutorial on using Odin here: [url="http://forum.xda-developers.com/showthread.php?t=1274337]Odin Tutorial[/url]
Finally, you're going to click where it says "Phone", navigate to the modem.bin file you downloaded and select it. Make sure nothing besides reboot (it may be called auto-reboot) is checked in the boxes on the left hand side. No seriously, double check again please.
Hit start to flash it. Your phone will flash and reboot and be all fixed and you can continue with what you were doing.
Remember, we all do stupid things. That's why we have Guides to fix them
Hit the thanks button if I helped ya!
**Update**
We now have access to all 4 modems. Click the link above to go the ACS forums, then click on the link there to get the downloads.

Updated. Now there's download links for EG12 and EG30 over in the ACS thread for those who want a specific one
Enjoy!

is one modem known to be better than the other? It's easy enough to try both, I was just wondering if it had been discussed already.
Sent from my SPH-D710 using xda premium

smark72 said:
is one modem known to be better than the other? It's easy enough to try both, I was just wondering if it had been discussed already.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I've heard it has (I've been busy with exams and first week of the new quarter in college), but I haven't seen it. Some people claim one gets better signal and less LOS, others claim the other does. Some claim there is no difference and there's a placebo effect.
But I thought as long as there's more than 1 I'd post it so people could choose. I only had eg12 before so now people have the full choice.

From what I've read the EG12 modem has been known to cause the phone not ringing when sleeping. I would go with EG30.

I just noticed that there is a size difference in the bin files. The eg30 you linked is 1.25Mb. The eg12 is 16Mb. A few posts down someone linked another eg30 that is 16Mb. Are they supposed to be around 16?
Sent from my SPH-D710 using xda premium

smark72 said:
I just noticed that there is a size difference in the bin files. The eg30 you linked is 1.25Mb. The eg12 is 16Mb. A few posts down someone linked another eg30 that is 16Mb. Are they supposed to be around 16?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Disregard that, fixing it now. Give me like 10 minutes lol.

AbsolutZeroGI said:
Disregard that, fixing it now. Give me like 10 minutes lol.
Click to expand...
Click to collapse
Cool. Thanks.
Sent from my SPH-D710 using xda premium

smark72 said:
Cool. Thanks.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
fixed
10char

Was on EG30 before, Trying out EG12 now.

I've odin both modem bins and both shows EG12. not sure if i'm doing it wrong, but i followed the instructions.

File comparison shows no differences in the EG12, EG30 or my pulled EG30 modem files, so who ever said they are different modems, they are not

Calkulin said:
File comparison shows no differences in the EG12, EG30 or my pulled EG30 modem files, so who ever said they are different modems, they are not
Click to expand...
Click to collapse
Can't wait to see what magic you work for our phones. Appreciate the insight as usual
Sent from my SPH-D710 using xda premium

Calkulin said:
File comparison shows no differences in the EG12, EG30 or my pulled EG30 modem files, so who ever said they are different modems, they are not
Click to expand...
Click to collapse
Is it possible that you can post your eg30 modem file?

Anyone thinking about flashing any of this should take a look at this thread
http://forum.xda-developers.com/showthread.php?t=1312790
You might be getting problems you can't get rid of
Sent from my Samsung Galaxy S2

I flashed eg12 and my calls went straight to voicemail, then I upgraded prl/profile and it doesnt happen anymore. seems like I have better coverage but slower 3g
Sent from my SPH-D710 using XDA App

I dont recommend anyone flash eg12. Its very hard to get eg30 back even after flashing it. My phones been stuck on eg12 for 2weeks now. Ive tried everything. Also it cauesed my wifi to be on constant error and no vibrate.
Sent from my SPH-D710 using xda premium

Calkulin said:
File comparison shows no differences in the EG12, EG30 or my pulled EG30 modem files, so who ever said they are different modems, they are not
Click to expand...
Click to collapse
Yep, md5's are the same. So one file is just renamed into the other, whether they are both EG12 or EG30. So proceed with caution (as always with everything you get from XDA ;P)

This might be the first time EVER that someone has said the following words.....
Wrong section. Mods please move this to Development.

jirafabo said:
This might be the first time EVER that someone has said the following words.....
Wrong section. Mods please move this to Development.
Click to expand...
Click to collapse
Thank you jirafabo, a shine of humor and delight in an otherwise sea of misery. If they want to they can move it lol. I've always posted my guides in the general section.
LISTEN UP LADIES AND GENTS. I realize that both are the same modem. That's a my bad. I spent 4 hours last night testing modem pulls and people either didn't do it right or had an eg12 baseband.
That being said, keep in mind that this is a guide for people to restore service to their phones if they've flashed something over phone instead of pda. this is not a guide for people to be fiddling with their modems (which you shouldn't be doing anyway) to see "which one is better". I will try to find one, but I don't consider it "imperative". The guide restores service, as promised.

Sprint pushing me a system update... Root safe?

Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron

Aairman23 said:
Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron
Click to expand...
Click to collapse
If you aren't on the "factory" ODIN odexed ROM with EG30 modem, the update will fail. The update from Sprint relies on the system files being in a particular condition and the update will fail if they are not in that condition.
I have heard that some people have perfectly working phones after rebooting (but not updated). If you want EK02 ROMs, they're available in the development sub-forum and would be easier to manage than returning to stock and accepting this update.
EDIT: You may need to pull the battery to get out of the update. Supposedly once you put the battery in, you'll get to CWM, and then should be able to boot back into Starburst. I haven't done this, so I can't confirm.

Go back to stock.
The update will fail.
Why not flash the update from here? Android 2.3.6 + root is in the development section.
Sources? Personal experience.
Sent from the future.

nivron said:
If you aren't on the "factory" ODIN odexed ROM with EG30 modem, the update will fail. The update from Sprint relies on the system files being in a particular condition and the update will fail if they are not in that condition.
I have heard that some people have perfectly working phones after rebooting (but not updated). If you want EK02 ROMs, they're available in the development sub-forum and would be easier to manage than returning to stock and accepting this update.
EDIT: You may need to pull the battery to get out of the update. Supposedly once you put the battery in, you'll get to CWM, and then should be able to boot back into Starburst. I haven't done this, so I can't confirm.
Click to expand...
Click to collapse
You are correct, I pulled battery, was directed to CWM and rebooted system...all is fine (as it was before).
I saw QBKINGs videos on updating the Modem, but am not sure I want to go through with that until i figure out if the update is worth it. I am still not sure if this was an android version update, or an update that fixes LOS...or both. If I see a majority of members recommending this update, then I guess I'll jump through the hoops.
I tend to not have very much luck with tinkering with my phone. Something always goes wrong and then I loose 2 hrs of my day trying to figure out how to fix it. but I guess that's the name of the game...

SocialReject said:
Go back to stock.
The update will fail.
Why not flash the update from here? Android 2.3.6 + root is in the development section.
Sources? Personal experience.
Sent from the future.
Click to expand...
Click to collapse
I'll check this out.
I know I SHOULD know this, but... what would the process be for getting 2.3.6+ root along with starburst Rom. Would I flash the above recommendation then flash starburst over it, then load my ICS them last?
P.S. please forgive my incorrect use of the technical terms flash and load. As you can see from my questions, I only have a cursory understanding how rooting/flashing/loading.....just enough to get my phone to the customized state that it is currently in.

If it ain't broke.... that's my motto and if you are not savvy with the phone I definitely suggest you leave your setup alone. Using Odin has got to be one of the easiest things to do though but once again if it ain't broke....

Aairman23 said:
I'll check this out.
I know I SHOULD know this, but... what would the process be for getting 2.3.6+ root along with starburst Rom. Would I flash the above recommendation then flash starburst over it, then load my ICS them last?
P.S. please forgive my incorrect use of the technical terms flash and load. As you can see from my questions, I only have a cursory understanding how rooting/flashing/loading.....just enough to get my phone to the customized state that it is currently in.
Click to expand...
Click to collapse
Wasn't aware you were hoping to continue using starburst. I don't think starburst supports EK02 yet.
Sent from the future.

SocialReject said:
Wasn't aware you were hoping to continue using starburst. I don't think starburst supports EK02 yet.
Sent from the future.
Click to expand...
Click to collapse
That was all I really needed to know...I am very happy with starburst... thank you!
Edit: last question For some reason I have a little "arrow loop" or "arrows in a circle" (in grey) in the middle of my top menu bar, and it is partially blocking the time. Did I induce this somehow, how do I make it go away (reboot didn't work)?

playya said:
If it ain't broke.... that's my motto and if you are not savvy with the phone I definitely suggest you leave your setup alone. Using Odin has got to be one of the easiest things to do though but once again if it ain't broke....
Click to expand...
Click to collapse
Indeed. You wouldn't believe how many people make one tiny mistake in Odin and BAM it's all over.
Sent from the future.

Aairman23 said:
That was all I really needed to know...I am very happy with starburst... thank you!
Click to expand...
Click to collapse
No problem
Sent from the future.

Aairman23 said:
That was all I really needed to know...I am very happy with starburst... thank you!
Edit: last question For some reason I have a little "arrow loop" or "arrows in a circle" (in grey) in the middle of my top menu bar, and it is partially blocking the time. Did I induce this somehow, how do I make it go away (reboot didn't work)?
Click to expand...
Click to collapse
The arrows are the sync indicator (for any "pull" accounts or contact/calendar sync). You can check under Settings->Accounts & sync to see if any of your accounts are spinning. You can cancel the sync from there and restart it if you like. Sometimes they get stuck.

Aairman23 said:
Quick question,
I'm rooted w/latest Starburst and ICS theme, and I accidentally allowed the most recent Sprint system update to go forward (12/12/2011 @ 8am [EST]). I did so without asking (here) if this was safe. So is it? I searched other threads and it appears that some recommend going back to stock prior to updating, while other swear that "re-stocking" is unnecessary.
So far (after 10 mins) I still have an exclamation mark triangle with a blue andriod guy. Not sure if this is normal. Thanks!
-Aaron
Click to expand...
Click to collapse
More to the point...I am rooted with stock EG30. Received update and failed so I assume I need to un-root in order to get this to install correct?

jeffvb9 said:
More to the point...I am rooted with stock EG30. Received update and failed so I assume I need to un-root in order to get this to install correct?
Click to expand...
Click to collapse
You can do that, or Calkulin has a Stock EK02 ROM in the dev section, which would be easier.

I've been running my phone stock with the EG30 ROM and radio(s) since the day I got it. I originally rooted it using ODIN just to download su (my applications / data were not effected); I do not recall what this method was called. I have not messed with it since due to lack of time.
Today I got a notice about a new OTA firmware update. I let it try to update but it failed with the following error:
Code:
E: Error in /cache/182a027d4e63.SPH-D710_update_EG30_to_EK02.zip (Status 7)
I could be wrong but this error doesn't seem indicative of a failure to update due to the fact that I have root.
I rebooted the phone and it's still at stock EG30 and it states that there is no update available. The only thing I've tried since was to flash (using stock recovery still) a pre-rooted version of this update but it failed to "signature verification".
Can someone give me a pointer on what I need to do to get this phone updated preferably WITHOUT having to reload my apps/settings?
Thanks!

Followed this thread here and was able to update perfectly without having to wipe my data:
http://forum.xda-developers.com/showpost.php?p=20233048&postcount=376
I think the issue may have been that I previously "integrated into ROM" some software via TB. Now have to figure out how to re-root.

Wayno-san said:
Now have to figure out how to re-root.
Click to expand...
Click to collapse
Very simple, just look at the first post in that thread and choose Option A.

Am I in brick city?

So i tried to update my AOKP with just using my phone. And after the reboot.. nothing happened. So i did a battery pull and now when I turn on my baby the led goes blue and stays there.. frozen. No access to recovery or download.
Black screen and blue led.. so yeah.
What I'm asking is.. there's no way of coming back?
Sent from my Old Evo using xda premium

Also.. I semi-bricked before and was able to fix via download mode.. so I know my way around.
Sent from my PC36100 using xda premium

When you updated AOKP you flashed the EL26 CWM kernel as per the instructions in all AOSP roms up until now? Both the recovery in AOKP 37 and the Zip for AOKP 39 (as far as I am aware) are not safe to flash in ICS Recovery.
BLoD is a sign that the bootloader is borked. Normally this is something fixable via JTAG. But it is also caused at Random by the Super Brick bug which can not be fixed. Sounds like you flashed not only an unsafe Zip but in an unsafe recovery and if you tell me you factory reset that would be even worse.
Our phone has a bug in its eMMC firmware which needs to be patched. All of the former ICS leaks have had kernels that can trigger it and last i checked only the Nighlies for CM9 have a safe updater binary used in conjunction with a made safe recovery are generally safe to flash from ICS. Which is exactly why the threads tell you to use the EL26 CWM kernel which if mobile can be flashed via mobile odin. Failure to do so will eventually at random trigger the bug.

Blue LED and not able to get phone into Odin mode = Hard Brick

another one bites the dust......i just don't know how the directions could be any more clear on flashing ICS ROM's. Maybe we need a sticky in every forum in bold letters that says:
"READ ME BEFORE FLASHING!"

I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium

I agree with Rican Bomba... Not everyone is a Android hacking Guru. We are all trying to learn here. I bricked my phone and i did follow QBking77's instructions (Who i believe to be the best at explaining things thoroughly in his videos) yet, there are so many post that aren't clear. I had force closes like crazy on AOKP and before i found the one poster that said don't wipe in ICS... I had done it and lights out R.I.P. First E4GT. I have flashed way too many times to count without incident. Some posters put more info on how not to brick than others. I followed QBking's method to a tee and something was still wrong... I don't blame him (He makes things crystal clear and is great at what he does), things happened and that was that. I learned something from a poster who was very clear and i won't make the mistake again (not to mention I'm leaving AOKP alone lol). Take it easy on these guys, they will learn soon with a little friendly direction

Rican Bx Bomba said:
I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt

iniz94 said:
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt
Click to expand...
Click to collapse
Flashaholic lol no computer access at my job and at home at the moment.
Sent from my PC36100 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!