yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] rp1226:
You know, I still have high hopes on getting this phone unlocked to some degree. Looks like I'm locked into this phone until December this year. So any support we have, I am grateful for.

This ROM still is the best out there. So far no major issues and the phone works great and is as up to date as possible.

Can you give us any tips for Kexec? Modules and such? Anything we load up for any improvement?

Thanks!
[Verizon Samsung Galaxy S 4] wavedashdoc:
Just saw this! [MENTION=5848265]npjohnson[/MENTION]

http://www.droid-life.com/2015/04/28/verizons-galaxy-s4-gets-lollipop-this-week/
[Verizon Samsung Galaxy S 4] rp1226:
Now we just need the image.
[Verizon Samsung Galaxy S 4] ravenmk:
Hey! I got the rom working on my device but Data and Wifi do not work. I flashed the Gogolie Wifi fix, but it didn't work. I am using everything that is required, please help. And I think the data wasn't working because of the APN was not set up.
[Verizon Samsung Galaxy S 4] npjohnson:
Woohoo! Good to hear. I have KitPop v2.0 ready, but I don't know if it will boot with the new LP kernel (The ATT guys have had trouble doing so thus far...), and if the kernel doesn't get along with the ROM, then... Its a sad day.

If you want to try to debug kexec, I'll walk you through some of it, but it isn't simple and requires an understanding of a lot of different stuff. Kexec doesn't work yet though, just hangs at the kernel execution.

As for loading something up to improve... Not really. You can look for Surges overclock modules in the Boot loader thread. I don't over clock my devices though, and wouldn't recommend it, as it is harsh on the device.
[Verizon Samsung Galaxy S 4] npjohnson:
Well. If you used the WiFi fix, I reccomend Odin to stock and start again. This time avoid the WiFi fix. Then use the change APN app from the play store to change to "VZW Internet - LTE", then reboot.

I am assuming you tried a hot reboot to fix WiFi/data issues?
[Verizon Samsung Galaxy S 4] wavedashdoc:
Awesome! So you are planning on releasing KitPop 2.0 to tie us over, right? :P Well honestly I'm enjoying a themed kitkat rather than jumping ship to lollipop, seems that there are just too many bugs still and not that many benefits. I'm thinking Google is going to release one hell of a patch (or at least a # jump to 5.2) at I/0 this year. Awesome work as always [MENTION=5848265]npjohnson[/MENTION]
[Verizon Samsung Galaxy S 4] ravenmk:
Thanks! Yes I did try hot reboot. What is the package name of the Change APN app? There are tons of apps I found.
[Verizon Samsung Galaxy S 4] npjohnson:
2.0 is LP based :p, 1.4 will still be KK, and likely released alongside 2.0.

"APN Settings" The Icon is a green square with arrows going back and forth.
[Verizon Samsung Galaxy S 4] wavedashdoc:
Haha that makes sense, and even more exciting that 2.0 is basically ready if the new kernel boots with it! Has anyone gotten the OTA yet? (who's still on stock 4.4.2 Touchwiz that is lol)
[Verizon Samsung Galaxy S 4] ravenmk:
Is this it?

BTW I was able to get WiFi by flashing Gogolies WiFi NK1 fix! :)
[Verizon Samsung Galaxy S 4] shawnsingh:
Guys the update is out for Verizon 1545 s4. Hopefully good news. I also heard rumors not sure if true but people might be able to unlock the boot loader who knows.
[Verizon Samsung Galaxy S 4] npjohnson:
Yes, for reference, when dealing with this ROM, avoid Gogolies WiFi fix's, they leave a setup that is hard to support/deal with. Just flash the modules next time.
[Verizon Samsung Galaxy S 4] npjohnson:
Correction. Verizon Announced it, not a single user has gotten the OTA yet, and I'll only believe that someone actually got it when I see an OTA Update.zip

And there is a group working on the bootloader, I am in it :p just research at this point though.
[Verizon Samsung Galaxy S 4] shawnsingh:
OK lol but people have been saying on Google when you search lollipop for s4 it shows 10 mins ago yeah I revived update so......
[Verizon Samsung Galaxy S 4] npjohnson:
You did? Would you be willing to pull images from it so we can put a TAR together? I can instruct you how to do so later this week.
[Verizon Samsung Galaxy S 4] shawnsingh:
Sorry lol I haven't received it yet but few have I wonder when I will.
[Verizon Samsung Galaxy S 4] RickGrimes411:
Wonder if I could Odin to stock and pull it using kies
[Verizon Samsung Galaxy S 4] RickGrimes411:
No dice in Kias. :(
[Verizon Samsung Galaxy S 4] shawnsingh:
Now I am able to update but I am gonna wait till 4 pm. At work
[Verizon Samsung Galaxy S 4] shawnsingh:
I will also wait to make the tar just pm me the instructions and i will get working at it lol.
[Verizon Samsung Galaxy S 4] RickGrimes411:
Mine said there was a 2 part update for 5.0. I took the ota update just now, it installed and everything but I'm still on 4.4.2. Said the 2nd part was coming soon.
[Verizon Samsung Galaxy S 4] skepticmisfit:
so this is part 1 of the update, to nk4. I didn't capture this, I forgot who did https://drive.google.com/file/d/0B6jLdJmYZakubk5tcHhkcVRVLVE/view
[Verizon Samsung Galaxy S 4] shawnsingh:
Mine updates to the nk4 but fails to update to 5.0.1.

I think due to the fact of having root.

I was wondering if it is safe to Odin nk1 stock tar on nk4.
[Verizon Samsung Galaxy S 4] npjohnson:
That's how most Sammy Lollipop updates are going... Not sure why.

So, we can use ODIN to dump you partition map. That's always an option. Have you ever seen the "dump" check box in Odin? That's what it is for.
[Verizon Samsung Galaxy S 4] npjohnson:
Likely yes. It can't hurt either way, it will failed with the error FUSED:BINARY if the rollback counter was set... But for the ATT people, it wasn't set, so I assume for us it won't be either.
[Verizon Samsung Galaxy S 4] RickGrimes411:
Think I'm downloading the actual 0c1 update now
[Verizon Samsung Galaxy S 4] shawnsingh:
So I flash nk1 because the root is still active so I will find out soon or if someone has the nk4 firmware then that will be good to.
[Verizon Samsung Galaxy S 4] N4styN1ghtm4r3:
I really need the second part of this update, as I have no Sim card to use it a and it isn't available on kies. I used the first part successfully with stock recovery, but I need part 2 to complete it.

Do you think you can post where you found this?
[Verizon Samsung Galaxy S 4] shawnsingh:
I would you have to restart phone and then wipe cache then try 2nd part via setting again it should work.
[Verizon Samsung Galaxy S 4] N4styN1ghtm4r3:
I'll try it, but the important thing here is that I have no Sim card, so it isn't recognized by Verizon for an Ota update (from my understanding). I was trying everything before I found the update.zip above and thought, why not? Luckily, it was successful, but software update is still saying it is temporarily unavailable.
[Verizon Samsung Galaxy S 4] shawnsingh:
I didn't have a Sim card in their and it updated
[Verizon Samsung Galaxy S 4] Legitsu:
most likely Samsung trying to be clever and failing miserably

how ever it may open a exploit path for us
[Verizon Samsung Galaxy S 4] N4styN1ghtm4r3:
Hmmm, odd.

I can't seem to get it to work for me. I've done factory reset, multiple cache clears, and other random shot-in-the-dark fixes, it remains temporarily unavailable for me.

Just my luck...
[Verizon Samsung Galaxy S 4] shawnsingh:
Lol.
[Verizon Samsung Galaxy S 4] Shagen34:
data problems

Can't seem to figure out what is wrong with my data. I flashed all the required items for my device from the original post. LTE wasn't working so I flashed the vzw-APN fix and now the internet works but I can't call or text at all. I used the Change APN app from the Play Store to get the LTE working. I read the post about the GravityBox app but I can't seem to get that to work on my phone either. I have already wiped the custom ROM and re-flashed everything. I originally had it all working, texting and all, but when I flashed the softbuttons removal mod that was posted in the original post I stopped receiving texts.

---------- Post added at 02:40 AM ---------- Previous post was at 02:34 AM ----------

Note I re-flashed everything AFTER discovering that texting stopped working from the softbutton mod. But even after that the texting/calling won't work.
[Verizon Samsung Galaxy S 4] npjohnson:
Odin to stock and try one more time. Works 95% of the time. :p good luck.
[Verizon Samsung Galaxy S 4] shawnsingh:
I got lollipop running smoothly. It is nice
[Verizon Samsung Galaxy S 4] Tech 4 9:
Still rooted?
[Verizon Samsung Galaxy S 4] N4styN1ghtm4r3:
So, is anybody willing to get the second part of the update into an update.zip? It would be greatly appreciated!!

---------- Post added at 08:41 AM ---------- Previous post was at 08:35 AM ----------

Sorry, didn't mean to quote you, and I can't edit on mobile.
[Verizon Samsung Galaxy S 4] shawnsingh:
No it wouldn't get updated if I still had root. I was on nk4 then I installed stock nk1 and tried again then it was no errors. The reason 5.0 wouldn't get flashed was because of the status of the phone was on custom not offical

---------- Post added at 12:55 PM ---------- Previous post was at 12:54 PM ----------

I am also sure some one will proably make a Cf auto root like the other model.
[Verizon Samsung Galaxy S 4] Legitsu:
all we are waiting for is a factory restore .tar

from that we can build a .zip to be flashed in safestrap

it may require some kernel swapping trickory like the s5

KEEP YOUR PANTS ON PEOPLE IT HASN'T EVEN OTA'D everware yet ffs jesus the entitlement on xda is unreal
[Verizon Samsung Galaxy S 4] Tech 4 9:
Could you please possibly expand on messing w/the partition map?...or hit me either link perhaps? I feel it's stuff I should know...I'm entitled. :D
[Verizon Samsung Galaxy S 4] Shagen34:
Did that, it worked, texting but not MMS. So i downloaded the Change APN app and I received the MMS message but then I was unable to send/receive text and calls again.
[Verizon Samsung Galaxy S 4] sinner822:
Your not sh itin.
[Verizon Samsung Galaxy S 4] Legitsu:
as [MENTION=5848265]npjohnson[/MENTION] said if it comes down to it we can dump the partitions via odin and build from there

a odin flash-able .zip is simply a deflated tarball of the partitions + the PIT file with some header magic
[Verizon Samsung Galaxy S 4] sinner822:
Updated kernel only to NK4 on MK2 bootloader. GPE/Super Nexus is all good except set SeLinux to permissive (original issues still exist). Same as NK1.

OC1 modem works with NK1 modules.

Personally. The OC1 modem gets the best signal for me.
[Verizon Samsung Galaxy S 4] Legitsu:
warning do not take the ota the OC1 Update increases the qfuse counter meaning you will not beable to root the phone because you can no longer downgrade to nc5!!!!!!!!

if you already did so then you are screwed and have permanently lost root

instead use the instructions here

http://xdaforums.com/galaxy-s4-verizon/general/how-to-update-to-i545oc1-5-0-1-keeproot-t3096558
[Verizon Samsung Galaxy S 4] sinner822:
Has anyone flashed the OC1 Kernel yet? I'm curious to see if it works on GPE/Nexus 4.4.4. I will try it after work. But like I said. "I'm curious".
[Verizon Samsung Galaxy S 4] Legitsu:
won't work the 5.0 kernel and the 4.4.4 kernel are very different

odds are that anything 5.0 based is gonna require a new installer routine based on flash-fire
[Verizon Samsung Galaxy S 4] npjohnson:
Sort of... the zip I have put together check to see if SS is present, then (if it is present), removes SS as it installs the ROM. That way the ROM will boot, and it can ALSO be flashed with FlashFire.

Also... an Update for all users of KitPop:

I have finally taken the plunged and updated my system using Muniz_ri's OC1 stock rooted ROM, and have begun work on a 5.0.x GPE ROM. After some work with Joe-Tech, after flashing it, it boots, and gets to the setup screen, but when ANY user interaction is made, the ROM will crash and reboot.

I am working on this, and have some ideas as to how to fix the the issues present, but would like to point out that I have already begun to get PM's asking me when KitPop v2.0 (5.0.x) will be released... and the answer is that it isn't ready yet. Due to Safestrap not working on 5.0.x (Surge said he may be working on that... FYI.), I have to use FlashFire to test ROM's, and that means if it results in a boot loop, I have to ODIN to stock and try again. This makes testing stuff WAY more tedious and painful.

Though I'd give an update.
[Verizon Samsung Galaxy S 4] Legitsu:
yea not to keen on fire-flash sounds like a pain in the ass

does safestrap work if you do some kernel swapping with odin ?

this is what we do on the s5 is flash using the stock rom slot and then reboot to download and flash the 5.0.1 kernel

anytime you need to get back into safestrap you flash the older kernel ;rinse repeat and superSU needs to have SU during boot enabled ...

its a still a pain in the ass but less of one then needing to go all the way back to stock

and in this case I suspect you may need to flash the modules via odin as well ./unsure ...
[Verizon Samsung Galaxy S 4] npjohnson:
Yes it does. I'd recommend using the NK1 kernel to do so. It works ok. Surge was talking about getting SS up and working on 5.0 though, so we will see.

I'd usually jump all over helping out with stuff like that, but me schedule is not forgiving right now :p
[Verizon Samsung Galaxy S 4] Legitsu:
I don't see why [MENTION=631273]Chainfire[/MENTION] could't make flash-fire install some sorta of twrp,cwm loader ala safe-strap it would make it exponentially more useful especially if something dies midway
[Verizon Samsung Galaxy S 4] npjohnson:
Well, flashfire (from my understanding) just takes the system and kills ALL possible processes, then unmounts all partitions, pushes what it needs into memory and executes the given instructions... so I don't see how that could be integrated at a lower level, because it requires a working (booting) system partition.
[Verizon Samsung Galaxy S 4] sinner822:
I have found Flashfire fairly user friendly. BuT if you F up your screwed! Better be near a computer. Found early on remove slot1 and kick TWRP. Installs kernels quick and efficient. Haven't had any problems yet. Would be killer if backup would flash in Stock Recovery.
[Verizon Samsung Galaxy S 4] Legitsu:
yea its a terrible idea as far as flashing new rom's go: system--updates are less of a issue but still meh ... fiddling with the partitions on a live system never a good idea ... on any platform this is just asking for trouble because noobs will be fiddling with it and breaking there devices left and right

and I haven't played with it but I am pretty sure it would be possible for safestrap and flash-fire to be made to play nice in the same sandbox
[Verizon Samsung Galaxy S 4] muniz_ri:
Safestrap is now obsolete. Check out MultiSystem, I will be helping hasbadr test for the S5 and S4. You may want to reach out to him if you are also interested in testing. Sounds like what you are looking for.
[Verizon Samsung Galaxy S 4] npjohnson:
tried to PM the username "hasbadr" and it said invalid recipient...
[Verizon Samsung Galaxy S 4] notonmdk:
Try hsbadr.

Multisystem:

http://xdaforums.com/verizon-galaxy-note-3/help/qa-multisystem-android-t3089530
[Verizon Samsung Galaxy S 4] Legitsu:
yea but not everyone wants to drop >60 bucks on a microsd card simply so they can use this

also calling safe strap Obsolete is quiet a big claim

I assume it can simply overwrite the stock rom slot
[Verizon Samsung Galaxy S 4] npjohnson:
Uhoh. Bad news.

According to Rovo89, Samsung made some *unnecessary* changes to the ART runtime... and it seems to be what is causing the Bootloops... ugh. In laymans terms... bad news... needs further research.
[Verizon Samsung Galaxy S 4] Legitsu:
disable ART via buildprop ???

afaik ART has never worked on touchwizz roms

any time spent on this is better spent getting kexec working lol fkin samsung
[Verizon Samsung Galaxy S 4] npjohnson:
Maybe you just haven't been on Lollipop yet... the ART runtime is the only option on 5.0.x+... There is no Dalvik to be used anymore...
[Verizon Samsung Galaxy S 4] Legitsu:
ahh thats right ... well down the rom source rabbit hole you go

:fingers-crossed:
[Verizon Samsung Galaxy S 4] wavedashdoc:
Just a heads up, I flashed the OC1 modem. Works perfectly with kitpop 1.3. I have a extra bar in my house where I know I only ever get 1. So I recommend it.

BTW. Egarly awaiting 2.0! Hope you can get the new kernel to play with the GPE ROM! Also wouldn't mind 1.4 too :P keep up the good work [MENTION=5848265]npjohnson[/MENTION].
[Verizon Samsung Galaxy S 4] shawnsingh:
Guys is their a way to root of we are on the offical lollipop version.
[Verizon Samsung Galaxy S 4] Legitsu:
not if you took the OTA

if you did you permanently lost root

theirs a giant red warning on the page 86

NEVER FLASH A OTA
[Verizon Samsung Galaxy S 4] wavedashdoc:
I don't think the giant red text will never be big enough for those who don't read.
[Verizon Samsung Galaxy S 4] Legitsu:
https://youtu.be/QDvQ77JP8nw
[Verizon Samsung Galaxy S 4] sinner822:
??? First rule of thumb. DON'T TAKE OTA!!

But really..

You were lucky to have had problems. You had a second chance and didn't take it.

Lesson learned.
[Verizon Samsung Galaxy S 4] Legitsu:
there isn't gonna be any new root exploits for a long long time IF it at all ... forget about autoroot not gonna happen ...
[Verizon Samsung Galaxy S 4] shawnsingh:
Actually never mind there will be a root exploit I have confirmed after reading a article hopefully that guy is right.
[Verizon Samsung Galaxy S 4] sinner822:
On locked BL via OTA?

Interesting. Something we are not privy to.
[Verizon Samsung Galaxy S 4] Legitsu:
hes full of crap it took geohot >2 years to come up with towelroot

unless there is something new and broken in 5.01
[Verizon Samsung Galaxy S 4] klabit87:
Could you link us to the article you are referring to?
[Verizon Samsung Galaxy S 4] sinner822:
Right
[Verizon Samsung Galaxy S 4] npjohnson:
Great to hear. I'll include it as an option in the next ROM.

Nope. Probably won't be... For a long while.

Agreed. OTA's in general on Locked devices is a bad idea.

CF Auto-Root will never, ever work on a locked BL. It relies on booting a custom kernel to root the device... Of which we will likely never be able to do.

Nope. No 5.0.x native root for a while...

On that topic though... *Begin Rant* there is a native 5.0.x root access bug. It is known as CVE-2015-1474 , it is based off a GraphicBuffer overflow, and, though tricky to exploit, I am 100% sure (after a lot of research) that the vulnerability exists on Stock 5.0.1 on the Nexus 6. I am actually working on something for this. The bad news is that Samsung uses a modified GraphicsBuffer, so I am unsure of /if/ it exists on Samsung FW's. I'll start looking into it. I doubt it is present though.

I also know that Surge1223 is working on that same exploit with some other people. Just FYI. Its still a long ways off though.

It was actually based on a 6 month old exploit by Comex (the futex sub-class bug, suuupper hard to exploit).
[Verizon Samsung Galaxy S 4] sinner822:
If I am not mistaken. Correct me if I'm wrong. That exploit only worked with Nexus (phone not ROM) and a couple of Sonys.
[Verizon Samsung Galaxy S 4] npjohnson:
It is partially present on the Note 4, so no. It applies to a lot of android builds.
[Verizon Samsung Galaxy S 4] shawnsingh:
That's what I heard on Google it was like a link to the xda forum on some Chinese website and I translated it and it said there will be root for galaxy s4 5.0.1
[Verizon Samsung Galaxy S 4] skepticmisfit:
so translations usually aren't accurate especially when you're using Google translate to translate websites
[Verizon Samsung Galaxy S 4] shawnsingh:
Yeah you might be right man I wish their was a way but whatever.
[Verizon Samsung Galaxy S 4] sinner822:
Lollipop boots on MK2 bootloader so there is no need to upgrade past it. With Flashfire you can save full backups and switch back and forth between Lollipop (with modified 5.01 zip) and KitKat permissive.

Personally I don't think Lollipop is worth upgrading to so far. For many reasons. But to each there own.
[Verizon Samsung Galaxy S 4] wavedashdoc:
That being said. [MENTION=5848265]npjohnson[/MENTION] any idea when we could be seeing 1.4? Also how is the GPE port coming? Any small breakthroughs with it's progress?

Sorry for the typical ETA, but I'm seriously tired of checking the other threads where its only, " hey I updated to OC1 and don't have root, can I have root cause I can't read "
[Verizon Samsung Galaxy S 4] Legitsu:
stop asking every time you ask a kitten drowns in acid
[Verizon Samsung Galaxy S 4] npjohnson:
As always everybody, LegitSU *Claps* XD.

1.4 is on the backburner for LP work. When I get LP running, I'll make get it tweaked to my inking and diff the changes back to 1.4 KK I decided. It will be easier for me, and everybody else that way.

But If I can't get LP at least booting by the end of the week, I have to take a break for Exams... and those run through the end of June. So it may be later this week, and it may at the beginning of Summer, I just don't know. (That's even granted that we ARE able to get LP booting, fricking Samsung managed to change ART to a point that stock ART, which EVERY other manufacturer uses, doesn't get along with the stock kernel, and prevents the ROM from booting).
[Verizon Samsung Galaxy S 4] wavedashdoc:
Thanks for the update! I'm sure everyone following this rom is happy to at least know some time frame now. Yeah, I saw your post about that earlier. Samsung can't just leave anything "stock" alone, now can they. Biggest reason never to go back to touchwiz, even the streamlined lollipop touchwiz.

Good luck on your exams bud!
[Verizon Samsung Galaxy S 4] whichonespink73:
Been loving this ROM the last few weeks. Lost my pre-MDK S4 to a broken screen and thought I'd never see stock again. Anyways, I've been having some troubles with my SMS the last week or so. After some seemingly random amount of time, my phone will stop sending and receiving SMS messages despite have full LTE. The only thing that fixes it is a full reboot. Anyone encountered this issue?

I'm on NC5 and applied the Gravity Box and ChangeAPN fixes. Odin'd before flashing as well.
[Verizon Samsung Galaxy S 4] Legitsu:
install textra and enable the wifi calling/sms fix

don't use changeAPN ever ...
[Verizon Samsung Galaxy S 4] aleggsue:
For some reason, I can never get any AOSP mix ROMs to work on my phone. NC5, SS 3.75.

I flashed the vzwapnfix, and it worked, for a little bit.

I now can't get any service at all. I tried the apn fix, I tried manually entering the apn info...

I followed the instructions to a T and for some reason service never stays on my phone. It always goes away after while (relatively high service area)

Any ideas?

Oh, and my service provider goes to "empty" if that helps

Edit:

I also tried smart radio in gravitybox, no avail.
[Verizon Samsung Galaxy S 4] XxD34THxX:
*insert expletives aimed as Sammysung*
[Verizon Samsung Galaxy S 4] sinner822:
Look in about phone. If you see a + before your number go to phone app *#*#4636#*#*

Then phone info and change to CDMA/LTE back out and reboot.
[Verizon Samsung Galaxy S 4] npjohnson:
Just an FYI, looking like true GPE 5.0.1 isn't viable on the stock kernel :( Samsung changed ART to much. No way to work around.

But... Although I will to continue trying to get true GPE to work, I have gotten both the GPE System UI (NC Shade) & GPE Settings & All other GPE Apps working on the Stock ROM, can't even tell it was at one point TW! Bad news is, no GPE lock screen :(, so I decided to replace the Sammy lock screen with AcDisplay (which is awesome BTW).

I should have more to report about this ROM (name undecided at this point... Taking recommendations [emoji14]) in a week or two.
[Verizon Samsung Galaxy S 4] wavedashdoc:
That's awesome that you've been able to replace the touchwiz look! Just wondering, will on screen nav keys be enabled like the 4.4.4 ROM?
[Verizon Samsung Galaxy S 4] skepticmisfit:
so it's going to kinda be like eclipse.. hehe.

also will this rom have an aroma installer or will it be compatible with flashfire (for those of us who did the oc1 rooted upgrade with the nk4 bootloader)