After rooting my phone, private mode won't work, any ideas or fix
Fix: Just install xposed then download xtouchwiz module and enable it.
I'm about 60% sure that rooting trips KNOX and renders private mode unusable, but no guarantees, though.
iSaitama said:
I'm about 60% sure that rooting trips KNOX and renders private mode unusable, but no guarantees, though.
Click to expand...
Click to collapse
Other users can use private mode after root, so maybe i think their is a flashable zip to fix it.
I'm using a stock rooted rom, other solution I think is to flash a custom rom that has private mode working fix but I want to stay at stock as possible because it's stable and fast
iSaitama said:
I'm about 60% sure that rooting trips KNOX and renders private mode unusable, but no guarantees, though.
Click to expand...
Click to collapse
Other users can use private mode after root, so maybe i think their is a flashable zip to fix it.
I'm using a stock rooted rom, other solution I think is to flash a custom rom that has a private mode working fix but I want to stay at stock as possible because it's stable and fast
S, same issue for me too.
I suggest you review this thread. It may help.
https://forum.xda-developers.com/s7...e-folder-samsung-knox-s-t3560079?goto=newpost
[GUIDE] Use Secure Folder, Samsung Knox and S-Health on a Rooted S7E
Related
I updated my phone today and I was able to root it an disable KNOX.
I used CF-Autoroot http://autoroot.chainfire.eu/ and it worked flawlessly and when I was updating the binary I got the option to disable KNOX.
Root Instruction:
1. Flash with Odin
2. Add a google account incase it has not been setup yet.
3. Install SuperSU from Market.
4. Open it and it wil ask you to update binary.
Respect to the developer.
Futhermore, I got CWM with one of the methods I was using when on JB 4.1.2
PLS NOTE: You will lose warranty if phone is rooted at this time. If you will like to keep your warranty with no possibility to go back to an older android version, please AVOID rooting your ROM and wait for custom ROM with KNOX disabled
Cheers,
But.. I don't know whether to use the i9305 or I9305T files :/
My device is I9305T but has been running I9305 FW (and probably bootloaders) for a while...
For those who need some more links/instructions:
Backup your data, SMS, settings - and make sure you got an IMEI backup
http://forum.xda-developers.com/showthread.php?t=1946915
If you use Google's 2-Step Verification, make sure you can receive the SMS via a 2nd phone or have a backup option like landline or authenticator app.
I removed my SD card (just in case) and did a full system wipe just to get rid of everything I did to my system over the last year:
Hold down volume up, home and power buttons, when screen turns on, leave these buttons, do the full system wipe. (Don't think this is really necessary though.)
Install 4.3 on your i9305
http://www.androidegis.com/how-to/install-android-4-3-update-galaxy-s3-lte-i9305/
Switch the phone off after first book (at SIM PIN prompt).
Get CF-Auto-Root and install it
EDIT: http://forum.xda-developers.com/showthread.php?t=1957273
Now after your phone booted you can run the Samsung setup. Add your Google account.
Install SuperSU from the Play Store - not SuperUser
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Update the binary and disable KNOX
Enjoy
For me what worked, was installing PhilZ Touch (latest version), and using the built-in rooting function of the recovery. Then, installing SuperSU gave me perfect root.
Does anyone know if Koush's superuser app works in any way in this release? I would prefer to use an open-source superuser app.
gulbrillo said:
For those who need some more links/instructions:
Backup your data, SMS, settings - and make sure you got an IMEI backup
http://forum.xda-developers.com/showthread.php?t=1946915
If you use Google's 2-Step Verification, make sure you can receive the SMS via a 2nd phone or have a backup option like landline or authenticator app.
I removed my SD card (just in case) and did a full system wipe just to get rid of everything I did to my system over the last year:
Hold down volume up, home and power buttons, when screen turns on, leave these buttons, do the full system wipe. (Don't think this is really necessary though.)
Install 4.3 on your i9305
http://www.androidegis.com/how-to/install-android-4-3-update-galaxy-s3-lte-i9305/
Switch the phone off after first book (at SIM PIN prompt).
Get CF-Auto-Root and install it
http://forum.xda-developers.com/showthread.php?t=2219803
Now after your phone booted you can run the Samsung setup. Add your Google account.
Install SuperSU from the Play Store - not SuperUser
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Update the binary and disable KNOX
Enjoy
Click to expand...
Click to collapse
Did you mean to link the [GT-I9505 + GT-I9505G] CF-Auto-Root page, or should we get the file from [GT-I930x/T/N][SHV-E210*][SHW-M440S] CF-Auto-Root?
Damn, sorry - that was my mistake. I just changed the link above - it should have been http://forum.xda-developers.com/showthread.php?t=1957273 of cause. Thanks!
aaronsclee said:
Did you mean to link the [GT-I9505 + GT-I9505G] CF-Auto-Root page, or should we get the file from [GT-I930x/T/N][SHV-E210*][SHW-M440S] CF-Auto-Root?
Click to expand...
Click to collapse
I don't understand if this method preserves the warranty.
No , it doesn't . By flashing CF-Root you will get Knox count 1 .
seaman5705 said:
No , it doesn't . By flashing CF-Root you will get Knox count 1 .
Click to expand...
Click to collapse
Uh. I think, at this point, that the best thing (for me) is to not update.
Update using Heimdall, and skip flashing tz.img and sboot.bin. Be aware that this will break WiFi until a custom kernel is released
Sent from my GT-I9305 using xda app-developers app
I prefer to wait until a solution will be find.
lallolu said:
I updated my phone today and I was able to root it an disable KNOX.
Click to expand...
Click to collapse
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Ed Roid said:
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
Thanks mate for clarifying the issue of Knox flag and warranty. I will wait for a dev to make Knox-free rom.
if you'd like to have 4.3 stock rom with root and warranty, you can update your phone to 4.3 using Mobile Odin PRO latest version (3.85). Let's say you're on 4.1.2, just download 4.3 for your phone, move it to phone storage, flash it using Mobile Odin PRO with EverRoot and Inject Mobile Odin features. This way you'll have a 4.3 rooted in warranty.
steebro said:
This way you'll have a 4.3 rooted in warranty.
Click to expand...
Click to collapse
4.3 stock + root + warranty ok but no wifi, am i right ?
Ed Roid said:
Thanks for sharing this interesting experience.
But I think it would be kind of you to edit the OP to say in a very visible way that someone doing that looses his warranty with no possibility to go back at this time (until a solution is found, but no one knows if this will ever be the case ...) because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
Thanks for pointing that out. I have updated the OP.
steebro said:
if you'd like to have 4.3 stock rom with root and warranty, you can update your phone to 4.3 using Mobile Odin PRO latest version (3.85). Let's say you're on 4.1.2, just download 4.3 for your phone, move it to phone storage, flash it using Mobile Odin PRO with EverRoot and Inject Mobile Odin features. This way you'll have a 4.3 rooted in warranty.
Click to expand...
Click to collapse
For sure?
I've buy the Pro Version ( in this moment the version is only working with this Mobile ( nobody knows, at which time the support will be stopped ) ).
I don't want see, that Knox is incr. from 0x0 to 0x1 with this procedure ....
THX
Wesie said:
For sure?
Click to expand...
Click to collapse
I think I've read that Mobile Odin isn't able to flash the bootloader. If this is really the case then it is true (old bootloader = no Knox flag). Note that you will also need to flash a custom kernel cause stock 4.3 kernel without Knox bootloader breaks wifi.
SHV-E210K
how can you root SHV-E210K with official 4.3 firmware?
Ed Roid said:
that someone doing that looses his warranty with no possibility to go back at this time because of the new Knox bootloader and the new Knox warranty void flag.
Click to expand...
Click to collapse
What about triangle away? (Or downgrading to a earlier stock Knox free ROM and than triangleing away?)
Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.
Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms
Hi Guys,
I'm basically knox free im on 4.2.2, can anyone give me
a: a brief guide to easiest way of rooting and installing a recovery i.e TW or CWM, hopefully one click solution?
b: If I go onto 4.4 kitkat will I have to have a knox bootloader even with a custom rom?, if so is 4.4 worth it?.
c: &
d:Mod Edit removed due to asking for best ROM ( not allowed on xda)
At the moment main thing I want to do is safely root and install recovery without triggering knox as I want the chance to install custom roms and not void my warranty as I can always use triangle away at a later date.
BTW have done a lot of reading but want to be 100% sure and would really like some experienced advice.
Many thanks
Mav
a) Use Saferoot -> HERE
b) TWRP -> All info HERE
c) and d) Try it by yourself. Read the rules of XDA too :highfive:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Mod Edit
You may continue with this thread , but please do not ask for best ROMS.
Saferoot , AFAIK , does not trip knox flag
malybru
Forum Moderator
maverick7777 said:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Click to expand...
Click to collapse
If you have an old bootloader you won't even have KNOX on it, lucky you.
If you have the new bootloader, it comes with KNOX.
You can check if you have a new or old bootloader by putting your phone in Download mode (Volume down + Home + Power buttons).
If the the top left corner is syas stuff like "KNOX warenty" etc. you have the new one.
Rooting using saferoot as mentioned earlier will not trigger KNOX anyways.
Installing a custom Recovery as well as installing a custom ROM will trigger KNOX (if you indeed have the new bootloader with KNOX offcourse).
Hello,
I've was forced to create a post about that because there is almost nothing of use that can be found about that phone in the internet.
I need to know how to check the bootloader status on this device so i can safely root it, and if there are any working ROMs. I've found out that it is possible to install 9505 roms on that phone, however the touch and other crucial features do not work while using them.
Cheers, Paweł.
Thanks in advance, i appreciate Your help!
Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.
LastStandingDroid said:
Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.
Click to expand...
Click to collapse
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
All the info, rooting recoveries, roms available so far for i9515
http://forum.xda-developers.com/galaxy-s4/general/i9515-value-edition-roms-development-t3002535
Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
I think you have misunderstood or misread.or users haven't understand that root is still possible. It isn't locked in any way. The bootloader still let's you flash custom kernels etc.
Rooting with cf root shouldn't and has never bricked your phone on newer recoveries. The bootloader isn't locked in the way of flashing in Odin you can still flash custom kernels and recoveries but it will trip the Knox counter.
However: tripping Knox will cause you being unable to use Knox apps from Samsung and might void your warranty.
Users have told different reports about them being tripped and got warranty and some haven't. I'm not sure if this lies in 3rd party repair centers repairing the phone even if it's tripped. I'm sure Samsung service center is against it.
I'd be 100% sure that my phone carrier would repair it no matter the status since it doesn't go trough Samsung service at first.
However to gain root you should try towelroot it's a one click apk and it won't trip Knox unless you flash a custom kernel or recovery.
Is there any way to make this work?
Since CF-autoroot doesn't work in nougat, I dunno how to make this work..
I don't know if is even possible, because as soon as i flash TWRP I cannot encrypt it again..
anyone?
For now only way is to install TWRP + SuperSU then flash old recovery
Im not sure but for this process you dont need no-verity-opt-encrypt..
Im on 7.0 Nougat and waiting better way to root it, i dont want custom recovery and i hear when you install TWRP bootloop is granted in 50/50 attempts
Talentooman said:
For now only way is to install TWRP + SuperSU then flash old recovery
Im not sure but for this process you dont need no-verity-opt-encrypt..
Im on 7.0 Nougat and waiting better way to root it, i dont want custom recovery and i hear when you install TWRP bootloop is granted in 50/50 attempts
Click to expand...
Click to collapse
But you tried that method? (Flashing TWRP + SuperSU and then back stock recovery)
Crap... Nougat is really nice, but some basic stuff is missing for me... encryption and Xposed
insaned said:
But you tried that method? (Flashing TWRP + SuperSU and then back stock recovery)
Crap... Nougat is really nice, but some basic stuff is missing for me... encryption and Xposed
Click to expand...
Click to collapse
im really sad, so i install custom recovery, flash Nougat debloated rom with root preinstalled and now i lose my CSC, *#060# or any other code not working.. im now on 7.0 UK version stock firmware and UUID codes not working ..
Root and encryption aren't working right now. Chainfire (SuperSU Dev) and a few other users are trying to get it to work.
For the time being, the most you can do is use a ROM like Helios and pick the encryption option. You won't have root but you can flash mods to /system in TWRP
My current setup is
Helios
Stock Kernel
Encrypted
Dual Speaker Mod
Private Mode Works
S Health Works
AppLock Works
Android Pay Works
Banking Apps Work
Galactus said:
Root and encryption aren't working right now. Chainfire (SuperSU Dev) and a few other users are trying to get it to work.
For the time being, the most you can do is use a ROM like Helios and pick the encryption option. You won't have root but you can flash mods to /system in TWRP
My current setup is
Helios
Stock Kernel
Encrypted
Dual Speaker Mod
Private Mode Works
S Health Works
AppLock Works
Android Pay Works
Banking Apps Work
Click to expand...
Click to collapse
Well, It's an option... the most interesting mods that I used were with Xposed anyway, and for that the wait is going to be longer.
The device not encrypted is not very nice though... I guess eventually I just try it out meanwhile.
Thanks for the heads up @Galactus
Just out of curiosity, why do you guys "insist" on encryption? I still don't understand the repercussions of a decrypted device, let alone those of an encrypted device. I genuinely don't know. This is not a sarcastic or passive aggressive question!
nitrous² said:
Just out of curiosity, why do you guys "insist" on encryption? I still don't understand the repercussions of a decrypted device, let alone those of an encrypted device. I genuinely don't know. This is not a sarcastic or passive aggressive question!
Click to expand...
Click to collapse
Mainly data protection.
If my phone is stolen with encryption, once the thief turns the phone off that is it. The phone won't even fully load without my password. Sure, he can fully wipe the phone but this will also delete all of my data. Once reported stolen, it will simply be an expensive media player. Nougat also doesn't let you turn the phone off by using the power button unless you enter the phones password, so that helps using Android device manager or say Cerberus to locate the phone or enable it to play a loud alert
Without encryption. The thief can simply go into TWRP and take all the data
How about sd card encryption? Is this also not possible with rooted nougat? I just tried it and am stuck at the "checking sd card" message since hours. However the device is still working.