yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] loonie01:
Bought a different phone? Lol. Please do tell.
[Verizon Samsung Galaxy S 4] Poofster:
do tell..do tell haha
[Verizon Samsung Galaxy S 4] DavidIanWarren:
Yes please... I unrooted and did stock ota for the taste of KitKat bud sadly its all Samsunged up... :(
[Verizon Samsung Galaxy S 4] spjetrovic:
well you got half of it! my proximity sensor was acting up from keeping my s4 in my pocket. I was one that had to try KK, I got the itch. Well I went to vzw and got a replacement that came with (thank god) MK2.

Off to rooting, learned my lesson
[Verizon Samsung Galaxy S 4] taz1458:
Just a quick FYI. I don't remember if it wad this thread or one of the others, but for the nc2 leak worth the phone had stopped working fc, someone said renaming the csc.apk fixed it, which it did, however, it made my camera quit working. Changed it back and all is good again. Does the phone fc have anything to do with the camera?
[Verizon Samsung Galaxy S 4] RedsonRising:
I have had that issue a few times. Seems as if the default messaging client doesn't hold. When that happened I wasn't seeing any texts.
[Verizon Samsung Galaxy S 4] Redflea:
Email uses data, texts use cell service. So you had Wi-Fi long enough to get emails, but lost cell service, so no calls or texts could get through.
[Verizon Samsung Galaxy S 4] I Hate Import Cars:
4.4 ota = brick!

Just an FYI for everyone, I took the 4.4 OTA this morning for my S4 on 4.3 MK2 (I believe) and it bricked this mother****er. So heads up everyone, don't take it. I was rooted but still on the stock ROM before you ask. Not sure what to do with it now to recover some form of a working phone, but just thought I'd pop in and give everyone the heads up.

EDIT: Recovered the soft brick with Odin with no problems, in case anyone else runs into this.
[Verizon Samsung Galaxy S 4] SamuriHL:
It's widely known that this update does install properly if you're rooted on MK2. So that's not surprising unfortunately.
[Verizon Samsung Galaxy S 4] Poofster:
Weird thing to that is I did get two phone calls in that time but no texts
[Verizon Samsung Galaxy S 4] mudflap2.0:
if you just got a your gs4 today and happened to update to kitkat, how would you root? the thread isn't updated for kitkat and I feel that anything I do can brick this son of a b@#%^, so I need to root this for my friend tomarow, he is on 4.4 as of today and I need to know a way of rooting and getting a custom recovery, this phone seems very locked down, so any help would be appreciated, btw my friend never touched or rooted his phone or anything like that, so he is completely stock on 4.4kitkat, so what would bethe root process???
[Verizon Samsung Galaxy S 4] robthefive0:
Did you read any of this thread? there is no root yet for kit kat.
[Verizon Samsung Galaxy S 4] Batttie:
take the phone outside, gently lay it face down behind your left rear tire and repeatedly run the phone over until custom recovery sticks... may take a few times but in general it will all work out.

:confused:

how is a thread titled 4.4.2 not updated for kitkat?...
[Verizon Samsung Galaxy S 4] Charlie115:
Just font get it!!!

---------- Post added at 02:24 PM ---------- Previous post was at 02:22 PM ----------

[/COLOR]I'm starting to see why devs get so aggravated now, I understand being a noob and all which I enjoy helping when I can but it's getting so that people are lazy don't even take two seconds to read up on anything at all!!!! It's "I did no reading no research and I frigged up my phone and why haven't you fixed it yet"!!!!!!! Sorry to ***** but please help us help you!!
[Verizon Samsung Galaxy S 4] joshtb86:
yeah i would contribute to a dev group/person looking for root... pm me if you are
[Verizon Samsung Galaxy S 4] D3Seeker:
Can't believe I did it, but darnit I did the OTA update Saturday afternoon when it finally showed up and I'm sure it drains the battery quicker. Bleh........

D3 MDJKD S4
[Verizon Samsung Galaxy S 4] jwhistler:
Um...I actually did this with my phone when it slipped out of my pocket getting into my car. I can confirm that it

WILL NOT

make custom recovery stick!

Just thought you'd all like to know...
[Verizon Samsung Galaxy S 4] PolishPoet:
If mudflap can't read, how will he ever root?
[Verizon Samsung Galaxy S 4] SamuriHL:
For those that REALLY want to comprehend what you're up against in terms of finding a root exploit, check out the first post of this thread:

http://xdaforums.com/showthread.php?t=2728051

That's 5 digits and a dollar sign. UNCLAIMED. If you doubt how difficult it's going to be to root these new 4.4.2 builds, well, there's your proof.
[Verizon Samsung Galaxy S 4] tech_head:
Yep. Smasung has decided they don't like rooted phones.

Currently the only way to be rooted is to "NOT" take the OTA and use the method below:

http://xdaforums.com/showthread.php?t=2726868&page=57

It does work.
[Verizon Samsung Galaxy S 4] jmgib:
Honestly it is good that its so hard to find security vulnerabilities. The real issue is that we can't just "fastboot OEM unlock" to unlock the bootloader.
[Verizon Samsung Galaxy S 4] droid4lif3:
**** I just bought my phone on craiglist and it has kikat installed uuuuuuuuuugh.
[Verizon Samsung Galaxy S 4] peppersu812:
Same situation. I had the s4 with T mobile and left them and came over to Verizon. Had no clue about the bootloader and all this mess. I really wish they would unlock this Damn device and they would be the top notch competitor!
[Verizon Samsung Galaxy S 4] Hashbang173:
There is an experimental root here http://xdaforums.com/showthread.php?t=2720163

You have to downgrade

[quote name="gigilie" post=52419240]hey bro you have an option for root :) not traditional but same not the less. method to achieve is a bit more complicated than normal. download the http://www.androidfilehost.com/?fid=23329332407590522 <-- downgrade odin pack and the upgrade --> http://www.androidfilehost.com/?fid=23329332407590523 then find a flashable mk2 system.img i made my own with IZArc (archiving program for PC) and the MK2 all upgrade stock odin file just deleted everything but the system.img and converted it to a .tar file. Then open Odin in AP put the downgrade odin pack and in CP put the system.img file (or AP after flashing the downgrade and going back into odin) then restart the phone you might have to flash nc5 cache file found in the afh folder if it doesnt boot. it should boot you into mk2 stock from there you need to root the phone with saferoot and install safestrap. then either get a custom rom or use a prerooted rom install it to your stock slot via Safestrap restart to download mode and flash the upgrade kit u downloaded. this will get you back to 4.4.2 with root.[/QUOTE]<br />
[Verizon Samsung Galaxy S 4] dazabale:
I would imagine they want I.T. departments to allow them on corporate accounts. I know multiple people who are stuck on Apple because their company I.T. departments dont trust android yet for company provided phones.
[Verizon Samsung Galaxy S 4] tech_head:
No offense, but the whole BYOD is a bunch of bull.

You don't need the device locked down all you need is a secure email client like Touchdown.

most companies don't allow access from a handheld of any type on their networks.

I can use my device but must go through a VPN.

Anyway, they could have sold two devices. One for enterprise and one for everyone else.

They could have made one device with a one way to enterprise bootloader lock.

There are a number of things they could have done.

This was about control by Verizon also AT&T.

You can get devices on Sprint and T-Mobile that don't have the issues.
[Verizon Samsung Galaxy S 4] Ravaged Pheonix:
Just got this phone the other day. The Jackass at best buy starts to hand me the phone then says "oh look there's an update".

CLICK!

You unholy piece of human garbage.
[Verizon Samsung Galaxy S 4] cbmggm:
I would return the phone to Best Buy and exchange for another S4. They cannot make you take an OTA. Let BB activate the next phone then Run out of the building!
[Verizon Samsung Galaxy S 4] attikrat:
Same deal

I did that too and it bricked it. All it would do is boot up the samsung custom logo screen.

I called verizon via chat at the website and sent me out another on, I have been out of my two year warranty since september or 2013.

Kept my unlimited data!!
[Verizon Samsung Galaxy S 4] ChaoticHavok:
Anyone having heat issues with the new software? It seems to heat up faster than 4.3. Non root stock
[Verizon Samsung Galaxy S 4] caniswesley:
I took the 4.4.2 (NC5) Ota after uprooting, then bricked (soft) trying to go back to 4.3(MK2). I then fixed back to MK2 root, and followed Surge1223's instructions to upgrade to 4.4.2 and keep root. I'm on 4.4.2 with root After taking the OTA... It's possible to have NC5 OTA and get MK2 back and root and following the instructions.

Asus MeMo Pad FHD 10

Verizon LG Enlighten[

Verizon Samsung Galaxy Stratosphere

Verizon Samsung Galaxy Stratosphere II

Verizon Samsung Galaxy S4
[Verizon Samsung Galaxy S 4] ngerber999:
Is anyone else having difficulty keeping Waze running due to the wonderful overheating messages that are apparently much more sensitive now? My device isn't hot to the touch and Waze was fine on 4.3...
[Verizon Samsung Galaxy S 4] jwhistler:
I'm still on rooted 4.3. Every once in a while I use TiBU to freeze another piece of bloat/crapware and run the phone for a few days to make sure there are no surprise side effects. I'm running the GEL launcher and the phone is very smooth and responsive. Yesterday I put 15 1/2 hours on the battery and still had more than 50%. Never had any reheating problems and have only had one spontaneous reboot about a month ago which has not recurred.

I'm beginning to think this will be my final version of Android on the last Samsung phone I will buy.
[Verizon Samsung Galaxy S 4] carguy37757:
Sorry if this has been discussed, but I couldn't find anything in search.

My wife and I have bone stock, non-rooted S4's. Since the update all has been well except for SMS messaging randomly not working. I performed a factory reset with no help, tried installing another messaging client with no help, and using hangouts which I thought helped but must have been a fluke because it no longer works regularly either.

Anyone else having this issue or a solution?
[Verizon Samsung Galaxy S 4] Blue Sun:
Oops, rooted I-545 running 4.3 was accidently updated to KitKat 4.4.2 and I lost root

HELP!

My original S4 had the updating software renamed so that I wouldn't even be notified about updates, but I had to get a warranty replacement. I rooted it, but forgot to turn of the ability to update. Last week, while I was undergoing surgery for a kidney stone, my wife was using the phone. She saw a message that an update was ready and, since her S3 is totally stock and she always updates, she hit the ok button. That night, I discovered I was no longer rooted and that KitKat 4.4.2 was the new O/S.

I am very dependent on functionality that will only run rooted, so I really need to clear this up. For example, I use RCB as my phone and text blocker and it requires root to run. It's big advantage is that it does this all silently before the call bubbles up to where non-rooted call-blockers do a pickup and hangup (with an annoying fragment of a ring each time). Since I'm unable to run RCB or a root-level file browser to recover the logs of blocked numbers to use (temporarily, I hope) in something like Mr. Number.

Is there anything I can do to either root under KitKat, or back down my version of Android to 4.3 and then re-root the standard way?

Blue Sun

"Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity."

-- Charles Mingus
[Verizon Samsung Galaxy S 4] myfishbear:
look at this
[Verizon Samsung Galaxy S 4] ian9654:
Blocking Update

I am sure that this has been answered in the past, but how can I keep the update prompt from asking me to install the update. Also how can I keep future updates from being prompted?

Thank you!
[Verizon Samsung Galaxy S 4] myfishbear:
i believe you freeze or delete sdm.apk and fwupdate.apk
[Verizon Samsung Galaxy S 4] swrght13:
Has anyone else tried this? I didn't think you could go back to MK2 from NC5.
[Verizon Samsung Galaxy S 4] caniswesley:
I didn't think it was possible either, but then I realized I'd done precisely that... It was risky, and quite honestly accidental, but I did it...
[Verizon Samsung Galaxy S 4] swrght13:
When you soft bricked, how'd you end up back on mk2?

Rooted, running CM 10.2 [4.3.1]
[Verizon Samsung Galaxy S 4] Scottchy014:
I've done a YouTube video showing you how to do this on your S4. Here it is: Protect Root Access from Over-the-Air Updates. Good luck!
[Verizon Samsung Galaxy S 4] klabit87:
If I am incorrect please somebody chime in and correct me.

But I believe the ability to Odin back to stock heavily depends on what bootloader you have at the time something gets borked up.

If you keep in mind what bootloader you have then you can always Odin back to that firmware version, I believe.

I just want to clarify since many many people have soft-bricked because of the bootloader/baseband/firmware mixture we currently have with MK2/NC2/NC5.

Once you get everything setup they way you like it whether you use [MENTION=3618916]gigilie[/MENTION] 's method or [MENTION=4939386]Surge1223[/MENTION] 's method

Run the commands in terminal emulator:

su
getprop ro.bootloader

as in my screenshot

I have NC5 baseband and stock rooted NC5 rom from [MENTION=4939386]Surge1223[/MENTION] but my MJ7 bootloader

So I should be able to Odin back to MJ7 if I am not mistaken.

Which is entirely possible as I am not a pro at all like these other amazing guys.

Maybe one of them can chime in and either confirm or debunk my thinking.

Just kind of throwing that piece of info out there.
[Verizon Samsung Galaxy S 4] caniswesley:
[MENTION=4168602]klabit87[/MENTION] - Thanks for your reply! I'm really quite intrigued by this little tidbit. If I took the 4.4.2 NC5 OTA after unrooting from 4.3 MK2, I would assume (though at the time I didn't have this command you just posted) that I was on NC5 boot loader. I don't imagine Verizon would've let me keep my MK2 bootloader. I used this command in terminal emulator and it returned:

I545VRUFNC2

So I'm going to keep with my hypthoesis that it is possible to downgrade from NC5 to NC2, though like you -- I would LOVE to hear some of the (far more knowledge than me Devs) such as [MENTION=4939386]Surge1223[/MENTION], or yourself. I think this wouldn't be entirely unreasonable to be able to downgrade from NC5 --> NC2 since one is just the leaked version of the other (perhaps???). At any rate, if this is the case, perhaps this is at least a rudimentary tiny hole in the NC5 setup, since from the NC2 bootloader I had MK2 successfully running for a while. Just my reply, hoping to keep this conversation going at least until someone comes along and illuminates my clear ignorance and utter idiocy :laugh: :highfive: :eek: It does look like that you can replace NC5 bootloader with NC2, though... which can run MK2 as your baseband...
[Verizon Samsung Galaxy S 4] klabit87:
I think it is entirely possible to go back to nc2 from nc5.

It was like that for MK2 to MJ7 those were the two that could be flashed back and forth.

It all depends on whether they incremented the fuse counter on aboot or not between NC2 and NC5.

Which I would see no reason to increment it being that NC2 was originally intended as internal testing only.

Then again nobody knows (or cares) why they allowed MJ7 and MK2 to go back and forth. Unless the two aboots are exactly the same as far as code and security goes.
[Verizon Samsung Galaxy S 4] caniswesley:
[MENTION=4168602]klabit87[/MENTION] - I think that's the key! For people who take the OTA NC5 Update accidentally or intentionally, and decide later they want to go back to root with NC5, they can probably do it via an NC2 bootloader downgrade!

I've no doubt the Devs probably already figured this one out ;p, but I do still feel clever (if only for a moment).
[Verizon Samsung Galaxy S 4] klabit87:
I'm pretty sure they have known it for a while. As soon as they can, they tear open the aboot to examine it.

I just thought it would be good to note that people should pay attention to which bootloader they have.

Whether it's MK2 or NC2/NC5 since that would help reduce the soft-bricks and bootloops that I keep seeing.

If you have to Odin use the Odin image for your bootloader then start over.

There are downgrade methods for NC2 and NC5 firmwares. Just can't go from NC2/NC5 to MK2 bootloaders.

This causes the problems when attempting to do so.
[Verizon Samsung Galaxy S 4] Surge1223:
I'm not sure which question(s) people would like an answer to but let me try to clear some things up. If you upgraded from MK2 to NC2 at any point in time, then your bootloader is NC2 most likely (in the original directions I posted I said it was optional to flash the NC2 "BL" tar but I found most people flashed it anyways) so when I released the NC5 method I removed the "BL" tar so people who upgraded from MJ7/MK2 to NC5 are still on the MJ7/MK2 bootloader.

Just like how MJ7/MK2 are interchangeable (meaning you can flash either or over the other) the same applies for NC2/NC5

You can downgrade to the MK2 system and kernel partitions after taking the NC5 OTA or flashing the NC5 Odin tar (though your bootloader will remain on NC5).

Everytime I mention this I get a lot of messages blaming me because wifi and sound wont work after downgrading, I started to get frustrated once people started complaining that bypasslkm wouldnt remain after a reboot (like typing a few lines of code after reboot is a burden or something) we're lucky we even have bypasslkm in the first place.

This is supposed to happen, and to cure sound you have to flash the NON-HLOS from the bootloader you're currently on. To fix wifi you have to use bypasslkm.
[Verizon Samsung Galaxy S 4] klabit87:
The only point I am trying to get across is that people should be aware of which bootloader they have.

If they know which bootloader they have, then they have to Odin using the corresponding tar otherwise they get bootloops/soft-bricks.

Correct??

Once they successfully Odin with the appropriate tar they can start over to downgrade/root/Odin prerooted NC5 whichever direction they desire.

I know I'm not anywhere near as good as you but I like to think this could be important to those that will read this to understand this.

EDIT:

I agree on the bypasslkm which is why I started on the app which [MENTION=3618916]gigilie[/MENTION] completed by creating a flashable zip to alleviate some of the complaints.

Thanks to [MENTION=3618916]gigilie[/MENTION] for taking the ball and running with it.:good:
[Verizon Samsung Galaxy S 4] Surge1223:
Your point is valid, knowing the bootloader you're on determines the Odin tar you can flash and the probability that the flash will be successful.
[Verizon Samsung Galaxy S 4] JTSDeveloper:
Sorry for the same question over again but so I took the nc5 update from mk2. Is it possible to downgrade ?
[Verizon Samsung Galaxy S 4] mdeblaz:
I'm also having this problem, very frustrating. Sometimes it's only SMS that doesn't work, or just MMS, our even both.

The only way I've temporarily fixed it is to go to airplane mode or reboot.

Is this a radio issue?
[Verizon Samsung Galaxy S 4] klabit87:
Yes. Look here for surge's method

http://xdaforums.com/showthread.php?t=2726868
[Verizon Samsung Galaxy S 4] RemnantKing2:
A question out of curiosity, if we're able to downgrade from NC5 to MK2, why can't we downgrade form NC5 to something earlier than MK2, or from MK2 to something earlier than that?
[Verizon Samsung Galaxy S 4] mike.s:
Why would you want to? The reason for downgrading to MK2 system is so you can saferoot (or as originally intended, to simply recover from a failed upgrade).

You are NOT downgrading the bootloader when you do that, and it's downgrading the bootloader to MDK which is needed to open things up beyond root.
[Verizon Samsung Galaxy S 4] RemnantKing2:
I thought that by downgrading to MK2 you're also downgrading the bootloader as well, which was the reasoning behind asking my question.
[Verizon Samsung Galaxy S 4] mike.s:
The current procedures in the OP don't touch the bootloader for either upgrades or downgrades (which wouldn't work, anyway). That's why a build.prop change is needed to get PIN unlock when upgrading (because of the bootloader mismatch) and why there are hacks needed to get sound and WiFi working when downgrading (on a phone with an NC2 or NC5 bootloader).

The NC2 upgrade provided an optional upgrade to NC2 bootloader, which is why people might now be running NC5 system with any of MK2, NC2 or NC5 (if they took the OTA) bootloaders.
[Verizon Samsung Galaxy S 4] J-Rock28:
Has anyone else that took the OTA been having horrible signal? I used to have strong 4G signal at home and at work, now all I can get is 3G unless I'm outside. Extremely frustrating...
[Verizon Samsung Galaxy S 4] tadiv:
Can someone post links to all the listed / needed files? - saying such-and-such a file from Surge1223's posts leaves me searching and searching (Surge1223 has many, many posts)...
[Verizon Samsung Galaxy S 4] Hashbang173:
+1 Have lost 4g more often, I wonder if you call verizon they will downgrade you somehow.
[Verizon Samsung Galaxy S 4] tadiv:
Thanks to Surge1223, I found the files needed to downgrade...
[Verizon Samsung Galaxy S 4] carguy37757:
Anyone have any input on this issue?
[Verizon Samsung Galaxy S 4] Eddie Hicks:
Replied to wrong user. Deleted.
[Verizon Samsung Galaxy S 4] Jraider44:
Anybody else still having overheating issues on 4.4.2?? I've had em bad since I got the phone.. Any suggestions to correct this issue? Thanks in advance guys!
[Verizon Samsung Galaxy S 4] ickray:
Only things I've noticed is, slight occasional studdering so to speak, like when I flip through the app drawer fast, and or do alot of things at once. Also the keyboard seems to sometimes lag, and or not even pop up at all especially happens when using chrome. I'll go to type in a url and it takes a few seconds sometimes for the keyboard to pop up. Let's not forget about how fast the battery drains now, but we all know this. Anyone else having these problems?
[Verizon Samsung Galaxy S 4] Mistertac:
What is the actual temp the phone is at do you know? They do run warm enough that it can scare someone yet it's not actually harming the phone. Granted I'm with you guys I'd like to not have my phone so hot that it's noticeable like that. There's so many bugs with each ota as far wakelocks etc that the phones are really never going to sleep and they're always " working"
[Verizon Samsung Galaxy S 4] Jraider44:
According to the battery widget I have , it reaches to 110 degrees Fahrenheit sometimes, it usually starts to get noticeable (and I stop what I'm doing) at around 100 degrees
[Verizon Samsung Galaxy S 4] Mistertac:
Just browsing and texting and not doing a crazy amount mine is usually around 100 and usually with my usage can reach 105 . so your 110 doesn't seem to crazy. KToonsez made his CPU Monitor display in Celsius because people frequently get spooked by the high numbers if it's in Fahrenheit.

Mine runs at these temps on an AOSP ROM with a custom kernel with next to no wakelocks. Each phone runs different obviously but I wouldn't be too worried just yet.
[Verizon Samsung Galaxy S 4] Jraider44:
OK thanks for the input! Glad I'm just paranoid
[Verizon Samsung Galaxy S 4] Mistertac:
Mine is running between 95 and 107 currently with a performance profile for my kernel...
[Verizon Samsung Galaxy S 4] ppat324wi:
Mines running at around 80-90 even though I use it a lot. Probably because my office keeps their air conditioning on all the time.
[Verizon Samsung Galaxy S 4] Redflea:
Mines at 95°, yet the cooing down mode is showing in notifications. Something's not right with this function.
[Verizon Samsung Galaxy S 4] mbl1979:
That is exactly right. Looks like the only thing that changed was the white icons at the top, and a short cut for default apps. 4.4.2 was on my S4 when i got it off Craigslist. Miss my HTC DNA lol.