I installed a new kernel last night, the 3.0.17-tuna-faux kernel. Playing around with it afterwards I was pretty impressed, until I went to Google Wallet and it said my NFC was off. I go into settings, click the check box and it immediately unchecks. Just does this over and over.
I'm on stock 4.0.2 ROM...any ideas? Should I try a different kernel or is it something else? I dont get any errors, just keeps unchecking itself. I tried Google searching in vain as all the results are about verizon blocking google wallet
I wanted to install the GummyNex ROM...but after reading about these issues with the NFC chip locking out if you don't properly deregister before upgrading it looks like I might be screwed...I can't get into Google Wallet without NFC turned on...and it won't turn on :/
Any help...and me love you long time.
tahoe916 said:
I installed a new kernel last night, the 3.0.17-tuna-faux kernel. Playing around with it afterwards I was pretty impressed, until I went to Google Wallet and it said my NFC was off. I go into settings, click the check box and it immediately unchecks. Just does this over and over.
I'm on stock 4.0.2 ROM...any ideas? Should I try a different kernel or is it something else? I dont get any errors, just keeps unchecking itself. I tried Google searching in vain as all the results are about verizon blocking google wallet
Click to expand...
Click to collapse
I had this problem on a different rom. The way i got it to turn back on, was to use the GNex toolkit, re-lock the bootloader & return to stock rom. The re-root and re-unlock the bootloader. And install the same rom.
Then NFC worked again.
It done the trick for me.. (if you do the above... remember to backup everything you need, as doing the above will wipe everything)
Good Luck
Sent from my Galaxy Nexus using xda premium
Since I'm on the stock rom, should I just relock reroot and reflash the stock kernel?
If it works, is there anything I should do before flashing a new ROM?
Appreciate the help, going to try your suggestion now!
tahoe916 said:
Since I'm on the stock rom, should I just relock reroot and reflash the stock kernel?
If it works, is there anything I should do before flashing a new ROM?
Appreciate the help, going to try your suggestion now!
Click to expand...
Click to collapse
1. Yes, relocking & unlocking will put you back on stock rom & kernel.
2. Regarding what you should do before flashing the rom. The dev of the rom will state in the OP what you should do.
You will need to re-install rom manager & install CWM, to install any ROM.
Sent from my Galaxy Nexus using xda premium
Saweet man, works like a charm. Thank you so much for sharing your knowledge.
Appreciate it!
tahoe916 said:
Saweet man, works like a charm. Thank you so much for sharing your knowledge.
Appreciate it!
Click to expand...
Click to collapse
No probs buddy. Glad I could help ;-)
Sent from my Galaxy Nexus using xda premium
Hi,
Im new to the Galaxy Nexus and to NFC technology. Im still using my SGSII as my "daily driver" while I get my GNEX all set up the way I like it but this has me curious.
Is this happening to pretty much EVERYONE who has unlocked their bootloader and flashed a custom ROM?
Im going to check my NFC when I get home today and see but I sure hope this is not the case.
I used the wugfresh unlock tool to unlock, root, flash CWM, etc. Are you familiar with that tool?
See siggy for more info about ROM, kernel, etc I have for my GNEX...
Manhattan NFC issue
stuu.f said:
I had this problem on a different rom. The way i got it to turn back on, was to use the GNex toolkit, re-lock the bootloader & return to stock rom. The re-root and re-unlock the bootloader. And install the same rom.
Then NFC worked again.
It done the trick for me.. (if you do the above... remember to backup everything you need, as doing the above will wipe everything)
Good Luck
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Going to try it, I'm on rom Manhattan and NFC doesn't works just in my case
Under Eagleblood or stock 4.0.2 it works.
stuu.f said:
I had this problem on a different rom. The way i got it to turn back on, was to use the GNex toolkit, re-lock the bootloader & return to stock rom. The re-root and re-unlock the bootloader. And install the same rom.
Then NFC worked again.
It done the trick for me.. (if you do the above... remember to backup everything you need, as doing the above will wipe everything)
Good Luck
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Unfortunately it doesn't works... anyone has an another idea? I can't ask the question directly on the thread Manhattan...
tahoe916 said:
...but after reading about these issues with the NFC chip locking out if you don't properly deregister before upgrading it looks like I might be screwed...
Click to expand...
Click to collapse
That is very interesting, can you point me to any thread that you found with this info. Searching but not having a lot of luck.
Related
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app
Everything must must be bone stock to install an ota.
Jellin' like a felon
The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.
Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2
And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.
Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app
HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?
Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.
alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!
gorealmighty said:
alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!
Click to expand...
Click to collapse
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
mjg688 said:
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.
gorealmighty said:
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.
Click to expand...
Click to collapse
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!
-EViL-KoNCEPTz- said:
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!
Click to expand...
Click to collapse
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!
gorealmighty said:
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!
Click to expand...
Click to collapse
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!
-EViL-KoNCEPTz- said:
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!
Click to expand...
Click to collapse
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!
gorealmighty said:
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!
Click to expand...
Click to collapse
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!
-EViL-KoNCEPTz- said:
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!
Click to expand...
Click to collapse
got stuck n a boot loop a dozen times, finally said to hell with it and found a stock .tar.MD5 and Odin'd this pig. Again, I appreciate y'alls' help.
Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2
loumoli said:
Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
TWRP. I was trying to flash Jellybam over CM10 . I got stuck in a boot loop, soft bricked it twice and removed my OS once (able to recover from TWRP) im playing around with it tonight.
I successfully unrooted my phone but it still shows up as modified. I'm wondering what I did wrong and if there's another way to go about it. Here's what I did.
Used Triangle Away to reset my binary. It said it was successful and shows my count as "0". Then I downloaded the Bell stock firmware for my phone, sgh-i747m. The md5 checked out. I then tried flashing using mobile odin. Still shows as modified. I then tried it all again with pc version of Odin. Everything boots up. I was unrooted and even though I reset my binary I'm seeing "modified" under settings/status.
Has anyone encountered this before? Any work arounds?
Sent from my SGH-I747M using xda app-developers app
marocca said:
I successfully unrooted my phone but it still shows up as modified. I'm wondering what I did wrong and if there's another way to go about it. Here's what I did.
Used Triangle Away to reset my binary. It said it was successful and shows my count as "0". Then I downloaded the Bell stock firmware for my phone, sgh-i747m. The md5 checked out. I then tried flashing using mobile odin. Still shows as modified. I then tried it all again with pc version of Odin. Everything boots up. I was unrooted and even though I reset my binary I'm seeing "modified" under settings/status.
Has anyone encountered this before? Any work arounds?
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
BWolf56 said:
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
Click to expand...
Click to collapse
I guess I needed a little "more" searching but thanks a lot for the info!
Sent from my SGH-I747M using xda app-developers app
BWolf56 said:
A little search would've gave you your answer. Simply factory reset and it won't show ''modified'' anymore.
*Know that it will clear all your data*
Click to expand...
Click to collapse
So I did it all again and did the factory reset. Still modified.
Sent from my SGH-I747M using xda app-developers app
marocca said:
So I did it all again and did the factory reset. Still modified.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Mind if I ask why you don't want it to show modified?
Also, little clarification: by flashing 4.1.1 (stock), you will get the modified status.
BWolf56 said:
Mind if I ask why you don't want it to show modified?
Also, little clarification: by flashing 4.1.1 (stock), you will get the modified status.
Click to expand...
Click to collapse
I fully admit to being a noob, but it seems that when I try to check for updates on my phone it gives me a message saying that my device has been modified and updates are not available for it. I've been spent months flashing and trying out different ROMS and just wanted to revert fully back to stock for a bit. I love using Bluetooth Audio streaming and have never had as good of audio quality as I did with stock. I understand that playing around with drivers and kernels could help that with custom rom but until i'm more knowledgeable about that kind of stuff I didn't want to flash anything.
Just before I checked this message I realized that I've been flashing 4.1.1 stock and figured that's where my problem lies. Currently downloading stock ICS for Bell.
Thanks again!!
marocca said:
I fully admit to being a noob, but it seems that when I try to check for updates on my phone it gives me a message saying that my device has been modified and updates are not available for it. I've been spent months flashing and trying out different ROMS and just wanted to revert fully back to stock for a bit. I love using Bluetooth Audio streaming and have never had as good of audio quality as I did with stock. I understand that playing around with drivers and kernels could help that with custom rom but until i'm more knowledgeable about that kind of stuff I didn't want to flash anything.
Just before I checked this message I realized that I've been flashing 4.1.1 stock and figured that's where my problem lies. Currently downloading stock ICS for Bell.
Thanks again!!
Click to expand...
Click to collapse
If you want a ROM that has working BT streaming, try Task's AOKP.
BWolf56 said:
If you want a ROM that has working BT streaming, try Task's AOKP.
Click to expand...
Click to collapse
I love Task's AOKP. It's the one I always returned to and used the most, but with any rom I tried the BT audio always had a bit of clipping/overdrive. I tried adjusting my volume levels but it wouldn't go away. I never tried other kernels, modems or drivers and suspect that the solution to that problem could be found in one of those, but like I stated above, I'm not knowledgeable enough yet. Wouldn't feel confident messing around with kernels and modems. And I always seemed to be on the modem intended for Bell users.
Here is what I did, this was on a Note 2, flashed back to stock rooted, ran triangle away, uninstalled superuser then flashed a stock rom without root. It may be the long away to the end but it worked.
I ended up getting it to work. Flashed stock ICS then upgraded to Jelly Bean.
Sent from my SGH-I747M using xda app-developers app
PLEASE TAKE THE TIME TO READ, THANK YOU.
Hello,
I am a Galaxy Nexus user, non rooted, running Android version 4.3. Yesterday I was running 4.2.2 and everything was fine and running as normal. Keep in mind I never rooted my phone, although I have to others in the past. My Nexus was running pure official 4.2.2. I had been waiting for the 4.3 update and was extremely excited when I was the notification that it was ready for my phone. I quickly downloaded it and then it rebooted the phone, as any update should. That's where everything went downhill. The phone started to lag immediately when I turned it on. It was sputtering and jerking but I just thought it was getting used to the update. Then the phone would loose its onscreen buttons and turn the page that I was looking at full screen (meaning I couldn't press home or back, because they simply just weren't there). Then the phone froze all together and after waiting 20 minutes I finally took the battery out and tried again. The EXACT same thing has been happening ever since yesterday and it has made the phone unusable because it will freeze 5 minutes into turning it on. And we then screen times out, the screen will not turn back on, as if the phone was off, when it is not. I'm very frustrated because the phone was working flawlessly before the update and now I have to use my retired G1 because the phone is that unresponsive. I was just hoping someone could please help me, or has a similar story and could make this known to Google. Thank you for reading, please if you can, help me.
Justin
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Carlos_Manuel said:
Wipe cache and dalvik cacheand flash stock factory images through fastboot
Then flash the latest root files superSU 1.45 and then everything will be okay again.
Click to expand...
Click to collapse
Did you even read the post? He's never rooted and 100% stock.
Sdobron said:
Did you even read the post? He's never rooted and 100% stock.
Click to expand...
Click to collapse
Whoops. Sorry I read that quickly... Anyway flashing JB 4.3 factory images should fix that...
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
ferozfero said:
His systemui .apk is force closing.. Reflash if ur gonna root .. Or wie data... Best method root and flash.. Seems to be a very simple fix..
Click to expand...
Click to collapse
Since he didn't root his Galaxy Nexus, this method should make him lose all apps data or even internal storage since he has to unlock his bootloader for root.
But it seems to be the only method.
It's time for a full wipe.
Sent from my Nexus 4 using Tapatalk 4 Beta
I had exactly the same problem so I did factory reset from phone settings 2 days ago and now is just like a new phone working great.
There are just too many changes google did in ~6 months so full wipe is necessary.
Sent from my Galaxy Nexus using xda app-developers app
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
teddy_irish said:
Here is my advice: use Nexus toolkit from the development section. Perform the unlock and then flash the factory image. Download it before to start. I always do that way with the new updates. Wipe ewerything. It's worth it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Please don't use a toolkit.
Just use fastboot commands.
Beauenheim said:
Please don't use a toolkit.
Just use fastboot commands.
Click to expand...
Click to collapse
Right, and it's safe.
Please backup all your data before you do it.
Hello XDA community, my brother has been having wi-fi and bluetooth issues on his T-MO Note II ever since applying the 4.3 OTA. Before I go on, the first thing I did was use CF-auto root and flash both agni pure stock and devil kernel and neither of them have worked. In addition, I have used dr.ketans patch as well as flashing some AOSP based ROMs such as AOKP and SlimKat and neither of them have yielded any results. I have tried almost everything I can find via XDA and I am truly stumped.
Do you guys have any solutions to the wifi issues? Any help would be greatly appreciated! :good:
Can you elaborate, what wifi issues ?
Frequent disconnects ?
Battery drains ?
Sent from my SGH-T889 using xda app-developers app
Wi-fi wil not turn on whatsoever. I can press the icon to turn it on and it will slide to the on position greyed out, and then go back to off right away. The same for bluetooth as well.
If the phone was already on 4.3 then wifi patch was not needed.
I would advise to flash stock image and start fresh. Make sure to wipe dalvik-cache after flashing stock ROM.
Sent from my SGH-T889 using xda app-developers app
Thanks, I will try that when I can. By any chance do you know where I can find a 4.3 image? I've tried looking into the stickies over at the Dev section and they don't have 4.3 as far as I can recall. The only 4.3 image I see is the stock root injected one from Mr.Robinson.
You can download one from sammobile.com. You will have to register though, make sure you download the file for sgh-t889.
Sent from my SGH-T889 using xda app-developers app
Thank you very much. I will do that tomorrow as I do not have the device with me at the current moment. I will let you know how it goes!
to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download
Squilchi said:
to clarify: http://samsung-updates.com/device/?id=SGH-T889 thats what you need to download
Click to expand...
Click to collapse
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.
leikamkei said:
Ah man, thanks! Unfortunately, I had just finished making an account at SamMobile not too long ago and the download should be finishing up soon. I greatly appreciate the help.
Click to expand...
Click to collapse
Cool cool just wanted to make sure you got the right tar file. Best of luck
Sent from my N7105 using Tapatalk
I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?
leikamkei said:
I just wanted to say thank you to both ciphercodes and Squilchi for all your help. My brother also says a big thanks as he doesn't have an account here. When the Note II finished rebooting from the image flash via Odin, I almost freaked out because nothing had seemingly changed but then I realized I was already on the 4.3 OTA. I also had an spectacular noob moment by forgetting to wipe cache in stock recovery. After I did that, I am glad to report that Wi-fi and bluetooth work as it's supposed to. I can't say thank you enough. In the odd occasion that this should happen again, a wipe of cache in stock recovery should be okay correct?
Click to expand...
Click to collapse
Glad to know issue was resolved. By default it's highly unlikely that these problems will return on a stock ROM but if they do then flashing back to stock is the most optimal solution.
Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app
leikamkei said:
Unfortunately I may have spoken too soon. Wi-Fi was working just fine for a bit but suddenly it can't connect to the network nor see any other networks. It can still turn on but connecting to remembered networks and seeing other networks are a no-go. Bluetooth is wonky as well. I'm starting to think it's hardware but I doubt it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So close! Hmm it could be hardware I'm not sure either. What are the wifi settings? Also are there any error messages? Did you wipe data after Odin?
Sent from my N7105 using xda app-developers app
I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app
leikamkei said:
I have yet to wipe data since it seemed okay although the notion has been floating in my head. I did wipe cache and shortly after, it didn't work. I suggested unforgetting the network and adding it again and that seemed to work for a little while. No error messages, just the same slide to on greyed out and back to off.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app
Squilchi said:
Its weird that it was working and now its not wiping data couldnt hurt. Do you have Odin 3.0.9? Flash that tar file again and make sure bootloader update is checked.
Sent from my N7105 using xda app-developers app
Click to expand...
Click to collapse
Just a little update, I booted to stock recovery and performed a factory reset and wipe cache partitions but still nothing after it booted. To answer your question, I did use Odin 3.09 and it was already on MK7 prior to my first flash of the tar file in Odin. This is so frustrating.
Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....
leikamkei said:
Sorry for the double post, but I just did a factory reset and wipe cache and just re-flashed the tar file with update bootloader ticked and still a no-go. It's a shame the 4.3 update has borked my brother's Note II to this extent but it seems like the majority of people don't experience this. I'm stumped....
Click to expand...
Click to collapse
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?
Squilchi said:
im stumped man... have you tried any custom roms?? flashing mk7 stock kernel?
Click to expand...
Click to collapse
Prior to all this madness, I did try flashing JediMasterX2(I think) and AOKP, two ROMs that I would heavily associate with being stable and basically have everything work. Unfortunately, they didn't work. After all that went down and I restored my backed-up OTA all the way to now, it has been on MK7 stock kernel since then. I'm about to flip a table or something.