yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] ltoney:
could you explain what you mean by "not properly rooted"? I was able to install apps such as Root Explorer and Soft Reboot with zero issues, so i was definitely convinced I had root... (plus RootChecker told me I was rooted) then again, SELinux was giving me problems so idk.

thanks!
[Verizon Samsung Galaxy S 4] Legitsu:
you need to flash supersu from recovery before the first boot of the rom
[Verizon Samsung Galaxy S 4] gmmorrell:
My root was flaky. It looked rooted and had SuperSU installed. Some apps asked for and was granted root. They were then able to carry out whatever root actions they needed to. But root was not perfect. SELinux would not 'stick'. And Safestrap had problems becoming active.

So I went back and reflashed the supersu 2.1 zip, rebooted, updated the binary...and then root worked 100%.
[Verizon Samsung Galaxy S 4] pdwjun:
really useful

useful!!! works perfect with my phone
[Verizon Samsung Galaxy S 4] Dahjah:
First off, good work. :good: This has been my daily driver for a couple months now and it works like a charm.

Quick observation here: When I go to switch the network mode to just 3g, 2g, or LTE in the settings menu, it automatically switches over to GSM. I'd imagine it has to do with this ROM coming over from the folks over at the ATT forums. You can switch using the dialer menu *#*#4636#*#* so it's not a problem, but isn't the first thought of most people. Just wanted to know if anyone else is having this same issue?
[Verizon Samsung Galaxy S 4] Chadwick108:
galaxy gear

anyone able to successfully get galaxy gear to work with this ROM?

Love the ROM just missing my gear :(
[Verizon Samsung Galaxy S 4] klowdhaus:
Everything is working fine for me besides GPS. I didn't see the post regarding that before (I agree it should go in the OP). I didn't try GPS right away and already starting customizing and adding all my apps and such and did a nandroid backup, so I'd like to avoid starting over completely. From what I've read, these are the steps I should take:

1. Reflash the stock NC5 with odin, no wipe

2. Activate GPS and open Maps to "lock" it

3. Reboot into recovery and restore my backup

4. Reflash NC5 modules and SuperSu

I just want to confirm that is correct. Without a wipe, how will this affect /data? Will I lose all my downloaded apps or be left with the stock TW ones?

Thanks in advance! =]
[Verizon Samsung Galaxy S 4] Jay_P11:
Tried this by flashing the SuperSu v2.01 zip on the 4.4.3 version (couldn't find the v.2.1 zip), but SELinux still goes back over to Enforce mode randomly. I want to make sure I get this SELinux thing sorted out before I do the upgrade to 4.4.4.

Useful info:

-Stock build is NK1

-SS v3.75

-Using romslot1 for this

Any ideas, or am I missing something? I don't see why this isn't working because the ROM isn't TW based so it doesn't have KNOX to conflict with SELinux...
[Verizon Samsung Galaxy S 4] DarkSky204:
Thank you for your work. It worked but I have a problem: Random vibrate and i don't see any notifications :( Please help me!
[Verizon Samsung Galaxy S 4] npjohnson:
The NK1 kernel has no way to currently go to permissive. Hard coded into the kernel, and Knox at kernel level prevents changing it.

If you flash back to NC5, you can attain permissive, and then just flash the nk1 modem
[Verizon Samsung Galaxy S 4] Jay_P11:
Thanks, should I flash just the NC5 boot or the whole thing, and if its just the boot, would that mess with SS?

EDIT: Flashed NC5 boot, everything's working fine now
[Verizon Samsung Galaxy S 4] RickGrimes411:
I get it too. No clue what is causing it. My best guess is a bug report of some kind but I can't find any log showing what would be doing it.
[Verizon Samsung Galaxy S 4] npjohnson:
The NC5 Kernel will work just fine for Permissive. But then you cannot go to any NK1 based ROMs or the Stock NK1 ROM without relishing the NK1 kernel through ODIN (but there aren't any NK1 ROMs, so I wouldn't fret...).

Nope. Shouldn't screw with SS.

---------- Post added at 01:39 AM ---------- Previous post was at 12:55 AM ----------

I think that it is the Google Now persistent Weather notification in the NC, as I have noticed that If I disable notifications from Google Now, the random vibrations stop entirely.

I think the reason this wasn't realized before is that on normal ROMs that shouldn't register as a notification.
[Verizon Samsung Galaxy S 4] JackWR:
It's not work :(
[Verizon Samsung Galaxy S 4] npjohnson:
Well... no need to contemplate now, cause as of the 23rd, Joe-Tech fixed it in the Super Nexus ROM :)
[Verizon Samsung Galaxy S 4] 06sharpshot:
I use the app GPS status when my GPS goes kind of haywire. Granted I am no longer on this ROM but that was how I solved it when I was.

---------- Post added at 11:57 PM ---------- Previous post was at 11:55 PM ----------

The random vibrates were recently fixed in the super nexus ROM. You may try asking Joe-Tech what he did to solve the issue or flash that ROM instead.
[Verizon Samsung Galaxy S 4] DarkSky204:
Can you show me link of that rom. and how to flash this? Thank you so much!
[Verizon Samsung Galaxy S 4] RickGrimes411:
http://xdaforums.com/galaxy-s4-att/development/rom-google-edition-s4-t2837239
[Verizon Samsung Galaxy S 4] LGtMgG2t:
I was thinking I read somewhere that disabling Google Now would stop the random vibrating. I always have it disabled so I'm not sure.
[Verizon Samsung Galaxy S 4] 06sharpshot:
Have you or anyone else successfully gotten the latest update of that rom working on Verizon? I was using it as my DD on an older version but unfortunately I can't get SMS and data to work at the same time on it any more. I've tried the APN zip, the method from the OP here, and messing with APN and secret menu settings for the radio band and stuff. Right now I had to flash back to Eclipse until I can get that one working. Anyone else have ideas on how to port it to Verizon?
[Verizon Samsung Galaxy S 4] sinner822:
Works fine. Only selinux does not work for me.
[Verizon Samsung Galaxy S 4] RickGrimes411:
Works fine for me too. This time I did mine a bit different. I pulled the apns and buildprop from this ROM.

https://www.androidfilehost.com/?fid=23501681358552862

Replaced them in supernexus using 7zip then flashed. Could try that.

Selinux works fine for me too. Still getting the random vibrations tho...just not as often
[Verizon Samsung Galaxy S 4] sinner822:
No selinux here.. GPS hits 13 sats in 3 seconds in a brick house. WiFi LTE phone all A OK. I am on MK2 BL maybe my prob with selinux. No biggie. Not really a must fix for me. I will get to it eventually. All good.
[Verizon Samsung Galaxy S 4] 06sharpshot:
Which baseband version are you on? I'm still on NC5.
[Verizon Samsung Galaxy S 4] RickGrimes411:
I'm on nc5 as well
[Verizon Samsung Galaxy S 4] pfizzle:
You only had to install the modules and do a soft reboot thru gravity box or xposed to get the WiFi!

Try restoring to a backup of your old rom again, one where you had working cell service, then just wipe system cache n data and flash this rom, modules and SuperSU.. It should work
[Verizon Samsung Galaxy S 4] JeeperDon:
I'm ok up to the 4.4.3 part, and WiFi works now for me (with the 'modules' zip added to the SS install). Once I get 4.4.3 all set up (Google doing it's thing now) with root and SuperSU and Root Explorer and TiBu, I'm going to look into freezing the OTA function. Then I'll be on 4.4.3 and not have the WiFi problem.

By the way, I think there are still a lot of ATT references still in there that might be cleaned up as this progresses, like the Bluetooth said it's a 9505, not a i545.
[Verizon Samsung Galaxy S 4] Spike96:
I actually did decide to flash this, and it looks great. Insanely fluid.

I got cell phone data to work, have root, but no matter how hard I try I cannot get wifi.

The first time I flashed this I followed step by step, but I mistakenly flashed the NC5 modem rather than the wifi module when on 4.4.3. Obviously, wifi gave the message: "Turning wifi on" and nothing more. I found out that I flashed the modem instead of the module so I went on to 4.4.4 thinking I could just flash the module and wifi would work. Nope. So I back tracked all the way to my backup.

I flashed my backup (Hyperdrive 16.1) and then flashed 4.3 again, but this time I correctly flashed the wifi module after. Didn't work. I soft rebooted, still nothing. (I used the google play app: Soft reboot (Root))

I just keep getting the message "Turning wifi on".

jfltevzw-NC5-modules.zip by Surge is what I flashed after the rom flash.

Any suggestions? I'd really love to get this rom to work, it is the smoothest I have had my phone running since I got it.
[Verizon Samsung Galaxy S 4] michaelg117:
Out of no where I cannot access any mobile networks. LTE data is fully working. But all my text fail to send and my calls return with a popup saying "mobile network not available"

Any ideas??

[
[Verizon Samsung Galaxy S 4] bryannn29:
Same thing happened to me, but restarting and flashing the WiFi modules instead of the modem fixed it for me. I also did a full wipe before I flashed (excluding wiping the external sd card of course). So my steps were like this:

-In Safestrap, went to Wipe>Advanced Wipe and checked everything except the micro sd card

-Flashed 4.4.3

-Flashed the WiFi modules

-Flashed UPDATE-SuperSU-v2.01.zip (this gives you root, so going to towelroot.com is not needed)

-Reboot

This happened to me as well. I ended up fixing it by downloading Gravity Box and going to Statusbar Tweaks>QuickSettings management. Once there, I added the Network Mode tile. I then went into Tile specific settings>Network mode tile settings and I checked both "Allow LTE network mode" and "Use CDMA network modes."

Edit: I don't think you NEED to add the Network Mode tile to the Quick Settings. I removed the tile and my mobile data still works.
[Verizon Samsung Galaxy S 4] michaelg117:
Perfect!

Much thanks sir. I was afraid I'd have to resort to a different Rom ?
[Verizon Samsung Galaxy S 4] Blue:
I did select LTE (recommended) and I still had no service even after a reboot. The first time I ever tried to flash this my data and service worked but then after a reboot it did not and now even when I start from scratch (fresh Nc5) it still won't work for what ever reason.
[Verizon Samsung Galaxy S 4] michaelg117:
Read the couple of post above this one and you should be set.
[Verizon Samsung Galaxy S 4] JeeperDon:
What this project needs is a dedicated VZW version of the ROM package. We are using the ATT package and altering only what is enough to make it work on VZW, and we are each doing that separately. The base ATT ROM, the vzw modem, the vzw modules, and other minor alterations needed for VZW (small text things like blue tooth SSID and such), and the 4.4.4 update could all be packaged as the one VZW 4.4.4 ROM load to SS install.

I looked over the 4.4.3 and 4.4.4 zip file internals and a lot of it looks like simple file replacing we are doing for the apns-conf file, but am not sure how to handle the 4.4.4 'patch' side of it. I'd be happy to do the work, I don't have the skills.
[Verizon Samsung Galaxy S 4] Spike96:
Should wifi successfully turn on after first boot? Or do you have to soft reboot first?

EDIT: I didn't do an advanced wipe, just a standard wipe but I followed everything else you said. Still stuck at "Turning wifi on"

Tell me what you did after you got 4.4.3 to boot... Did you soft reboot? If so what app did you use?

I appreciate the help!
[Verizon Samsung Galaxy S 4] JeeperDon:
I added the Modem to the install, ROM + modules + modem + SuperSU, and WiFi started fine on 4.4.3.
[Verizon Samsung Galaxy S 4] bryannn29:
I believe that the WiFi worked from the first boot of the ROM. But after I booted up I installed SElinux mode changer from the playstore. I then installed the Xposed Installer for the soft reboot. If all else fails I would try to do the advanced wipe before installing the ROM but I'm all out of ideas after that one.
[Verizon Samsung Galaxy S 4] ahmed.zubair:
No need to update your bootloader .. Just update to kitkat nc5/nc2 and then follow the procedure. :o
[Verizon Samsung Galaxy S 4] Spike96:
Unfortunately, none of this is working. I'll go back to square one if I have a little time today. I'll probably start (as the OP suggested) with stock NC5.

JeeperDon is also right, all of these zips: the rom, module, modem, as well as super root can be packaged as one zip. It's not much work to flash multiple zips, but I may not be having this wifi problem if they were packaged together as one universal zip for everybody on safestrap. It makes the rom easier to flash and less prone to errors.

Either way, great job, [MENTION=5942286]RickGrimes411[/MENTION] ! Finally, a clean AOSP rom for safestrap. Thank you.
[Verizon Samsung Galaxy S 4] 15goudreau:
Hey guys,

Trying to get this working properly on my friends phone. I can flash up 4.4.2 fine, and wifi works on the first bootup. Then when I am in my first bootup and rerunning root, I can't get recovery to work. It tries to execute the reboot to recovery and nothing happens. It has root control too. When I reboot wifi no longer works, just permanent off position. Also, when I reboot and I'm given the option to get SS, if I select SS, I get a black screen that needs a battery pull, and then if I try to boot back up into the ROM, I get the same black screen and need to do a factory reset with the actual recovery. Thoughts on why SS won't work after I flash the ROM? Am I missing something?
[Verizon Samsung Galaxy S 4] Spike96:
Finally I've gotten wifi! Thanks to everyone who helped! The problem was I couldn't go directly from Hyperdrive 16.1 (which is NC5 btw) right to 4.4.3. I had to go to the stock NC5 and then after I flashed 4.4.3 I had wifi! So [MENTION=5942286]RickGrimes411[/MENTION] , maybe you should delete the part that you can skip step 1 if you are on any other NC5 rom. Apparently Eclipse worked, but Hyperdrive didn't.

Safestrap recovery issue: Well all of your issues with the black screen and trying to boot back to the rom are because you simply don't have safestrap recovery installed. You did when you installed the rom, but it must've uninstalled after you booted.

What version of safestrap are you using? 3.72? 3.75? Maybe an even older version?

After you successfully booted into 4.4.2, did you have the safestrap app installed? If not this issue is an easy fix, install it and click install recovery.

If you did, click install recovery anyway.

That should do it.

Wifi issue: You have to soft reboot to get wifi to work. Wifi will stay until the next full reboot. Then soft reboot again.
[Verizon Samsung Galaxy S 4] emarietta:
I set up the ROM and everything worked fine but now SMS and calls won't work. I did the right APN in messaging and APN.config file. Do I have to restart or is there another fix
[Verizon Samsung Galaxy S 4] Spike96:
I'll refer you to post #65

http://xdaforums.com/showpost.php?p=54229876&postcount=65
[Verizon Samsung Galaxy S 4] RickGrimes411:
Thanks for the info. That's good to know. I removed that part entirely.

Sent from S4 i545 NC5 GPE 4.4.4
[Verizon Samsung Galaxy S 4] bryannn29:
Awesome, glad you got it working.
[Verizon Samsung Galaxy S 4] Legitsu:
kitpop seems to be the most relieable of the s4 SS ASOP roms its got it issues but its very usable as a daily
[Verizon Samsung Galaxy S 4] npjohnson:
I was just checking this thread and reading about the GPS issues people were having and their specific situations. Good to hear you are enjoying it (;
[Verizon Samsung Galaxy S 4] Legitsu:
gps seems to work fine here

my only real annoyance is MTP Not working its a giant pain to pull my phone out of the case and remove the back cover to get at the micro-sd
[Verizon Samsung Galaxy S 4] npjohnson:
Good news! I delayed the release of v1.3 b/c I stumbled onto a way to replace MTP with UMS, allowing us to plug the phone in and copy files to the extSDCard. Best part is that you can just run a symlink to /sdcard on your extSD , only bug is that when you write to internal storage via the symlink, you first have copy the file, then unmount the SD via the UMS prompt in the NC Center, then the file will copy in the background.
[Verizon Samsung Galaxy S 4] Legitsu:
but that still means no ADB which isn't really a issue for anybody other then me

I don't know why you would want to symlink /sdcard thats a bad idea in general for the reasons you listed so long as you can plugnplay to transfer to the microsd thats good enough
[Verizon Samsung Galaxy S 4] npjohnson:
ADB? Adb works just fine here.

Do you mean ADB during UMS? I swear I was using it earlier today, but could be wrong, and will check tommorow.

Due to the lack of internal storage write access, that's why the /sdcard symlink. For me, I never really store things long term on my extSD, only on my internal storage, so that's why I use that. I wouldn't ever ship something like that in a production build. But FYI the limbo time that it spends after unmounting doesn't appear to be harmful whatsoever, according to the logs, it is just as if it were waiting for the device to come online before transferring.
[Verizon Samsung Galaxy S 4] Legitsu:
the only time the limbo would be a issue is if something needed to write to iSD still menu prompts and stuff are a annoyance

and yea I was talking about ADB Whilst MTP I use it for "experimenting" sometimes
[Verizon Samsung Galaxy S 4] obey.aw:
Would the method used for this work with PAC ROM? Ripping out the build.prop then flashing APNs? (Sinners zip) I would love to go back to my PAC ROM days

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] klabit87:
I believe pac rom wouldn't work without a custom kernel. I don't know if anybody had tried or both though.
[Verizon Samsung Galaxy S 4] obey.aw:
I might try this method with AOKP since they use very similar kernels. There is one nightly I lost the link too that flashes on safestrap but no service no matter what (kernel) and no WiFi but it flashes.

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] RickGrimes411:
Never heard of AOKP working on an s4 with a locked boot loader.
[Verizon Samsung Galaxy S 4] obey.aw:
I can confirm from hand testing that it does flash. I wouldn't lie about that. Its on my SD card now and the ROM is very buggy and I can't get screenshots unfortunately since the ROM says I have "no SD card".

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] RickGrimes411:
Interesting. Well give it a shot I suppose. Good luck:D:thumbup:
[Verizon Samsung Galaxy S 4] AustinoLambino:
GPE newbie here

Im just curious. Can someone inform me of the benefits of having a GPE rom installed? Anything special?
[Verizon Samsung Galaxy S 4] ATGkompressor:
Popular opinion holds that Touchwiz is "ugly", and that it lags. Most of us here on XDA want to do what we want to do to our devices. Not what Samsung or HTC or even Verizon wants to do. As far as modding, rooting, etc. is concerned. While many will argue that Touchwiz has a bit more streamlined ui that contours nicely with the everyday end-user, that OEM interface may slow down a user that demands performance and great battery life. It's all in what you are looking for, what u expect and how you use your device.

If I were you, I would stick to touchwiz based roms. Mainly because these AOSP roms slightly vary from TW roms at the kernel level. Things like Wi-Fi, nfc, camera...usually don't work due to this imbalance. Which means alot more buggy, and greater odds that your modding experience will end quickly and on bad terms.
[Verizon Samsung Galaxy S 4] LGtMgG2t:
What ATGkompressor says to be exact. :)
[Verizon Samsung Galaxy S 4] {davros}:
You may think you own your device, but in all reality you dont
[Verizon Samsung Galaxy S 4] obey.aw:
I will report back any findings ?

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] obey.aw:
Rick here is the link to the ROM

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

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] RickGrimes411:
Sounds like the WiFi and data problem is kernel related. If that is true then swapping the apn file wouldn't do any good. I might try that kitpop one soon here. Itching for some flashing.

BTW. Post 800. When I made the op never thought it would get this many. Crazy stuff.
[Verizon Samsung Galaxy S 4] obey.aw:
Oh sorry for the missunderstanding But I meant pull the files from the AOKP (build.prop ect) and put them in the super nexus zip. This may be a shot in the dark here but you miss all the shots you don't take ?. And I have not tested this of yet because I have no access to a computer atm

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] npjohnson:
To point it out, just replacing files in super nexus won't make the ROM AOKP, AOKP is based on a much different source tree.
[Verizon Samsung Galaxy S 4] RickGrimes411:
I installed kitpop last night. Had a little trouble getting data working but other than that everything has been smooth. Nice to have a ROM like this for VZW and not have to mess with replacing files on the AT&T ones.
[Verizon Samsung Galaxy S 4] obey.aw:
I tested it and I still had no visible service ?

Sent from a Google driven BEAST
[Verizon Samsung Galaxy S 4] RickGrimes411:
Oh well. Always fun to try things
[Verizon Samsung Galaxy S 4] technique00:
I'm failing to flash both of the modified Super-Nexus or GPE_4.4.4 zips in Safestrap. I'm am not getting the build.prop error spoken of around #653. My Selinux is set to permissive for what that's worth. Perhaps there was there a specific way I should have gone about replacing the build.prop and apns-conf files? I extracted original AT&T archive, replaced said files, then created a new .zip archive and transferred to phone's exSd card. My Safestrap log below. Thanks a lot

Removing all files under '/system'

Updating partition details...

Installing 'external_Sd/Android/ROM/Super-Nesus_020525.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found.

Error flashing zip '/external......515.zip'
[Verizon Samsung Galaxy S 4] RickGrimes411:
Don't extract the zip. Open the zip file with 7zip. This allows you to modify the zip without extracting.

7. Right click and choose to open archive with 7-zip

8. Once open in 7-zip, open system folder. Open etc folder. Delete apns-conf.xml.

9. Back up one directory so the system folder is open again in 7-zip. Drag and drop the etc folder(from step 6 which contains the apns-conf from factory) from your desktop into the system folder in 7-zip. This will add the apns-conf to the etc folder in the flashable zip. See this for more details about altering flashable zip files.

Do the same for buildprop
[Verizon Samsung Galaxy S 4] technique00:
That did it! Thank you sir!

Judging by the quickness and completeness of your response i take it nobody's ever asked that before ;)
[Verizon Samsung Galaxy S 4] RickGrimes411:
The first thing I originally tried was extracting, replacing and re-zipping the files. Found out that doesn't work pretty quickly. Figured replacing the files without extracting was easier than making it a flashable file again. So your description sounded exactly like that scenario. Glad its working for ya.
[Verizon Samsung Galaxy S 4] technique00:
Question: If coming from an NK1 build, is it actually necessary to downgrade to NC5 before flashing, or can you go strait from NK1? Im originally coming from an NK1, and I ask because initially not wanting to divert in any way from the instructions, I had downgraded to NC5 before flashing the modified super-nexus, modules, and update-supersu. After second boot and a hotboot, wifi still wound't work and having spend 12+ hours and it being midnight I decided to backup in Safestrap and restore my previous rooted Nk1 until i can figure out what the deal. This morning I discovered my NK1 was bootlooping. Tried flashing the NK1 modules to fix but it did not. Then, impatient, and without thinking to downgrade back to NC5, I did a full wipe, flashed moded super-nexus, modules, and update supersu and now wifi works on first boot. Any thoughts here?