yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] samccfl99:
Well I just decided to check on this thread, why I do not know, and I see my name mentioned. It is all well and good what you guys are trying to do and I am happy for the people who never had root either because they took a LP OTA or just got the phone will LP and now they have it and can enjoy root and custom roms.

As I have said before, the best of the best have tried. I think it would behoove us all to flood the email servers of those pr*cks at Kingroot because they have the secret and the NERVE to take the method away. This freaking phone is almost 3 years old and pretty much every other S5 phone that does not belong to ATT can attain root.

I really have no need to change my rom because I am happy with it, but i do not like to be stuck on this OI5 BL. But whatever. Since you mentioned my name about this PIT file (but I am not the only one rooted), you can tell me how to get what you want and if I do not deem it dangerous, I can try it.

Let me know.

My finger is on the trigger for a new phone, but honestly I cannot find a decent and lower price phone with a removable battery and sdcard and plenty of dev. Those S8 specs sure look great. Maybe the S7E will go down in price when they come out, supposedly in April. A 935-F is still around $585, but then it does not have a removable battery. We shall see.
[AT&T Samsung Galaxy S 5] TheMadScientist:
i dont think its a bios issue ive updated my drivers and there installed i got it night i reinstalled window and started fresh after i updated the same drivers i already had installed it started working

the issue started as soon as i switched to legacy compatilbility mode then booted back into windows to do the dos script to update

i had tht issue and didnt update my bios for a few more days

is all i wanted to do is overclock my pross a little see if i could crank some more power out but found out my pross in not ocable
[AT&T Samsung Galaxy S 5] DejaVuAgain:
The fact that you get sound through the headphone jack suggests that it's simply a configuration problem.

Have you checked the mixer settings to make sure that the hdmi output isn't muted when it's plugged in?

(Right click on your tray sound icon & open volume mixer to check it out. Also check control panel/sounds/playback.)

This is especially likely if you have a 3rd party mixer app (like Realtek or B&O or whatever) on your system.

Also, I'm sure you know that most "player" apps have their own mixer as well.

It's really easy to accidentally mute an output somewhere in the chain ...

---------- Post added at 06:58 PM ---------- Previous post was at 06:50 PM ----------

Since I'm the one who needs the rooted PIT for a test, here's the scoop ...

You can use ChainFire to backup the PIT.

Just select the "normal" option & uncheck everything but the PIT.

ChainFire is totally safe (& you should be backing up at least your system partition with it anyway).

I'm not too hopeful that this test will work, but it's a very small file & every bit of information is helpful.

Thanks ...
[AT&T Samsung Galaxy S 5] AptLogic:
Guys kingoroot works to root devices running OI5, managed to root today :D
[AT&T Samsung Galaxy S 5] TheMadScientist:
yea my hdmi tv wasnt even showing up in my playback mixer. unknown monitor type which was usally picks up. im assuming it was a conflicting driver issue i installed all my intel graphic driver before i installed relteks audio and i started working rite after fresh windows install problem still existed normally only display reso isnt rite until driver installed but i have sound this time i didnt

but like i said once i got intels graphic driver on first all is good

thanks for your advice also

been dealling with this for a few weeks now so ive checked and looked at a lot of stuff plus having 3 drives on pc all data and ****s backed up for quick installs aftewr clean install

i like to do fresh installs on pc and android every now and then
[AT&T Samsung Galaxy S 5] davidalindsey:
Does this work through the Android app on the phone or via the windows application?
[AT&T Samsung Galaxy S 5] TheMadScientist:
So this is kind of to everyone

ima start to try to find a way to get super su me to get su perm root and get su

Which version og kingroot u use and i believe u said sume works with 4.81 and lowerrite????
[AT&T Samsung Galaxy S 5] AptLogic:
The android app works for rooting. Usually you should avoid using windows applications to root because there is a chance they will install malware on your PC (and nobody wants that lol)
[AT&T Samsung Galaxy S 5] TheMadScientist:
lol ill let u know here how it goes on my end gotta do a downgrade first tryin out ph4
[AT&T Samsung Galaxy S 5] TheMadScientist:
mine keeps failing im 59% of the way through
[AT&T Samsung Galaxy S 5] lordmorphous:
What would the equivalent version be for the 870a?
[AT&T Samsung Galaxy S 5] 719c6:
I flashed back to OF3 then rooted... but that was before Kingroot stopped and then just recently started working again. Might wanna try there.

---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------

LINK
[AT&T Samsung Galaxy S 5] wforider:
I doubt that
[AT&T Samsung Galaxy S 5] AptLogic:
Okay so King/o/root kind of works, and by kind of I mean you'll have to root twice or it won't work, and it only works for about 5 minutes before the phone reboots and softbricks.

On the bright side though I think I got the entire kallsyms file from the /proc partition so we'll see what we can do with that. nevermind its all zeroed out rip, but I think I got the PIT file so here it is: https://www.androidfilehost.com/?fid=817550096634741439

Um.. what am I missing-OH! Yeah, Super-sume doesn't work (as expected) and because I can't get SuperSU installed without bricking I can't use Flashfire at all.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
I assume you're sayin' that you dumped the PIT during your window of rootedness.

Your PIT file turns out to be identical to stock (other than null filled length).

Soooo, no hole there ...
[AT&T Samsung Galaxy S 5] AptLogic:
Ah it was worth a try though. I think next would be trying to see if we can grab the binaries that Kingoroot is using and replace the files it uses with SuperSU files... I'll take a quick look at that but I've got some things to do tomorrow so I won't spend long on it.
[AT&T Samsung Galaxy S 5] UsandThem:
The latest KingRoot from their site worked with no problems on the first try.
[AT&T Samsung Galaxy S 5] TheMadScientist:
Which firmware are u on???
[AT&T Samsung Galaxy S 5] UsandThem:
OI5
[AT&T Samsung Galaxy S 5] AptLogic:
Didn't work for me, tried a couple times.
[AT&T Samsung Galaxy S 5] UsandThem:
I tried uninstalling the latest KingRoot to try the exploit where we reverted back to KR4.8.1 then SuperSUme to get SuperSU, I ended up in a hard brick, but successfully recovered. I'm trying to remember what I did to get root in the first place. Will keep y'all up-to-date!
[AT&T Samsung Galaxy S 5] TheMadScientist:
Yah oi5 aint workin for me either
[AT&T Samsung Galaxy S 5] DejaVuAgain:
No joy for me either ...

I wonder if Kingroot perhaps blacklists IMEI's that they rooted & then "disappeared" (after we changed SU)?
[AT&T Samsung Galaxy S 5] UsandThem:
Proofs...?
[AT&T Samsung Galaxy S 5] UsandThem:
Every time I try to remove root, my phone hard bricks. I'm trying to use KR4.8.1 to root after I used KR5.0.3 to root THEN use SuperSUme to install SuperSU binaries. Is there a reason behind this?

UPDATE: I uninstalled KR5.0.3 without removing root, installed KR4.8.1 over 5.0.3. I installed SuperSume v6.0 (as used before) and it successfully removed KR and SuperSU popped up. I ACTUALLY installed SuperSU binaries and rebooted my phone. My phone became hard bricked again. Am I getting closer or no?
[AT&T Samsung Galaxy S 5] AptLogic:
Prolly KingRoot found this thread and blocked rooting, downgrading, and rooting again. Was fun while it lasted tho... if we can somehow capture the files KR uses to root we can replace the binaries with SuperSU.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
I don't remember with absolute clarity, but I think that I recall using KR 5.1 to get root & then being able to run supersume after freezing a bunch of KR stuff using Titanium, & taking ownership of the KR SU.

That might be worth exploring if you have KR root ...
[AT&T Samsung Galaxy S 5] samccfl99:
First, glad you have root. Nothing like root with SS oe FF. You did not say yet how you got it. I am just curious and monitoring the thread in the hope that Kingroot will get their heads out of their butts and make this permanent since our phones are the only ones left that cannot get root!!! (note, I have had root since 10/2014, but now with an OI5 BL, due to someone...LOL)

I did not understand what you said before about uninstalling Kingroot. I did it when this thread came out when it worked and ran the 4.81 version where it got to 16-20, then rebooted and finished rooting. then PAYED for and ran SuperSu-me, which injected SuperSu and GOT RID OF Kingroot.

I would not even trust that Kingroot on your phone, but if you try to mess with it you might lose root. who knows, those maniacs could cause you to lose root anytime they wanted to. we do not know what the app is doing.

It is sad that the ATT version of this GREAT phone (for it's time) is the only one with these problems...
[AT&T Samsung Galaxy S 5] UsandThem:
BTW, I installed SuperSU binaries, rebooted my phone, and ended up in a hard brick. Have you any idea on how to "capture" these files? I'm going to re-root and install SuperSU binaries without rebooting this time. Maybe a soft reboot could work?

---------- Post added at 09:26 AM ---------- Previous post was at 09:21 AM ----------

Probably not a good idea on my part, but I did run both KR AND KingORoot simultaneously. Totally not positive on what my procedure is. Will try to develop a "method".
[AT&T Samsung Galaxy S 5] AptLogic:
Well I don't know for sure, but I've been doing some testing with King/o/root and I was able to grab the binaries they installed, but never the exploit they used. The directory that Kingo put the files in was permission locked, and I wasn't able to get in until after rooting, and by then it seems Kingo removed the script to prevent what I was doing :/

We may be able to capture something from the desktop app using a self-man in the middle attack to copy any files that are pushed to the phone during the rooting process, but again I don't know absolutely for sure.
[AT&T Samsung Galaxy S 5] TheMadScientist:
crazy idea?

for the ones that are achieving any kind of root what about

as soon as you get root run flashifire and attempt to flash one of the rooted roms?

or has this been tried

dont even bother with su suME
[AT&T Samsung Galaxy S 5] AptLogic:
Flashfire only works with SuperSU or CyanogenMod root.
[AT&T Samsung Galaxy S 5] wforider:
No one has posted anything credible at this point and let's post detailed information on the process of obtaining root so we don't waste our time regurgitating the same process over and over please provide as much information as possible
[AT&T Samsung Galaxy S 5] TheMadScientist:
figures kinda new to flashfire i use it on the g4 to instal xposed and thats it.

i am in the proscces of making a rom for the sprint g4 more like modding a rom that all user should have to do is restore it as a system in flashfire and be good to go

its a long ass thing to flash some of the roms on g4 seein there is no twrp and root only on 2 out of like 7 or 8 firms.

thats why i am looking into dd a rooted system image on s5 too even with locked bl got su and full root sys r/w

kernals permisive

---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------

normally i keep to myself on this and im sure most would agree we may be spitting the same ideas over and over. but each idea with a new outlook and fresh eye = good things most of the time. if its not rootable then its not. oh well but dont knock a man for trying.

i havnt seen to many ideas on your end. or are u risking your device by trial and error. well i am ive bricked my s5 in the last week at least 20 times with various things
[AT&T Samsung Galaxy S 5] TheMadScientist:
straight up I can respect that sir im about the same i am a mechanic by day rebuild some and try to most electronics by night as we speak im tearin down a couple ps4s to build one why for the hell of it. and by the way i need some parts for my glass top stove lol

i feel some times even old ideas bring up new things. 1 problems 1,000,000 ways to solve it

As seein technicly this thread has gotten off topic i see where you are coming from and i do apologize for being rude about it.
[AT&T Samsung Galaxy S 5] wforider:
What's the Make And Model on your serial tag
[AT&T Samsung Galaxy S 5] UsandThem:
I honestly can't record my steps on how I keep getting root even after hard bricking 10 times or more. I was able to switch KR with SuperSU and flashfire worked fine as in I was able to add zips and all that jazz, however I wasn't able to install FreedomROM (custom OS). I was hard bricked and am now recovering as I speak. Am gonna try to flash the rooted stock OF3.
[AT&T Samsung Galaxy S 5] AptLogic:
You have to install the rooted OF3 first because Freedom runs on an OF3 kernel.
[AT&T Samsung Galaxy S 5] UsandThem:
Flashing Rooted OF3 worked! Will update THIS POST when running FreedomROM.

UPDATE: FreedomROM doesn't go past the Galaxy S5 screen with the custom lock on the screen. Hard bricked once again..
[MENTION=7597286]AptLogic[/MENTION] what do you suggest I do? I can boot the rooted OF3 but can't boot the custom rom.
[AT&T Samsung Galaxy S 5] AptLogic:
Hmm.... only thing I can think of is that SELinux could still be enforcing... try checking that out and we can work from there. If that doesn't work then try installing a different ROM (ex. XtreStoLite)
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Hey, if you want to try a totally stripped down rom (kinda based on XtreStoLite), get it here

(It's a zip flashable with ChainFire.)

If you can run the rooted OF3, it will run & if I recall correctly, it runs on PA2 as well

I stopped working on it when I lost root, but it's 100% functional, quick & really good on battery life.

If it works for you, I'll give you details about what's in it & what's not, & how to add some stuff back that you might want ...
[AT&T Samsung Galaxy S 5] UsandThem:
Your ROM worked. Like you said, there are no apps. Help me get Google Apps, please?
[AT&T Samsung Galaxy S 5] AptLogic:
You can use FlashFire to install OpenGApps.

And if you could tell us how you rooted that would be great ;)
[AT&T Samsung Galaxy S 5] wforider:
Don't hold your breath :p
[AT&T Samsung Galaxy S 5] UsandThem:
[MENTION=7597286]AptLogic[/MENTION]

I used KR AND Kingo simultaneously. Kingo would usually root the phone saying ROOT SUCCEEDED and I would see the Kingo Superuser app in my app drawer. I then used the KR4.8.1 to overwrite? the Kingo SU and eventually Kingo would pop up asking KR for root permissions. After, I used SuperSUme to remove KR to use SuperSU in order to use Flashfire. I used Flashfire to flash STOCK ROOTED OF3. THEN, I flash the stripped down X ROM over OF3 without a full wipe. I just tried installing the FreedomROM and it isn't working. I have to recover the phone and re-root ATM.
[AT&T Samsung Galaxy S 5] wforider:
Works
[AT&T Samsung Galaxy S 5] UsandThem:
What method did you use? Curious to know if whatever you did was easier. :p
[AT&T Samsung Galaxy S 5] wforider:
I'm currently testing repeatable root and logging the steps will advise soon
[AT&T Samsung Galaxy S 5] AptLogic:
Man, I just went back to OF3 last night now I have to upgrade again lol

Android 5.1.1: Now with even more battery sucking power!
[AT&T Samsung Galaxy S 5] TheMadScientist:
ive been all over firmwares of3 all the way upto ph4 havnt even got a temp root yet.
[AT&T Samsung Galaxy S 5] ChikhaiBardo:
Any idea how to get this working with G870A? Kingoroot makes it to 90% then goes to blank home screen like it's trying to add SU app. I am on 5.0 OF3
[AT&T Samsung Galaxy S 5] AptLogic:
Try on OI5 (or whatever 5.1.1 version the 870 uses)
[AT&T Samsung Galaxy S 5] davidalindsey:
Any update?
[AT&T Samsung Galaxy S 5] oriax123:
I rooted successfully last night with kingo root on OI5. but it would go away so reroot with kingo root. After It rebooted got stuck on startup so I had to flash stock again.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Unless I screwed something up, the Google Play (store) app is on the rom ... it's one of the things I updated.

For a whole bunch of optional "standard" apps, you can use the XtreStoLite_LP_Aroma_Add-on_Package_XXU1BOD3_v2.2.zip to flash what you want with ChainFire.

Unfortunately I can't test anymore since I lost root, but let me know what you need in the rom & I'll pop it in for you.

(The concept with my rom was to strip out everything that can be added by normal means, which is why it's so bare.)
[AT&T Samsung Galaxy S 5] davidalindsey:
.....

And it sticks?

Also can we get SuperSU to overwrite the kingo superuser?
[AT&T Samsung Galaxy S 5] UsandThem:
[MENTION=7597286]AptLogic[/MENTION]

--STEPS TO ROOT OI5--

--------------------------------------

STEP 1.

Install:

- Kingo ROOT v4.1.9

- KingRoot v4.8.1

- SuperSU from PlayStore

- SuperSUme v6.0

- FlashFire from PlayStore

- Any Root Checker app to your liking

--------------------------------------

STEP 2.

Disable these toggles:

- WiFi

- Location

- NFC

- Sync

- Powersave mode of any kind

--------------------------------------

STEP 3.

- Open Kingo ROOT

NOTE: Kingo ROOT must not show Install Recommended App below Android version.

If it does, you didn't disable the above toggles. Clear from Multi-Task and start over. This worked for me.

- Root using Kingo ROOT v4.1.9

If the first time it says ROOT SUCCEEDED check if that's true using a root checking app. If true skip to STEP 4.

If the Root Checking app says No Root Detected then re-root using Kingo ROOT v4.1.9

- Check to see now if you have root(you should). If you do, STEP 4 is for you.

NOTE: If you are not able to get root using Kingo, just keep trying it.

--------------------------------------

STEP 4.

- Open KingRoot v4.8.1

It should already show you the Security Index page where you see the big blue numbers. Press the button saying Fix Now/Continue.

Let it run its course...

--------------------------------------

STEP 5.

- Uninstall SuperUser (installed by Kingo ROOT)

Just press and hold the app in the app drawer and drag to uninstall. Simple step.

--------------------------------------

STEP 6.

- Open Super-Sume

KingRoot should ask you for permissions. Allow it.

You may get Force Close errors about KingRoot. Ignore these.

--------------------------------------

STEP 7.

- Update SuperSu binaries

When completed, DO NOT, I REPEAT, DO NOT REBOOT YOUR DEVICE! Simply press Ok.

--------------------------------------

STEP 8.

- Grant permissions to FlashFire

Flash Order:

- Wipe Everything even Internal Storage (move stuffs to computer or external sdcard) Don't select the last two options!!

- Select the pre-rooted OF3 zip

Upon selecting, an options screen pops up. Toggle Mount /system read/write.. Important..

Begin the flashing process.

NOTE: If Flashfire says (waiting for device)/(waiting for internal memory), don't trip.

--------------------------------------

STEP 9.

- DONE?

HELP!

If anyone found an easier way, please let the community know!
[AT&T Samsung Galaxy S 5] AptLogic:
ummmm......

XD I think I may have screwed up LOL

turns out I did an OTA to OI5, and then decided it was a good idea to flash an OF3 AP file on top of it... gg brain.

Will update when I've tried the root correctly
[AT&T Samsung Galaxy S 5] UsandThem:
Have you looked at my butched instructions? I want to know if there's something that doesn't make sense to you so I can clarify.
[AT&T Samsung Galaxy S 5] davidalindsey:
Looks like I we have something to play with..

Maybe hope for marshmallow root.. really needed WiFi calling
[AT&T Samsung Galaxy S 5] AptLogic:
No that whole thing was caused because I'm really tired and I wasn't paying attention to what I was flashing lol

[MENTION=3965781]davidalindsey[/MENTION] may have something of the sort in the works, don't get your hopes up but stay tuned for more.

Oh also a little tip: if you get a bootloop just re-flash the stock AP in Odin and you'll be good to go, all your data will be safe. (ONLY THE AP SLOT!!)
[AT&T Samsung Galaxy S 5] davidalindsey:
And instructions look pretty straight forward

Will try soon

Just have downgrade the 6.0 to the OI5 and download the rooted OF3 zip
[AT&T Samsung Galaxy S 5] AptLogic:
Try Reinstalling the kingroot app and starting over. Remember it may take a couple tries
[AT&T Samsung Galaxy S 5] lingo2012:
Ok will let you know
[AT&T Samsung Galaxy S 5] dthaha:
Reporting here from CPA4. I am stuck on 26% on Kingroot. I will update if it changes.

EDIT: Stuck around 20% after a few tries.
[AT&T Samsung Galaxy S 5] lingo2012:
That's a no go on the 7.1 rom. Kernel is not seaandroid enforcing, then I got software modified please take your phone to AT&T or something like that
[AT&T Samsung Galaxy S 5] AptLogic:
Darn... I really wanted that to work. Alright then maybe someone will find a work around at some point like a safestrap variant or something
[AT&T Samsung Galaxy S 5] NavSad:
I think it's time for Hashcode to help us.
[AT&T Samsung Galaxy S 5] AptLogic:
[MENTION=4243514]Hashcode[/MENTION]
[AT&T Samsung Galaxy S 5] lingo2012:
I was hoping it would work to
[AT&T Samsung Galaxy S 5] Raphu88:
I get to about 20% and kingroot says it failed to root. ive tried close to 20 times. reinstalling kingroot after each try for the last five or so tries. this is on a 900a running on ph2. any help?
[AT&T Samsung Galaxy S 5] AptLogic:
use ODIN to downgrade to Oi5 using the files in post 2,and then try.

Be aware this will wipe all of your data, so back up before doing this
[AT&T Samsung Galaxy S 5] Raphu88:
what are the chances of bricking post 2 says it pretty much will happen. thanks for the reply btw.
[AT&T Samsung Galaxy S 5] AptLogic:
No what it says in post 2 is that if you do brick after you have root, then to use those files to restore using ODIN
[AT&T Samsung Galaxy S 5] AptLogic:
[MENTION=4911082]lingo2012[/MENTION] [MENTION=7533813]NavSad[/MENTION] Got a new experiment for you!

I want one of you to try using Safestrap on OF3 to upgrade to Nougat. All I want you guys to do is get Safestrap running, and flash ONLY the Resurrection Remix 7.1 ROM, no GApps. I want to see if this works and adding GApps is just a waste of time. This will accomplish 2 tasks:

See if Safestrap works on 5.0 builds

See if we can use Safestrap to flash a Nougat ROM

Side Note: I think if we can turn off KNOX we could (in theory) bypass the AT&T error.
[AT&T Samsung Galaxy S 5] NavSad:
Can we flash a KitKat kernel?

Cause I found this here:http://xdaforums.com/att-galaxy-s5/general/nce-flasher-odin-to-safestrap-t3087450
[AT&T Samsung Galaxy S 5] AptLogic:
I think we could if you try using FlashFire to flash down to NCE. If you were to just flash a KitKat kernel on top of a non-KitKat build you'd softbrick.
[AT&T Samsung Galaxy S 5] dave1977nj:
I can't get past 18% with Kingroot 5 Android 6.0.1
[AT&T Samsung Galaxy S 5] Raphu88:
flash to coi5 using odin, then try.
[AT&T Samsung Galaxy S 5] AptLogic:
Refer to the warning on Post 1: "WARNING FOR ANDROID 6 USERS: KingRoot does not work on some builds of Android 6.0/6.1 for this device. Because of this, I am going to say now that this root does NOT work on 6.0 basebands. BUT: You can easily downgrade from any Android 6.0 build to Android 5.1.1 using the instructions in post #2, and then root."