Develop Bugs

How to get Google Wallet Working

This'll work right now on Euroskank(CM10) as that's what I'm on. Want to try on something else, try it should work I wont test.
YOU SCREW UP GOOGLE WALLET IT'S ALL ON YOU
What to do...
Move app to system>app
edit build.prop
Code:
ro.product.device=maguro
ro.product.name=yakju
ro.product.model=Galaxy Nexus
reboot
enter Google Wallet
edit build.prop
Code:
ro.product.device=d2tmo
ro.product.name=d2tmo
ro.product.model=SGH-T999
reboot
Give Thanks

got it working

This originally worked for me on stock, but didn't seem to stick for some reason. When I tried to use it a few days later, Wallet just told me that my phone wasn't authorized. I had to go back in and change my build.prop back to the maguro settings. Then it worked just fine.

it opens and I can log in, but I get unsupported device in the upper left corner of app. Does that mean it no work? (sorry, I am noob).
Thanks

i get insecure element
Sent from my maguro using xda app-developers app

qben88 said:
worked on caspers AOKP nightly build 3. should add that after you edit the build prob, go into play store and download wallet. then push the modded wallet from here to system and open up wallet.
Click to expand...
Click to collapse
Why the hell would I add that if 1. I didn't do that. 2. that makes no sense. Just follow the directions and it'll work.

mikew29 said:
it opens and I can log in, but I get unsupported device in the upper left corner of app. Does that mean it no work? (sorry, I am noob).
Thanks
Click to expand...
Click to collapse
It means you are rooted. That's all.

this has an updated wallet that removes the unsupported device message. i followed this for a more permanent solution, not to say this method doesnt work but this is a more widespread method. http://forum.xda-developers.com/showthread.php?t=1794733

qben88 said:
this has an updated wallet that removes the unsupported device message. i followed this for a more permanent solution, not to say this method doesnt work but this is a more widespread method.
I did this and nfc service kept crashing..
Click to expand...
Click to collapse

You guys need this one. I have used this on stock and cm10. On stock u have to flash the NFC tw fix first then this. On cm u just flash this. I used the htc_jewel build.prop. anyways I get no unsupported device bull sit and everything works awesome.
http://forum.xda-developers.com/attachment.php?attachmentid=1236702&d=1343889041

which one did you flash. theres a way to do it with TW and one for all others. read a little bit more and try again. i had to read it a couple times and even went to the original modaco post before i flashed.

Any one else have a crash issue? Mine will vibrate and say Nfc services crashed

omega46 said:
Any one else have a crash issue? Mine will vibrate and say Nfc services crashed
Click to expand...
Click to collapse
Do u guys read? U had to flash the wrong one. Same thing happened to me a long time ago then I tryed the version I posted on page 1 and have been good since

Did as instructed, doesn't say "unsupported device" so that's good. Now I need to test to confirm.
Sent from my S3

Has anyone been able to get this to work on a, LH2 base rom
Sent from my SGH-T999 using Tapatalk 2

sarni84 said:
Do u guys read? U had to flash the wrong one. Same thing happened to me a long time ago then I tryed the version I posted on page 1 and have been good since
Click to expand...
Click to collapse
um yes I read, and followed the basic instructions. Thank you for your witty sarcasm, +1 for you buddy.
Anyway, I followed orig post and got the insecure error. Then went over to the thread with the lib fix and all works well with the exception of the nfc services error. Wondering if anyone on a tw rom is having the same issue or suggestion. Thank you in advance

Ronsha95 said:
Has anyone been able to get this to work on a, LH2 base rom
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
um yes I read, and followed the basic instructions. Thank you for your witty sarcasm, +1 for you buddy.
Anyway, I followed orig post and got the insecure error. Then went over to the thread with the lib fix and all works well with the exception of the nfc services error. Wondering if anyone on a tw rom is having the same issue or suggestion. Thank you in advance
Click to expand...
Click to collapse
Nothing will work on an LH2 base until Sprint gets an update that lib files can be pulled from. For this reason I flashed Wicked ROM and had to temporarily mod the build.prop and flash the latest update.fix file. Haven't tested it yet but I feel confident it will work as setup went smooth once I took those steps. If you are willing to use a ROM version prior to LH2 it will work.

Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.

s0nniez said:
Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.
Click to expand...
Click to collapse
Great! I've got my fingers crossed. If for any reason it should fail this time when I test tomorrow, I'll just wait for Jelly Bean, lol.

s0nniez said:
Thanks for this. I installed wallet a week ago, but couldn't add any cards, saying that it has failed. I just did this on my phone and I could finally add my card. THANKS! Going to go test it out tomorrow. I am on Wicked v5.
Click to expand...
Click to collapse
Tested today and it's working fine! I'm on Wicked V5 too.

will custom roms like cm10/JB allow bell mobile tv to work?

hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!

I just tried mine running task650 aokp and after the app opens it tells me that my device is not supported. But, maybe I'll try changing my build.prop so that it reflects a Bell Canada phone and not an American AT&T phone.....might work....I'll have to get back to you.

I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.

jethro650 said:
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
Click to expand...
Click to collapse
ok good to know, and rom wise what is a good rom to run right now? i notice there is jellybean roms and cm10 rom, well cm10 is jelly bean i know that but whats the differences? i know my old phone, all roms where gingerbread and cm9 was ics, so of course you'd go cm9 if you wanted ics because its your only choice
and not sure device id wise, but i got this for you if it might help, kernel version 3.0.8-20120814.100513-user and build number of imm76d.i747mvlalh1

patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.

BCSC said:
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
Click to expand...
Click to collapse
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks

Octanee said:
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Click to expand...
Click to collapse
The Bell leak is somewhat buggy, but not enough to keep me from using it as a daily. The reason I use it over CM10 is simply because I love Touchwiz. CM10 seems way faster and loads of other benefit, but I think that Samsung has done really well with this as stock. If you don't stay stock, the Bell TV app will not work (to the best of my experience). It all comes down to what you like and what you want to work.

Octanee said:
hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
Click to expand...
Click to collapse
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues

kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,

Octanee said:
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Click to expand...
Click to collapse
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change

kvpxray said:
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
Click to expand...
Click to collapse
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL

Octanee said:
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Click to expand...
Click to collapse
Haha, I think i got it. Yup, so far so good on my phone running CM10, in fact I'm using it right now! hahah.
There's a thread under the development section that tells you how to root without tripping the counter so that no one will know that you've rooted. And I believe that all you have to do to unroot is to flash an original stock rom

Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM

kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
This works for me also running task650's jellybean aokp.

I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app

otoolerc said:
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you reboot after making the changes? I got the exact same message when opening the app. Made the changes and rebooted and started watching TV.

Beautiful, sir.
For the record: I had restarted, initially, but when it didn't work and I went back to the file to review the text once again, I realised I forgot to stick that capital M in there. I changed it, saved it, but still no tv - simply because, I didn't restart again.
Cheers bud.
Sent from my SGH-I747M using xda app-developers app

I'm curious if anyone has got this working with Rogers Live TV. I have edited my build.prop to reflect what has been posted in this thread to no avail. I am running the latest AOKP. I have even taken editing the build.prop as far as modifying the description and fingerprint.

The ro. product.name may be different for Rogers. The rest should be the same. After editing make sure you save the edited file. Hopefully you have a nandroid in case changing something here makes your phone non-booting. After saving the edited file reboot, if that doesn't work reboot recovery wipe cache/dalvic/fix permissions and try that. If none of that works you may have to get a Rogers stock ROM and see what those four lines are on stock and change them to reflect that.
BTW- which app are you using to edit the build.prop?

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?

[Q] Wifi issues/flashing rom

I am flabbergasted at my new note 2. I got it a few weeks ago, I set it up how I wanted it and everything was fine. The wifi at home works flawlessly. When I try to connect at work, it will connect for about 30 seconds and then the wifi turns itself off. I'm now on vacation and the wifi here acts exactly like it does at work, connects for about 30 seconds and then turns off. I have looked all over these forums, including forums on the other iterations of the phone to no avail. I can't seem to get it to work. Any suggestions? Will flashing the ROM potentially fix the problem?
I've been never flashed a phone before, but it sounds like a nightmare for a newb like me. I wouldn't be able to replace the phone if I turned it into a paperweight. Is it worth the risk? I've been trying to do my research, but it's daunting with everything involved. Any suggestions onI certain posts I should read? I just can't stand the bloatware companies add to devices. I do build my own PCs, but that seems like cake compared to flashing a new ROM. I just don't know where to start... Any suggestions would be more than helpful.
Thanks in advance for any help!

Try disabling at the smart wifi app in system settings. That fixed my wifi problems.
Sent from my Nexus 7 using xda app-developers app

Jrockttu said:
Try disabling at the smart wifi app in system settings. That fixed my wifi problems.
Click to expand...
Click to collapse
Wow! That's all it took... Stupid bloatware. This has definitely made up my mind about rooting my phone. If I want to root my note 2 with the Jedi ROM, where should I start looking and learning about doing it. I don't want a super expensive brick... Thanks again for the solution.

Animaljr said:
Wow! That's all it took... Stupid bloatware. This has definitely made up my mind about rooting my phone. If I want to root my note 2 with the Jedi ROM, where should I start looking and learning about doing it. I don't want a super expensive brick... Thanks again for the solution.
Click to expand...
Click to collapse
Read.....read again.....read some more til ur comfortable with what your doing.
http://forum.xda-developers.com/showthread.php?t=1987541
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Flashing ROM
jyazzie110 said:
Read.....read again.....read some more til ur comfortable with what your doing.
http://forum.xda-developers.com/showthread.php?t=1987541
Click to expand...
Click to collapse
I have been reading all morning... I'm still not sure what I need to do exactly. Do I download all of those files to my phone and do everything from here or is part of this process done on the PC? I was reading in a separate part of the forum about having to download Odin (I believe) and using it to flash the ROM? Also, I use AT&T, I'm assuming that's the carrier files I need but I don't see them on the Jedi ROM page. Does this mean Iccan't flash that ROM with my carrier? When it says desired modem, does that mean that's optional or I need to pick one? And do I have to do that at the time of flashing the ROM or can I do that at a later time? What is nandroid and what do I use it for? Next, what is the factory data reset? I've downloaded CWM, do I use that app to wipe the system? How do I actually flash the system? How do I wipe the cache and what is dalvik? What permissions need to be fixed and how do you do that? How do I flash the carrier files, modem and add-ons? Do I need to do that at the time of flashing the ROM or can it be done later?
This is my first attempt at flashing and have no idea what I'm doing, even after days of trying to figure it out. I have a gazillion questions... This forum is amazing and everyone is super helpful, but it would be nice if there were some kind of general flashing guide or maybe a general FAQ. I didn't find the search function of the forums too helpful. It seemed that the results weren't even anything close to what I was looking for. anyway, thanks again for the help and sorry about all the questions.

[Q] help with fixing permissions

I have had a sprint gs 3 and everythhog worked fine except they suck net speed wise.
Anyway I am on the tombile gs 3 now. I love this program called LBE security but in order to get it to work you have to reboot into recovery and fix permissions. This is where my issue starts.
On my sprint version it took a while to fix permissions but on me and my wife's s3 it says it completed but completes almost instantly which makes me think something isn't right. There are no programs for an alternate that I know of.
I used the same flash file I used with the sprint version which was clockwork mod and I even updated it to the touch...same thing..downloaded .tried team win recovery same thing.
Anyone have any ideas here? Rooted running different roms and same thing happens.
Sorry for the typos. Its hard to do this from my phone. I still use a t9 keypad app
Stock kernel i think running tesm infamous newest version

Josh McGrath said:
I have had a sprint gs 3 and everythhog worked fine except they suck net speed wise.
Anyway I am on the tombile gs 3 now. I love this program called LBE security but in order to get it to work you have to reboot into recovery and fix permissions. This is where my issue starts.
On my sprint version it took a while to fix permissions but on me and my wife's s3 it says it completed but completes almost instantly which makes me think something isn't right. There are no programs for an alternate that I know of.
I used the same flash file I used with the sprint version which was clockwork mod and I even updated it to the touch...same thing..downloaded .tried team win recovery same thing.
Anyone have any ideas here? Rooted running different roms and same thing happens.
Sorry for the typos. Its hard to do this from my phone. I still use a t9 keypad app
Stock kernel i think running tesm infamous newest version
Click to expand...
Click to collapse
I use the ROM Manager app for fixing permissions. You can watch it run, then it will prompt you to reboot. It creates a file on your sd card. I have used this app for awhile and it seems to do the job. I was also like you when using recovery to fix permissions and it's over in a second. I don't use ROM manager for anything else though. I use twrp for recovery. Good luck.
Sent from my AT100 using xda premium

Thanks. I will try that. I tried it before and got the failed to fix permissions error. Anything else anyone can think of it could be.

Fixing permissions is pointless anyway. I haven't used it since the original Galaxy.
Sent from my SGH-T999 using Tapatalk 2

When you do it with CWM, it creates a log file. Don't remember where it goes, but it's easy to find. Called fix_permissions.log

Fixing permissions is the only way the lbe program I wanted to use would work since jellybean. Its apparently been abandoned on the market but I found a rough newer version but don't really like or trust is since chinese made and probably has a backdoor as zte and huwei supposedly have
Sent from my SGH-T999 using xda app-developers app

It's probably not safe to trust.

I only fix permissions after i flashed a bunch of **** and my phine starts acting funny. After that it seems to fix it. Other than that I don't bother with it
Sent from Flip's S3

elflip88 said:
I only fix permissions after i flashed a bunch of **** and my phine starts acting funny. After that it seems to fix it. Other than that I don't bother with it
Sent from Flip's S3
Click to expand...
Click to collapse
That's what I do with mine. The lbe will cause reboots over and over until the permission fix is run.
Sent from my SGH-T999 using xda app-developers app