yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] skepticmisfit:
well we're not just trying to run CM here. kexec opens us up to so many other options because we can actually use different kernels. we can multi boot ROMs thanks to ROM slots in safestrap, and we could also potentially use other mobile Linux-based oses (like Ubuntu touch, uh.. and others)
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
yup i agree.
[Verizon Samsung Galaxy S 4] dewhashish:
This is great! I hope kexec with SS works out well enough to throw CM on this phone for a daily driver
[Verizon Samsung Galaxy S 4] NighthawkXL:
Let's keep the premature celebration down folks... let's not forget this is still a work in progress and isn't guaranteed to work.

Anyway, I'm setting up a new kitchen so I can take a gander and poke around it a bit. Probably won't find much since this isn't my forte but hey who knows I may learn something.

Keep up the good work Surge & Co.
[Verizon Samsung Galaxy S 4] dave4100:
What about NC6?
[Verizon Samsung Galaxy S 4] anthonyg45157:
Its been a long time coming..but my contact is up in 3 days. Im getting the nexus 6(whenever it is released). I wish everyone the best of luck with this device including surge! I will still be following this thread and WILL do my part in donation if this thing gets custom kernel/rom support... we have an incredible community here and work amazing together!

Good Luck!:good:
[Verizon Samsung Galaxy S 4] toaster22:
You should be on NC5 since this is what it has been developed for. It could work on NC6 but if an exploit that is getting used was fixed for NC6, it won't be able to work.
[Verizon Samsung Galaxy S 4] Surge1223:
Not worried about it. I was debating posting the Odin tars for NG6 for awhile, I see Muniz did, which prob good since it will save some bricks but I have no idea if ng6 has the ability to be set to Permissive (though I'm 74% i can make it Permissive but not really a priority for me atm).
[Verizon Samsung Galaxy S 4] michael3770:
So this still means we have to use ss instead of some workaroud against the bl?
[Verizon Samsung Galaxy S 4] junjlo:
Exciting stuff though my s4 has kexec it's nice to see newer firmwares may possibly get it. Hope this research pays off going forward like with s5 and note 4.
[Verizon Samsung Galaxy S 4] DX.Deception:
I don't know if we have a fully working kexec yet
[Verizon Samsung Galaxy S 4] Surge1223:
I think people go crazy over wanting custom recoveries (TWRP, CWM) but in reality the only reason custom recoveries are needed is because its booted into an environment that allows you to flash a custom kernel (since its not using the system kernel in recovery). The problem with SS is that it while we are in the ramdisk, the kernel is still initialized (albeit with way less interference from drivers etc) but with kexec it would eliminate the problem since we could just as easily boot into a new kernel. Using SS the normal user wouldnt even notice the difference between using TWRP or SS. A means to an end.
[Verizon Samsung Galaxy S 4] SnyderGuy:
It sounds like with kexec we would be able to run custom recoveries, without the need of SS. Which would allow custom kernels, custom roms beyond TW.
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
Surge said "Using SS the normal user wouldnt even notice the difference between using TWRP or SS." So probably SS for the time being.
[Verizon Samsung Galaxy S 4] DeadlySin9:
It would still be SS technically, but since we can flash kernels it would be the same functionality of TWRP. Stock recovery would remain untouched.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] npjohnson:
This is correct. But we would still have to have the Stock kernel in place. (Nothing else, just the kernel.) and then Safestrap would use ROM Slots to Kexec to the new kernel
[Verizon Samsung Galaxy S 4] twizzlejr:
With all this kexec talk and excitement going on I'm wondering while having rom slots and multiple roms is cool and all I'm wondering if with kexec it will make it a lil safer to flash roms over the stock slot I know it has its risks now but I've been hesitant to do it yet even tho I'd like to have most of my 32gb phones space to use thanks in advance
[Verizon Samsung Galaxy S 4] SnyderGuy:
Speaking of stock recovery... Is there any recovery.img that is the stock so I can just flash that using SS or ROM toolbox? I accidentally flashed a CWM recovery a few months back, and I can't access recovery mode anymore since. That's actually how I discovered safestrap, so I just use that, but I would still like to get my old stock recovery back that way I don't have to boot into odin mode and boot normally from there every time I accidentally boot into recovery (rarely, but still)
[Verizon Samsung Galaxy S 4] DeadlySin9:
You'll have to get an Odin tar of just the recovery for your version.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] SnyderGuy:
Do I actually need a recovery? When the bootloader has been 'unlocked', could I just flash one from safestrap?
[Verizon Samsung Galaxy S 4] DeadlySin9:
If it were unlocked, you wouldn't need Safestrap, and you can't flash one from there. It's best to have the stock recovery still intact just to minimize points of failure.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] SnyderGuy:
So would it be correct to say that once we use SS 3.8.2+ to unlock the bootloader, we can have an entirely new boot.img? Is this a complete unlock or will just be like the current bypass but with the ability for other stuff too.
[Verizon Samsung Galaxy S 4] carl1961:
download your firmware from www.samfirmware.com

unzip with 7-zip

uzip the md5 if it is also in a zip

find your recovery.img

repack to a odin install with TAR_MD5_PACKAGER

install with odin
[Verizon Samsung Galaxy S 4] DeadlySin9:
Safestrap will NOT unlock the bootloader. Kexec will be another bypass. The original boot.img will remain untouched, we'll just be able to load others over that one at boot. It will function differently than Loki, but the end result is the same (minus a "real" custom recovery that replaces stock).

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] SnyderGuy:
Hmm... Okay. So, how far does this bypass go? What could we do with it? Flash roms away from TW, yes, flash kernels, is that it? Could we flash android lollipop early? (since samsung takes forever),
[Verizon Samsung Galaxy S 4] Thr33-F0ur:
Yeah we could pretty much flash anything except flash a true custom recovery.
[Verizon Samsung Galaxy S 4] DeadlySin9:
We could flash it early as long as somebody develops a kernel that works with Lollipop and our device (which if I remember has already been brought up somewhere). Kexec will allow us kernel flashes and since that's basically the only thing it couldn't do before we can flash anything.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] Bright09:
Hopefully that we could see a unlocked boot loader again on the gs3 miss it
[Verizon Samsung Galaxy S 4] SnyderGuy:
Well, we can flash anything currently, but whether it'll work or not is a different question. Third party roms like cyanogenmod don't work currently. But they'll work with kexec, correct?
[Verizon Samsung Galaxy S 4] DeadlySin9:
Yes, because the kernel is the reason they didn't before. SS would flash everything except kernels.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] brd912:
I just wanna say thanks to all you guys. This is a great device and with an unlocked bootloader, I could be satisfied with this phone for a while. The S5 and note 4 are awesome but they really haven't come out with anything since the S4 that made me want to spend the cash like the S4 did. This phone is solid and you awesome folks make it even better. Thanks for everything you are doing.
[Verizon Samsung Galaxy S 4] jjppott:
MD5 Hash

I am not sure if this is really relevant (it is way over my head), but thought I would share anyway. It does not seem like I can post external links (not enough post) but the info can be found: natmchugh.blogspot.com/2014/10/how-i-created-two-images-with-same-md5.html It seems like there are some vulnerabilities with md5.
[Verizon Samsung Galaxy S 4] SnyderGuy:
I can't wait!(:

A few people at Reddit are asking me a few questions about this...

1) Would this work with the S3 and or S5? (I presume no, but just double checking)

2) How can we be sure this won't destroy our phone even if we install correctly? ( told them there's no way to be sure for anything besides looking at what other people have reported, and doing a full clean wipe of the phone before proceeding just in case)
[Verizon Samsung Galaxy S 4] DeadlySin9:
1) A different exploit for loading modules would need to be found, but past that the kexec module may be easier to set up based on our own.

2) Part of Safestrap's "safe" part is leaving all the stock system and kernel in place. All this will be stored just like the slots in image files and loaded on boot, leaving the stock system in place. Even in the stock slot a custom kernel would be stored separately.

PM me a link to this thread, I'd be glad to answer questions there. I go by the same username.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
hey one tiny noob question:

Should I stay on mk2 or up to nc5? would that affect kexec?
[Verizon Samsung Galaxy S 4] DeadlySin9:
I believe it's being developed on 4.4, but since modload is available on both you should be fine. In the end it shouldn't matter since you'll be loading up a different kernel, but it's really up to the devs if they make it detect the version and appropriate address in memory to be exploited.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] scryan:
Hrm, if there isn't anything specific you looking for maybe just stay on mk2... lol sometimes it almost seems like you may as well just leave it at the earliest your happy with.

However, you should be OK with NC5. I do belive this is what Surge is on. bypasslkm didn't work on it originally but they just needed to find the correct address, so as far as I know you should be fine. Don't go further (NG6) though.

Random aside: if your a vim user make sure you have checked out the vimperator add on for firefox. Maybe this is well known, but I just found it and its sure nice.
[Verizon Samsung Galaxy S 4] DX.Deception:
What is vim?
[Verizon Samsung Galaxy S 4] scryan:
Improved version of vi...

And before you ask, vi is a robust alternative to ed.
[Verizon Samsung Galaxy S 4] GRock84:
^^This but, this provides a better understanding --> http://www.linux.com/learn/tutorials/228600-vim-101-a-beginners-guide-to-vim
[Verizon Samsung Galaxy S 4] kamameel:
As everything gets finalized should we expect a new thread on the "S4 General" board which will include step by step directions and file links and everything, or will all of that stay inside this thread?
[Verizon Samsung Galaxy S 4] scryan:
What is getting finalized?

Where is all this almost done coming from?

Kexec still doesn't work.... Hopefully it does soon but as far as you all are concerned we are exactly where we were when hash stopped work.... A couple months ago. We can load moduals but Kexec freezes and doesn't work.

Not to discredit surge, I hope he understands I not just being pessimistic or saying he can't get it to work....

Its just that some of you act like this is an English paper he just needs to finish writing.

There are not steps, he is not a certain % done.

Currently we have source code from a linux utility that is trying to be compiled for android. This is not impossible and it has been done before... But on other phones on other systems that run other kernels and have completely different security, adresses for important information that needs to be passed and well... Just on a different system entirely.

They have to go through and find each place it stops working. Trouble shoot that is not working then try and figure out what the equivilant would be on our system. On any given day he could find one major flaw that is stopping it from working that just needs a minor tweek and were done. OR he could find one minor flaw where Samsung has changed things enough so that it will NEVER work right. There are multiple devices that had kexec in progress where it NEVER got sorted. there are multiple devices where working versions of Kexec were created, however stability was never achived to a point of making it usable. There are multiple devices where working versions of Kexec were created where not all CPUs couldbe brought back on line and so performance of the system has crippled enough that it was not realistically usable. We are not even this far.

We aren't steps away. We don't just need to figure out how to make _____ work. We don't even know why it doesn't work. First we are hoping they figure that out, THEN we are hoping they figure out if and how to fix it.

But yes... If surge manages to find a work around to effectively give us a full working recovery it will obviously be posted about. People STILL post to let the S4 forum know about the loki exploit, why on earth would you think that after a year of work (litterally) Surge isn't going to tell anyone past this immediate group? If nothing else there IS that issue of the thousands of dollars of bounties "up for grabs" that he likely won't even see a fraction of :(

And here I was just hoping someone was going to ask "What is ed?"
[Verizon Samsung Galaxy S 4] Surge1223:
^^This. Exactly

And you're right everyday I have found some flaw I've had to fix, I haven't pushed commits because I've made a ton.
[Verizon Samsung Galaxy S 4] brd912:
Just wondering, is it at all possible to overclock our stock kernel? I love the echo rom but after some time of using a stock rom, I remember why I love aosp and all that jazz. I love features and a beautiful layout but I need speed and performance overall
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
i don't think so. You might be able to do a tiny bit of tinkering though. But don't count my word for it.
[Verizon Samsung Galaxy S 4] brd912:
I'm dying here lol.
[Verizon Samsung Galaxy S 4] daredevl99:
that would require modifying the kernel source which makes it a custom kernel and wont flash. it will most probably brick your phone.
[Verizon Samsung Galaxy S 4] liljoe727:
Has anybody tried simply pulling up the hack screen and gaining kernel access that way? This may be a stupid question but in Jack Ryan: Shadow Recruit, Jack Ryan (played by discount Tom Cruise) steals this Russian dudes entire plot for world domination by just plugging his mobile device into the Russian guys personal computer via USB and pulling up the hack screen. Sounds crazy, right? I thought so too until I remembered the scene in the Avengers where Tony Stark hacks into S.H.I.E.L.D via jump drive....maybe it has something to do with the USB port vulnerability then? Just wondering...I have a bunch of USB cables and some jump drives if you guys need to borrow em... :D

"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
[Verizon Samsung Galaxy S 4] brd912:
I knew that but didn't want to admit it lol. Sometimes it gets hard to not act like a 3 year old who just wants what they want! Haha. I love this phone..when I had the Sprint version I ran the same rom for months with not a problem. The safestrap roms are amazing giving the limitations but I can still feel that little bit missing. Thanks and good luck to all of you trying to unlock this phones true potential!!

???
[Verizon Samsung Galaxy S 4] tobiascuypers:
I'm not sure that I'm following anything that you are saying..
[Verizon Samsung Galaxy S 4] liljoe727:
It's only jokes is all.

"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
[Verizon Samsung Galaxy S 4] PetrichorXFi:
Is there an NC6? I've been using the NC5 and disabled OTA to maintain possible Kernel Unlock... who knows what updates do so I've been trying to play it safe
[Verizon Samsung Galaxy S 4] sokrboot:
Perhaps you are thinking NG6?
[Verizon Samsung Galaxy S 4] DeadlySin9:
Easy rule of thumb is don't update. Unless you're running stock ROM, updating won't do you much unless you maybe want to try out the modem for better service. As long as you can get back to NC5 Then you can update, I don't know the equivalent downgradeable versions on Verizon s4's.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] MorrisC2010:
NG6 is the newest OTA and is safe to take in the since that you can Odin back to NC5. It actually fixed some bluetooth issues for me that just having root on NC5 couldn't. So user preference as always on whether or not to take it
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
ah I see. I'll upgrade to nc5 then. It's a pain upgrading back to nc5 everytime i clean wipe to mk2 for romming xD
[Verizon Samsung Galaxy S 4] junjlo:
So what is the difference between kexec and loki?
[Verizon Samsung Galaxy S 4] scryan:
One is a utility to replace the kernel in memory during run time in unix based systems, The other was an exploit found in the boot code of MDK S4 devices that allowed hijacking the boot chain before the kernel loaded.
[Verizon Samsung Galaxy S 4] dewhashish:
I remember Hashcode got kexec working back on the Droid 4 (possibly the OG Droid Razr too) and was able to port all kinds of ROMs to safetrap
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
Those devices didn't have all the "security" measures that the S4/Note 3 have. And yes OG Droid Razr did get kexec as well.
[Verizon Samsung Galaxy S 4] twizzlejr:
What's this security policy update I'm getting from Samsung in the play store anybody else get it yet and is it safe
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
I keep getting crap about it. I problably wouldnt update.
[Verizon Samsung Galaxy S 4] skepticmisfit:
never gotten it in the play store but I'm pretty sure it's safe.. granted I haven't really heard anything about it or noticed anything negative that happened when enabling it. don't worry about it.
[Verizon Samsung Galaxy S 4] scryan:
Did you seriously just come here to say he should take an OTA security update from samsung?

In this year old thread here about people trying to find a vulnerability in the current level of security? So you want to patch potential flaws and increase Samsungs control over your phone? THATS how we will get the phone "hacked"?

(no. how does this website not have a face palm smiley face?)
[Verizon Samsung Galaxy S 4] carl1961:
have you deleted all your knox files ? ever since I removed all my Knox related files I do not get that.
[Verizon Samsung Galaxy S 4] twizzlejr:
I'm gonna avoid it like the plague I just thought it was weird that Samsung had a security policy update coming thru the play store not just a regular update is Samsung being sneaky or what

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

Even weirder now it's gone didn't say it did the update or anything
[Verizon Samsung Galaxy S 4] dewhashish:
It's just security policies for KNOX and email. I have my work email on my note 3 and it requires security updates for certificates
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
can you please link me or tell me what files I need to delete to get rid of that knox ota from the play store? im assuming they are system apps

EDIT: forgot to quote, sorry!
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
Hey Surge and company!

I was wandering around XDA when I stumbled upon this

http://xdaforums.com/galaxy-note-3/devs-only/kernel-kernel-execution-loading-custom-t2812650/page13

It seems like the Note 3 forums are making great process on kexec as well. Maybe you guys can team up to make a super kexec developer team :D? You guys might already know this, though :P. I know surge and ryanbg communicate alot.

Nevertheless, thanks guys for your hard work!
[Verizon Samsung Galaxy S 4] Surge1223:
This gets mentioned quite often, and I usually just defer commenting on it but I figure I should probably give a reason why.

Long story short, (note 3 Alliance ROM users prob already know) that I and a few of the devs in that thread have unresolved differences so for the time being its best we don't cause any drama.
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
Oh ok. Yeah um nevermind that then :)
[Verizon Samsung Galaxy S 4] XxD34THxX:
I feel like an idiot for saying this, and it probably has already been said but I can't find it, so I will say this now so I don't do anything stupider later.

Why not just uninstall knox and remove all traces of it? As far as I can see(23 inches onto phone screen), it is deeply integrated into the system, but won't mock Knox or a modded version of the knox in the system help with unlocking the bl?
[Verizon Samsung Galaxy S 4] npjohnson:
The KNOX at the system level has no control over the KNOX kernel lock at BL level. Plus even if we made a modded KNOX app, it would invalidate the cryptographic signature on the app, its the same reason we can't flash a modded stock BL, the signatures are invalidated, and to resign it would require Samsung's RSA key. Of which no one has/would take years to crack with a supercomputer.
[Verizon Samsung Galaxy S 4] XxD34THxX:
So to get through the bootloader, we have to get thru knox first?
[Verizon Samsung Galaxy S 4] dewhashish:
No he just said you need Samsung's RSA keys to crack the bootloader
[Verizon Samsung Galaxy S 4] Surge1223:
Don't lose any sleep about Knox. I would gladly trip the Knox counter for an unlock (in fact my Knox counter has been tripped for as long as I can remember)

Edit: just wanted to add that threads like this are a dying breed, there was a time not too long ago (gs 3 days) where devs would work together and make threads like this. I think we are the last one, so before anyone decides to post anything that has nothing to do with our goal, just remember that this thread is an remnant from a time long gone, and success is the only thing that will bring this format back. Just saying. Sorry for the philosophical ideology type post but it needed to be said.
[Verizon Samsung Galaxy S 4] dmc2359:
http://xdaforums.com/showpost.php?p=57025502&postcount=13277

Well it looks this this is the end....and I can say that I am saddened to see you go. I really wish I knew what happened that made you and Nate come to this decision, I can only assume the Open-Bump might have played a role but I really dont know because I dont follow any boards other than the s4.

It was an honor to have such great minds as yourselves working on these locked devices for as long as you have been. I really like Samsung and the only reason I kept my s4 was because of workarounds such as Safestrap and such, but it looks like from now on its Nexus or HTC for me.

Thanks for all the hard work, you will be missed. :crying:
[Verizon Samsung Galaxy S 4] skepticmisfit:
well then. kinda sucks the situation got to this point..wait what was the situation to begin with? what happened? and this may be a harder question to answer but what could we expect the future to be like for those who use ROMs on ss?