yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] Kiwyxda:
When you buy a computer, you can change OS change version of driver modify windows registry or linux kernel and it does not normally remove your warranty.

With a Samsung, you can't do anything of those things without voiding the warranty (at least when knox is activated).

Is it fact enough or maybe it was a joke :D
[Galaxy S 4 General] mahmoud007:
Knox

hello there

today i was comparing s4 JB 4.2.2 ROM and s4 JB 4.3 ROM

and this is a picture for the both ROM's from inside

View attachment 2491222

as you see there is new file in 4.3 ROM name of sbl1.mbn

View attachment sbl1.txt

i clanged extension to a text and removed the encrypted part till first readable word to make it easier to read

this is an s4 Odin logo for someones device while he was trying to downgrade !!

notice that sbl1.mbn file interferes :

[COLOR="LightBlue"]<OSM> Enter CS for MD5..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OJVBMGA_I9505XXUBMGA_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
[COLOR="Red"][B]<ID:0/004> sbl1.mbn[/B][/COLOR]
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!![/COLOR]
[Galaxy S 4 General] testadeferro:
Depends where you are. At least in my country there's some legislation that is above EULA.
[Galaxy S 4 General] szczeslaw:
Can you change MB or VGA BIOS with some unofficial version and still keep warranty? Nope.

Besides voiding the warranty by rooting or flashing something custom is not limited to Samsung. Almost every manufacturer does that.
[Galaxy S 4 General] Kiwyxda:
Well they goes to the next level with that knox flag which might or might not be an efuse.

Concerning flashing unofficial bios on your motherboard or vga controler, I in fact never fell any need for that but if you flash something unofficial and it does break your hardware (what a flash can do) then I guess it's normal that your screwed because it's a really low level program.

Your not trying to flash the bios of your CPU when you flash you phone. And in the case of samsung even the flash of an unofficial version can make you loose warranty.
[Galaxy S 4 General] gazeddy:
Our flahsing though GENERALLY doesnt touch the bios etc we flash the os
[Galaxy S 4 General] mahmoud007:
who said its an efuse ??

downloadable efuse ???

i think its loop program will exit the loop when knox counter hits 0x1 .. meaning knox it will stop working when counter hits 0x1 tho it'll still be working as security program against rooting process .

and as in aboot.mbn Knox warranty void 0x%x depend on %x status ... i still dont know where %x gets his value from but probably a file .

we will know soon
[Galaxy S 4 General] Kiwyxda:
Well I say it might or might not be I never affirme it is, I don't know. but when youmake a low level clone with JTAG and it set your flag to 0x1 I find it pretty creppy.

Well I'll hope we'll find out soon enought what Samsung Knox void flag really is
[Galaxy S 4 General] mahmoud007:
knox

what happens if i have i9505 pit file and did re-partition along with stock JB 4.2.2 ?

anyone have good/bad experience in this step ?
[Galaxy S 4 General] bungadudu:
Been a while since the threads regarding knox are running in a circle..

From 2 months ago.. :
[Galaxy S 4 General] dpeddi:
by mounting in loopback NON-HLOS.bin (I9505XXUEMJ7) on "/image/tima_atn.b02" file there are some interesting strings:

/efs/prov_data/knox/knox.dat

"Not enough space to save TIMA measurement"

"Not enough space to save Tamper fuse"

"Failed to get tamper fuse value!...."

"Attestation: Failed to load measurement!"

"Not enough space to save Nonce"

"Private key must start with {0x30,0x82,xx,xx,0x02,0x01}"

"Attestation: failed to open key file"

"Cannot alloc mem for private key\n"....

"Attestation: Failed to load modulus: %d\n".

"Attestation: Failed to load private exponent: %d\n"....

"Attestation: Failed to load public exponent: %d\n"

I don't have that file and directory and I have knox 0x1.... maybe the bootloader delete that file if knox void?
[Galaxy S 4 General] mahmoud007:
Knox

one of the Samsung staff working in IT just confirmed to me that Knox CAN BE RESETby the legal Samsung Warranty Company only !!!

but he told me they'll charge additional Cash .. when i told him it was triggered by bad Kies update .. he asked me to go the warranty Company and tell them my story .

this is confirmed news from an IT working inside Samsung warranty branch Company .. but the branch he works on only deliver devices to the original Company if this branch cant fix it .. like Knox !!

this is Confirmed news he told me that Just Now !!
[Galaxy S 4 General] bungadudu:
If you are friend with him, you can ask him to share the method used and split the ~3000$ bounty together;)
[Galaxy S 4 General] mahmoud007:
ill tell him that tomorrow . :good:
[Galaxy S 4 General] Damir78:
Rooting smartphone is EXACTLY like using Control Panel in your Windows, especially so called "hidden options". But in PC world you wil NEVER lose your warranty if you used it.

In PC world you will losing your warranty ONLY if your overclocking or incorrect flashing caused hardware failure.

Plus Samsung do not allow you to re-install older software, so you are their slave EXACTLY. YOU ARE NOT OWNER OF YOUR DEVICE - in their eyes YOU ARE JUST ANOTHER STUPID CONSUMER.
[Galaxy S 4 General] gazeddy:
Not quite. Rooting is like installing control panel and then using it.
[Galaxy S 4 General] bungadudu:
Not quite. Rooting is like operating the pc as an administrator and not as a guest.
[Galaxy S 4 General] testadeferro:
Just imagine you have a Linux desktop and can't have root privileges on the machine... or the seller telling you you loose your warranty because of that. Or in windows loosing warranty by using a program as administrator... lol
[Galaxy S 4 General] FlanjeUK:
Imagine overclocking your Samsung and raising the throttling start temp well above the recommended specification's, then stressing the phone until the heat killed it, THEN expecting Samsung to replace your device at their own expense...
[Galaxy S 4 General] testadeferro:
Imagine you never updated your brand new s4 awhile ago (the first firmwares) with known heating issues and it burned like some did?
[Galaxy S 4 General] FlanjeUK:
You would be covered by warranty either way because knox wasn't activated back then ;)
[Galaxy S 4 General] bungadudu:
You're a Samsung employee or paid student?

Again, relate to the pc situation.

Can you overclock the **** out of your pc's cpu?

Can your cpu die even though you had great care of it?

What happens?

If they can't prove it's your fault the cpu is replaced.

Now please tell us why this isn't possible with our smartphones which are basically the same thing and have similar prices. :what:

//20% of the people i know have their pc's cpu/gpu/ram oc'ed.

20 times less persons I know to have their smaryphone's cpu/gpu oc'ed.
[Galaxy S 4 General] gazeddy:
Killing it by overclock is not the same as rooting "destroying" the home button

I and many others root to debloat and make firmware tweaks. Ive never overclocked my phone and wont due to passive cooling

---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------

Either way root killing the hw is not what this thread is about its how the device behaves after tripping the knox flag. Apart from multicoloured script top right booting into recovery i havent noticed any differences
[Galaxy S 4 General] dpeddi:
OT: It seems that Samsung overclock your phone for you when you use antutu or similar sw ?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] FlanjeUK:
I merely pointed out a different perspective...

In my case I have pre knox bootloader and am running a custom AOSP KitKat 4.4.2 ROM and will never trip my flag :P
[Galaxy S 4 General] planetf1:
I'm close to rooting and or re romming...the reason is primarily debloating and address issues reported to Samsung but unresolved in official builds. I'm just deciding whether to make the jump.m
[Galaxy S 4 General] linedot:
what's that in aboot.mbn at offset 0x59565: androidboot.warranty_bit=%d. This looks like a parameter passed to the kernel. If overriden with a hard 0 might cause some software to think the bit isn't set. Isn't helping with resetting the bit of course, but could make the container work with 0x1 or something...
[Galaxy S 4 General] Damir78:
Like in EVERY CASE of hardware failure, SERVICE has to prove that it's customer fault. It's easy to find a reason for damaging chips. In most cases rooting gives me abillity to remove bloatware or to stop some unwanted service, or just to remove comercial ads.

But with this knox Samsung acts very unfriendly, and rigid. They have to realize that their devices are expensive and for that money I expect A FULL CONTROL OVER MY SYTEM.

Whatever, they will probably learn THAT on a hard way - they are already loosing some buyers because of this shameful move. Greedy and stupid Samsung.
[Galaxy S 4 General] androidtweak:
Samsung made the Knox so there will be a reset app for it.
[Galaxy S 4 General] andyfactor:
Or a work around of some sort. I don't see this whole KNOX thing as air tight. Now, will someone please correct me on what exactly KNOX is, and what it's doing that won't allow users flash older firmwares and bricking phones. Is it setting off some sort of eFuse that renders the phone useless if tripped, or is that there specifically for simple tampering identification or warranty proof. Why cant the feature be removed, and what is SELinux's role in this. I'm new to all of this, simply driven by the fact that the performance of 4.3 is absolutely dismal.

P.S: Why is KNOX using up 300+MB of RAM, and 35% of my CPU when my phone is idol?
[Galaxy S 4 General] mahmoud007:
Knox

i know this sounds crazy .. but there is a way to flash eMMC using BlackBerry wiping software BBSAK and JL_cmder

i never tried it but ... i know BB depend on eMMC and i had one always Brick and unBrick it till battery finally Blows

maybe it'll work with s4 or we add new identifications for S4 it might work .. specially JL_cmder i think it might work
[Galaxy S 4 General] [opensys]:
After read all posts on that Thread in past tree months or so, I think that could be pretty close to a solution.

That cold be some pass over knox making a illusion that it is at 0x0.

In my opinion exists two possibility's to solved the "knox malware".

1º Use the repair utility from Samsung authorized repair stores, if some one can get it :)

2º Make the boot thinking that is all ok, doing that by overriding the location where it is reading the bit of 0x1.

But some questions:

Is boot reading about knox on aboot.mbn file area ? and passes that information to kernel ?

Is possible to flash aboot.mbn without brick it ? I say this because knox have set at 0x1 and don't let you flash boot files with odin.

Don't boot files signed ? if so any change on files will result on unsuccessful flash.

Maybe can be done by jtag...
[Galaxy S 4 General] Mwyann:
I agree with you with the fact that you should have full control over your own phone, and Knox doesn't prevent you to do that, it just flags that you did it. Now market is market, they're probably losing power users like us on XDA (which is a very low percentage of their customes frankly) and on the other hand they're gaining much more enterprise users, where the secure Knox container is used. Enterprises were waiting for strong security measures like this, and now Samsung have it so they can sell phones to businessmens. And that pays much more than power users who keep fiddling and bricking their phones ;)
[Galaxy S 4 General] Mittaa:
Flashed 4.3 Samsung firmware a few days ago and of course I now have KNOX 0x1.

It was a choice between Samsung or freedom ... and I choose FREEDOM :victory:

My daily is CM11, I have custom recovery and I flash whatever I want ;)
[Galaxy S 4 General] mrgold2505:
why in stead of fighting with NSA and Samsung, the Devs just don't tell us the best way to hard brick our mobile and after that send it back to a new replacement. This will resolve our problem of the avoid warranty....lol
[Galaxy S 4 General] Mittaa:
Flash wrong firmware ... :laugh:
[Galaxy S 4 General] Damir78:
No, you are wrong - Knox is something what they're trying to present as ultimate business solution, but it isn't. In a fact, knox is something what restricts (us) users to gain full control of OUR DEVICES!

And it's very treacherous move. What they REALLY want is to REDUCE OUR FREEDOM in every possible aspect. They are already spying us, now they have to limit our freedom. Next step is slavery. But that slavery will not be like medieval slavery - we wil be their slaves in our own minds, reduced, stupefied and FULL CONTROLED.
[Galaxy S 4 General] Mwyann:
Let me know if I'm mistaken, but Knox doesn't restricts anything at all, besides warranty. You CAN do anything you want with your phone, at least they're not fighting against rooting. It's just a matter of security and warranty (except in Europe where it cannot be used to void your warranty).

So, stop complaining that you "CANNOT" do whatever your want with your phone, because you CAN actually. Just trip the f***ng flag, or buy another smartphone, or stop using smartphones/internet altogether if you don't want to be spyed or slavered (lol).
[Galaxy S 4 General] Damir78:
Glad that you find my post funny. Exactly because such conformistic people (sheeps) like you they are rulers of the world. And I'm sorry if you don't understand that.

Actually Knox is very restrictive mechanism - because you can lose your warranty if it was triggered. So, you CANNOT ROOT your expensive phone, nor if you want something simple as to remove ads. So actually You are not the OWNER of your phone (or your money).

Is it so hard to understand?
[Galaxy S 4 General] Mwyann:
What I understand is that you CAN do exactly what you want to your phone, you can root it, flash it, brick it or whatever. The only thing is, if you do so, you might lose warranty (again that's not true to everyone).

Let's extend it to both sides (not only your side) : you could understand that Samsung won't provide software warranty if that software has been modified by you in a manner that was not permitted by Samsung (but a hardware problem like a broken button or screen issues shouldn't be a problem). Also, removing ads is quite always against the User Agreement, because ads are supposed to support the developers, and you can often buy full versions without those ads. So if you don't want to play the rules by removing ads or installing warez, you must admit that the rules don't apply to you either.

You want all the goods things to you without a return, that's not how this works, sorry. You knew it when you purchased the phone, or if you did not, you can also sell this one and buy another brand's.

Good luck.
[Galaxy S 4 General] Damir78:
No, I am talking about those ADS which are in my BROWSER, and I want to remove it! Also I want to be able to remove some unused bloatware, services, etc.

And those ads (profit) aren't for support developers, they are just for GOOGLE. Google exploiting open source project (Linux/Unix/Android) for their profit and to collect data about us. Why we can't roll back ROM if newest has some issues? You didn't asked yourself that?

As they have full control over my device, I want it too. I want FULL CONTROL over my hard payed device. I don't want them to reduce my rights nor monitoring me.

I am against that. Every man and woman must be against greedy corporations and twisted govs, for our benefit and benefit of our children.

Soon will be just: US or THEM.
[Galaxy S 4 General] romaniansuperhero:
Samsung jig

Hello

so if you start your phone with the 3 button combo you get odin mode.

if you start your phone with a samsung jig you get factory mode.

here is how to build one http://xdaforums.com/showthread.php?t=1604707

Can someone that has a triped hnox flag please downgrade in factory mode?
[Galaxy S 4 General] clonednull:
Ok you say i can do anything with the knox flag like before. Please tell me how to downgrade the bootloader!?

...I cant hear you mate...? :banghead:
[Galaxy S 4 General] Michal Z.:
For example you can't downgrade to lower version than 4.3 (specifically you can't get back to bootloader that has no knox because it will brick your phone).
[Galaxy S 4 General] bungadudu:
Any follow up for this?
[Galaxy S 4 General] Mwyann:
I don't have a S4 actually, but a Note3 with Knox (and no pre-4.3 anything). I assume you can't use an old bootloader for a newer OS (ex 4.2 bootloader and 4.3 OS). But can you downgrade the full phone, OS included? That would make sense.
[Galaxy S 4 General] gazeddy:
No as there isnt a 4.2 rom for note 3
[Galaxy S 4 General] frostmore:
no,no downgrade as the bootloader is locked when u update to 4.3 on the s4.

any attempts to downgrade to previous version will cause a bootloops and trip knox.

like you i do not have a s4.but i have been following this thread for some time and pple have reported what happens when they tried to roll back to 4.2 pre-knox.

in other words,once you update to 4.3,you have a locked bootloader and there is no way you can do anything about it.

so,do you still want to claim knox lets you do anything and everything you want? coz from my view point,knox effectively is restricting MY RIGHT on how to use MY PHONE paid for with MY MONEY.
[Galaxy S 4 General] Mwyann:
Apparently you can still revert OS to 4.2.2 even with 4.3 bootloader (http://xdaforums.com/showthread.php?t=2491499). So as long as I can still use the OS like I want to (i.e. kernel, root and everything), even if there's locked bootloaders, that's not really a big concern for me. The bootloader is just the first thing running, but after that you still have the full control over your phone as long as you can boot any (compatible) kernel/ROM. Also, Knox is one of the features implemented in 4.3 but certainly not the only one, maybe it's not because of Knox that you cannot downgrade bootloaders (typically unreversible changes in some eMMC configuration that breaks 4.2 bootloader or whatever).
[Galaxy S 4 General] tcntad:
you CAN root your phone, you CAN do whatever you want with it.
[Galaxy S 4 General] bungadudu:
Really man?

Following your logic - you CAN enter a car dealership with a gun and no money and CAN walk away with a car.

Our similar, you CAN rob a man.

Yes, you CAN. But there are repercussions!

For the above examples jail.

For the knox situation loose of warranty and loose of the possibility to access knox containers ever again on that phone.

So in reality, no YOU CAN'T DO WHATEVER YOU WANT TO YOUR OWN PHONE!
[Galaxy S 4 General] tcntad:
Yes you can walk in to a dealership and steal cars

yes you can rob a bank or a person

Yes you still can root your phone, you were sayng you cant root your phone due to KNOX which is NOT correct. Many have rooted their phones.

Im sure in EU they cant just void warranty like they want, they have to follow EU-laws etc.

Then it depends on what warranty is void, whole or just software warranty.

PS. Are you using KNOX? I knox E-fuse/knox sucks and I agree somewhat with you, its all bulls***.
[Galaxy S 4 General] Opensystem:
I wish a moderator would drop in and clear out your guy's petty squabbling. This isn't a thread for your disagreement over freedoms.
[Galaxy S 4 General] tomicop:
i have s4 mini gti9195 custom rom cyanogem mod 11. if somebody can tell me. i can come back to stock with knox kernel lock 0x0 and knox warranty void 0x1?
[Galaxy S 4 General] gazeddy:
Going back to stock will bring you back to exactly that
[Galaxy S 4 General] PANCAN:
Question

Isn´t it possible to "update" your device via OTA like if you were Samsung and flash an other rom or bootloader with debugging.

So I think that Samsung wouldn´t lock the bootloader for themself and if you prepare an update with an older Stock rom or a rom without locked bootloader like the new updates (mh5, mj5, ...) there could be a way to downgrade or get rid in any other way of the bootloader and also the Warranty Void am I right?

sorry for my bad english ;)
[Galaxy S 4 General] gazeddy:
Problem is ota updates are signed and the phone knows to reject unsigned ones
[Galaxy S 4 General] PANCAN:
possible to sing as samsung

thanks but isn´t ther a way to treat your device like if you we signed to? :(

do you think they use PGP for that? then it could be difficult
[Galaxy S 4 General] gazeddy:
Possibly with an xposed module to disable the signature but i dont think its will work
[Galaxy S 4 General] PANCAN:
I have Xposed this would be great :eek:

but i think the signature "check" is done with the bootloader and that is looked
[Galaxy S 4 General] goodex:
How is the bootloader locked? With a password?

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] nitrate:
It's encrypted... Every hardware in these days that uses some kind of an operating system has an encrypted bootloader. It's just for security reasons. Game consoles as well use it that way. An unencrypted bootloader with an exploit is a big security fail with catastrophic end effects. For example: PlayStation 3.

Gesendet von meinem SM-N9005 mit Tapatalk 2
[Galaxy S 4 General] PANCAN:
it isn´t that easy but its kind of crypted so you can´t write on it without that key or if you want so password :)
[Galaxy S 4 General] goodex:
Thanks both :D

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] nitrate:
I think this would require an exploit within the bootloader since xposed is a software mod. You would actually have to break into the bootloader itself. That won't be easy - maybe impossible.

Gesendet von meinem SM-N9005 mit Tapatalk 2

---------- Post added at 08:03 PM ---------- Previous post was at 07:55 PM ----------

Plausible would be a boot process like this: the bootloader verifies the signature of the boot image, decrypts it's contents into a safe and encrypted area (like RAM), deletes the decryption keys from that safe area and boots the decrypted image afterwards. This is just a short possible boot method. There are plenty other possible ways - for example if you choose to make user processes (apps) boot from another "level" than the bootloader does.

This is all just speculation. But it has almost been done: PlayStation 3. The console has several encrypted boot levels. Hardware / software levels are separated that way.

Gesendet von meinem SM-N9005 mit Tapatalk 2
[Galaxy S 4 General] PANCAN:
thanks for the hope

but maybe true :(

---------- Post added at 08:12 PM ---------- Previous post was at 08:04 PM ----------

if the decrypted files would be on the ram you could make a snapshot of your phone by freezing it and read the ram with you pc :P
[Galaxy S 4 General] gazeddy:
In theory possible but bear in mind this would likely be done in a few cpu cycles and therefore far to fast for us to catch lol
[Galaxy S 4 General] PANCAN:
true but would be worth the work

thougt buying a new device with older firmware or mayb switch away from samsung
[Galaxy S 4 General] goodex:
why :0

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 General] gazeddy:
Unless this is sorted im not buying another samdung
[Galaxy S 4 General] PANCAN:
first of all because of Knox and the looked bootloader

second because of region look and trying to lie to there costumers
[Galaxy S 4 General] bogdan1980:
I see a lot of Sammy employers here, they are quite aggressive like my pitbulls.