yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] HORiZUN:
Yes. Exactly. Its a bypass for the locked bootloader which will allow custom roms. Everyone on mf3/me7 is watching the thread lol
[Verizon Samsung Galaxy S 4] Volvogia:
Thank you. Like i said, im on MDK and im watching it with you all. This is a tight community and i feel as if the MDK people out there are not watching this thread then shame on them.
[Verizon Samsung Galaxy S 4] HORiZUN:
Myself, along with many many others received an s4 with the dreaded update already installed. You're lucky you have one you can install loki on. Loki is similar to safestrap.
[Verizon Samsung Galaxy S 4] jamesonelam:
I'm so exited for this to work. And, if anyone is wondering, Beanstown said his JellyBeans ROM will work with this once its up and running. :D :thumbup:
[Verizon Samsung Galaxy S 4] dwd3885:
If this is successful, would we be able to flash Google Play Edition ROMS?
[Verizon Samsung Galaxy S 4] baling:
So stoked for this!
[Verizon Samsung Galaxy S 4] Hashcode:
I'll definitely post a new thread in the dev section once a usable version is ready.
[Verizon Samsung Galaxy S 4] Brave Sand:
I'm not sure how many times it's been said, but no, it won't work by default. The ROM is going to need to be optimized for Safetrap. But I'm pretty sure someone volunteered to work on the GPE ROM to get it working for us.
[Verizon Samsung Galaxy S 4] dwd3885:
I know it won't work by default and the ROM needs to be updated. Just didn't know if it were possible, since they said AOSP ROMs wouldn't work yet.
[Verizon Samsung Galaxy S 4] mavverick:
This is absolutely amazing work HC. I'm looking forward to SS on my AT&T S4 (mf3). Thanks, and good luck!
[Verizon Samsung Galaxy S 4] sppatel:
Seems like we need to get some of the repetitive questions on a FAQ.
[Verizon Samsung Galaxy S 4] BIGDADDYXXL:
I hope that this will work soon for at&t im having flash withdrawal
[Verizon Samsung Galaxy S 4] Addiso:
Nevermind.
[Verizon Samsung Galaxy S 4] mrro82:
In using it on my AT&T S4. Obviously you can't flash anything yet but the proof of concept works.

Sent from the other side of the Milky Way with my S4.
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
You can't flash ROMs with it, but have you checked out Flash Gordon?
[Verizon Samsung Galaxy S 4] anthony92170:
question to anyone here 1st dont shoot the questioneer here. is it possible to take a rom and make it odin flashable till ss is done or if people dont want to use ss? example take a rooted rom like beans or any me7 rom and use odin
[Verizon Samsung Galaxy S 4] michaelg117:
I was thinking the same thing but never really found an answer.

Sent from Navi
[Verizon Samsung Galaxy S 4] hondabomdc5:
So im new to the s4 game...I have previously rooted and installed safestrap on my droid razr days....however, im new to safestrap with samsung phones and all. From what I understand, stupid verizon locked our phone with the latest update so installing roms is basically not able to happen but we can still root. If hashcode gets this safestrap working. ...does that mean flashing roms is in the near future? That would be awesome. Im really excited because ive been wanting to root and flash the hyperdrive rom
[Verizon Samsung Galaxy S 4] thatbigmoose:
Any partition you flash in Odin has to be signed by AT&T/Samsung or it will abort. If you could just flash custom ROMs in Odin that'd defeat the purpose of the locked boot loader.
[Verizon Samsung Galaxy S 4] Au_A7:
Sorry if this is a repeat question but it didn't look like this was answered. What is stored on the 1-3gb rom slot partition? And can multiple slots access the same data, so that if you installed a ROM in a new slot it would have all the data from your previously used rom slot?
[Verizon Samsung Galaxy S 4] killajoe:
Yes flashing Roms is in our near future. Be patient president hashcode has everything under control
[Verizon Samsung Galaxy S 4] anthony92170:
cool thanks i kinda figured something was stopping it. to bad we the community couldnt figure a way to put signature in and screw samsung.
[Verizon Samsung Galaxy S 4] decaturbob:
Me7 is locked . No roms can be flashed. Once we have ss working we are limited to roms that works with stock kernal. So have some patience folks and read the thread.
[Verizon Samsung Galaxy S 4] anthony92170:
we/i know that just asking questions on other ways to work. thank for your info
[Verizon Samsung Galaxy S 4] michaelg117:
People here need to either

1) Find jobs with Samsung,

Or

2) make friends on the inside. :P

Sent from Navi
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
I would take Honey Boo Boo's mother home with me if it meant for an unlocked bootloader.
[Verizon Samsung Galaxy S 4] anthony92170:
you don't want that. i know i don't. my exwife now looks like that man did i doge a bullet
[Verizon Samsung Galaxy S 4] Febby:
Does anyone know if kexec really will be possible? I remember adam outler commenting on it a while back. Here's a screen shot to what he said. Number 4 on the list. I'm assuming he said we would need some sort of possible vulnerability to load kexec. :(
[Verizon Samsung Galaxy S 4] Hashcode:
SElinux is only in permissive mode on the current builds. That won't be a problem.
[Verizon Samsung Galaxy S 4] DeadlySin9:
The 1-3 GB slot is the data partition for that ROM, where user apps and data are stored. They are not shared.
[Verizon Samsung Galaxy S 4] eskomo:
People need to start reading before asking questions. And instead of answering these questions over and over just tell them to read. Its getting out of hand the same questions being asked when the answer is right there for them to read. You will learn much more and feel better about it when you read for yourself.
[Verizon Samsung Galaxy S 4] Andrew149:
And those people wont read what you just said.
[Verizon Samsung Galaxy S 4] phobia09:
Correct me please if this is wrong, but logic tells me that if someone has apps moved to their external microsd, ROM slots should still be able to access those apps as if they were on internal storage. Again, I'm just spitballin' here.
[Verizon Samsung Galaxy S 4] PetrichorXFi:
Agreed...

This entire thread is mostly what ifs... If we remove them they won't happen
[Verizon Samsung Galaxy S 4] Roland_D:
Yeah I would say the thread is 25% informational 25% good questions 25% what if's and 25% people who tell the what if's to STFU... Do you guys think 12 comments in a row about how people should read the forum instead of posting questions is not polluting the thread at all?

This is my first and last 2 cents about it... Whoever will try to argue will be doing it with him or herself as I won't participate.

Just wanted to give you guys something to think about while we wait for SS.

Sent from my SGS4
[Verizon Samsung Galaxy S 4] brad457:
Willing to help build roms

Greetings,

I currently have a Galaxy S4 with the latest update (MF3). I also develop Android applications and have a mid to high level programming / scripting skills set (PHP, C#, VB, Java, etc). I am very familiar with Linux development and administration. I am willing to help on this project with either the development/testing of a custom ROM or with any development/testing of Safestrap.

Let me know if I can help either way.

FYI: I'm not interested in any bounty... I just believe that when people buy something, they should be able to do what they want with it, because that's the cornerstone of ownership of property. I Just want people (myself included) to be able to use a product that they paid for the way they want.

Thanks.
[Verizon Samsung Galaxy S 4] DeadlySin9:
In theory, yes, but I believe you'd have to do more if it's actually possible in practice.
[Verizon Samsung Galaxy S 4] Lou 270:
I have a question and I haven't seen it asked yet but it could have been I dont know I might have missed it if so dont shoot me so here it goes I currently have my pbone rooted with no way of flashing a rom and I know that ss will b the work around but will I have to do anything special to use ss or will it just pick up where we are at now because some of us have 0 recovery not even stock so will we have to use odin to rest everything ;)
[Verizon Samsung Galaxy S 4] sokrboot:
Once SS is working. Download SS and install then you will have recovery. And we can flash ROMs that are friendly to the stock kernel.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] jesssiii:
Extract the system part of the ME7 stock and zip it? The extracted Tar I have has the system labeled system.img.ext4

Does that sound right? I got it off IncredibleK's dl site. Anyone have the correct image?

OK, that is the correct file. My question is, is that the only file (system.img.ext4) that I should zip up or do I need any of the others to work (to not overwrite user data, I mean, in case of bork).

Sent from my DInc, due to my GNex dying before my VZW S4 arrived :-\
[Verizon Samsung Galaxy S 4] Alxoom33:
We respnd to noob questions, even if they have been answered before, became it's really not that difficult to be helpful!:cool:
[Verizon Samsung Galaxy S 4] HORiZUN:
Even if we've never flashed the system partition on our s4 through Odin before, we but knew we were on the right track in getting a fellow member out of the boot loop left from encryption :)
[Verizon Samsung Galaxy S 4] SamuriHL:
WOA. No no no no. You don't just "zip up" the file to make it an ODIN flashable file. I suggest checking out some threads here on XDA on how to create an ODIN tar md5. Yes, system.img.ext4 is what is needed, but, no you don't just "zip it up" and think it's going to work.
[Verizon Samsung Galaxy S 4] jesssiii:
Ok, thanks. Found a thread, gonna research:D

Sent from my DInc, due to my GNex dying before my VZW S4 arrived :-\
[Verizon Samsung Galaxy S 4] SamuriHL:
If my response sounded strongly worded it's because I don't want to see people brick their phones....and flashing the wrong thing in ODIN can certainly get you there in a hurry. Be careful.
[Verizon Samsung Galaxy S 4] jesssiii:
I understood that, thank you. That's why I've been scouring these S4 threads, reading, before the phone has arrived. I've never bricked, but have definitely soft bricked many times. I don't want to be in panic mode when it happens. I say when, not if, because it's just what happens. I seem to learn the hard way sometimes, no matter the research, lol.
[Verizon Samsung Galaxy S 4] SamuriHL:
Well, the fact that you're doing the research now so you can be prepared puts you lightyears ahead of most. I, for one, appreciate users that do the reading before getting into trouble. It makes helping them so much easier. It's precisely the point, in panic mode, that people tend to make a bad situation worse.
[Verizon Samsung Galaxy S 4] nbaj2k:
I'm definitely looking forward to this, thanks Hashcode for your hard work.

Just a quick question. If SS will only work with ROMs that allow the stock Kernel, does that count out Cyanogenmod? I was more just curious.

Thanks,

-J
[Verizon Samsung Galaxy S 4] Au_A7:
No because I'm pretty sure cm installs its own kernel. However I think someone offered to help make a build that's compatible with ss
[Verizon Samsung Galaxy S 4] nbaj2k:
Thanks for the info!
[Verizon Samsung Galaxy S 4] Alxoom33:
Amen to that!! We have the best community. :D:thumbup:
[Verizon Samsung Galaxy S 4] Hashcode:
Just a heads up: I got the S4 that sound-mind sent over today. I've rooted it and have the latest testing build of SS installed on it.

I'll have more time tonight to experiment w/ the build and do some debugging.

From what I saw today tho, there is a timeout happening w/ the touchscreen / panel. If you wait about 20 seconds and then touch the screen, it doesn't refresh, and then if you hit the back button, it'll be on the screen you should have been before.

Very interesting. :P

Anyway, more info as I get it.
[Verizon Samsung Galaxy S 4] SamuriHL:
Scariest words ever from a software engineer. :D I say that all the time. LMAO
[Verizon Samsung Galaxy S 4] Tomsgt:
Thanks a

Hashcode following closely
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Thanks Hashcode hopefully you can get us a recovery for us soon. Subscribed:thumbup::D
[Verizon Samsung Galaxy S 4] dooperman:
Anyone elses heart stop when they get a notifcation that hashcode commented in this thread?
[Verizon Samsung Galaxy S 4] littlebigarm:
Bro your a freaking genius..... I've been following this thread for a little bit now.... I'm stoked for this....I bought this phone a couple weeks ago and was distrought when I couldn't get recovery.... but now your making serious progress.... good work man..... major props to you
[Verizon Samsung Galaxy S 4] D Stave:
Could somebody point me in the direction of how to donate to Hashcode?
[Verizon Samsung Galaxy S 4] sokrboot:
Go back to earlier this thread. Link is there.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Bahaha yes. Every single time. It's to the point where I'm checking my phone notifications for XDA so frequently, my fiancee has started to ask me what's so interesting. Off course, when I nerd out and try to explain it, her eyes get glassy lmfao.
[Verizon Samsung Galaxy S 4] mrjinglesusa:
If there were a way to ONLY be notified that Hashcode posted in this thread I would subscribe to it. Would be way too annoying to be notified every time someone posts "What if..." or "Can I...." or "How do I...", which is 98% of the posts in this thread.
[Verizon Samsung Galaxy S 4] littlebigarm:
Or just to say how much of a bad ass hash is for the work he does
[Verizon Samsung Galaxy S 4] dwd3885:
Yea I wish. I was just notified of your post just now ;)
[Verizon Samsung Galaxy S 4] sppatel:
Good idea!!! I think I'm going to setup a gmail filter for this then label with it "hashcode". Then add the gmail widget that shows email from the label "hashcode".

Matches: subject:(Reply to thread '[RECOVERY LOCKED/ME7] Safestrap Recovery v3.5x [WIP DISCUSSION]) Hashcode has just replied to a thread

Do this: Apply label "Hashcode"

Matches: subject:Safestrap -Hashcode

Do this: Skip Inbox, Delete it
[Verizon Samsung Galaxy S 4] sound-mind:
Snipped the image b/c it is huge.

OK so here is the deal. Yes kexec is possible in ME7. We have a kernel-level exploit for escalating privilege, not a userspace exploit. That means we can do whatever the hell we want in kernel space. We can load kexec.

I wrote a whole diatribe on the subject below but redacted it as it provided too much information WRT mitigations. Bottom-line is that in the face of a kernel-level exploit, with the current hardware and kernel, you can circumvent everything.
[Verizon Samsung Galaxy S 4] SamuriHL:
Let me be the first to point out something to everyone that should be obvious by now but I promise you it isn't. If a new update should come out before all this work comes to fruition, *DO NOT TAKE IT*. I can't stress this enough. People need to STOP taking OTA's blindly just cause it's new. Right now you have a kernel level priv escalation exploit....there is a good chance a new OTA would patch it. Which means anyone who takes any OTA that comes out is at risk of having it get patched with no downgrade capability.

TLDR: Stay the **** on ME7 until further notice!
[Verizon Samsung Galaxy S 4] my-blue-snog-box:
Here's to hoping the same can be said of MF1 on the I537.
[Verizon Samsung Galaxy S 4] sound-mind:
Hate replying to myself but one additional point here - the statement above has *nothing* to do with bootloaders, traditional custom recoveries, custom ROMs, etc. It only provides benefit once the first, cryptographically signed kernel shipped by Samsung, is loaded. Is this a big issue? Thankfully no, others have blazed the kexec trail for us :)

SS provides a great solution without relying on kexec. It facilitates customizations without a modified kernel. SS will likely be all most people ever need on ME7. Myself included.
[Verizon Samsung Galaxy S 4] lynyrd65:
I remember using bootstrap recovery on my old Motorola Defy to run CyanogenMod and MIUI. Will AOSP roms be possible with safe strap as well? I don't really see why not so long as the GS4 stock kernel is close to an AOSP kernel, which I think it is.
[Verizon Samsung Galaxy S 4] rebel1699:
I definitely agree that SS will be a great solution without relying on kexec. At the same time, utilizing kexec will assure all roms are compatible with SS. All aosp/non touchwiz kernels. I have used kexec kernels for almost a year now via multiboot on my Nexus 7, and has proven an invaluable tool. Imho, not using kexec would be pretty limiting, when compared to the mass advantage it would provide with very little effort of compiling a kernel with it included.

Those are just my personal outlooks. Whatever the final product is, or thereafter becomes, I will be extremely thankful for. Never look a gift horse in the mouth. :)

Just in case any readers are unsure of what all the kexec talk is about, here is a link to a great post by developer [MENTION=3418703]Tasssadar[/MENTION] with an informative explaination of what kexec is, and how it works.

http://xdaforums.com/showthread.php?p=36841808
[Verizon Samsung Galaxy S 4] DeadlySin9:
Read through this thread, specifically about kexec.
[Verizon Samsung Galaxy S 4] eskomo:
Questions like the one above has been answered 100 times in this thread. People don't look but ask anyways. This is my point. Its honestly why a lot of people stop paying attention to many threads. To many garbage posts to sift through.

Everyone asks of they can install a ROM that doesn't use a stock kernel. Most of these people are asking even though they read that only roms with stock kernels are supported. So why ask again? If you think something has changed then read and find out. If that changes it will be posted in the main post.

When in doubt, READ. And then READ some more. After that READ it all again.

To answer your question... Close is not the same is it? Any change in the stock kernel makes it different right? So its not stock anymore right? Its a custom kernel right? So no, any kernel that is not stock will not work until the Dev updates the rom with a stock kernel. This is how it is until hashcode or someone else figures out a exploit or something to allow it.

I'm really not trying to be mean here and I don't mean to pick on lynyrd65, just posts like this. But every thread dealing with the bootloader or recovery is just filled with either off topic nonsense useless posts or people asking the same question as someone 4 posts above. Its getting out of hand.
[Verizon Samsung Galaxy S 4] T3T3droid:
And posts like this are what get them shut down... Just saying...
[Verizon Samsung Galaxy S 4] eskomo:
Lol not so. I'm trying to help the situation. After talking to Kenny about this many times he has expressed concern with these posts as well. I'm pretty sure rule number one(1) in the forums rules sticky states "search before posting". My post didn't flame or troll and was not disrespectful.
[Verizon Samsung Galaxy S 4] rebel1699:
Agreed. Hoping a mod will clean the thread. The "WIP" in the title means "Work In Progress". People need to be considerate of Hashcode, as he should not have to put in extra work sorting junk posts from post containing legitimate info and questions, consistent to where the project is currently at in development. Besides that, most questions have been proactively answered in the op, and ensuing posts. Sometimes, the best way to show a dev appreciation, is to stay out of his way while he works.
[Verizon Samsung Galaxy S 4] T3T3droid:
I do understand that it's in the rules and I know you weren't being disrespectful, sorry if I made it seem that way... All I want to say is that I've been around for a while, not to long on xda but other sites as dev, and noob questions and nonsense always exist in every type of thread. The only threads with typical garbage in them that get shut down are the ones where people complain about the garbage (and on another note, the complains turn into the very same garbage) telling them to read doesn't stop them cause they DON'T READ YOUR POST lol it's a catch 22 and totally pointless... Sorry for the rant and sorry to hashcode on behalf of all the garbage... Thanks for everything hash!
[Verizon Samsung Galaxy S 4] lynyrd65:
I've looked back 8 pages and haven't found a definitive answer. Thank you for answering my question and explaining.

New builds will need to be modified to be able to work with the stock kernel.
[Verizon Samsung Galaxy S 4] ntowell:
How about quit whining about ppl asking questions. Either answer it or ignore it. Reading the same question 50x it's less annoying than reading someone complaining about ppl asking questions rather than reading through 40 pages of discussion. It's a thread, not a faq. Not everyone is a total nerd that sits around reading threads all day long. Ppl are always going to ask questions, so get over it. If you don't want to answer the question then don't, quit chastising ppl for not being as obsessive compulsive as you are about checking forums every 5 seconds. That it all, sorry for my whine.
[Verizon Samsung Galaxy S 4] rebel1699:
That, and/or the possibility of using kexec as a way to load other non stock kernels.

---------- Post added at 07:03 AM ---------- Previous post was at 06:58 AM ----------

Please refer to XDA Rule #1. It is there for a very good reason. You are correct, it is not an faq. It is a wip discussion, as labeled. Asking questions about the end result is like asking you what you'll be having for dinner next monday. ;)
[Verizon Samsung Galaxy S 4] ntowell:
Where's the rule about spanking ppl for asking questions? Wouldn't that actually be more off-topic?
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Can we please just drop this b4 thread gets locked and we dont get ss. Thanks:rolleyes::thumbup::beer:

S4 on a SAD ME7 Build
[Verizon Samsung Galaxy S 4] rebel1699:
[/COLOR]@sound-mind Since we have been throwing kexec around, and with the kernel exploit, has a kernel been compiled yet to test? Are you looking at regular kexec, or kexec-hardboot patch?
[Verizon Samsung Galaxy S 4] rushless:
Even in jest, no you would not.
[Verizon Samsung Galaxy S 4] sound-mind:
Yes I have compiled Samsung's opensource kernels for the i545, i337, and i9500 with Samsung's defconfigs. They all successfully boot with all hardware coming up. The only difference is exfat. The ME7 and other kernels were released before Samsung opensource'd the exfat code so they shipped that as a binary blob and it isn't in their kernel tree.

Hardboot seems to be out of the question. It requires a modified kernel in boot.img which is signed by Samsung.
[Verizon Samsung Galaxy S 4] rebel1699:
Thats some excellent news. I'm glad you mentioned the i337. That should keep all AT&T folks in the loop. Taasssadar also mentioned that he was able to remove the need for the guest kernel to be patched. That could really be handy in making virtually every compatible kernel useable with this setup, without kernel devs needing to do a thing. One less step.
[Verizon Samsung Galaxy S 4] Devo7v:
Any chance you could take a look at the i537, S4 Active, to make sure that works as well?
[Verizon Samsung Galaxy S 4] equake:
Not to hijack this thread but is there a kexec type of bypass being worked on alond with the SS?

My 2 cents.
[Verizon Samsung Galaxy S 4] Hashcode:
I'll get a new dev thread going soon.

And I'll see if we can continue this thread for discussion and keep the dev thread clean for folks to subscribe to.
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
Thanks if you need anything to be tested i dont mind doing it even if it bricks me as long as we get this up and running im in:good::laugh:
[Verizon Samsung Galaxy S 4] lazer9:
Thanks Hash! If you do make the dev thread as you suggested, could I pose an idea to keep it locked for only you to post updates, news, ect... in and as you said, keep this one for general and open discussions?

That way we could subscribe to your dev thread and only get the important and relevant posts we are so eager for from you. :good:
[Verizon Samsung Galaxy S 4] sppatel:
+1