Related
Hello, everyone,
my note 3 runs android 4.4.2, has 0x0 (since that it has not yet been rooted) and I'd like to keep it that way.
So, my question is: is there a rooting method that will not trip my knox?
Thanks in advance for help.
Sent from my SM-N9005 using xda app-developers app
n0t3 said:
Hello, everyone,
my note 3 runs android 4.4.2, has 0x0 (since that it has not yet been rooted) and I'd like to keep it that way.
So, my question is: is there a rooting method that will not trip my knox?
Thanks in advance for help.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
There is not a way to root it without tripping KNOX, it's possible only for Jelly Bean
And downgrading is not possible either, so I'm kinda stuck for now, huh...
Well, anyway, thanks for the quick reply!
Sent from my SM-N9005 using xda app-developers app
I'm on KitKat too... I don't care about tripping KNOX, is there a guide to root the stock KitKat ROM?
Lieu10ant said:
I'm on KitKat too... I don't care about tripping KNOX, is there a guide to root the stock KitKat ROM?
Click to expand...
Click to collapse
Probably atleast 10 guides. It will take less than 5 minutes to root.
Sent from my SM-N9005 using Tapatalk
Lieu10ant said:
I'm on KitKat too... I don't care about tripping KNOX, is there a guide to root the stock KitKat ROM?
Click to expand...
Click to collapse
CFautoroot.
3 mins to read, 1 min to download, less than 1 min to flash via odin.
Sent from N7105, DN3 with AGNi kernel.
I was hesitating to root or not to root, but I don't like Android without root, so I have rooted it with CFautoroot and we are both happy with tripped KNOX so I suggest to root
Hi
I used CF auto root. It works fine ..
Now, I´ve got the following status:
current binary: custom
system status: custom
know warranty void: 0x1
Click to expand...
Click to collapse
I dont care about the the knox status, but I want to change the custom status to update my phone with Samsung updates. I downloaded TriangleAway v3.26 but I cant choose the option (see attachment). As I understand I can use the App to block the status but it doesnt work. And I have no idea what "System executable needed to implement workaround not found" means. Where can I find the workaround and where shall I store it on my device ?
The second message I dont understand too. I dont find another version in the play store... I think its the same version like in the board?
Maybe someone could help me
fL!p said:
Hi
I used CF auto root. It works fine ..
Now, I´ve got the following status:
I dont care about the the knox status, but I want to change the custom status to update my phone with Samsung updates. I downloaded TriangleAway v3.26 but I cant choose the option (see attachment). As I understand I can use the App to block the status but it doesnt work. And I have no idea what "System executable needed to implement workaround not found" means. Where can I find the workaround and where shall I store it on my device ?
The second message I dont understand too. I dont find another version in the play store... I think its the same version like in the board?
Maybe someone could help me
Click to expand...
Click to collapse
Yeah, but you need to uninstall the version you have and pay for the google play version..... It is a paid app on google play store...
ultramag69 said:
Yeah, but you need to uninstall the version you have and pay for the google play version..... It is a paid app on google play store...
Click to expand...
Click to collapse
And after that I can reset the modified status and install the offered Samsung updates?
And what about: "System executable needed to implement workaround not found"
fL!p said:
And after that I can reset the modified status and install the offered Samsung updates?
And what about: "System executable needed to implement workaround not found"
Click to expand...
Click to collapse
You can also install xposed framework and use the cosmetic system normal mod. This will make it look "Official" in settings...
I don't know if this will allow OTA, most people just use ODIN to flash what they want - but you most definitely will loose root doing an OTA.
fL!p said:
And after that I can reset the modified status and install the offered Samsung updates?
And what about: "System executable needed to implement workaround not found"
Click to expand...
Click to collapse
If the device is rooted. I would never suggest OTA updates. Odin is the way to go.
Sent from my SM-N9005 using Tapatalk
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
banerbocken said:
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
Click to expand...
Click to collapse
Works perfectly!
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Alestilohomer said:
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Click to expand...
Click to collapse
Towelroot installs needed files for root. I didnt install SuperSU at all from play store cause its not latest version.
ChainFire is updating SuperSU soon and when latest version (1.99) is online you can install it from play store.
After Towelroot I just installed Titanium Backup (and pro key) and freezed all crap including knox.
After using towelroot on a KNOX-enabled stock 4.3 device, is is possible to revert back to the 4.2.2 bootloader without burning the e-fuse?
Ok, tried to delete system apps, including the knox ones, with root explorer and was successfull!
And about the downgrade, it will change the knox status for sure, because knox is in the bootloader too, not only the apps and libraries, and here, root doesn't made any chance...
Enviado desde mi GT-I9506 mediante Tapatalk
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
tlund said:
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
Click to expand...
Click to collapse
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Now I have my GT-I9506 Singapore version with KNOX warranty void 0x0 in this configuration:
System and NON-HLOS from Finladian version: I9506XXUBNE1
The others from original Sigapore version: I9506XXUBND2
towelroot.com installed and working!
Thanks to towelroot
tomogo said:
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Click to expand...
Click to collapse
Yes, but you are talking about flashing this via download/odin mode, right?
My point is that with root, you should be able to modify the flash directly, overwriting the bootloader.
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Probably not
topimax said:
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Click to expand...
Click to collapse
As we have root I would think (so don't quote me on this) that OTA is blocked. But as I see it it does not really matter as the next update for this devise is probably going to be 4.4.2 and flashing that probably also means loosing root.
Now that was a lot of probably but as I see it..
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
mar10o said:
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
Click to expand...
Click to collapse
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond of rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
windstrings said:
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond if rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
Click to expand...
Click to collapse
Was told that xposed could chance the status from custom to official.
Sendt fra min GT-I9506 med Tapatalk
For those who failed check last version !
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
bertrand13 said:
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Click to expand...
Click to collapse
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Don't know why he doesn't label his site or the filename better but it should be the latest version when you download from his site.
When you open the app to install it, it should say the version at the top.
Sent from my GS4 Zombie Communicator
mohammedkhairy said:
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
Click to expand...
Click to collapse
It should work. It does not trip Knox
kerko said:
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Click to expand...
Click to collapse
Well I downloaded it from the towelroot web :laugh::laugh:
I saw on XDA tnat somebody mentionned a new version so I tried
If you need more PM me...
The why
A lot of this has been said in other threads, however I decided to gather all the up-to-date (as of Jun 17, 2014) instructions and info in this thread to alleviate fears of the infamous 'KNOX WARRANTY VOID 0x1' and help people with the process. People with tripped KNOX can of course use this as well, however it won't untrip their devices, duh.
The cheers
First of all big cheers for Pinkie Pie (person who discovered the Linux kernel vulnerability that makes rooting without tripping KNOX possible), geohot (person that used the vulnerability to make a rooting app), chainfire (developer of SuperSU), rovo89 and Tungstwenty (developers of Xposed). Go and donate to these guys if you can!
The what
This post will tell you how to upgrade your P605 to 4.4.2, if you haven't already. And how to install SuperSU and Xposed all the while keeping your KNOX counter at 0x0, CURRENT BINARY: Samsung Official and SYSTEM STATUS: Official!
Note: The versions in this text are just for reference - telling you what versions already worked. New ones will surely also work, so you should usually download the newest available.
The how
Firmware
4.4.2 NEE P605XXUCNE2 (any of the current 4.4.2 firmwares should be fine, although Samsung might use an updated kernel for the future versions, disabling towelroot)
From http://forum.xda-developers.com/showpost.php?p=53092676&postcount=1
Simple instructions available here http://www.sammobile.com/firmwares/3/?download=30325 (you can also download the firmware from here, but download is slow for free accounts)
Root
From http://towelroot.com
No special instructions (it's a 1-click root)
SuperSU
Version 1.99.rc5 from http://download.chainfire.eu/448/SuperSU/
Extract Superuser.apk (in 'common') from the zip, install and run
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
Xposed
From http://repo.xposed.info/module/de.robv.android.xposed.installer (version 2.6.1)
No special instructions
The victory
Congrats! Now you should be on a rooted, SuperSUed, Xposed KitKat with warranty left intact! However before sending it to Samsung, e.g., for repairs, you should flash your original firmware, of course.
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
no.0ne said:
SuperSU
Version 1.94 from Google Play (Jun 17, 2014)
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
At the end it will say it failed, however it will be working!
If you are annoyed by the 'failed' message for some reason, download an updated version from http://download.chainfire.eu/448/SuperSU/ (you'll have to flash it manually though) which supposedly fixes it.
Click to expand...
Click to collapse
Just Download specified zip and extract superuser.apk from common folder and install as normal program, don't download play version
İ am gonna try and write my appreciate ) thanks in advance
It did work . Thanks to you and that steps i have rooted kitkat knox is 0*0 what i was waiting for last 5 months. Thank you so much now i can use my tablet in full capacity
iPhone 'den Tapatalk aracılığı ile gönderildi
Eudeferrer said:
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
Click to expand...
Click to collapse
It seems that so far people have had no success using towelroot on P600. Wait and hope it will change...
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
yararli said:
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
Click to expand...
Click to collapse
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
no.0ne said:
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
Click to expand...
Click to collapse
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
yararli said:
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
Click to expand...
Click to collapse
First you wipe then you flash
You can download the driver from the Samsung website, e.g., http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW (don't worry that it is on the US page, the driver is the same for all Samsung devices)
Glad I can help. I waited for root quite long myself :victory:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Matthias.ja said:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Click to expand...
Click to collapse
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
alright, thanks!
so if i have some warranty issues, wiping everything from recovery or re-flashing the unrooted stock ROM would make everything official again, right? I know I sound like a scared little girl, but I just really don't want to risk my warranty on this rather expensive device
Heyy its wonderful i did it but there is a problem about kitkat rom i saw a little lags and the biggest problem is whatsapp says it is not compatible with this device also twitter in playstore what should i do thnx for your all help
iPhone 'den Tapatalk aracılığı ile gönderildi
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Hello i should restore system defaults how should i do directly by using recovery mode can i clean systam cache and ... Or before it should i unroot from su?
iPhone 'den Tapatalk aracılığı ile gönderildi
To make sure; unroot and then factory reset
Matthias.ja said:
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Click to expand...
Click to collapse
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
dt33 said:
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
Click to expand...
Click to collapse
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
valexi said:
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
Click to expand...
Click to collapse
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
dt33 said:
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
Click to expand...
Click to collapse
I'm not quite sure, but it seems that in some cases the ROM can detect if it's rooted.
For me it changed to "Custom" after rooting with towelroot and SuperSU installation. I changed it back to Official with Wanam xposed.
after I root my S4 during booting the following message appears on the screen:
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
Can anyone explain me if this is normal or it's an error message?
The rooting was not completed?
Thank you.
imishte said:
after I root my S4 during booting the following message appears on the screen:
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT: KERNEL
Can anyone explain me if this is normal or it's an error message?
The rooting was not completed?
Thank you.
Click to expand...
Click to collapse
Mate .
we need more information , what s4 model you have , what rom you had when rooted, what root method you used??
seem like you rooted but you set the warranty bit, knox kicked in
It's normal. That means you are on a custom kernel.
Lennyz1988 said:
It's normal. That means you are on a custom kernel.
Click to expand...
Click to collapse
Ok man, thank you.
But I have one more question?
I saw that with the same rooting procedure (CF-Auto-Root Android 4.4.2 Package) this message was not displayed on the phone from the example. That was the reason that I started this thread, so I have to understand why my phone is displaying this message
Thank you.
imishte said:
Ok man, thank you.
But I have one more question?
I saw that with the same rooting procedure (CF-Auto-Root Android 4.4.2 Package) this message was not displayed on the phone from the example. That was the reason that I started this thread, so I have to understand why my phone is displaying this message
Thank you.
Click to expand...
Click to collapse
Hi , rooting without setting the warranty bit is possible , like with towelroot , but flashing anything else like a Custom recovery , kernel or rom will kick in knox security
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.