Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As you can see my idea was a bust but here is the original op
Okay, Lets try this here because nobody seems interested in helping in the T-Mobile section.
ThePagel said:
Correct me if I am wrong here, the reason knox is being tripped by cf auto root is because of the way it acquirers root not because it is rooted. With that in mind I would Like to make a tar ball with a pre rooted system.img. To make sure it will have the best possibility to not trip knox and not cause a soft brick I want to use a system dump from a running phone that has only been rooted. I am pretty sure this has worked on every galaxy phone before the s6 and the only reason you don't hear more about it recently is because of the success of towelroot. I am getting this phone on the 1st (so excited) and would like root but want to try samsung pay more.
If you are willing to help I need the following:
Be on a 100% stock samsung bloated system with root (absolutely no tweaked systems I need pure stock with root)
Install supersu into /system (supersu settings)
Make a system.img dump with adb or terminal emulator and upload it for me (as long as you do not dump the data partition no personal data will be dumped)
At this point I will make the tarball and upload it and have the person who made the system dump flash the tarball. If he/she boots up fine I will the need a volunteer who has not rooted and verified that knox has not been tripped on his/her phone to flash it and see if knox still has its warranty. Obviously the volunteer should go into this not caring if knox gets tripped.
To make things completely clear I need the following:
Somebody who knows how to dump with adb/terminal emulator and already rooted
Somebody without a tripped knox warranty who doesn't care if it gets tripped
Click to expand...
Click to collapse
As soon as you flash an unsigned image Knox is going to be tripped.
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
^^^ This, unfortunately, ends the discussion altogether.
Drumrocker said:
As soon as you flash an unsigned image Knox is going to be tripped.
Click to expand...
Click to collapse
Hawke84 said:
Lots of work went I to finding a solution on S4 when knox first came out including by chainfire with no luck. Also since october people have been trying to root note 4 without tripping knox with no luck.
There is no difference in the system of tripped and not tripped. Soon as anything unsigned or insecure is flashed the bootloader burns the efuse
Sent from my SM-G920F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CafeKampuchia said:
^^^ This, unfortunately, ends the discussion altogether.
Click to expand...
Click to collapse
Indeed now I get closure, thank you.
So how does safestrap work?
lowspeed said:
So how does safestrap work?
Click to expand...
Click to collapse
Doesn't matter in this instance because you need root to use safestrap. He is pretty open on how safestrap works if you look at his threads and website.
Sorry guys, which signature needs to be applied? I found a guide to sign Windows modded drivers, I don't know if this can be applied here, too...
The real trick is getting it signed. There might be no easy way to do that unless the key method can be replicated to make signed binaries. This could be a samsung proprietery tool. That said I did find an interesting nugget of info hxxp://galaxys4root.com/what-is-binary-counter/ in the comments section.
HI,
I flashed pre rooted firmware 4.2.2 using ODIN on my Samsung I-9500 4.2.2. Then the status is remain same
Binary : Samsung Official
System : Official.
Then I installed Wanam apk to modify the UI, It asked me to download Xposed framework I grant Super user permission. Once It completed I checked the status
Binary : Samsung Official
System : Custom.
I flashed stock firmware 4.2.2 and did the reset factory reset. Then it changed to
Binary : Samsung Official
System : Official.
My question, Is the hidden binary count or knox counter triggered or not ?
If I updated to stock 4.3 Is the Knox Warranty bit 0×0 or 0×1 ?
Please help me.
The rooted aspect only seems to be possible provided nothing in the UI itself is changed? There is a trigger file in the rom. Something that obviously a Wanam install triggers. All that seems to indicate that it might actually be possible to have a pre-rooted rom and install via recovery. But considering the phone model referenced, its possible this particular workaround has been plugged. On the off chance that it has not. It might be the only viable way to do root without tripping knox. I imagine the existing stock roms with root preloaded however trip knox (I saw no indication of that in posts but I did not dig that deep).
If anyone can answer that in the affirmative or negative it might be worth noting. Will knox get tripped on a stock (but pre-rooted) rom?
The point of this thread is to point out something we already know and have known for some time? WTF
shollywood said:
The point of this thread is to point out something we already know and have known for some time? WTF
Click to expand...
Click to collapse
I don't think the OP was aware of all the information when he started the thread. I think the thread title has since been changed.
But yeah, i guess the thread could be closed.
Related
UPDATED POST:
Hello,
As @Dumbo53 has mentioned below posts, there is a root method by the developer @designgears and it seems that this root method does NOT trigger the knox flag.
Unfortunately, it is just for the AT&T Note 3 devices.
Maybe someone could port this root method for our international N900 and N9005 model devices?
Root de la Vega:
http://forum.xda-developers.com/showthread.php?t=2474422
----------------------------------------------------
Hello there,
I wanted to share something from Chainfire's Auto-Root thread.
Chainfire has mentioned:
Using this root method sets current binary and system status to custom. Additionally, it will also trigger the KNOX warranty void status.
This device store the traditional flash counter. Nor is is possible with Triangle Away to reset the current binary status. You will need to flash a stock kernel and stock recovery to reset the binary status.
The KNOX warranty status change is permanent, and a service center may deny warranty based on this flag - even if the other flags are reset correctly. The KNOX flag being tripped may also prevent certain Samsung KNOX features from working (enterprise security features).
If this is something you care about, use a root method not based on custom kernels or recoveries, like a modified system partition. These are possible, but I don't personally make them, so look around!
Click to expand...
Click to collapse
So my question is simple:
Is there any talented developer who can look at the system partition on the devices N900/9005 and somehow to look if he can modify it to root without triggering the knox counter. Iaw chainfire's post, it seems to be possible, but we need a talented developer to look for this
I would be really so happy, if it can be done this way...
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
BlueChris said:
No because if you do anything you alter the md5 checksum m8 and knox watch this
Sent from my SM-N9005 using Tapatalk 4
Click to expand...
Click to collapse
I was talking according to Chainfire, dude. He just showed us that there could "may be" a way to root without knox would recognise this.
I think may be knox watches only the bootloader and recovery situation (if it is custom or official).
Chainfire's root method includes to flash first insecure recovery and after root flashes back the official recovery. During this process knox recognise the shortly time with the insecure recovery and the counter goes to 0x1. But iaw Chainfire's post, i think if someone could root without touching the recovery or kernel, it could be possible not to trigger the knox during the root process.
I don't think we will have a way to bypass it. I think once you get root it will still trigger it.
Funny how this is something from an Android device and not an iDevice.
Guess Samsung got tired of fixing devices after someone oc the hell out of it!
Sent from my SM-N9005 using XDA Premium 4 mobile app
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There already is a root method that doesn't trigger the Knox flag by designgears, but as of now only for At&t Note 3 (Root de la Vega). It however only gives root, not a custom recovery. There are already people begging him to port it to other devices and he seems to be willing to do them one by one.
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
Thanks mate, i will also look to his thread and beg him for n900
Sounds promising. Don't really need a custom recovery thanks to xposed.
Sent from my SM-N9005 now Free
Knox problem thanks (lovelesss)
we are waiting for n900 please
n900 I want to wait for the Root de la Vega.
What about N9005?
vinokirk said:
What about N9005?
Click to expand...
Click to collapse
+1
Sent from my SM-N9005 using Tapatalk 4
vinokirk said:
What about N9005?
Click to expand...
Click to collapse
Yeah I can add N9005 also as request on this topic.
Changing the subject of this thread just a sec
I don't have any information showing Knox flag in Odin mode, Exynos SM-N900. Does this mean my phone doesn't have this flag?
I recently purchased a SM-N900W8. Love this device, just retired my S2 which i messed around with for a few years and never had issues...
I neglected to do research on XDA (Big mistake) before rooting it and had no idea about the repercussions of this KNOX issue.
I used this method to root it (http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/)
I successfully installed CWM recovery and SuperSu and the phone is rooted. I had no intentions of installing Custom Roms just yet just wanted to be able to use some of my favorite apps that require rooting. The phones Current Binary and Phone status have both been tagged custom but my KNOX Warranty Void is still tagged at 0X0. Needless to say maybe I got lucky?
I was hoping to Revert to Stock and Unroot so I could follow this method instead (http://forum.xda-developers.com/showthread.php?t=2498850)
Is there anyways to Accomplish this without tripping the KNOX counter? I've been scouring the forums for several hours trying to find a concrete answer but cannot.
I have downloaded my stock firmware (http://www.sammobile.com/firmwares/3/?download=26653)
Any help or suggestions would be greatly appreciated. I have included a screenshot of my device info. I apologize in advance if this issue has already been addressed.
Thanks,
-Rob
For device info and Knox warranty status, you can use my app Phone INFO ★Samsung★ to get more detailed info.
Download link in my signature.
Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005
Dejan Sathanas said:
Why did you even install CWM if you didn't need it ?
Why do you want to remove it ? Don't fix it if it ain't broken. De la vega will trip Knox in 4.4, so leave it as it is.
Sent from my N9005
Click to expand...
Click to collapse
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.
SSJ3Rob said:
Will do. Was just worried about official updates and warranty if phone still says custom but knox is not tripped. But bell outsources another company for repairs and doesn't send back to Samsung directly so I probably don't need to worry to much..
I used CWM because I've used it for a couple years with my S2 and enjoyed the features so when I saw cwm was avaliable for note 3 I jumped on it.
But there is no way to revert to stock without tripping count?
Thanks.
Click to expand...
Click to collapse
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Khizar said:
Flashing stock using odin should rever everything back to stock and possibly not trip knox counte, I am saying possibly cuz nobody has tried to flash stock recovery and try to keep knox cool as custom recoveries have tripped everyone's knox AFAIK. But your phone FW or maybe something else might make your device an exception.
Click to expand...
Click to collapse
I will leave as is for now until more info on the subject surfaces. As much as I want to try to flash back to stock recovery and test your theory I will hold out and not mess around with CWM or mess with apps requiring root to much incase it decides to trip the counter.
Thanks.
Now that we have Root without KNOX problems.. Will it ever be possible to flash custom Recovery / Roms too... And still have KNOX 0x0 ?
You can use Safestrap Recovery
Please read carefully before taking any step
What version of Safestrap revovery to use on the F model ?
joeherlev said:
What version of Safestrap revovery to use on the F model ?
Click to expand...
Click to collapse
Safestrap is only for ATT and Verizon devices afaik, it probably does not work on the G900F.
Okay.. So I wont try.. Will it ever be possible to have custom recovery for F model then without KNOX 0x1 ?
joeherlev said:
Okay.. So I wont try.. Will it ever be possible to have custom recovery for F model then without KNOX 0x1 ?
Click to expand...
Click to collapse
Not atm, KNOX is impossible to hack as security is iron clad
gee2012 said:
Not atm, KNOX is impossible to hack as security is iron clad
Click to expand...
Click to collapse
But how can it be done on models with locked bootloader then ?
joeherlev said:
But how can it be done on models with locked bootloader then ?
Click to expand...
Click to collapse
Safestrap creates virtual partitions afaik and writes data on those, look here http://forum.xda-developers.com/showthread.php?t=2793891 for more info.
joeherlev said:
Now that we have Root without KNOX problems.. Will it ever be possible to flash custom Recovery / Roms too... And still have KNOX 0x0 ?
Click to expand...
Click to collapse
Sure. Anyone who says otherwise is exercising a certain failure of imagination.
That however doesn't mean that it is easy. And you certainly can't put a fixed time frame on it. A few weeks ago we couldn't root the locked bootloaders on a Verizon or ATT phone. Then Pinkie Pie discovered the CVE-2014-3153 vulnerability and Geohot developed the towel root exploit on that doorstep.
And if you haven't been following the forums here recently we've seen some exciting work and success in not only downgrading a device from Kitkat to Jellybean but also undoing the Knox flag in the process. Something that Samsung told us was impossible. But now we find that Samsung was playing fast and loose with the truth again. They told us that the Knox qfuse was a permanent and irreversible OTP. But it turns out that qfuses, or some of the qfuses at least can actually be reset if we are creative.
Samsung probably does this to make their own code development easier. Certainly it's easier for them to reset a Knox flag than have to replace a motherboard when factory refurbishing devices. The lesson in all of this is to take pronouncements that something is impossible with a grain of salt. All is not always as it seems. Yes the day will come when we can flash a custom recovery or kernel and still have a 0x0 Knox flag.
.
Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.
MaxiBizzle said:
Hi,
Its been a few years since ive Rooted or been ontop of the forums ect.
Just wanted to let other people know my experience with Un-Rooting my S5 GM-900F
- Rooted with Odin + tar file
- Un-Rooted with Super SU
- Typically their is now an update available but cannot update as Samsung recognise that the phone was previously rooted.
- On a PC or Mac download Kies and update.
- Nothing has flagged up with any counters, did not experience any problems with KNOX
Hope this helps everyone.
Click to expand...
Click to collapse
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.
castillofr said:
Using CF Auto Root increases your flash counter and trips the KNOX warranty flag!
Unrooting with SuperSU and updating with Kies have reset the KNOX WARRANTY VOID to 0x0?!
Until now, it was impossible to reset KNOX!!!
Please confirm
Click to expand...
Click to collapse
Hi,
Well the uninstall of SuperSU went ahead with no problems, a box did flag up saying something about would you like to disable KNOX before continuing and just confirmed it.
Since the Un-Root, i have just opened KNOX again and havent had any problems at all. I did complete a factory reset just for my OCD needs with it and nothing has been triggered and no flags or counters. Still have the KNOX app with the set up wizard client available to get it going if i ever need it again so..
Didnt realise that people where having a problem with KNOX if im honest, when i finish work i shall have a play around with it and update this if i encounter any problems.
gee2012 said:
Not true, KNOX will still say 0x1 after unrooting, he probably means the system status and binaries are reset to Official again.
Click to expand...
Click to collapse
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.
MaxiBizzle said:
This might well be the case, i dont fully understand all of the tech terms regarding the binaries but only have a little knowledge when it comes to checking the counters and any flags or problems.
- Say for example that KNOX was tripped, a) What would happen and when/where would i encounter a problem and b) Is their any detrimental effect on the overall phone or just for KNOX?
Regards.
Click to expand...
Click to collapse
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.
gaudent 206854
gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again if you flashed a stock rom.
Click to expand...
Click to collapse
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!
MaxiBizzle said:
Hi,
Well KNOX is working as it did the first day i got the S5 and havent encountered any problems nor seen any flags. IF their were to be a void flag 0x1 where would i see this?
I was just nosing around on the forums and saw that alot of people were Un-Rooting via SuperSU and then using Kies to then boot the stock rom.
Thanks for your help and advice. Sorry this seemed like a dud thread!
Click to expand...
Click to collapse
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.
kararye and
gee2012 said:
KNOX is only tripped intentionaly (not by accident), that is if you root with CF Auto Root or flash a custom recovery or kernel with (Mobile) Odin.
Click to expand...
Click to collapse
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?
MaxiBizzle said:
Ok no worries. Completed the Root with Odin v3.09 i believe, did not flash any custom roms or anything was just playing around with xposed installer, Mobile Odin was never used.
Not sure if that makes any difference?
Click to expand...
Click to collapse
What what software did you root with Odin? If you used CF Root your flag is 0x1.
gee2012 said:
What what software did you root with Odin? If you used CF Root your flag is 0x1.
Click to expand...
Click to collapse
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root
MaxiBizzle said:
Hi,
Oh right i see what you mean now, sorry for the delay. It was CF-Root
Click to expand...
Click to collapse
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.
gee2012 said:
As you live in the EU warranty for the device is still valid when rooted/tripped KNOX unless the manufacturer can prove the issue is caused by rooting.
Click to expand...
Click to collapse
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.
MaxiBizzle said:
Hi,
Oh right i didnt know that. Is it just within the EU that the warranty is still valid? Are their any other countries that are the same?
Just a general question then, with regarding the voidance of KNOX or anything, would that only effect me if i wanted to send the phone back for whatever reason? The counters for example wouldnt made a difference for my phone and daily useage anyway so if i just keep the phone and continue to not having any problems i could have as many counters on it as possible?
Just getting my head around the whole void/counters thing.
Click to expand...
Click to collapse
Afaik only in the EU by EU law wich superceeds OEM terms/conditions.
gee2012 said:
KNOX, Private Mode and off course warranty are affected when the KNOX void flag says 0x1 and you are rooted. If you unrooted correctly as discribed by the OP Knox and Private Mode should work again after you flashed a stock rom.
Click to expand...
Click to collapse
I have currently official status but Knox 0x1.
The one & only thing concerned then is warranty. Knox based apps and all others should work as before Knox 0x1.
Hawke84 said: "If the Knox warranty void line says 0x1 then you cannot use knox softwareas your device has been flagged as insecure. By this i mean that if your workplace / company supports bring your own device to work for corporate emails etc and they use knox to keep security your device will not allow this. You are still able to use future samsung firmware releases with the knox flag 0x1. hope this makes sense. sorry for any confusion this has caused!"
Is there any way to root a Galaxy S5 G900V running Lollipop without tripping KNOX?
I'm not looking to use a custom rom, I am just trying to get root for data recovery. (Deleted Photos)
Yes. There are plenty of threads discussing how to root Lollipop. Browse around this forum and you'll find them!
As of right now the only root method for Lollipop I know of is flashing a custom ROM, but there is one that is 100% stock with root.
mrjiggywiggy said:
As of right now the only root method for Lollipop I know of is flashing a custom ROM, but there is one that is 100% stock with root.
Click to expand...
Click to collapse
I think that may potentially destroy the data I'm trying to get. Will that method trigger the Knox warranty flag?
chakotay2 said:
I think that may potentially destroy the data I'm trying to get. Will that method trigger the Knox warranty flag?
Click to expand...
Click to collapse
I believe so, as when I boot my phone it says "Custom."
mrjiggywiggy said:
I believe so, as when I boot my phone it says "Custom."
Click to expand...
Click to collapse
Showing the custom boot screen does not mean knox is tripped. Go to the play store and install samsung phone info app. It shows the knox status. I have rooted and rolled back to stock a number of times although not to 5.0, have had the 'custom' screen and my knox status is still 0x0 which is 'not tripped' ...
Chopstix9 said:
Showing the custom boot screen does not mean knox is tripped. Go to the play store and install samsung phone info app. It shows the knox status. I have rooted and rolled back to stock a number of times although not to 5.0, have had the 'custom' screen and my knox status is still 0x0 which is 'not tripped' ...
Click to expand...
Click to collapse
@mrjiggywiggy Could someone please let me know where the " ... one that is 100% stock with root" can be found? I have a new Developer Edition Verizon S5 (SM-G900V, baseband version 0900V0YU1BOC4) running lollipop 5.0.
Of course, I want to avoid tripping KNOX if at all possible. I've searched dozens of sites, and hundreds of pages in 30-40 XDA-developers threads, but I haven't found a solution.
If possible, I'd like to not have to downgrade to 4.x first. Thanks in advance!!
nataliegrn said:
@mrjiggywiggy Could someone please let me know where the " ... one that is 100% stock with root" can be found? I have a new Developer Edition Verizon S5 (SM-G900V, baseband version 0900V0YU1BOC4) running lollipop 5.0.
Of course, I want to avoid tripping KNOX if at all possible. I've searched dozens of sites, and hundreds of pages in 30-40 XDA-developers threads, but I haven't found a solution.
If possible, I'd like to not have to downgrade to 4.x first. Thanks in advance!!
Click to expand...
Click to collapse
You do not want to flash that ROM because it will lock your bootloader. You have a developer edition so your bootloader is unlocked. Flashing a ROM for the retail version will lock your bootloader. You have to look for ROMs that say "dev ed" or "de" in the thread title.
nataliegrn said:
@mrjiggywiggy Could someone please let me know where the " ... one that is 100% stock with root" can be found? I have a new Developer Edition Verizon S5 (SM-G900V, baseband version 0900V0YU1BOC4) running lollipop 5.0.
Of course, I want to avoid tripping KNOX if at all possible. I've searched dozens of sites, and hundreds of pages in 30-40 XDA-developers threads, but I haven't found a solution.
If possible, I'd like to not have to downgrade to 4.x first. Thanks in advance!!
Click to expand...
Click to collapse
Knox is not even an issue with the Dev edition anyhow. Just be wary of what has already been stated so you don't turn your Dev phone into a retail version.