Trying to upgrade to custom 4.3 roms and have run into an issue (been at this for almost 48 hours, I can't get anything to work at this point so I'm quite frustrated).
Upon flashing a 4.3 custom rom, wifi stopped working, so I sought a solution to that. After wiping and installing several different ROMs with the same result, i ODIN'd a stock 4.3 (so now i have that knox counter). That didn't work either. I ended up flashing that Dr wifi patch, which finally got my wifi to search properly.
But wait, there's more!
I get no mobile service now. Phone doesn't recognize SIM, no baseband, no IMEI, no nothing. All other 4.3 roms give the same result. All other functions seem to work. Re-flashed modem, didn't fix it. Tried to use NV items reader/writer to write my IMEI back, but every time I try to read the phone it fails.
Also been trying to flash a Jedi x20, but every time it just boot loops me right back into recovery.
I'm stuck, and I need help.
I read somewhere using SELinux Mode Changer
Sent from my SGH-T889 using XDA Premium 4 mobile app
Neomop said:
Trying to upgrade to custom 4.3 roms and have run into an issue (been at this for almost 48 hours, I can't get anything to work at this point so I'm quite frustrated).
Upon flashing a 4.3 custom rom, wifi stopped working, so I sought a solution to that. After wiping and installing several different ROMs with the same result, i ODIN'd a stock 4.3 (so now i have that knox counter). That didn't work either. I ended up flashing that Dr wifi patch, which finally got my wifi to search properly.
But wait, there's more!
I get no mobile service now. Phone doesn't recognize SIM, no baseband, no IMEI, no nothing. All other 4.3 roms give the same result. All other functions seem to work. Re-flashed modem, didn't fix it. Tried to use NV items reader/writer to write my IMEI back, but every time I try to read the phone it fails.
Also been trying to flash a Jedi x20, but every time it just boot loops me right back into recovery.
I'm stuck, and I need help.
Click to expand...
Click to collapse
Install this app and let us know which bootloader you are running if you cam boot at all. https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
What your story indicates and what your results are don't sound typical. Also, which device are you running (according to the sticker under the battery)? Is this a device you bought new or is it one you bought used, if used when did you get it and did it work before?
Which modem did you flash and using which method?
Hastily spouted for your befuddlement
@technogadget I have tried to set permissive via Selinux modechanger, didn't work
@Coug76
Device was bought new Dec 2012. Prior to this issue I had been using Liquid-JB-v2.37-OFFICIAL-t0ltetmo with no issues (other than awful battery)
Phone INFO:
Bootloader Version: T889VVLUCMK4
Under the battery -
Model: SGH-T889V
Most recently flashed a MK7 modem from http://forum.xda-developers.com/showthread.php?t=2564430 via TWRP hoping it would revive network functions, no dice.
Neomop said:
@technogadget I have tried to set permissive via Selinux modechanger, didn't work
@Coug76
Device was bought new Dec 2012. Prior to this issue I had been using Liquid-JB-v2.37-OFFICIAL-t0ltetmo with no issues (other than awful battery)
Phone INFO:
Bootloader Version: T889VVLUCMK4
Under the battery -
Model: SGH-T889V
Most recently flashed a MK7 modem from http://forum.xda-developers.com/showthread.php?t=2564430 via TWRP hoping it would revive network functions, no dice.
Click to expand...
Click to collapse
You are on a Canadian Note 2 then. You should flash the LUCMK4 rom for your device's original carrier from this thread and factory reset. Once you have done that boot and ensure that you have baseband. One fellow reported that flashing the a tmo modem was tough to fix on his Canadian Note 2.
http://forum.xda-developers.com/showthread.php?t=1975560
Hastily spouted for your befuddlement
Coug76 said:
You are on a Canadian Note 2 then. You should flash the LUCMK4 rom for your device's original carrier from this thread and factory reset. Once you have done that boot and ensure that you have baseband. One fellow reported that flashing the a tmo modem was tough to fix on his Canadian Note 2.
http://forum.xda-developers.com/showthread.php?t=1975560
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Just tried your recommendation. Still no baseband.
Neomop said:
Just tried your recommendation. Still no baseband.
Click to expand...
Click to collapse
What does that app from a couple posts up show for your modem/baseband? Canadian devices seem to want Tmo modems to stick tight.
Hastily spouted for your befuddlement
Coug76 said:
What does that app from a couple posts up show for your modem/baseband? Canadian devices seem to want Tmo modems to stick tight.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Baseband version and modem board are both blank.
You might give Kies emergency recovery a shot. That Canadian modem swap bit is harsh. I think Teshx had a thread about the subject at one point. I think he just ran the tmo modem... That doesn't seem to work for tie device though.
Hastily spouted for your befuddlement
Related
Hello there. Just wanted a question answered. I just bought a note 2 (coming from the HTC One) to try the note line without breaking the bank. What I wanted to know is if I could flash international note 2 ROMS on the tmobile version of the note 2. I'm loking for a ROM that basically mimicks a lot of the note 3's functions and also has unique looks and customization with exposed and wannam. I think I came across one on the At&t forums so I also wanted to know if we could openly flash At&t roms on this variant of the phone as well without issues. Also, ive read a little and have seen many posts about issues with wifi and fixing it with some kernels. Can someone elaborate on that please? Thank you for your time.
osmosizzz said:
Hello there. Just wanted a question answered. I just bought a note 2 (coming from the HTC One) to try the note line without breaking the bank. What I wanted to know is if I could flash international note 2 ROMS on the tmobile version of the note 2. I'm loking for a ROM that basically mimicks a lot of the note 3's functions and also has unique looks and customization with exposed and wannam. I think I came across one on the At&t forums so I also wanted to know if we could openly flash At&t roms on this variant of the phone as well without issues. Also, ive read a little and have seen many posts about issues with wifi and fixing it with some kernels. Can someone elaborate on that please? Thank you for your time.
Click to expand...
Click to collapse
Ditto Note 3 would work fine for u. Check out SkyNote as well.
Smack that Thanks button if I helped!
XDAing from a N7105 powered by Illusion ROM.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
osmosizzz said:
... Also, ive read a little and have seen many posts about issues with wifi and fixing it with some kernels. Can someone elaborate on that please? Thank you for your time.
Click to expand...
Click to collapse
If your T-889 is still on a 4.1.2 software version and hasn't been updated to 4.3 you may experience wifi initiation problems on 4.3 touchwiz based roms.
You can remedy this by either updating to the new official 4.3 version which installs the knox enabled bootloader, or use PC odin to flash Dr Ketan's bootloader to enable the rom and device to work out wifi start up. A third option is flashing a custom kernel specially the devil kernel by derteufal1980. I have had mixed experience with devil kernel but overall it is good. I personally stock with the stock kernels as they do everything pretty well.
Personally I would go with the Dr Ketan bootloader patch option as it doesn't "burn any bridges" or limit future use like the official bootloader can (causing version regression hassles, allowing knox to pop e-fuses etc). Using the bootloader patch will allow things such as triangle away to work so that you can get back to official stock status for whatever reason you have (selling the device, return for factory service etc).
Others will tell you differently for a variety of reasons that are, at least partially IMHO, valid in a practical sense. Their opinion is valid for their circumstance, I have different needs than they do. YMMV.
If you flash the Dr Ketan bootloader patch you will also want to flash the current modem. There's are odinable versions and some for installation with a custom recovery. They are all the same except for the installation method. If you choose the official upgrade methods you will automatically get the new modem during the process.
There is no downside to installing the current modem, it makes signal acquisition for LTE quicker and I haven't seen it do anything worse than the previous versions.
Before installing anything read all the applicable thread info and check your md5 data.
Hastily spouted for your befuddlement
Irwenzhao said:
Ditto Note 3 would work fine for u. Check out SkyNote as well.
Smack that Thanks button if I helped!
XDAing from a N7105 powered by Illusion ROM.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Click to expand...
Click to collapse
Got cha. Thank you! I was checking out that rom too. Looks clean and nice. so im assuming being t-mobile phones, if we want to flash international version rom, the section that must be used is the 7105 correct?
Coug76 said:
If your T-889 is still on a 4.1.2 software version and hasn't been updated to 4.3 you may experience wifi initiation problems on 4.3 touchwiz based roms.
You can remedy this by either updating to the new official 4.3 version which installs the knox enabled bootloader, or use PC odin to flash Dr Ketan's bootloader to enable the rom and device to work out wifi start up. A third option is flashing a custom kernel specially the devil kernel by derteufal1980. I have had mixed experience with devil kernel but overall it is good. I personally stock with the stock kernels as they do everything pretty well.
Personally I would go with the Dr Ketan bootloader patch option as it doesn't "burn any bridges" or limit future use like the official bootloader can (causing version regression hassles, allowing knox to pop e-fuses etc). Using the bootloader patch will allow things such as triangle away to work so that you can get back to official stock status for whatever reason you have (selling the device, return for factory service etc).
Others will tell you differently for a variety of reasons that are, at least partially IMHO, valid in a practical sense. Their opinion is valid for their circumstance, I have different needs than they do. YMMV.
If you flash the Dr Ketan bootloader patch you will also want to flash the current modem. There's are odinable versions and some for installation with a custom recovery. They are all the same except for the installation method. If you choose the official upgrade methods you will automatically get the new modem during the process.
There is no downside to installing the current modem, it makes signal acquisition for LTE quicker and I haven't seen it do anything worse than the previous versions.
Before installing anything read all the applicable thread info and check your md5 data.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Thanks for the information! really apprciate it. Hopefully the phone is not updated to 4.3. I'm receiving it tomorrow. will definitely flash that bootloader for sure. Thanks for the awesome tip!
osmosizzz said:
Thanks for the information! really apprciate it. Hopefully the phone is not updated to 4.3. I'm receiving it tomorrow. will definitely flash that bootloader for sure. Thanks for the awesome tip!
Click to expand...
Click to collapse
Before you flash anything, boot into stock recovery mode and check if the screen has a line saying knox warranty void or something similar. If I only has device counter you can go ahead and do what you need to do. Once the knox bootloader is installed, there is no going back (a big reason why I prefer the patch option).
If it has one that mentions knox counter don't bother with flashing any bootloader stuff as it is already been taken down the 4.3 update path.
Hastily spouted for your befuddlement
Coug76 said:
Before you flash anything, boot into stock recovery mode and check if the screen has a line saying knox warranty void or something similar. If I only has device counter you can go ahead and do what you need to do. Once the knox bootloader is installed, there is no going back (a big reason why I prefer the patch option).
If it has one that mentions knox counter don't bother with flashing any bootloader stuff as it is already been taken down the 4.3 update path.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Wow, Seems like knox is a giant headache from what you;re telling me. But even if it has the knox bootloader, will i be able to root, flash a custom recovery and custom rom or knox totally just kills that?
osmosizzz said:
Wow, Seems like knox is a giant headache from what you;re telling me. But even if it has the knox bootloader, will i be able to root, flash a custom recovery and custom rom or knox totally just kills that?
Click to expand...
Click to collapse
Knox is an obstacle to be dealt with. You can do all those things with it. Doing things like reverting to previous versions of Android are more frustrating (and less obvious) than with the old bootloader.
Also, once the knox bit is tripped there is no known revert method. If you ever need knox functionality you are out of luck. Most people will never need it at this point. Samsung may or may not decide that the warranty is invalid based on knox counter status. People have stated both Ok and void results. YMMV.
Rooting a knox enabled rom can be tricky but doable as long as you follow the processes outlined in the guides.
Me personally, odin flashing the wifi patch (and modem) was by far preferable. Both can be found in the Tmo gn2 forum right here in river city.
Having said all that, some quality time reading and deciding what is important for you personally will take you far with this device. It really is a great phone and extremely capable.
Best of luck to you.
Coug76 said:
Knox is an obstacle to be dealt with. You can do all those things with it. Doing things like reverting to previous versions of Android are more frustrating (and less obvious) than with the old bootloader.
Also, once the knox bit is tripped there is no known revert method. If you ever need knox functionality you are out of luck. Most people will never need it at this point. Samsung may or may not decide that the warranty is invalid based on knox counter status. People have stated both Ok and void results. YMMV.
Rooting a knox enabled rom can be tricky but doable as long as you follow the processes outlined in the guides.
Me personally, odin flashing the wifi patch (and modem) was by far preferable. Both can be found in the Tmo gn2 forum right here in river city.
Having said all that, some quality time reading and deciding what is important for you personally will take you far with this device. It really is a great phone and extremely capable.
Best of luck to you.
Click to expand...
Click to collapse
Great. thanks for your time! really appreciated.
Hello to all. Is it possible to transform a Tmobile Note 2 into an ATT Note 2 using this ROM http://forum.xda-developers.com/showthread.php?t=2568537 ? I tried searching but couldnt find anything on it and since the ROM says its multicarrier I wanted to know if it was possible. I intend to use that Note 2 on net10 by the way. Thanks in advance!
Whatever you do, don't flash the AT&T note 2 modem. You can't make a T889 into a I317. You can make it look and mostly act like one though.
Hastily spouted for your befuddlement
Coug76 said:
Whatever you do, don't flash the AT&T note 2 modem. You can't make a T889 into a I317. You can make it look and mostly act like one though.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
So, If I intend to use the T889 with net10, which modem should I install in order for the phone to get LTE?
sentinel5000 said:
So, If I intend to use the T889 with net10, which modem should I install in order for the phone to get LTE?
Click to expand...
Click to collapse
As long as your note 2 is unlocked, you will be able to get LTE on AT&T. You can use the current ROM that you are using now... Nothing had to be done/changed. Just pop in the new SIM, put in the correct APN, and you're good to go.
kozmo21 said:
As long as your note 2 is unlocked, you will be able to get LTE on AT&T. You can use the current ROM that you are using now... Nothing had to be done/changed. Just pop in the new SIM, put in the correct APN, and you're good to go.
Click to expand...
Click to collapse
I see. Well then problem is my T889 is not unlocked, so I was thinking about downgrading it to 4.1.1. unlock it and then upgrade to 4.3. Thing is, How do I upgrade to 4.3? Cant seem to find the 4.3 stock rom here. The instructions on the jedi rom say one needs to be on 4.3 for wifi to work.
sentinel5000 said:
I see. Well then problem is my T889 is not unlocked, so I was thinking about downgrading it to 4.1.1. unlock it and then upgrade to 4.3. Thing is, How do I upgrade to 4.3? Cant seem to find the 4.3 stock rom here. The instructions on the jedi rom say one needs to be on 4.3 for wifi to work.
Click to expand...
Click to collapse
UVALJ1 modem on a T889 *should* get you to the point of being able to unlock. If not, odin the whole package (UVALJ1). MrRobinson's root66 works great.
If you have the 4.3 knoxed bootloader you may have issues with reverting.
Hastily spouted for your befuddlement
Coug76 said:
UVALJ1 modem on a T889 *should* get you to the point of being able to unlock. If not, odin the whole package (UVALJ1). MrRobinson's root66 works great.
If you have the 4.3 knoxed bootloader you may have issues with reverting.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I see. Well I have a T889 that had to be sent to samsung because the board died. Before it died, the phone had 4.1.2 and when it was returned fixed, the phone had 4.3. So, If I flash the UVALJ1 modem on my 4.3 T889 (stock non rooted) will I be able to unlock using this method: http://forum.xda-developers.com/showthread.php?t=2176721 or is that only for 4.1.1?
sentinel5000 said:
I see. Well I have a T889 that had to be sent to samsung because the board died. Before it died, the phone had 4.1.2 and when it was returned fixed, the phone had 4.3. So, If I flash the UVALJ1 modem on my 4.3 T889 (stock non rooted) will I be able to unlock using this method: http://forum.xda-developers.com/showthread.php?t=2176721 or is that only for 4.1.1?
Click to expand...
Click to collapse
Dunno. You could ask in the thread, someone there may know. Good question though.
Hastily spouted for your befuddlement
Coug76 said:
Dunno. You could ask in the thread, someone there may know. Good question though.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone
sentinel5000 said:
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone
Click to expand...
Click to collapse
You might have luck flashing the UVALJ1 modem only. If that is successful, the unlock should work.
Hastily spouted for your befuddlement
sentinel5000 said:
Ok. So I tried flashing in Odin Mr. Robinsons 4.1.1 image in order to unlock my phone, Tried it 3 times but it always resulted in a Fail. I searched a bit and apparently the Knox thing prevents from downgrading so I flashed Mr. Robinsons 4.3 image and to my surprise the phone booted back up like it was before, all my settings, everything was there. Only new thing is that now my T889 was rooted... Which is a good thing but still I cant unlock my phone
Click to expand...
Click to collapse
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!
Coug76 said:
You might have luck flashing the UVALJ1 modem only. If that is successful, the unlock should work.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Ok, So I finally found the UVALJ1 modem and flashed it on my T889. Tried the unlock method and it worked like a charm. Thanks for all that tried to help and to Cough76, that was a great suggestion. :good:
LanceDiamond said:
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!
Click to expand...
Click to collapse
Well, Flashing the UVALJ1 modem on my T889 with the Jedi Master X 4.3 custom ROM worked like a charm. There was no need to flash the whole image. Just the modem was enough. Hope it helps for those who are on 4.3 and need to unlock their Note 2.
Let me ask this using the same thread just to not open a new one. Well my new question is, After I flashed the UVALJ1 modem I was able to unlock the phone but I noticed I cant get 4GLTE anymore. So If I flash the newest modem for 4.3 will I lose Unlock on the phone? Thanks in advance!
No unlock sticks
Sent from my Nexus 7 using Tapatalk
sentinel5000 said:
Let me ask this using the same thread just to not open a new one. Well my new question is, After I flashed the UVALJ1 modem I was able to unlock the phone but I noticed I cant get 4GLTE anymore. So If I flash the newest modem for 4.3 will I lose Unlock on the phone? Thanks in advance!
Click to expand...
Click to collapse
You'll be fine. It should stick with you.
As you found out, UVALJ1 doesn't support LTE. It gave my phone epic battery life though. The original rom was phenomenal on battery. Subsequent releases lowered battery life until LTE was support dropped then battery was relatively crappy. It always had to hunt for LTE which sucked as it released when Las Vegas was the only market tmo supported.
Hastily spouted for your befuddlement
Coug76 said:
You'll be fine. It should stick with you.
As you found out, UVALJ1 doesn't support LTE. It gave my phone epic battery life though. The original rom was phenomenal on battery. Subsequent releases lowered battery life until LTE was support dropped then battery was relatively crappy. It always had to hunt for LTE which sucked as it released when Las Vegas was the only market tmo supported.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Yeah I noticed that flashing the UVALJ1 modem gave my Note 2 excellent battery life. Since here where I'm from T mobile just has 3 small areas of LTE and none apply to me then Ill just stay with UVALJ1. Thanks again!
little more help
LanceDiamond said:
I've got the same phone and, thanks to my recently flashing (with Odin) to 4.3 Stock, I think I'm in about the same situation if I were to want to revert. As I understand, once you've gone to the stock 4.3 bootloader - however you got there, via Odin flash, OTA update or factory returns phone to you with it - you can no longer use Odin to revert anything because with Odin you're flashing an entire image - bootloader, modem, ROM, Kernel - and you now need to cherry pick non-bootloader items you'll revert. You can't get rid of the locked down 4.3 bootloader at all.
I am hoping we can still use Odin to at least go back to stock 4.3. I'm actually going to try that in a bit and mess with my flash counter - it seems to not want to reset that's another subject.
I'm not sure if the 4.3 bootloader prevents going back to an older modem or not - I might try that too and see what happens. If it does not, then these steps might get you back to an unlockable state - might also trip your Knox Warranty Void along the way in case if that concerns you. Mine is tripped and I'm really not sure why or when it happened.
1) Get GooManager off Play Store and use it to install custom recovery - you need this because you can no longer just flash an entire pre-4.3 image thanks to the 4.3 bootloader
2) Using custom recovery, flash UVALJ1 modem & Odexed or Deodexed ROM from here: http://forum.xda-developers.com/showthread.php?t=2102380
If it'll boot at this point, you should be able to do the unlock thing - this is how I originally unlocked mine last April - but that was pre-4.3-locked state for me. If we cannot get back to that unlockable state, I'm going to be really sorry I knowingly let myself get locked down by 4.3 - I assumed at the time last week that it wouldn't affect that much but in hindsight I'm afraid I shoulda thought about it a bit more lol.
Hope this helps!
Click to expand...
Click to collapse
Can you provide some additional detail on how to use goo manager and which custom recovery to install? (a lost newbie)
Thanks
I have had annoying ongoing problem of my phone needing to restart due to my Sim card being removed. I have not removed my sim card at all and it has been happening since I have updated to the newest modem NB4. My setup is as follows the Insane Kit Kat Rom V5 with the included Kernel. To note this has happened since updating to the new NB4 modem. If anyone has any suggestions I would appreciate it.
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
baseballfanz said:
I started getting this same message a while back when on Wicked v10 and mk2 baseband. It wasn't the ROM's fault because I was using the ROM for a few months without problems. I updated to NB4 baseband and the same thing was happening. Flashed a 4.4.2 Rom didn't help. it hasn't happened since I flashed Insane kk v5.
☞ Sent from here ☜
Click to expand...
Click to collapse
Really?? That's great, hopefully it stays working great. What kernel are you using?
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
vinniej said:
I was having the same problem and I did 2 things:
1) I verified I had no foreign debris or anything in the sim card slot. Took a can of compressed air and blew it out.
2) I re'Odin'ed the modem again (twice as mentioned in @shiamatsu thread)
It seems to have fixed things for me. Good luck.
Click to expand...
Click to collapse
I will try all of these suggestions that I have seen so far. What about Odining back to stock and then rooting again? Like I have stated previously I have started seeing this issue since updating to the NB4 Modem and Insane KK. I am sure it isn't the ROM, so I will stick with Insane KK because it is a nice ROM. If anything changes I will report back.
Well, I'm going to take back what I said about fixing it. Sim card removed error happened again. I managed to get a logcat, and dmesg. I have not seen any smoking guns in the logs so I'm going to try a different kernel.
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
crazyc78 said:
Let me know what kernel you use.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had Talexop's and switched to Ktoonsez's (TW 4.4.2). I did get another error after switching so I'm not sold on a kernel issue either.
I think I'm going to retrace my steps and start from the ground up. I jumped directly from the MDL modem directly to NB4. Maybe I need to go MDL>MK2>NB4?? Maybe try a different Odin version? Switch USB ports on my desktop? Different cable? I'm going to keep trying different things until I get it fixed. It is quite an annoyance because the error happens at times when the phone is asleep and you obviously cannot get any calls, messages, etc.
I'll keep the thread updated for sure.
Been half a day and no errors yet (knock on wood). I did not change anything as far as kernel, rom, or modem is concerned. I did go into Settings>More networks>Mobile Networks>Network Operators>Search Networks and then tapped the tmo network (manual network selection).
I do live / work in an area where Tmo goes bye-bye and there is only Vzn and ATT. I recall having to switch networks recently in order to make a call in that area for work from the no signal zone (I have a spare "work" SIM and my phone is unlocked). Perhaps doing that jacked with my selected default network and could indirectly be the cause of the no sim errors?
And I've done the SIM switch in the past on 4.3 roms without issue. Maybe it is a KK / NB4 bug?
Sounds like you're on track bro, I have tried a few things and so far knock on wood like you said it seems to have worked. First I thought about going back to stock but Odin couldn't recognize the md5 or tar files I downloaded. So then I decided to reflash the NB4 modem. I flashed it three times!! Maybe to see if that would make a difference. Then I reinstalled Insane Kit Kat V5 and did a clean install then restored my backup. So far I have Been running my set up for almost 24 hours and not one error! I will keep looking out for it and report back after my current battery had drained out.
SENT FROM MY INSANELY SICK S4
So I just wanted to give an update on my situation. I have gone back to stock the original 4.2.2, and then rooted my device and then installed Insane KK V5. I have noticed with the stock tar ball file of 4.2.2 I get the NB4 modem. A couple times I did not get the NB4 modem I had the original modem. So then I flashed the NB4 modem and my phone was saying unknown baseband. The last two times I have went back to stock it has given me the NB4 modem and I am still on Knox free bootloader. I am still getting SIM card removed errors, more frequently than ever now. A few times my phone tells me that there is no SIM card inserted at all!!! Very frustrating, I was on a phone call earlier tonight and the error happened during the call. So I called Tmo for a replacement SIM card and we will see if that helps, I'm optimistic that it will. I'm now convinced it may be the NB4 modem, we will see what happens when I get my new SIM. If anyone has any more suggestions I will be open to them.
SENT FROM MY INSANELY SICK S4
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
vinniej said:
I had one error since I last posted. I agree that it must be something with the modem and perhaps we are the only 2 people seeing this issue (I find it hard to believe). I am also on the 4.2.2 bootloader with the NB4 modem. I'm hesitant to downgrade as it has not happened more than once over 4 days.
Let me know if the new SIM cures your problems. I may have to make a trip to the local tmo store as well.
Click to expand...
Click to collapse
This was the 2nd post in the thread. I've tried all that and for a while I thought it was fixed. I think I made it 4 days without a problem but then they came back.
_eroz said:
Nope, so far nothing fixes it other than exchanging your phone and hoping the replacement is fine. There is a thread over on the AT&T forum where people, me included, are having this problem. I've replaced the SIM card, SIM card holder, returned to an earlier nandroid when I did not have this problem. I've also unsynced the play store thinking it had something to do with it since it would always occur when I had an app update waiting for me. So far nothing has fixed it.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well...Here is my latest and greatest attempt. I flashed the NB4 modem 3 times (no auto reboot throughout the process), and did battery pulls after the first two flashes. 36 hours and no messages.
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
analogchild said:
Sorry if this is a noob question but I'm having this same issue and waiting on new sim tray, which I gather....isn't going to fix the issue. Did you flash this modem in recovery or through Odin? And I'm not too keen on this Knox business. Im on a 4.4.2 ROM and not sure what bootloader I'm on and not really sure how to go about finding out. From what I gather, the process is different...... Or the file nb4 file I need to flash is different for each bootloader. I'm glued to this thread because I just bought the phone on CL about 2 months ago. Im pretty upset about this to say the least. I loved this phone before all this bull****
Click to expand...
Click to collapse
I'll try to explain what I know (which ain't much!). In order to avoid Knox some folks including myself have retained the knox free (MDL) 4.2.2 bootloader. How to tell if you have a knox free bootloader look HERE (credit to @shiamatsu) By flashing a modem.bin (which can only be done via. ODIN) we are able to have the benefits of the newer radio, but keep the knox free bootloader. A few of us like _eroz and crazyc78 have seen issues with SIM errors since going to the NB4 modem with MDL bootloader. And thus this thread. And in case you want the instructions to upgrade to the NB4 modem look HERE
I imagine if you don't mind knox and you did the full upgrade, you probably should not be seeing the SIM card errors. I'd be curious to know if anyone is seeing SIM card removed errors with the NB4 bootloader / modem.
Brain hurts. Time for a beer...
Thank you. I'm gunna give it a go and see if it works
This may be a hardware issue. My wife gets it on stock never rooted.
I am curious to know when you flashed the NB4 modem did you go back to stock first and then reroot your device and then flash a rom and then odin the NB4 modem? I did all that and still got errors. I am going to update to Insane Kit Kat V6 later tonight hopefully I don't have issues after updating. I am going to try your remedy and see if it works, and if it doesn'tjust wait for my new simcard.
SENT FROM MY INSANELY SICK S4
i seem to be having problems maintaining service in areas i know i should have it. i was on insane kit kat previously, i used to have to put in airplane mode or hot reboot just to get service again. everytime i would turn screen off it would drop service again. i even flashed the nb4 modem...so i switched to gpe 4.4.4 had great service..now again...in areas i had 4g i have nothing...not sure what to do at this point..tried both touchwiz and aosp roms...tried nb4...frustrated...anyone have any clue as to what else i am doing wrong? i alwasys enable roaming...always change network if needed to the most options...at a loss....
What bootloader are you on?
i am not sure...
serio22 said:
What bootloader are you on?
Click to expand...
Click to collapse
not sure what boot loader..how do i tell? is there a place to look?
not sure
Heffler said:
not sure what boot loader..how do i tell? is there a place to look?
Click to expand...
Click to collapse
i didnt start on 4.4.4...never had the official update to kit kat. only jelly bean. rooted then...been on custom roms since...never flashed anything except the nb4 modem while was on insane kk because i thought that might solve problem...
So you did the update to 4.3? Get phone info from playstore and under firmware info it will tell you what bootloader you are currently on.
bootloader
serio22 said:
So you did the update to 4.3? Get phone info from playstore and under firmware info it will tell you what bootloader you are currently on.
Click to expand...
Click to collapse
m919uvuamdl is my bootloader...ummm its also identical to the baseband version...not sure if that means anything...
Check your baseband version in settings, more, about device see if it matches up. To my understanding, you had flashed the NB4 modem correct? It might have failed
serio22 said:
Check your baseband version in settings, more, about device see if it matches up. To my understanding, you had flashed the NB4 modem correct? It might have failed
Click to expand...
Click to collapse
it matches up...m919....so this means i have to re odin flash the nb4? does the basband change on every rom you flash?
Yes Odin the NB4 modem, and no it does not change when you flash ROMs.. It probably just failed to flash, make sure you flash it twice
no go...
serio22 said:
Yes Odin the NB4 modem, and no it does not change when you flash ROMs.. It probably just failed to flash, make sure you flash it twice
Click to expand...
Click to collapse
flashed it twice with odin...i was told to open modem.bin file with the phone button in odin...although if its updating the bootloader...wouldnt i use the boot loader button? but no way was gonna test without checking...so only did with phone button..
Its not updating the bootloader, its updating the modem
Having the same exact issue - cell signal was working to make calls when I got the phone and for a while on an older SOKP rom.
Flashed a newer version and now signal is weaker, data/text works, but making a call fails saying "out of service area" and cell signal completely drops out for 10-15sec before returning for data/text.
I've flashed FROM MDL modem to MK2 and NB4 both and no improvement.
Flashed back to the older SOKP version, no fix.
Flashed other AOSP/GPE roms, no fix.
Flashed Wicked v10, no fix.
Flashed back to stock, no fix.
Flashed back MDL modem, no fix.
Checked IMEI, not stolen or blacklisted.
This is an SGH-M919 S4, but is unlocked (otherwise would not be getting ANY data/text signal either).
My next step is to make sure AT&T has the correct IMEI in their system and see if that helps at all.
But I'm really at my wits' end as to why it all of a sudden flaked out for phone calls.
[UPDATE] Went to AT&T and updated my IMEI number in their system. Signal strength has improved enough and I'm not able to make calls.
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.