yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] samccfl99:
I was just checking on something. My problem is I do not know all that much about Lynix, but a lot about my phone. At the moment, going to the OI5 BL (or any LP BL) was a bad mistake for people (like me) that were already on the OA1 BL, where the BL would allow everything below a 5.1 kernel to load (maybe all LP kernels). If the freaking Kingroot app ran the same code all the time, the code that worked, then none of this would be a problem.

[MENTION=7533813]NavSad[/MENTION] OP'd a thread about this from June to Dec 19 of this year and he has been in this thread. I have not seen him lately. maybe he can help. That thread is here:

http://xdaforums.com/att-galaxy-s5/general/guide-downgrade-firmware-sm-g900a-t3398934

I am on page 3 of 14, but I fear the answer is that you cannot Odin files below OI5 (of which I only have the files for NCE), which means you can either go to UNrooted Stock OI5 or go to UNrooted Stock PH4 (6.0.1). UNLESS Kingroot fixes the app to permanently root OI5.

I HAVE A QUESTION FOR [MENTION=7533813]NavSad[/MENTION] OR [MENTION=7597286]AptLogic[/MENTION]. SINCE IT SEEMS THAT THE OI5 BL ALLOWS AN OF3 KERNEL, WILL IT ALLOW AN OA1 OR OC4 KERNEL? I ASK BECAUSE I WOULD LIKE TO KNOW IF SAFESTRAP WILL STILL WORK. IT DOES NEED AN OA1 KERNEL (OR ANY KK ONE) TO BOOT INTO SS. THANK YOU.

For those that may be new, Safestrap is an app that was created by one of our genius', that allowed the BL Locked G900/870A to attain a custom recovery. That was when we got root and custom recovery, which allowed the flashing of custom roms for our phone. This was in the KitKat days and lived thru the LP days AS LONG as you kept a KK BL. Safestrap needs a KK kernel to load correctly at boot and it boots right into SS custom recovery where you can Wipe and Flash, etc. Flashfire is the modern replacement for FF. The thing is that FF requires you to be booted up! So many of you might have gotten your S5 after OC4 was out, which is why you might have (or had) a 5.0 or 5.1 or 5.11 baseband on it. No LP BL's until this Kingroot came along, could attain root. So there you have a little history and I hope this helps to at least understand this situation. UNDERSTAND??? LOL.

I might also add that those that have the T-Mobile versions of our phone and also the Note4, come with an Unlocked BL. Those people have it made. Also several months ago, the devs unlocked the Verizon version of those phones. Verizon sucks also because they lock down their BL's too.
[AT&T Samsung Galaxy S 5] NavSad:
Yeah. There is an app called NCE Flasher to temporarily get safestrap running. But you need root and once you're done installing the rom you have to install the OC4 kernel for it to boot up again.
[AT&T Samsung Galaxy S 5] samccfl99:
I know all that! The question is will the OI5 BL (if rooted like I still am and will stay that way), that we now have, allow the booting into SS with an OA1 kernel, which is KK? It obviously seems to allow all LP kernels. I still have not gotten back to your discussion in the thread I referred to.
[AT&T Samsung Galaxy S 5] NavSad:
Yes. But not via Odin, it will bootloop.
[AT&T Samsung Galaxy S 5] samccfl99:
I am assuming you mean that the OI5 BL would not allow a flashing of a KK kernel anyway, but you are sure that after running NCE Flasher, that it will boot into SS fine? I guess then all 5.0 kernels will run ok then under the OI5 BL and allow a proper boot?

That would make me very happy...as long as I do not have to Odin anything again.

Do you know if there is a Kingroot app that keeps the code that allowed the rooting of LP?

FROM 10/13/2016: Nope, not possible because of locked bootloader. The farthest you can go down too is OF2.

http://xdaforums.com/showpost.php?p=69119416&postcount=50

You both knew this and wrote a thead about rooting LP without a root method that did not change??? I should have known better. Was just looking for a ray of sunshine...
[AT&T Samsung Galaxy S 5] NavSad:
Nope, haven't heard of anything.
[AT&T Samsung Galaxy S 5] samccfl99:
read that again. I changed it, you might not have seen it.

---------- Post added at 03:28 PM ---------- Previous post was at 03:12 PM ----------

So is there a Brave Soul out there who has stock rooted OF3 (or any LP rooted rom with an OI5 BL) and knows about Safestrap, like to install it properly and also NCE Flasher and also has the Flashable OC4.zip, like to give it a go? Or can confirm that it works and are able to get back to your rom after using SS? I am afraid to. SS now has become a necessity in case of an emergency as long as you have root. Also any valid rooted LP rom. As long as you still have root. Oh my, good grief. If your phone will not boot and the OI5 BL will not allow Odin to flash a KK kernel, then even if one has SS installed, one will be completely screwed. Will just have to hope they come up with a PERMANENT root method for OI5 (or dare I say MM)?
[AT&T Samsung Galaxy S 5] NavSad:
The only way you can run a kernel is too have the same system, for ex. if you're on OI5 and you want to run an OF2 kernel you need to Flashfire down too OF2 because 5.0 kernels and 5.1.1 systems aren't compatible.
[AT&T Samsung Galaxy S 5] samccfl99:
Hello? According to the OP, you can obviously have a 5.1.1 BL with an OF3 kernel and OC4/OC7 rom and it does work. So what you just said does not make any sense. I just want to know definitely if NCE Flasher is run (replacing the kernel with OA1) with SS installed, will it still boot into SS and then before rebooting, using the Flashable OC4 kernel.zip? I do not know how many times I have to ask this same question. This is easy stuff for someone who knows Linux.
[AT&T Samsung Galaxy S 5] NavSad:
Oh, Sorry. But yes you can do that.
[AT&T Samsung Galaxy S 5] samccfl99:
Thanks, I will try it if I ever need it and pray. But without a permanent root method for OI5 (which again I state should have been the case or been warned), if something happened to the phone, even if you have SS on it, there would be no way to Odin the OA1 kernel to save the phone and then be forced to be on an unrooted stock rom. I know it probably won't ever happen (to me, anyway) and they may get the permanent root for it again, but it makes me a bit uneasy.

I have not seen [MENTION=7597286]AptLogic[/MENTION] comment yet. Maybe he is on a rest, which would be nice. He said the other day that he would check with the Kingroot people and see why the exploit was taken out of their system. I am assuming it is some exploit, but maybe not. In the current state of mine and many phones, OI5 must now replace NCE for Odin base flashing and OI5 needs a permanent root solution. I hope they get it and also I hope they find a root exploit for MM.
[AT&T Samsung Galaxy S 5] AptLogic:
Trying to rest a little, but I've been lurking here from time to time ;)

I got a reply today from the Kingroot people, didn't help much though. I'm still taking with them so we may have a chance yet. Their reply is attached (sorry for the tinting I've got my blue light filter turned on)
[AT&T Samsung Galaxy S 5] captivated1971:
Definatly dont hit the extresolite yet lol i tried and same failures as above.
[AT&T Samsung Galaxy S 5] NavSad:
Do you think we could try this? http://xdaforums.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120.
[AT&T Samsung Galaxy S 5] AptLogic:
Already tried it both on my Fire HD 8 and on my S5, didn't work.
[AT&T Samsung Galaxy S 5] samccfl99:
I too sent them a support message yesterday. Their stupid form did not allow me to copy it to the clipboard. How long did it take for you to get that response from them, may I ask? They do not seem like a reliable company and they are not in this country because they cannot spell too well on their website. Is this normal for a company that does this to have server control over the program? I do not think very much of them if they take exploits out of their database. They are screwing with peoples phones. Even though I am still rooted and probably will stay that way until something bad happens to my phone (probabilities are small), I am not thrilled about my phone having a LP BL.

I thank you for your hard work, but the exploit should have been permanent when telling people they can do this.

HAPPY NEW YEAR....
[AT&T Samsung Galaxy S 5] EfWithEffectz:
I'm still stock on MM at the moment, just happened to miss out like a day later.
[AT&T Samsung Galaxy S 5] mwrobe1:
Eeeek...from a privacy standpoint...this gives me pause.
[AT&T Samsung Galaxy S 5] AptLogic:
If people are interested in helping find what we need to do to get iovyroot working please speak up, it could be our last hope.
[AT&T Samsung Galaxy S 5] AptLogic:
You might have a problem with rooting it since it's on 5.1.1, most of the time the only way you can do it is via a Systemless root.
[AT&T Samsung Galaxy S 5] johnkirchner:
I can try as much as I can. Most of my programming is windows/VB based though...I did not jump ship when Android started up, lol. From what I have seen, isn't iovyroot more of a temp root only thing?
[AT&T Samsung Galaxy S 5] Helgen:
i see, could I still use the metro pcs firmware on this non rooted?
[AT&T Samsung Galaxy S 5] AptLogic:
No because you'd get an AUTH error when you try to flash it.

[MENTION=2846794]johnkirchner[/MENTION] yeah iovyroot is a temp thing.. but when you think about it so was that Kingroot exploit. Also its coded in C.
[AT&T Samsung Galaxy S 5] lordmorphous:
Don't do what I did.....I had everything going great running x on my 870. Decided to flash Xposed and bricked! So now back to no root!
[AT&T Samsung Galaxy S 5] johnkirchner:
It would be nice to have the specific exploit that worked, it would give us a direct focus. Problem now is that kingroot says there is no exploit so reverse engineering it would be pointless. We possibly could try the Windows version and use a packet sniffer to capture the communication protocol if it is truly server side. I did this a lot when I used to hack the Yahoo messenger login protocol back in the day. Shows my age, lol.
[AT&T Samsung Galaxy S 5] wforider:
Never too old [emoji123]
[AT&T Samsung Galaxy S 5] samccfl99:
Now here is what I really think and am sorry if this offends you. What do you have to say for yourself starting this thread and now inserting what is on top??? I've had root since 10/2014 and now maybe i might lose it (still doubtful) because of this thread. There was no mention about this root method not being permanent. DO YOU UNDERSTAND???
[AT&T Samsung Galaxy S 5] AptLogic:
Sowwee ;-; I'll put that in now but it isn't much help now.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Whoaa dude ... ( is colour (color for the 'mercans here) the new CAPS LOCKS?)

Aside from the fact that just about every gambit here has a disclaimer that YOU are solely responsible & no one else, why express harshness toward someone who has been trying to help?

I personally have (finally) managed to achieve root & have managed to keep it through many iterations of updating the Xtresolite rom, (something that I'll happily share if there's any interest).

I'm not going to risk my root to try to debug the Kingroot situation, but clearly the Kingroot folk have either cut off the G900A or "artefacts" are interfering with the root process.

I suspect they've cut it off because i's pretty clear that the intent of most people here is to move to another SU binary ... from my superficial look at the Kingroot "residue", it certainly looks like there's on ongoing "presence" ... it's not in Kingroot's interest to facilitate us moving on to an independent rom.

As I mentioned in my first post, Kingroot automatically updates itself to prevent installing another SU binary.

Has anyone restored to a virgin 5.xx & tried Kingroot using data only, not WIFI?

If so, Kingroot has cut us off ...
[AT&T Samsung Galaxy S 5] wforider:
Funny how one click root would would scan my g900a and come back with no root available for this phone up until kingroot found away and now one click says it can root what's changed
[AT&T Samsung Galaxy S 5] invert_nexus:
First of all, the thing about Kingroot is they're pretty fishy to begin with. It's a shame that nobody with the wherewithal was present during the window opportunity to snoop around the process and find out what particular exploit that Kingroot was utilizing to root OI5. Because, that's just it. An exploit does exist. But what is it? Maybe some of the other root solutions have it? Anyone made the rounds with Towelroot and whatnot since this whole debacle began?

There has to be a way, and hopefully someone will stumble across it again.

I for one am incredibly happy to finally have root, as tenuous as it is. I'm terrified of doing something risky that would end in a bootloop because that pretty much means rootdeath as of now. I'm on Twi5ted Lollipop and have it up and running in an adequate fashion, but I had planned on moving on the Xtrestolite or whatever it's called because people have been talking it up. Maybe even seeing about modding my own flavor of this or that. But, now I'm nervous about flashing anything, even trying a new xposed module or whatnot. To lose root would be painful at this point.

But, this anger against AptLogic is ridiculous. Caveat Emptor. Not only that, but I would never give up the original root with fewer burned qfuses for this tenuous grip on 5.0 that we've managed to achieve. For what? To give Marshmallow a taste? Know what I think of Marshmallow? Practically identical to Lollipop. Certainly not enough differences to make me risk any root solution. And, yes, something like this is always a risk.

LIve and learn though, eh?

I say we give AptLogic a huge hand of applause for being the one willing to go out on the ledge to experiment more than anyone else here. He even went back and sacrificed his own root to test the reports of Kingroot no longer functioning (I did read that right, yes? Much sorrow for that one. That had to hurt.)

And, while we're at it, let's give Lingo2012 a hand for being the first one to stumble into this whole thing to begin with.

Oh. This just happened while I was responding.

Really?

There we go. Fingers crossed.

Anyone try yet?
[AT&T Samsung Galaxy S 5] eviljonny1:
One click didn't find Jack Sh#t in the way of root on my 900A and Kingcrap is done.
[AT&T Samsung Galaxy S 5] wforider:


---------- Post added at 09:31 PM ---------- Previous post was at 09:31 PM ----------
[AT&T Samsung Galaxy S 5] EfWithEffectz:
Let me know if this works because I literally just came back from 5.1.1

---------- Post added at 06:38 AM ---------- Previous post was at 06:34 AM ----------

Wait but that says it's a t mobile phone according to the carrier at the top
[AT&T Samsung Galaxy S 5] wforider:
No it says it a t-mobile network and ATT phone
[AT&T Samsung Galaxy S 5] EfWithEffectz:
Ohh okay I understand now, and if this works for you please let me know asap
[AT&T Samsung Galaxy S 5] EfWithEffectz:
Are you attempting root?
[AT&T Samsung Galaxy S 5] Helgen:
What's up with the "doesn't persist past a reboot?"

I've rebooted many, many times and I'm still rooted. I've did all kind of tweaks and system mods and my root is just fine. Maybe I'm "very very lucky" lol.
[AT&T Samsung Galaxy S 5] arthurbxp:
What's the name of the app?
[AT&T Samsung Galaxy S 5] EfWithEffectz:
One click root
[AT&T Samsung Galaxy S 5] samccfl99:
And you WILL stay rooted until some disaster occurs, which most likely will not if you do not do dangerous things. Now I am sorry I caused such a ruckus (not really), and even though there was a "disclaimer" (that no one really reads), the fact still remains that it should have been posted that THIS IS A TEST AND NOT FOR PERMANENT ROOT. I am wondering how many really understand? Permanent Root is what Towel Root is. Something I will never be able to use again because I could not go to NCE anymore. Heck, I am afraid to even try to go into SafeStrap (if I absolutely have to) even though it has been said it would work. Well I am not sure because if the OI5 BL does not like the OA1 kernel, well then that would be the end of that and no way to get back except to flash a crappy stock unrooted rom.

Really this is all ATT's fault. Their fault for locking the BL. Their fault for not having a developer copy of ABOOT. Their fault for even being in existence with their high prices and being cheap on DATA!!! LOL.

I am very happy for those who have suffered with unrooted OI5 or MM and now have a proper phone. I feel for those who had it for a fleeting moment and now it is gone. I do not see any dummies like me who have done this only to maybe having a useless brick sometime maybe in the future (an Android is useless without root!).

---------- Post added at 08:40 AM ---------- Previous post was at 08:15 AM ----------

and now i will be silent until someone finds a solution to this mess (doubtful) that should not have been given to other people to begin with...They have been chasing LP root for how long???

For those who never had root and got it now, I am happy for you. For those that had it for a fleeting moment and lost it, sorry. Google has absolutely ruined the Android experience that they created. Almost makes me want to get a Rotten Apple, but that ain't ever going to happen!!!

A HAPPY NEW YEAR TO ALL FROM AN OLD CURMUDGEON!
[AT&T Samsung Galaxy S 5] johnkirchner:
Ok dude, calm down. The root process was permanent, the app stopped supporting it, this is not anyone's fault here. There was nothing misleading about anything at the time of it working. Yes, YOU are solely responsible for what you do to your phone. Speak for yourself, I do read the disclaimers as it has pertinent information. If you do not read them or understand them, that is on you. Yes, I am getting defensive about it being an app (Windows) developer. If I decide to go skiing down a mountain side, I know there is a chance I break my leg, it's not the resort's fault that I choose to do that.

As for "this mess that should have never been given to other people"...really?? This gave root to many more that did not have it. If you are not going to be part of the solution, then please stay silent or get a different phone and leave!
[AT&T Samsung Galaxy S 5] Helgen:
"Dangerous things," of course I won't do dangerous things, I just wanted a root which is what this thread was all about. Just because one person's phone messes up doesn't mean everyone else will. And as said in the first post, this is potentially dangerous so do it at your own risk. I followed the instructions AptLogic made out, and everything went well for me and hundreds if not thousands. I understand you're frustrated, but this isn't his fault and I still thank him till this day, even though I'm very tempted to go back to stock because the roms currently are not worth the root.
[AT&T Samsung Galaxy S 5] johnkirchner:
You have to pay for one click root? Now I'm really skeptical about it. Convenient that it is a free download and you get your phone plugged in to usb and then when you try to root it, it says to login...and then pay to do so, lol.
[AT&T Samsung Galaxy S 5] EfWithEffectz:
That's messed up, I guess we are out of a solution until someone finds another way, and good thing you said this because last night I was gonna go ahead and downgrade to 5.1.1 to test that one click root but I was too tired. So good luck i guess.

---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------

Someone on 5.1.1 could try iroot, or another tool. I tried to stay on stock 5.1.1 but my phone eventually got to the point where, instead of just asking me to update, it just straight up restarted my phone and updated for me.
[AT&T Samsung Galaxy S 5] invert_nexus:
Well, just a heads up to those who wish to try:

"In fact, we’re so confident about our software that we guarantee success. If you can’t root your Galaxy S5 for any reason with One Click Root, we’ll provide a full refund. We also guarantee your phone will not suffer any damage as a result of using our software."

https://www.oneclickroot.com/samsung-galaxy-s5/

Of course, how easy it is to get this refund, I can't say.

I also seem to have some difficulty finding how much it costs to begin with.

---------- Post added at 05:55 PM ---------- Previous post was at 05:45 PM ----------

Looks like $30ish. Bad reviews, too.

http://download.cnet.com/One-Click-Root/3000-2094_4-75910907.html
[AT&T Samsung Galaxy S 5] AptLogic:
Look guys, I only put the temp only disclaimer there because people have been saying early on that they'd reboot and root would be gone. If it's not happening to a majority of users who tried it, just say so and I'll change it. Personally when I first tried Kingroot it worked past reboots.

And don't give Sam a hard time, he's just trying to provide input, and he's mad at AT&T for locking down something he paid good money for (for the record I'm pretty pissed with them too). We don't need a flame war here. :)

I'll maybe look at iovyroot again today. But that oneclickroot looks really sketch if they're asking you to pay like 30 bucks.

If anyone has any input they want me to see FAST, please PM me. I can't read every post in this thread, so the best way to get something to me quick is via PM.

Happy New Year, folks.
[AT&T Samsung Galaxy S 5] johnkirchner:
Agreed, lets move on and see what we can try doing to accomplish this. Forgive my non android programming knowledge...if you download iovyroot (from GitHub), I noticed it is not an apk or windows exe file, are these just binary files? What do you do with them? I will try and help as much as I possibly can with limited Linux/android skills. If we can at least get something, I could possibly roll it into a windows based root to use a pc and usb cable.

Side note: anyone else having issues with the XDA app? I tried using it on my tablet but it says could not connect to server...
[AT&T Samsung Galaxy S 5] AptLogic:
You have to modify the source for your device and then build it using NDK

Ive been having that issue on and off with my tablet. Just reboot and it should work.
[AT&T Samsung Galaxy S 5] CreeperPVP:
I couldn't personally downgrade as i was on PH4 but then i found this thread and used the Odin provided and i downgraded from PH4 to OI5! I'm so happy because i hated 6.0.1!
[AT&T Samsung Galaxy S 5] eviljonny1:
Does not work for me. :( I get this message:

"SORRY

There Is No Root At This Time

Brand: samsung

Model: samsung-sm-g900a

Android Version: 5.1.1 (lmy47x.g900aucu4coi5)

Please enter your email to get notified when your device becomes rootable."

***I dont know why I cannot upload a working screen shot image today. Never had a problem before.
[AT&T Samsung Galaxy S 5] plx2016:
G870A with 5.1.1 - rooting wont happen

Hello,

after downgrading to Lollipop 5.1.1 and following this guide I cannot root it

using KingRoot 5

I alsoi reset to fcatory default, wiped cache and tried it again. Without SIM....

Tried it 10-11 times, still wont work.

Any suggestions on this one?

Thank you

plx
[AT&T Samsung Galaxy S 5] DejaVuAgain:
"modified" ODIN ...

Do I understand correctly that if I dumped my rooted system partition & created an ODIN flashable file, that someone else could then use the "modified" ODIN (from above) to push that file onto their phone? ...

What am I missing here?
[AT&T Samsung Galaxy S 5] johnkirchner:
The kingroot app apparently does not support the AT&T S5 anymore. At this time (yet again) there is no active root for lollipop.
[AT&T Samsung Galaxy S 5] plx2016:
OK, so what about using an older version of kingroot?

Is it only possible to root 5.0?