Database Info

official 4.3 update att l337

spoke to supervisor at att and said 4.3 is att and is n testin and will b released this week comin up about 500 to 600 mb download so get ready .ps those will get notified thru text for upgrade and others will get it the next day so there wont b no errors n the download and no overloadin the system yadaya...and more bloatware aswell from att but hey we get wat we pay for so get ure phone prepared and clean it good so u wont miss any files or uno
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

If there is going to be an update, we all should be prepared to see its affects on rooting and recoveries, I don't want another MF3 nightmare- again.
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4

I will not trust too much AT&T guys! From my experience they are not too many people knowing when the update will be release. Well lets keep the hopes up and freeze the update to not lose the root!
Sent from my Galaxy Nexus using xda app-developers app

The Canadians haven't received it yet (though it is slated for October) and you expect people to believe AT&T will be releasing it this week? I guess it could happen, but I've yet to see any convincing evidence. Anyone working at AT&T should not be considered a good source for anything. Regardless, don't touch it until it is checked out by those that know what they are doing. Of course, the same "challenged" people that screwed up with MF3 (and continue to do so) will do the same with 4.3 no matter what kind of warnings people post. Some people just don't know how to read and never learn from their mistakes.

scott14719 said:
The Canadians haven't received it yet (though it is slated for October) and you expect people to believe AT&T will be releasing it this week? I guess it could happen, but I've yet to see any convincing evidence. Anyone working at AT&T should not be considered a good source for anything. Regardless, don't touch it until it is checked out by those that know what they are doing. Of course, the same "challenged" people that screwed up with MF3 (and continue to do so) will do the same with 4.3 no matter what kind of warnings people post. Some people just don't know how to read and never learn from their mistakes.
Click to expand...
Click to collapse
Well my phone auto updated, so not everyone who upgraded to MF3 did it on their own, it just happened with mine, now I know to freeze those processes with titanium backup

Kingo root might still work for it. It worked for mf3 baseband with one-click root.
Sent from my SGH-I337 using xda app-developers app

It'll be locked down tighter than mf3. Each new version will patch the previous versions vulnerabilities.

ACardAttack said:
Well my phone auto updated, so not everyone who upgraded to MF3 did it on their own, it just happened with mine, now I know to freeze those processes with titanium backup
Click to expand...
Click to collapse
It was posted several times well before MF3 was ever released:
A. Do not take the MF3 update until it was checked out (unless you don't care about modding).
and
B. A couple of ways to prevent the update, automatic or not.
It was then reported / posted several times directly after MF3 started pushing (within 1 day) that it would auto-update and exact instructions were provided on how to keep it from doing so.
There are no excuses, just lack of reading.
Like I said, if you don't care about changing or modding your phone than it doesn't matter, but if you are here at XDA in the first place, it means you DO want to do things to your phone and therefore, there is no excuse for not knowing about the updates, what to do or not to do with them, and how to prevent them if needed. The only reason for this is not reading.
Personally, I don't care. I know what to do for my phone because I search, learn, and read. However, the dozens and dozens of people that come running here crying for help when they should have helped themselves is annoying. It's sad when people take the time to provide information in an informative and easily understandable way and others just ignore it and then want to blame others because they did so. And that is exactly what happens...again, no excuses.
If people would read THIS, I am telling them NOT to update before the update is checked out to see what it changes and effects. The thread title is, "OFFICIAL 4.3 UPDATE AT&T I337". That is all the information that is needed for a search here at XDA, on Google, or even a simple visual search. If anyone puts ANY minimal effort into it, they can see what I have posted here. But, that is the problem, people are too lazy and to entitled to do anything on their own to take responsibility for what they do to their phones. They would rather call the people that follow XDA rules and take responsibility for what they do names like "****" or "Condescending" when it is pointed out to them where to learn about what they want to do and what they should have done to begin with.
So, here it is if you want to ever MOD your phone again in any way:
DO NOT TAKE THE AT&T 4.3 UPDATE (OR ANY OTHER UPDATES) OR ALLOW YOUR PHONE TO AUTO-UPDATE UNTIL THE DEVS AT XDA HAVE A CHANCE TO CHECK THE UPDATE OUT TO SEE WHAT IT CHANGES!
If you do, it is your own damn fault...take responsibility for it!

jd1639 said:
It'll be locked down tighter than mf3. Each new version will patch the previous versions vulnerabilities.
Click to expand...
Click to collapse
Sigh... so true. That's why I will never outright buy a phone from AT&T again.
Will be getting a GPE phone if I go with another Galaxy.
To keep it on topic, I'm with the others on this, I don't put my faith in employees at AT&T. Sure it's possible the update could drop this week... but either way I won't be updating any time soon.

scott14719 said:
It was posted several times well before MF3 was ever released:
There are no excuses, just lack of reading.
Click to expand...
Click to collapse
No excuses you know, unless you don't frequent forums like this and it just happened....

ACardAttack said:
No excuses you know, unless you don't frequent forums like this and it just happened....
Click to expand...
Click to collapse
scott14719 said:
Like I said, if you don't care about changing or modding your phone than it doesn't matter, but if you are here at XDA in the first place, it means you DO want to do things to your phone and therefore, there is no excuse for not knowing about the updates, what to do or not to do with them, and how to prevent them if needed. The only reason for this is not reading.
...take responsibility for it!
Click to expand...
Click to collapse
..

scott14719 said:
..
Click to expand...
Click to collapse
I come here once and awhile, not in my wildest dreams did I expect a forced over the air update to come, even apple doesn't pull that...so people who like to have a rooted phone does not mean they frequent this site often

ACardAttack said:
I come here once and awhile, not in my wildest dreams did I expect a forced over the air update to come, even apple doesn't pull that...so people who like to have a rooted phone does not mean they frequent this site often
Click to expand...
Click to collapse
I agree that it is a crappy tactic from AT&T, but the fact that your phone updated is completely your fault. The XDA rules state, "To search before you post". That is the first thing you should do when coming here for any information. The second thing is to read the "pinned" threads in the General and Q & A sections. It doesn't matter if you come here for something once or 100 times, it is still your responsibility to do so. What happens to your phone is ONLY your responsibility. Some things can not be fixed, changed, or controlled. The phone updating is not one of those things. Your phone auto- updated because you did not learn about it being able to do so. If you signed any paperwork with AT&T I guarantee you signed a waver that said they can and will modify your software at any time with or without any further consent. It's your fault if you didn't read it.
There are plenty of people around here that were born with the same knowledge about phones, and Android, and Modding that you and I were born with. But those people (and myself) took the time to learn about their phones and took responsibility for what they wanted to do to their phones. They didn't come to XDA, ignore all of the rules, and make a user account just to ask a question about something they did wrong to start with. Instead, they came here, read the rules, agreed to them, made a user account, and proceeded to search, read, and learn about their device. Many of them then went on to start modifying and developing so others could benefit from their time and actions. Not everyone achieves that level of knowledge but everyone IS expected to follow the rules, search, read, and learn. In other words, like I said, there are no excuses. Everything involving what has or will happen to your phone is your (and only your) responsibility. Just like it is for everyone else and their phone.

one of the first things I do after rooting a device is to freeze all the bloat AND any ota or updates. when an update starts to come , immediately hit airplane mode and don't disable it until figuring out how to kill the update.
don't play the modding game without fully understanding what you're doing.

Russ77 said:
one of the first things I do after rooting a device is to freeze all the bloat AND any ota or updates. when an update starts to come , immediately hit airplane mode and don't disable it until figuring out how to kill the update.
don't play the modding game without fully understanding what you're doing.
Click to expand...
Click to collapse
With the MF3 update.. It seems the 3 Required apps to freeze the OTA are not all there. 1 Of them has a different name under my phone. It seems to be now listed as AllShare Cast Dongle S/W. Can someone confirm that this is indeed the third piece of the puzzle to freeze updates? Has this any affect to AllShare feature?
I tried searching around, but everything seems to point to only blocking the update prior to MF3. Nothing notes the new changes. And I guess is there any real point in stopping the next update? Seeing as LOKI is the only real(no limitations) solution to the bootloader lock?
Is there anyone working on the bootloader for MF3?
Thanks!

scott14719 said:
I agree that it is a crappy tactic from AT&T, but the fact that your phone updated is completely your fault. The XDA rules state, "To search before you post". That is the first thing you should do when coming here for any information. The second thing is to read the "pinned" threads in the General and Q & A sections. It doesn't matter if you come here for something once or 100 times, it is still your responsibility to do so. What happens to your phone is ONLY your responsibility. Some things can not be fixed, changed, or controlled. The phone updating is not one of those things. Your phone auto- updated because you did not learn about it being able to do so. If you signed any paperwork with AT&T I guarantee you signed a waver that said they can and will modify your software at any time with or without any further consent. It's your fault if you didn't read it.
There are plenty of people around here that were born with the same knowledge about phones, and Android, and Modding that you and I were born with. But those people (and myself) took the time to learn about their phones and took responsibility for what they wanted to do to their phones. They didn't come to XDA, ignore all of the rules, and make a user account just to ask a question about something they did wrong to start with. Instead, they came here, read the rules, agreed to them, made a user account, and proceeded to search, read, and learn about their device. Many of them then went on to start modifying and developing so others could benefit from their time and actions. Not everyone achieves that level of knowledge but everyone IS expected to follow the rules, search, read, and learn. In other words, like I said, there are no excuses. Everything involving what has or will happen to your phone is your (and only your) responsibility. Just like it is for everyone else and their phone.
Click to expand...
Click to collapse
I disagree it is the users fault. Mine did the same thing. By the time I left the store mine was already updating on its own. It's not like you can root while you are at the store. I have rooted every Android I have owned but never had a device update on its own until this S4.
Sent from my SAMSUNG-SGH-I337 using Tapatalk now Free

jdog_12345 said:
I disagree it is the users fault. Mine did the same thing. By the time I left the store mine was already updating on its own. It's not like you can root while you are at the store. I have rooted every Android I have owned but never had a device update on its own until this S4.
Sent from my SAMSUNG-SGH-I337 using Tapatalk now Free
Click to expand...
Click to collapse
It's difficult to predict a phone updating before you leave the store you bought it at. That is probably one of the few excuses that would be legitimate. It's still your responsibility to research the phone before you buy to see what it might or might not do, but even then it's difficult to do anything about it that quickly. It was posted several times to not put the sim card into the phone before you could take steps to prevent the update but sometimes it's just not possible. Blaming it on "other" phones you have had not auto-updating is just an excuse. This isn't those other phones and it is / was still your responsibility to research and learn about THIS phone before you took ownership. It is simply no one else's fault that you didn't read and learn. You might feel like you didn't need to or shouldn't have to but that doesn't change the fact that the information was out there, you just didn't seek it. However, like I said, even if you would have, it still might have been difficult to stop it in your particular situation.
Most people (99.9%) of people that throw around excuses are solely to blame for the phone updating (or anything else that happens to it). It is completely their responsibility, they just want to blame someone or something else. Using, "I didn't know" or ,"Who would expect the phone to do that", as an excuse when as much information exists about it as does, is just an attempt at not taking responsibility. Some people take responsibility for their actions and have no trouble stepping up and admitting something happened because of their actions or lack there-of. Others, always want to blame someone else.

If anyone is keeping score I am one of the (apparently rare) folks who reads this forum but has no intention of rooting or modding or hacking etc my phone.
But thanks to this forum I learned which of the att and Samsung apps I could safely disable.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

scott14719 said:
Most people (99.9%) of people that throw around excuses are solely to blame for the phone updating (or anything else that happens to it). It is completely their responsibility, they just want to blame someone or something else. Using, "I didn't know" or ,"Who would expect the phone to do that", as an excuse when as much information exists about it as does, is just an attempt at not taking responsibility. Some people take responsibility for their actions and have no trouble stepping up and admitting something happened because of their actions or lack there-of. Others, always want to blame someone else.
Click to expand...
Click to collapse
Its not like an iphone where you have to tell it to update, it just happened, I had an iphone for 4 years, never once did I update until there was a jailbreak and I know I can't be the only one, I rooted, tried a few custom roms, didnt like them and never came back to this site until my phone updated itself. So I'd just get off your high horse because well putting down people to make one feel better isn't a great trait to have.

There will be NO 4.3 update for ATT before the INTL peeps get it, I am telling you now, att will not have one till way after the 1st of the year....
That ATT rep is full of .....need I say more...

Bootloader unlocking discussion thread

I made this thread to try and get the get the flame burning again on this topic. It seems since we've achieved safestrap people don't seem too interested in pursuing an unlocked bootloader. I understand that if i want AOSP i should try trading my phone for one with an unlocked bootloader (knowing that somebody is going to comment saying that). But what does that do for the community? Nothing productive. Speaking theoretically here, how is a bootloader unlock achieved with the bootloader lock key? Is there some way of inputting it to unlock the bootloader? What happens if you have the wrong key? Is there a way to create script a keygen that goes through every possibility of however many digit of a code the bootloader lock key is? Or can it only be done via exploit?
Thank you very much for taking the time to read this. Let the discussion begin.

Travisholt92 said:
I made this thread to try and get the get the flame burning again on this topic. It seems since we've achieved safestrap people don't seem too interested in pursuing an unlocked bootloader. I understand that if i want AOSP i should try trading my phone for one with an unlocked bootloader (knowing that somebody is going to comment saying that). But what does that do for the community? Nothing productive. Speaking theoretically here, how is a bootloader unlock achieved with the bootloader lock key? Is there some way of inputting it to unlock the bootloader? What happens if you have the wrong key? Is there a way to create script a keygen that goes through every possibility of however many digit of a code the bootloader lock key is? Or can it only be done via exploit?
Thank you very much for taking the time to read this. Let the discussion begin.
Click to expand...
Click to collapse
If you took the time to read the numerous discussions on this you'd know the answers. People are dropping the unlocked bootloader since even the S4's hasn't been unlocked (since MDK baseband). Regarding the five key questions, it would take a super computer thousands of years to try every possibility. Wrong one would equal bricked phone. Exploit would be only way, and now that Geohot works for Google, he's out of the picture and I'm sure the other Devs aren't going to bother. SS is fine for now, you can always switch carriers if you care that much.

So the community on this device will never progress. Awesome.

Travisholt92 said:
So the community on this device will never progress. Awesome.
Click to expand...
Click to collapse
That is a real possibility. Now with this lesson learned, look for a carrier or device next time that does not lock the bootloader. HTC locks their bootloader but is good enough to provide us users with a way to unlock it. As mentioned, bootloaders are WAY different than obtaining root and there is a very real chance of killing the device in the trial and error process.

I feel where you are coming from i felt the same way. Switched for an HTC One m8 and besides the fact that the bootloader can be unlocked, it's just a much better phone. Should give it a shot! A GS5 is an equal trade for an m8 on craigslist so it shouldn't be too hard. It does seem the general consensus is that the dev's have given up on even trying to unlock it so i would just accept it and move on unfortunately.

Ulterior options to Sunshine for rooting

Hello all,
There was asimilar thread to this (which was short lived because it turned into nothing but a few little d-bags fighting like little girls) in the M8 non-specific carrier forum for conversation and information regarding potential other projects in progress for rooting the VZW M8 that is running 4.4.4 considering there is absolutely no options as of now... I for one have already decided to leave Verizon for this very reason, and if t_mobile is floating the bill for early termination...awesome! However I'm still stuck with the phone,which i love,but have never had a phone i couldn't root after one day of googling. So i want to know if anyone else is privvy to any info that I am not, it looks as though susunshine will be at least another 3 months. It seems there is easy too many geniuses out there to have jcase being the only one that has enough knowledge to do this, don't get me wrong, he is brilliant and very generous with his work but crap! This is aa pretty popular phone and lots of folks using VZW even though they suck for this kind thing, some have no choice and go to who offers the best reception in there area. Please post your thoughts.....
P.s. - as mentioned iam going to be having this VZW branded M8 AND I HAD heard there was a law passed stating that the carriers had to unlock the phones if the customer requested?? Anyone know about this, if so what do ineed to do?

As far as I know there is no progress on unlocking/s-off'ing 4.4.4 except for sunshine. It currently only works on 4.4.3 and below but it has been alluded to that future updates may support 4.4.4. You'll just have to wait and see.
Regarding the unlocking law, that's a different kind of "unlock". You're asking about unlocking your bootloader to allow you access to deeper levels of the phone's memory. That law was about being able to "carrier unlock" a phone to take it to another carrier which uses he same or overlapping frequencies.

It's unfortunate, but as far I can tell no new root method is working, and it might be a while until one is, as basically all other methods have been completely "fixed".

No one would be willing to burn an exploit right now knowing l is so close. Doing so right now would allow them to patch before l drops. We don't want or need that.

dottat said:
No one would be willing to burn an exploit right now knowing l is so close. Doing so right now would allow them to patch before l drops. We don't want or need that.
Click to expand...
Click to collapse
That completely makes sense, with L coming so soon they would be wasting their time and effort, as they may have one now but they do not want to release it because it would more than likely still work on L when its out and it would probably be a good while before an update after L so by waiting they are just being using good business sense.
But then again another dev or team could beat them to a crack, that is the good thing about a free society there is competition and no one owns the market at least not for long. I say bring on the competition lol.

M9guy said:
That completely makes sense, with L coming so soon they would be wasting their time and effort, as they may have one now but they do not want to release it because it would more than likely still work on L when its out and it would probably be a good while before an update after L so by waiting they are just being using good business sense.
But then again another dev or team could beat them to a crack, that is the good thing about a free society there is competition and no one owns the market at least not for long. I say bring on the competition lol.
Click to expand...
Click to collapse
Competition could lead to everyone who gets this phone with L being locked out if that's the case.

dottat said:
Competition could lead to everyone who gets this phone with L being locked out if that's the case.
Click to expand...
Click to collapse
I really doubt that because there are a lot of devs out there that all they want is the recognition for being the one to crack it and are not looking for financial gain.

M9guy said:
I really doubt that because there are a lot of devs out there that all they want is the recognition for being the one to crack it and are not looking for financial gain.
Click to expand...
Click to collapse
Once an exploit is burned its burned. If it is burned before L and it gets patched in L it means L gets delayed and everyone else gets locked out. It's a matter of the few versus the many. The fact they are NOT burning the exploit now because of this should tell you it's not about $.

dottat said:
Once an exploit is burned its burned. If it is burned before L and it gets patched in L it means L gets delayed and everyone else gets locked out. It's a matter of the few versus the many. The fact they are NOT burning the exploit now because of this should tell you it's not about $.
Click to expand...
Click to collapse
That does NOT mean it has nothing to do with $ because it would not be smart to release it now because there would be no gain giving away the crack then they would not make much $ because yes L would most likely patch it. The most financial gain would be to wait till after L because the next update would be a lot farther away, giving more time to collect.

M9guy said:
That does NOT mean it has nothing to do with $ because it would not be smart to release it now because there would be no gain giving away the crack then they would not make much $ because yes L would most likely patch it. The most financial gain would be to wait till after L because the next update would be a lot farther away, giving more time to collect.
Click to expand...
Click to collapse
Couple weeks of use versus couple months of use.

dottat said:
Couple weeks of use versus couple months of use.
This thread is no longer serving a purpose. You are upset after being locked out which I understand. Unless you come up with a method and exploit of your own I would suggest you cease this conversation as there won't be a happy ending.
Click to expand...
Click to collapse
I"am already unlocked I only responded to the posts already made, and I did not make this thread. No Iam not upset at all you stated your opinion and I did mine and we dont need to agree. I"am more than happy to cease the conversation that you started. I was only replying to the comments you posted replying to mine. I think we can both agree and both agree to disagree, after all we dont have to agree.
Thank you for your opinion and have a good day.

M9guy said:
I"am already unlocked I only responded to the posts already made, and I did not make this thread. No Iam not upset at all you stated your opinion and I did mine and we dont need to agree. I"am more than happy to cease the conversation that you started. I was only replying to the comments you posted replying to mine. I think we can both agree and both agree to disagree, after all we dont have to agree.
Thank you for your opinion and have a good day.
Click to expand...
Click to collapse
Agreed. Hopefully the wait for L isn't that long...and the issue becomes moot.

dottat said:
Agreed. Hopefully the wait for L isn't that long...and the issue becomes moot.
Click to expand...
Click to collapse
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.

M9guy said:
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.
Click to expand...
Click to collapse
I appreciate that. Nothing personal here either man.

M9guy said:
Sorry I apologize I forgot I did first reply to your post my bad. I respect everyone opinion and I"am not looking to get in to anything with anyone I think two people can have a difference of opinion and debate it without it being anything more.
Click to expand...
Click to collapse
Oh and for the record actually I have used your fixes on here quite a few times so I appreciate the things you put on here. I can respect someone and still debate with them and have a difference of opinion and as you can see if I make a mistake in something I do my best to correct it.

heck yes
There can always be a fruitful discussion without people agreeing, that is the way our forefathers did it, and as far as I know, they didn't kill one another, good thread.
Cheers

Except for that little incident 1861 - 1865.......

MOD's please delete this post.

Deleted...
Leaving Verizon.

Sharpie603 said:
Recently Verizon has shown their true colors. They do NOT want to give us control of a device that we bought and paid for. (That's like buying a radio that only plays Country).
In my eyes. If we pay you monthly then why do you care what we do with our device? We own it right?
However, after days of researching and very knowledgeable co-workers..... The solution is here.
ODIN 3.10. That's Correct. ODIN 3.10 has the ability to look past the locked bootloader and grant access to roll back. This was not made to be public but (Thank GOD) was leaked on Aug 26th.
You can download ODIN 3.10 here: http://www.theandroidsoul.com/download/download-odin-3-10-6/
I have not yet tried to root after rolling back to the BOA8 Kernel. Anyone want to test this out and let me know if you were able to root after downgrading?
Click to expand...
Click to collapse
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?

scadilla said:
So you were able to downgrade from OG5 to OA8, just by using the 3.10 version of ODIN? Has anybody else tried this yet?
Click to expand...
Click to collapse
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.

Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
I'm definitely following this thread!!! Thanks for the info Sharpie603!!! Man... I really hope you're successful!!! I'm ROOTing for you! (Pun intended! Damn I'm funny! No?!?! Anyone???) LOL

Sharpie603 said:
Just the Kernel, not the firmware. Which in reality.... Serves no purpose.... The bootloader still remains locked and prevents from downgrading the firmware. However, this method works for downgrading kernels...
I'm still looking into ways to obtain root with a downgraded kernel. Not saying it's possible, but I'm not giving up just yet.
Click to expand...
Click to collapse
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.

scadilla said:
Ah, OK, that makes sense so the thinking is if you are on OG5 with the locked bootloader that you could downgrade the kernel and then root. I'll be following closely as well.
Click to expand...
Click to collapse
Not looking very promising.

Can you downgrade APNHLOS?

Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.

In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.

Spartan117H3 said:
Terribly misleading title. OE1 and OG5 didn't do anything about locking the kernel, they were bootloader locks. As you said, unless you can downgrade which you can't. The only way this would be useful is if we could get root by only downgrading the kernel, which we cannot. We could access safestrap if we HAD root access, because we could flash the NI2 kernel to get access, but no root = no safestrap.
I don't think you made a discovery, I think you just came across what wasn't stated bluntly, simply because it wasn't necessary information to tell people. As for your quest to find a way to root.... I'm just going to say, have fun.
Click to expand...
Click to collapse
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...

KennyG123 said:
In regards to the OP's statement - Verizon could care less about the rooting community and allowing you to do what you want with your "owned" devices. Verizon and AT&T locked the phones down tight as they should because this is a portable personal computer with all your financial information being transferred back and forth. Tightening the security of the phone against hackers trying to steal all your information and identity had the unfortunate side effect of making root near impossible currently. The device performs exactly as advertised on the box and in the specifications. Your analogy of a radio stuck on country is a poor one. Think more like you bought a car and it will not go 200 miles an hour. There is nothing preventing you from purchasing a car that can, or replacing the engine to do so which would have other downfalls such as gas mileage going to crap. In the same analogy you can purchase a T-Mobile motherboard, swap it out, be able to root, but not get certain LTE bands. Verizon has not targeted you at all...you can blame the hackers constantly trying to get information off the phones. Verizon and AT&T took steps to try to prevent that and of course increase profits by being rated the most secure phones out there. Verizon never gave you the keys to root...ever! So they are not keeping this info from you. Just like every device that took a little time to find root, it is up to you and the developers to find away around it.
This is the same as saying Acme safe company is trying to keep you from being rich because they made their safes more secure.
Click to expand...
Click to collapse
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.

Sharpie603 said:
The title is not misleading at all. It does exactly what I described. Gives you the ability to downgrade the Kernel. and the Kernel only. I clearly mentioned this in post #3 that this still leaves the bootloader locked. then in later posts went on to mention that it looks like we are still SOL. Take it how you want, sorry for actively trying to find a solution...
Click to expand...
Click to collapse
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265

Spartan117H3 said:
It is misleading because you mark it as solved as if it was a puzzle that nobody else can figured out, like you had new information to provide. If I'm not mistaken, the kernel was never locked, and you can use any Odin to push a different kernel. It was never a question if the kernel was locked. So you didn't do anything except state what was redundant. The people who confirm that the bootloader is locked say so because it means you can't downgrade. They didn't say you can still downgrade the kernel because it's absolutely meaningless. That's like saying, the bootloader is locked, but you can still Odin and flash any file you want even if it doesn't work.
There are countless people like you in other threads who claim they're trying to find a way to root. Neither you nor I are smart enough to come up with an exploit, as I have detailed countless times before. So why don't we leave that up to the developers?
It doesn't matter if you don't care yourself, because you are not everyone. You are a single person. If you were everyone, obviously Verizon wouldn't make money off you, and wouldn't secure their phones. But this is flawed reasoning yet again.
A bad analogy shows you have flawed reasoning. It doesn't matter if you care or not, you don't have a problem with stating things that don't make sense, then by all means, continue (which I don't even have to say, because you do indeed continue).
Slander? Are you serious? You acknowledge the reason for his post, which claims you have a bad analogy, and explains why Verizon does what it does. Then you make an insane, baseless claim that says xda discourages root. Yet XDA was where the original root method was released in detail, with the newsworthy 18k bouty.
Why does he need to explain why it wouldn't work, when you yourself have already done that? It's the same when you responded to me. You answer your own question but then argue against people when they confirm with your latter findings that it doesn't work?
I don't understand why people like you are so happy to see 1 posters support you, but then immediately get hostile when anyone with any knowledge comes in to speak. You running from Verizon doesn't solve any problems and shows you weren't invested to begin with, which is fine, since you wouldn't have accomplished anything anyway. Unless you're claiming to be smarter than those who found the original root.
You want to know why it won't work? All these people have similar ideas to yours, they either want root, or want to "try" with little to no knowledge at all about what they are doing.
http://forum.xda-developers.com/showpost.php?p=62378933&postcount=19
http://forum.xda-developers.com/showpost.php?p=62380538&postcount=23
http://forum.xda-developers.com/verizon-galaxy-s5/help/vz-replacement-s5-oe1-t3190365
http://forum.xda-developers.com/ver...g5-verizon-t3192598/post62746265#post62746265
Click to expand...
Click to collapse
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck

Sharpie603 said:
Listen I came here thinking I found a way. In no way was trying to start a war among like minded individuals. All you are doing is trying to ream me out for what? For a mistake I made, thinking I had a solution? Way to be professional. Sorry for cluttering the forum. Sorry for everything I have done thus far. Sorry for bothering you sir. Sorry for not being as knowledgeable as you are. I'm sorry for everything! F*ck
Click to expand...
Click to collapse
The problem is, you just assume things without actually comprehending what people say. That's why you believe this is apparently a war. Ream you out? You miss the entire point, repeatedly. All it is is people telling you why your statements don't make any sense.

Sharpie603 said:
I'm not worried about my phone being hacked. I have nothing to hide. I do not bank online or make purchases online. If there is fraudulent activity on my bank account, my credit union will inform me. This is besides the fact. I could care less if I made a "bad" analogy. I'm not sitting here thinking "Hmmm I wonder if anyone will have a problem with this statement" when writing up a comment. Your paragraph is nothing but slander "Something XDA strongly discourages". A simple "I don't think this will work, and here's why" would of been suffice.
On a side note. I'm leaving Verizon so you won't have to worry about me trying to find root and help you guys out anymore.
Click to expand...
Click to collapse
As stated that is just YOU. 99.9% of people do not want their phone hacked or their identity stolen.
How is stating the facts slander? And I think I would know best what is encouraged here and what isn't. Now you are just lashing out for no reason and making no sense.
I guess we can close this as you wished. Thanks for trying.

{DEV NEEDED} Closer Than Ever To Root (Cutting Bloat from Bounty Thread)

Hey all. Currently, evilpotatoman has gotten us closer than ever to achieving root with our phones. He's out of commission at this time until his device back comes in, which could take 2 weeks or more. He has extended the torch to any dev who might be interested in taking a crack at it with his notes (included below). Reference the bounty thread here for details about the bootloader/root bounty information.
!!!!PLEASE DO NOT POST YOUR BOUNTY AMOUNTS HERE!!!! DO IT IN RAYLON00'S THREAD FOR CONTINUITY: http://forum.xda-developers.com/showthread.php?t=3339857
evilpotatoman said:
Here's where it's at, but first a few notes and thoughts;
A) Even after upsetting dm-verity, the system remained somewhat stable*
*The only issues I see are the system:custom message, an unlocked boot logo, and that the stock installer refuses to install anything but FOTAs or a sec_csc.zip flashed on the CACHE partition. If cleared, the system boots up normally​
B) It's extremely difficult to reverse dev this device - Every piece of secure-trust-knox-DRK-verity-crapola increases the chance of a misstep and ending up with a really nice IOT brick. Because of all this security, looking for buffer overflows and random execs would take ages. I focused on stupid programming mistakes, sifting through log files, much like I did when developing the original Note 3 recovery method.
C) The HOME_CSC partition file that seems to fail typical odin flashes -- It sets something permanent, like kind of hard-coding the verity keys. During my testing, I flashed one only to later realize that my CSC was then hard-coded to Chinese branding. Before that flash, I could mess around with the branding at will (and subsequently write to the system partition). It was only after I flashed that CSC_HOME that dm-verity actually failed. In short -- I had root BEFORE download mode labeled my system as custom. I flashed HOME_CSC, dm-verity then failed when I changed the CSC following the hard-code.
I have yet to fully re-create my EFS partition, and sent it to someone who wears darker hats than I for a fix. Because I won't have the phone for a while (at least 2 weeks), I've decided to give a brain dump in hopes that someone can pick up where I left off.
PM me for additional details, but the following should get better devs searching for a more stable method.
sec_csc.zips (found in cache.img.ext4) can be used to modify the system partition, and the partition itself isn't signed. Those zips also set the region.
*A particularly interesting csc zip exists for the G9300's CSC file.....
Odin happily flashes specific "partitions" individually, so piece-meal it out.
nand partitions can be written to while still failing in odin (but system.img is signed in 2 places, so fyi)
The exploit leverages those download-mode/recovery, plus the stupid programming error found below:
on the stock firmware, there's a boot script that calls a missing binary, which is a perfect -in- for the su daemon.
Click to expand...
Click to collapse
You can PM evilpotatoman here: http://forum.xda-developers.com/member.php?u=2322344

Very cool! This looks promising
Sent from my SM-G935P using Tapatalk

maybe @jcadduono can do something here?

Holy ****! This is big news!

seanvree said:
maybe @jcadduono can do something here?
Click to expand...
Click to collapse
He does not have a s7, so I doubt he can help much

Maybe jcase can work on boot loader and root
Sent from my Nexus 6 using Tapatalk

@jcase and @beaups come to mind.

I'd love to see this take off. To that effect, may I suggest contacting the dev you're wondering about and asking (POLITELY) if they intend to or are willing to contribute to this project?
Additionally, since we have nearly $2000 pledged for a root method, we can set up a fund to get the devices in the hands of the devs willing to work on the issue that may not have a device, starting with @evilpotatoman if he needs it. This might also give people who were apprehensive about contributing to the bounty another option to support this endeavor, and gives the rest of us a way to actively contribute instead of saying "here's your prize if you win."
Someone could even act as a third party to set up the fund (be it gofundme or something else, I need to research options). We may not all know how to fight on the front lines, but there are definitely ways the rest of us peons can actively support the effort instead of being passive and hoping it eventually happens because someone else did it.
Thoughts, suggestions, questions?

@jcase hacked the unhackable black phone.... I ask him on Twitter but he didn't say if he would have time to do it or not...
Sent from my Nexus 6 using Tapatalk

Tagging him won't help. I don't think he likes to tagged often. I'm talking about jcase. If he wants to he will. Since evilpotatoman has opened up this whole new scenario. I hope all the devs see it and try to put on their magic. But yes. I have my bet on jcase. Have seen his work from a while back. A mastermind I must admit.
Sent from my SM-G935T using XDA-Developers mobile app

Mew351 said:
Holy ****! This is big news!
Click to expand...
Click to collapse
No it isnt, this is exactly zero news.
That entire post is wrong, it is full of basic factual errors that make question if its a troll, or a misunderstanding of how these things work.
I may nitpick it when I get home if anyone disagrees with my evaluation of it, but a simple view:
a) messing with dm-verity wouldnt cause system stability issues at all, either it would boot or not.
b) reverse engineering this device is no harder than previous ones, there is no insane obfuscation or anything (just some simple obfuscation). Standard toolsets would work ehre.
c) The "custom" symbol is just a sign of tampering, in fact I could make a standard app to cause it. It wouldn't stop or remove root from a system.
The whole post in general is gibberish.

Dont start funds for developers who need phones, too many times it comes out bad.
We allow bounties, but funds need to be pledged not held by a single person, and they should not be paid out unless the project is completed, and posted (and is of primarily original work).
psych0r3bel said:
I'd love to see this take off. To that effect, may I suggest contacting the dev you're wondering about and asking (POLITELY) if they intend to or are willing to contribute to this project?
Additionally, since we have nearly $2000 pledged for a root method, we can set up a fund to get the devices in the hands of the devs willing to work on the issue that may not have a device, starting with @evilpotatoman if he needs it. This might also give people who were apprehensive about contributing to the bounty another option to support this endeavor, and gives the rest of us a way to actively contribute instead of saying "here's your prize if you win."
Someone could even act as a third party to set up the fund (be it gofundme or something else, I need to research options). We may not all know how to fight on the front lines, but there are definitely ways the rest of us peons can actively support the effort instead of being passive and hoping it eventually happens because someone else did it.
Thoughts, suggestions, questions?
Click to expand...
Click to collapse

jcase said:
Dont start funds for developers who need phones, too many times it comes out bad.
We allow bounties, but funds need to be pledged not held by a single person, and they should not be paid out unless the project is completed, and posted (and is of primarily original work).
Click to expand...
Click to collapse
Fair enough. I probably should have checked to see if there was any rule against this. Regardless, from a common sense standpoint you make...well, sense. Wrote myself into a corner there. >.>
As for the entire OP being gibberish...you're essentially saying we're back at square one, or is he at least barking up the right tree, in your opinion? As you can tell, I'm a little overzealous when it comes to this phone getting root lol.

jcase said:
No it isnt, this is exactly zero news.
That entire post is wrong, it is full of basic factual errors that make question if its a troll, or a misunderstanding of how these things work.
I may nitpick it when I get home if anyone disagrees with my evaluation of it, but a simple view:
a) messing with dm-verity wouldnt cause system stability issues at all, either it would boot or not.
b) reverse engineering this device is no harder than previous ones, there is no insane obfuscation or anything (just some simple obfuscation). Standard toolsets would work ehre.
c) The "custom" symbol is just a sign of tampering, in fact I could make a standard app to cause it. It wouldn't stop or remove root from a system.
The whole post in general is gibberish.
Click to expand...
Click to collapse
psych0r3bel said:
Fair enough. I probably should have checked to see if there was any rule against this. Regardless, from a common sense standpoint you make...well, sense. Wrote myself into a corner there. >.>
As for the entire OP being gibberish...you're essentially saying we're back at square one, or is he at least barking up the right tree, in your opinion? As you can tell, I'm a little overzealous when it comes to this phone getting root lol.
Click to expand...
Click to collapse
Well he did manage to get root so I don't know how it is all gibberish.

jakebake102 said:
Well he did manage to get root so I don't know how it is all gibberish.
Click to expand...
Click to collapse
I don't believe you or him on that. It is gibberish because its factually wrong, if it wasnt factually wrong I wouldnt have a reason to doubt someone in particular got root. When you make it apparent you are making stuff up or dont know what your talking about, it casts a major doubt.
Plus the proof shown, just showing that syscope got tripped, its not showing root, its not showing unlock, its literally showing nothing of any indication.

jakebake102 said:
Well he did manage to get root so I don't know how it is all gibberish.
Click to expand...
Click to collapse
It is possible to see and not understand. Often times an opinion held about the cause of a specific behavior in a complex system can be premature, and when new information comes to light suddenly all of the indicators that pointed to one cause suddenly mean something very different. The problem comes not with forming these theories about what causes a behavior, but in voicing that opinion before it is fully vetted out by your own tests.
In short, it is possible to be right about what you see, but wrong about what caused it.

jcase said:
I don't believe you or him on that. It is gibberish because its factually wrong, if it wasnt factually wrong I wouldnt have a reason to doubt someone in particular got root. When you make it apparent you are making stuff up or dont know what your talking about, it casts a major doubt.
Plus the proof shown, just showing that syscope got tripped, its not showing root, its not showing unlock, its literally showing nothing of any indication.
Click to expand...
Click to collapse
Ok well thanks for looking this over.

jakebake102 said:
Well he did manage to get root so I don't know how it is all gibberish.
Click to expand...
Click to collapse
Everyone beat me to it, but yeah. He said it, hasn't proven it. If he managed to get root, great. I gave him the benefit of the doubt, but now we have a known dev basically discrediting everything based upon his own expertise.
So from this point forward, the onus of proof is on the OP to prove he has/had root. Nothing a screenshot can't prove. It's entirely possible he did get root, but for a different reason than he stated, and posting his proof opens up the floor for a discussion on the exact process. The result doesn't produce the method, so maybe he stumbled upon root by chance in the midst of his work, which led him to think his method worked. Too many variables. That's why we discuss these things.

jcase said:
No it isnt, this is exactly zero news.
That entire post is wrong, it is full of basic factual errors that make question if its a troll, or a misunderstanding of how these things work.
I may nitpick it when I get home if anyone disagrees with my evaluation of it, but a simple view:
a) messing with dm-verity wouldnt cause system stability issues at all, either it would boot or not.
b) reverse engineering this device is no harder than previous ones, there is no insane obfuscation or anything (just some simple obfuscation). Standard toolsets would work ehre.
c) The "custom" symbol is just a sign of tampering, in fact I could make a standard app to cause it. It wouldn't stop or remove root from a system.
The whole post in general is gibberish.
Click to expand...
Click to collapse
Hey jcase (I know you from the old days on XDA, just a bit undercover now for XDA reasons.) Anyway, please don't let the excitement of some folks turn you off to this whole idea. These Qualcomm variants of the S7/Edge are majorly great devices, and root would be ****ing awesome for everyone, so people are gonna get worked up about it. You KNOW how XDA gets. If you believe that there might be a straightforward exploit available, similar to the CID directory exploit that was used in the VS5, please pass on any help you can. (Or even if it has nothing to do with that route.)
All I know is that if you, or bceups, or anyone could actually help make this happen (and this is definitely a "they say it'll never happen" moment, like the Evo3d or the VS5) then you'd be rockstars of the community, more than you are now, however much that means to you. (It means a lot to me, I promise you.) If you think there's hope, and you're willing to give it a shot, ****ing bad ass... If not, maybe PM evilpotatoman and give him a nudge in the direction you'd think would work best.
Either way, I, and I'm sure every GS7/EDGE customer in America who's into Android, definitely have your back.
Let us know your thoughts, and if there's actually a ray of hope.
That's all I got.
Peace, bro.
Edit: and, btw, there IS some big bounty or something to boot, lol.

..