yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 General] SysAdmNj:
After reading adamoutler's thread, is it just me or is his thread contradicting this thread? Is this device unlocked or not??
[AT&T Samsung Galaxy S 4 General] spenserj87:
Great news, I actually like having the stock version of the S4 for a while before putting on a custom ROM. It makes the reward that much greater. I love the S4. Kudos for making us aware of the success and for being thoughtful and deliberate in how it is released. I'm happy to be patient.
[AT&T Samsung Galaxy S 4 General] Sushibagel:
I don't understand a lot of the jargon being used in that thread. But from my understanding they are looking for a lower level hack just in case the exploit djrbliss used gets patched at some point.
[AT&T Samsung Galaxy S 4 General] noahthedominator:
US cellular GS4

What forum do we use for the US cellular version of the GS4 sorry if its already been answered.
[AT&T Samsung Galaxy S 4 General] djrbliss:
I'd like to remind everyone that none of you know any of the technical details involved in this hack, so anything anyone says is pure speculation.

That being said, there is essentially nothing (short of replacing physical components in the phone) that can be done to make it permanently unlocked if you insist on installing an OTA update. Even if someone leaked an entire unlocked boot chain, including SBL1-3 and aboot, that could still be overwritten to "relock" the bootloader with an OTA (this is exactly what happened with the Verizon Galaxy S3).

To go into more detail, Samsung doesn't handle locking/unlocking like Motorola does. On the Qualcomm-based Motorola devices, it was possible to blow a Qfuse to unlock the device, which changed a physical property of the phone, resulting in a permanent unlock. There is no equivalent Qfuse on the Samsung Galaxy S4 to unlock, so the only determiner for whether a handset is unlocked or not is based on the software running on it, which can always be overwritten by an OTA update.

So I'm not exactly sure what AdamOutler thinks could be done to make a solution more permanent than mine will be, since it all comes down to the same fact: if you don't install OTA updates, you'll be able to continue installing custom kernels and recoveries, but if you do install an update, that could be taken away. And of course AT&T and Verizon will patch this promptly as soon as it's published, but there's really nothing that can be done about that.
[AT&T Samsung Galaxy S 4 General] alacrify:
I think the only part that Adam is talking about/hoping for is that Samsung KNOX would allow sandboxing the "protected" trust chain from the trust chain that would allow loading custom ROMs. Since Samsung hasn't gotten it to work yet, it's an open question. And I'm not sure how that would work but I'm not at either of your levels ;)

And of course Adam can (and should) correct me.
[AT&T Samsung Galaxy S 4 General] LLStarks:
All I want to know is if the exploit can be backported to the S3
[AT&T Samsung Galaxy S 4 General] MacAlert:
Essentially anyone that buys a Galaxy S4 after an OTA update may not be able unlock their bootloader?
[AT&T Samsung Galaxy S 4 General] sd_N:
2 cents..

I appreciate that the unlock is on the table just not served...I have also seen that TeamWin has posted an official touch recovery for our (AT&T) model. I would like very much for the unlock to be given to us; especially since the recovery is waiting. I also understand wanting to wait for the Verizon release which would help those users as well. It is a tough choice, BUT the Devs were so quick in finding an exploit that I would most likely assume that one would be found for the Verizon model as well and just as quick, even if the AT&T unlock was released. I do appreciate your hard work. I would ask that you release the unlock then when the end of the month rolls around, work on the Verizon model. Im sure there have been times when an exploit was found first for the Verizon users and was released first. Anyways...that's just my 2 cents worth. I have donated to devs and will continue to donate, sometimes there's a time to act, and sometimes well....

Thanks
[AT&T Samsung Galaxy S 4 General] jcase:
Pretty much any device with newer firmware may not be able to use his method.
[AT&T Samsung Galaxy S 4 General] LLStarks:
You don't get it.

There are 2 exploits ready, an AT&T(?) aboot and Dan's solution that should work on any locked US S4. Neither party wants to release or jeopardize the other's solution especially since Verizon is still an unknown variable.

In fact, Verizon still has more than enough time to do a zero-day OTA (similar to the S3 LG1 "update") that blocks both solutions to the point where there will be no "Verizon solution".

Not suggesting that Verizon would do that, but it's certainly within their power. Look at the Droid DNA's newest OTA.
[AT&T Samsung Galaxy S 4 General] drock212:
Wow selfish much? Patience is a virtue you seem to be lacking... I think we'll refund you those 2 cents and wait for you to contribute something worthwhile :D
[AT&T Samsung Galaxy S 4 General] jcase:
When the exploit has your name next to its name, then you can add your two cents.

Lets end the whining and/or begging posts here please people.
[AT&T Samsung Galaxy S 4 General] sd_N:
Yes I see that. I appreciate that info. I assumed the two exploits were based on two totally different parts of the software. Could one be released and then the other AFTER the Verizon release?

---------- Post added at 08:24 PM ---------- Previous post was at 08:15 PM ----------

I thought this forum was open and equal. Jcase everyone can put their two cents in. Waiting is no big deal. No one wants to tho. I'm patient. Haven't told anyone they can't say this or that because they "don't have their name on it". But OK. Whatever. I like to understand and learn as much as the next guy. Thanks.
[AT&T Samsung Galaxy S 4 General] hyghonryce:
Good point. This basically allows both Versions to use the same exploit without them being able to patch things up. This sucks for the earlier releases but this is over all BETTER for the GS4 community.

Basically buy the phone now, don't do any OTA updates and just wait patiently for the release.
[AT&T Samsung Galaxy S 4 General] SysAdmNj:
I gotta ask you all then I'm on build JDQ39.I337UCUAMDB, it hasnt taken an ota or udpated at the store correct?
[AT&T Samsung Galaxy S 4 General] jcase:
This forum is primarily for the developers (as was expained to me). I am tired of seeing people complain about what a developer does with their property, and seeing them badgering the developer. I asked that the type of behavior you are exhibiting stop, several times. I deleted dozens of posts over it in this thread already.

Lucky its not my unlock, I would have walked away it (which I have in the past)
[AT&T Samsung Galaxy S 4 General] jjgrantham:
I hadn't heard about a second (aboot) exploit. Where did you see that one?
[AT&T Samsung Galaxy S 4 General] Thermalwolf:
Come on people just stop asking why or how or when he's gonna release it. Dan never had to unlock the bootloader, he isn't obligated to do a damn thing. There's good reason devs do what they do and you shouldn't question it if you want to reap the benefits of their work.
[AT&T Samsung Galaxy S 4 General] sd_N:
And I thanked u for cleaning up the thread. I only asked questions...not demanded a release or ETA. I think my posts are clear about that. Anyway.... I say thanks again. I'm glad there's devs that r doing this for us. Peace
[AT&T Samsung Galaxy S 4 General] LLStarks:
You don't want either solution right now. If the aboot leaked today, it would permanently sabotage efforts to research a proper unlock and probably dissuade Dan from ever releasing his solution as it'll be buried as irrelevant by dozens of guides using the other method.

https://twitter.com/sxtpdevelopers/status/329699068181880833
[AT&T Samsung Galaxy S 4 General] stl-soldier:
In the event that a forced update is released, do we know of a way to block it? I see FWUpgrade 1.2.0 and LocalFOTA v2_1303_2_1. I froze both of them, but do we know for sure how to prevent receiving such an update?
[AT&T Samsung Galaxy S 4 General] LLStarks:
You can do that.

Assuming that the AT&T S4 uses kexec for a few weeks, you can also use a rom that disables updates. Any AOSP rom would practically guarantee this.
[AT&T Samsung Galaxy S 4 General] stl-soldier:
This is only to prevent a forced update before the bootloader unlock is released. Surely custom ROMs will have updates disabled. I'm just trying to make sure I don't get patched by force in the next few weeks.
[AT&T Samsung Galaxy S 4 General] cbazz1378:
Disable OTA's

Is there a way to disable future OTA's on our S4 so that we can use this exploit once it is published or do we just sit and hope this ship doesnt't sink before Verizon releases thier S4?
[AT&T Samsung Galaxy S 4 General] ErebusRaze:
The prospect for the development of this phone seemed dire before release, but has quickly gained ground. With some of the greatest talents in XDA (quite possibly) moving to this phone, the S IV will be solidified as a force to be reckoned. Technology has become more broad, yet unified and XDA is at the forefront of that movement.

- The Galaxy S IV -
[AT&T Samsung Galaxy S 4 General] jjgrantham:
Are you rooted? Do you have Titanium installed? Freeze the following apk's among others:

AT&T Software Update Vxxxxxxx

FWUpgrade xxxxx

LocalFOTA Vxxxxxxx
[AT&T Samsung Galaxy S 4 General] highaltitude:
I think the title should be "Bootloader hacking details Soon", right now it leads the reader to believe there are details already out on how to unlock the bootloader, which there isnt. It may be claimed by the OP that he is able to, and I am not doubting it, but since he is the only one with those details... there really isnt any info yet.
[AT&T Samsung Galaxy S 4 General] lowandbehold:
So I was thinking that even this solution might run into issues eventually. When 4.2.2 was released, we had to update our firmware and radios on the Nexus 4 so custom ROM's would work properly. Basically, you might get some good 4.2.2 ROM's out of this, but it might require another hack when 4.3 or 5.0 drops..whichever it may be...
[AT&T Samsung Galaxy S 4 General] bigblue95z:
Nevermind.
[AT&T Samsung Galaxy S 4 General] sd_N:
Totally true
[AT&T Samsung Galaxy S 4 General] gdevil:
I just bought this phone, it's telcel (Mexico) branded and I can confirm it's Bootloader locked, the rooting process was piece of cake, now we'll just have to wait for the unlocking method, just wanted to point out this in case someone else have this phone from the very same operator.

BTW I hope the moderators think in change the name of this sub forum because it can be confusing as it states it's just AT&T

Regards

Enviado desde mi GT-I9300 usando Tapatalk 2
[AT&T Samsung Galaxy S 4 General] jcase:
It says AT&T because it is just AT&T, but I will bring the suggestion up to include all I337. How was it confirmed to be locked?
[AT&T Samsung Galaxy S 4 General] StolenVW:
Problem I see with it covering all the I337's is that so far it looks like only the at&t one has the locked bootloader so if someone with a i337m posts something and don't say they have the rogers version and someone from at&t tries it it could brick them
[AT&T Samsung Galaxy S 4 General] Thermalwolf:
This is why you need to completely read the thread inside and out BEFORE doing anything, and then re-read the entire thread AGAIN. You gotta make sure your method is sound and the files you are downloading ARE what you need to be downloading. If the file name is vague and doesn't completely describe what it is, DON'T DO ANYTHING WITH IT UNTIL VALIDATED. This should be common practice by any modder of any caliber, period.
[AT&T Samsung Galaxy S 4 General] StolenVW:
Your right but how many noobs do you know that read
[AT&T Samsung Galaxy S 4 General] Thermalwolf:
Noob and can't read... *shudders* But to be back on track you're right, not many are willing to read and this has obviously been the case since the root was released and barely anybody took the time to even update there usb drivers before trying to root.
[AT&T Samsung Galaxy S 4 General] jcase:
I disagree entirely, I foresee no bricks coming from this.
[AT&T Samsung Galaxy S 4 General] gdevil:
Enviado desde mi GT-I9300 usando Tapatalk 2
[AT&T Samsung Galaxy S 4 General] jcase:
That is not confirmation, if the CID fo the device is normal, then the bootloader is going to display that. Verification needs to be done by backuping up recovery, flashing custom then booting recovery.

Do not use adb reboot recovery until you know it works, shut down the phone, hold home, volume up and power to boot recovery.
[AT&T Samsung Galaxy S 4 General] Snakeforhire:
Not wanting to quench your fires, bro, but come october you'll likely be saying "waiting for the upcoming GalaxyS5 to upgrade".. xD (and I don't much doubt that it'll be called so.. Now that Samsung's got a winning streak, you can expect them to squeeze it dry like lemon slices in a coke glass on a dry summer heat..
[AT&T Samsung Galaxy S 4 General] gdevil:
OK, so what should I do or check once I boot into recovery?

Enviado desde mi GT-I9300 usando Tapatalk 2
[AT&T Samsung Galaxy S 4 General] Zer0_:
I'm a bit confused about this too. I have a Koodo I337M and I have no idea how to check if it is locked or not... :$
[AT&T Samsung Galaxy S 4 General] scottbot95:
Don't want to start a flame war, but that was probably the most destructive and harmful to the community I've read on xda. He was merely stating that if there was a working hack for AT&T, then it should be released. That will in no way whatsoever make anything worse for Verizon or Sprint users. I understand Dan's reluctance to want to release a hack that only works for some people and the Verizon bootloader might shed some light on the others, but we don't need to go around insulting one another for asking for whatever Dan has now.

It seems to me that you were just being pissy because Verizon tends to be slower with some things. That doesn't help. We all want to see this bootloader unlocked, and criticism on other's opinions doesn't help that at all.
[AT&T Samsung Galaxy S 4 General] artvandalay22222:
So, I'm assuming by the time I'm eligible for an upgrade in October, they will have patched it making the phone practically unlockable.
[AT&T Samsung Galaxy S 4 General] Thermalwolf:
It's very much a possibility if AT&T is that hellbent on keeping it locked.
[AT&T Samsung Galaxy S 4 General] mattdm:
I'm gonna go ahead and re-state what has been stated several times already. The bootloaders are most likely locked using the same mechanism. If he releases the exploit for the AT&T version now, then Verizon will most likely be able to patch it and make it unworkable on their S4's. How will that not make things worse for Verizon users?
[AT&T Samsung Galaxy S 4 General] scottbot95:
If it was really that obvious, then AT&T would have patched it. Plus, Verizon gets it soon anyway and we all know how slow carriers are to make patches.

Edit:

Also bare in mind that anyone trying to block the hack would probably have enough info based purely off what has been said on this thread. Having the hack released will only allow them to patch it slightly faster.
[AT&T Samsung Galaxy S 4 General] jcase:
If custom recovery boots then you are fine
[AT&T Samsung Galaxy S 4 General] artvandalay22222:
Like a bunch of kids who can't wait to open your Christmas presents. Have some patience....

The longer he waits to release it, the more people who may be able to benefit from it.

He's doing the right thing.
[AT&T Samsung Galaxy S 4 General] mattdm:
The information in this thread only tells them that he hacked it. It doesn't tell them where or how the exploit will work. Releasing it, however, would tell them exactly where and how it works, and allow them to patch very quickly. You think they'll be slow? It only took them 15 days last time a similar situation arose.
[AT&T Samsung Galaxy S 4 General] scottbot95:
a lot of information can be infered. And knowing that it was hacked alone is a lot of info. I think youre also way over estimating how much they care. I diubt they will divert more than maybe 2 or 3 engineers to fixing it. Plus if/when we crack it at the odin level, were golden cuz samsung actually enjoys customers to mod their stuff. I have always had Samsung phones and half the cracks came from samsung workers.
[AT&T Samsung Galaxy S 4 General] mattdm:
You're making a lot of assumptions. Yes, Samsung is moderately developer friendly, in that they don't really care if we unlock the bootloader or not. It's not just Samsung we're dealing with though; it's Verizon. And it seems like Verizon has Samsung by the balls when it comes to this stuff.

Dan is just being cautious and considerate by waiting. Am I anxious to unlock my bootloader and get some AOSP love on my S4? Of course. Would I chose to do it now if there was even a 10% chance it would prevent Verizon users from doing the same? No way.
[AT&T Samsung Galaxy S 4 General] jcase:
You are absolutely right, if not understating it.

Im going to clean it up one more time when I get home than give out infeactions if I these kids keep thw bickering.
[AT&T Samsung Galaxy S 4 General] scottbot95:
Ok. Fair enough.
[AT&T Samsung Galaxy S 4 General] Bradl79:
Does Verizon still try to patch older phones, since this is kinda new to att I wanna know what to expect
[AT&T Samsung Galaxy S 4 General] scott14719:
Well, according to some people over in the T-Mobile S4 forum, Samsung is releasing future Kernels with the ability to block "Root" at the Kernel. If this is true, it's gonna be hard to put a custom recovery on the AT&T S4s (or any I9505 phones) even with an unlocked bootloader in the future. I'm sure there will be ways around it, but it seems to just be getting harder and harder for the everyday user to keep up....maybe that's a good thing.
[AT&T Samsung Galaxy S 4 General] alacrify:
And then I sell this and get an OPPO Find 5. No, it's not a good thing.
[AT&T Samsung Galaxy S 4 General] mocsab:
Way ttoo much engery and conversation is being wasted about something that is all moot anyway. Unless you or someone else comes up with a way to unlock the bootloader and releases it - it is going to stay locked until the Dev who broke the bootloader decides to release it. NOTHING can be said that will change that. And with all the disrespect that has been spread around second guessing his decision not to release it sooner, well, it wouldn't surprise me one bit if he decided to keep it to himself.
[AT&T Samsung Galaxy S 4 General] mg2195:
Edit: ignore post it was a waste of space
[AT&T Samsung Galaxy S 4 General] SeanHacker:
You run aosp with custom kernels. You will never have to worry about it. ;)

This build for this device of my version of aokp is burning a hole in my desktop. :D
[AT&T Samsung Galaxy S 4 General] stevehkim:
Dude Task so good to see ya here dude. One of my fav devs. Dont let it burn too long homie.

ATT S4 Rooted. Beastin.

4.2.2
[AT&T Samsung Galaxy S 4 General] alacrify:
You damn skippy...and when you need a guinea pig, I'm right here - and so is my checkbook...:D
[AT&T Samsung Galaxy S 4 General] jcase:
It would be highly irresponsible (and stupid) for ANY OEM not to patch a known security vulnerability. It would be a major disservice to their customers, and be putting them at further risk. They will and should do so. It will NOT prevent putting any recovery on the i9505, as they are unlocked, flash from recovery.

As far as AT&T S4, we dont have details. Assuming dan's exploit unlocks everything, then no patching the vulnerability used in motochopper will not stop recovery from being flashed. But since we don't know, that is just speculation on multiple levels.
[AT&T Samsung Galaxy S 4 General] dbg11235:
It is also a possibility that any patches down the road could also be exploited.
[AT&T Samsung Galaxy S 4 General] Hidden Username:
It's like the factory puts all the source code, keys and files on the first 100,000 S4s and then a dev gets one of them and an infinity amount of awesomeness comes out :)
[AT&T Samsung Galaxy S 4 General] Shammyh:
Alright guys... Let's calm the F down.

1st: Dan is correct in that waiting for the Verizon phone to be released is the way to go. If he doesn't, the Verizon version might get a 0-day patch, or something along those lines that permanently prevents any bootloader exploit. AT&T users complaining about this are simply being selfish. And on top of that, this is Dan's exploit! He can do whatever the hell he wants with it, and it's final. He can dump the whole thing, never release it, and that would be totally within his right. So stop fricking complaining! Jeeeze... way to bite the hand that feeds you.

2nd: This thread has gotten way way off topic. If you're not contributing to the thread in a useful and productive way, then STFU slash GTFO. This is not a "let's whine and complain" thread. Or a "let's discuss the merits of how Dan releases his work" thread. Or a "let's go way off topic about other GS4 issues" thread. This is a DEVELOPMENT thread in the DEVELOPMENT sub-section. If your post is not directly related to the exploit itself or the technical aspects of the bootloader unlocking process, then post elsewhere. By spamming this thread, you're simply making it harder for people who actually want to keep track of the progress/release of the exploit to find what they want. Which means when others read the thread, they waste time reading useless junk, instead of a simple update on the status.

And finally, but not following the rules, you set bad precedent for future development threads. N00bs are flooding in every day, and when they see threads like this get filled with junk, they learn that it's acceptable behavior. And then it gets worse and worse until a MOD finally has to lay down the hammer, delete tons of posts, and waste their valuable time. Let's try to avoid that path.

So please, please, PLEASE! Can my post here be the last random off-topic, non-development post that goes into this thread? k-thx-bye.
[AT&T Samsung Galaxy S 4 General] scott14719:
Dude, use the "report" button next time.
[AT&T Samsung Galaxy S 4 General] dirtyballoonot:
DesignGears

Where's DG when you need him? I'm still very disappointed ATT did this after not doing so for so long.
[AT&T Samsung Galaxy S 4 General] LLStarks:
People feel so entitled to things these days.
[AT&T Samsung Galaxy S 4 General] RicoStang:
Forgive me if this sounds useless, but can we stop being dicks about this and giving your rude opinion about having it now? The last thing we want to do is turn him away by begging.

One other question too which I don't mean to sound stupid with, but it's honest.

I know there is a concern of an update. If our devices are not updated and we unlock them, then we wont have to worry about OTA updates (assuming we are running a custom rom). However, wont this hurt development if the new devices released are indeed "fixed" to prevent it from being hacked? In other words, we will be able to take advantage of custom rom's, but anyone else getting the phone wont if it is new and unhackable with a preinstalled update. That would surely hurt development because there would be a small user base of custom rom's for our devices. I'm not doubting it could be hacked again, but it seems like it would be difficult to impossible from what has been said here before. Just curious. I'm following the hell out of this thread so I'll definitely see if someone posts a response to this.
[AT&T Samsung Galaxy S 4 General] LLStarks:
The dev community holds all of the cards right now. There's not much to worry about.
[AT&T Samsung Galaxy S 4 General] akira02rex:
I highly doubt AT&T will "fix" the newer devices. Has this sort of behaviour ever been shown in the past? - NO.

They do this probably for security reasons - not to f*ck with development. Some of you act like AT&T is some sort of enemy - they aren't believe me. If they wanted to screw us they could.

Be patient, wait for the vzw release and ye shall be happy for eternity.