yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 5] DejaVuAgain:
I don't think there's any other option once you're on 5.x

There are lots of working roms, but they all require ChainFire to flash (which requires root).

What I'm trying to do is get a rooted rom flashed via ODIN.

I'm hoping that the "modified" ODIN will do that.

It seems to flash & get a "Pass", but I don't have feedback about the result yet ...
[AT&T Samsung Galaxy S 5] wforider:
It flashes it passes but no root
[AT&T Samsung Galaxy S 5] 719c6:
Tries but getting error unable to copy busybox - permission denied
[AT&T Samsung Galaxy S 5] DejaVuAgain:
What build shows in the "about Device" screen?
[AT&T Samsung Galaxy S 5] wforider:
http://cloud.tapatalk.com/s/586a906b18831/Screenshot_2017-01-02-09-38-32.png?
[AT&T Samsung Galaxy S 5] AptLogic:
rip

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1203)..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1203)..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

What you are seeing there is me flashing the AP and then going back into download mode and flashing the Kernel. Phone rebooted and NOTHING CHANGED. Seems like the phone just altogether rejected the update even if ODIN returned a Pass.

My first red flag was when the entire AP only took 7 seconds to download.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Thank s ...

If this is right after flashing AP_X_G900A_ROM_DVA_10.tar then the "modified" ODIN is not successfully flashing the system partition, even though it says "PASS".

Does the progress bar on the phone's download indicate flashing progress?

After the flash, is there a 5 minute bootup?
[AT&T Samsung Galaxy S 5] wforider:
That is correct same happened for me

---------- Post added at 09:50 AM ---------- Previous post was at 09:46 AM ----------

Yes no matter which build starting from OI5 PA2 I tested it same results
[AT&T Samsung Galaxy S 5] AptLogic:
The progress bar does run (too fast though) but there is no 5 minute bootup, it just goes right into the old OS.
[AT&T Samsung Galaxy S 5] wforider:
No 5 min boot up which was my first clue
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Ah ok ...

It looks like the "modified" ODIN doesn't work after all.

Thanks for testing ... it looks like another dead-end for now.

I still don't know what the DeviceInfo checkbox does in that ODIN ... perhaps someone could try to flash with that unchecked?

Also, is the result the same if you start from OF3?

I'm going to go back to trying to get the stock ODIN to accept my system partition.

I may have to dust off my rather rusty reversing skills & tackle ODIN myself.

I'm grateful to finally have root & I sure hope I can share it.

All in all, an interesting journey ...
[AT&T Samsung Galaxy S 5] AptLogic:
good luck lol

THE EXPERIMENT WAS A FULL SUCCESS!! Guide coming up in Post 2, stay tuned!!
[AT&T Samsung Galaxy S 5] lingo2012:
Well i will just wait then lol
[AT&T Samsung Galaxy S 5] AptLogic:
guide has been published in reply 2 (post 3).
[AT&T Samsung Galaxy S 5] lingo2012:
Awesome thank you. Alliance rom is a themed rom i was gonna check it out but im really wanting the samsung theme store, ill have to figure out which rom has it. Excited, very great news,
[AT&T Samsung Galaxy S 5] frustrated_photog:
This is huge...i just registered to XDA to thank you both Lingo and AptLogic ( i used to lurk here :) )

Problem is i am using the marshmallow PH3 firmware

How can i go back to Lollipop so i can abuse phone and root it with Kingroot v5 apk ?
[AT&T Samsung Galaxy S 5] lingo2012:
Downgrade using the guide in the second post
[AT&T Samsung Galaxy S 5] NavSad:
[MENTION=7597286]AptLogic[/MENTION]

In your guide it says to re-root with 4.8.1. How are we supposed to re-root if we are all ready rooted?
[AT&T Samsung Galaxy S 5] AptLogic:
Alliance has Samsung Theme Store, I was just looking at it in Settings. [MENTION=7533813]NavSad[/MENTION] there is an uninstall option in KingRoot general settings. Just use that, wait for it to complete, and then re-root with KingRoot 4.81 (it'll probably throw a fit if you try to root with just 4.81, but I've done it once)
[AT&T Samsung Galaxy S 5] frustrated_photog:
Thanks lingo... so i am going to flash that file with Odin...but i am afraid/nervous of bricking the phone because i heard that with S5 ATT you can't revert to older baseband firmware
[AT&T Samsung Galaxy S 5] lingo2012:
Yes you can I downgraded to OI5 the same one in the second post no problems.
[AT&T Samsung Galaxy S 5] AptLogic:
As long as the baseband begins with G900AUCU4 or G900AUCS4, you'll be fine flashing OI5, just make sure to back up! (Not responsible for loss of memes if you don't!)
[AT&T Samsung Galaxy S 5] frustrated_photog:
I am on G900AUCS4DPH3 so i should be good to go.... awesome :good::good::good::good:
[AT&T Samsung Galaxy S 5] Mavy1000:
So I tried going down to OI5 and redid all the steps but once again after I update SU Binary and reboot I lose root. Is anyone else having this problem? I was on PH4 prior to starting this process.
[AT&T Samsung Galaxy S 5] AptLogic:
Really peculiar... try without updating the SU Binaries and let's see what happens. All you really need is basic SuperSU to get FlashFire to work and flash pre-rooted OF3

I AM SEEKING PEOPLE WITH ATT S5's THAT WOULD LIKE TO HELP ME WITH AN EXPERIMENT, REPLY AND MENTION [MENTION=7597286]AptLogic[/MENTION] IF INTERESTED!
[AT&T Samsung Galaxy S 5] lingo2012:
[MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] NavSad:
[MENTION=7597286]AptLogic[/MENTION]
[AT&T Samsung Galaxy S 5] Vesnyx:
YAY! Good job [MENTION=7597286]AptLogic[/MENTION]

Not interested in experiment btw, but congratulations on finding a working root method!
[AT&T Samsung Galaxy S 5] Kyleklit462:
Kingroot seems to not work for me I get it to about 56% then it won't go past

---------- Post added at 06:32 AM ---------- Previous post was at 06:22 AM ----------

@AptLogic ill give you a hand with your experiment if you can help me out :)
[AT&T Samsung Galaxy S 5] skyrocketeer:
Great job AptLogic. Now time to wait for root on marshmallow :P
[AT&T Samsung Galaxy S 5] AptLogic:
[MENTION=4911082]lingo2012[/MENTION] [MENTION=7533813]NavSad[/MENTION] so here is the experiment:

I want to see if it is possible to use Flashfire to go from COI5 to one of the Nougat ROMs for KLTE.

So what I want you to do is go download the Resurrection Remix 7.1 ROM from the S5 unified development forum, along with OpenGApps, and try going into Flashfire > Wipe, Flash Zip or OTA Resurrection, and Flash Zip or OTA GApps

In that order
[AT&T Samsung Galaxy S 5] AptLogic:
I tried with the DeviceInfo checkbox unchecked and absolutely nothing happened. The program would hang at CheckFile or something like that. Bottom line is it just fails.
[AT&T Samsung Galaxy S 5] eviljonny1:
You sound like such a douche in every post you make

Seriously, dude. Stop whining. Your tone is always hostile and douchy. Lighten up. No one cares that you cannot root (or if you bricked) your phone. Now grow up..
[AT&T Samsung Galaxy S 5] DejaVuAgain:
I'm not quite ready to give up on the "modified" PrinceComsy ODIN just quite yet.

Based on the feedback about the 7 second "flash", it seems clear that the DeviceInfo checkbox in fact downloads info from the phone, perhaps partition info, whatever, for subsequent flashing.

After more testing, I noticed that my kernel would just hang at the file analysis stage.

I tried a different ODIN packager to make a .tar.md5 file & that file in fact tries to flash but fails as non-stock software.

That's kinda expected 'cause that's what the bootloader is (definitely) enforcing.

I don't know what's modified in the PrinceComsy ODIN (other than bypassing SHA), but I have to assume it's trying to address the issue of flashing a non-stock system partition.

So it's not quite the end of the road yet.

I'm making another package with a proper .tar.md5 structure.

I'll post when that's ready to go ...
[AT&T Samsung Galaxy S 5] wforider:
Ready to brick when you are
[AT&T Samsung Galaxy S 5] invert_nexus:
For those that aren't too savvy about this sort of thing, in the s5 the number is mmcblk0p23 as in:

dd if=/dev/block/mmcblk0p23 of=/sdcard/system.img

root@kltetmo:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 2014-04-11 22:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-04-11 22:14 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-04-11 22:14 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-04-11 22:14 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-04-11 22:14 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-04-11 22:14 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-04-11 22:14 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-04-11 22:14 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-04-11 22:14 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-04-11 22:14 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-04-11 22:14 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-04-11 22:14 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-04-11 22:14 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-04-11 22:14 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-04-11 22:14 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-04-11 22:14 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-04-11 22:14 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-04-11 22:14 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-04-11 22:14 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-04-11 22:14 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-04-11 22:14 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-04-11 22:14 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-04-11 22:14 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-04-11 22:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-04-11 22:14 userdata -> /dev/block/mmcblk0p25

root@kltetmo:/ # dd if=/dev/block/mmcblk0p23 of=/sdcard/system.img
5251072+0 records in
5251072+0 records out
2688548864 bytes transferred in 383.154 secs (7016888 bytes/sec)
root@kltetmo:/ #

Although, I tried the command without root and it doesn't work.

Do you mean to backup a rooted system?

Mine is twi5ted lollipop, probably not what you're looking for.
[AT&T Samsung Galaxy S 5] samccfl99:
I never said I bricked my phone or that I was not rooted. Read, please. As a "senior" member of XDA, you should know a bit about the rules. You might get a "visitor". Ridiculous.

Please, anyone who is rooted, please do not play these games with your phone. The S5 is a great phone, but playing with it like this, it could become easily unrooted. I will not say anymore. This thread has already done enough damage...
[AT&T Samsung Galaxy S 5] DejaVuAgain:
The command works on a rooted system, & yes block 23 is the system partition.

The dump it produces is by directory & file rather than an image.

It's equivalent to what you get using the backup option in ChainFire.

Backing p a rooted system is relatively easy, even without a custom recovery ... just another reason to root.

---------- Post added at 08:42 PM ---------- Previous post was at 08:34 PM ----------

DVA_X_G900A_ROM_ALPHA2 ready for test ...

While packaging up ALPHA2 I noticed that I had compressed AP_X_G900A_ROM_DVA_10.tar which is probably why it hangs at the file validation step.

The ODIN packager app seems to mess up the binary when adding md5, so let's try a naked uncompressed tar

Get DVA_X_G900A_ROM_ALPHA2 here

Don't change any settings in ODIN ... just load up the AP slot & let's see what happens.

If the file format is finally right, perhaps the PrinceComsy ODIN will work as intended.

Again, testers should be unrooted & comfortable with recovery to stock ...
[AT&T Samsung Galaxy S 5] wforider:
Testing........

---------- Post added at 12:31 PM ---------- Previous post was at 11:49 AM ----------

fail Unsupport dev_type

---------- Post added at 12:31 PM ---------- Previous post was at 12:31 PM ----------

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1203)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> system.img

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1203)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> system.img

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<OSM> All threads completed. (succeed 0 / failed 0)

<ID:0/005> Removed!!

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1203)..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

with device info checked it flashed

no change

---------- Post added at 12:47 PM ---------- Previous post was at 12:35 PM ----------

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1101)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> system.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

non moded odin 3.11
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Thanks for the feedback ...

At what point do you get "fail Unsupport dev_type" & how did you bypass it?

The error isn't surprising since the PrinceComsy ODIN comes from an S7 forum.

As I said before based on the 7 second runtime, the DeviceInfo box allows the flash to appear to run, but I think it's retrieving phone data.

Would you please try flashing ALPHA2 with a stock ODIN & let me know what happens ...

Wait a second ... looking at the engine version numbers, I think you already tried the modified ODIN as well as 2 stock versions.

Is that correct?
[AT&T Samsung Galaxy S 5] wforider:
I did look at my last post

<ID:0/005> Added!!

<ID:0/005> Odin engine v(ID:3.1101)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> SingleDownload.

<ID:0/005> system.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

---------- Post added at 12:54 PM ---------- Previous post was at 12:52 PM ----------

correct
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Back to the drawing board ...

It looks like the rom file format is OK now, so the next line of attack is to look more deeply into the workings of the PrinceComsy ODIN to try to get it to work with the S5 ...
[AT&T Samsung Galaxy S 5] EfWithEffectz:
Ummm... yesterday I was in the middle of rooting and became impatient with King Root so I just quit it and like 50 percent. Now the screen looks like this. Does this mean I have root ?
[AT&T Samsung Galaxy S 5] oka1:
FROM THE MODERATOR -

People I must remind all of you .......... Rooting and customizing is not for the Newbie or the weak minded person ...... When you begin down the path of rooting...etc. You are Now Taking FULL RESPONSIBILITY for your actions alone.

It it up to you to figure if the Dev of person posting ROMS, Hacks or Customizing Patches Has done his due diligence or not.

In other words it is YOUR responsibility to make sure what you decide to flash is safe or not or if it is beyond your skill set.

Remember no one is twisting your arm ....... it is your choice and if you Bork your device ........ then ......... look into the mirror to see who is at fault.

This is why We ALWAYS say READ, READ, READ .... make sure you understand enough before jumping into something ........ not after you jacked up your device and then, come looking for a savior to help you out of your predicament ....... This is XDA not a Church, Religion or Cult. WE all strive to improve our devices and together we can, but not with whiny complaints from under skilled people who endeavor on flashing stuff beyond their level of understanding.

ATT and Verizon make things even harder for the Dev's if you really like flashing things then look at other carriers who are not so hell bent on locking EVERYTHING down.

Be kind, be civil when posting

Thanks ~~~ oka1
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Use a root verification tool (search the play store), or just install an app that requires root (Root Explorer, Titanium, ChainFire, etc) & see if it asks for or gives SU access ...

You just may have luckily interrupted Kingroot at a good moment.

If so, try installing ChainFire so that you can get to rooted OF3.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
DVA_X_G900A_ROM_ALPHA2a ready for testing ...

Hello again testers ...

After trying to contact PrinceComsy without success, I decided to simply reverse engineer his reversal.

Assuming his actually works (& it seems to on the S7), it should work on the S5 ... that is if the latest Odin (v3.13.3) runs ok.

Get DVA_X_G900A_ROM_ALPHA2a here

This package contains a stock Odin, my DVA version & the rom

The test required is to first ascertain whether v3.12.3 will flash something stock in the AP slot on the S5.

Let me know if it doesn't run & I'll try patching an older version Odin.

If the stock Odin runs ok, then try flashing the rom with the DVA Odin.

With any luck it will load ...

On second thought, try the DVA Odin first & if it doesn't work, then please try the stock Odin with a stock file (kernel, rom, whatever) to test if the stock Odin runs ok.
[AT&T Samsung Galaxy S 5] AptLogic:
The modified ODIN seems to have no problem flashing a stock OI5 kernel, but hangs at File analysis when flashing the OC4 kernel. It throws an UNSUPPORT DEV_TYPE error on my phone when I try the DVA ROM tarball:

<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The stock ODIN doesn't even OPEN! Instead it gives me the nice little error message you see in the attachments.

Hope this helps!
[AT&T Samsung Galaxy S 5] simstimstar:
The .md5 is there so that you can be sure whether or not you have an unaltered copy of a given odin file (I say this because you were questioning the authenticity of a given image). I'm guessing that you can strip the MD5 hash out of the first few lines of the file with grep or similar. Then change the filename to .tar instead of .tar.md5, run the .tar file through your md5 hasher, and compare the hash to the line stripped from the odin file. MD5 hash should = MD5 hash

Now that you have an authenticated tar file you can flash it directly from odin.

You could just bypass all of that by leaving the file as .tar.md5 because odin will automatically check the MD5 sum when the file extension is .md5.

Apologies if I come across like an ass tonight. I'm in a weird kind of a mood :D I probably have no idea what i'm blathering about, anyway!
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Thanks AptLogic ...

Yes, it's all helpful.

This remote debugging is kinda tough, but interesting .... makes you focus.

The fact that OI5 flashes & not OC4 shows that v3.12.3 is not compatible with 5.0

That means that I'll have to patch v3.11.1

It will involve a bit more work 'cause I'll have to find the equivalent subroutines in the older code.

I presume that will fix the "unsupported dev type" issue.

The error message you got with the stock Odin basically says "odin.ini file not found".

Any chance you ran the exe away from the ini?

(BTW, I don't read Korean, but I did snip the text out of your screenshot, OCR'd it & then popped it into Google Translate ... & voila ... "no file found").

Given that the S7 people are using a modified Odin to push a custom bootloader, I think I'm on the right track with this.

I'll ping you when I have a new(old) Odin ready ...

---------- Post added at 05:45 AM ---------- Previous post was at 05:10 AM ----------

I'm not sure exactly what you're trying to tell me ...

I wouldn't say "no idea what i'm blathering about" ... let's say "some idea".

The md5 hash is in fact concatenated onto the

end

of the tar file.

It's entirely optional in Odin ... a security measure as you suggested.

You might have noticed when you put a big stock rom into the AP slot rather than a little kernel, that it takes along time to come back ... well that's because it's verifiying the md5.

So what is it that you were sayin' ? ...
[AT&T Samsung Galaxy S 5] simstimstar:
That is indeed what I was trying to say. Why I felt the need escapes me at the moment :D

Sorry about that.

Cheers!

-SimStim
[AT&T Samsung Galaxy S 5] wforider:
:confused:
[AT&T Samsung Galaxy S 5] dsome564:
Can I flash cyanogenmod 13 and 14 safely?
[AT&T Samsung Galaxy S 5] DejaVuAgain:
Safely? .... of course you can ...

As long as the Cyanogenmod build is for your device.

Here we're talkin' G900A & we're struggling to try to get 5.x rooted ...
[AT&T Samsung Galaxy S 5] dsome564:
Yes I have a g900a. Sorry for not clarifying.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
I don't think "you caught my drift" ...

The G900A bootloader is locked.

Right now, custom roms are just a dream ...
[AT&T Samsung Galaxy S 5] dsome564:
[MENTION=7958871]DejaVuAgain[/MENTION], refer back to page 10 on this thread, its rather interesting.
[AT&T Samsung Galaxy S 5] DejaVuAgain:
dsome564, please refer back to ALL the subsequent pages that tell the story of achieving root & then loosing that ability when Kingroot shut out the G900A.

I was one of the (probably) very few people who got root & have retained it, so everyone else is now back to dreaming ...
[AT&T Samsung Galaxy S 5] straitjacket525:
So just to clear things up for newcomers to this thread such as myself, this Kingroot no longer works on the S5 with 5.1.1.? That would also include the 6870-A S5 active correct? I've been trying the proposed methods in the thread for 2 days. I have the S5 active at&t variant. Thanks for everything

On a side note is there a reason why Kingroot removed the g900a?
[AT&T Samsung Galaxy S 5] 719c6:
I have to boast as I still have it. :highfive:
[AT&T Samsung Galaxy S 5] Respect35:
Hi i have lost my connection after root (youtube works playstore works but chrome and internet does not have connection)

My problem still working chrome and internet pages dont load, ı do clear cache and data how solve my problem
[AT&T Samsung Galaxy S 5] DejaVuAgain:
OK, so that's 2 of us ...

Actually, I'm thinking of risking my root to do some testing 'cause it's too difficult debugging remotely.

(The only thing I really need root for is to increase the phone volumes.

Everything else can be accomplished with EZ Disabler with the result of great battery life.)
[AT&T Samsung Galaxy S 5] wforider:
What kinda of test you pondering?