yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] Vessina:
Last day i went back to carrier firmware mk9, all is ok, wifi is ok, updates via phone are ok and no problem with anything.. No problem with kernel and bootloader said to me all is official except warranty void..

The only one thing that surprise me is knox security.. Was off by samsung kernel, doing a virtual process that dont have knox and their stupid messages spaming on my phone.. ???????

Eachtime i reinstall this phone i understand nothing..
[Galaxy S 4 General] marcash:
hello i have the i9505

i flashed cm11 and ML1 modem

now i have the no sound ishue. Knox is x01

is it possible to flash back to stock to get sound back?

thanks
[Galaxy S 4 General] Repulsa:
You need to flash the newest 4.3 modem + Non-Hlost in order to get your sound back :) , Please use the search button , have a nice day.
[Galaxy S 4 General] mahmoud007:
knox

this is logo of Knox warranty void after check everything is not ok ??

SEAndroid = SELinux if I'm not mistaken !!

where did you get this from and how !!!

i tried everything to get root access on my S4 to explore system files for this exact logo ! but it didn't let me -_-

and if that SEAndroid = SELinux then we should find a solution for breaking SELinux before removing Knox ... otherwise we will be moving in an empty circuit .

---------- Post added at 11:48 AM ---------- Previous post was at 11:38 AM ----------

if you have root access to your android

download busybox and terminal emulator

and write this if its ok with you of course :)

-sudo su

-SEAndroid=disabled

or

-SELinux=disabled

might work
[Galaxy S 4 General] Surge1223:
You can only turn SELinux off temporarily, or until the next reboot. But another solution exists, if you can figure out what causes the bolded text below to be called
[Galaxy S 4 General] mahmoud007:
knox

tima is knox working

its like one protecting another

knox protect SELinux from disabling

and SELinux protect knox from removing

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

did you tried to remove knox after disabling SELinux while device is on ??

---------- Post added at 01:07 PM ---------- Previous post was at 01:01 PM ----------

or try to install old bootloader in download mod after switching the device off

---------- Post added at 01:19 PM ---------- Previous post was at 01:07 PM ----------

there is a file called keystore im not sure what is it ... but try to edit it or remove it ... i dont know what to do because my device is with the warranty
[Galaxy S 4 General] marcash:
hello i have the i9505

i flashed cm11 and ML1 modem

now i have the no sound ishue. Knox is x01

thanks

-----------------

You need to flash the newest 4.3 modem + Non-Hlost in order to get your sound back

-------------------

i have flashed

GSM_Modem_XXUEML_and_LTE_Modem_XXUBMH1.tar

is modem.bin and NONHLOS.bin

but not working
[Galaxy S 4 General] Repulsa:
Bro i already sent you a Pm to solve your problem if the problem still persist make a thread here http://xdaforums.com/galaxy-s4/help this thread is regarding only for Knox void warranty. Have a nice day.
[Galaxy S 4 General] Surge1223:
removing the Knox flag is not going to be as easy as disabling or deleting a file. Just saying
[Galaxy S 4 General] bogdan1980:
The master for Acer and not only that came to mobiles. Greetings Master!
[Galaxy S 4 General] robolo:
Why are people complaining about not being able to use the warranty after root? Obviously after all the warnings from Samsung and even HTC (No idea why you guys are considering the One) your warranty is void if you root/modify your device. Samsung are only doing to make sure that they only repair and replace devices that are actually under warranty. Having a warranty is a price to pay to get your device rooted. Deal with it.
[Galaxy S 4 General] bungadudu:
What's the difference between a stock, never rooted phone and a stock, previously rooted phone, hardware wise?

And why if there's no difference (yea, the blown e-fuse) they void the hardware warranty for the latter?

Let's say you've got your oem pc/laptop with Windows 8 pre-installed.

You don't like it, you buy and install windows 7 or better yet you install Linux and enable superuser. :rolleyes:

After a month a HDD fails.

Do you think dell/etc will say "no, you've installed another version of Windows, your warranty is void!"

Does it sound fair or normal for you?

We now live in a world where hardware warranty normally reside all but when they can prove you directly caused the hardware problem (eg you smashed your hdd with a hammer).

Samsung and pretty much all other mobile phones OEMs say they won't honor hardware warranties if you've rooted. Even though the hardware problem isn't in any way related to rooting.

Imagine if you are rooted and the battery gets swollen, your LCD get 5 dead pixels etc. They void your warranty and refuse the repair even though there's no direct connection between rooting and the hardware problem.

Does it sound OK to you?

Samsung is a bully, the biggest now in the courtyard, but we should unite and stand up for our common sense rights!
[Galaxy S 4 General] robolo:
Samsung isn't the only one, nearly every major phone manufacturer like HTC void your warranty when you root your device. It's because sometimes the issue is caused by rooting the device. The only change with Samsung is that they're trying to make sure that the device isn't tampered with, you can't blame them for enforcing their written statements.

Off-Topic: Your warranty is usually voided when you install a different version of Windows. :P
[Galaxy S 4 General] Michal Z.:
The thing is that tripping knox is not about only voiding warranty. It messes with your phone (as many people mentioned about it before), wifi problems, dissappearing apps etc. And it's not ok to force users to install such thing without informing them.
[Galaxy S 4 General] robolo:
Knox wasn't forced onto us, it was already a phone feature, the recent update just got it working, that's the issue. How can you force someone to install something it came with?
[Galaxy S 4 General] zzz2002:
What is more important to Samsung/Google the 1% or the corporate market.

My guess is that in the fairly near future Samsung will start to distance itself from the XDA community. Particularly if they can persuade the corporate world to do the testing for them.

My second guess is that Google will start to distance itself from the 1% as well. We tend to be the people that remove things from our devices that they want us to keep and add things that they would prefer us not to have. They want everybody's data on their cloud and they want to see everything that everybody does. We provide a model of what can be done, that the corporate world would prefer to have suppressed.

On top of these pressures, are those from the phone companies to make the devices absolutely tied to them so as to push their profits.

---------- Post added at 08:49 AM ---------- Previous post was at 08:07 AM ----------

Samsung cares greatly about its customers. But remember we (the public etc) are not Samsung's customers. Their customers, for these devices, are the cell phone companies.

As for KNOX, it may get them the same sort of corporate endorsement the Blackberry used to get, and which made BB the darling of the corporate world. Until BB's got complacency lost them the market, they were the device to have.

If Samsung gets it right you might see a President using one, and that sort of endorsement is worth a lot of money.
[Galaxy S 4 General] bogdan1980:
When that time will came i will buy am normal phone and that's it. No more bull**** for me.

And my next phone will be nexus, then any other mobile name that does not add these stupid protections. Samsung is starting to go down. Samsung is the New Nokia. Remember Nokia? Samsung, you're gone.
[Galaxy S 4 General] testadeferro:
After this knox Bs Samsung lost 3 devices from me. Bought new LG pad 8.3 instead note 8. Bought Asus memo pad for my kid instead galaxy tab 3 and LG optimus 4x hd instead of any Samsung midrange device for my wife. For me they're done. And close friends will also happen.
[Galaxy S 4 General] Michal Z.:
Yes it was. I had no idea about it when I was buying my device. There was no info anywhere, then I got 4.3 update also no info about knox, I downloaded it and guess what? Some hidden crap is turned on. What's worse - I have no idea what it's doing, I can't remove it and I DON'T NEED IT. It's not only another bloatware :/

Say what you want, I feel cheated and as many others - my next device will be probably nexus. But for now I want to help solve this knox thing. So if someone needs any images or whatever, pm me.
[Galaxy S 4 General] Damir78:
Knox probably is in bootloader - today my friend went to repair shop and they returned him the device in just 10-15 mins and KNOX NOW IS ZERO.
[Galaxy S 4 General] gazdajezda:
Same here. I lost passion to S4 completely after reading about it...
[Galaxy S 4 General] rodrigoyasuda:
Galaxy note 2 didn't have anything related to knox on 4.1.2, so it was forced.
[Galaxy S 4 General] bogdan1980:
We're not sheep's, we don't care about Samsung, we bought Samsung phones because they were faster then competition and rooting easy, no lock bootloader. But now all phones are identically fast, rooting easy, etc. Now we have options.

Look at Lg, super cheap, Optimus G, G Pro, G2,etc. they have super apps.
[Galaxy S 4 General] testadeferro:
Agree. The only great issue from LG are updates and some fuses like Samsung. And a thing called MLT a issue that drains your battery completely because they uses this to track you everywhere. A bit Samsung alike. I think south Koreans are people that need to be well informed about what you do with your goods that you buy from them and belongs to you. I think it's time to act legally. That's privacy violation and spying of companies.
[Galaxy S 4 General] !crazy:
Do then mentioned issues persist also on rooted phones with AOSP ROMs? How is the scene of custom AOSP ROMs with LG?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] Absolon:
This is something we heard before. From time to time.

Let us bring some real clarity in this!

What repair shop? In which country? Can you provide me a phone number to them?

Your friend must have all those details. Please ask him and report back here.

That would help a lot of your fellow friend here.

Samsung say it's an e-fuse (that short circuit something) and can't be removed.

There are many that experienced problems with their WiFi (that is of course something you notice at once).

Even a JTAG seem unable to fix that.

And it would bring us clarity. Something we lack since "Steve" doesn't want to give us that. He sits and writes the same letter over and over.

Poor "Steve". His fingers must be tired. But it's good that he is consistent since when we compare the letters they seems to be the same, 100%.

Really hellish job to sit and write that, don't you think? ;)

Happy new year, fellow S4'eres :)

/Abs
[Galaxy S 4 General] Damir78:
NO; IT IS NOT E-FUSE! Samsung's workers confirmed that. Maybe it is in Note3 but in S4 and S3 it isn't.

And EVERY repair service can reset Knox back to 0 in just a few minutes, if they want. In Italy there are already shops which offer knox back for 15 euros, in Portugal, Greece and in my country official services are rolling back Knox in cases when your phone isn't rooted.
[Galaxy S 4 General] Michal Z.:
It's good if it's not an efuse, but still... I would like to remove it completely from my device rather than resetting it to 0x0.
[Galaxy S 4 General] _alex74_:
C'mon.... we are not so stupid.... these info will be shared privately.... you sai Sammy is watching right?

of course sammy will say that .... who are you? Sammy employee? there are already guys proved it is only software related(flashing aboot.mbn gives a third value on knox void warranty)

Please...

wifi problems are related only to wrong kernel/modem for rom version

I've knox 0x1 everything working as a charm...all even allshare on Sammy TV(custom ROM)

Had issues with wifi only when flashing wrong/incomptible kernel or modem, proved and solved. 4.3 is a little more harder to flash... you have to find right kernel/recovery/modems/Rom to have all working

Knox do not involve efuse neither will break our phone(read well about efuse... you will understand that in electronical point of view cannot damage phone functionality....or better can but will be the same for everyone Knox voided)

you're good man..... so

happy and prosperous year to you and all XDA staff, members, thanks again to giving this we enjoy now

:good::good:
[Galaxy S 4 General] hepterci:
Why do we reset knox counter 0×1 to 0x0 . How are they doing. if necessary, let's sneak programs :D ?

GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S 4 General] Absolon:
In that case PM me the details.

And I think that my signature hints that I'm NOT and employee, or? ;)

I just think it's fishy that fishy (and are not alone) that someone, sometimes, say this.

And in the case of missmatch, why does not an Odin bring back the stability? I mean. It should, not?

And please, how do you know it's a mismatch? Can you give a good "match", because I know a user with a Wifi DEAD.

It would be helpful to fix his phone :)

But still there are many questions that are strange is this matter. Samsung could be transparent if they wanted. This is and will hurt

their sales.

One thing that they should give a rationale for is for instance why are they hiding processes from users?

During my 20+ years of experience I have never seen that you don't see the whole process list as a user...

I mean if an user knows the ps command, but still can't do anything because he is not root, what is the point?

Why are there so many kcryptd instances? Is all fs crypted nowdays? I don't get that. And I'm not sure you see it as an "user" either.

So transparency from Samsung's side could and would calm people down. All are already oversensitive with all this NSA-tish. Why add more?

Why is that "case to case" root access something you can't get ANY info about how that works, How to apply for that. Believe be, I asked.

So no, sorry, until Samsung doesn't come clean I rather go for the safe alternative. And so does many others.

Can you give a reference? Or well, I ask you in a PM since SS reads this.

And thank you. I try to be. And I always get in trouble for the fights of what is RIGHT! I should probably NOT visit Russia ;)

I was dictated my Mammon for a while but then I got some clarity in life. Mammon is nice, but it's nicer to have free speech and basic human rights!

All the best,

/Abs
[Galaxy S 4 General] Absolon:
And here I thought they already had that installed... But then this document is from 2008...

From GSM Arena: Eyefon

"Conspiracy freak", "Crazy" hmm, yeah, all that I am
[Galaxy S 4 General] mahmoud007:
knox

did anyone thought that the knox solution might be within kies3 ??

http://update.kies.samsung.com/kies3_recovery_guide/firmware/emergencyrecovery/?lang=en-us

re installing upgrade might be the solution

if you know how to brick your device and what to do after this step fails

*Note:this step might work on device in download mode in general

for experts only ... do not brick your device if you dont know what to do next.

im not responsible for what will happen to your device ... try on your own risks.;)

hit thanks if this step did worked on your device :D
[Galaxy S 4 General] gazeddy:
No infact that procedure is known to trip knox in some cases
[Galaxy S 4 General] mahmoud007:
knox

now i get whats going on here

SECURE: SECURE MAGIC failure (recovery.img)
SECURE: SECURE MAGIC failure (boot.img)
SECURE magic check passed...
[TIMA trusted boot]: SEAndroid MAGIC failure (recovery.img)
RECOVERY IS NOT SEANDROID ENFORCING
[TIMA trusted boot]: SEAndroid MAGIC failure (boot.img)
KERNEL IS NOT SEANDROID ENFORCING
SEAndroid magic check passed...
SECURE: signature check fail. (recovery.img)
SECURE: signature check fail. (boot.img)
SECURE : Signature verification...
SECURE : Signature verification succeed
SECURE : Signature verification failed
SECURE CHECK FAIL : %s
SW REV. CHECK FAIL : fused : %d , Binary ::%d
KNOX KERNEL LOCK: 0x%x
KNOX WARRANTY VOID: 0x%x
[TIMA trusted boot]: SMC call to set the warranty violation fuse failed
[TIMA trusted boot]: SMC call to set the warranty violation fuse succeeded
[TIMA trusted boot]: Boot-time measurement successful
[TIMA trusted boot]: failed to obtain measurements %d ERROR: Cannot read ramdisk image
[TIMA boot measurement] : kernel secure check fail
[TIMA boot measurement] : Old/non-CL device - KNOX warranty void
kernel secure check fail.
Set Warranty Bit : %s
Secure check fail : %s

this is a part from file sboot.mbn that comes inside the official rom 4.3 for s4

the part which have knox and SELinux "SEAndroid" ... but still its just call lines include values for another program

and i asume the encryption part is none text ... or another programs or some 3d pictures or etc ..

but the question is what will happen if we change these calls with each other ?

for example :

KNOX KERNEL LOCK: 0x%x
KNOX WARRANTY VOID: 0x%x

changed to :

KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0

or at lease make knox run checking program again if that possible .re-scan the rom incase rom is fail in knox test

witch i believe will stop testing incase rom fails once .

will that be success or fail in flashing ?
[Galaxy S 4 General] fzeta:
It is clear that everything is in sboot.bin (i9305) but I can not unzip it :(

Enviado desde mi GT-I9305 usando Tapatalk 2
[Galaxy S 4 General] romaniansuperhero:
bypass the Knox Security on samsung galaxy s4 mini

Hi i found kernel to bypass the Knox Security on samsung galaxy s4 mini.

original thread http://www.pda-planet.com/forum/forum918/thread12024.html

XDA tread http://xdaforums.com/showthread.php?t=2431953

Hope it helps.:good:
[Galaxy S 4 General] TheEgonSpengler:
Sboot.bin is encrypted to prevent easy unpacking no doubt.
[Galaxy S 4 General] barto760:
+1
[Galaxy S 4 General] mahmoud007:
Knox

i have some info that might not be important ... but id like to say it anyway ... anything to help resetting Knox BS

if you were acknowledged with the Russian hack called freedom ... you probably faced the Google services issue that couldn't be opened after deleting freedom or even after freedom being halted "Turned off" even if you flash new ROM or anything you do is hopeless ... there was a solution for it actually:

if you didn't knew the solution ... it was acquiring rooted device and program called root explorer !!!

so you must have targeted a file name "hosts" in root/system/etc/ or system/etc "i don't actually remember" after changing every directory you enter permissions to rw and delete it in order to fix play store and all Google services issue

is it possible that Knox working in the same behavior ??

my suspensions come from this logo :

"tima_measurement_info has wrong size: %ld"
"tima invalid signature for measurements"
"tima keystore fails to read tamper fuse bit"
"tima keystore found tamper fuse bit set"
"tima keystore read good measurements FAILED: %d"
/data/keystore
"tima keystore sfs_mkdir() FAILED: %d"
/data/keystore/tima_key_store

and i suspect that the file named by fuse

i think tima must fail to read this file
[Galaxy S 4 General] romaniansuperhero:
Disable knox

# Amestris kernel script

# Mounting
/sbin/busybox mount -t rootfs -o remount,rw rootfs
mount -t rootfs -o remount,rw rootfs
mount -o remount rw /system
/sbin/busybox mount -o remount rw /system
#Disable knox
pm disable com.sec.knox.seandroid
setenforce 0

if [ -e /system/app/Superuser.apk ]; then
chown 0.0 /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
else
cp /res/misc/amestris/Superuser.apk.xz /system/app/Superuser.apk
cp /res/misc/amestris/su.xz /system/xbin/su
cp /res/misc/amestris/daemonsu.xz /system/xbin/daemonsu
cp /res/misc/amestris/chattr.xz /system/xbin/chattr
chown 0.0 /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chown 0.0 /system/xbin/daemonsu
chown 0.0 /system/xbin/chattr
chmod 06755 /system/xbin/daemonsu
chmod 06755 /system/xbin/chattr
ln /system/xbin/su /system/bin/su
fi;

if [ -e /system/xbin/busybox ]; then
echo " busybox is installed "
else
ln -s /sbin/busybox /system/xbin/busybox
ln -s /sbin/busybox /system/xbin/pkill
fi;

if [ -e /system/bin/busybox ]; then
echo " busybox is installed "
else
ln -s /sbin/busybox /system/bin/busybox
ln -s /sbin/busybox /system/bin/pkill
fi;

/system/bin/setprop pm.sleep_mode 1
/system/bin/setprop ro.ril.disable.power.collapse 0
/system/bin/setprop ro.telephony.call_ring.delay 1000

if [ -e /system/app/KNOXAgent.apk ]; then
rm -f /system/app/KNOXAgent.apk
rm -f /system/app/KNOXAgent.odex
rm -f /system/app/KNOXStore.apk
rm -f /system/app/KNOXStore.odex
rm -f /system/app/KLMSAgent.apk
rm -f /system/app/ContainerAgent.apk
rm -f /system/containers/framework/sec_container_1.zzzKnoxLauncher.apk
fi;
if [ -e /system/lib/libknoxdrawglfunction.so ];
then
rm -f /system/lib/libknoxdrawglfunction.so
fi;
if [ -d /system/containers ]
then
rm -r /system/containers
rm -r /system/etc/secure_storage/com.sec.knox.store
fi;
#Disablingadb shell knox Agian
su pm disable com.sec.knox.seandroid
setenforce 0
[Galaxy S 4 General] .NetRolller 3D:
Sboot.bin is not a zip file, it's the actual bootloader code. To analyze it (e.g. with IDA), load it to memory offset 0x43E00000 with a file offset (AKA header size) of 0x6000.

EDIT: I wonder if AdamOuter, Rebellos or anyone who can do UART readout as described in the UnBrickable threads has an I9305 (or any other Galaxy S3 with Knox). I would like to see a bootloader log.

Also interested in bootloader UART logs from the S4 and the Note 3.
[Galaxy S 4 General] dpeddi:
But... how to get uart log? You have to solder some test point?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] bungadudu:
Yea, would be cool if [MENTION=3682533]AdamOutler[/MENTION] and [MENTION=1767826]Rebellos[/MENTION] would join the efforts to reset knox.
[Galaxy S 4 General] Rebellos:
Bootloader log buffer can be fetched from kernel level by using viewmem on a rooted device (binary available there: http://blog.maurus.be/2011/01/23/samsung-i9000-irom-dump/) and reading addresses passed to kernel from bootloader in cmdline.

At eFuses tripping and whatnot: Qualcomm had an API for that in their bootloaders for pretty long time. Samsung is just the first OEM who really started to use it on consumer devices the way it's intended to be used.
[Galaxy S 4 General] mahmoud007:
Knox

i heard some people saying that Knox warranty void 0x1 will be reset when you receive new update by Samsung

is this true or just a blabs ?? :confused:
[Galaxy S 4 General] testadeferro:
No friend unfortunately it will be set with software update. Lol. From 4.2.2 to 4.3. And then there's no return.
[Galaxy S 4 General] mahmoud007:
Knox

i'v found these files and they changed the date recording to my Rom violation date :
[Galaxy S 4 General] dpeddi:
Which phone model? On my i9505 I don't have that folder..

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] cezaralboiu:
hi there do you know any way to root i9505 4.3 ML1 without knox go to 0x1? thank you in advance
[Galaxy S 4 General] rgshah3:
Kingo app
[Galaxy S 4 General] cezaralboiu:
the last kingo app is flashing a custom recovery via odin.. i mean version 1.1.7. is it safe?
[Galaxy S 4 General] gazeddy:
Not for knox
[Galaxy S 4 General] mahmoud007:
Knox

kingoapp root's the official rom .. no need for odin to install custom rooted rom

http://www.kingoapp.com/

but it might trigger knox .. im not really sure
[Galaxy S 4 General] xXTheLawXx:
Quit whining, you don't own a device truly until the warranty is void :p
[Galaxy S 4 General] testadeferro:
Can you explain? With facts?