yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Samsung love:
haha thats true :D we hope so much ^-^
[Verizon Samsung Galaxy S 4] pr3dicament:
Developers never get the real recognition they deserve. I know this is a Verizon thread, but I'm only posting simply because AT&T is the other carrier with this locked boot loader crap. Stop trying to piss them off. Don't aggravate the hand that feeds you.. and hell they might never even bother posting it simply because of other morons want to take their code and run with it. i.e. Xposed for Lollipop, that was one hell of a soap opera.

This is pretty much the only place to find anything worth reading when it comes to modding/flashing phones and tablets. My phone, my tablets, all useless without root access and even more useless if stuck with the Touchwiz kernel. Hell, the latest version for AT&T is 5.0.1 (TouchWiz, and honestly it doesn't really work very well---Marshmallow is the bomb if you have MDL. I did.. then recently I renamed a rom that was able to use the loki patch, so to speak, and the other one was renamed.. just a freak accident and so another S4 of mine is locked up) and they aren't releasing anything further.. AT&T S4 users will not receive MarshMallow or even a slight OS version differential (5.0.x to 5.1.x--Closest thing is Albe's rom for version 5.1.1--based on Touchwiz, can flash in safestrap.. i think that's for AT&T) Could technically buy some blanks and solder them on, take a dump from 4.2 or the 4.4.2 MDL and go from there. I'm not a developer on HERE, don't get me wrong.. I did run into an interesting thread though.. and I've been reading about ways around this for weeks.. and I'm failing :) I never saw this thread until tonight, and that's only because I am on AT&T. I saw this and thought maybe the developers have not come across it or maybe to give it more attention? And sorry for the novel.. I just.. hell, I'm just aggravated with all of this ignorance and no recognition and near constant questions that will be answered in due time. The thread I mentioned:

http://xdaforums.com/redmi-note-3/how-to/modified-emmc-file-unlocking-bootloader-t3358486

Probably nothing unless you get a blank.. I don't know. If that's already known, then I do apologize.

Thank you to all of the developers that spend so much time on stuff that people never appreciate. Please know that I do.
[Verizon Samsung Galaxy S 4] hisham2630:
what about knox

if someone can decompile knox.

maybe you will find a something helpful as the knox have a flag in bootloader.
[Verizon Samsung Galaxy S 4] doubleaykay:
Not going to help. We've pretty much established that kexec is our best option unless a Toshiba CID exploit is discovered.
[Verizon Samsung Galaxy S 4] hisham2630:
loki and the new aboot.

did someone compare between the dan loki and the new aboot.

to see what is the differences.

now when i enter the download mode on my sch-i545 on nc5 bootloader.

i didn't see the knox flag.strange?
[Verizon Samsung Galaxy S 4] doubleaykay:
We know what exploit Loki uses. It was patched a long time ago, and this patch is still present. We cannot downgrade to a lower version that does not have this patch as rollback prevention is enabled. Basically, Loki will NOT work.
[Verizon Samsung Galaxy S 4] hisham2630:
i know its won't work,but if we have a look on the new lines.
[Verizon Samsung Galaxy S 4] doubleaykay:
We have already looked. Everything has been significantly hardened up in terms of security. There is no way we would be about to bypass that on a software or hardware level. There are certain things we can do, though: use kexec to spawn a new kernel in after checks are complete, or use a CID exploit to change the identity of our eMMC to allow for the flashing of a developer aboot. Both of these methods are being investigated right now. You will know when either of these comes to light.
[Verizon Samsung Galaxy S 4] cicuye:
Need instructs to flash MDK build

Are there any instructions with the necessary downloads to flash a custom recovery and install a rom on the SCH-i545 with a build ending in MDK? I checked on a used one and found that build. I would dearly love to get around that locked boot loader. I have an S4 with an OF1 build and I cannot get past it. Hell, I can't even get Flash Fire to work. It says Are you rooted? (I am) and are you running super su or cm su... Is it possible to flash over that MDK build? Seems like i saw it in here somewhere. I would greatly appreciate someone pointing me in the right direction. Sorry for the ignorance of the issues, I sure don't mean to waste anyone's time. Just a semi high tech redneck from Austin trying to learn new things. Any takers?
[Verizon Samsung Galaxy S 4] jam0688:
If you do not have a mdk version of the s4 there is no way to flash a mdk version. Especially not on OF1. So if that's what you're wanting the I'd suggest getting that mdk version s4 or wait it out like the rest of us in hopes that they can find us at least some solution to boot CM at least.
[Verizon Samsung Galaxy S 4] tshelby73:
Can't believe anyone still on this phone as its its locked down has security holes due to it not being supported by Samsung anymore. Bootloader or kexec is pretty much a pipe dream. I still have mine only because it has a slightly separated screen in corner and is not worth selling as it isn't worth anything.
[Verizon Samsung Galaxy S 4] Matthew M.:
How about we keep the comments in a developer thread serious. If you want to be negative go somewhere else.
[Verizon Samsung Galaxy S 4] Sonichedgehog360:
Just curious. pr3dicament mentioned that developers never receive their due recognition. I agree with this sentiment. Which developers are working on this? If so, can I have their PayPal emails? A time ago, I donated anonymously to stang5litre. I would not mind doing the same to the developer(s) who have invested their time and energy into this already. Freeware shouldn't be greedware, folks! Let's show some real appreciation!
[Verizon Samsung Galaxy S 4] bg260:
A Captain never abandons ship.
[Verizon Samsung Galaxy S 4] elluciovpe:
I bought this phone a while ago without knowing how restricted it was (don't ask, I'm just stupid) and have been watching the whole bootloader unlock scene from the outside. I would gladly donate to the awesome guys working behind this. Also, I take this opportunity to thank everyone who is involved here. I can't wait for the day when we can finally slap Verizon on the face.
[Verizon Samsung Galaxy S 4] XxD34THxX:
AFAIK, all devs have stopped working on unlocking this device...

And I have it for another year and a half...
[Verizon Samsung Galaxy S 4] rp1226:
FYI.

Check out [MENTION=7459177]laginimaineb[/MENTION]'s Tweet: https://twitter.com/laginimaineb/status/737051964857561093?s=09

Just managed to extract the Qualcomm KeyMaster keys directly from TrustZone! Writeup coming soon :) (1/2) https://t.co/WKdSfPkRvN
[Verizon Samsung Galaxy S 4] doubleaykay:
iirc TrustZone is an issue for us... I believe this satisfies the very rare scenario of getting a leaked/cracked/extracted signing key. Correct me if I'm wrong.
[Verizon Samsung Galaxy S 4] Surge1223:
Even though this is mostly true, it should be noted that when this thread started a few years ago, neither [MENTION=766721]ryanbg[/MENTION] were actually that knowledgeable. Time went on we realized we had a similar interest and decided to investigate. Along the way we both learned quite a bit. This thread serves as a place where people can chat about the bootloader without having to deal with people on newer devices trolling asking for this and that. It's like a hidden bootloader chat lol.

Anyways, even if i don't post anything here that often anymore, I still regularly update the ida mbn/sbl loader on git, so people can still see the bootloader for themselves that way, and I often use the s4 aboot as a test when testing changes to the loader.

Im sure lots of up and coming devs make a pit stop here now and again, if only because this thread is one of the only 3yr + active bootloader chats and so prob appears somewhat regularly in search results.

TL;DR keep posting bootloader related questions and posts here and maybe it will help someone as much as it's helped us.
[Verizon Samsung Galaxy S 4] doubleaykay:
Any confirmation on whether those TrustZone keys will be of any help? I assume since they're KeyMaster they may apply to all phones, or at the very least the method used could apply to get our unique keys.
[Verizon Samsung Galaxy S 4] XxD34THxX:
Pretty sure it was said that that was of no help
[Verizon Samsung Galaxy S 4] k1mu:
This is on MK2 on the Verizon I545? If so, very impressive if your modifications are to the module code.
[Verizon Samsung Galaxy S 4] jeboo:
I just posted it over in ATT forum, but it supports vzw mj7/mk2 as well!

http://xdaforums.com/showthread.php?t=2578566
[Verizon Samsung Galaxy S 4] k1mu:
Superb - that's exactly what I've been playing with - it's interesting that the module loader isn't integrity checked. :)

I've been too nervous about doing this and triggering Knox, so thanks for trying it.
[Verizon Samsung Galaxy S 4] jamesd1085:
By any chance was the Loki bypass a module in the mdk kernel...if so could we edit it to work on mj7\mk2 and get that workaround usable again...I'm no dev...lol...just picking your brains a bit
[Verizon Samsung Galaxy S 4] MehStrongBadMeh:
No, Loki was an exploit to the bootloader, which is better than this. But, we'll take what we can get. This exploit will allow Hashcode to implement Kexec into SafeStrap, allowing us to use SS with roms using any kernel. That means, once implemented, things like AOSP roms, 4.4+ roms, etc. can all be flashed using SS. It may not be an unlocked bootloader or loki, but at least we will have enough control to use whatever rom, kernel, modem and Android version we please.

EDIT: Hats off to jeboo and co. for putting in the hard work to make this happen.
[Verizon Samsung Galaxy S 4] jamesd1085:
Awesome news nonetheless!...great job guys!
[Verizon Samsung Galaxy S 4] camparks:
FYI - for those that didn't go over to jeboo's thread, it's on Hashcode's radar. No unlock, but hopefully will lead toward KEXEC exploit in SafeStrap so we can flash custom kernels and ROMS like those on MDK with LOKI!

Been watching this thread since it's start. Would just like to say thanks to ask those keeping this push going. Special thanks to Surge - you've contributed a lot to the community since joining this fall.

Sent from my SafeStrap enabled Hyperdriven S4
[Verizon Samsung Galaxy S 4] Fu5ion:
I sold my S4 to pick up an HTC one a couple of days ago (a couple of reasons for that, not just the bootlaoder, although that was among them) But I'm going to continue looking into working on this s4 boot loader haha. Surge, expect a PM from me soon to get caught up on where you are again. The people in this forum were great, so I'd like to stick around and help if I can.
[Verizon Samsung Galaxy S 4] k1mu:
Here's another example of what we can do using that exploit.

The I545 for MJ7 and MK2 are compiled with "CONFIG_ALWAYS_ENFORCE" defined, which means that the system starts up with SELinux in enforcing mode, and ignores attempts to downgrade it to permissive.

The program at https://github.com/k1mu/selinuxoff allows you to place SELinux into permissive mode again.

It doesn't need root for the I545. It needs root on other devices, but the right kernel address can be added for those so non-root can do this.

Disabling SELinux only works until you reboot, of course.
[Verizon Samsung Galaxy S 4] jamesd1085:
What can be achieved while set to permissive that cannot while enforcing?
[Verizon Samsung Galaxy S 4] JLow0214:
So I was reading about the Motorola trustzone boot loader unloader unlock and don't we have the msm8960 chip in our phones??? If so we might to see about unlocking boot loader in the same manner

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] jamesd1085:
I believe trust zones are carrier specific not board\chipset specific...but if tz are both Verizon it could be possible...don't hold me to it though
[Verizon Samsung Galaxy S 4] k1mu:
Among other things, restoring using Titanium Backup.
[Verizon Samsung Galaxy S 4] Mistertac:
That would be nice

Oh well it made it me clean up my play store history of something like 350 apps and other things I didn't need at all.
[Verizon Samsung Galaxy S 4] Bloodcrav:
If I recall correctly. Samsung blew a fuse to prevent the Motorola exploit. I'm sure djbliss looked into this before he took the Loki route.
[Verizon Samsung Galaxy S 4] :
Good thing I have extras. ;)
[Verizon Samsung Galaxy S 4] Bloodcrav:
Hahaha!
[Verizon Samsung Galaxy S 4] ryanbg:
It'd be nice if we could spoof those attestation servers...

(Samsung AttestationCA cert1) prob not possible though
[Verizon Samsung Galaxy S 4] Samsung love:
and i have it for the rest of my life lol xp
[Verizon Samsung Galaxy S 4] cicuye:
I was able to locate a Verizon Galaxy S4 with an MDK build. It's in good shape, running a 4.2.2 OS version, JDQ39I545VRUAMDK build, 3.4 0-562219 Kernel dated Apr 29, 2013. Then, the SE Linux status is set to Permissive, Hardware version I545-06. It was a demo model in a Verizon store (how appropriate)! Issues: Demo messages Verizon and Samsung would play every so often and it wouldn't allow you to turn those and the power off. All of this was fixed by rooting and downloading Titanium Manager, locating the appropriate files and freezing them. Also I have an issue with maintaining root. I use Kingroot and Kingo but when Superuser Sume Pro uninstalls either of them the root goes away. I'd like to download a Cyanogen Mod and take it up to Marshmallow but I'm proceeding with caution, gathering information. I believe I've got a good opportunity here and don't want to screw it up. I still consider myself a noobie to all of this.

I started learning on a Sprint S2 throwaway phone and have been able to do wondrous (to me) things with it- root, launchers and roms. It is absolutely wonderful to me to be able to actually take control of my property, what a concept.

If I can be any assistance to anyone on here, let me know. I was thinking there might be some build information that could prove useful to someone. It's basically been sitting in a box in the backroom of the store and seldom touched. And if anyone has some suggestions about recovery and rom installation with instructions I would be eternally grateful. Also, my older S4 with an OF1 build has finally hard bricked and I'm encountering difficulties getting it cranked up again. I have the Verizon Update/Repair tool which has proved very useful. However this time my laptop won't recognize the phone so I can't get it to connect in order to initiate the repair sequence. Any advice?
[Verizon Samsung Galaxy S 4] iwearthebelt:
Hey if you're looking to run CM13 on that S4 I can tell you that it runs great. I have the latest nightly installed and am using TWRP recovery 3.0.2.0. If you have any questions just message me and I'll help you out.
[Verizon Samsung Galaxy S 4] bg260:
I couldn't have chosen a better device to cut my teeth on. I have learned a lot in a short time. I'm glad I took my kicks first. Most other devices are a snap now. You don't have to run CM or Xposed to get the most out of your device.
[Verizon Samsung Galaxy S 4] Atomicmuffin:
A VZW SGS4 that is still on MDK is a golden nugget in a sea of turds. I'd be cautious, especially around stock odin tars. If you want to keep your bootloaders lock-free, any type of flashing which even thinks about messing with any of the main bootloaders (SBL1, SBL2, SBL3, and

especially

ABOOT) should be avoided like the plague.

Though Most zip-flash based roms (assuming compatibility) generally only mess with the system and perhaps kernel, so as long as you stay vigilant. And anytime you need to Odin-flash something, make absolutely sure you know what you're flashing beforehand.

As of late, most of my spare tinkering time has been spent attempting to gain root on my VZW SGS6-E, but I haven't given up on this device. Unfortunately, BL-unlocking and the investigation thereof tend to be quite the time sink, as well as outside my typical comfort bubble skill-wise. But so long as there's life in my S4, I'll keep grinding the axe. Time-permitting, of course.
[Verizon Samsung Galaxy S 4] killer5000:
This might help to unlock the bootloader

http://bits-please.blogspot.com/2016/04/exploring-qualcomms-secure-execution.html?m=1#more
[Verizon Samsung Galaxy S 4] sokrboot:
Already discussed and determined not to be what we need, but way to keep your eyes peeled. [emoji106]
[Verizon Samsung Galaxy S 4] killer5000:
There was some talk about the guy releasing your way to unlock a bootloader that way. Not sure when he's releasing it
[Verizon Samsung Galaxy S 4] cicuye:
My S4 with the MKD build updated and didn't prompt me before it did it, those jack booted Nazi Verizon thugs! Way upset. How about an S4 with a Nk1 build. What could I do with it? Or an S3 with an NE1 build? Thanks for your input
[Verizon Samsung Galaxy S 4] pharmaceutiKILL:
OH7?

Anyway to get custom roms on build PPVRUAOH7? There is almost 300 pages in this thread and i didnt feel like searching for my answer. I am unsure if my versions bootloader is possible to unlock. Unlikely im assuming.

I am rooted using kingroot... and that is about all i have done as im sure the bootloader is locked. i havent tried to flash any recovery. Is there any way to do this? or do i have one of these dreaded unROMable s4s? also im on 5.0.1..

hope im not bothering anyone!

---------- Post added at 04:11 PM ---------- Previous post was at 03:55 PM ----------

Ok so i also just read that the developers edition's bootloader comes unlocked by default....i do have the developer options in my settings...does this mean the bootloader is unlocked?? i though most phones had the hidden dev options.
[Verizon Samsung Galaxy S 4] sokrboot:
On Verizon S4 the only firmware that has bootloader unlock is MDK (was actually a bypass I think, not an unlock), so your OH7 bootloader is locked and cannot be unlocked.

Also, the presence of "developer options" on your phone does not mean it is a developer edition phone.

---------- Post added at 12:46 PM ---------- Previous post was at 12:42 PM ----------

Maybe I should clarify my previous post...that vuln will not help us unlock VZW S4 bootloader. Certainly it may help other devices.
[Verizon Samsung Galaxy S 4] ryanbg:
He's lying to you.
[Verizon Samsung Galaxy S 4] JoshwaDroid:
our Last option??

I were watching a lot time this thread and hopes come and go away fastly... but everyday we notice devices with high security systems being hacked and tricked but still there are a bunch of devices with bootloader locked as verizon versions of some devices included this one. But I think why dont contact ex devs from verizon or toshiba for Cid??

Because that could be our last option, try to contact ex devs form those companies and see if they reveals the right codes. Its hard expect for positive answers but its a try.
[Verizon Samsung Galaxy S 4] Surge1223:
If you're referring the the guys that unlocked the s5, n4, n3 and others, then you're looking for the guy right above you (hint: it's not god)

As for Verizon devs, they have no interest in helping and would never sacrifice good paying jobs for something that does nothing for them. That's not to say someone working for one of the companies hasn't helped before, but usually you don't seek them out, they find you.
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
This might not help but would any of these files from a near identical S4 help us in any way:

http://xdaforums.com/showpost.php?p=66880587&postcount=64
[Verizon Samsung Galaxy S 4] XxD34THxX:
nope. Still have physical fuses blocking that flash.
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
I had a feeling that was the case myself.
[Verizon Samsung Galaxy S 4] wolfen1086:
Yall have no idea how bad I want to unlock my bootloader, I'm currently on 5.0.1 with Kingroot. I wanna run TWRP so bad it hurts, but alas I'm stuck with the stock recovery.
[Verizon Samsung Galaxy S 4] cicuye:
Verizon Sucks

Verizon is a bunch of jack booted Nazi thugs!!!
[Verizon Samsung Galaxy S 4] cicuye:
Just located and bought a Verizon S4 with that MDK build. I hear that the best way to work on this is to not use Odin because it might return to stock and lock that boot loader. Also that the best recovery to install is Twrp which I have not used yet. I have a Sprint S2 unit (basically a throw away) that I've been learning on. I guess I'll fire that up and start experimenting till that new (to me) S4 arrives. If anyone would be kind enough to send me some advice/input, I would greatly appreciate it. It's really been interesting to follow this thread, see the net working and effort put in by the community that contributes to this site. I admire you all very much, a lot of this is way over my head. But I enjoy learning new things and have developed an affinity for these Galaxy S4's. I have to use Verizon because my work takes me out to West, South Texas and there's that coverage issue. I sure don't want to lose my cell signal and data when I'm crossing over or near the border line. I wish everyone the very best in all your endeavors. Thanks for the assist.
[Verizon Samsung Galaxy S 4] kevinco1:
Wasn't this same exact message posted here or possibly the general S4 thread a few weeks back? Then a short time later through some flashing missteps the phone had been loaded with the latest firmware and became locked. Well hopefully you were able to work things out. I
[Verizon Samsung Galaxy S 4] wolfen1086:
mines locked, never had it plugged into odin it was an ota update that did it, it IS rooted, still running stock launcher and stuff but I do have a few things, only thing it to keep from losing everything I use titanium backup and put the files on the computer just in case
[Verizon Samsung Galaxy S 4] cicuye:
Yeah guys I have to admit that the other S4 with the MDK build did update. It soft bricked while I was working with it. I hooked it up to a Verizon Repair utility that I have in order to remedy the situation. Unbeknownst to me, it updated during the repair process. I was really hacked off about that. Verizon does not want you to take control of your own property. I caught the thing updating once and I know it didn't prompt me to okay it. I ended up putting the Albe 95 Port S6 rom on that one with Flash Fire, so it wasn't a total loss. I just need to do a better job with Titanium back up of locating and freezing that update file in the system. I told you I was a noob at this and a lot of it was over my head. The first step to learn something is to recognize and admit that you don't know everything and then start the learning process.
[Verizon Samsung Galaxy S 4] cicuye:
The S4 I received had been updated so I booted it up to find the dreaded OF1 build. I'm returning it and will hang on to the input you were kind enough to offer. Many thanks, Kemosabe! I'm going to keep looking for that coveted unlocked MDK build. I've begun developing a few sources that may be useful.

What about shifting to S3? Is it any more developer friendly? I'm going to jump on that thread and pursue it. They're cheaper and real close to having the S4 specs and capabilities. I have one coming with an NE1 build, know of any possibilities with that model? It's running an Android 4.4.2 operating system. I appreciate your input.