yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Erisnoob:
Exactly! I remember calling to ask why the droid incredible 4g was not available on the HTC Dev site for unlocking and they about lost their minds that I even knew what that was and that I wanted an unlocked boot loader. Ahh good times.
[Verizon Samsung Galaxy S 4] twiz0r:
Great source LOL
[Verizon Samsung Galaxy S 4] jova33:
This is going to end up on Gottabemobile.....
[Verizon Samsung Galaxy S 4] Jayrod76:
Hey...maybe he's one of their writers :rolleyes:
[Verizon Samsung Galaxy S 4] tee00max:
Well all this is over for me. Just traded my S4 for a brand new Note 2 plus some cash. Alresdy rooted. I will keep interest in this thread though
[Verizon Samsung Galaxy S 4] d.ouyang:
I'm an early contributor who has stayed quiet and hopeful. This latest rumor about an August update has cruelly gotten my hopes up in spite of logic, but... Why ever would these companies, with their track records, do something so helpful, magnanimous, and in complete reversal of what appears to be a very successful security crackdown? More likely this is wishful thinking, misinterpretation, or even misinformation. "I mean, don't bother with breaking the current update because the easy way is just around the corner - be patient, trust us..." or something like that. If we're such a small community, why would they make these changes to suit us? I imagine that releasing an update is a pretty big deal.

So, rooting...

I've read every post. Supposedly there is a method, but no details have been revealed while work continues on recovery and possible bootloader. The explanation is that once the exploit is revealed, Verizon will begin patching it. However, by extension that means that they will eventually try to patch the exploit no matter when it is revealed. I assume that no developer would take any update, so any attempt to repair a vulnerability would only affect future customers or warranty returns, which is inevitable in the long run. Current work with ME7 should be unaffected unless I'm missing something, and eventual attempts by Verizon or Samsung to block a new exploit are inevitable because the whole point is to publicly release and for us to all use such a method to take back control of our devices.

But if a root method is revealed sooner rather than later, we can disable OTA updates. We can disable updates! And prevent any more lockdowns while work continues on recovery and bootloader. And finally backup with Titanium, install rootkeeper just in case, maybe restore some sorely-needed apps+ data from the old broken phone ;)

Who is to say that ME7 won't immediately take and install an OTA update? Will we be able to defer it even once? Many of us tried to avoid ME7 and managed to get stuck with it in spite of best efforts. I *really* don't want that to happen again.

So here's my plea: Developers, please allow us to root and disable OTA updates. Let's get a bunch of us one step ahead for once. If there is a specific reason why not... Don't specify - I get it. But let us know that there actually is a reason. Stay anonymous and relay it through someone else in the thread if you wish. But please give us something concrete if a root method is indeed possible. People are returning phones, switching devices and carriers, or opting for the backordered 16GB developer edition.

16 just isn't enough on this device, even with apps2sd.

I suspect there are other people reading this thread who will be able to relax only when future updates are disabled.

Comments?

Sent using Tapatalk 4 Beta
[Verizon Samsung Galaxy S 4] Rebel908:
I believe at least for the camera its tied to the Firmware that locks the device. So no firmware, no camera AND no wifi
[Verizon Samsung Galaxy S 4] BeansTown106:
Yes they blacklisted the kernel just like they did on the verizon note2. I know there was a way around it on note2 though not sure whatbit was youd need [MENTION=3682533]AdamOutler[/MENTION] to clarify how they did it

Ps im sure sxtps production aboot could help but hes mad at xda :/
[Verizon Samsung Galaxy S 4] Delakit:
Throw me in for $10.
[Verizon Samsung Galaxy S 4] garwynn:
Sextape's not mad at XDA - just not coming around.

Think it's a matter of getting burned too many times by only a few.

When that happened before with kernel how about recovery?

Maybe that can be our way in if we can get Loki to play nice....
[Verizon Samsung Galaxy S 4] jcase:
Ralekdev downgraded the bootloaders I believe.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
If I recall correctly, on the Note II [MENTION=3682533]AdamOutler[/MENTION] was able to exploit the PIT file to be able to flash anything to the aboot partition. Granted it is an Exynos-based device unlike ours as Qualcomm.
[Verizon Samsung Galaxy S 4] garwynn:
Well, again, while we sort this out I think it's better that I continue on with what I was going to do first - get an ME7 Odin package together that has only what's needed to update. Modem, NON-HLOS, system, boot. Everything else leave it for now. That way folks can still go to ME7 without losing what they have now... and I can then go back to focusing on helping fix those already stuck on ME7.
[Verizon Samsung Galaxy S 4] jcase:
It was Ralekdev
[Verizon Samsung Galaxy S 4] BeansTown106:
Wifi dont work without the new sbl2 and sbl3. Trust me I arleady did this and now my device is being jtagged. I dont think the new sbls liked not having the new aboot :/ I initially flashed modem, nnhlos, rpm and tz and still no wifi so then I flashed the sbls and wifi started working but first time I rebooted the device didnt turn back on. I triple checked partitions and had all the files sha1 verified

Edit only reason I tried the sbls is because thats what we do on verizon s3 we update "EVERYTHING" but the aboot. Seems like they caught on to that :/ but if u get it working all the power to you im just warning you you might have to send your phone out to get fixed. I could have messed up but like I said I triple checked partitions and had all the files sha1 verified on flash
[Verizon Samsung Galaxy S 4] garwynn:
Thanks for the heads-up. Guess it's hard to tell while your phone is in the shop but was it narrowed down whether that was a kernel or ROM issue? (Taking notes furiously on this topic)
[Verizon Samsung Galaxy S 4] BeansTown106:
Yea it was where is our good old friend [MENTION=2918486]Ralekdev[/MENTION] lol

---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------

I didnt look into it farther than knowing I needed more of the bootchain to make it work as its happened on the s3 woth wifi and camera when either the trustzone or sbls werent updated
[Verizon Samsung Galaxy S 4] mikeyinid:
SECURE MAGICCODE CHECK FAIL : boot

Thats the error i get on my phone when flashing just boot.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
I was going to make a method available two days ago for everyone who didn't update to update without locking down their bootloader (I had a thread up and ready and was going to upload the files), but after further consideration I decided against it: http://xdaforums.com/showpost.php?p=43432953&postcount=186

EDIT: Two main reasons because I'm not able to verify on my own device and after further talks with a few folks if not tested first there is a good chance of a hard brick due to the requirement of the new aboot, and also on top of all that it would take focus away from finding a root method for those that already did the update.
[Verizon Samsung Galaxy S 4] csimms:
Could we get bootloader from the delevopers edition like they did the htc one?
[Verizon Samsung Galaxy S 4] dadsterflip:
I was thinking this. Since I was lurking on the HTC one thread. But I don't know much in what's involved.
[Verizon Samsung Galaxy S 4] Rebel908:
I think its more of a lack signature verification rather than a different bootloader
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Was attempted on the Verizon Galaxy S III before and failed with no surprise. That would be too obvious/easy and of Verizon and Samsung already know about that possibility.
[Verizon Samsung Galaxy S 4] dobo84:
Im sure some one already has there gears turning on this.
[Verizon Samsung Galaxy S 4] csimms:
Yeah i figured that just thought i would throw it out there
[Verizon Samsung Galaxy S 4] Rebel908:
Has anyone looked into the AT&T folks yet? There in the same boat as us, although it pretty much seems like there as far as we are, selectively updating parts
[Verizon Samsung Galaxy S 4] Tada10:
I'd be happy with just root but the way things are going everyone probably just gave up. I lost hope with the posibility.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] matt_1224:
And this is why I switched phones again
[Verizon Samsung Galaxy S 4] r_hippy:
I read this bootloader lock out is part of lojack. And just seen this today

http://www.androidheadlines.com/2013/07/the-fbi-might-be-looking-into-the-galaxy-to-replace-blackber

Figures
[Verizon Samsung Galaxy S 4] udmatador:
Well some of us haven't given up on at least root yet. If root isnt achieved by October or November im going to get a dev edition and maybe just hand this one off to the girlfriend as a bday/xmas present. Rooted or not I do love this phone and rooting/flashing is more of a luxury to me. Im bummed the sales person at the store pushed the update while i was there, but I still smile every time unlock the screen. :)
[Verizon Samsung Galaxy S 4] AshyKnuttz:
I refuse to believe noone out there is capable of getting this rooted, specially with this bounty. Even the Motorola Droid Maxx HD was rooted, this device, I'm sure, has way more developers working on it than that motorola did...
[Verizon Samsung Galaxy S 4] KidJoe:
NOt sure I believe the article, as I haven't seen it reported any place else yet... But one thing is true.. Samsung's KNOX is an added layer of "enterprise security" and mobile device management. Its meant to make their phones more secure.

But its a similar idea Moto had a while back...

In fact.. all this dates back a few years.. see -> http://www.itworld.com/security/136...androids-enterprise-weaknesses-without-google
[Verizon Samsung Galaxy S 4] open1your1eyes0:
For the record, I want everyone to know (including developers and security experts who have root working and waiting for recovery), you may release your working root methods at anytime upon your choosing to help out those folks who do not need recovery or an unlocked bootloader. Once we have root, the first person to release a recovery or unlocked bootloader AND recovery method will be the one awarded the appropriate bounty for that category. Until then there is nothing to hold back from releasing a simple root method. Just want to clarify for everyone in case someone is waiting for something.
[Verizon Samsung Galaxy S 4] rdcamero:
It has been posted in this thread that root is not a problem to get.Every time some one ask for it to be released by the same line.Do not want to release it now and give Verizon a head start on a patch.Go ahead and release it and let people be able to block future ota updates and at least be able to use their apps that require root again.

In the past as soon as a way to root was found it was made available.The people who know the method may not want to go against the grain and face possibly being blacklisted by the dev community.I think this bounty was a good idea at first but I have to wonder if it is holding things back now.

In the past most devs seemed to offer root and recovery methods just because they wanted to prove they could.They enjoyed doing something that was not supposed to be possible as well as helping out the community.I know people like money but it seems that if the only reason someone has to work on this is the money and not the reasons root and recovery have been made available in they past they need to find something else to do that they enjoy.
[Verizon Samsung Galaxy S 4] droidstyle:
no worries...:good:
[Verizon Samsung Galaxy S 4] ddemlong:
This :good:
[Verizon Samsung Galaxy S 4] AshyKnuttz:
I'd be happy with just root. I just want to at least be able to get rid of all these damn bloatware apps! so annoying. :mad:
[Verizon Samsung Galaxy S 4] SamuriHL:
The current version isn't and won't be as Dan (author of motochopper) quit the exploit finding game.
[Verizon Samsung Galaxy S 4] jcase:
Yeah because Dan is the only person who has ever written a root exploit for an Android </sarcasm>
[Verizon Samsung Galaxy S 4] jcase:
Holding roots has nothing to do with the bounty, I don't think anyone (*edit* that I know personally) who is working on this even gives a hoot about it. If you want to complain about how people operate with their time, they property (code/exploit etc) then I suggest you take it up yourself and work on it. I'm more than willing to point people to starting places on Android security research.
[Verizon Samsung Galaxy S 4] ncope562:
Okay maybe dum idea but what if you made a kernel that was dated as newer (eg ME8) that allows flashing of recovery and routing then flash back to ME7 or to custom one if you want after. Kinda like prior work around only future kernel Onsted of pre release one... Not that I know how to make this happen.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] Tada10:
Thats what Spock did with the red matter so why not apply it here.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Cruiserdude:
I'm curious at the method Samsung themselves would use to revert a device to older firmware, would this be done through JTAG, or require a Samsung Anyway rig? I understand that if they wished to flash an engineering bootloader, they could simply sign it with their newer key, which obviously isn't a realistic option for us, nor is there any realistic expectation of such a thing being created then leaking out. But I would think they'd have some way of reverting their own hardware to an older software, and I'm wondering if this may open some avenues for us?
[Verizon Samsung Galaxy S 4] jcase:
No way to sign it
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
its only been 13 days....you couldnt wait any longer?!.....i sold my Note 2 for $450 on Craigslist (Long Island NY) and bought this 16gb white S4 from someone who needed to sell immediately for $420 on Craigslist.... i acually made $30 on the deal

---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------

Jcase....didn't AT&T receive a very very similar update to our S4? If someone were to crack it on that phone would that be applicable and / or helpful in any way towards our device?
[Verizon Samsung Galaxy S 4] jcase:
Similar update, but i don't think anyone published anything
[Verizon Samsung Galaxy S 4] JamesPumaEnjoi:
OK was just wondering at least it gives us double the shot at it

---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------

Thanks
[Verizon Samsung Galaxy S 4] sokrboot:
Would it be possible to use another phone as a boot workaround? I have a Droid 1 which can be modded/hacked in a million ways. Could a smart person flash MDK on that then sideload or maybe run boot from one phone to another like booting ur computer from usb or something. OR maybe put rooted ME7 on Droid 1 then use that to do the same thing.

Probably been thought of but I figure id throw it out there.
[Verizon Samsung Galaxy S 4] Gunthermic:
Couldn't have said it any better. If it's not fast enough, then learn how to do it, so you can share faster.. Luv it!

Relax all... it will happen, but stomping feet, and claimign they are holdign it just to piss you off, doesn't make it come out faster..

Ever watch a pot of water boil? LOL
[Verizon Samsung Galaxy S 4] SamuriHL:
No but he seems to be the only one who's done so for Motorola devices in a very long time. Unless of course you know something I don't?
[Verizon Samsung Galaxy S 4] coldhardtruth:
And to think one simple Google search before taking the update could have saved all these IDIOTS a lot of time and money. It's not like this is the first device Verizon has locked root with an OTA...

Crying about how long it takes to fix their ignorance. LOL :rolleyes:
[Verizon Samsung Galaxy S 4] riker147:
This was a very helpful and informative post. Thank You. :rolleyes::rolleyes::rolleyes:
[Verizon Samsung Galaxy S 4] rushless:
Not hugged much?
[Verizon Samsung Galaxy S 4] Rhodesy757:
so has there been any recent updates? are there any fixes anyone is currently working on?
[Verizon Samsung Galaxy S 4] open1your1eyes0:
First Samsung device however with the fact that this time around even using official firmware to downgrade is blocked (the whole issue here and reason starting this thread was necessary). But regardless as others have stated, please do not spend time on a post if your post is only going to contain insults. We need support here not criticism. What's done is done and I'm sure everyone here knows the mistake they made (even though to what extent this was a bit surprising).

Current situation summary as far as I'm seeing

: Root is had just being waited on for a proper recovery method. Recovery method status is unknown at this time, last I have heard it was had but very inconveniently and not at all close to release of a useful method, but the idea is there. Unlock of bootloader status: unless something official from Samsung, it is looking very unlikely at this point due to the level of lockdown on this update.
[Verizon Samsung Galaxy S 4] tee00max:
Well I just thought the Note 2 for my use was a better device for me. I didn't use any of the motion or air view functions and the battery life is insane. I can give up the 13mp camera and 1080 display.
[Verizon Samsung Galaxy S 4] djrbliss:
Seriously, this is ridiculous. The only real excuse is if someone bought or otherwise received a new device with the new update already on it.

When Motochopper was published, I included this warning:

When Loki was published, I included this warning:

This is not the first Samsung device to be locked on Verizon (see Galaxy S3 and Galaxy Note 2). This is not the first device capable of preventing downgrading. You're allowed to be upset at these restrictions, but you shouldn't be surprised, because the reality is most of the people in this thread just weren't paying attention and paid the price for ignoring what people have repeatedly warned. You should have known this device was going to be locked in the first place, and you should have known that applying an OTA update would prevent rooting or using Loki. Ignorance is no excuse.

As for achieving root, I'd say it's fairly embarrassing that at least two public exploits will work on this device, and no one can even get those working. Hint: the perf_event_open() exploit and the second Android "master key" exploit both affect this device. If the entire community can't even get two existing exploits working for a device, I don't have a lot of faith in its ability to find and exploit a new flaw in the bootloader.
[Verizon Samsung Galaxy S 4] whizdumb:
Almost seems like those exploit warnings gave Samsung/Verizon everything they needed to design an OTA that would really screw us over.. My $0.02
[Verizon Samsung Galaxy S 4] coldhardtruth:
Exactly!!

The ignorant are ALWAYS surprised and make up excuses of how it wasn't their fault. :rolleyes:

OP, you and your horde are offering over 3gs to fix YOUR mistakes. That is ridiculous and hilarious in itself. If you're not prepared to be ridiculed by the obvious, you have much bigger problems than taking an OTA...
[Verizon Samsung Galaxy S 4] soocold:
Schooling the community even in retirement. Love your work Dan.
[Verizon Samsung Galaxy S 4] Erisnoob:
Think you are missing the point, you may be in this situation due to a warranty return/replacement in the future. Some already have all the goodness but would like to get it back in the event life happens and have a replacement phone that is locked down.

edit: However I do agree that if an individual willingly took the OTA and is now crying for lack of exlpoit then lesson learned. I don't see the point in testing if the new OTA breaks root/locks down phone, on VZW the answer is yes it will. I do support hacking the latest releases though to free future devices that come from returns, purchases, etc...
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Hey Dan,

Glad to see you checking in occasionally on the status of this thread. Just wanted to clarify on a few points you have noted here.

Regarding Motochopper

: It was already known that this root method was not working on the stock Verizon Galaxy S4 from the very start so no surprises there and I don't think anyone expected it to work on the update as well in the same stock scenario.

Regarding Loki Method

: Perhaps this one was less expected but at the same time also not surprising since this was just a soft workaround and it was obvious how easily this can be patched from the very start (which is why it gained a lot of criticism upon release). The only question was whether or not the carriers/Samsung were actually going to notice and do something about it. Obviously we know the answer to that now but we haven't gotten to this step yet to be upset about it seeing as how we can't even get the above.

Regarding Lockdown

: True and obvious that the Galaxy S III and Note II were both devices that were locked on Verizon but thanks to always being able to downgrade back to an older firmware (based on history of how Samsung devices worked in the past) that was not so much a concern.

Regarding Root

: Not sure if you have read through the entire thread (most likely not and not expected of course) but it is already clear that a working root method is already had using a few exploits. The only issue here is it is being withheld for a number of reasons by the creator(s).

The very key issue here is two very small things in fact that might not be so obvious to many folks.

Firstly, flashing the pre-release kernel to gain access back to the Motochopper method to work again was blocked with this update. I cannot speak from personal experience on the Note II since I never owned the device but based on the condition of the Galaxy S III (even on Verizon) and past Samsung devices this is somewhat unexpected especially for the low-level lockdown nature of this update.

Secondly, even if you would think the first point is not too surprising, the fact that this update even prevented flashing back to a full official factory image of the same build that this device came out-of-box on is really indeed a shocker (once again based on experience of Galaxy S III and past). If we had this ability still then we would have no issues and everything of the above including the whole point of this thread would be completely unnecessary as we could easily work our way back. This is really a category of lockdown you would normally expect from a Motorola device but NEVER a Samsung. I guess now that we know I don't think we should be surprised with anything going forward but this is indeed a "first of its kind" lockdown for a Samsung device.

Just wanted to respectfully clarify a few of the above points regarding which were surprising and which weren't.
[Verizon Samsung Galaxy S 4] coldhardtruth:
Well if it's not apparent already, some things are just out of your control. Can't sweat what you can't control. If you're unfortunate enough to be in that situation, I could see a reason to donate. I think though, you represent a small percentage of people donating.
[Verizon Samsung Galaxy S 4] livinginkaos:
Point is, you want root AND the ability to keep it-buy an unlocked device . The warrantee situation just amplifies that . Does this limit your choice in devices - sure, but if root is priority, then its a sacrifice you have to accept. Dan has posted with every exploit I've seen the warning. All I can say is heed..... and thanks Dan for what you have done and taught the community.