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?
Related
Hi Guys!
I did not find anything concerning this problem, so i considered posting it here, I hope this is the right section though.
I own a GSM Galaxy Nexus (German Phone) and after finally getting the update 2 4.0.4 my phone always jumps into this state after rebooting and trying 2 update:
{
"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"
}
As i found no way to update manually this is probably the only way to get to 4.0.4.
The Phone is rooted and has 4.0.2 running atm.
Anyone some advice?
Greetings
Julian
DasEtwas said:
Hi Guys!
I did not find anything concerning this problem, so i considered posting it here, I hope this is the right section though.
I own a GSM Galaxy Nexus (German Phone) and after finally getting the update 2 4.0.4 my phone always jumps into this state after rebooting and trying 2 update:
As i found no way to update manually this is probably the only way to get to 4.0.4.
The Phone is rooted and has 4.0.2 running atm.
Anyone some advice?
Greetings
Julian
Click to expand...
Click to collapse
Your have one or more of the following:
1) a radio that is different from XXKK6;
2) a boot image that is either not stock or (if it is stock), a different version from the one included in the factory image of the ROM you are using;
3) a stock recovery that is a different version from the one included in the factory image of the ROM you are using;
4) files in /system that were modified or deleted, either by you, or one of your root apps.
Those issues need to be rectified before the update will install.
Have a read of this thread for additional info.
Hey efrant
Thanks for you fast answer!
I checked the list.
1.) My Baseband/Radio is I9250XXKK6, so i guess thats ok so far.
2 and 3.) As far as I know I'm on stock Boot image and ROM, how can I check that on my phone? (Heres the info from the system info menu: Kernel-Version: 3.0.8-gaaa2611 [email protected] #1, Build number: ICL53F)
4.) I had several files altered by root apps:
- I'm using Avast Anti Theft and had the Anti Theft functions written into my bootrom (which could likely cause a problem)
- I'm using a Web Remote App that altered some files in the system at least it requested superuser access
Thanks
Julian
DasEtwas said:
Hey efrant
Thanks for you fast answer!
I checked the list.
1.) My Baseband/Radio is I9250XXKK6, so i guess thats ok so far.
2 and 3.) As far as I know I'm on stock Boot image and ROM, how can I check that on my phone? (Heres the info from the system info menu: Kernel-Version: 3.0.8-gaaa2611 [email protected] #1, Build number: ICL53F)
4.) I had several files altered by root apps:
- I'm using Avast Anti Theft and had the Anti Theft functions written into my bootrom (which could likely cause a problem)
- I'm using a Web Remote App that altered some files in the system at least it requested superuser access
Thanks
Julian
Click to expand...
Click to collapse
The easiest way to proceed is to flash CWM, download the IMM76I-from-ICL53F update from here and try to install it in CWM. CWM will tell you exactly which file/files is/are causing the problem.
So, I'll use Method 2 from your link above and this firmware right, and report back!
Worked flawlessly! Thank you!
Or not....
I had OTA RootKeeper installed before the Update and just reflashed the device afterwards being sure that my device will be rooted again....
Well as i found out right now it didnt protect anything, i tried Root Check Basic (Which says my device isnt properly rooted) and wanted to do a superuser binary update which always fails at "getting root access".
I tried rerooting the device using the GNex Root Toolkit several times, with OTA RootKeeper protection on and off, no difference.
Im not sure what a rest would do to my phone as I have an anti theft app installed and several other things that would cost me some time to rebuild after reset. So i'd by happy to solve this without a factory rest. Any Suggestions?
Thank you
Julian
DasEtwas said:
Or not....
I had OTA RootKeeper installed before the Update and just reflashed the device afterwards being sure that my device will be rooted again....
Well as i found out right now it didnt protect anything, i tried Root Check Basic (Which says my device isnt properly rooted) and wanted to do a superuser binary update which always fails at "getting root access".
I tried rerooting the device using the GNex Root Toolkit several times, with OTA RootKeeper protection on and off, no difference.
Im not sure what a rest would do to my phone as I have an anti theft app installed and several other things that would cost me some time to rebuild after reset. So i'd by happy to solve this without a factory rest. Any Suggestions?
Thank you
Julian
Click to expand...
Click to collapse
Just flash this in recovery.
You guys are the ****ing ****!
Thank you!
Hello devs, I have a quick question here. I've read as many threads here as I can, but I still have this doubt before I go ahead and try to root my phone.
I just bought my Galaxy S3 I747 from AT&T yesterday, which came as I747UCALG1. Today it automatically downloaded the package from the network and updated to:
Build Number: IMM76D.I747UCALH9
Baseband Version: I747UCLH9
Kernal Version: 3.0.8-985684
My question is, since the phone is already in a newer version of firmware (I747UCALH9), can I follow mrRobinson's thread (http://forum.xda-developers.com/showthread.php?t=1739426) and flash back to ATT I747UCALG1, which is actually a relatively older version, using Odin? I ask this because I have a PS3 and I know that it is technically not allowed to perform a "downgrade", and I know that it very complicated to downgrade iPhone's baseband as well. So I don't know whether this is the case for Galaxy S3 here
I just want to get my phone rooted so far. Thanks for your patience! Please let me know your comments.
First, questions should be asked in Q&A.
Odin will flash any firmware to your phone. That's why it's important to get the right dl.
But,
Even if you flash back to LG1, you will get prompted to update again.
slinson said:
Hello devs, I have a quick question here. I've read as many threads here as I can, but I still have this doubt before I go ahead and try to root my phone.
I just bought my Galaxy S3 I747 from AT&T yesterday, which came as I747UCALG1. Today it automatically downloaded the package from the network and updated to:
Build Number: IMM76D.I747UCALH9
Baseband Version: I747UCLH9
Kernal Version: 3.0.8-985684
My question is, since the phone is already in a newer version of firmware (I747UCALH9), can I follow mrRobinson's thread (http://forum.xda-developers.com/showthread.php?t=1739426) and flash back to ATT I747UCALG1, which is actually a relatively older version, using Odin? I ask this because I have a PS3 and I know that it is technically not allowed to perform a "downgrade", and I know that it very complicated to downgrade iPhone's baseband as well. So I don't know whether this is the case for Galaxy S3 here
I just want to get my phone rooted so far. Thanks for your patience! Please let me know your comments.
Click to expand...
Click to collapse
If your just looking for root, flash CWM with ODIN and then flash superSU with recovery.http://forum.xda-developers.com/showthread.php?t=1538053 Your counter will go up but then you can install triangle away and reset the flash counter. http://forum.xda-developers.com/showthread.php?t=1494114. This should take less than 5 minutes after you have read everything.
If your completly new to this check out this thread http://forum.xda-developers.com/showthread.php?t=1903437
Read this http://forum.xda-developers.com/showthread.php?t=1802160
and pretty much read all stickies.
nakedninja42 said:
If your just looking for root, flash CWM with ODIN and then flash superSU with recovery.http://forum.xda-developers.com/showthread.php?t=1538053 Your counter will go up but then you can install triangle away and reset the flash counter. http://forum.xda-developers.com/showthread.php?t=1494114. This should take less than 5 minutes after you have read everything.
If your completly new to this check out this thread http://forum.xda-developers.com/showthread.php?t=1903437
Read this http://forum.xda-developers.com/showthread.php?t=1802160
and pretty much read all stickies.
Click to expand...
Click to collapse
thanks dude!
mrhaley30705 said:
First, questions should be asked in Q&A.
Odin will flash any firmware to your phone. That's why it's important to get the right dl.
But,
Even if you flash back to LG1, you will get prompted to update again.
Click to expand...
Click to collapse
does that mean I'll lost root after I update?
After LH9 update, maybe. After flashing the stock firmware, definitely. There is a no trip root method (won't touch your flash counter).
mrhaley30705 said:
After LH9 update, maybe. After flashing the stock firmware, definitely. There is a no trip root method (won't touch your flash counter).
Click to expand...
Click to collapse
If I understand it correctly....what mrRobinson mentioned as the following link is the no tripping method. Basically it flashes rooted official ware so the counter wouldn't be triggered, I assume? http://forum.xda-developers.com/showthread.php?t=1739426
And even if I've done that, I still need to come up with a solution when it prompts LH9 OTA again....emmmm
Thanks a lot mrhaley!:good::laugh:
If you just want to maintain root, try this:
{
"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"
}
just follow the directions in the app.
mrhaley30705 said:
If you just want to maintain root, try this:
just follow the directions in the app.
Click to expand...
Click to collapse
thanks mrhaley30705:laugh::good::good:! you are the man!
Several people who have gone back from LH9 to LG1 get an error about android.process.acore failing when they boot. If that happens, do a factory reset in recovery and reboot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
If u t rooted just freeze the ATT update app. Will not try to update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
lgkahn said:
If u t rooted just freeze the ATT update app. Will not try to update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I intend on downgrading back to LG1 also being as I get horrible battery life with LH9.
Are there any other options besides freezing it? I know titanium will freeze apps, but I hate to install that app just for one thing, being as I would never use anything else in there. Plus if I remember correctly, I think you need to purchase titanium to freeze apps. Not that I'm cheap, but I'd hate to buy the app just to freeze one thing.
So I am just trying to explore other options as well. Preferably free options.
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 everyone!
Recently I've decided to flash over to the new NH7 Update because I wanted to try out the 4.4.4 Modem. After flashing both the ROM and Modem, I no longer have any sound. I'm a "bit" new to some of this so I'm hoping I could get some help. I've flashed plenty of other ROMS and Modems before without an issue (At least issues I could fix) but I can't seem to find any information on how one would fix this problem. I'm assuming the problem is the 4.4.4 Modem?
I'm also having the lockscreen freeze up on me when I try to unlock the phone. If I let the phone set for a while it settles down but it's still really buggy. Seems to do this with any ROM I flash and random things FC on me.
Lastly, Not sure if this helps with the problem but every time I boot into recovery and go to start the phone, it tells me that I lost root and gives me the option to fix. If I choose not to fix, I still have root. No idea why it prompts me about this?
Anyway, here's some info on what I did.
Flashed this ROM and used the modem provided in the thread - http://forum.xda-developers.com/gal...-4-4-4-nh7-insane-kit-kat-v1-9-14-14-t2876946
1 Wiped Cache, Dalvik, Data, Factory reset with TWRP
2 Flashed ROM with TWRP
3 Put phone in download mode and flashed the NON-HLOS.bin
4 Restarted then booted download and flashed Modem.bin
5 Restarted normally and setup phone like normal.
6 No sound :/
Used the latest version of TWRP I could find. (2.8.1 I believe?)
{
"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"
}
Anyway, thanks for any help you guys can give!
Jeff
Try the double flash method (start from phone off, flash without auto reboot, pull battery, boot back to ODIN, flash again, pull battery, boot normally). Some bits may not have updated. This will fix it.
The thing about losing root is I believe a known TWRP bug in that version.
Marc
Hi Marc
I've tried the method you describe with no luck
Oh, I suppose it's worth mentioning that I'm using ODIN version 3.0.7
Thanks,
Jeff
For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue
Kriptik210 said:
For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue
Click to expand...
Click to collapse
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff
jeffreythe00 said:
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff
Click to expand...
Click to collapse
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere
Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.
jeffreythe00 said:
Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.
Click to expand...
Click to collapse
You can't do OTA if you don't have the stock firmware already on your phone. But you can Odin.
You can use this link if you need anything...
http://www.droidviews.com/update-t-mobile-galaxy-s4-to-android-4-4-4-kitkat-and-root-it/
I got it. Sound is working now. I was apparently on the MDL bootloader. I used this thread http://forum.xda-developers.com/galaxy-s4-tmobile/help/nb4-to-nh7-firmware-upgrade-via-odin-t2880284 to get updated and re-rooted. Thanks for the help. I never would have known about the bootloader if it had not of been for this thread. I think I can handle the rest from here
Cheers!
Jeff
If you are unsure of your bootloader, there is a Phone Info Samsung app in the play store. IT will show you your boot loader version, modem baseband, etc..
Kriptik210 said:
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere
Click to expand...
Click to collapse
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.
ShinySide said:
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.
Click to expand...
Click to collapse
Part of me knew this.....lol
Edit....................
T-Mobile the last carrier to update ...I hope we get 5.1.1 soon
winco209 said:
T-Mobile the last carrier to update ...I hope we get 5.1.1 soon
Click to expand...
Click to collapse
What is this, I don't even.
Actually, I can't even. I'm too odd.
No surprise. R&D, QC, whatever you want to call it is taking a backseat on T-Mobile's list of concerns. To think they once were a bit more efficient.
I still don't understand what's going on here.
The are known to skip on updates like this they will probably push 5.1.1 before the rest do tho
Aou said:
I still don't understand what's going on here.
Click to expand...
Click to collapse
TMo hasn't pushed out AOEx yet, while AT&T and Sprint have. Memory management fixes are needed pretty badly.
Sent from my SM-G925T using Tapatalk
It's kinda pathetic. Oh well. I have my other concerns and issues with T-Mobile so I'm about to close my account and move to sprint. The development team is much active over there as well.
xEVILFREDx said:
It's kinda pathetic. Oh well. I have my other concerns and issues with T-Mobile so I'm about to close my account and move to sprint. The development team is much active over there as well.
Click to expand...
Click to collapse
Good luck with that.
Sent from my SM-G925T using XDA Forums
{
"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"
}
I'm pretty sure that they're working on updating straight to 5.1.1. given the leaked OTA which runs perfectly. Makes sense with all the issues plaguing Android 5.0 right now.
I just got the update but also got an error about my device being modified
What update?
xEVILFREDx said:
I just got the update but also got an error about my device being modified
Click to expand...
Click to collapse
If you're rooted, your phone will not update with the OTAs.
Is T-Mobile rolling out a update ?
winco209 said:
Is T-Mobile rolling out a update ?
Click to expand...
Click to collapse
Not as far as I know.
xEVILFREDx said:
It's kinda pathetic. Oh well. I have my other concerns and issues with T-Mobile so I'm about to close my account and move to sprint. The development team is much active over there as well.
Click to expand...
Click to collapse
Hahahaha [emoji23] good luck with that!
Transmission sent from my Galaxy S6 Edge.
xEVILFREDx said:
I just got the update but also got an error about my device being modified
Click to expand...
Click to collapse
Did you get the original update from April? There was one pretty much out-of-the-box for this device. Something like 177MB or 178MB. Something like that.
Also, if you have indeed already received that update, yet you're being prompted to download a new one, I would highly recommend doing us all an awesome favor (assuming you don't mind tripping knox):
- Make some good backups of your device (TWRP or otherwise) such that you don't wipe anything
- Use Odin to return back to stock.
- Install TWRP v2 via Odin. There's an Odin-flashable version in the OP here: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
(this should allow you to maintain an "Official" status, according to SysScope, but have root access through ADB in the TWRP recovery)
- Get advice somewhere here (I'm sure there's plenty that know how to do with on Lollipop) on how to snag that Update.zip of the OTA.
If I'm wrong, and flashing the TWRP via Odin marks the system status as "Custom" then I'm sure there's a different order we can do this in.
Or maybe I'm just crazy altogether. It's been a long day. But in any event, there should be some way to obtain that Update.zip and share it with us!
Aou said:
Did you get the original update from April? There was one pretty much out-of-the-box for this device. Something like 177MB or 178MB. Something like that.
Also, if you have indeed already received that update, yet you're being prompted to download a new one, I would highly recommend doing us all an awesome favor (assuming you don't mind tripping knox):
- Make some good backups of your device (TWRP or otherwise) such that you don't wipe anything
- Use Odin to return back to stock.
- Install TWRP v2 via Odin. There's an Odin-flashable version in the OP here: http://forum.xda-developers.com/tmobile-galaxy-s6-edge/development/5-1-1-blck-tw-t3096994
(this should allow you to maintain an "Official" status, according to SysScope, but have root access through ADB in the TWRP recovery)
- Get advice somewhere here (I'm sure there's plenty that know how to do with on Lollipop) on how to snag that Update.zip of the OTA.
If I'm wrong, and flashing the TWRP via Odin marks the system status as "Custom" then I'm sure there's a different order we can do this in.
Or maybe I'm just crazy altogether. It's been a long day. But in any event, there should be some way to obtain that Update.zip and share it with us!
Click to expand...
Click to collapse
Ideally we'd want them to have the update download and then use a root method that doesn't clear that cache so they could pull the update.
The Root said:
Ideally we'd want them to have the update download and then use a root method that doesn't clear that cache so they could pull the update.
Click to expand...
Click to collapse
Yeah. What this guy said.
xEVILFREDx said:
It's kinda pathetic. Oh well. I have my other concerns and issues with T-Mobile so I'm about to close my account and move to sprint. The development team is much active over there as well.
Click to expand...
Click to collapse
I was with sprint, very bad all the way around, from service to CS, they are 100 years behind