yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] resurektz:
I would have, if i had known beforehand that you couldn't have roms on the update, i went and bought the phone without doing the research first, dumb on my part i know, but i always heard that Samsung devices usually are easier to root, and unlock, at least that's what everyone that has a moto phone seems to think :p i might go back and ask if i can exchange it for an non updated one, but i highly doubt they would let me, if i had the money i would just go back buy geeksquad insurance, smash the screen and claim warrenty, but i dont :p

EDIT: is there anyway to format my 16 sd card from the computer connected to my phone to exFAT? i dont have a card reader so i can't root unless i can format it while its in my phone..
[Verizon Samsung Galaxy S 4] Redflea:
yes, this ME7 ROM retains root and and custom recovery.

Not having to download and install another app...priceless. :)
[Verizon Samsung Galaxy S 4] ncope562:
True, yet this doesn't factor in the inner anger raging against the machine, the spirit of rebellion welling in all of us, or the fact that some employee bought an s4 and is p-o'd at their employer making their device less than the epically amazing if can be! Let's just hope said employee isn't just the intern who gets people coffee and has no access to bootloader code. :)

Sent from my SCH-I545, rooted, rommed, and raging
[Verizon Samsung Galaxy S 4] jorceshaman:
Just to clarify because I think you're misinformed with what seems like conflicting information but actually isn't. The bootloader isn't actually unlocked but with MDK you can do what an unlocked bootloader can through an exploit called Loki. That exploit was patched with ME7 but root alone was just released for ME7. They're currently working on finding an exploit that works for it but no luck quite yet.
[Verizon Samsung Galaxy S 4] waltersobchak96:
Count me in for $20 for root, $50 for full unlock!
[Verizon Samsung Galaxy S 4] Bloodcrav:
Still lokid and running the the ME7 ROM here. But please up bootloader unlock by an extra $50 on top of my $20 donation. I dont want to watch people that got new updated phones go through this again!
[Verizon Samsung Galaxy S 4] 808phoneaddict:
I went from cleanrom over to HyperDrive! CleanRom was awesome! But HyperDrive was a nice and stable replacement for it... Check out HyperDrive
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Donator lists updated

Bootlocker unlock bounty has now reached over $4000. :good:
[Verizon Samsung Galaxy S 4] dvsgod:
over the weekend I decided a 16 gig was not enough so I returned it for a 32 gig and it came with MDK. out of the box it started doing an update all on its own I was able to hold it off without accepting it. Now I have a rooted S4 on MDK. I'm still in from my donation I would take the new upgrade with full unlock.
[Verizon Samsung Galaxy S 4] rdcamero:
Who's going to be first here to give it a go and report back ?
[Verizon Samsung Galaxy S 4] asdecker:
Damn it sure is tempting. ...
[Verizon Samsung Galaxy S 4] sporty377:
Thats what I read...but thats was when ppl was doing the update through kries or using verizon updater using the computer.

---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------

Very tempting....:banghead:
[Verizon Samsung Galaxy S 4] asdecker:
It says right there in the app that it doesnt work updating via KIES, only ota's that use the update.zip type

---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------

Im running hyperdrive now so would I have to odin back to stock, reroot (stock only), then take the ota?
[Verizon Samsung Galaxy S 4] dstreng:
even if it does keep root through ota, most likely the bootloader will still be patched, killing loki
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Voodoo will work through OTA everytime

UNLESS

this OTA has patched the Voodoo root-keeping method. That is the only thing you guys might want to check first (need one test dummy).

The Desktop and Kies update flashes an entire factory image onto the phone (hence the huge file). The OTA only applies changes into the current files already on your device.
[Verizon Samsung Galaxy S 4] mikeyinid:
You have to be completely stock rooted. Stock recovery. Cant delete any system apps or the update will fail. I assure you, if you do what voodoo root keeper tells you, you will keep root through the update. Has to be ota tho. Not through pc
[Verizon Samsung Galaxy S 4] rdcamero:
Waiting for temptation to get the best of someone and they try it first :)
[Verizon Samsung Galaxy S 4] mikeyinid:
I doubt this has been patched. ATT update wasnt. But I didnt think about the loki patch after taking the update. What good is a rooted phone with no recovery lol.
[Verizon Samsung Galaxy S 4] dstreng:
one way to tell for sure, I think but I might be wrong, is to pull the ota, not install, but look through the updater and see if the ota updates the bootloader. if so, loki is dead atm. if it doesn't, which is unlikely, then we could technically still have loki and potentially root if voodoo does indeed work
[Verizon Samsung Galaxy S 4] r_hippy:
You all can hold out my kid is out till tomorrow. The phone is all stock except what I added for root and it's not a big deal to lose root on that phone. If it does indeed work it's most likely because it's stock (no rom) but if it has root it will be a plus but I'm not sure loki recovery will work tho after.
[Verizon Samsung Galaxy S 4] r_hippy:
That's why I said ota ;)

The desktop flashes every dir in return there is s no rootkeeper left.

---------- Post added at 09:55 PM ---------- Previous post was at 09:53 PM ----------

Then again I had it fail keeping or restoring on my nexus 7 but did not have the super bootloader lol
[Verizon Samsung Galaxy S 4] Rebel908:
So just flashing the MD2 kernel, running motochopper, flashing back the original MDK kernel, voodoo to temp unroot AFTER backing up root, then flashing OTA not Odin or Kies or Verizon installer, then restoring root?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
OTA update does update the bootloader as well as the kernel, both of which effectively kill Loki-method in it's current version (and of course prevent you from downgrading as well). This has already been confirmed in a few external chats.
[Verizon Samsung Galaxy S 4] mikeyinid:
Yes but be mindful of the last few posts. You will be rooted but loki is patched and you will not have recovery. Or the ability to downgrade. Not worth it imo.
[Verizon Samsung Galaxy S 4] sporty377:
I guess we'll wait for rebel908 to see if it works
[Verizon Samsung Galaxy S 4] r_hippy:
That's a good question there . to temp unroot or stay rooted.
[Verizon Samsung Galaxy S 4] udmatador:
Id like to raise my pledge for the unlock to $50 please

Edit:And thanks for the successful root.
[Verizon Samsung Galaxy S 4] zerofighter1:
I recommend not closing it for the sake of keeping track if previous donations. Let's just try to keep on topic please.

Maybe open a discussion thread in the general area?
[Verizon Samsung Galaxy S 4] BeansTown106:
its really not that bad. The whole point of this thread is to tell how much $ you are going to donate and talk about the bootloader, I say let [MENTION=3313404]open1your1eyes0[/MENTION] decide what is right and wrong. After all he is the one keeping track of the donations. When it gets tough for him to decifer through everything then he can pm a mod etc.

We are in general :D
[Verizon Samsung Galaxy S 4] 318sugarhill:
i agree with the discussion getting out of hand. I'm going to start a discussion thread. So many unnecessary comments. Just make a pledge and move on. Openyoureyes does not need to read your personal stories and wishes while counting bounty pledges.

Let's take the discussion here

http://xdaforums.com/showthread.php?t=2384222
[Verizon Samsung Galaxy S 4] andybones:
Put me down for $20 on the bootloader unlock, please.
[Verizon Samsung Galaxy S 4] pschatz12:
Put me in for a hundo! $100 for unlocked + recovery
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Donator lists updated

Please note, as stated very clearly in the disclaimers you may not place a contribution for only ONE bounty. If you make a contribution, it will be added to both lists, but only one bounty is paid at the time of claim (which ever bounty is claimed first).
[Verizon Samsung Galaxy S 4] Covert_Death:
you know what, im in... im tired of just waiting to get a recovery going.

i'll pledge $10 for a recovery unlock method so i can start flashing ROMs again.

anyone else just reading this thread should do the same, if you're here you're interested and if you're interested you should help reward the person who makes this happen, just pledge 5-10 bucks and help the system out!
[Verizon Samsung Galaxy S 4] resurektz:
Put me down for 10$
[Verizon Samsung Galaxy S 4] :
Could you up my amount to $50 for the bootloader unlock? Thank you much!
[Verizon Samsung Galaxy S 4] jbis:
put me down for $20 each
[Verizon Samsung Galaxy S 4] TheJ0hnman:
My fault, tag-teamed without reading OP. Sign me up for $100 please, and gently caress Verizon.
[Verizon Samsung Galaxy S 4] clemente718:
I'm good for $40
[Verizon Samsung Galaxy S 4] DamiaNations:
I ordered my replacement last Friday and it came yesterday with mdk.
[Verizon Samsung Galaxy S 4] pschatz12:
Did it ship from Texas?!
[Verizon Samsung Galaxy S 4] DamiaNations:
Yup I believe so.

sent from my brain
[Verizon Samsung Galaxy S 4] pschatz12:
PM sent
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
I got my replacement 5 days ago from the Texas warehouse and it wasn't updated to ME7....I posted this a few days ago actually but yeah it wasn't updated and it came with MDK...I'm rooted and running recovery since then but still have kept my pledge up there...its only right. And anyone who does get a replacement device "should" do so as well
[Verizon Samsung Galaxy S 4] resurektz:
What did you say to get a replacement I dont see how everyone is getting their replacement phones lol.
[Verizon Samsung Galaxy S 4] pschatz12:
I told them the speaker was sounding muffled and distorted and that it sounded like it blew... The external speaker... They put me on with a level 2 rep and that was it... I told them I did a factory reset already and it didn't change anything
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
You could make something up but once you get to a Level 2 representative thats the people usually authorized to give replacements, however I have had Tier 1 reps. give me replacements before...my BlueTooth legitimately wasnt working so thats why I got a replacement device.
[Verizon Samsung Galaxy S 4] jignasze:
bounty question?

How are we splitting up the bounty? Since someone has already provided root - how much should they get? if anything? I don't think to whole bounty should go to just recovery? & since the bounty is still growing, should the bounty for root have stopped on the date it was acquired? Not fair for whoever ends up with recovery to get it all?

just some random thoughts -
[Verizon Samsung Galaxy S 4] prstorero:
It's supposed to be the one who gains both root AND recovery that gets the bounty. Not sure how it will be if two different people got each one.

prshosting.org
[Verizon Samsung Galaxy S 4] jorceshaman:
Root was had by an existing exploit modified by someone. The person who modified it said that if you wish, you can donate to the original creator. But right now, the full bounty is going to whoever gets the recovery or recovery + bootloader unlock.
[Verizon Samsung Galaxy S 4] xs11e:
So far, no results

It's possible there may not be any results, ever. Samsung may have succeeded in locking this phone permanently (and think what this would mean for future Samsung devices!)

Has anyone considered a time line? Some date in the future at which we can say, "It isn't going to happen?"

I propose a cut-off date of January 10th, 6 months after the initial post. Why? Because nobody should have to hold money, even a small amount, in limbo for ever.

Comments?
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
I think there needs to be patience...the security they added to this phone is pretty insane. You may be right that itll never be unlocked...I for one don't believe that. If they don't have unlock 6 months after its release (which I highly doubt) then most people would have moved on anyway by then. Theres definitely atleast 15 people I know working on it. It is going to take time...Its only been 16 or 17 days since the update was released which is not a long time AT ALL for what has to be achieved in unlocking the boot-loader and getting recovery installed...all of the people working on an exploit are NOT working on this all day every day they have lives as well as jobs/wives/children etc. Patience is key here and thats all we can do
[Verizon Samsung Galaxy S 4] KennyG123:
Thread cleaned

The OP has requested that this thread stay on topic and for development

No more idle chit chat or talk about replacing phones

Thank you for your cooperation

Friendly Neighborhood Moderator
[Verizon Samsung Galaxy S 4] elliwigy:
Delete
[Verizon Samsung Galaxy S 4] xs11e:
My post has nothing to do with patience, it has to do with financial common sense. I won't (nor should anyone) pledge money to be paid out if something happens in the next unstated number of years. There needs to be a cut off date and I believe 6 months is adequate time for the devs. It'll be cracked in less than that or it won't be cracked.

I don't want my grandchildren being sued 10 years from now because some diehard finally cracked the phone and wants to collect on a promise I made 10 years ago, I want an end date after which time I can spend the money I pledged on booze and cheap hookers!

I haven't pledged yet nor will I until a cut off date exists, any accountant and/or attorney would have a stroke if I did!

So how about it, can we set a date? My suggestion is 6 months, anyone else?

NOTE TO MODS: This isn't off topic, it's a request to modify the terms of the original post.

And PLEASE don't post stuff such as above which only shows you didn't read or understand my initial post on the subject.
[Verizon Samsung Galaxy S 4] :
Deleted.
[Verizon Samsung Galaxy S 4] bajasur:
Please post off topic bounty comments here

http://xdaforums.com/showthread.php?t=2384222
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
lmao dude your worried about $10 to $100 10 years from now? and you didn't even pledge in the first place? I have a rooted S4 and STILL pledged money...pledge whatever you can it doesn't have to be earth shattering...I fully understood your original post yet you failed to quote my whole response...I know what you meant but its kind of ludicrous that you're talking about accountants and lawyers for less than $100.....its a pledge...an honor system is in place here, that when it is cracked you will pay...and we the community and devs are TRUSTING you will pay...you think ANYONE would pay after a year (or 10 years as you like to put it) after the phone is cracked? I think you are thinking/looking way too much into this...but to each is own enjoy yourself....feel free to delete this comment I'm sorry but I had to respond to this guy
[Verizon Samsung Galaxy S 4] Rebel908:
Is there any dev locking for a guinea pig to test any potential recovery or bootloader work? Trying to mess with my device and I'd rather be given instruction versus stumbling around on my own.
[Verizon Samsung Galaxy S 4] andybones:
Instructions are to wait patiently.
[Verizon Samsung Galaxy S 4] eskomo:
This thread just stays off topic. Needs to be closed.
[Verizon Samsung Galaxy S 4] rushless:
Since there will probably be updates before six months and likely resetting current efforts, if six months- it probably ain't happenin'. That said, it would be nice to get a general update on status. Something as simple as "we're close", "brick wall", "no real progress" or something. I have read through and still have zero clue on a mean trend of what the status is. If WIP, that tells nothing, since WIP anything from "no real progress", to "we're real close".

Does not seem unreasonable to get a general status of progress, based on the collection of efforts. Unless all are working on their own thing.
[Verizon Samsung Galaxy S 4] Cruiserdude:
What part of "Be patient" do people not understand? Yes, it may take some time for a workable solution to be found, and there's always a possibility that one will not be found. However, this is a hugely popular phone, coming on the heels of the S3 that was basically the go-to Android device for a year and still going quite strong. Plus our bounty is over 4k, so there's plenty of incentive for those not motivated by the sheer challenge alone, of which there are plenty.

But this is a new level of security from Samsung than we are used to, the guy who found the last exploit doesn't appear to be interested in this for now, not to mention that we were doing alright with Loki until this update came out and blindsided everyone, so focus on this just recently picked back up for many. It's only been about 2 weeks, so be patient and stay positive.

Keep in mind as well that the bootloader is the bigger prize for a few reasons, not just the ease of building and flashing kernels without some sort of workaround that may or may not be found. The current root exploit, whatever recovery solution is found, and any possible workaround for flashing kernels (like Loki) that may or may not accompany those solutions, can and almost certainly will be defeated once again in a future update. So while it'll help a lot of people, it still won't be a permanent solution, meaning eventually both new users, as well as those of us needing replacements, will still get stuck at some point.

A true bootloader unlock, on the other hand, is much less likely to be patched. Don't get me wrong, it certainly can be patched, it's just much more involved depending on the implementation of whatever unlocking method may be found. Look at the S3 and it's engineering aboot, for instance; once it was unlocked, it stayed that way. Granted, it's different here because Samsung seems to have implemented some hardware method of preventing downgrading, but that means that a true unlock would likely defeat or bypass this, or potentially be a sort of "master key" method to spoof or disable error checking that would make this irrelevant.

It's not a given, but it's certainly more desirable to unlock the bootloader than simply achieve recovery, as it IS a given that root/recovery will be patched in the future. And it's harder to achieve, which means more time, and less time for status updates that clue Verizon in to what they need to tell Samsung to patch.

So be patient and think positive, all this negativity does is drive folks away from this project, which doesn't help anyone.

/
[Verizon Samsung Galaxy S 4] bajasur:
Guys please take this over here.

http://xdaforums.com/showthread.php?t=2384222

It is welcomed in that thread. Let the devs and people who know what they are doing talk to each other in this thread!
[Verizon Samsung Galaxy S 4] rajat12345:
Speculating

Just guessing but couldn't someone dump the bootloader or kernel of the developer edition and flash it to a normal one, wouldn't that unlock a normal one?
[Verizon Samsung Galaxy S 4] AsaSpades:
Why are you crying about setting a cut-off date? You either pledge or don't, nobody asked you nor told you to. Who is thinking that far ahead? The phone just came out.

Maybe no one who devs has received theirs yet? No idea
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
Its being looked into as we speak (erm type :) )
[Verizon Samsung Galaxy S 4] BeansTown106:
from what i have read/heard selinux kills any possibility of 2nd init/kexec
[Verizon Samsung Galaxy S 4] :
Could someone point me to where I could read and educate myself about this stuff? :)
[Verizon Samsung Galaxy S 4] Jayrod76:
Which is probably a big reason hashcode has advised against taking the possible upcoming Omap updates (Bionic, RAZR,etc)

Sent from my Platyraptor extreme ultra maxxxx 4gLTE/GSM/ABC/123 Nick Knack Pattywack Ermegherd GED, MD,RNA,DNA,YMCA Edition S4! Via the 4th dimension....NOW RUNNING ECLIPSE
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
wow it doesnt even let it create a 2ndsystem...this is something else man I couldve sworn I saw someone guinea pigging people for safestrap but it never unfolded

its really a thing where most people have done it by trial and error and worked and tinkered on stuff themselves....there are courses online to take but i would suggest reading a bit about how android is compiled/and what its made up of.....its really quite simple when you understand the "lingo" for lack of a better term...there are only 4 or 5 main parts to android....its written mostly in Java and based off of Linux....it consists of app frameworks....libraries like Open GL and SQlite....runtime and the kernel....if you just Google "an introduction to android" youll find a million articles about what android is and how its made....security however is a completely different story....samsungs security on this latest update is pretty much something that has never been seen before (as far as phone security is concerned) and they took it to another level but theres a million people smarter than myself who actually are working on it in their free time and I have faith in them....I'm almost positive Beans and Jcase and open1your1eyes0 (some of the head honchos on xda) would agree that reading from credible sources is key to learning about android and what it actually is...thats how I feel at least....you have to read and read and maybe have an experienced friend willing to help teach you the ropes a bit but mostly its trial and error and doing your own due diligence
[Verizon Samsung Galaxy S 4] heyazzo:
Bootchain in a nutshell...

Samsung Developers have used the 2048 bit RC4 RSA key to sign their work...

Merely using their same signature will not do.

--TrustZone®-based Integrity Measurement Architecture (TIMA)--

First, up to bat, is TIMA. Trustzone on this processor requires 4 of these keys to be provided within each image introduced to the bootloader, Tima observer looks at the code coming in, if it does not have MAGICCODE , then it fails by default, and reverts to normal. I've corrupted my recovery by using TA several times already, but that's what a pool and extended warranty is for.

Second up, is the bootloader itself. It says it is a secure bootloader, 'nuff said.

I'd like to see what hooking up a FGPA processor up to crank out some numbers, and roll script at this handset until it bleeds unlock...

Hope this helps anyone not perhaps more read on the subject of cryptography, and the authors of the code we all want to see broken. This phone, after all was supposed to get rid of all "known vulerabilities" according to the engineers.

The whole idea of keeping the phone secure is to keep the containers good, because it's supposed to be like a Sensitive Compartmented Information Facility.
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
very nice, very nice thank you sir....I am definitely not verse in Cryptography/symmetric keys/security engineering and the like... and do not claim to be...I know the very very very basics of what it entails...but thank you for that I appreciate it
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
No it seems it cannot be applied here...As Beanstown stated a few posts above safestrap uses a primary and secondary "system" to bypass the lock....the selinux will not let the 2nd system be applied or even created i believe
[Verizon Samsung Galaxy S 4] heyazzo:
I need some logcats to confirm where we are having the problems like, SElinux denying permissions, and doing things to this. SELinux gives permissions at boot like SU, 0, 1, whatever user... If an application does not have it's respective user associated, then it crashes the program, and keeps authorithy with that process in it's respected thread.:D
[Verizon Samsung Galaxy S 4] hlxanthus:
The answer to your question was just answered. No safe strap is possible

http://xdaforums.com/showthread.php?p=44156431

Edit: sorry for some reason it took like an hour to post this. :)