yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Bait-Fish:
Dark. The initial boot screen is black as is the Samsung splash screen. Then comes a horrible Verizon splash with white background.

Dark. Definitely dark.

P. S. HUGE THANKS to sound-mind, Hashcode, and Oblivion...!
[Verizon Samsung Galaxy S 4] Blue:
Yes what he said (:
[Verizon Samsung Galaxy S 4] twizzlejr:
Dark definitely
[Verizon Samsung Galaxy S 4] ahoslc:
Dark
[Verizon Samsung Galaxy S 4] Hashcode:
I apologize for blowing up this thread. :/

Let's move Safestrap discussion to here:

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

Moderators feel free to clean out this thread of non-Bounty related content.
[Verizon Samsung Galaxy S 4] jova33:
Apology accepted..... this thread is all off topic banter, so the mods would have a whole lot of cleaning to do
[Verizon Samsung Galaxy S 4] Alxoom33:
It's dark! Very dark.

EDIT:I guess HC got his answer lol! Didn't see the last page of responses.:D
[Verizon Samsung Galaxy S 4] bobosir:
thank you sound-mind!:good::good::good:
[Verizon Samsung Galaxy S 4] wtherrell:
OK, but next time, 30 lashes.
[Verizon Samsung Galaxy S 4] equake:
I'm unsure if that's only s/w disabled per model because the GPe model has fastboot enabled even though there is no official factory image

My 2 cents
[Verizon Samsung Galaxy S 4] 318sugarhill:
So Hashtag is working on a safestrap for the S4. I currently have never taken the ME7 and kept my custom recovery. In the future if safestrap becomes a reality, would there be any benefit to taking the update and using safestrap instead for new roms? I know they all would need to be based on the TW stock kernel. I guess what I really want to know is, where will the development head? Will developers shift to safestrap Roms, stay with Loki Roms, or will there be a nice mix of both?
[Verizon Samsung Galaxy S 4] Cruiserdude:
I've wondered the same thing, as both Odin and fastboot talk to the same Loki daemon in the bootloader IIRC (NOT to be confused with the Loki exploit). Odin adds a little functionality, but the lack of fastboot hurts compatibility, which is probably why Google insisted on including it on their version. Not sure why they didn't just make Odin an extended layer atop fastboot, like Motorola did with RSDLite, but I haven't heard of anyone enabling fastboot on any non-Google Samsung. Not that there's much need I suppose, what with Heimdall, though I'm sure I'm not the only one who prefers using a shell-based restore method over a GUI.

No, don't update to ME7. Hashcode himself will be working with an MDK device, as previously stated, so Safestrap will work fine with it. Besides, the Loki method (this time referring to the exploit) will still be the preferred method, as it emulates a true hardware unlock. And until he is able to get kexec working, SS won't let you flash custom kernels, or roms that require one. There's no guarantee that kexec will ever work, though we're of course all hopeful on that front.

Long story short, SS will be a great option for MDK folks as well, due to its ability to boot multiple roms. But it will have its limitations over something like Loki or a possible successor. So hang on to MDK for the option. If you truly find you have no need for it, then you can wipe it and sell your MDK, get an ME7, and pocket the difference while giving someone else an option to play in the sand.

As far as rom compatibility, we don't know yet, but I don't expect it to be much of a problem. There's plenty of TW options, and if Hashcode is able to block kernel flashing through SS, those same roms will work. Those that require a custom kernel could likely be modified by the dev to work without much of an issue. If kexec is achieved, I don't see why you couldn't flash the exact same roms and packages either way. Since Hashcode will be working with an MDK device, I would assume that a potential kernel flashing method would be able to use a boot.lok by default. So devs wouldn't need to do anything different. But we'll have to cross that bridge when we come to it.
[Verizon Samsung Galaxy S 4] trook:
Speaking of JTAG.... Has anyone ever tried to JTAG back to MDK?
[Verizon Samsung Galaxy S 4] Bait-Fish:
Yes.
[Verizon Samsung Galaxy S 4] dadsterflip:
Ignore loll.
[Verizon Samsung Galaxy S 4] jova33:
Huh, he locked his thread.
[Verizon Samsung Galaxy S 4] Cruiserdude:
Just read through that thread, any confirmation that actually is working? Not that I doubt anyone's credibility, I'm just wondering how it would reset/bypass the efuse states that ME7 sets?
[Verizon Samsung Galaxy S 4] jova33:
I've been following the HTC One thread, and JTAG and javacard has come up in their bootloader discussion multiple times.

I think it has something to do with putting in a special SIM card or SD card, and that's why you have to send your phone to the person who has that card.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I only took what was posted at face value. I'm not sure of any feedback confirming. Seeing that h311sdr0id is a recognized developer eased my usual level of doubt.
[Verizon Samsung Galaxy S 4] Obsidian...:
Stay with MDK. You can always take the update in the future but you can never go back. Dev work will happen on both. Oh and wait until Hash releases SS anyway lol
[Verizon Samsung Galaxy S 4] 318sugarhill:
I'm quite happy with the Rom I'm on, and unless some major great thing happened, I'm not about to give up something there is no turning back from unless I was force to. I was asking in general as I'm sure IF SS happens, some will. Then again, many don't use the search so it will get asked 50 times.
[Verizon Samsung Galaxy S 4] Obsidian...:
Here's an answer to using SS on mdk

Sent from my SCH-I605 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] jova33:
So if switching between AOSP and TW, just flash appropriate kernel?
[Verizon Samsung Galaxy S 4] dynospectrum:
Yes, and always clear cache & dalvik cache before flashing.

Sent high from my SGH-M919
[Verizon Samsung Galaxy S 4] jova33:
Well, that was in regards to SS and those of us on MDK.
[Verizon Samsung Galaxy S 4] VincentDHam:
Replacement Devices still on MDK

Just an fyi, i ordered a replacement device that i received today, and they still ship with MDK.
[Verizon Samsung Galaxy S 4] Cruiserdude:
Color/size/warehouse?
[Verizon Samsung Galaxy S 4] VincentDHam:
White, 16 GB, and idk the warehouse. How do I find that?
[Verizon Samsung Galaxy S 4] therobzilla:
Replacement/New Phones From Verizon Store

I recently, last weekend cracked my screen on my S4, this phone was originally delivered with MDK on it, however the upgrade was downloaded when I was on the road one day, and I was pushed through and updated to the ME7, so I like many was pretty much a "Stocker".

Just as an FYI when my phone became cracked, I was told by out IT department head to go to Verizon and get another phone, just use one of our upgrades as we are a very large company and have many upgrades on account. So off to the local Verizon store I went.

When I got there the verified our account status and I was asked what I wanted for a new phone, could have had anything I wanted, company does not care, however I wanted the S4 again, so I told the associate that I wanted another S4, however I flat out told the associate that I did not want a phone with the ME7 upgrade on it, and to check their stock for a S4 with the MDK version of phone. He said he would check in the back when he went to get the phone.

About 2 minutes later, he came back with a NEW phone in had with the MDK version firmware on it. I asked him if it was hard to find one, he said that more than 1/2 the phones in the stock room had the MDK version on it, and that the shipment just arrived about a day ago, as they were burning through the S4 phones.

I told him I wanted the ESN numbers changed and that I was going to activate it later that day or the next day, would that be a problem, he said no problem, just to insert the SIM into the phone when I was read the phone would work as soon as I turned it on. I gave him my old S4 for the trade in program got a credit on our account, ordered a S4 Mophie and off I went.

This particular store is one of the busiest stores in the East Valley of Phoenix and they go through a bunch of phones.

The associate I know from being in there pretty regularly, and he had ZERO issues with not activating or upgrading the phone at time of sale, I actually asked him did he have to update the firmware since it was the old version, he said no, that it would automatically update once I turned it on, and I asked him if there was any policy about updating the firmware before or after after activation that was corporate driven from Verizon, he flat out told me, nothing at all.....

Just and FYI, at least where I reside, there are still MDK phone available, and you can ask for them when and if you are purchasing one.....
[Verizon Samsung Galaxy S 4] 318sugarhill:
Thanks man.
[Verizon Samsung Galaxy S 4] thunderbls:
Curious... I bought my s4 from costco and they have a 14day if your not happy with the phone swap plan.... if I take it in saying I dont like the upgraded software and want the mdk if they would do that for me, maybe worth a shot?
[Verizon Samsung Galaxy S 4] JPMontana:
Hello everyone...

So the original [BOUNTY] thread has been shut down. Is anyone still collecting bounty money?

It seems like the developer community has lost momentum on Bootloader and Recovery exploits for the S4, and an increasing bounty seemed to be a good motivator. Maybe it's just a perception, and perhaps people are still working on it.
[Verizon Samsung Galaxy S 4] :
Have you checked the threads lately??
[Verizon Samsung Galaxy S 4] sokrboot:
Definitely people still working to free up this device. Sit tight.

««I used to be a Serial Flasher...now I'm just a Cereal Flasher.»»
[Verizon Samsung Galaxy S 4] equake:
Its highly unlikely that a Bootloader unlock/hack is available unless there is a a leak of some sort.

There is work being done on a bypass method with Safestrap that is being worked on by Hashcode.
[Verizon Samsung Galaxy S 4] Mightycaptain:
I can't help but wonder a little bit if a vulnerability has been found and the waiting game is on for a 4.3 update that will surely come for this phone . To try and prevent a patch.
[Verizon Samsung Galaxy S 4] eskomo:
You can revert back to mdk if you have a jtag riff box. If someone had a exploit working I'm sure they would step up. Waiting for 4.3 or 4.4 gives no advantage. It doesn't solve anything.
[Verizon Samsung Galaxy S 4] biglil1:
Yeah but if ur within ur 14 day trial then why not. After all it was set up for u to test the device see if ur happy and if not then return it within that period. They pushed an update that changed ur opinion of the device thus making u unsatisfied with it rather it's the fact that u can't achieve custom recovery, battery life SUCSKS!!, or any other aspect u want.

In my case the stock recovery isnt working properly and even though it doesn't effect the OS its still a defect that doesn't allow me to maintain my device to keep it runnig smoothly so its going back.

Not tring to start anything just my opinion
[Verizon Samsung Galaxy S 4] jmgib:
I don't really have an issue with people simply taking it back if they are within the 14 days or whatever. I just don't like the the intentional bricking or making up BS if they are past that cutoff.
[Verizon Samsung Galaxy S 4] :
Yea, such fraud. If only they would update all replacements with me7, then all this nonsense would end.
[Verizon Samsung Galaxy S 4] andybones:
+1,

and if you are going to do it, why come into a thread like this and tell everyone (including the Verizon reps most likely reading this...)
[Verizon Samsung Galaxy S 4] Phatdawg:
Well, I think there's two ways to look at it.

1) Customers are returning unethically because they are lying about the true reason of why they are returning their phone.

2) Verizon shouldn't lock the phones as they are and customers are justified in returning as it is a paid product (expensive) with expensive service (relative to others).

The whole idea of what we are doing here it to break Verizon's "protection" over the phone and create root, recovery, unlocked bootloader. How can anyone justify this act which in itself isn't exactly acceptable from Verizon's okay and not returning the phone to obtain it not-okay?

Before you start judging people about this. Just remember these returns - verizon probably already knows this is a problem and probably has a team on these forums. It's no secret.

Verizon's policy on their phones makes them eat it when things like this happen. If it's a big enough loss, perhaps they will open up certain things to the dev community, but it hasn't over the last few years, so why should it now?

As far as I'm concerned, everything is far game when it comes down to root/recovery/bootloader.

And bricks are easy to fix from the seller level. They have the software and equipment to debrick quite easily (as long as it's not a physical issue).

I'm more than happy that the verizon reps are reading this -> give us access to root/bootloader please. Also it would be nice if you developed a back up program and ways to recover from various type of bricking. i.e. UI for idiots that can create recoveries that make it difficult to brick or bootloads from sd card like the nook color.
[Verizon Samsung Galaxy S 4] abe_cedar:
AMEN!

also if I buy the device upfront I want it unlocked rooted and SIM unlocked so that it can run on any network (Provided radios permit). It is mine. and I am willing to pay 800 USD for a phone then you should not been locking it. Also for that kind of money they need to provide a software image. That's how is done with the real computers.

And now dear verizon team get to work,

many thanks
[Verizon Samsung Galaxy S 4] andybones:
Thats the thing though, you can buy the phone outright from Samsung, with it unlocked, but this of coarse, kills the warranty, which is technically invalid once rooted anyway.

but I completely agree, the phone is ours, we paid for it, I think we should have an option like HTC now does to let us have root + recovery, at the least.

S-OFF is still always wanted, which is a full unlock (and it doesn't break warranty), much to what out bootloader unlock is.
[Verizon Samsung Galaxy S 4] s0m3f00l:
Let's not forget. If you don't take the discount from verizon are you excluded from the locked bootloader? No. If you pay off the subsidized amount can you request the lock be removed? No. Will Verizon honor a rooted/unlocked phone that you paid for outright? No. And these people are giving the customers sh*t for being unethical?

Who exactly is unethical here? You have supplied them an end product that you legally still own. While I don't agree with the classical US cell phone market model, and choose to buy all my phones outright. The phone companies should supply these phones as unlocked or offer a way to have them unlocked after the subsidized price is paid. Ethically that would be the correct thing to do. The company however isn't interested in fair, they are interested in eventual end support of your device and moving you on to the next one for a minimal of features and lack of updates. No, these people unlocking and rooting and returning phones... They are doing the work of Adam Smith's free market. They are doing the work of Capitalism and Freedom. They are showing the company there is a demand for this and there will continue to be. They are saying we do not agree with your model and will not participate. They are clicking the opt out button in real life. They are doing Gods economical work....

I say brick root and replace your phones. Show them what you think of there feature downgrade, I mean update...
[Verizon Samsung Galaxy S 4] elliwigy:
like when sony removed other os from ps3.. remove features instead of adding and building on them
[Verizon Samsung Galaxy S 4] vegittoss15:
Sorry if this is a dumb question, but is there any place I can go to for a technical discussion on the bootloader? Whether it be forums or an IRC channel, both are fine with me.
[Verizon Samsung Galaxy S 4] lycwolf:
http://xdaforums.com/showthread.php?t=2389246
[Verizon Samsung Galaxy S 4] Loglud:
I agree with you that it is unethical to lie about the true reason for returning your phone however it is also unethical to not allow other reasons for returning the phone ice boot loader is locked. If you walk in and say "I am not satisfied with this phone because the boot loader is locked". They'll look at you and say tough cookies. Deal with it, as it not something they ensure under their satisfaction guarantee. However there are some problems with this. It is part of their satisfaction guarantee. If your within 14 days you are within your right to ask for a refund anyone who is having issues should be able to point out their policy's. http://www.verizonwireless.com/b2c/support/return-policy states that

There are no limitations placed on this clause. As for the boot loader lock we must look at legal reasons that they lock their phones. Some applications such as, I believe NFL TV and HD Netflix require a locked boot loader as stipulated in their contract. I agree that they should allow for unlocks and do what is known as proprietary removal on unlock, which is stipulated in their contract. But they get money for every stream you use and thusly would loose money if they allowed for you to remove their proprietary streaming.
[Verizon Samsung Galaxy S 4] vegittoss15:
Cool, thanks!
[Verizon Samsung Galaxy S 4] resurektz:
I bought my phone from bestbuy, and there was no fee. I just walked in today and exchanged it for a white one that came with the mdk build an thats the reason i wanted to get a different phone, kinda liked having a black one, but i rather have root and loki then just root, so i got a white one incase there is never an unlock. Simple easy way to get the mdk build thank god i was in my 15 day period that bestbuy gives you.
[Verizon Samsung Galaxy S 4] jova33:
Now my question is, what happens when I need a warranty replacement in 8 months and it comes with a Loki patched update? I'll be upset because many of my paid apps will no longer work. Titanium Backup, Root Explorer, Team Blackout Updater, and SetCPU are some examples. Will I be able to say I'm not satisfied then? With the update it's no longer the phone I paid for, it's a locked down tight device that I can't run custom software on. Will I be able to exchange it for a different phone of equal value?
[Verizon Samsung Galaxy S 4] Au_A7:
Sorry for the dumb question but would this be too easy?
[Verizon Samsung Galaxy S 4] ozzzzysh:
Haha it's a little bit more complicated than that. :)

Look here is you wanna see the kind of exploits from the past.

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

It's like those..
[Verizon Samsung Galaxy S 4] elliwigy:
there is a root method for me7 therefore tb will still work as well as root explorer.. team blackout updater as well.. only one wouldnt work is setcpu since would have a stock kernel
[Verizon Samsung Galaxy S 4] jova33:
Blackout updater will also flash zips that can't be installed from .apk
[Verizon Samsung Galaxy S 4] Phatdawg:
I think it's about the bigger picture of how verizon and other companies keep on "breaking" our devices with updates. Since we functional devices that might have minor bugs, taking an update to fix those bugs may render our devices less effective due to the loss of root/recovery/bootloader.

This is going back to the argument about why some people may "soft brick" their phone to get a new one that might not have the update on it. Some feel that this is unethical and wrong. Others think it's justified under the circumstances.

The rooting community is small, and of those using other roms, even smaller, hence I think the people that return devices for the sake of root/recovery/bootloader is extremely small to the general population. Something verizon can easily absorb and insignificant, if it couldn't there would be more stringent control over the returns and post processing evaluation of the phone to see if you broke warranty -> which I don't believe I've heard people routinely been called out on.

So, I think it's all fair game. Verizon to me is basically a monopoly. They have the best service in general and they know it. They command a price premium, don't have unlimited data, and although we can buy phones off contract at full price that are unlocked -> you don't get a service discount. So as far as I'm concerned, verizon's business practice in itself locking a 650 dollar phone from full use is rather a problem in itself.

Due to my line of work, I don't have an alternative to Verizon's services - several answering services only consider verizon reliable enough to double their phones as text pagers otherwise I would have to have a pager AND a cell phone on my person.

I personally wouldn't return a device just for root/recovery as I know the community eventually finds a workaround or later on another update root becomes available some other way. However, some people _NEED_ root/recovery and I can't fault nor judge them if they decide they need to return their device.

To each their own.
[Verizon Samsung Galaxy S 4] Dubbsy:
I was linked to a post on twitter today claiming to have found a way around the bootloader issue. Time will tell if it is actually related to what we all hope it is related to.

https://twitter.com/P3Droid/status/377632762930290688
[Verizon Samsung Galaxy S 4] SamuriHL:
Woa. P3 doesn't mess around with nonsense, so, that should be taken quite seriously.
[Verizon Samsung Galaxy S 4] Dubbsy:
I just meant because of the lack of details that it may or may not mean what we want it to mean. Regardless, exciting and worth the share. :good:
[Verizon Samsung Galaxy S 4] SamuriHL:
Fair enough. Here's hoping for you guys and gals.
[Verizon Samsung Galaxy S 4] hollovoid:
Later tweet said will be made available at earliest convenience. Kind of exciting to see safe strap almost here and maybe a hint of another solution.

This phone has gotta be a beast rommed up.
[Verizon Samsung Galaxy S 4] stevey500:
Yeah, definitely exciting! I know Hashcode is going wild with safestrap with a (re-)bootable(not quite cold bootable yet) for the S4 locked bootloader variants. Hmm dee dum, patiently we wait :D
[Verizon Samsung Galaxy S 4] krazy_smokezalot:
i hope we get a release by the end of my 14day return period as i bought the phone yesterday and im bummed out cuz i didnt know me7 didnt have a recovery option for it... but i know my guys in xda will crack this:good::good::good::good::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

another thread SUBSCRIBED
[Verizon Samsung Galaxy S 4] hollovoid:
To be honest tho, I got the phone after fully researching the situation, knew I may never get off of stock, but got it anyways because it is that good. A little debloating and nova made it good enough for me. If we do get unlocked, that would be great, if not, im not going to worry about it. Gotta admit tho, would be hard to do it for the money, because you know most aren't going to pony up. 1/3 of the bounty at most I would think.
[Verizon Samsung Galaxy S 4] Alxoom33:
P3Droid is a respected developer. I would listen and be very hopeful that his information is correct!

I do, hope to hear some good news soon.
[Verizon Samsung Galaxy S 4] SamuriHL:
Yea, I've not heard any more since he posted that. Not even sure who's working on the S4 bootloader issue.
[Verizon Samsung Galaxy S 4] SamuriHL:
ROFLMAO! If someone figured out another method for Loki then they definitely deserve the bounty.
[Verizon Samsung Galaxy S 4] thedanks:
I hope this amounts to something. My asurion replacement was an ME7. :(
[Verizon Samsung Galaxy S 4] epmacman:
Check out the bottom comment...