yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] tanishq.dubey:
Let's all calm down for a minute...

Before we get too excited, can someone describe the similarities between the G3 and the newer S4 bootloaders? Basically, would it even be worth considering a port of some kind of this bootloader exploit to the S4, or should we continue on our path, perhaps waiting for Black Hat?
[Verizon Samsung Galaxy S 4] Brooklynsour:
Or not the newer boot loaders (mf3 mk2) I thought companies have different boot process? Also does the g3 have efuse chip/knox? The devs are probably looking it over now
[Verizon Samsung Galaxy S 4] tanishq.dubey:
Should have been clearer, by "newer" I meant to say past our last unlock-able bootloader.
[Verizon Samsung Galaxy S 4] ahmed.zubair:
If its working on galaxy s5 I think it might help us or even unlock the bootloader .. because its from the same manufacturer "Samsung" so there must b something common or clue for the dev's to unlock the bootloader but who knows what happens ..
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
Didnt they already confirm the exploit that Dan was going to show off at blackhat not effect samsung bootloaders?
[Verizon Samsung Galaxy S 4] tanishq.dubey:
I don't think it was confirmed, but there was a strong consensus that it was a Motorola exploit (I think Motorola). However, that did not rule out the possibility of it being applied to Samsung devices.
[Verizon Samsung Galaxy S 4] Surge1223:
depends ln whether its a qcom exploit or not and whether Samsung bootloaders have similar code. Its safer to assume that it wont work for now until they revel/post the unlock so we can see how they did it.

[MENTION=4630246]joshuabg[/MENTION]

Im not sure if thats it based on the date that patch was posted...hmm

Thanks though
[Verizon Samsung Galaxy S 4] sokrboot:
Post content deleted by author
[Verizon Samsung Galaxy S 4] jcase:
Where is this coming from, we didn't release for lg
[Verizon Samsung Galaxy S 4] sokrboot:
[MENTION=2376614]jcase[/MENTION] I stand corrected...Got my wires crossed. I've deleted my previous post's content.
[Verizon Samsung Galaxy S 4] jcase:
Several people have mentioned it so I'm just confused
[Verizon Samsung Galaxy S 4] Walter.White:
I think they are confusing with Sunshine (www.theroot.ninja)
[Verizon Samsung Galaxy S 4] eragon5779:
I believe it was [MENTION=2684188]autoprime[/MENTION], right?
[Verizon Samsung Galaxy S 4] autoprime:
wats working on g3 will not work for gs4/gs5.
[Verizon Samsung Galaxy S 4] Surge1223:
Oh I forgot that I used my razr to do some debugging, ignore the MSP430.
[Verizon Samsung Galaxy S 4] Fu5ion:
Thanks for clearing that up, saw that in the kernel info and had me confused haha
[Verizon Samsung Galaxy S 4] Mightycaptain:
[MENTION=4939386]Surge1223[/MENTION] might I make a suggestion, if you or anyone else for that matter stumbles across things of interest related to this topic whether previous exploits or just information about the various parts of the bootloader etc... To start including links in the op so everyone one can see what everyone is looking @. Google is your friend for sure but sometimes you got to know what to Google. Sounds like you might and a few others here. My 2 cents, worth less than one... Usually.

Edit I know you've done that already but reads like you and others have found additional sources since the beginning.
[Verizon Samsung Galaxy S 4] Surge1223:
Will do. Ill update the title as well, and make the current ideas we have/what were working on more clear in the OP. Thanks for your input.
[Verizon Samsung Galaxy S 4] D0CTOR:
I found the "MPRG8960.HEX file" you're looking for on a Chinese site, and after numerous faild attempts at downloading it I finally was succesful. I uploaded it here. You may also want to look at this site, as they're trying to do the same thing. I've also done some research on JTAG and found this site where you can purchase a JTAG box and the software to unbrick many phones, including ours.

I hope this may in some way help you out in your endeavour!
[Verizon Samsung Galaxy S 4] Mistertac:
Just want to say you guys are awesome... Wish I could help ya!!!

:what:
[Verizon Samsung Galaxy S 4] thunderbls:
Agreed, same here
[Verizon Samsung Galaxy S 4] D0CTOR:
I'm glad that I could be of some help Surge. I'll keep lQQking around for more info...
[Verizon Samsung Galaxy S 4] apompura:
Could you guys put this in to "stupid terms" like how close are you guys to finding a solution
[Verizon Samsung Galaxy S 4] kalestew:
Surge and a few other developers have found a few areas where there may be exploits but for now it seems pretty far out, but this thread shines light on the possibility of getting through to the bootloader.
[Verizon Samsung Galaxy S 4] jamesd1085:
No way to know...could be right on target for a bootloader exploit and or workaround...could also be miles off base...these are just ideas being set in motion...just cross your fingers and let the devs do what they do...we may never get unlock...but as long as even one determined dev is devoting time and energy then i refuse to give up hope!
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
I don't know if this will work for us but can we set enforcing back to permissive and be able to run like safestrap?

http://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing
[Verizon Samsung Galaxy S 4] Surge1223:
Yeah, sorry I've been meaning to, just so no one gets the wrong idea here, this is just a bunch of ideas, all of them with a low probability for success but hey you never know what you might learn. I have learned a lot since the OP, but in general I guess I haven't been updating it because I don't know how useful it would be. I also spend a lot of time reading other threads to see was done and what wasn't done. When I wrote the original thread I thought I did a pretty good job of linking to relevant threads and giving info about how to learn more about this stuff etc. Ill make a pretty big update, telling you what has been tried, what hasn't, and what the current ideas are, ill remove the other two zips and combine them into own with the updated or relevant files removed/added. Ill start updating it soon, might take me a while since I have to take/append some screenshots etc.

I sent Hash a pm with similar info. I figured he probably already knew, or was common knowledge in his experience. He didn't respond so I take it he already knows whats up with SELinux and trying to set it to permissive for longer than 5 minutes. Cant say ive honestly tried to find a method to get Safestrap to work though. Hashcode has a WIP dev thread for Safestrap so I think he'd probably appreciate it if people who could add to that posted there.
[Verizon Samsung Galaxy S 4] kalestew:
I'm just getting back into the game, and I would love to see exactly where you have been going with this. As for SDLinux my device is showing permissive, and has been for a while.
[Verizon Samsung Galaxy S 4] Surge1223:
Also, ill clean this up later, I just needed to post it temporarily. Essentially, I hard bricked this S4 to the point of no return. Send the the wrong flash programmer, wrote over the bootloaders, send everything I could find at it code wise, even blacklisted 05c6:9008 (Qualcomm Qdl high speed mode). Thought id try to see if I could figure more out about the gobi loader (Qualcomm's modem interface) and load firmware on to it. Well with a combination of usb_modeswitch, editing the gobi rules, sending the phone sbl1 as its flash programmer and more apparently its once again a Samsung phone, albeit a dead one.

I had to port some tools to busybox to see what was going on but if you're wondering what this has to do with unlocking the bootloader, well I need to be able to write a entire new partition table to this thing, plus I wanted to see how it responded..
[Verizon Samsung Galaxy S 4] hemirunner426:
Is the idea here such that, if you can write a new partition table, you can write the MDK/GPE bootloader to the new partition thereby giving us loki?
[Verizon Samsung Galaxy S 4] ncdub:
So, I just want to say thanks. I appreciate the time and effort you've personally put into this and I hope this is NOT where it ends! I have an MDK phone so I have all I want but this thing would be so much better with an unlocked bootloader!

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] Surge1223:
404 - Post not found!
[Verizon Samsung Galaxy S 4] dmt010:
If you take the link from the website you posted.. below

https://www.codeaurora.org/cgit/qui...cadbf8a72aabe6c7ff538ffa</a></li><li><a href=

and you strip the unicode off of the end (malformed url - %3C/a%3E%3C/li%3E%3Cli%3E%3Ca%20href=) you get this

https://www.codeaurora.org/cgit/qui...r&id=f39085971c8c4e36cadbf8a72aabe6c7ff538ffa
[Verizon Samsung Galaxy S 4] ryanbg:
While I know I should be skeptical Dan will release an exploit for Samsung, I don't see him releasing one for Motorola. Their flagship device can already be unlocked (save Verizon and AT&T) and Samsung has really utilized TrustZone beyond other OEMs. Hope for the best, expect the worst. I feel like Samsung would be a greater accomplishment than Motorola. However, any TZ exploit is commendable in its own right.
[Verizon Samsung Galaxy S 4] zeb carter:
I saw something this morning (Facebook I think) indicating that Samsung was considering dropping Knox in favor of Google's new security features in future editions of the OS. What this means for current devices & users, I have no idea. But what I hope is that Google will continue to lock down the OS with regard to OEM skins and by extension, the carriers.
[Verizon Samsung Galaxy S 4] RuggedHunter:
Somebody posted this to the developers discussion thread yesterday:

http://www.forbes.com/sites/bobegan...ixs-knox-the-android-security-saga-continues/
[Verizon Samsung Galaxy S 4] failedjedi:
Oh god that gives me such an Android boner. For what its worth knox wasn't about to win over the government. I'm sure each agency is different, but maybe not if they fall under department of defense, but I know 2 people in 2 different federal law enforcement agencies that have been given government iphones since the 4S.

A new approved security standard isn't enough to break through established government bureaucracy. They have their setup and do things their way, and it doesn't matter how much tech changes, they won't change on a large scale until they absolutely have to.

Samsungs mistake was thinking they could get the government and businesses to switch. Places that finally gave up blackberry had to make a switch, they arent going to do it again because samsung might have something better. Look how many corporate PC's are on XP still. New tech doesn't matter. Companies won't put in effort to change unless they have to or it offers a financial benefit.
[Verizon Samsung Galaxy S 4] tech_head:
KNOX may have a crappy adoption rate for MDM (mobile device management) but, the NSA and DOD have approved KNOX devices for everything except "TOP Secret" communication.

The Samsung bootloader is signed with SHA256 which was co-developed by the U.S. Government.

If Google's security is not the same or better, look for Samsung to continue to provide SHA256 bootloaders for their devices.

KNOX is secondary.
[Verizon Samsung Galaxy S 4] scryan:
Why on earth would google deciding to include their own version of knox in all future versions of the OS giving you and Android boner?

And as Tech said, Maybe now on we just see the current security with a second layer of googles security to prevent us from modding out phones. that gives me a full on Android soft-off.
[Verizon Samsung Galaxy S 4] joefrog1996:
True, but if the security is the same for all devices then unlocking the bootloader for one device will unlock it for all. All devs on XDA will be working on it instead of one team of devs pre phone. Plus there's a better chance of a leak that benefits all devices that comes straight from inside google.
[Verizon Samsung Galaxy S 4] dmt010:
Maybe Google will provide a web interface that will allow us to opt out if we don't want the added layer of security which will hopefully remove the govt garbage from our devices

Sent from a piece of **** Samsung KNOX phone
[Verizon Samsung Galaxy S 4] MorrisC2010:
Seems as though KNOX isn't dead http://www.androidauthority.com/samsung-knox-still-alive-403590/
[Verizon Samsung Galaxy S 4] nes4r2:
Had to replace my phones PCB :( came with NC5, dang it. Safestrap is a life saver but man gonna miss those aosp . Gonna donate to the bounty.
[Verizon Samsung Galaxy S 4] thesoldier:
I have a big WiFi issue and I've thought about getting the phone replaced but I can't...just can't give up MDK!
[Verizon Samsung Galaxy S 4] ahmed.zubair:
Its been a year but no success.. Gonna sell this ****in crap... its now frustrating.. :crying::crying::crying::crying::crying: Btw i want to know what is KNOX warranty void 0x1 something like it ..?
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
I don't blame you. I've been considering it myself but im going to wait for blackhat. KNOX warranty void would be 0x1 instead of 0x0. It basically means you tampered with your phone and Samsung/Verizon will know that forever.
[Verizon Samsung Galaxy S 4] ahmed.zubair:
Then I will wait also ... I have read that if knox warranty void triggers than we can flash customs recoveries also ?
[Verizon Samsung Galaxy S 4] Mistertac:
This isn't really the thread for all this but yes. I'm assuming you have an i9505??? If your Knox is already tripped then have at it... Flash a custom recovery
[Verizon Samsung Galaxy S 4] ahmed.zubair:
I am on i545 .. I just want to knw.
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
Wait what? I didn't know that. If you trip the Knox counter you are allowed to flash custom recoveries? Does this apply to the I545?
[Verizon Samsung Galaxy S 4] ahmed.zubair:
Thats for I9505 .. You can also google it .. i dont remember the link u wil get the information easily...
[Verizon Samsung Galaxy S 4] DeadlySin9:
There's no way to put custom recovery on locked variants past 4.2.2. The Knox thing is simply this: unlocked variants with a Knox bootloader can flash a custom recovery if they don't care about voiding the Knox warranty.

Sent from my SGH-I337 running GPE
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
Stopped at the local Verizon wireless to buy my father a GS5. Took a look at the GS4s and they are all still on MDK. Oh the pain.
[Verizon Samsung Galaxy S 4] k1mu:
No. The 9500 doesn't have a locked bootloader, but if you flash a custom kernel/recovery it will set the Knox Warranty Void flag.
[Verizon Samsung Galaxy S 4] Brooklynsour:
Guys I'm sorry for my nubness I think ryan or somebody mentioned something about safe mode? I was curious to what its for cuz my phone somehow booted into safe mood screen started flickering....
[Verizon Samsung Galaxy S 4] decaturbob:
not the place to post this....why we have a Q&A forum

you should try to pay attention to each forum posting rules.....and you can get answers more quickly ...also thanks for the PMs.....I'm sure the mods will appreciate what you sent me
[Verizon Samsung Galaxy S 4] Addiso:
Edit: take to pm please.
[Verizon Samsung Galaxy S 4] JLow0214:
What kind of condition is it in? I currently have an MJ7 S4. PM me

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] Blue:
I am. How will we do this trade? I have a NC5 32Gb s4.
[Verizon Samsung Galaxy S 4] Walter.White:
I sure hope you are right man.. It's been painful to say the least. Good thing is we don't have to wait much longer to find out :)
[Verizon Samsung Galaxy S 4] F1a5hP01ntX:
[MENTION=4939386]Surge1223[/MENTION] What were the changes in the bootloaders between mi1 and mk2? I'm trying to decide if i should update or not. Also wondering, what ida loader are you using to look at them?
[Verizon Samsung Galaxy S 4] poppers162:
http://xdaforums.com/showthread.php?t=2815591

Don't know if this applies to the s4 but still.

We're currently researching, so if anything new comes up, we'll test and release.

Sent from my Unlocked SCH-I535 running AOKP
[Verizon Samsung Galaxy S 4] Surge1223:
Quite a bit, I didnt ever really look at MI1 though. Its up to you if you want to upgrade, I did but only because I know I'm one of the only ones looking at the bootloaders so I dont have that

fear that someone may unlock the bootloader on a previous build. I used parts of cycad's and Ralekdev's ida loaders and wrote my own that incorporates parts of their loaders as well as additional features/definitions/functions I thought I might find useful. I cant post it because its commented with my curse filled rants, also I named it in such a way too (Qualcomm ******* sucks **** mbn/sbl loader).

I explored this option early on. I talked to bliss about it as well, he didnt seem optimistic about the possibility of using the trustzone to unlock the bootloader on Samsung devices (then again his upcoming talk suggests otherwise). I didnt read the entirety of the thread you linked but from a glance over I dont see any analysis of the trustzone or code in the trustzone that makes you guys believe that this is a viable route?
[Verizon Samsung Galaxy S 4] poppers162:
I do not want to get any hopes up or anything, and it's just me and an educated friend snooping around the files, and we noticed a file, install-recovery.sh. Well he noticed it. He's thinking that the file is ran before aboot and if we could modify it in a way, that it can push a custom kernel or something before aboot does its thing. But we are jist beginners trying to help.

Sent from my Unlocked SCH-I535 running AOKP
[Verizon Samsung Galaxy S 4] SamuriHL:
It's not run before aboot.
[Verizon Samsung Galaxy S 4] poppers162:
Darn. We're still optimistic about djrbliss's method possibly working for the s3. It's worth snooping around.

Sent from my Unlocked SCH-I535 running AOKP
[Verizon Samsung Galaxy S 4] LiLPurP:
So guys, not sure if this makes a difference, but the galaxy s3 apparently has kexec support now

http://www.droidforums.net/threads/...proof-of-concept-for-vzw-galaxy-s-iii.215992/

AT&T Galaxy S4 4.3 MK2 rooted with saferoot, safestrap recovery installed, Running Hyperdrive ROM, Praying for unlocked bootloader lol

EDIT:THE DATE ON GOOGLE WAS DIFFERENT THAN THE ACTUAL DATE, SORRY GUYS
[Verizon Samsung Galaxy S 4] tanishq.dubey:
Curiosity got the best of me...

With just a couple days until Blackhat USA, and about a week until Dan's TZ exploit talk, I was curious as to if we have currently halted progress, on our side, at least, on the bootloader unlock in order to see what Dan has in store for us (I find this situation to be perfectly acceptable). In addition, I haven't really seen any truly development based posts in here for a while, is it possible to get a status update for where we are at? If secrecy, lack of time, or something of that sort are the matter, I understand. I guess that after seeing this thread get pretty stagnant after a while, curiosity got the best of me and I just wanted to read something technical...

Side note: Do any devs know of good resources to learn the technical aspects of bootloaders? It does not have to be a newbie tutorial or something, I know how to program in multiple languages, but have found it difficult to find resources that introduce more hardware/software aspects of programming.
[Verizon Samsung Galaxy S 4] windstrings:
https://archive.org/details/ShmooCon2014_Arms_Race...Bootloaders
[Verizon Samsung Galaxy S 4] Surge1223:
There are no good sources, just scraps you can find on the internet before Qualcomm removes them via threatening to sue ungodly amounts, that's why we have to reverse engineer.

Good vid.
[Verizon Samsung Galaxy S 4] LiLPurP:
Ok guys, i have decided to go tomarrow and buy the htc one m8 from att, i will be giving the att gs4 to my girlfriend, so i will still be watching, and here to contribute in any way, btw i noticed that the htc one m8 on verizon, is acctually locked down tight, does att version share the same fate? Ik its unrelated sorry, but just wondering before i do anything as thats what put me in the locked bootloader pool the first time

AT&T Galaxy S4 4.3 MK2 rooted with saferoot, safestrap recovery installed, Running Hyperdrive ROM, Praying for unlocked bootloader lol
[Verizon Samsung Galaxy S 4] windstrings:
I think AT&T and Verizon are the two areas that people have the most trouble with locked bootloaders probably not good news.
[Verizon Samsung Galaxy S 4] failedjedi:
I was also thinking about the m8 and from just a quick search in the att m8 section here on xda it looks like it's fairly easy to unlock and get a custom recovery on.
[Verizon Samsung Galaxy S 4] DeadlySin9:
At this point it's already certain that ATT & VZW will keep to locked bootloaders. The only hope for us, besides threads like this, are the hardware companies allowing unlocks or not restricting as much with the bootloader. HTC likes to let people have their phone free, don't know if any other manufacturers put out unlocks.

Sent from my SGH-I337 running GPE
[Verizon Samsung Galaxy S 4] windstrings:
I have the vrzn s4 and my phone is lightning fast and totally stable, do you think I'm really missing anything by having a locked bootloader?
[Verizon Samsung Galaxy S 4] jackassxl101:
I am in the same boat windstrings. Coming from an unlocked galaxy nexus I love how fast it is but all the extra bull**** and not being able to use custom rooms really makes me sad. Using community based roms that have been tweaked to give your phone better everything is really something I miss.
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
with a unlocked bootloader, your phone has so much more potential.
[Verizon Samsung Galaxy S 4] windstrings:
I

Seems many roms have their own bugs... Just didn't know if it was overrated hype or just the challenge or of real benefit.

I do love a stable system! Especially if it's fast!

I understand the security of ROMs.. Someone else does all the weeding out and hands you the finished product.

Nothing like a virgin system..

But sometimes you can take a slut and clean her up and she performs rock STEADY and faithful ! ?

---------- Post added at 03:26 PM ---------- Previous post was at 03:21 PM ----------

I ask one question your too stupid to answer and I'm a troll?

Really?... Who's the troll?

Who are you with your bad 21 posts to date? Wet behind the ears?
[Verizon Samsung Galaxy S 4] KaratemanTJ:
Well, first of all, I must applaud you for so maturely calling me stupid. (P.S. It's spelled "you're".)

Second, I apologize if I misunderstood the tone of your initial question. I took it to be sarcastic, which given your response, I feel fairly justified in doing. Given that it was apparently a serious question, I'll try to respond appropriately. Also, as this is a thread dedicated to working toward unlocking the bootloader, your question would probably be better suited to the Q & A forum.

The main advantage of having an unlocked bootloader is the ability to use a different kernel. With safestrap, you can use a different ROM, but it has to be based on the stock kernel or it won't work. If you wanted to use for example, CyanogenMod, you'd have to run the CM kernel which you can't without an unlocked bootloader. Once you have an unlocked bootloader you can flash whatever you want. You can even take the source from a kernel you like, modify it and build your own to suit your needs. It's basically about the freedom to do what you want with your hardware.

Hope that helps.
[Verizon Samsung Galaxy S 4] eragon5779:
Or KEXEC. That would allow custom Roms too
[Verizon Samsung Galaxy S 4] mikeneff2006:
Does any one know what day Dans brief of reflecting on the trust zone happen on at black hat?
[Verizon Samsung Galaxy S 4] decemberchild:
I'd post a link, but I can't.

Wednesday, August 6 at 3:30-4:30. I believe that is Pacific time.
[Verizon Samsung Galaxy S 4] NighthawkXL:
August 6th, 15:30 - 16:30. So three days from now.
[Verizon Samsung Galaxy S 4] DeadlySin9:
The 6th, at 15:30 PDT. I'm not counting on that being our device but maybe someone who sees it can gather some good information.

Sent from my SGH-I337 running GPE
[Verizon Samsung Galaxy S 4] SamuriHL:
There's also no guarantee that he releases whatever it is he ends up demo'ing.