yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] DjeMBeY:
Hehe, it's NOT as simple as it looks... Explain this to me, Flashing Pre-Rooted ROM's on NOTE 3 is triggering flag, all stock, same procedure as with S4 and different results...

it's very confusing TBH... Sammy is NOT telling us the whole truth IMO.. :p

BTW, don't forget that flashing Older NON-KNOX but still Official STOCK Kernel from Sammy, will rise the flag as well!! In this case we're NOT talking about any Custom part of FW and your warranty is VOID anyway!! Bollocks..
[Galaxy S 4 General] somator:
majority of samsung users never root never flash leaks custom kernels mods - they just use the phone

as someone said samssung will showcase kind of safe solution for the devices

do not expect samsung to warranty your fried by overclocking cpu/gpu

or device f...d up by flashing some crap or firmware from other device

on the other hand they will always service issues with display batery casing buttons and so on

btw this is RESEARCH not 'i want to whine on knox here' thread ...
[Galaxy S 4 General] Hawke84:
I already set up a seperate thread for that :p
[Galaxy S 4 General] chubby65:
EVEN FLASHING OFFICIAL FIRMWARE THROUGH SAMSUNG WILL VOID YOUR WARRANTY

THAT'S THE PROBLEM
[Galaxy S 4 General] dandroid13:
Why the caps lock? When I flashed the leak my knox thing remained 0x0...

Enviado do meu Xposed Galaxy S4 4G now Free
[Galaxy S 4 General] DjeMBeY:
Take this http://www.androidfilehost.com/?fid=23060877490003644 and flash ...

IT is Sammy STOCK Kernel ONLY!! Not even whole FW and you'll be screwed... :p Is it OK for you?? :p
[Galaxy S 4 General] CarlM34:
Mine too.....went 0x1 when I rooted!
[Galaxy S 4 General] 2dorr:
The 4.3 leak do not modify the Knox counter. I am done with Samsung phones because of a logical thing. Ok they want to stop ppl bringing broken phones to warrany after overclocking or modding the software. With this I agree. But if I put custom ROM with root, and the screen get yellow spots, and then I want to put official ROM and send it to warranty, they'll cancel my warranty because of Knox. And my phone has a problem that is not related to root. I agree to cancel the warranty if I send the phone with custom ROM, but not with stock. If you kill the phone with overclocking, you can't reflash it. Even iPhone can be brought to stock after you had jailbreak.
[Galaxy S 4 General] dandroid13:
Haha, I have 0x1 already. :D

But I bet that the guys from Samsung Brasil don't even know what knox is...

Enviado do meu Xposed Galaxy S4 4G now Free
[Galaxy S 4 General] lavafire:
I was a HTC customer, but then came the locked boot-loader on my Sensation which pissed me off. So I moved on to Samsung, the S4 being my first Samsung device already disappointed me 2 month in. 0x1 is staring me in the face and I can't do anything about it. Screw you Samsung, I'm going with XiaoMi or Oppo or Huawei next. Because guess what? They are cheap, have pretty similar spec, and hell they don't lock their bootloaders so I'll actually get warranty. FFS Samsung
[Galaxy S 4 General] somator:
that is not problem in any way,

if you use your device like 90% or more of owners, that is unrooted and updated only via official channelss OTA/KIES your flag will stay 0

that means samsung will replace your device when you will use it like it should be used in 100% of occasions unless you will try to dry it in microvawe

they fried 2 chickens on one stove ;] device is more secure (much more buisness clints) and they will be able to service more devices as those bricked by newblet users will not be serviced

lets be honest, most of issues with devices came from custom roms and their copy paste cooks. i wonder how many customized devices service centers saw ;]

and as ive said earlier they will still fix buttons, antenas, bateries, dispplays, any MECHANICAL or production issues but anything connected to fimrware cpu gpu with 0x1 flag will be denied

do not make such halo about it

---------- Post added at 05:20 PM ---------- Previous post was at 05:19 PM ----------

samsung is just saying 'do not f..k with us' ;]
[Galaxy S 4 General] elesbb:
Im sorry, but if we cannot mod our system, then i will not buy a Samsung device. If they refuse to support developers, then there is no reason getting an android device. Every user has different needs/features/uses and i personally customize mine to support my needs. There is no way i will have a device i cannot customize to MY liking. I would much rather have an HTC Touch Pro 2 running android on it then the Galaxy S5 running Tizen.
[Galaxy S 4 General] dandroid13:
I think more answers will emerge from their upcoming devcon... We need to wait and see, October 27th isn't far away.
[Galaxy S 4 General] somator:
customize ;] look ath the feature list of all thatm roms ... lmao

customization mad by changing icons, backgrounds and text heights

give me a break

---------- Post added at 06:37 PM ---------- Previous post was at 06:10 PM ----------

as themes should be an OPTION in stock menu ... why not ... even give thmers possibility to sell thm via samsung store WHY NOT SAMSUNG

but 9/10 kernels and other shenenigans ... cmon usless ... now most is based on cm (same base compiled with diff theme basicly)

and now when cm will fall apart it will be all down to theming ...
[Galaxy S 4 General] MattBooth:
I ahve two questions:

1) Why are you all STILL flashing with Odin, knowing this is the secondary root of the problem.

2) Will the 4.3 leak flash via CWM when converted in the Kitchen?
[Galaxy S 4 General] donalgodon:
That's exactly right. They do want to void your warranty, because it releases them from any and all liability for repairs and/or replacement of your device in the future. It's not "illegal" to experiment, but it let's the manufacturer off the hook, because the Samdung motto is basically:

"The customer is always wrong... screw the dev community, you don't get proper sources, and you'll use your device the way we command you to! Shut up and by another one."

I'm done with Samdung forever. Knox was absolutely the last straw for me, and I don't even have a Knox bootloader. It's just the principle of the whole thing. Loss of freedom masquerading as safety has long been the method of tyrants and despots.
[Galaxy S 4 General] dandroid13:
At least they still let you choose...

Enviado do meu Xposed Galaxy Note 10.1 now Free
[Galaxy S 4 General] somator:
how iss flashing via oin a problem

lmao, recognized in what :))))))) gj xda tribunal
[Galaxy S 4 General] elesbb:
Im also curious about your number two question.

As of now, us T-Mobile users have the ability to flash 4.3 TW ROMs. I am wondering if we can extract the /system partition from the odin file and extract the kernel, modem, etc and see if we can flash that via CWM. Thus eliminating the KNOX warranty bootloader.
[Galaxy S 4 General] jmw2207:
I don't find a problem with Knox and what Samsung are doing but it's more how they didn't warn of the new bootloader and it's consequences. I would've been nice for a choice to go down the Knox path or not. Then have firmware separated for normal users and business/high security users that want Knox. This whole thing was a bit of a ambush
[Galaxy S 4 General] MattBooth:
Oh boy.

1. Flashing with Odin is the cause of problem (apart from Samsung's ever present wisdom and bull**** against the dev community)... In that flashing with Odin will flash the bootloader. If you rooted with CF Auto-Root and kept CWM and flashed ALL your firmware via CWM, you wouldn't have this problem. The bootloader isn't flashed. Everyone rushes to Fayraab's threads to grab the latest and great and flashes it in Odin instead of waiting for a CWM flashable zip. It happened on the S3 with the bootloader that made triangle away mroe difficult, and it happened here with KNOX. Everyone flashed away, then realised it voided their Samsung warranty when it was too late.

2. It's unclear at the moment as to whether or not the 4.3 ROM checks the bootloader is up-to-date as well. If there isn't a current flashable CWM zip for it, I shall make my own and post it for users.

Search my profile and you will find out why I was given RC status. :good:
[Galaxy S 4 General] donalgodon:
At least on the S3 you could (and still can) flash the old ICS bootloader. The entire approach that Samdung has taken with the S4 and Knox is beyond reprehensible.
[Galaxy S 4 General] Fornowagain:
Seems 4.3 ROM's have problems with sound and wifi without the newer bootloader. But if you can do better that be great!!
[Galaxy S 4 General] SeaFargo:
Exclude the knox flag verification?

Is there a way to modify the actual bootloader, and exclude the knox flag verification? I mean, if it's a eFuse, it will remain fused, but the donwload mode will not show the flag, or can show a fake 0x0 flag, for warrenty purposes ... :D
[Galaxy S 4 General] donalgodon:
Modifying the bootloader is extremely complex and potentially dangerous, mostly because Samdung does not provide documentation on the bootloader. If they did, be something easier to resolve, but without documentation, you are just basically poking around at a bear in the dark, and if you poke in the wrong place, bye-bye device.
[Galaxy S 4 General] chickentuna:
There should be a way but that hacked bootloader needs to be signed which is thr hardest part
[Galaxy S 4 General] dandroid13:
I still think we need to wait to see what's going to happen next, they need developers to keep making great apps to sell together with the awesome devices they build... The upcoming devcon will be very interesting.

Enviado do meu Xposed Galaxy S4 4G now Free
[Galaxy S 4 General] chubby65:
Don't worry mate some people just can't seem to grasp the fact of what Samsung are up to
[Galaxy S 4 General] SeaFargo:
Let's hope that some Samdung developer will pass some info to other developers. Even the most secure documents have been often "cracked", Savage teaches ...

We will se. I have 0x1, and I just care about an eventually warranty request in the future ...

I am remarcably upset, because I have fused 0x1 just trying to flash back stock UBMGA over stock UDMHB. Reason for downgrading? Just because the phone, after OTA, boot with some crash on some app. And so the fastest way to have a full working phone was to flash the only complete stock rom in my hands at that time, the UBMGA. Results was Odin fault, Knox fused and phone in failure condition.

A compete flash of (later downloaded) UDMHB solve the problem. The Knox is done. Let's hope to be luky with my hardware. :eek:
[Galaxy S 4 General] nfribeiro:
We need help inside Samsung, unofficially of course.

Sammobile could help also but I doubt it...
[Galaxy S 4 General] MattBooth:
I'm in the process of running it through the kitchen at the moment, so we'll see what happens.

---------- Post added at 11:49 PM ---------- Previous post was at 11:32 PM ----------

CWM TW Android 4.3 leak flashable version:

http://romhut.com/rom/samsunggalaxysivi9505/stockgt-i9505rom52586c6fc1dae

HOWEVER, this is untested officially in the kitchen, but this should flash fine. The only issue that might arise is it's not pre-rooted... in which case just flash Chainfire's SuperSU zip from his website. Though I'm 80% certain it will be prerooted.

Please report back if it works.

ALSO, this is for anyone, of course, but feedback will be EXTREMELY useful form people on pre-KNOX bootloaders.
[Galaxy S 4 General] dxzh:
FYI, this article (http://www.gsmarena.com/samsung_galaxy_s4_mini_and_galaxy_mega_to_get_android_44-news-6932.php) has a leaked page seeming to suggest (if genuine):

- a "Business Knox" and a "Consumer Knox" will be coming to: Mega, GS4 Mini, GS3, GS4, Note 2 and Note 3, but not to GS3 Mini.

- Knox for consumers will be pre-loaded (either fully pre-loaded or loaded as a stub (which requires further download before activation) "depending on the operator").

- Knox is preloaded on all Note 3s.

- Knox is preloaded with 4.3 on GS3, GS4, Note 2.

- Knox is preloaded with 4.4 on GS4 Mini and Mega.
[Galaxy S 4 General] dimkit:
What's the difference between your version and the free boatloader Odin version of this thread. I believe none. So most possible is to come with a 4.3 Rom without a working Wi-Fi and sound.
[Galaxy S 4 General] dandroid13:
Yeah, you'll need the bl to get them working...
[Galaxy S 4 General] chickentuna:
Yeah. This was exactly what I'm thinking. I can only hope that when the time comes someone can poke around the kernel so that we can use the old bootloader and still have sound and wifi
[Galaxy S 4 General] MattBooth:
Did you try the zip?

It no, why are you posting?

Until someone tries this flashable zip we won't know. This is simply the /system partition and kernel. No radio is included, but there is a radio thread here: http://xdaforums.com/showthread.php?t=2192025 which includes the MI8 modem. Flashing with CWM is totally different to flashing with Odin.... Odin is actually flashing the NAND. CWM is more like copying files. In the Odin files there are more than just the system partition files included, which may affect things without the BL.
[Galaxy S 4 General] dandroid13:
Sure, I'm on the new bl so it should work fine here, must wait for someone else... :)
[Galaxy S 4 General] donalgodon:
Yeah, but think about what that really means for a second. We can be almost 100% sure that all the new flagship devices are going to have Knox bootloaders, and the consumer will (ostensibly) simply get to decide whether or not to run the software container which will come as a later install. There's no way that Samdung will not ship without Knox bootloaders. It gives them an automatic out in all warranty disputes, regardless of the reason for failure. Motherboard died? Screen died? Digitizer? Battery exploded? (insert failure)

Samdung resonse: "Too bad. Knox flag was tripped, No warranty for you. You must have caused it."
[Galaxy S 4 General] MattBooth:
Hmm, on my device, MGA bootloader, it won't boot. It may be a problem with the zip/implementaiton however :/

Can someone already rocking the 4.3 update check for me?
[Galaxy S 4 General] Segamalaga:
Don`t know ir already posted but I have some good news. There is one dev in Note 3 forum who have root his device whithout trigger his Knox counter. Maybe this kind of people (and [MENTION=631273]Chainfire[/MENTION] and more) can do the trick with all that Knox stuff.

Check it out:

http://xdaforums.com/showthread.php?t=2474422

(sorry for my poor english :) )
[Galaxy S 4 General] chickentuna:
It has been proven at least with the S4 that flashing a pre rooted stock firmware doesn't trigger the knox flag. I know that his method is different but for us with s4's, it's much easier to flash a pre rooted firmware.

Anyway great job on the root process. A very well written guide. Who knows maybe someone can find a loophole or an exploit of some sort regarding the rooting process that he did
[Galaxy S 4 General] timberwolf60:
I read up dJembey thread. Upon flashing the xxmei8 will set the knox flage to 01.

Send via i9505 using Tapatalk,

ROM: PYRANA MF8 1.7 LITE.,

CSC/Modem: OLBBMF8(STH)/XXUBMGA

Kernel/rec: GE V7/Phil 5.07.6.

SuperSU Pro 1.41, 64GB exFAT Card
[Galaxy S 4 General] chickentuna:
I was reading that thread as well and there are several reports that pre-rooted MI8 didn't trigger the knox flag. Now i'm confused.
[Galaxy S 4 General] krz_ayman:
Hi, changing motherboard solve the problem Knox?

or you can buy a new motherboard 9500/9505?
[Galaxy S 4 General] Dumbo53:
I've been following this thread as well as numerous Note 3 ones and all I can say is I think Knox is a buggy piece of crap, while at the same time the hardware quality control has gotten much worse. I think these 2 factors may help account for why different results are appearing from the same nominal procedures.

Among other problems, people are getting boot loops on brand new stock phones. One woman had to return four Note 3s to get one that would stop looping on her! Some put down their phones and a couple hours later they start boot looping on their own. Of course those rooting and installing custom recoveries are also getting boot loops. Some of these prove to be unrecoverable. I'm talking about unexplainable stuff, as if the system itself is unstable. Others of course have no problem and think these are flukes.

I recall reading about the history of Japanese automakers. To be very brief, they started cheap, then became well made, then achieved success and expanded like crazy, which caused them to lose control of their quality. Now they have as many recalls as US automakers. And to top it off, now there are computers inside, so occasionally their cars suddenly take off on their own like a bat out of hell...

Sent from my SAMSUNG-SGH-I317
[Galaxy S 4 General] garf02:
I have flashed I9505XXUDMI1-PRE-ROOTED-ODEX-FULL.rar and the knox warranty is 0x0. but you must not flashing custom kernel and/or recovery mod otherwise the trigger change to 0x1.
[Galaxy S 4 General] knakkers:
Hi guys, I have been reading keenly about this knox issue. I must say that like most of you I am greatly dissapointed!

Now on to my question...

If this (yet to be verified) efuse is located on a chip soldered onto the main board, would it be possibly to render it unreadable if for example the board is wet (while being careful not to allow the water indicators to spoil)? Or perhaps by some other method?

This may be morally the wrong thing to do but in all honesty, if my device fails due to a manufacturing fault then I feel I am entitled to a repair/replacement - especially since I am not going to be playing with cpu clock speeds or loading incompatible ROMs
[Galaxy S 4 General] nilezon:
I would guess that the eFuse, if it exists, is integrated into the processor chip. If not, then maybe we could find a hardware mod to prevent eFuses from blowing. Such hack already exists for the Xbox 360 eFuses.
[Galaxy S 4 General] knakkers:
In that case would rendering the chip unreadable also prevent Samsung from detecting efuse value change to 0x1?
[Galaxy S 4 General] dandroid13:
So, nobody tested it yet? I might give it a try then...
[Galaxy S 4 General] chickentuna:
Well he did. On an old bootloader:
[Galaxy S 4 General] .NetRolller 3D:
An idea:

Efuses are normally built into the SoC, I have never heard of an efuse in an eMMC chip. However, someone reported that replacing the eMMC removes Knox.

My guess is that "Knox warranty void" is indeed an efuse, but "Accept Knox-signed bootloader only" is stored in the eMMC.

Someone shouls compare pre/post-Knox dumps from the same eMMC chip (read out directly with an SD/MMC/eMMC reader, including boot0 and boot1), and look for a flag. This way, a pre-Knox bootloader may be flashed, and while the efuse stays blown, it won't be visible until/unless the bootloader is upgraded again.
[Galaxy S 4 General] bungadudu:
Sounds good!
[Galaxy S 4 General] spinky360:
Efused is in NAND ( eMMC ), All the new bootloaders are singed 265 bits key by hardware. And you have 3 secured bootloaders that are signing on to anotherone .... I will try a hack for loading bootloader on SD. But for this I need to oprn my phone so I can have acces to pins. ( that means only when my wife is not home :))) )
[Galaxy S 4 General] Hawke84:
How do u know for sure it's on emmc?
[Galaxy S 4 General] nilezon:
Well, in the Xbox 360 case you would actually not render the eFuse unreadable, but unwritable. The eFuse will never get blown. However, if you're already KNOX flagged, you're out of luck.
[Galaxy S 4 General] knakkers:
Now that is interesting! Since Samsung would have no reason to write to the eFuse, this should work. Now lets hope and pray that the clever people on this forum are able to make this happen.

Thanks for the lesson! :)
[Galaxy S 4 General] spinky360:
Here it is
[Galaxy S 4 General] dpeddi:
I rooted my phone using motochopper hack some time ago, that time I downgraded kernel to MDF rooted and upgraded kernel again using odin.

I applied all ota to my phone (I ignored about knox) and some time ago root stop working.

I apply same trick like first root...downgraded MDF than I see knox warranty 0x1.

So I'm sure that samsung changed their private key and newest bootloader miss old public key.
[Galaxy S 4 General] Burgscheinkerkdeiktraast:
I was about to buy SGS IV, then I wait for SGS V or get other phone like Oppo I think.

From one side I am not surprised Samsung blocked their phones - majority will have no problems with that. XDA members\users and other "custom" are meaningless so this is only their problem, however there should be possibility made phones customed :eek:
[Galaxy S 4 General] chubby65:
It's a pain in the arse Samsung have knox and by the looks of it LG are going to be joining them with LG gate

Who's next?
[Galaxy S 4 General] acme1974:
Mediacom:p

Inviato dal mio GT-I9505 con Tapatalk now Free
[Galaxy S 4 General] silentscreamer:
Samsung's Note 3 @ Amazon: best Sh|T ST0rM since Asus :D:p:thumbup:
[Galaxy S 4 General] medicus07:
A great dev found out a way rooting the note 3 without affecting the knox counter.

http://xdaforums.com/showthread.php?t=2479952
[Galaxy S 4 General] DjeMBeY:
Wake up mate..... since yesterday we have working version for S4 (I9505)....

Today I released the new leaked FW (XXUEMJ3 4.3) using this method so everyone can enjoy root and KNOX 0x0 in S4 as well. ... :p
[Galaxy S 4 General] lmerega:
Can you share the link? :)
[Galaxy S 4 General] DjeMBeY:
http://xdaforums.com/showthread.php?p=46442317

[ROM]><I9505 XXUEMI8><[JB 4.3]><Pre-Rooted STOCK ROM's><Odin/CWM><Odex/DeOdex>
[Galaxy S 4 General] .NetRolller 3D:
New idea:

If the data is indeed being stored inside the eMMC, then presumably the RPMB feature is being used. This feature allows reads/writes to a "hidden" area of the eMMC, protected by access keys. However, the binary doing the reading/writing (in this case, the bootloader) must somehow know the correct key. From what I read in the specifications, the security of the RPMB relies on this binary being secret. In our case, the bootloader itself is published, so maybe we should start looking for RPMB accesses in it.

OFF:

I sense a pattern here... first Samsung (Fort) Knox, then LG (Water)Gate... what's next? Huawei (Penta)Gon?
[Galaxy S 4 General] spinky360:
Hm,,,... i was trying all ( even NAND erase ALL ) but as all we know ... abut.mbn - fail ... And right now im will start to study this "thing ". I want to see in witch sector is writing "aboot". Why i want to find out: I have 2 phone's i9505

1. MF8

2 MH8

I made this thing. I downloaded the MF8. Deleted the aboot.mbn file from it. And guess what ? ODIN says PASS. In settings i had: Base Band MF8 and Permisive after rooted

Lets not rush ... a solution will come ( soon )

PS: 1st the phone wasnt booting: I needed to enter in recovery ( original ), and there i saw: Invalid Argument /Data

Unable to mount /Data

I give a restore factory data , Started to format data, cache ... etc ... and that's all ! Working but knox still in boot and 0x1

---------- Post added at 08:57 PM ---------- Previous post was at 08:43 PM ----------

Can someone try to enter in Service Menu and to restore Golden Backup ? Because at me is not working service Menu ...
[Galaxy S 4 General] joecool666:
Service Menu

i had ago no joy on MH8 BTU-but there is a service menu star hash-0011-hash so when i enter it i hit back button then enter 1 it just brings me back to the start. unrooted
[Galaxy S 4 General] 95mediatech:
Yeah true, I agree with you we actually pay for that software too, but look at Samsung they did many stupid tricks like flash counter to give us headaches and now forcing KNOX security system to all the devices it's not good they lock our freedom. Cyanogenmod mod is the only solution to this. Cyanogenmod is good if u love pure android experience on a raw powerful device like S4. I only use Multi Window and smart stay that even exist before S4.

Thats all friend. Hope solutions available for this.
[Galaxy S 4 General] lynx2k50:
I'm sorry for the noobish question but how can I regocnize if my KNOX flag was set to 0x1?

I booted to the bootloader but can't find anything with "KNOX Void" or something like this. Is it normal?

And, which original firmware is safe to flash to get back the original state without changing the flag?

ATM I am running a GE rom.