C9000 secure folder open error - Samsung C9 Pro Questions & Answers

When i Open Secure Folder Then Show
C9000 Secure Folder Cannot Be Set UP Because Unauthorized Software Was Installed On The Device
Try To Flash With China & Hk Rom But Same Problem
Whats Wrong With This Phone

I have same problem both on secure folder and a health app. Any solution?
Sent from my SM-C9000 using Tapatalk

Because your knox status is 0x1 , your warranty is void from the moment you root or install twrp if i remember right.

i have same problem, any one tell me how to solve this issue

1) Root your device
2) Edit build.prop and change ro.config.tima to 0

Related

Questions about knox 0x1 and how to improve it

Hey guys, sorry my bad english end lets go to the problem.
I FLASHED the 4.4.2 by odim and in the sequence I rooted my phone. In the time what I use the root privileges, show on screen a message by supersu tell me about knox and ask me to click in "yes" to desactivate the knox. I CLICKED. Now my knox is in 0x1. And I cant get install apps of playstore or apks by third parties. The only way is to install by aptoid because it installs with root privileges. NO ROOT, NO INSTALLATION NOW :/
So my questions is:
Can I reflash the same rom by odim for fix this problems whit apps?
my phone doesnt is with CWM I dont no why, because the file what I used to get root, install cwm together. But I tryed put in cwm and it go into the recovery stock.
Can i try install a custom recovery to after get some custom rom ?
Heeeeeeelp ME
Sent from my GT-I9505 using xda premium
1. Dont mix things. Knox app isnt the same of KNOX in Download Mode.
2. SuperSU didnt ask for KNOX. Knox noticed SUPERSU telling u: KNOX app blocked SUPERSU.
3. Knox 0x1 appeared when u rooted ur phone. Nothing new.
4. I dont think ROOT and CWM comes together. But anyway you can flash the custom recovery u wish apart.
*SOLUTIONS:
- Use THIS for root ur i9505.
- Delete or freeze KNOX app in ur phone:
KNOX in System/App folder:
ContainerAgent.apk
KNOXAgent.apk
ContainerEventsRelayManager.apk
KLMSAgent.apk
KnoxAttestationAgent.apk
KNOXStore.apk
KNOXStub.apk
SPDClient.apk
KNOX in DATA/DATA folder:
com.sec.knox.containeragent
com.sec.knox.eventsmanager
com.sec.enterprise.knox.attestation
com.sec.knox.app.container
com.sec.knox.seandroid
com.sec.knox.store
com.samsung.klmsagent
More KNOX remains:
Folder = Data/clipboard/knox
Folder = system/containers
Folder = system/etc/secure_storage/com.sec.knox.store
Lib = libknoxdrawglfunction.so
File = system/tima_measurement_info ---- TIMA is a Trust-Zone of KNOX
Ooooh, thanks very much.
But you think that is better than flash again the rom with odim ?
Because if I fix the issue about the installation of apps, I can return my phone to original and after I can use one normally whithout root.
Can I do this ? Have problem ?
Sent from my GT-I9505 using xda premium
Sent from my GT-I9505 using xda premium
Curiousrge said:
Ooooh, thanks very much.
But you think that is better than flash again the rom with odim ?
Because if I fix the issue about the installation of apps, I can return my phone to original and after I can use one normally whithout root.
Can I do this ? Have problem ?
Sent from my GT-I9505 using xda premium
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
You dont need flash again any rom.
So if follow this steps that you suggest, will I can back to install apps normally ?
Sent from my GT-I9505 using xda premium

Titanium Backup Help I9505

thanks to the brilliant efforts of all the members here at xda forums I was able to root my Samsung galaxy s4 i9505 bought may 2014 out of warranty (didn't need even though had no root) bought may 2014 successfully all things work fine my question is that:
titanium backup detects both backup directories as valid shows all the files but says with extSdCard shows a red folder saying "This folder is not writeable" what's the deal here and how to fix it
additional question not related to this topic exactly but better than starting another thread
I didn't use triangle away and don't give a fudge about knox counter but would really like to remove knox and all its components from phone
the stuff that's on the phone is taking a lot of space and I want some of it back
any help would be appreciated
Samsung Galaxy S4 GT-I9505 Qualcomm Snapdragon 600
Lollipop 5.0.1 Official Rom
Kernel Version: 3.4.0-5978264 [email protected] # ! (CF Auto Root)
Running Latest CWM for I9505
Angel-King said:
thanks to the brilliant efforts of all the members here at xda forums I was able to root my Samsung galaxy s4 i9505 bought may 2014 out of warranty (didn't need even though had no root) bought may 2014 successfully all things work fine my question is that:
titanium backup detects both backup directories as valid shows all the files but says with extSdCard shows a red folder saying "This folder is not writeable" what's the deal here and how to fix it
additional question not related to this topic exactly but better than starting another thread
I didn't use triangle away and don't give a fudge about knox counter but would really like to remove knox and all its components from phone
the stuff that's on the phone is taking a lot of space and I want some of it back
any help would be appreciated
Samsung Galaxy S4 GT-I9505 Qualcomm Snapdragon 600
Lollipop 5.0.1 Official Rom
Kernel Version: 3.4.0-5978264 [email protected] # ! (CF Auto Root)
Running Latest CWM for I9505
Click to expand...
Click to collapse
Enter titanium backup preferences and go to the "backup folder location" setting. Next, touch the "storage provider" and select something else, like documents provider if available.
This may fix that problem.
As for knox, just do a Google search on what apps belong to knox and delete them with titanium backup.
GDReaper said:
Enter titanium backup preferences and go to the "backup folder location" setting. Next, touch the "storage provider" and select something else, like documents provider if available.
This may fix that problem.
As for knox, just do a Google search on what apps belong to knox and delete them with titanium backup.
Click to expand...
Click to collapse
as I understand using your method does show the backup location in extSdCard
but the entire root directory containing system file i.e.
/storage says not writeable
/storage/extSdCard not writeable
/storage/emulated/ not writeable
but
/storage/emulated/0
/storage/emulated/legacy
are accessible by TB here it says <<Create New Folder>>
I'm going like this {} trying to solve this over and over navigating file path changing locations
also does freezing BusyBox would effect this
or is it affected by SuperSU's Mount namespace separation
I'm very confused and frustrated because finding an alternative to TB would be a miracle
Angel-King said:
as I understand using your method does show the backup location in extSdCard
but the entire root directory containing system file i.e.
/storage says not writeable
/storage/extSdCard not writeable
/storage/emulated/ not writeable
but
/storage/emulated/0
/storage/emulated/legacy
are accessible by TB here it says <<Create New Folder>>
I'm going like this {} trying to solve this over and over navigating file path changing locations
also does freezing BusyBox would effect this
or is it affected by SuperSU's Mount namespace separation
I'm very confused and frustrated because finding an alternative to TB would be a miracle
Click to expand...
Click to collapse
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.
GDReaper said:
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.
Click to expand...
Click to collapse
wil try it tomorrow
GDReaper said:
My method was a temporary fix for when marshmallow first released and app permissions were f'd up. It had the same problem. Thought it might help you too.
You can restore apps from the sdcard, but you can't backup to it.
Busybox is required for pretty much any rooted app. It also doesn't show up in Titanium Backup normally.
Maybe you should update it or install another version.
Or try the sd fix app by nextapp inc.
Click to expand...
Click to collapse
sdfix worked I OTA updated to lollipop so all is good user apps are able to write on extSdCard

NTCODE Error Solution

1. Go to secret menu of your phone (*#546368#*850#)
2. Tap SVC menu, then Version Info.
3. In Version info find NT Code.
4. Change wbatever code you have there to "1","FFF,FFF,FFFFFFFF,FFFFFFFF,11" - that is open europe.
After pasting the above code, the NT Code should display something like code write done, or similar, instead of your old NT Code.
This info is from MrBeem, he sent to me. I have this error but it did not work for me, i get Write Error maybe because i I dont have root. If you are rooted can work for you.
I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?
stuclark said:
I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?
Click to expand...
Click to collapse
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).
Error
yken said:
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).
Click to expand...
Click to collapse
Can't pass the step 2, it gives an error.
fmartins29 said:
Can't pass the step 2, it gives an error.
Click to expand...
Click to collapse
You can flash your countries Rom, not EU
I've installed TWRP ans SuperSU as shown above, but I still get Write Error.
Looking in the SuperSU app, it says under "Install SuperSU into /system" - "Not (currently) available in system-less mode".
How can I fix the SuperSU issue, as I'm guessing that's why I haven't got write access to the NTT code?
Hi. What exactly do you get in your ntcode error? Mine was FFFFFF,FF is not a proper code or something like that. Now, if your error is something else but not '0', you can just do the following:
1. Memorize or write down your error code ( in my case it was FFFFFF,FF)
2. go to /cust folder, mount it as R/W
3. Check what carrier subfolders folders you have in your cust solder (i had OPEN_EU, P4P_PL and a couple more)
4. Open file cust_path_mapping.cfg with TEXT EDITOR
5. Change the number/letter string before = of your desired carrier in the above mentioned cfg file to whatever it says in your ntcode error (my error message said FFFFFF,FF, i wanted the P4P_PL to be my carrier so i changed 26006,06=/cust/P4P_PL to FFFFFF,FF=/cust/P4P_PL).
6. Save changes, close, reopen the cfg file to check if your changes stick (if not, make sure you've enabled the R/W option in your cust folder).
7. Reboot
This should fix your problem. I tried this on 5 different devices and always worked.
Help changing NT using SVC menu
yken said:
You can flash your countries Rom, not EU
Click to expand...
Click to collapse
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.
wimmerfield said:
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.
Click to expand...
Click to collapse
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.
No progress with changing NT code
cancunia said:
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.
Click to expand...
Click to collapse
Sorry - I wasn't able to resolve that issue but as you say the G5 has now received its Oreo upgrade which is really all I wanted. Good luck anyway
Thank you! It worked for me. I have an h850ar running Android 8.0 without root. Finally the damn sign went away every time I started my phone ...
my device 860 h GCC middle East
I FLASH OREO VERSION sg (Singapore)
everything is work but ( NTCODE) PROBLEM ? ANY solution ? your discussion work for my device?
thank you
sorry bad English ?
WARNİNG
1 - WARNİNG - Current version is not available for user. Can't find matched cust for NTCODE = (23430,02)
2- WARNİNG _ Current OP name by Buyer-code is (EEO_GB). But cannot find matched NT-code mcc/mnc (23430), subset (02)
Telefon yeniden başlatıldığında bu hatalar çıkıyor bir çözüm var mı acaba LG G5 H850 model cihaz
Did anyone work out how to change the NT Code via the hidden menu? I tried downgrading to Marshmallow but still get a write error.
Thanks
This is a solution that worked for me, on a Wind branded phone with an OPEN_EU rom (root required):
go to /cust/ folder and edit cust_path_mapping.cfg, adding a new line with the code you see in the NTCODE error (22288,FF in my case), pointing it to the OPEN_COM folder:
22288,FF=/cust/OPEN_COM
Then do the same with open_path_mapping.cfg, but here you should put OPEN_EU instead of OPEN_COM:
22288,FF=OPEN_EU
Then, after saving both files, reboot the phone, and the NTCODE error will be gone.

No root - Knox S-Health Not working

Hi !
My phone was rooted once, I flashed new system via Odin to uproot my phone but knox is not working nor S-Health.
S7Edge SM-G935F 7.0 Enyxos
Thanks for your replies.
Howzer95 said:
Hi !
My phone was rooted once, I flashed new system via Odin to uproot my phone but knox is not working nor S-Health.
S7Edge SM-G935F 7.0 Enyxos
Thanks for your replies.
Click to expand...
Click to collapse
If you ever rooted your phone, the knox e-fuse is blown permanently.
You can check this by going into download mode and you'll see knox status as 0x1 (tripped) instead of 0x0.
There is no way to reset this, you will have to go back to a rooted/custom rom with Masgisk and use Magisk Hide to simulate a knox 0x0 for apps. This may not work forever.
S-Health
You can still use s-health by doing the following which i have done and it works..
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
Error
chainsuk said:
You can still use s-health by doing the following which i have done and it works..
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
Click to expand...
Click to collapse
Is not working on my S7 G930. It os pop up one error: Root access is required to edit system properties. Is not let me to do any changes, from 1 to 0, what should I do? Thx in advance for help.
Try adb
Andromega, can you share how to fix this using adb?

Does change /system change KNOX ?

Hi,
I have succesfully finished to root my Note 3 and keep KNOX 0x0.
I need to change now some files in /system
Is this modification remove 0x0 ?
Is it possible olso to change boot.img and keep 0x0 ?
Thanks.

Categories

Resources