Now that I'm rooted... - Verizon Samsung Galaxy S 4

I know I'm a pain, but I have a few more questions. I'm unable to find the answers that are specific to this device.
I've decided that (at least for now) I'll be keeping the stock ROM that is currently on this phone. I have yet to look at all of the other great ROMs and decide which ones I'd like, and I will eventually do that, but not today.
One of these days, Verizon will be pushing an OTA update. I don't want to lose my root, but if I'm keeping JB, I want the update. Will Voodoo OTA Rootkeeper work on this phone?
Will I get the OTA with a fully debloated device?
What apps do you recommend for a rooted device other than Titanium backup?
As always, any and all help is much appreciated.

If you're debloating the stock rom (using TiBu to remove apps), your phone most likely wont update properly. OTA Root Keeper should work. This phone hasn't had a update so no one can confirm any of this.
Your best bet is to flash a stock based rom (Clean Rom or something similar) and whenever we get an update, the rom developers will update the rom.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

I backed up using twrp to my sd card. I apparently didn't have enough space on the phone, so I did sd. Is that enough or do I need to backup onto my phone as well?
Sent from my SCH-I545 using Tapatalk 2

When an OTA finally rolls out, you will receive a notification. It's not going to force you to update. Then to get rid of the notification, you just need to change a few lines in the build.prop to the newest build number.
Sent from my SCH-I545 using xda premium

My wife's Note 2 was stock w/ root and recovery. Sometimes in the mornings her phone would be in TWRP from where it had downloaded the OTA and attempted to install it. I imagine the S4 will be the same way.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

Just read in the root thread that the OTA updates your bootloader and prevents you from flashing the old kernel to root again. BEWARE - Do not update if you plan to keep root.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

If I were to get this update without unrooting first, would I get in trouble/lose warranty with this update?
Sent from my SCH-I545 using Tapatalk 2

bpmamom said:
If I were to get this update without unrooting first, would I get in trouble/lose warranty with this update?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You'll only ever get in trouble/lose warranty if you return a rooted/modded phone. Research Odin and download a stock Odin image. If you ever need to return your phone, just flash that first and you're good to go.
Also look into an app called Triangle Away. I haven't checked this phone ik download mode yet to see if I've tripped the flash counter but Triangle Away is an invaluable app for resetting it (requires root on a stock rom).
Sent from my SCH-I545 using Xparent Green Tapatalk 2

Make the Jump!
To be completely straightforward -- you probably really don't want the new update. From what I've been hearing around the boards, it doesn't really provide any new important (at least not in my eyes) functionality to the device. If anything, it's mostly just a patch for holes that they unintentionally left. Those holes are what allow you to root the device so easily.
You're doing the same thing I did, by the way -- I hung on to the stock ROM for quite some time, and was a little worried to separate. However, I highly recommend just making the jump and going with HyperDrive. It's on release 5.7 at this point, and I've been using it as a daily driver for a few days now. I'ts really solid, you get all of your stock capabilities and functions plus MORE customization. Pretty cool, and much better than whatever Verizon will eventually push out in my opinion.
Good luck with whatever you choose!

I did decide to unroot for now, and go with the update. Sooner or later, after a good root method comes out, I will likely root again. Mostly, I just wanted to see what this update was all about. It's both good and underwhelming. It's good because the phone doesn't lag like it used to, but otherwise underwhelming.
Thank you, everyone, for your help. I'll definitely stick around on the forums. I really like the community here.

A rom would have fixed that lag.
Sent from my SCH-I545 using Xparent Green Tapatalk 2

Related

[Q] verizon ota

Just got an ota yesterday on my verizon lte galaxy 10.1 tab. Anyone get the same and know what was in it? It was not ICS despite my hopes, dreams, and prayers.
IPv6 and some MLB.com stuff nothing special..
droid life has an article. /2012/06/29/verizons-galaxy-tab-10-1-lte-has-an-update-on-the-way-build-fe01-addresses-minor-bug-fixes/
Questions go in the Q&A section
Just tried to apply the OTA over existing rooted stock (with pershoot's kernel) and as expected the update failed. I have a fresh NAND backup saved for good measure but I'm not in the mood to do all of the work right now to go back to bone stock just for this incremental update. I guess i will have to put up with the update nag screen every time i wake the tab up until it drives me crazy enough to do the update lol.
Sent from my SCH-I905 using Tapatalk 2
muzzy996 said:
Just tried to apply the OTA over existing rooted stock (with pershoot's kernel) and as expected the update failed. I have a fresh NAND backup saved for good measure but I'm not in the mood to do all of the work right now to go back to bone stock just for this incremental update. I guess i will have to put up with the update nag screen every time i wake the tab up until it drives me crazy enough to do the update lol.
Sent from my SCH-I905 using Tapatalk 2
Click to expand...
Click to collapse
This worked for my Charge, so it might work for the tab...change the EL01 (or whatever build it was) entries in build.prop to FE01. There were 2 lines where this was done, but I don't have them on hand ATM. Hope that points you in the right direction.
Sent from my SCH-I510 using xda app-developers app

Why are you updating?

Anybody here feel confused with some of the users that are updating to the latest locked down firmware, I just find it weird that people are knowingly locking down their phones, the main reason people come here is to do the opposite. I've read people apply the update and they still ask for some sort of support from community members. I just dont get it.
Sent from my SCH-I545 using xda app-developers app
I read some saying they didn't care and after some did the update they said the phone was faster and worth losing root. Others just want root and were able to update using voodoo ota rootkeeper. To keep root and update.
Sent from my VZW Galaxy S4 using Tapatalk 4 Beta
They kept root in a sense. Yes, they can still run some apps that require root, but they cannot flash a custom kernel or recovery.
Sent from my SCH-I545 using Tapatalk 4 Beta
I traded my note 2 and got this. Met the guy at Verizon. Got the prompt for the OTA and took it before I knew what was good for me. Although I would have preferred not to, I am very impressed with the stock firmware.
Only disappointment which would make me want to root is WiFi tethering doesn't work in Pdanet, and of course the annoying WiFi toggle - both things I'm content dealing with without pulling hair out while I wait for the new exploit.
Sent from my SCH-I545 using xda app-developers app
I've noticed a few of the update fans haven't posted in here for awhile. Possible a good thing for the community.
Sent from my SCH-I545

New update OTA status, any one installed yet?

Just checked got a 19 MB update after manually checking. Has anyone installed it yet?
Does it remove features, add features or security updates to prevent root?
If you don't know how to check:
1) menu button (left of the home button it doesn't light up till you touch it)
2) click "settings"
3) scroll down (run your finger toward the top of the screen) till you see system update.
4) select system update (I kind of recommend that you be on wifi or 4G before checking)
5) click update It should then check for an update and then download it and ask if you want to install.
If you are new and have not yet got used to rooting phone be aware that by installing it, that it may cause errors, loss of root, or even dogs to say meow and Cartman to be nice by installing it.
Sent from my SM-N900P using Tapatalk
I rooted after the update everything went smoothly.
Sent from my SM-N900P using XDA Premium 4 mobile app
rbaucom said:
Just checked got a 19 MB update after manually checking. Has anyone installed it yet?
Does it remove features, add features or security updates to prevent root?
If you don't know how to check:
1) menu button (left of the home button it doesn't light up till you touch it)
2) click "settings"
3) scroll down (run your finger toward the top of the screen) till you see system update.
4) select system update (I kind of recommend that you be on wifi or 4G before checking)
5) click update It should then check for an update and then download it and ask if you want to install.
If you are new and have not yet got used to rooting phone be aware that by installing it, that it may cause errors, loss of root, or even dogs to say meow and Cartman to be nice by installing it.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Supposedly its an update for allowing the use of benchmarking applications.. And yes root like jurey24 said still works! :good:
http://www.androidpolice.com/2013/10/04/sprints-day-one-mi5-ota-update-for-the-galaxy-note-3-may-remove-controversial-benchmark-boosts/....
Did it add features take away features?
Sent from my SM-N900P using Tapatalk 2
http://www.androidpolice.com/2013/1...-3-may-remove-controversial-benchmark-boosts/
Looks like the only thing it did was allow you to download bench mark apps which was stated earlier
Sent from my SM-N900P using xda app-developers app
36 hours and I'm already tired of looking at that update notification.
Is it still believed that this update is safe with respect to future rooting and knox avoidance?
Thanks.
ogretech said:
36 hours and I'm already tired of looking at that update notification.
Is it still believed that this update is safe with respect to future rooting and knox avoidance?
Thanks.
Click to expand...
Click to collapse
I updated and then ran CF root, no issues and no Knox reset
piaa_nissan said:
I updated and then ran CF root, no issues and no Knox reset
Click to expand...
Click to collapse
No Knox trip, how you get away with that?
Sent from my SM-N900P using Tapatalk 2
No, nothing changed on the 0X1 status from my original root
Sent from my SM-N900P using Tapatalk 4
The Knox changed to 0X1 after I rooted it, it never reset or changed back to 0X0. The counter was tripped and stayed that way
Sent from my SM-N900P using Tapatalk 4
cherylbaker said:
How? Everything I have read says rooting trips the counter. . How do you check it. Can you get a picture for us. I will root right now and start working on a custom Rom if I can root without tripping it
note 2 for sale pm me if interested
Click to expand...
Click to collapse
No matter what u do the counter will trip.. It was at 0x0 before root and now it's at 0x1 after
Love roots of all kinds
~N3
Just put the phone into download/Odin mode and it will be at the top. I've heard some phone don't have the counter but I can't say for sure. Since mine will never be used business I rooted. I have a square trade warranty if I have issues
Sent from my SM-N900P using Tapatalk 4[/QUOTE]
Sent from my SM-N900P using Tapatalk 4
There's nothing in their contact terms that state they would care or even look. Last time I had a claim with my note 2 they never said a word and claim went fine.
Sent from my SM-N900P using Tapatalk 4
Haven't seen an update available yet.. has it taken care of the noises ?!?
Sent from my SM-N900P using Tapatalk now Free
cherylbaker said:
Cool.. Going to root this weekend and start working on a rom.. hope twrp gets working correctly soon.
note 2 for sale pm me if interested
Click to expand...
Click to collapse
I rooted mine via Chainfires auto-root last Friday when i picked up my N3 and although it did change my Knox flag to 0x1 as reported by everyone else, I have not experienced any issues with restoring backups from TWRP.
As others said, there's nothing in Sprint's contract (that I'm aware of) pertaining specifically to root. The only time the Knox counter MIGHT matter is if you had to send it into Samsung directly for service. But then again, all of us know that rooting/modding our phones is an inherited/know risk taken by each user... or at least I hope this is true.
Sent from my SM-N900P using Tapatalk 2

I'm confused about if i can or should take the OTA?

This is the deal. I rooted my note 3 and was not able to receive OTA's like everyone else because my device had a "custom" status. Well I used Wanam xposed and changed my status from custom to Official and now I see there is a 530mb download and it starts downloading it but I cancel it because I don't know if it's safe to take the OTA. I have my phone set up with all the features I wanted like hotspot, missing data, and airplane toggle and don't wanna mess that up or brick my phone.
What do you guys think about my situation? I'm on a stock rooted MJ4 rom tweaked as I said above.
Sent from my SM-N900P using XDA Premium 4 mobile app
The best thing you can do is put the device back to stock or flash the 4.4 rom from Sprint via odin. In the general forum you can find the rom, instructions and steps to do it safely.
Sent from my SM-N900P using XDA Premium 4 mobile app
Normal practice is never to take a Ota while being rooted, it's best to Odin as recommended above.
Sent from my SM-N900P using Tapatalk
MrWicked1 said:
Normal practice is never to take a Ota while being rooted, it's best to Odin as recommended above.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Or install a custom kitkat rom, never ota as root!
bignibb said:
This is the deal. I rooted my note 3 and was not able to receive OTA's like everyone else because my device had a "custom" status. Well I used Wanam xposed and changed my status from custom to Official and now I see there is a 530mb download and it starts downloading it but I cancel it because I don't know if it's safe to take the OTA. I have my phone set up with all the features I wanted like hotspot, missing data, and airplane toggle and don't wanna mess that up or brick my phone.
What do you guys think about my situation? I'm on a stock rooted MJ4 rom tweaked as I said above.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many good answers here, all appropriate.
Your update is not taking because even though Wanam can fake your status to official, your phone's rooted status (assuming you didn't use a Knox safe rooting method) is preventing the update from sticking. Samsung syscope is looking for signed binaries that are official, and thus you're hosed as far as the OTA update is concerned.
But you have many options, the easiest of which start with grabbing one of the tar (freeza) or one-click packages (Rwilco12) from the dev forum, installing from your computer, then adding recovery, rooting, open bootloader if you wish, and then staying put or forging ahead.
There are already a few good roms that are live, and some mods you can flash, if you are so inclined.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Many good answers here, all appropriate.
Your update is not taking because even though Wanam can fake your status to official, your phone's rooted status (assuming you didn't use a Knox safe rooting method) is preventing the update from sticking. Samsung syscope is looking for signed binaries that are official, and thus you're hosed as far as the OTA update is concerned.
But you have many options, the easiest of which start with grabbing one of the tar (freeza) or one-click packages (Rwilco12) from the dev forum, installing from your computer, then adding recovery, rooting, open bootloader if you wish, and then staying put or forging ahead.
There are already a few good roms that are live, and some mods you can flash, if you are so inclined.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I don't know if it will stick or not. I cancel the download before it ever finishes. Before the Wanam it said I couldn't because the status said custom but now it says official it recognized there is an update available.
I am happy with my note as is but that may be because I don't fully understand what 4.4 kit kat has to offer over 4.3?
Sent from my SM-N900P using XDA Premium 4 mobile app
bignibb said:
I don't know if it will stick or not. I cancel the download before it ever finishes. Before the Wanam it said I couldn't because the status said custom but now it says official it recognized there is an update available.
I am happy with my note as is but that may be because I don't fully understand what 4.4 kit kat has to offer over 4.3?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is some misc improvements and a few little new things. But if you are happy with the way it is you can long press on the notification in your notification bar and it will bring up "app info" click that then uncheck allow notifications....hit ok then back out and it will hide the notification for you.
Sent from my SM-N900P using Tapatalk

S4 Randomly Shuts Off After Screen Locks??????

So I've been having this issue ever since I upgraded to kitkat. I'll be messing with my phone normally for all day and then once in awhile when I lock it and and go to pull it back out or unlock it, the phone is turn off. I know it shuts off because I have to hold the power button and all of a sudden the Samsung Galaxy S4 screen pops up like it usually does from boot up. This is really frustrating and I don't know why it keeps doing this. It's not usally a daily thing but I'll happen once every 3 to 4 days and sometimes happens twice a day. Has anyone else had this issue or know any suggestions how to fix it??????? Any help would be greatly appreciated! !!! My s4 is the Mk2 version btw.
Sent from my SCH-I545 using Tapatalk
You're on KitKat but you're on MK2?
Sent from my SCH-I545 using Tapatalk
My S4 baseband version is the Mk2.
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
My S4 baseband version is the Mk2.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
You're baseband version only represents the modem you're on. When people say they're "on MK2" or "on MDK" they mean the bootloader version. What method did you use to upgrade to 4.4? Are you on the leak, NC2 or the official update NC5?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Official OTA Update
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You're baseband version only represents the modem you're on. When people say they're "on MK2" or "on MDK" they mean the bootloader version. What method did you use to upgrade to 4.4? Are you on the leak, NC2 or the official update NC5?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Anyway I can fix.this issue? Still need help!!!((
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
Anyway I can fix.this issue? Still need help!!!((
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Were you rooted or anything, or completely stock when you took the OTA? If you were completely stock, then the baseband should've updated to NC5 as well, so something went wrong with your update. Can you screenshot your about phone screen?
I wonder, if the modem didn't update with your OTA, then something might've went wrong with the boot.img/kernel as well, which is the most common culprit with this type of issue.
I'm going to say try a factory reset first and if the issue persists then you will need to use Odin to flash a fresh NC5 tar image.
joshm.1219 said:
Were you rooted or anything, or completely stock when you took the OTA? If you were completely stock, then the baseband should've updated to NC5 as well, so something went wrong with your update. Can you screenshot your about phone screen?
I wonder, if the modem didn't update with your OTA, then something might've went wrong with the boot.img/kernel as well, which is the most common culprit with this type of issue.
I'm going to say try a factory reset first and if the issue persists then you will need to use Odin to flash a fresh NC5 tar image.
Click to expand...
Click to collapse
Well I didn't realize on either updated it my baseband version changed from MK2 to NC5. So yeah it did change along with the OTA update. But see I DID have my phone rooted like 2 weeks before the OTA and decided I didn't want root on my S4 so I uninstalled, eveything. From SuperSU. To busybox. So when I took the update no I was not at the time rooted. But I'm thinking some old root filed are still on my phone causing it to do this random power off thing. So I don't know really what to do yet besides factory reset:C
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
Well I didn't realize on either updated it my baseband version changed from MK2 to NC5. So yeah it did change along with the OTA update. But see I DID have my phone rooted like 2 weeks before the OTA and decided I didn't want root on my S4 so I uninstalled, eveything. From SuperSU. To busybox. So when I took the update no I was not at the time rooted. But I'm thinking some old root filed are still on my phone causing it to do this random power off thing. So I don't know really what to do yet besides factory reset:C
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, unfortunately that seems like the only option. You might want to wait for someone else to chime in with an idea, but personally I don't care about the data on my phone so I would factory reset.
joshm.1219 said:
Yeah, unfortunately that seems like the only option. You might want to wait for someone else to chime in with an idea, but personally I don't care about the data on my phone so I would factory reset.
Click to expand...
Click to collapse
I'll give that a try. I didn't want to do that unless it.was absolutely the last choice I had. I'll see what it does after reseting it. Anyone have any other suggestions or have this hopping to them.as well?
Sent from my SCH-I545 using Tapatalk
Yea I'm with Josh in that I don't care about the data on my phone so when things like this pop up I can just either factory reset or use Odin. You can at least save all your important stuff to your PC or external sd first. Hard to say what's causing it really... If you were able to flash a new kernel I'd suggest that but that's not an option right now... Unless surge or someone can extract the 4.4 stock kernel to use with Odin.... Most likely Odin the full kit kat image though should definitely help worse case
Sent from my jflte using Tapatalk

Categories

Resources