I tend to get confused about which ROMs are compatible with my device.
I know there are Sprint specific Galaxy Note 4 roms, but I get confused when I have problems installing a ROM and I ask for support and I'm told "Oh! The reason it's not working is because of you go in about phone and look at section A, yours says "ABC" at the end, the ROM you tried to install was meant for Sprint Note 4's that end in "DEF"
And I'm just like.. wat.
I'm trying to learn and trying to absorb as much as I can from threads that already exist, but with certain issues I just can't help but make my own thread because I can't find a solid enough answer.
So. My Problem:
I attached pictures of my "About Phone" section. I'm rooted but with no custom ROM. Which ROMs will be compatible with my device? I would like to find a CM ROM and a Touchwiz ROM as I like to switch between the two occasionally.
I just don't want to run into the problem again where odin keeps failing and my phone is unavailable for an entire night simply because I tried a ROM that won't work with my situation.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are currently running the 3rd release of lollipop for the sprint note 4, that being OF5. (and yes the last 3 letter/numbers identify the version of any rom on any phone)
The last kitkat release was NK2, then came the 1st Lollipop OB7 release. Up to this point downgrading was and is still possible.
Then came the OE1 release of lollipop and the ability to downgrade vanished because as well as there being no official "tar" file released by Sammy for the OE1 rom. Once on OE1 there was no going back and the only custom rom choices were Cyanagen (CM) or as was found out the ob7 based Noterized rom.
Then lollipop OF5 (the one your on) was released along with this time an official Sammy "tar" file. Your custom rom choices are the same as OE1. All roms up to OF5 are rootable.
Lastly is the OG5 major (meaning [email protected]+MB) 5.1.1 lollipop release. Not rootable as of this writing but the dev's are working on it and we all are waiting for the "tar" file and kernel source to drop.
And that is the recent history of the sprint note 4 so far. As to your question;
Sac's ported S6 rom, Noterized, and CM. Check these out in the "development" threads and do always, always back a backup in recovery before doing anything once you are rooted. And keep on reading, you'll get there.
kenjesse said:
You are currently running the 3rd release of lollipop for the sprint note 4, that being OF5. (and yes the last 3 letter/numbers identify the version of any rom on any phone)
The last kitkat release was NK2, then came the 1st Lollipop OB7 release. Up to this point downgrading was and is still possible.
Then came the OE1 release of lollipop and the ability to downgrade vanished because as well as there being no official "tar" file released by Sammy for the OE1 rom. Once on OE1 there was no going back and the only custom rom choices were Cyanagen (CM) or as was found out the ob7 based Noterized rom.
Then lollipop OF5 (the one your on) was released along with this time an official Sammy "tar" file. Your custom rom choices are the same as OE1. All roms up to OF5 are rootable.
Lastly is the OG5 major (meaning [email protected]+MB) 5.1.1 lollipop release. Not rootable as of this writing but the dev's are working on it and we all are waiting for the "tar" file and kernel source to drop.
And that is the recent history of the sprint note 4 so far. As to your question;
Sac's ported S6 rom, Noterized, and CM. Check these out in the "development" threads and do always, always back a backup in recovery before doing anything once you are rooted. And keep on reading, you'll get there.
Click to expand...
Click to collapse
Good advice you gave him. One minor comment.
Samsung doesn't release TARs for any device.... They are hand made. You pull the unmodified partitions, and then TAR them, then run them through an MD5 program that attaches an MD5 Sum to it.
ODIN is a Samsung internal program that gets leaked pretty often. This allows us to interface with download mode and flash the tar.md5 files (or just tar's but md5'd ones are safer due to integrity checks).
So there is no Samsung official TAR. Nor Official ODIN software. Either leaked, or hand made.
Sent from my Nexus 6 using Tapatalk
I grabbed anie.tar via kies from sammobile. Thought that was official. Was I wrong?
npjohnson said:
Good advice you gave him. One minor comment.
Samsung doesn't release TARs for any device.... They are hand made. You pull the unmodified partitions, and then TAR them, then run them through an MD5 program that attaches an MD5 Sum to it.
ODIN is a Samsung internal program that gets leaked pretty often. This allows us to interface with download mode and flash the tar.md5 files (or just tar's but md5'd ones are safer due to integrity checks).
So there is no Samsung official TAR. Nor Official ODIN software. Either leaked, or hand made.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
And "they" said I'd never learn anything frittering my time away on the XDA forum site. Well this will sure show "them". [emoji4]
Related
I have been running the rooted stock ver 4.1.2 GC01 That i found here on the forums mos ago. This morning i tried to flash a new kernel and rom and figured i would test out a few new roms. I download the blasphemy kernal, slimbean, carbon, CM10.2 and dirty unicorns roms. I was looking for a stable and reliable 4.3.1 rom as daily driver. problem i ran into is no matter what i do i get a operation failed, cant verify signature. after hrs of reading a tinkering. i install cwm but it never flashed over the e3 recovery that came with the rooted stock 4.1.2 rom i had flashed. I read that you had to disable the verify signature in cwm settings but no such option is available. I tried flashing the kernal and all the roms and i keep getting the same error no matter what i try. Can somebody please explain to me what im doing wrong? Also if i missed a stable 4.3.1 rom to dl and try im open to suggestions. i figured i would check them all out and see which i like best. Any help in the error problem and possible suggestions for roms is most appreciated.
Well first off, I would say none of the 4.3 ROMs are "stable". Functional yes, but not stable. Try the EL29 Direct Boot kernel-http://www.rwilco12.com/downloads.p...ernels/Recovery Kernels/GB/Noobnl Direct Boot for flashing. Don't forget to get an ICS modem for the 4.3 ROMs and Wimax was removed from 4.3 by Google so no 4G if that's a dealbreaker.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ok, tyvm for the info. im dl the tar file now. hope that fixs the problem. when you say 4.3.1 isnt stable. what excatly do you mean by it. i know with a lot of roms with this phone it seems like its a ymmw situation, esp data from what ive read. Would i be better of just sticking with a 2.2 rom? 4g isnt a big deal for me. im normally on wifi anyways. when im not i just really need to make sure i can get emails form work and txt messages. 3g is generally good enough for that. most the time i have 4g turn off just to save batt, as im a somewhat heavy user. biggest reason i was looking at 4.3.1 is because of an app. I get the "incompatible device" message if not on 4.3 or higher. i know for fact if i manually install app it will work just fine. It will just be a pain to get new updates since i can just use the play store to update. i did read about a work around but i lost the thread due to trying to get this phone to be able to flash roms. other than the app my main concern is getting the most out of my batt as possible. i seam to have huge battery drains lately. so figured a fresh clean install with a custom kernel might do the phone some good.
Sry for the noobish questions. I came from the fascinate, charge and razr on verizon and was active in thoughs sub forums. But for some reason this phone seems to be a pain in my butt for some reason. idk if its because to jellybean, the phone or im just getting dumber lol. again ty for your help ill post back soon on results.
awesome. it now boots into cmw but wont boot back to my rom. i guess i have to just to flash a kernal rom and modem now right? is only being able to boot into cmw and not boot into stock rooted rom normal at this point?
Also is FC14 the better ics modem to use if trying out a 4.3 rom?
Yes, it boots to a "safe" recovery then you flash your ROM and reboot. The one problem with EL29 is it can't flash modems, you can do that after your ROM boots up tho.
Undzis said:
awesome. it now boots into cmw but wont boot back to my rom. i guess i have to just to flash a kernal rom and modem now right? is only being able to boot into cmw and not boot into stock rooted rom normal at this point?
Also is FC14 the better ics modem to use if trying out a 4.3 rom?
Click to expand...
Click to collapse
Try whatever ICS modem you like. Some report better performance with some than others. You might try the official releases first before grabbing a leaked one. Either way, your phone, your experience is your best guide.
In a word, with items like this (best modem), searching may not be as useful as experimenting.
Swapping those is quick business.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Many thanks! im up and flashing like a champ.Your advice works like a charm. TYVM. I dont honestly know which are leaked and which are official modems. the list i got doesnt say which are which. is there a list that states official modems and which are thanks any leaked? Which modem was the last official ics modem? also if i decide to go with a 4.2 rom i would need to go back to jb modem correct?
Undzis said:
Many thanks! im up and flashing like a champ.Your advice works like a charm. TYVM. I dont honestly know which are leaked and which are official modems. the list i got doesnt say which are which. is there a list that states official modems and which are thanks any leaked? Which modem was the last official ics modem? also if i decide to go with a 4.2 rom i would need to go back to jb modem correct?
Click to expand...
Click to collapse
FL24 is the last official ICS released, only JB TouchWiz uses JB modems, all AOSP uses ICS modems.
bilgerryan said:
FL24 is the last official ICS released, only JB TouchWiz uses JB modems, all AOSP uses ICS modems.
Click to expand...
Click to collapse
Your the man! thanks again for clearing all that up.
So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.
Ryan92394 said:
So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.
Click to expand...
Click to collapse
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates. This won't work because the Knox Bootloader won't let you downgrade your firmware and you can easily brick your device trying to do so.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates
Click to expand...
Click to collapse
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?
Ryan92394 said:
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?
Click to expand...
Click to collapse
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.
bilgerryan said:
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.
Click to expand...
Click to collapse
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?
lol I just noticed your name is Ryan <3 awesome name =-D lol we even have the same join date oct 2011. Thatd be crazy if we had the same birthdate lmao im Sept '87 was I close? lmao
Ryan92394 said:
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?
Click to expand...
Click to collapse
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
from here: https://community.sprint.com/baw/message/782055#782055
and alternately here: http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy
bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
Any ideas?
Ryan92394 said:
Any ideas?
Click to expand...
Click to collapse
The PUC is based on Sprint's official OTA source code. PUD is based on Samsung source code for all Sprint devices (Virgin Mobile, Boost, etc). That is the only difference from what I understand.
I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.
I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
why not the KK stock ND8 tar?
6th_Hokage said:
why not the KK stock ND8 tar?
Click to expand...
Click to collapse
Because i have read a bit about it and i believe that flashing the firmware might wipe internal data and it comes with knox as well. And from what you posted, all you need is a jb firmware. But that's also why I said to wait until someone more knowledgeable confirms what I'm saying
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
Click to expand...
Click to collapse
Just confirming, that's the correct one.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
You people are awesome!
Thank you. I will try it tomorrow, and check back. Samsung has done a lot to thwart rooting lately, and I didn't want to close any doors by installing something TouchWiz-based.
Argh!
Link #5 is broken. Crap. Back to reading...
badmojorayman said:
Link #5 is broken. Crap. Back to reading...
Click to expand...
Click to collapse
If you go to that same thread and find the spoiler under "old versions" (bottom of post #1) you can flash the "MB1 firmware/modem/baseband update" as well
Sent from my SPH-L710 using XDA Free mobile app
badmojorayman said:
I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.
Click to expand...
Click to collapse
Hold the phone! (Pun intended) There are two context clues in your op that lead me to believe that you should under no circumstances flash any firmware found in that firmware thread linked here.
1
badmojorayman said:
Knox was enough trouble to overcome.
Click to expand...
Click to collapse
If you have Knox your bootloader cannot be downgraded.
2
badmojorayman said:
I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
Click to expand...
Click to collapse
The only time I've personally witnessed this behavior is on the ND8 bootloader. If you don't know which bootloader you're on already you would be wise to find out before flashing any firmware file.
You've all given good advice, but the best advice came too late. The phone no longer powers on because of the baseband update I was attempting. I'm now waiting for a MicroSD card to show up so that I can attempt this:
http://forum.xda-developers.com/showthread.php?t=2345860&page=63
Hello! I received a replacement for a TMO Samsung Galaxy S3 for a S3 LTE (. It did an auto upgrade to 4.3. Because that v is a POS I rooted 4.3 with Odin3 (v3.09) and root66 tar. NOW I find out that there is an upgrade to 4.4 for the S3 LTE (or all S3s I assume) and I am in a dilemma if I should back out of root; how difficult would that be; allow the 4.4 upgrade; and then re-root?
Give me your thoughts, advice, emoji and pats on my girlie head.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You now have an s3 LTE, aka sgh-i747?
I recommend getting back to stock and upgrade to 4.4.2 via ota updates. This is the slowest but safest method to install the updated boot loader and modem.
Once you are fully updated, you can flash a custom recovery and root by flashing supersu in recovery. Flashing a custom recovery will trip Knox and set the warranty bit to 1 and this will void your Samsung warranty.
Crap. I am lost. Newb Jr.
First, I have attached the image from About to verify the stats.
Second, can you tell me what your recommendation is to back out of root (having used Odin3 + root66 tar to stock?
I am hoping that once I return to stock, upgrade, I will root again using the same method. Let me know if that all makes sense.
Crap. I am lost. Newb Jr.
First, I have attached the image from About to verify the stats.
Second, can you tell me what your recommendation is to back out of root (having used Odin3 + root66 tar to stock?
I am hoping that once I return to stock, upgrade, I will root again using the same method. Let me know if that all makes sense.
audit13 said:
You now have an s3 LTE, aka sgh-i747?
I recommend getting back to stock and upgrade to 4.4.2 via ota updates. This is the slowest but safest method to install the updated boot loader and modem.
Once you are fully updated, you can flash a custom recovery and root by flashing supersu in recovery. Flashing a custom recovery will trip Knox and set the warranty bit to 1 and this will void your Samsung warranty.
Click to expand...
Click to collapse
sorry, double post. Don't see how I can delete the one without the quote.
Sorry, I re-read your post. You used to have an LTE s3 (sgh-i747) and now have an T999. I guess I was too tired when I read your post.
I'm not sure that there is anything beyond 4.3 for the T999. The latest for the s3 LTE is 4.4.2.
Even T-Mbile's Note 2 is stuck on 4.3 while other Note 2 carriers have moved to 4.4.2.
My current device is the LTE that replaced the S3 (not LTE). The (HUGE, sorry) image of the About is my current device.
audit13 said:
Sorry, I re-read your post. You used to have an LTE s3 (sgh-i747) and now have an T999. I guess I was too tired when I read your post.
I'm not sure that there is anything beyond 4.3 for the T999. The latest for the s3 LTE is 4.4.2.
Even T-Mbile's Note 2 is stuck on 4.3 while other Note 2 carriers have moved to 4.4.2.
Click to expand...
Click to collapse
I believe all s3s carried by T-Mobile, AT&T, Rogers, Bell, Videotron, etc. are LTE-capable.
If your phone is the T-mobile version of the s3, I don't think there is a 4.4.2 update or stock ROM for the phone.
My carrier is TMO - there is the S3 T999 (not LTE capable) and there is an S3 T999L (LTE). I updated to Jelly Bean / 4.3, then rooted with Odin (mainly to manage bloatware, pre-installed, etc.) So if I understand you correctly, you do not believe that Kit Kat is even available for the S3 T999L? I checked for a software update through the device and received the message that "since my phone had been altered, the software update will not install." Understand why I would receive that message, however, I made the assumption that 4.4 must be the update. If so, I would back out of root, upgrade to 4.4 - re-root.
If you are saying that 4.4 is NOT available for my phone, then I will keep my device rooted over 4.3
audit13 said:
I believe all s3s carried by T-Mobile, AT&T, Rogers, Bell, Videotron, etc. are LTE-capable.
If your phone is the T-mobile version of the s3, I don't think there is a 4.4.2 update or stock ROM for the phone.
Click to expand...
Click to collapse
This is the latest firmware for your phone from sammobile.com: http://www.sammobile.com/firmwares/download/35794/T999LUVUBNF4_T999LTMBBNF4_TMB/
It was released in June 2014. The mk4 firmware on your phone was released in December 2013.
If you think there is a Kit Kat update, you could use Odin to flash back to stock mk4 firmware and run the OTA updates which should take you to at least NF4 firmware.
Thanks, @audit13!
audit13 said:
This is the latest firmware for your phone from sammobile.com: http://www.sammobile.com/firmwares/download/35794/T999LUVUBNF4_T999LTMBBNF4_TMB/
It was released in June 2014. The mk4 firmware on your phone was released in December 2013.
If you think there is a Kit Kat update, you could use Odin to flash back to stock mk4 firmware and run the OTA updates which should take you to at least NF4 firmware.
Click to expand...
Click to collapse
Update
Issue after 4.3 Auto Upgrade:
I have looked through many, many questions on this forum group relative to push notifications but most do not have an answer (or reply). I had learned that developers must update their apps to comply to 4.3 notification process that is part of 4.3 (POS). Is that my problem? I don't know.
I have tried 10 different reminder apps that notify me of events I have created that repeat, are persistent and stick to the notification drawer, but rarely, if even do. Sometimes they work, sometimes they don't. Other apps have similar behavior: one message comes through and 5 after will not. I am baffled.
I am rooted: Odin 3.09 root66 tar
Samsung Galaxy S III LTE
Any help is greatly appreciated. I do NOT have the funds to get a new phone and am stuck with the S3. Thank you in advance.
After doing tons of research on the push notifications, I have installed DynamicNotifications, removed any other lock screen app, customized DynamicNotifications and hopefully this will do the trick. So for anyone coming to this forum about 4.3 and push notifications issues .. take heed that you won't get a reply but try DynamicNotifications and uninstall any app you have that uses a lock screen. I was using CM Locker. DynamicNotifications has a built-in lock screen. You can read about the app in the Market/Play Store. I would also recommend watching a few YT vids on DynamicNotifications.
This app will help as well:
http://forum.xda-developers.com/showthread.php?t=2142503
Could the notification problem be related to your rooted ROM? I'm not sure.
Good Read:
https://productforums.google.com/forum/#!topic/nexus/fslYqYrULto
audit13 said:
Could the notification problem be related to your rooted ROM? I'm not sure.
Click to expand...
Click to collapse
I am not using a ROM. I am rooted with no ROM installed.
marinazar said:
I am not using a ROM. I am rooted with no ROM installed.
Click to expand...
Click to collapse
You might want to read the article I just posted.
I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?
More help: http://www.digitalinternals.com/mobile/fix-wifi-push-notifications-delay-android/361/
I rooted with Odin 3.09 and root66 tar. That's it.
audit13 said:
I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?
Click to expand...
Click to collapse
Of course its from 2013. I am on o/s 4.3. That is when all the push notifications began to disappear. This is the reason:
http://www.digitalinternals.com/mobile/fix-wifi-push-notifications-delay-android/361/
Trust me, if there were a way I could get off 4.3 I would but I am stuck with the S3.
audit13 said:
I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?
Click to expand...
Click to collapse
I am using PNF (root), DynamicNotifications, have checked the TCP timeout, and everything inbetween. Will have to do a factory reset next, but I've read that didn't help at all.
"In a nutshell, Google’s push notifications service work by making a connection on TCP port 5228 between the phone and Google servers."
The latest T-mobile NF4 ROM came out in October, 2014. You could move to a custom Lollipop ROM to see if that solves the issue.
The fact that the Root66 ROM is rooted may have something to do with the push notifications.
Looks like the solution may require changing TCP time outs on a wifi router.
Unfortunately, my Netgear genie does not allow for TCP parameter changes.
I will try a ROM change next but I cannot even tell you how many hours I have invested in this device since it auto upgraded to 4.3 - ridiculous.
audit13 said:
The latest T-mobile NF4 ROM came out in October, 2014. You could move to a custom Lollipop ROM to see if that solves the issue.
The fact that the Root66 ROM is rooted may have something to do with the push notifications.
Looks like the solution may require changing TCP time outs on a wifi router.
Click to expand...
Click to collapse
have you tried a stock rom without root to see what happens?
I haven't. What steps would I need to take knowing I have root66? Speak in noob, audit
audit13 said:
have you tried a stock rom without root to see what happens?
Click to expand...
Click to collapse
Download the latest rom from sammobile.com and use Odin to flash it.
Did you use Odin to flash root66?
http://forum.xda-developers.com/showthread.php?t=1949687
I did.
In another thread you had sent me a link for firmware for my device. I've attached the screenshot.
So I really don't want to brick my phone Are you thinking I should find a new ROM, install with Odin, or revert back to stock? I am lost on what to do now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
audit13 said:
Did you use Odin to flash root66?
http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse
I found these instructions for converting back to stock with Odin:
http://androidromupdate.com/2013/12...-official-4-3-stock-t-mo-galaxy-s3-lte-t999l/
The phone doesn't look like it is running the latest firmware.
How did the phone get an ota update if it was rooted?