yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] bryantjopplin:
I prefer the getprop app, it's simpler. Lol

Why are you on mk2 bootloader? [emoji85]
[Verizon Samsung Galaxy S 4] jds3118:
Hahaha I'm not that's my friends phone. It was blacklisted on sprint for nonpayment so now I have it fully functional on t mobile?
[Verizon Samsung Galaxy S 4] mochamoo:
Baby steps.
[Verizon Samsung Galaxy S 4] Gahar:
I gave up on stock TW 4.4.2 rom ran for about 2 months without any issues maybe one or two but its great rom but the battery life since day one was driving me crazy it wouldn't last me one full day and i don't game on mobile. Tried KTweaker and different profiles and few tweaks here and there but no luck. So i installed S4 GPE 4.4.4 rom and ran for about a day with my normal use and all my apps no gaming and the Battery lasted 30 hours and I still had 12% left. Got some ported S4 and S5 apps and phone is good to go.:)
[Verizon Samsung Galaxy S 4] CC268:
Just normal factory wipe and cache and dalvik before installing this? Everything working on this? I am on MDK but just want stock NC5 like I would get straight out of the box...I don't mind that the bloat, etc has been removed.
[Verizon Samsung Galaxy S 4] dark_overload:
I'd also wipe the internal and external SD (after backups of course). We're still testing but it seems that earlier versions of android might leave behind some sort of possessed file in one of the paths that the media scanner process regularly scans. Whatever it is the mediascanner code in JB was fine with it but Kit kat chokes and dies. The best thing to do for now is just what mochamoo and I have dubbed the "shotgun wipe."
[Verizon Samsung Galaxy S 4] CC268:
I actually don't have an SD card...never picked one up for this phone for some reason...what is the shotgun wipe?

Also...is NF1 technically the newest release? I figured I would just try NC5 since it is the newest Verizon release?
[Verizon Samsung Galaxy S 4] dark_overload:
As bryantjopplin was kind enough to point out on page 101; NF1 is the international ROM while NC5 is the Verizon ROM. The last 10-15 pages of this thread are almost primarily dedicated to the main issue (random reboots) and solution (shotgun wipe) that I've discovered so far. You still have an internal (emulated) SD that may or may not hold the haunted folder. Lol.
[Verizon Samsung Galaxy S 4] CC268:
Can you link me to this so called shotgun wipe? Do you still do the standard factory wipe plus dalvik and cache?
[Verizon Samsung Galaxy S 4] dark_overload:
I'm sorry if I didn't make this clear enough: the shotgun wipe means to format your internal and external SD storage.
[Verizon Samsung Galaxy S 4] Scorp123:
I switched to this kernel

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

And I have not had a reboot, freeze, or any other issues since. I'm also getting the best battery life and performance I've ever had on this phone with the pegasusq governor. That's the only change I made to the kernel
[Verizon Samsung Galaxy S 4] CC268:
Ahh gotcha sorry about that. So for instance in TWRP I would select "Internal Storage" as well as Dalvik and Cache. Also do the Factory wipe as normal.
[Verizon Samsung Galaxy S 4] dark_overload:
That's affirmative. I'm not exactly sure where it is in TWRP because I use CWM (it's under advanced for me).
[Verizon Samsung Galaxy S 4] CC268:
Same here! I appreciate the help!

Any other suggestions? I am already on the NC5 Radio and I assume the stock kernel with this will be fine.
[Verizon Samsung Galaxy S 4] dark_overload:
You could also upgrade any of the other kernels people speak of here if you wanted to. The options are limitless if you have the knowledge. Scorp123 suggested a popular kernel. Though I highly doubt which kernel you run has anything to do with the bad file issue. That has already been investigated and discussed. I've upgraded to the latest KT kernel. It's entirely up to you.
[Verizon Samsung Galaxy S 4] CC268:
Also...won't wiping internal storage delete the ROM I need to install? How would I even install the ROM?

Thanks maybe I will try the KT kernel down the road.

---------- Post added at 09:04 PM ---------- Previous post was at 08:53 PM ----------

I just need to verify how I would install the ROM if I am going to wipe internal storage. Should be good to go once I get that figured out
[Verizon Samsung Galaxy S 4] dark_overload:
Make a backup. Backup backup backup. You could mirror your storage for ease of re-deployment but don't forget about nandroid backups too. Afterwards you would wipe from within your current system, then copy just the necessary zips back onto the internal storage before install.
[Verizon Samsung Galaxy S 4] CC268:
Dang...don't have an easy way of doing that with no SD card...I could never figure out how to get my phone to mount in recovery either to copy files over from my computer...
[Verizon Samsung Galaxy S 4] dark_overload:
Do the nandroid backup before you backup your internal storage (Hint: MTP over USB) and your nandroid backup will come with it (in the "clockworkmod" folder).
[Verizon Samsung Galaxy S 4] CC268:
Alright sorry it has been a long time since I have done all this. I actually already installed the ROM...I could make a Nandroid backup in TWRP...then backup internal storage? I guess this is a just a bit over my head. Sorry about it...maybe I will just have to deal with it and hope I don't get the reboots. I would like to know how to do this, but I would need like step by step lol.

I could switch to CWM to make it easier as well
[Verizon Samsung Galaxy S 4] CC268:
Why is the full stock package NC2 and not NC5?
[Verizon Samsung Galaxy S 4] Redflea:
You guys don't necessarily need to wipe your internal/external storage to install/use this or any other ROM. If you run into problems you might want to do it later. I never have, and am not having battery life issues. Do a normal factory reset, install and see how it goes first.

---------- Post added at 07:16 AM ---------- Previous post was at 07:12 AM ----------

NC2 was an early leak of KitKat, the zip installs the full Verizon build.

NC5 is the formal Verizon KitKat release, Jkruse provided an aroma installer on those two builds he made to allow you to choose what to install.
[Verizon Samsung Galaxy S 4] dark_overload:
Now you see why it is so hard to track down this bug. Not everyone suffers from it. Like I said in a previous post though: if you want to be 100% sure there will be no reboots then do the shotgun wipe. You don't have to do it, but there's a chance you could run into issues if you don't.

Doing the shotgun wipe after the fact may or may not help, I'm not sure. When I did it, I also re-installed the system, clearing caches and such along with it. I cannot say whether or not the haunted file causes any detrimental changes so better safe than sorry.

I'm not going to explain my findings again, this issue has been discussed in depth and if anyone wants to learn they can use the previous and next page buttons.
[Verizon Samsung Galaxy S 4] Redflea:
Thanks, that's fine. My point/opinion is that just that it's overkill to tell everybody that they have to do this, as long as we don't make people feel like it is a requirement for everyone I think it's a good thing that you provide info/options like above. :)
[Verizon Samsung Galaxy S 4] mochamoo:
If it is the media scanner causing the reboots it is worth going into app manager. Stop the media storage app, clear cache & data. Reboot. This may help and is worth a try before the shotgun wipe.
[Verizon Samsung Galaxy S 4] dark_overload:
I actually already tried that. That doesn't help. The problem lies in a scanned file, not in the cache of scanned meta data.

---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------

Oh I agree. I didn't say it was mandatory. That's just my recommendation. I am still waiting on more data to narrow it down.
[Verizon Samsung Galaxy S 4] Redflea:
Good point, I should have mentioned that, as it's solved problems for me in the past as well.
[Verizon Samsung Galaxy S 4] stang5litre:
Anyone remember how to make your sdcard your internal memory? Tried the app but doesn't work with emulated storage. I know there is a work around can't remember it off hand. Getting that storage message. It's like you can have only 4 hd games and your through. Hope someone remembers the fix. I had a flash zip for it gonna search for that . Any info is greatly appreciated
[Verizon Samsung Galaxy S 4] Redflea:
I believe there is a post in this forum, in our GS4 section. Don't remember where it is, exactly, but someone had posted a process.
[Verizon Samsung Galaxy S 4] stang5litre:
Thanks ill have to look some more . Found a method for s3 but not with emulated storage
[Verizon Samsung Galaxy S 4] Redflea:
Found this...

http://xdaforums.com/showthread.php?t=2468596
[Verizon Samsung Galaxy S 4] stang5litre:
Thanks I feel asleep last night reading hahaha. I'll give this a shot. Thanks a million. ☺ if this works hello hd games. Will report back
[Verizon Samsung Galaxy S 4] CC268:
Big problem here and no one can seem to help. When I try to reboot into recovery I get get a message from Verizon on my screen saying I have software on my phone that isn't authorized and I should take it to a Verizon store. In the top left hand corner in red it says Secure Failed: Kernel...does anyone have any idea how I can fix this...can't even get into recovery...everything works if I restart but no way to get into recovery now

---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------

This is so bizarre...never seen anything like this...looks like I may be screwed
[Verizon Samsung Galaxy S 4] jds3118:
You need to flash loki-doki patch or a kernel like ktoonsez that has loki built in

Sent from my UPSM v25.1 S4.9
[Verizon Samsung Galaxy S 4] CC268:
I am on MDK though? But I will give that a try
[Verizon Samsung Galaxy S 4] jds3118:
Did you try 3 button combo to access recovery? I've only seen that message when a non loki kernel is flashed on MDK without flashing loki after, example if you flash AEL kernel without the loki patch zip afterwards.

Sent from my UPSM v25.1 S4.9
[Verizon Samsung Galaxy S 4] CC268:
Yea I've tried it all...well I will try the loki doki thing
[Verizon Samsung Galaxy S 4] crossen0:
Manually boot into download mode. Then then tell the phone to reboot and hold power and volume up to boot into recovery.
[Verizon Samsung Galaxy S 4] CC268:
Hmm I will try that...Although you only get like half a second to do anything when you get to the download mode screen lol...I will try that though
[Verizon Samsung Galaxy S 4] dark_overload:
We had another fella with that same problem last week. Your recovery image should be lokified. Either that or your bootloader is locked.
[Verizon Samsung Galaxy S 4] mochamoo:
Power down the phone. Then PRESS AND HOLD VOLUME UP + Home Button + Power. Keep holding HOME + Volume UP, but after vibrate release power. That should get you into recovery. Once there flash loki-doki.zip. Then you should be good to go. I have sometimes tried using the vol down button for this and that frustrated me to no end until I got it that it should be the vol up button :)

What kernel do you have on your phone?
[Verizon Samsung Galaxy S 4] CC268:
Pretty pissed....I was on MDK and unlocked bootloader and getting into recovery the manual way doesn't work. it is the stock kernel that comes with this ROM which is ktoonz...I don't even know how I can flash any fix if I can't get into recovery...

How can I even do anything with no recovery..basically can't change anything now.

---------- Post added at 04:17 PM ---------- Previous post was at 04:12 PM ----------

My phone now says Security Software Version: MDF in the About Phone menu...
[Verizon Samsung Galaxy S 4] mochamoo:
Something similar happened to me a while back and think that it has something to do with the official twrp version that I had on my phone. I ended up having to install ktoonez modified twrp. But to get there I think that I ended up getting koush's rom manager to flash cwm. Then eventually I was able to flash kt's version and all was good again. I might have the steps wrong but maybe that will help get you going. Can you boot up the phone at all?
[Verizon Samsung Galaxy S 4] jds3118:
Try a stock rooted tar file in odin then flash recovery tar file in odin. That should get you back.
[Verizon Samsung Galaxy S 4] CC268:
You may very well be right. I am done with TWRP...always had issues with it. I actually flashed CWM through some Playstore app, but even that didn't work. I forgot about the ODIN way, but I will do that.

---------- Post added at 04:54 PM ---------- Previous post was at 04:39 PM ----------

[/COLOR]Think this phone is pretty well done...It just sits at the Verizon screen now

---------- Post added at 05:24 PM ---------- Previous post was at 04:54 PM ----------

I may just have to take into Verizon...I have been rooting and running custom stuff since the Thunderbolt days and never seen anything like this. Part of the reason why I have been out of this for about a year is because of the increased risk with doing this stuff now a days. If I can get it back some how I am saying goodbye to root and custom recovery and going back to locked down and stock.

---------- Post added at 05:55 PM ---------- Previous post was at 05:24 PM ----------

Finally got it to work thank god
[Verizon Samsung Galaxy S 4] stang5litre:
Running MDK with rom. As stated before only need loki when your using a different kernel than ktoonz. What version you flash? He has several out. He makes them monthly almost . Aroma installed? And several ways to get to recovery?.
[Verizon Samsung Galaxy S 4] mochamoo:
Glad you got it working. What ended up working?
[Verizon Samsung Galaxy S 4] jds3118:
Odin is your friend ?
[Verizon Samsung Galaxy S 4] CC268:
Alright guys so i am on stock MDK and stock kernel...flashed CWM, but still get the same message when trying to get into recovery
[Verizon Samsung Galaxy S 4] iwearthebelt:
Try downloading TWRP version 2.7.1.0 recovery.IMG from twrp's website and install it using Flashify from the play store. I'm still on the MDK bootloader and this recovery version is working great.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Making this way to hard guys, try using root checker first, then off you get that then download terminal emulator and type

getprop|grep bootloader

What is your output?

Then if that is mdk, got to play store and download this.

https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools

Follow instructions for jfltevzw and I would recommend twrp imo of using about 6 or 7 recoveries since rooting phones.
[Verizon Samsung Galaxy S 4] CC268:
I got it fixed...won't use twrp anymore though...had too many issues with it. Cwm from now on
[Verizon Samsung Galaxy S 4] dark_overload:
Boy am I glad I never tried upgrading from CWM... Lol, I just always figured if it ain't broke don't fix it. If you have any more problems (or we have this issue again with someone else for that matter) I've dug up my old loki_flash and recovery.lok files. PM me for them, as I don't want to feel guilty when someone who doesn't know how to use the tool finds it here and bricks their phone. You have to have root to flash recovery though.
[Verizon Samsung Galaxy S 4] Redflea:
I've had zero problems with TWRP...YMMV regardless of which recovery you choose, but in my experience TWRP has been excellent.
[Verizon Samsung Galaxy S 4] dark_overload:
It probably has something to do with how the scripts in the zip handle flashing. Also, I think the recovery partition has its own independent kernel. Anyone know for sure?
[Verizon Samsung Galaxy S 4] gpz1100:
I posted this in the other (international) thread but didn't get much of a response. What are the functional differences between this and the international version?
[Verizon Samsung Galaxy S 4] CC268:
I think it was TWRP that screwed something up...which isn't unusual...it has done wacky things like that in the past. I won't use TWRP anymore, too many issues and I think the development for it is not up to par with CWM. CWM has always been stable/
[Verizon Samsung Galaxy S 4] maplewood:
coming late to this thread. Two questions:

Can/should this be installed installed with Safestrap? If not, how? Odin?

(and I guess there is a third: If not SS, should it be removed first?)
[Verizon Samsung Galaxy S 4] casey225:
Just flashed the rom yesterday and noticed that my wifi and mobile data indicators in the notification bar stay white and never turn blue, although I have been able to connect to play store and google apps without problems. Stock battery indicator is also now white, it in case it matters. Is this supposed to be the case with this rom? I've searched the thread and haven't been able to find this mentioned. Thanks in advance!
[Verizon Samsung Galaxy S 4] heath2805:
Everything in notification bar is white on kk roms.
[Verizon Samsung Galaxy S 4] casey225:
Did this fix the problem? I just flashed the rom a few days ago and having the same issue. Happens at least half the time I use the camera. Lost several pics I would've really liked to have.

This also brings up another problem I'm having both with camera app induced reboots and with random reboots, sometimes it won't boot to system. It shuts down then shows battery charging screen and stops there. If I hit power button, it vibrates and displays battery charging screen but that's all. I have to boot to recovery and then boot to system from there.

I'm hoping a reflash might fix both. If so, would a dirty reflash be adequate or is full wipe necessary. I'm using twrp 2.7.1.0 unmodded.
[Verizon Samsung Galaxy S 4] MHotovec:
If you're reflashing to fix problems, don't even consider doing a dirty flash.
[Verizon Samsung Galaxy S 4] k1mu:
No. Read the title: "For MDK BootLoader". If you're running Safestrap, you're past MDK and can't use this.
[Verizon Samsung Galaxy S 4] ViperGeek:
Easiest way to go from Full Stock NC2 to NC5?

Thank you for this! I've been waiting (and procrastinating) to upgrade to a VZ KK full stock+root image. In my haste, I didn't even notice the "NC5" in the first URL and "NC2" in the second and third. Now that I've installed I545VRUFNC2_4_17_14.zip, customized it, and installed my kazillion apps, is there an easy, painless way to update to NC5?

In a related question, does anyone have the changelog for NC2 to NC5?

Thanks!

- Dave
[Verizon Samsung Galaxy S 4] evilryry:
just want to say the nc5 aroma rom works for SS. just remove the ktweaker apps and stuff. works fine.
[Verizon Samsung Galaxy S 4] Velocifero:
Hey man, did you get my PM about the toggle themes? You volunteered to help me implement them but I haven't heard anything from ya in a while.
[Verizon Samsung Galaxy S 4] evilryry:
I thought I pm'd you a zip for it last week?
[Verizon Samsung Galaxy S 4] haza12d:
I recently started having problems with my phone with the home button not working when you single press it. It works when you double press and when you long press. I didn't know how to fix it so I decided to do a factory reset in recovery (I'm running Philz). After it booted up, I can't seem to access stuff on my SD card. I can't seem to find folders when I use My Files, ES File Explorer, or Root Explorer. I'm not sure that it was like that before I wiped data. Is there a fix for this? I'm thinking I can wipe again and flash this over again.
[Verizon Samsung Galaxy S 4] casey225:
I just started having the same problem with the home button. I hate doing FDRs, let me know if this works.

Secondly, I got a notification yesterday for a software update. I just assumed this was disabled. Has anyone else received this? I suspect Verizon wants to steal our mdk bootloaders!
[Verizon Samsung Galaxy S 4] syintiphic:
I haven't received a notification for an update. I checked and didn't see the SDM or FW Upgrade apps in this ROM. I think those are the usual ones.
[Verizon Samsung Galaxy S 4] casey225:
The one I'm referring to is simply named "Software update" ver. 2.131231 Had to go into application manager > all to find it. I turned it off and now it is located in the Turned Off list. Interestingly, when I went to get this information, there is now a Software udate app listed in the All list, but is version 6.140111. Turn off option is grayed out, but, I can force stop. When trying to do a long press to get app info, I accidentally tapped the first time and it gave me a confirmation page. When I hit cancel, I got a second window stating that if I cancelled I would not be able to perform the update OTA. It was shortly after this my home button quit working and some apps which had root access previously needed to be granted permission again. Also some of my settings and preferences were changed. I suspected this app was responsible for the home button issue, but, after a little searching, this seems to be common problem with S3 & 4 users after KK update, so now, I'm not sure. I assumed this was a Samsung or Verizon OTA update app, anyone know for sure what this app might be?
[Verizon Samsung Galaxy S 4] syintiphic:
I checked my application manager and didn't see a "Software Update". I'm not sure what that is. Sorry I couldn't be of more help.
[Verizon Samsung Galaxy S 4] casey225:
I checked my Galaxy Tab Pro (stock rom, rooted, wifi only) and it also has 2 versions of this same app, so I assume it is from Samsung. Wanna guess how long it took me to freeze those suckers!!! I was encountering more and more problems daily - totally messed up my toggles and couldn't pull down full list, TiBu said my android ID had changed, etc. Totally screwed my phone. Finally forced me to FDR and that has fixed everything, so far, with exception of one random reboot while TiBu was restoring my apps.

Well crap, I may have found the problem. I just installed Xposed framework and home button problem started immediately after the reboot.
[Verizon Samsung Galaxy S 4] calebcabob:
I'm running this right now and its flawless! I'm really liking it! I hope to see more ROMs off this build!:)

Thanks a lot for this!!!
[Verizon Samsung Galaxy S 4] syintiphic:
Same here. :thumbup: This was the first ROM I installed when i got my S4 a few weeks back. Very nice so far and I'm pleased with the performance.
[Verizon Samsung Galaxy S 4] Malaclypse5:
Help - Lost Bootloader?

Clearing this post but reporting the behavior: came from hyperdrive, after running this rom went into soft brick going back to hyperdrive but could still flash this rom, usually with weird behavior, several reflashes to no avail, I checked buildprop, still showed MDK, reinstalled latest TWRP, dirty flash and FDR and back in business, see posts few pages back if you have these issues: the big sign for me that this had to be done was home button not working on single press.
[Verizon Samsung Galaxy S 4] calebcabob:
Hey I'm currently running VZW_NC5_AROMA_4_29_30 and want to flash the S5 Theme from [MENTION=1949695]jrkruse[/MENTION]. However, I read that the theme was originally intended for use with the I545_VRUFNC2_AROMA_4_18_14. Can anyone tell me what I might be sacrificing if I were to switch over to the NC2 build...like features, bug fixes, etc. Thanks everyone:)!!
[Verizon Samsung Galaxy S 4] casey225:
Has anyone found a solution for this yet? I have done FDR and reflashed ROM a couple of times, mainly to fix home button issue. This has cured pretty much everything except this camera issue. This happened to me multiple times this weekend causing me to lose several important pics - quite frustrating! Since this never happened with MDK, would installing the camera apk from a different build be worthwhile?
[Verizon Samsung Galaxy S 4] calebcabob:
Does anyone know whether or not this Ultra Power Saving Mode S5 mod should work fine for us? I've currently got the NC5 build going.

Thanks for any feedback:good::)
[Verizon Samsung Galaxy S 4] calebcabob:
This definitely isn't bad!