yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Sterben Pistole:
Just put these on my AT&T S4 and I can already see a huge difference in the amount of heat that comes out of my device. These settings plus Coolify will be god like, haha.

[MENTION=5848265]npjohnson[/MENTION] Nice rom, by the way, I've got a couple of Xposed modules you might want to look at regarding Lollipop theming for this rom. Here are there names. MonsterUI, Material Status Bar, and for a lockscreen I would go with AcDisplay. You might also want to slap on HKTheme Manager with the theme I'll be linking for your convenience. https://drive.google.com/file/d/0B5wspZ9xT_gjbW4ycnNJa2pvQTQ/edit?pli=1 Remember to stay safe VZW users :) I'll be heading back to the AT&T S4 section now, lol.
[Verizon Samsung Galaxy S 4] aleggsue:
Am I the only one with service problems? I'll have service and data for about 5 minutes on this ROM, then I'll lose data and service. Then in settings it turns my carrier to "unknown" and I can't get any service at all.

Sent from my Eclipse'd S4
[Verizon Samsung Galaxy S 4] npjohnson:
Flash vzwapnfix.zip. Should solve your problem
[Verizon Samsung Galaxy S 4] aleggsue:
I did that. For some reason, no apn fixes have ever worked with my phone.

Sent from my Eclipse'd S4
[Verizon Samsung Galaxy S 4] past_pluto:
I have service issues too sometimes. Have to toggle airplane mode. Idk why it's an issue but it's not much better on stock NC5. Only difference I notice is stock will go into 1x mode while this ROM doesn't.
[Verizon Samsung Galaxy S 4] Legitsu:
Can I get a hells yes for anybody still rocking kitpop
[Verizon Samsung Galaxy S 4] XxD34THxX:
I went to Stang's ROM because lollipop... I'd jump to get back on this, but I'm stuck on lollipop xD
[Verizon Samsung Galaxy S 4] npjohnson:
No promises here. I may have found something that will make ART play nicely with the kernel in 5.0.x.

Testing it out tomorrow when I have my S4.
[Verizon Samsung Galaxy S 4] shawnsingh:
Is there any compatible recovery for oc1. I have finally succeed a root.
[Verizon Samsung Galaxy S 4] sinner822:
Not if you have an OC1 bootloader.
[Verizon Samsung Galaxy S 4] wavedashdoc:
Still on kitpop 1.3, this is awesome news! If you need a tester I would be able to test over the weekend.
[Verizon Samsung Galaxy S 4] rp1226:
I'm up for some testing as well.
[Verizon Samsung Galaxy S 4] DottinS:
how to install recovery

hi i have a s4 i545 Lollypop 5.0.1 build oc1 rooted via kingroot apk so i try to find a tutorial to install a custom recovery i dont know the way or if its possible to do that.

thanks

Omar
[Verizon Samsung Galaxy S 4] skepticmisfit:
you can't use this ROM with the lollipop firmware. you're stuck with ROMs based on lollipop (and the FlashFire app, no custom recoveries)
[Verizon Samsung Galaxy S 4] XxD34THxX:
The only ROM that seems to work(as far as I know) is Stang's ROM. Not sure if [MENTION=1300608]gigli[/MENTION]e's ROM will work.
[Verizon Samsung Galaxy S 4] skepticmisfit:
there's also muniz_ri's ROMs if you want a simple deodexed ROM

in order to use xposed framework on lollipop you need a deodexed ROM, stock is odexed.
[Verizon Samsung Galaxy S 4] Legitsu:
I flat refuse to use touchwiz ill stick to 4.4.4 for the lifespan of the phone if need be
[Verizon Samsung Galaxy S 4] sinner822:
Been trying to use lolli, But once I get one thing figured out. I find something worse for my usability. Might be quite a while before it is a daily for myself.
[Verizon Samsung Galaxy S 4] patt2k:
sorry for noobish questions here, I gave a s4 long time ago for a friend and want to update from very old hypderdrive to this,NC2 and safestrap 3.75 03 version.

is it safe to flash this rom on NC2? same way just use slot 1 or in stock rom slot?
[Verizon Samsung Galaxy S 4] XxD34THxX:
Yeah, but you will probably have to flash the nc2/5 modules.

Hey, [MENTION=5848265]npjohnson[/MENTION], if and when the next version comes out, will it have the same notification panel as the nexus 6?
[Verizon Samsung Galaxy S 4] skepticmisfit:
I know I'm not npjohnson, but yea that's the aosp notifications panel
[Verizon Samsung Galaxy S 4] XxD34THxX:
Wait, in 1.4? I know the current one is AOSP
[Verizon Samsung Galaxy S 4] mrmondaynight:
Anyone else lose safestrap after flashing hyperdrive?
[Verizon Samsung Galaxy S 4] npjohnson:
Not discussion for this thread. Simply put:

When you wipe /system you lose SS. You have to reinstall it after a new ROM. Some ROMs bake it in. Or, if you use a WiFi Fix (not recommended at all), it flashes SS back in place.
[Verizon Samsung Galaxy S 4] patt2k:
rom works fine no issues at all NC2 , SS 3.75 03! Thank you!

Thanks for your great work! wanted to ask if I flash the NC2 wifi fix,which I am on (flashed for my friend) everything works superb! hot reboot indeed does fix wifi but if I flash the NC2 wifi fix will it not require hot reboot to fix wifi? thank you!
[Verizon Samsung Galaxy S 4] npjohnson:
It still requites the hotboot. I've tried to solve that many ways, nothing sticks.
[Verizon Samsung Galaxy S 4] aleggsue:
Verizon sch-i545?
[Verizon Samsung Galaxy S 4] npjohnson:
Yes. Why do you ask this? You're in the SCH-i545 forum.
[Verizon Samsung Galaxy S 4] skepticmisfit:
i flashed this ROM again (was craving some pure aosp again ugh)

and the gps doesn't work. is there any way to fix it on this ROM or will it require flashing another ROM?
[Verizon Samsung Galaxy S 4] aleggsue:
I'll flash this again when I get back from a trip. Every time I flash this ROM or any AOSP-hybrid ROM, I lose service. I have service at first, then I lose it after and it never comes back. No data, SMS, or anything.

I've tried apn fixes and those don't seem to work either.
[Verizon Samsung Galaxy S 4] skepticmisfit:
ya know

the definition of insanity is doing the same thing over and over again expecting different results ;)
[Verizon Samsung Galaxy S 4] npjohnson:
You can back up your current setup. Then ODIN NC5, root, safestrap, and restore your KitPop backup overtop stock without wiping /system. Only 100% way to fix it.
[Verizon Samsung Galaxy S 4] skepticmisfit:
figured. im upgrading to lollipop again and will impatiently wait for ur themed whatever thing d00d
[Verizon Samsung Galaxy S 4] aleggsue:
Lol. It's just confusing because others have no problems but I do.
[Verizon Samsung Galaxy S 4] XxD34THxX:
Can someone show me the APN fix? I can't find it. Also why the heck is my screen dimming and brightening up... Auto is off.
[Verizon Samsung Galaxy S 4] rrrrrrredbelly:
Not sure if this is the most recent, it's posted towards bottom of OP

http://xdaforums.com/showthread.php?t=2837239
[Verizon Samsung Galaxy S 4] npjohnson:
Reboot after turning auto off
[Verizon Samsung Galaxy S 4] XxD34THxX:
I did... Lets see if it works... Oh, the APN is on a different thread. no wonder. I tried the manual fix, but it didn't let me save it.
[Verizon Samsung Galaxy S 4] patt2k:
That's fine, phone is being used in Europe on Play Poland, Play roams on all 4 carriers so switching between carriers work fine while it didn't on HyperDrive, also performance is sweet. Thanks again! The wifi thing.. well I told him to get it to work. Hopefully one day you can figure it out :)
[Verizon Samsung Galaxy S 4] XxD34THxX:
APN flash fix did not work. It worked for about 5 minutes. Also messed with Gravity box. Still didn't help.

Now it is working. I'll see if it turns off again.
[Verizon Samsung Galaxy S 4] aleggsue:
Let me know if it changes. Mine worked for like five minutes and then it never worked again. Even the gravitybox fix didn't work
[Verizon Samsung Galaxy S 4] XxD34THxX:
Been good for the last few hours. Been calling and texting.. I flashed it again and that did the trick.
[Verizon Samsung Galaxy S 4] aleggsue:
Update me in a few days. Curious how it turns out
[Verizon Samsung Galaxy S 4] magiin:
Can this rom be installed on mdk or is it only made for safestrappers?
[Verizon Samsung Galaxy S 4] skepticmisfit:
you might be able to install it on mdk if you flash a custom kernel (made for kk)
[Verizon Samsung Galaxy S 4] Legitsu:
you forgot to mention that he needs to make double sure he stripps the boot image from the rom or he could end up permanently locking his bootloader [MENTION=5848265]npjohnson[/MENTION] I know you are super swamped any word on a 1.3.1 KK with the wifi work-around we where talking about ?
[Verizon Samsung Galaxy S 4] XxD34THxX:
Data doesn't want to work again... Might switch ROMs to where it works. I can just call and text
[Verizon Samsung Galaxy S 4] sinner822:
In about phone Is there a + in front of your number? If so change your radio from gsm/lte to cdma/lte
[Verizon Samsung Galaxy S 4] npjohnson:
There is no Boot Image in this ROM. It works off whatever you have flashed. That's why NC5/NG6/NK1/NK4 mileage may vary. MDK can flash this, but must also flash a Custom KK Kernel, and their corresponding modules to that kernel. This will, however, update their modem. They can always just roll-back to the MDK modem if they wish.

No, I tried almost all conceivable methods to fix the hot-boot bug. I tried replacing reboot with a script, but, apparently, the reboot option doesn't actually call the reboot command (confusing, right?) So it makes it useless. Plus, that still wouldn't solve a battery pull. I've tried to get a shutdown script to run, but init.d refuses to acknowledge shut down before its too late!

Honestly, no source level fix is gonna be available for this one. What you guys have access to is what I have to work with (in terms of the hot-boot bug), so, if anyone wants this problem solved, experiment with renaming the reboot command ==> reboot1 , then name a text file reboot, and make it dump the WiFi modules (Su -c rmmod dhd.ko), then call the actual reboot command (Su -c reboot1) . That fixes it when you reboot from terminal, but its up to you guys to find a way to re-reroute the power menu to call the actual reboot command. How to do that last part? I don't even know. You see, Pure Nexus doesn't include any Power Menu related edits! And (confusingly), the only way to get it to work is to flash XPosed, but activate no modules! I haven't ever taken the time to truly track down what the cause is there. I don't have the time nowadays to spend hours working on this.

If someone figures it out, PM me, or just make a flashable a.zip and post it up here! I'll merge it if it works, and you allow me to.

Ending note on KK, I will be releasing 1.4 as soon as Dell returns my laptop form warranty. It will ONLY contain vulnerability fixes (stage-fright/bash), and will remove the NK1 modem so that other carrier can use this.

As far as LP goes. Got to the beginning of the optimizing apps screen by using some specially crafted ART libraries that null out the Sammy methods, but leave their placeholders (same way XPosed for TW ART binaries are built). But it hangs at 0/x apps.

Definitely needs some more research... that I don't really have time to do with another semester of college starting up.
[Verizon Samsung Galaxy S 4] XxD34THxX:
Will the data bug be fixed by any chance in v 1.4?

My phone number doesn't have a + in front of it in settings.
[Verizon Samsung Galaxy S 4] sinner822:
Have you tried nk1 modules and nk1 non-hlos
[Verizon Samsung Galaxy S 4] XxD34THxX:
No, just the nc5 modules.
[Verizon Samsung Galaxy S 4] sinner822:
Doesn't this rom ship with nk1?
[Verizon Samsung Galaxy S 4] XxD34THxX:
Which is why I flashed the nc5 stuffs
[Verizon Samsung Galaxy S 4] sinner822:
Then it is your APN. But I am betting you are running gsm/lte also. I just flashed the rom and it defaulted to gsm/lte. I had to play with apns-config also.
[Verizon Samsung Galaxy S 4] XxD34THxX:
I fixed the APN... will check again.
[Verizon Samsung Galaxy S 4] aleggsue:
My number just displays my regular phone number, and I tried changing radio to cdma but that didn't help.
[Verizon Samsung Galaxy S 4] XxD34THxX:
I flashed the APN fix, and I got data, but I maxed out at three bars of 3G, in places where I have had max 4g...
[Verizon Samsung Galaxy S 4] npjohnson:
4G or LTE? Big difference.
[Verizon Samsung Galaxy S 4] aleggsue:
Does the AOSP rule of don't use *228 apply on this rom?
[Verizon Samsung Galaxy S 4] npjohnson:
Yes. It dies. Don't use that code.
[Verizon Samsung Galaxy S 4] XxD34THxX:
LTE. That's what Hyperdrive and Stang's ROM and verizon said(verizons map thing, like I trust that)
[Verizon Samsung Galaxy S 4] npjohnson:
Make sure you are able to currently get LTE on Hyperdrive and or Stock.
[Verizon Samsung Galaxy S 4] XxD34THxX:
I am getting LTE on Hyperdrive AND Stock
[Verizon Samsung Galaxy S 4] aleggsue:
I get LTE on those two and Eclipse.
[Verizon Samsung Galaxy S 4] klabit87:
[MENTION=5848265]npjohnson[/MENTION] this post is very useful.

The user has created a script to check wifi status.

Could be changed a little as well as translated bc of language and linked to the reboot process?

I'm pretty tied up lately but when I get a chance I will get back on this rom and work on this if you don't get to it before me.

Let me know what you think.

Edit : forgot link! Lol

http://xdaforums.com/showthread.php?p=62286521
[Verizon Samsung Galaxy S 4] patt2k:
hey one more question how to fix gps? it does find location but it's super slow and shows looking for GPS constantly.
[Verizon Samsung Galaxy S 4] skepticmisfit:
you'll have to restore back to stock (nc5), turn on gps, then reflash kitpop. LEAVE GPS ON !!!
[Verizon Samsung Galaxy S 4] patt2k:
oh man I am not in Europe anymore :/ it will be tough with this one.. but my friend might help him. So basically flash NC5 turn on GPS for example gmaps: then reboot into safestrap and flash?
[Verizon Samsung Galaxy S 4] skepticmisfit:
yea

to test gps, i actually just use an app called GpsFix on the play store, it's a little easier to determine if gps works through that than with google maps imo
[Verizon Samsung Galaxy S 4] patt2k:
yea i tried it yesterday on that phone and it ran for like 10 minutes and didn't find it,but things like weather etc.. work so if I knew I would reflash it lol. Thanks for the help!
[Verizon Samsung Galaxy S 4] Dr_Wolodya:
Can I FlashFire this rom on OC1 5.0.1?
[Verizon Samsung Galaxy S 4] klabit87:
If your bootloader is OC1 then no you can't run this rom.
[Verizon Samsung Galaxy S 4] Legitsu:
so is this rom officially on hold ?
[Verizon Samsung Galaxy S 4] npjohnson:
Well. No new KitKat Base to build off of, so, no real reason. Can't fix anything else in it's current state. And lollipop is hopeless (ART conflicts/sig checks make it almost impossible.
[Verizon Samsung Galaxy S 4] ImpytheBiscuit:
Still, this is a really good port. I can't believe I missed this one!
[Verizon Samsung Galaxy S 4] Legitsu:
I think the best option for the S4 is going to be

direct porting AOSP or CM11 to the vzw-sammy kernel (take the ASOP base and re-write whatever is necessary to be incompliance with what the vzw-samsung kernel wants)

really tho it shouldn't be terribly difficult if we can run diff's on the code and see what the differences are may even be possible to get 5.1.1 working if samsung ever gets around to releasing OF1/OF2 source

just a matter of time and interest something the S4 is short on given its age,tho if there was a way to create a 'flexible` rom-base FOR vzw-samsung kernels [MENTION=226374]locked[/MENTION]-bootloaders, it may be worth the effort for other devices .. such as the S5/S6
[Verizon Samsung Galaxy S 4] XxD34THxX:
I especially need that sort of thing to run Kali nethunter...
[Verizon Samsung Galaxy S 4] npjohnson:
This has already been tried multiple times.

CM11 relies on kernel functions to do many of the modifications CyanogenMod is known for. And loading in a kernel module /could/ he module can only inject kernel level code, it can't overwrite existing functions. And, say we managed to magically overcome the kernel function problems, the way that ART (AOSP) vs. ART (Samsung) differs means that no amount of rewriting AOSP source will allow us to understand how closed source Samsung ART libraries interacts with other parts of the system.

As for AOSP, we have an AOSP build base booting... that is what this ROM is. Plus, running a diff on a 32 GB source repo containing 145+ git repos? You'd need one HELL of a computer to pull that one off.

Samsung released OC Kernel Source, not sure why you are after OF1 Source, just some patches/root vulnerability patching.

I don't really understand what you mean by a "flexible" rom base. If your referring to on the fly driver selection/etc. (like in Windows), on ARM, that is NEVER gonna happen simply due to how ARM boards work. The S5/S6 share virtually no characteristics, the S6 even has a different brand processor.
[Verizon Samsung Galaxy S 4] Legitsu:
I was talking about building a base rom and supporting code/tools for locked bootloader devices particularly making the kernel dependency stuff as portable as possible , I had a idea for a way to translate art/VM calls via a module a while ago I just need to sit down and decide if its worth the effort to research the differences to make it work ...

the problems with stock kernels can be overcome its just a matter of reverse engineering the vzw-sammy code,which is far easier then then spending months on end attacking a uncrackable bootloader or trying to get kexec to work BLIND
[Verizon Samsung Galaxy S 4] npjohnson:
Oh, you mean ripping kernel functions out into loadable modules? Yeah, that is possible, to an extent, as modules can't void out kernel functions (well, some can, but a limited set of exceptions).

The ART calls don't really rely on the kernel much, it relies more on the app emulation layer, which relies on the ART Libraries. Back in the days of Dalvik, we had a deeper understand of how it worked, as Dalvik was extremely well documented. ART, however? Not at all. Sure we have AOSP source, but Samsung modified it a ton. All we can do is drop the library in IDA (or similar a disassembling tool), and look at vauge ideas of how the functions relate to the AOSP source, but we have no possible way to discern what Samsung's proprietary functions do (the logs do little more than mention them).

Kexec isn't blind at all. We have UART logging and checkpoints via Micro-USB. I know you said it doesn't work on retail VZW S4's in the bootloader thread, but maybe you haven't been wiring it right, cause I can name several people other than myself who have UART working. We got through more stages of kexec, but more time is required, which I (and the others) don't have. Kexec is still just as viable as it ever has been, and debug-able fairly easily.

(This last part isn't intended towards you, just generally speaking)

On a side note: I am sick of hearing this. The bootloader definitely isn't uncrackable, I promise you this. It is possible, and with the amount of known TZ exploits, and how well documented they are, it can be /unlocked/. I've seen these TZ exploits in action on device/contributed to some of them. We got to a point where all that needed to happen was a re-implementation of Dan's TZ exploit's Bounds Bypass, but the team lost interest/fell apart. If you want to take a crack at it, use Dan's exploit (so well documented it needs to explanation) to get to a context where you can make use of the msm8974 TZ exploit (source is LITERALLY on Github, called fuzz-zone, you will need to update the addresses to ones you get from disassembling the S4 TZ Image in IDA or similar) to get TZ shellcode execution, and with TZ shellcode, you can do magical things with QFPROM/Fuse addresses/read outs. If anyone actually shows that they know what they are doing, are knowledgeable enough to do this, and gets parts of this working, I'd be more than glad to talk to them about it.

DISCALIMER: This requires a HIGH level of understanding of how these thing work, if you feel like you might not understand it, you don't. Don't just PM me asking "How I unlklock BL on my VZW S4?" -- if you can't code, and aren't versed in ARM dis-assembly, and QCOM Hardware/Software, you have a very small chance of getting anywhere.
[Verizon Samsung Galaxy S 4] klabit87:
In relation to what you said here [MENTION=5417447]Legitsu[/MENTION] which module needs to be loaded and does it need modload or insmod to be loaded?

I know its the wifi but if i recall its the dhd.ko? is that right?
[Verizon Samsung Galaxy S 4] Legitsu:
yea I was talking about moving/hijacking as much as the kernel level stuff into a module that we can build/load on the stock kernel's

as for the TZ stuff I was under the assumption most of it was patched or simply not viable. last I heard in the bootloader thread you could't get serial debugging to live though the boot process

this is the problem with closed development projects nobody has any frigging clue what was discussed or found or what can and can not be exploited

so when everybody packs there toys and goes home all the progress is lost and devlopment stops dead .
[Verizon Samsung Galaxy S 4] ImpytheBiscuit:
[MENTION=5417447]Legitsu[/MENTION] - ^This times a million. I think it's a shame how closed that project was and for them to just drop and not share their findings is selfish. I get if they no longer have interest in the device, but at least pass the torch on.
[Verizon Samsung Galaxy S 4] Legitsu:
don't get me wrong I am not calling anybody out or blaming anybody

merely disappointed
[Verizon Samsung Galaxy S 4] ImpytheBiscuit:
Oh I know. I'm disappointed too :<
[Verizon Samsung Galaxy S 4] npjohnson:
NOTHING about this project was closed. If any person (that proved they aren't just going to sit around and do nothing) had asked to be in the chat, we would've added them. We did this many times.

See above. In the previous post, I LITERALLY STATED what needed to be done. Torch passed
[Verizon Samsung Galaxy S 4] sob372:
[MENTION=5848265]npjohnson[/MENTION], searched thread and couldn't find much. You recall if anyone reported success with flashing this on mdk w custom kernel?
[Verizon Samsung Galaxy S 4] npjohnson:
Yep. Flash the ROM, then your Custom AOSP 4.4 Kernel of Choice, and you builds modules, shouldn't have any bugs. Have Fun!
[Verizon Samsung Galaxy S 4] sob372:
Mdk modules?
[Verizon Samsung Galaxy S 4] lextacy:
This ROM will not work on a NK1 build ! After installing the rom to a custom rom slot and then flashing the Linux fix module it will not boot. There is a flashy strobe lighty android logo on boot (pretty much boot looping) and it sits there for hours and does a quick vibration every 4 seconds. Will there be an update to fix this issue? I have been trying to get a custom rom to work on my phone from hyperdrive and supernexus and those are only for NC/MTK builds.
[Verizon Samsung Galaxy S 4] klabit87:
Have you tried on stock slot? Rom slots don't work well at all on safestrap
[Verizon Samsung Galaxy S 4] lextacy:
Pretty dangerous proposition there as not suppose to install anything on the unsafe slot. Restores wont even work on the unsafe slot so Id not only lose my stock android, id also have a bricked device due to a failure of backups restoring on the stock rom slot. This was the whole purpose of custom rom slots.
[Verizon Samsung Galaxy S 4] klabit87:
No brick. I have always flashed to stock slot.

If something goes wrong you may have to Odin if it happens to mess up the safestrap installation also.

I have had to Odin back to nc5 a few times myself.
[Verizon Samsung Galaxy S 4] lextacy:
great, the wifi now does not work on the stock rom , how do I fix it back? Apparently the googlie wifi fix destroys your boot.img and make the wifi stop working all together
[Verizon Samsung Galaxy S 4] klabit87:
You need nk1 wifi modules. They should be somewhere around here
[Verizon Samsung Galaxy S 4] lextacy:
i have tried , gapps-kk.zip , and I545_NK1_Modules.zip , were those the right ones?
[Verizon Samsung Galaxy S 4] klabit87:
if you are nk1 then yes nk1 wifi modules in the op should fix it.
[Verizon Samsung Galaxy S 4] lextacy:
well then that didnt work, I did an Odin flash to factory so Im writing this off as incompatible, any ROMS you know of that work on my phone?
[Verizon Samsung Galaxy S 4] klabit87:
Most any in the development section will. The are ports and stangs rom is what I would recommend.

He spends a lot of time on it and make sure it's stable.

Builds it all completely from source too.