yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Scottchy014:
The craziest thing happened to me last night. When I was upgrading to NC5, going through the Aroma installer, I hit the "back" button (I wanted to add another Samsung App) and my phone completely froze up. I couldn't hit the "next" or the "back" button. I had to pull the battery and install the MK2 downgrade just to get my phone to come alive again.

After I rooted, SS'd, and flashed the NC5 .zip, I decided to test my theory again. I hit the "back" button and froze my phone again. I'm not quite sure what happened but I wanted you all to know this. I'm pretty sure I can upgrade to NC5 but I just left my phone in MK2 mode for now.

Has anyone else hit the "back" button with success?
[Verizon Samsung Galaxy S 4] gregwhit:
Same exact thing happened to me yesterday... I thought I did something wrong... Appreciate you taking the extra step to confirm hitting the back button buggered it up, twice! My resolution was kind of similar to yours...

For some reason, I could not get into SS after it froze, only the original boot loader (MK2?). I tried to flash but it wouldn't take. So I put it in Download mode and tried to install w/ ODIN. Unfortunately, I could only get it to boot up to the Custom logo and it stopped...

I was getting a little concerned that I really screwed up my phone. So I connected my phone to my computer and let the Verizon Software Update application install NC5 (via Download mode). I realized I'd loose root, however, I just needed my phone working and I know the Developers here would get that sorted at some point.

After my phone was up and running it really started to bother me that I missed something or didn't follow one of the steps, so I tried again... I followed the process outlined in the OP to downgrade to MK2, and low and behold, it worked. I was concerned that taking the update from Verizon would not make that possible... Then I rooted the phone with SafeRoot and installed NC5 as outlined in the OP. Now I'm loving my phone and I am not having any issues!!!

Just wanted to share my experience for the greater good. Really appreciate everyone here who makes this possible, especially the Developers- many thanks [MENTION=4939386]Surge1223[/MENTION].
[Verizon Samsung Galaxy S 4] lazer9:
[MENTION=4939386]Surge1223[/MENTION] Sorry if this is a stupid question but I had taken the original path from HD RLS15 on my stock MJ7 to get to your previous NC2 KitKat prerooted. This contained the BL flash as well as the others of course.

When I had tried to update to your current NC5 prerooted, if you recall, I made the mistake of choosing that SS module thing in Aroma which caused havoc and made me have to use your "Downgrade to MK2" process to get back up and running and then proceed to NC5.

Now my question. Am I still on the NC2 KitKat bootloader OR is my bootloader back to MK2 because of that downgrade step? I know all the downgrade files were flashed in the AP slot in odin and non to BL so I'm just uncertain where I'm at regarding the bootloader and thinking knowing this may be important if other SS compatible Roms start popping up that I want to try?

Thanks.
[Verizon Samsung Galaxy S 4] aknotts415:
So not sure if this is a dumb question but are there any 4.4.2 SS NC5 Roms yet or is everyone stuck on the stock root nc5 rom in this thread?
[Verizon Samsung Galaxy S 4] JeeperDon:
FYI: The sensitivity classes are on Tuesdays and Thursdays.
[Verizon Samsung Galaxy S 4] quarky42:
The software update function is disabled as far as I can tell. You wouldn't want it to automatically update to something that kills your root and can't be rooted.
[Verizon Samsung Galaxy S 4] {davros}:
i got one booting perfectly just WiFi doesnt work .. yet
[Verizon Samsung Galaxy S 4] aknotts415:
huh lol
[Verizon Samsung Galaxy S 4] quarky42:
The easiest way to disable the update function: Remove the APK (application) that handles the updating.

The tradeoff: Although just removing it is nice, it doesn't remove the button from the user interface. This means that there is a button pointing to nowhere. Programs don't like that. It causes "exceptions" or errors.

This is a situation of: "Doctor Doctor, it hurts when I do this." "Well, don't do that.". (Because, I'm pretty sure it was intentional.)

The hard way to disable the update function: Remove the APK (application) that handles the updating. (okay, so that part is easy.) Then, you go into the Settings User Interface Framework and actually start removing code that makes the button show up. This isn't "hard" for people that are really intimately familiar with this particular UI, but for someone with different goals, just removing the APK is good enough.

I don't mean to put words into Surge's mouth. I just suspect that this is what is going on. I've seen this done numerous times before on different stock ROMs where the update function is disabled in and quick and dirty of a way as possible. You call it a bug, but the update function is supposed to not work on this ROM. You aren't supposed to click on it. I understand the curiosity aspect of it, but it won't work, it isn't expected to work and the amount of effort it would take to remove that button is far more time consuming than: "Don't click it".

I hope you don't think I'm being mean here. I'm just trying to be as clear as I can without overloading you with detail and without holding back too much detail.
[Verizon Samsung Galaxy S 4] lazer9:
Just thinking out loud here but maybe Surge's jfltevzw-FN2-modules.zip from the original NC2 upgrade would be helpful to get the wifi going? :confused:

Again, this is just a wild guess. Proceed at your own risk or until Surge chimes in. I'm still trying to figure out what bootloader I'm on, lol :laugh:
[Verizon Samsung Galaxy S 4] {davros}:
I tried a variety of different patches and flashing combinations.
[Verizon Samsung Galaxy S 4] tech_head:
If you followed this thread and went from MJ7/MK2 to NC5, you are still on the MJ7/MK2 bootloader.

If you had the "screen lock" issue you are not on NC2 or NC5 bootloader.

If you did the MJ7/MK2 to NC2 on the original thread and didn't uncheck the BL area in Odin, you are now on NC2.

I don't think anyone on this thread could have gotten to the NC5 bootloader, but I could be wrong.

This stuff is what I remember but ..... YMMV
[Verizon Samsung Galaxy S 4] lazer9:
That's the thing. I did both in reverse order. So I'm really not certain where I'm at regarding the bootloader. I'm guessing still NC2 as I "don't think" doing the downgrade later in the game, downgraded the bootloader but I could be wrong.

I don't mess with the "Screen Lock" as I don't use pattern, pin, ect... :p
[Verizon Samsung Galaxy S 4] quarky42:
No worries. It doesn't hurt to bring stuff up and discuss them.

If I felt really really adventurous I would try and decompile the framework, pull out that button and recompile it. I've done something like it twice before. The first time I had to completely odin my phone. :/ The second time I was much more successful. The only reason I don't give it a try for the fun of it is I have absolutely no idea what was different between the two attempts, why one was successful and the other failed. I did it the same way both times or so I thought.
[Verizon Samsung Galaxy S 4] moonglows:
Not exactly sure what CSC.apk does but looking at other resources both on this site and others, here are the likely things that might break if you rename it:

CSC com.samsung.sec.android.application.csc CSC.apk /No/ Country Specific Codes, controls APN settings, etc.

com.samsung.sec.android.application.csc CSC.apk Breaks finding and installing things from the CSC like apn settings
[Verizon Samsung Galaxy S 4] tech_head:
Actually, when you go from NC2 down to MJ7/MK2 you keep the NC2 bootloader.

From the original NC2 posts.

"4. I was going to type something about Wifi...but this issue drives me crazy...(...its not a issue, learn adb) You need to use bypasslkm. Flash the NC2 hlos for sound to work and use bypasslkm for wifi"

The WiFi will not work and you need to be rooted again to get it to work if you want the MK2 system after updating the bootloader to NC2.

You my friend are on the NC2 bootloader.
[Verizon Samsung Galaxy S 4] Surge1223:
Yep you are correct this was done intentionally :)

NC2, as im sure you aleady have figured out :)
[Verizon Samsung Galaxy S 4] hipcarrot:
Slowdowns

Hey everyone,

Two days ago I successfully upgraded to 4.4.2 from MK2 and kept root. However, my phone has been incredibly choppy and slow. Has anyone else experienced this? Any info would be appreciated. Thanks.
[Verizon Samsung Galaxy S 4] Surge1223:
Collection of flashables

Extended Power Menu - reboot recovery + download, plus screenshot and flashlight

S5 SystemUI

4.4.2 International Keyboard
[Verizon Samsung Galaxy S 4] shindiggity:
Hey surge I'm on nc2 and I run international Roms but can't get a gps lock, there are no stock nc2 Roms to flash enable gps and then load my backup to get a lock. Any ideas on how to get a gps lock. I know wrong thread but ur a very smart guy and was hoping u could help.
[Verizon Samsung Galaxy S 4] JeeperDon:
Surge, I did this procedure (MK2->NC5 without the removed.zip added) when first available and don't really have any problems now, even have Google Now Launcher working fine, including 'OK Google'. I intend to get the phone to a nice clean 4.4.2 place and leave it. I think I have that now, from an outside point of view. but I'm not sure how clean things are below the surface. Given that, is there any reason to re-do the procedure to pick up the enhancements/cleanup you have done since the first pass? Can the procedure even be back peddled and re-done?
[Verizon Samsung Galaxy S 4] tech_head:
I'm in the same boat and I've used ROM manager to delete some apps.

I also use Xposed and Wanam.

I'd say don't redo it unless you like setting up your phone all over again.

Since you are on the MK2 bootloader, you can actually redo the procedure.
[Verizon Samsung Galaxy S 4] dyrnych:
Same here except that I went MK2->NC2->NC5. My phone is noticeably slower.
[Verizon Samsung Galaxy S 4] fightincowboy:
UGH!

So like an idiot, I took the OTA VRUFNC5 update in a moment of Woo Hoo! But it turned into a D'oh. Will this process still work to downgrade and regain my root?

--Tex
[Verizon Samsung Galaxy S 4] {davros}:
No
[Verizon Samsung Galaxy S 4] DRELUXOID:
What's the current recommended path from MK2 to NC5? Do I need to go to NC2 first or can I go straight to NC5?
[Verizon Samsung Galaxy S 4] mike.s:
... quoted the entire OP for a one line reply?
[Verizon Samsung Galaxy S 4] tech_head:
Hi,

If we flash the S5 SystemUI, how do we go back to the original if we don't like the S5?

Is there an S4 System UI to flash?
[Verizon Samsung Galaxy S 4] Surge1223:
Yeah the procedure can be redone but id say there's no reason to redo-it at this point, I mainly wanted to release the second version to remove the modules from the aroma install; probably saved this thread 5 pages in doing so lol. Other than that that if you use busybox for anything then It might be worth a consideration

Straight to nc5
[Verizon Samsung Galaxy S 4] RemnantKing2:
Is there a specific way to take the OTA if I am already on NC5? I am trying to sell the phone and would rather just keep it on 4.4 instead of downgrading back to MK2 and odining to stock.
[Verizon Samsung Galaxy S 4] lazer9:
[MENTION=4939386]Surge1223[/MENTION] just realized you're correct of course my busybox is screwed up. BusyBox Pro which I have, won't even let me install/update it. Can I just safely dirty flash NC5 v2 overtop the old NC5?
[Verizon Samsung Galaxy S 4] zmedhaug:
Surge you said earlier that the phone stopping on boot was driving you nuts. the issue is csc.apk in system private app. I removed it and my phone is faster and no longer force closes FYI
[Verizon Samsung Galaxy S 4] quarky42:
Just do a factory reset where it wipes the data and cache. Leave it at that. Offer the phone as "stock operating system + root admin access".

Put a note in the listing that says that the phone is an unmodified version of the latest Verizon Samsung Galaxy S4 Android operating system, but it does have root access. If it is returned to full stock without root access, you cannot root the phone again and this may not be possible in the future either.

You can point out that the buyer does not have to use root for anything and can leave it alone. If there are a couple people that don't know what any of that means, there will be other people that do and will pay more.
[Verizon Samsung Galaxy S 4] leandrae400:
so i was on nc2 and followed the procedure perfectly to upgrade to nc5 but its stuck at the samsung s4 splash screen ive went into factory recovery and factory reset and it says im on nc5 but will not go pass the splash screen....
[Verizon Samsung Galaxy S 4] rab5705:
I also did MK2 to NC2 to NC5. Phone is extremely slower than previous rooted build. I have reflashed a few times without a problem, wiped system, cache, data, davlink, and still have problems with slowness and performance.

I even have tried a few times with installing all of the removed apks, toggles, and getting it as close to factory and then removing manually when setup completes. Cannot put my finger on what is causing the performance to suck so bad.
[Verizon Samsung Galaxy S 4] mike.s:
I was able to install a working busybox by opening a shell, mv'ing /system/xbin/busybox to /system/xbin/busybox.old, then running a busybox install app (I used stericson busybox free). After I confirmed it working, I rm'd busybox.old. YMMV.
[Verizon Samsung Galaxy S 4] moonglows:
I originally went MK2 -> NC2 -> NC5 and had the FC issue on reboot. Last night, I went directly from NC5 -> NC5 v2 with a full wipe process (not dirty) and no more FC issue on reboot. :highfive: I can't attest to using dirty flash but full wipe process worked fine.
[Verizon Samsung Galaxy S 4] lazer9:
I did the "dirty" and all seems well :highfive:
[Verizon Samsung Galaxy S 4] tech_head:
I'm bold and daring.

Flashed the Power Menu.. Works Great!

Flashed the S5 SystemUI - Unnerving at first boot. That VZW splash screen stays up too long to be comfortable.

Looks interesting. Fingerprint option is there, so it's not clean :(

Oh well, I'll use it until there is a S4 System UI to flash. Just don't touch the fingerprint option.
[Verizon Samsung Galaxy S 4] blazingwolf:
Sigh! Now Odin doesn't want to flash anything to my device. :(
[Verizon Samsung Galaxy S 4] RyaNov1333:
Same here, I'm having the exact problem as you. Odin won't even recognize my device anymore.
[Verizon Samsung Galaxy S 4] Surge1223:
WiFi is really important to you huh? Here is the bypasslkm thread http://xdaforums.com/showthread.php?t=2578566 and here ive uploaded the binary for you https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm.

To tell you the truth I havent even examined the partitons from VRUFNC2 other than checking if the counter in aboot was incremented. Havent had time and didnt anticipate people having all these questions related to the upgrade/downgrade to/from VRUFNC2! ??

But with the qcom leak, n3 KK leak, our KK leak and having to find/come up with a method to upgrade with root, I havent much time for anything lately ?
[Verizon Samsung Galaxy S 4] nshawn43:
FIXED

I had the same problem last night.. Heres the fix Let the phone turn on so that it says Firmware Upgrade Fail connect to Kies...That is a modified Download mode.. in that mode i was able to reflash the Leak and it worked perfectly any other way caused the phone to FAIL..give that a shot and you should be back up and running on the leak 4.4.2
[Verizon Samsung Galaxy S 4] Surge1223:
What do you mean? can you elaborate? what were you doing that caused this?

What were you doing that caused this?

Did you install the zadig.exe driver? if so then switch usb ports and try.
[Verizon Samsung Galaxy S 4] shindiggity:
Ha ha I know so many posts sorry! I pushed it and when I use terminal I get that error. I'm not supposed to change permissions our anything right
[Verizon Samsung Galaxy S 4] mikeneff2006:
Thanks for the quick reply surge! I'm staying hopeful! I'm sure something came out of this hopefully you and the other devs can sniff it out.
[Verizon Samsung Galaxy S 4] RyaNov1333:
Yes I can. When I enter Download mode and open Odin on my PC, the phone does not come up. I followed everything in the guide, and when it got to the last step, the stock recovery failed at trying to mount something. I then went and followed the "In case the last step above fails" section, and when it got back to the stock recovery and the blue progress bar, it failed with the same error. Now Odin will not recognize my device is connected.
[Verizon Samsung Galaxy S 4] blazingwolf:
Changing USB ports worked. Thank you. Downgrading to MK2 again. Did you see my earlier question in regards to using a stock MK2 cache.img in heimdall?

---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
[Verizon Samsung Galaxy S 4] Surge1223:
Yeah when I downgraded to MK2 I still had the /cache issue so after flashing the mk2 downgrade tar i flashed the mk2 cache.img.ext4 in heimdall. What version of Odin are you using? it might be worthwhile to reflash the mk2 recovery.img and cache.img.ext4 along with the pit when downgrading to see if it fixes this issue.
[Verizon Samsung Galaxy S 4] blazingwolf:
I'm using 3.09.

I'll give the above a shot as well. I'll have to do that later tonight though as I need to go for a bit. Got to take the wife to lunch. :)
[Verizon Samsung Galaxy S 4] shindiggity:
Sorry for multiple posts but is anyone else having trouble with the wifi fix in terminal emulator? I get no signal at home and really need wifi.

Once I get to the second line it says, "unable to chmod bypasslkm: no such file or directory. I feel retarded for because I can't figure this out.
[Verizon Samsung Galaxy S 4] lazer9:
Uhm, I have an issue here. During the first Oden 3 step flash, it ended with 0 succeeded 1 failed and my phone is still stuck in "Downloading.. Do not turn off target" with the progress bar most of the way filled but still solid. I don't know if "WonderShare" on my computer interfered with the process or what as I heard some USB type connect/re-connect beeps and WonderShare tried to load into Manage device...

What to do? I'm still connected via USB to the computer with the phone in above mentioned state. :(

---------- Post added at 03:00 PM ---------- Previous post was at 02:29 PM ----------

Ok got past that problem by disabling wonder share on the PC and forcing phone back into download mode and was able to proceed through ALL odin steps including the final one and I'm booted into the ROM fine. Other than all the force closes, things seem proper so far.

Now my problems. I can't seem to get into STOCK recovery to do the factory reset to get rid of the force closes as when I hold down Vol Up, Power, and home, it flashes back n forth from a battery symbol to SS recovery.

2nd, I of course no longer see V3.71 or ANY SS recovery in the app drawer so I'm confused when it says first uninstall the old SS before installing the AT&T 3.72.

Thanks
[Verizon Samsung Galaxy S 4] loonie01:
I re installed 3.71 then uninstalled the recovery. Then installed 3.72
[Verizon Samsung Galaxy S 4] Surge1223:
I said to uninstall 3.71 then install 3.72 so people would uninstall SS 3.71 in case they had already downladed and installed it prior to that step. But at least people will check what version of SS they are installing, and hopefully install 3.72.

You don't need to do a factory reset via recovery, you can do that in SS 3.72 once you install it. If you want to restore stock recovery you can try flashing the NC2 recovery.img in Odin/Heimdall, though it should have installed by default..strange.
[Verizon Samsung Galaxy S 4] lazer9:
Thanks, lol , I'm out of the "Thanks button" for the day. I did resolve getting into RECOVERY and got that step completed and did the factory reset/data then cache wipes as stated so now on to what you said above. :highfive:

---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------

Thanks, Hrmmm. I did get into factory Recovery via SS boot menu and did the factory/data reset and cache, now I just booted back up and the force closes are still present. :confused:

On to proceed to do what the other user mentioned to get the proper SS and removal of old one.
[Verizon Samsung Galaxy S 4] jwendt79:
Thanks for the work on this. Good to see progress. But I think I'm gonna just wait till a simpler root is achieved. I have no need for safestrap. I just want root for ad blocker and to manually pull files from system to do my own themes.
[Verizon Samsung Galaxy S 4] lazer9:
Rebooted into factory recovery and did factory/data reset then cache twice now and still have the force closes on boot. Any other ideas? :silly:
[Verizon Samsung Galaxy S 4] BoxBeatdown:
Will I have to perform the wifi fix every time I reboot? I installed Xposed and after rebooting had to redo the fix.
[Verizon Samsung Galaxy S 4] eklipz3:
surge when i go into recovery to install the zip files for reboot and ui i get errors saying something is missing it went to fast for me to read, is there a way to odin or some other way? i'm on nc5.
[Verizon Samsung Galaxy S 4] tech_head:
You need to install these files via Safestrap.
[Verizon Samsung Galaxy S 4] eklipz3:
thanks tech_head i will have to wait because i did the full wipe to nc5 because i couldn't get the other way to work.
[Verizon Samsung Galaxy S 4] Surge1223:
so the s5 ui is messing up? I can certainly make a revert zip

Lol yay!
[Verizon Samsung Galaxy S 4] loonie01:
I have noticed some lag with the Google launcher on NC5. Stock launcher is running smooth.
[Verizon Samsung Galaxy S 4] tech_head:
Not really messing up. Just some things are there that force close.

But it's that "doctor it hurts when I do X".

Doctor says "don't do it then". ;)

I'm good. don't spend any cycles. Other folks need more help than I do.
[Verizon Samsung Galaxy S 4] crazychapin:
Can I just flash the update V2 on safetrap, I am already running the nc5 but I'm having some issues and I just want to reinstall
[Verizon Samsung Galaxy S 4] {davros}:
yes
[Verizon Samsung Galaxy S 4] ct_tec313:
I dont if your taking request, but is there a way to get the s5 bowser working on our rom tried everything in power to get it working but it just keep force closing.....btw im noticing that the s4 and s5 are not that much different seeing that people have almost imported the entire s5 over to the s4....keep up the good work bro....
[Verizon Samsung Galaxy S 4] myfishbear:
i just made two update zips for people who have lockscreen issues that dont want to update the boot loader. i didn't figure this fix out myself (i think mike.s did) but i did test it and pack it into a update zip.

system lock screen fix with generic Samsung logo at boot and live wallpapers phase beam and sunbeam

Download here

system lock screen fix with generic Samsung logo at boot live wallpapers phase beam and sunbeam. it also has gs5 quicktoggles and s finder and all of the gs5 sounds and ringtones google maps 8

Download here
[Verizon Samsung Galaxy S 4] V0latyle:
Has anyone else been having issues with lagginess and slow data? Battery life has also been less than impressive.
[Verizon Samsung Galaxy S 4] myfishbear:
just the first day but now mine the fastest its ever been.
[Verizon Samsung Galaxy S 4] V0latyle:
Hmm. I figured my phone would be laggy with power saver turned on but the battery life doesn't suggest any improvement...

Also I have been getting sporadic notifications for security policy updates. Anyone know how to disable this?

Also, [MENTION=4939386]Surge1223[/MENTION], your hosting links are broken. Asks me if I have the Mega app installed and doesn't allow download.
[Verizon Samsung Galaxy S 4] myfishbear:
delete the security policies updater with titanium backup.

use chrome to download from mega. Firefox and ie 11 don't work
[Verizon Samsung Galaxy S 4] mike.s:
Thanks, but it wasn't me - I just reported it as working for me.
[Verizon Samsung Galaxy S 4] V0latyle:
I'm using Chrome beta on Android.