Database Info

[Rom][ODIN] Stock Gingerbread 2.3.3 Deodexed + Root KF2

Some people have requested this, this is Gingerbread KF2 Deodexed + Root and odin flashable.
This contains all bloat.
Instructions:
1. Perform Factory Data Reset/Wipe Data (If you skip this step it may still work but may leave existing apps and may cause FC's)
2. Flash Via Odin
3. Wait 5min to boot
4. Hit Thanks
The messed up Rainbow at boot is normal if using Froyo BootLoaders just wait it will boot.
Below File contains no BOOTLOADERS
T959VUVKF2 NO BOOTLOADERS
Thanks
Dr.Honk for answering all my stupid questions.
Krylon360 for original KF2 leak

nice dude!!!

Been looking for this. Might be enough to make me give KF2 a try finally.
Thanks.

Nice up man
Sent from my SGH-T959V using XDA Premium App

If I apply this (without manually doing a factory reset along the way), will I retain all of my apps and app data through this process?
I know I've used ODIN to update to the current stock release and used ODIN on my Vibrant and didn't lose my apps and app data.
Yes, there was some people in another thread that said you ALWAYS lose data when you update. I know they are wrong, but not sure what the case is with this particular update.
Does that fact that it's deodexed make it less likely that the data will be retained?

just flashed and waited 15 minutes on the rainbow screen, flashed again,same thing. how long does it take to boot the first time?

lexluthor said:
If I apply this (without manually doing a factory reset along the way), will I retain all of my apps and app data through this process?
I know I've used ODIN to update to the current stock release and used ODIN on my Vibrant and didn't lose my apps and app data.
Yes, there was some people in another thread that said you ALWAYS lose data when you update. I know they are wrong, but not sure what the case is with this particular update.
Does that fact that it's deodexed make it less likely that the data will be retained?
Click to expand...
Click to collapse
This will erase all apps, you need to use titanium backup first if you want to save that stuff.

Do I place in pda or phone in odin
My Fon is the shizz'nic!

Tommyboy2k said:
Do I place in pda or phone in odin
My Fon is the shizz'nic!
Click to expand...
Click to collapse
place in pda

punkkloser said:
just flashed and waited 15 minutes on the rainbow screen, flashed again,same thing. how long does it take to boot the first time?
Click to expand...
Click to collapse
try hitting the power button quickly it should loop once then work.
which bootloaders are you on?

froyo bootloaders. will try it again.....
K. running smooth now,will test more tommorrow.
I see the wifi signal is weak,as with the previous rom

Strangely enough I have the froyo bootloaders, flashed this, got an upgrade failure to which got me to that annoying ass screen rom upgrade failed, so I tried it again, it was successful, but oddly not only did I not get the rainbow screen but I booted with all my apps and everything intact but confirm that I am now at 2.3.3 by su binary had gotten downgraded to 2 from the ,3 beta I had had and I was coming from the KD1 rom.... Anyway strange I know....
Sent from my SGH-T959V using Tapatalk

aestivalisakito said:
Strangely enough I have the froyo bootloaders, flashed this, got an upgrade failure to which got me to that annoying ass screen rom upgrade failed, so I tried it again, it was successful, but oddly not only did I not get the rainbow screen but I booted with all my apps and everything intact but confirm that I am now at 2.3.3 by su binary had gotten downgraded to 2 from the ,3 beta I had had and I was coming from the KD1 rom.... Anyway strange I know....
Sent from my SGH-T959V using Tapatalk
Click to expand...
Click to collapse
That's strange I wonder if its not clearing everything before flashing. I will look into this.
Sent from my SGH-T959V using XDA Premium App

Flashed last night no problem, but now my phone wont register to my tmobile network.
Sent from my SGH-T959V using XDA App

Thanks my friend!
My Fon is the shizz'nic!

Like I said, weird as hell but no issues and its running beautifully..... Shrugs....im not going to argue lol
Sent from my SGH-T959V using Tapatalk

anyone else having issues registering to there network? ive flashed 3 times now and still cant register to my tmobile network.

dj02 said:
anyone else having issues registering to there network? ive flashed 3 times now and still cant register to my tmobile network.
Click to expand...
Click to collapse
What were you running prior to this flash?
If you are having troubles with this flash please give more info, what rom did you have before, what bootloaders are you using? Any info helps so that I can narrow down any issues and fix them.
Thanks.
Sent from my SGH-T959V using XDA Premium App

corradokng said:
What were you running prior to this flash?
If you are having troubles with this flash please give more info, what rom did you have before, what bootloaders are you using? Any info helps so that I can narrow down any issues and fix them.
Thanks.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
had the fully stock gb rom that shipped with the phone. i was able to flash with no problems, just cant get it to connect to the network just keeps saying searching, wifi calling and txting work just fine.
-edit
oh right after i did the flash, i did do sgs unlock pro app. not sure if that would of caused any problems but it looks like my IMEI is showing up as .[]x[]~ ".[]x[]~

I was having issues with this version and getting stuck on samsung screen a whole lot; and i'm talking about i started clean with KC1 full with .pit>whitehawkxKD1+root>then this rom.
tried the other route and odined back to KD1>boot into cwm>checked mount and flashed the cwm version. worked flawlessly; except the rainbow, ofcourse.
my recommendations are quiet obvious
dj02 said:
Flashed last night no problem, but now my phone wont register to my tmobile network.
Click to expand...
Click to collapse
try toggling airplane mode on & off.

[Q] [SOLVED]home button not working

Okay so.. I have an answer to my problem.. this is a problem that i had encountered many times in forums while i was looking for my answer.. big thanks to diablo2224 for his help and a thanks goes out to Cranvis for actually replying at all..
Okay so the home button wasn't working at all and it would flash and basically do zero (im sure this fix would help any buttons if this was the case). In the end i didnt have much to lose the home button not working was giving me the 'sheets' so i just tried to flash most things for wifi xoom as i was hoping it would crack a difference but it didnt... i ended up seeing a post from stachre for an update and in it was there he had pointed to stock motorola files.. i grabbed these and preformed all wipes (user data, cache, delvik - i doubt it would do much but i did it anyway).. using fastboot i then flashed the boot.img, the system.img, the userdata.img and finally the recovery.img (can always flash over the CWM anway so not a big deal) and booted it back up... suprise suprise the home button was perfectly functional again (every other update/flash of software would seeming 'update' and not actually flash to that portion of the device thereby leaving my problem and the stock images must have actually hit these sectors) i know my answer is long but just trying to be helpful to anyone else with this type of problem (stock Xoom WiFi MZ604 HWI69 images from Motorola)
as a side note : this was followed by flashing the CWM again and booting into CWM and flashing the 2.1 hammer and then wiping user data and booting into the freshly updated rom stoked!
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol

joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem

Cranvis said:
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Click to expand...
Click to collapse
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
Thank you for the speedy reply to my questions. And I am sorry to say, this is one that is over my head. I would suggest that you go to Tiamat's (Or current ROM's) maker and inquire for their help. I am new to some of this but I thought I should at least ask you the basics and make sure on everything. (Woo A+ Tech Training haha!) But unfortunately, I cannot help you with this problem because I do not know what could be doing this other then maybe a line of code didn't get placed into memory when the device was flashed, or maybe there is a small error in the code itself and only certain devices have this problem (different model number = slightly different change to the chip-sets and code of the device.) There are many things that could be the trouble, and like i said, unfortunately, they are out of my understanding of the device.
I do hope that you are able to get an answer soon to your question and I hope it is a simple answer.
Sorry I could not help any more but I hope others can!
Good Luck

joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...

diablo2224 said:
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
Click to expand...
Click to collapse
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I see. I've never heard of this version of the problem. My problem occurred when updating from the 3.1 Rom to the 3.2 Rom. I only had this problem because I didn't wipe data the first time because after it booted up I thought all was well... until I discovered the home button was broken... lol.
Anyways, even I'm at a loss here for how we can solve your problem. A simple data wipe resolved mine in a heartbeat... but it seems your problem is still persistent even after a clean data wipe install... interesting... can't say that I've ever seen a problem stay in the memory even after a complete data wipe...
The only thing I can suggest is to maybe drop back to a stock Rom, maybe 3.1, then installing Tiamat from that fresh stock Rom with another clean data wipe before and after. That's all I can think of since after a data wipe it's still there. Good luck!

I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
That might help. I can help as much as I can, but...
Try to go full stock first before anything. Do not use Tiamat for right now. Install a completely stock, but rooted 3.1 Rom is what I suggest for you to do so that you can see if it's still giving you troubles on a stock Rom.

I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I dunno man, I'm usually one who has great helpful answers, but... uh, this one stumps me. Like I said, I've never seen a problem that still persisted after a data wipe. It's almost as if it is much deeper than a data wipe, but more like something has locked itself into your Xoom's memory and won't leave without forcing it out manually... something must be messing with your system files or something like that. Possibly something left over from the OTA updates of some sort maybe. Very strange...
I would pass this by Team Tiamat. Sorry I can't help this time. Good luck!

I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
So you want someone to have a completely data wiped nandroid backup of the latest Tiamat Rom so that you can use that? That should work, especially if the backup has everything working perfectly. By having the ability to use nandroid backups you have nothing to lose since it can be restored very easily.

im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me

joshndroid said:
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
Click to expand...
Click to collapse
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.

diablo2224 said:
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
Click to expand...
Click to collapse
thanks for ya help... i solved my problem and edited my first post

joshndroid said:
thanks for ya help... i solved my problem and edited my first post
Click to expand...
Click to collapse
Cool! I knew it was something with the system files. Case closed.

RE: Process system is not responding

RE: Process system is not responding
Anybody else ever run into this problem. I restart my phone and process system doesn't work right away. it takes sometimes 5 or 6 reboot attempts before the phone process system runs.
I'm not rooted regular stock.
Sent from my SAMSUNG-SGH-I727 using xda premium

I'm sorry your question makes no sense try explaining a different way

I would suggest rooting and flashing another rom. Sounds to me like something got corrupted.
Sent via smoke signal

yep same problem here. i tried all the answers i found online. havent came up with one that worked yet. not the rom because i just flashed a new one and same problem.
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
alright i fixed it on my phone. i did a full wipe. tell me if i need to explain how to do this. reflashed the ROM and gapps. when i went through the setup the first time there was an option to restore from google. it was checked by default. i left it checked. same problem... system process not responding... wiped and started over and reflashed ROM and gapps. unchecked restore google and it didnt come back. phone hasnt crashed since. the problem lies within the wifi passwords restore. the problem started when i was trying to start wifi. i dont know where to report the bug or i would. good luck and any questions? just quote this so i get an email and ill try to explain if this didnt make sense. hope it helped. if it did consider buying my buddy a beer who is a dev and needs a new computer. http://johntriger-development.yolasite.com/

txt msg help

im running cm9 and hefe kernel. my problem im having with my txt msgs is when i go over 160 characters it fails to send and im not sure why its doing this, im using the "go sms txt msg" app as the stock is annoying and a disturbance due to not being custimizable (yes if your going to say try the stock txt msg app, i have tryed and it still fails to send when over 160 characters) and my friends that i am txting have 3g/4g phones so it shouldnt be an issue, so im wondering if anyone else has come across this issue or knows how to fix the issue as i have looked and havnt found the answer to fixing it. i am also having the issue that when i send a pic msg to anyone 90% of the time they will recieve the txt but not the pic, i am also still unable to send/recieve pics over wifi (not to worried as i can just turn wifi off and send pic or recieve them)

Try changing the modem
Sent from my SGH-T999 using xda app-developers app

Try the KG4 modem. Link in my sig.

jeffsf said:
Try the KG4 modem. Link in my sig.
Click to expand...
Click to collapse
is needing to wipe anything necessary before doing this?
E: whats the differences between the 3 modems that are posted in that link?

Jenovah said:
is needing to wipe anything necessary before doing this?
E: whats the differences between the 3 modems that are posted in that link?
Click to expand...
Click to collapse
not to much, some work better in different areas. you could flash kg4 modem or use go sms or handcent sms, there have to setting that will allow you to make long text

You shouldn't need to do anything but flash.
Then again, backups are cheap insurance
Posted from my AOKP-ified SGS4G

jeffsf said:
You shouldn't need to do anything but flash.
Then again, backups are cheap insurance
Posted from my AOKP-ified SGS4G
Click to expand...
Click to collapse
i made a backup, flashed what you recomended, and instantly after flashing and started up i got a android.system.error has stopped working??? any ideas? i even fixed permissions to see if that would help and the error still came up

i am needing help, i am getting an android.process.acore has stopped working and i have to restore to fix it but it only comes back, should i try reflashing the modem?

Jenovah said:
i am needing help, i am getting an android.process.acore has stopped working and i have to restore to fix it but it only comes back, should i try reflashing the modem?
Click to expand...
Click to collapse
Were you on KJ6 earlier? If so, I would go back to that and just keep that modem, unless you really have major issues with it. If you still are experiencing issues, flash back to stock (either with the heimdall one click or the gremlin remover) and start over.
Sent from my SGH-T959V using xda app-developers app

cpkelley94 said:
Were you on KJ6 earlier? If so, I would go back to that and just keep that modem, unless you really have major issues with it. If you still are experiencing issues, flash back to stock (either with the heimdall one click or the gremlin remover) and start over.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
i was using kg4 as jeff recomended for my txt msg issue
E: i must say i am getting annoyed that every time it reboots on its own, it restores back to the kg4 modem and gives me the android.process.acore error

I would try going back to KJ6, and if that doesn't work, use the heimdall one click back to stock and start again from a clean slate. Sometimes multiple flashes can cause problems within the phone and starting over with a one click is the only way to fix it.
Sent from my SGH-T959V using xda app-developers app

I remember Raver telling someone awhile ago the the android.process.acore error was caused by leftover data from a previous flash. I wood save everything with titanium backup, then reflash the ROM, making sure to wipe caches, data, and factory reset. Then restore your apps with titanium making sure to only restore the apps and not the previous system data.

[Q] Why does this happen? NFC Related

Ok, so I've discovered something interesting. Being the crack flasher I am, I often flip flop between AOSP, the occasional AOKP and TW roms. Seeing as I have a little 7 year old brother, my mother finds it nice to be able to instantly transfer stuff back and forth when dealing with him thru NFC and WiFi direct, so NFC is a big factor for me, in addition to being able to use Google Wallet. I notice that as long as I stick to AOKP/AOSP, my NFC is fine, but the minute I flash a TW rom and go back to AOKP/AOSP, it instantly breaks NFC functionality completely, regardless of me doing anything else.
For instance:
1) Odin back to stock ICS
2) Flash CM10 or any other AOSP/AOKP rom and check NFC functionality and its able to be toggled
3) Flash TW
4) Immediately flash back to CM10 and NFC will be grayed out and unable to be toggled
The same could be said for doing it this way:
1) Odin back to stock ICS
2) Flash TW
3) Immediately flash CM10/AOKP/AOSP rom and check NFC and it's grayed out and unable to be toggled.
What can be going on in TW that completely snaps NFC functionality so that you can't use it in CM10? All the MD5 checksums are valid and none of them have issues when being flashed, so I know it's not in part to doing anything wrong. Also, the only way to fix this is to flash back to a TW rom OR Odin back to stock if you want it to work in CM10 and stick to strictly that styling of ROM.

Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app

I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.

Bern612 said:
I'm not trying to hi-jack your thread, but i have been trying to find a solution to my nfc issue... Have you ran into a situation neither tw or CM10/AOKP/AOSP won't enable. When i try to do it in tw it just jumps back to the off position. and in cm it just stays grayed out.
Click to expand...
Click to collapse
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Have you returned to stock via Odin and observed the same issue still?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited

Bern612 said:
yes i locked, odin back and still same issue. I stole wife battery, put that in my phone. Same issue. i rerooted, have tried every rom i could and still nothing. running beantown 2 now.
The main issue i have is i took it to Verizon, they said they would switch it out but i would lose unlimited
Click to expand...
Click to collapse
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
That's unfortunate but it looks like you need a replacement in this case. Have you contacted Samsung to see if they'll exchange it for you?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No never thought of calling them. I actually thought i could only use verizon. I thinking about just giving it to my son, and getting the note II. My phone is on a business plan and his is on a plan with my wife, so i was going to do it that way.
And sorry digitalsynner85 for stealing your thread

SlimSnoopOS said:
Known AOSP problem, it's not TW.
I don't know the technical reason for why but I have read in passing that you must have NFC checked on the ICS rom PRIOR TO flashing an AOSP rom. NFC is unchecked by default on TW so each time you observed it greyed out in AOSP roms is because you did not leave it turned on within TW. It sounds weird, especially since you wipe data when switching between roms but try it and see what happens.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.

ddurandSGS3 said:
this is the same experience ive had.
if you ever have it greyed out all you need tod o is the followng...
1. nandroid
2. flash a tw rom.
3. enable NFC.
4. Restore nandroid.
5. enable NFC.
hasnt failed for me yet.
Click to expand...
Click to collapse
This is the answer, works great.. Thank the man!

Did you know there is a NFC fix zip in the CM10 nightlies discussion? Flash this in recovery after you flash back to CM10 and it should fix NFC.
Props to the person who made this zip (dont have time to look right now, sorry)

Lol I know about odin'ing back to stock and all that, I was being curious as to the technical reasons as to why flashing a touchwiz rom then going back to cm10, even through a restored backup would cause the nfc capabilities to break, that was the purpose of the thread thanks for everyone's input so far
Beamed via NFC through the local store to the internet from my SGS3.

annoyingduck said:
This is the answer, works great.. Thank the man!
Click to expand...
Click to collapse
It doesn't work 4 me. not at all.
my steps
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.Restore my CM10 nandroid
5.try out NFC. Nothing to do. greyed flag.
Tried also those steps:
1.Nandroid my CM10 14/11
2.Flash tw ICS from Mobile Odin
3.Turn NFC on/off/on (it works)
4.NEW installation CM10
5.try out NFC. Nothing to do. greyed flag.
Any ideas?

Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.

annoyingduck said:
Turn on nfc, sbeam, basically everything. That's weird its not working. What I did was restore a nandroid of Jellybomb, turned on everything, went to recovery, did not wipe anything, restored aosp rom, nfc worked.
Click to expand...
Click to collapse
ok. I'm trying not to wipe anything. do u think wiping could be the problem?

Seams to be. Others reporting the same thing