Develop Bugs

[Q] No data connection after 4.3 update

My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks

mewikime said:
My phone is unlocked and using a MetroPCS sim card, so I couldn't get the OTA update, even on Wifi. After following the instructions at [Download][Install] 4.3 OTA Update, I no longer have data connection on the phone unless I use wifi.
From what I've read, this usually happens because a modem wasn't flashed, but I assumed that the 4.3 update in that thread had a modem. Even so, I entered stock recovery and flashed the modem from the hidden part of Loserskater's post here. But I still have no data.
Does anyone have any ideas what went wrong or what I can do next? I don't mind rooting if that's what I have to do (I plan on it anyway, but didn't know if I should work on getting data first).
Thanks
Click to expand...
Click to collapse
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants

winosxbuntu said:
it could be that, you mixed a leaked modem with a different build thus messing with the final official build or update that ATT released last week
wipe everything if thats possible then download the 4.3 firmware from this link http://www.androidfilehost.com/?fid=23212708291680243 and since you are on stock just download it using odin (use this link if you have no idea of how to use odin) http://droidow.com/galaxy-s3-i747-update-with-ucuemj2-android-4-3-leaked/ but on the PDA part use the file you download from the link above (update43.zip) and that will fix your problems
this may or may not work, i have not tested as i have not updated to 4.3 am waiting for devs to update their roms to 4.3 and then i can go with 4.3/rooting
follow instructions carefully since 4.3 for the S3 is like a virus, this update just leads to HARD BRICKS but dont worry just do everything right and things will be fine
hope you have i747 = ATT not i747m = CANADIANS variants
Click to expand...
Click to collapse
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!

mewikime said:
After hunting through all the settings options, I found that I had nothing in the Access Point Names menu under Mobile Networks. I think because I updated with a Metro-PCS sim card in the phone, rather than an ATT one, for whatever reason I didn't get any APN settings.
So after hunting down T-Mobile's and writing them in, I now have Data. Phew!
Click to expand...
Click to collapse
nice to know you fixed it :laugh:

[Q] HELP!!

Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed

ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.

dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.

ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.

dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?

ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.

dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.

ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.

Did that modem fix some of the problems?

If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .

Second Hand Note II, cannot get cellular data

I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.

GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/

absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse

Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.

Just use your father's sim card. Either it connects to the GSM network or it doesn't.

absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?

1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.

GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.

One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.

absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.

GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!

1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.

GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!

absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?

GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.

absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.

Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649

Wifi going crazy. Need some help.

I know that a lot of people are gonna say to read several other similar threads, but having gone through all of that I still don't get it.
THE SITUATION:
My Samsung Galaxy Note 2 GT-n7100 is :
1) Stock Android 4.1.2 Rooted
2) Modified with Xposed
3) TWRP (Latest, updated regularly)
4) Never been updated ever. Like never ever.
THE A-HOLE PROBLEM:
I honestly never bothered to flash anything on my note 2, since I have all the stuffs working perfectly as it is. Until the god-damn son of a gun WIFI started acting like a sissy she-dog. The problem is that the WIFI keeps on disconnecting itself and reconnecting itself automatically, wierdly enough, only when an app tries to access it. I hope everyone can understand how horrible it is, especially when you are talking dirty to your girlfriend over a whatsapp call and it keeps dropping, just like my errection.
All jokes aside, this has been driving me mad. In-case you need the details, here is what I did to solve my annoying problem :
1) Factory reset.
2) Reboot.
3) Phone works fine. Wifi works fine. Does not disconnect or reconnect. Seems like problem solved.
Then, the camel-crap happens.
4) Open Google play store, it updates. Play services updated. Need it to access the google services.
5) Open any internet enabled app.
6) Wifi switches on/off automatcally.
7) I tear my gonads off.
Side-Note : I also turned off the wifi power saving mode using *#0011#. I also made all the necessary changes in the wifi settings menu.
THE QUESTION:
Since I have never updated, my bootloader, etc are still stock. I read a thread that if I dont update the bootloader, future flashing will not work. I have no earthly clue so as to what the heck am I supposed to do.
I need some simple directions, to the point if possible. I have taken a full nandroid backup, just to be safe.
I think only a CFW now can solve this weird problem of mine. So, any help will be appreciated.

Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.

audit13 said:
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
Click to expand...
Click to collapse
Okay. But, what about the filthy Knox ? Also, what about my root? Also, what about Knox ? Hmm, I wrote knox twice. Now, thrice.
Simply put, knox is poo. I dont want that. So, how do I get the latest knick-knacks without knox. Is it possible to flash the latest bootloader, modem etc.
Sorry for using "noobish". I hate that language too, but when it comes to 40k phones, I get a bit nervous. Hope you can help. Or someone else.
Regards,
TheBasterd.

If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.

audit13 said:
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
Click to expand...
Click to collapse
So, here is the thing. If I go here : http://forum.xda-developers.com/galaxy-note-2/development/rom-resurrection-remix-5-6-0-t3278709 and downloaded the ROM, did all the stuff the ROM maker says and flash it.
Without the latest bootloader and other poo, you are saying that my flash will be unsuccessful ?

That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.

audit13 said:
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
Click to expand...
Click to collapse
Hey audit, thanks for sticking around and helping me bro. I really appreciate that.
So, I took your advice and have put the ROM from Sammobile.com for the latest bootloader and the modem stuffs.
Hope that will work. Also, when I flash the ROm, wont I loose my root ?

Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.

audit13 said:
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
Click to expand...
Click to collapse
Allright ! That was easy. Done and done. Thanks audit. (Thanks hitted)
Now, I will ensure a painless future for all noobs like me by making a tutorial. This thread can be marked as fixed. Thanks audiot bro.

It's great that you resolved the issue.
We're all here to help and learn from each other.

Can't connect to certain Wi-Fi, need help

I just joined in the past few days because I decided to try different ROMs on my i747. This is my 1st ever post, and I thought I'd try out this rooting and flashing that I'm missing out on.
First of all, THANKS to EVERYONE that posts here for all of the help given to me and that others have used. Nice to see people helping out other people in such ways.
Second, I have successfully put a few different ROMs on my i747 over the past few days and can't believe how easy it was. I was always scared to do it. I decided since the thing was just sitting in a drawer not being used "What's the risk?"
Third, my actual issue...No matter what ROM I have on the i747, it will not connect to Wi-Fi at my work. FYI, I work (in IT ironically) in a very large company with hundreds of access points around the campus. So I know it is not the network, as we would have others with the same issue. It connects to all other (that I've tried so far) Wi-Fi networks with no issues.
I just don't understand all the terms bootloader, firmware, kernel, modem etc. I read decriptions (on here) trying to explain and I just can't grasp it.
I was on stock with whatever the last OTA update from AT&T was. I updated the boatloader (I believe) from NE4 to NJ1 to NJ2 using this thread. At least, I'm assuming I did it right. Nothing failed and the Phone Info app looks like it worked. https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Anyone can give me any tips on what I need to do to possible get this working? It's not really a huge deal breaker, it's just bugging me as to why it isn't working.
Thanks in advance!

You upgraded the modem/baseband software when updating the bootloader?

audit13 said:
You upgraded the modem/baseband software when updating the bootloader?
Click to expand...
Click to collapse
I'm guessing no. How do I do that? Don't want to brick it.
I found this link, but what firmware am I on? How do I tell?
https://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577

Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.

audit13 said:
Did you flash the zip or did you flash aboot.mbn? If you flashed the zip, the bootloader and modem would have been updated at the same time.
Click to expand...
Click to collapse
I flashed the zip.

So an unrooted stock ROM also refuses to connect?

audit13 said:
So an unrooted stock ROM also refuses to connect?
Click to expand...
Click to collapse
I don't know how to go back to stock.