yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] leathan:
I think i need to push sbf files for 2.3.4 but i dont know how and every link on the internet of those files is broken. Please help :( and now battery says "battery to low to flash"

:(

:(
[Android Q&A, Help & Troubleshooting] leathan:
I tried the option "starting bp only hardware bypass mode" and it loaded to the screen of a battery with a ? Mark on the battery, when i plugged in my charger it said battery charging and that it was At 5%
[Android Q&A, Help & Troubleshooting] leathan:
Woa so i tried a different mode and it loaded the battery screan saying it was at 30% then when i unpluged the charger it turned off.
[Samsung Galaxy Mega] sanjay_2001:
hi guyz... i have purchased Samsung Mega 5.8 a week back..

i am facing a new problem i am unable to move my apps to SD. i installed APPMRG (III) its shows it does not support.

is there any way to send the apps to SD card.

Thanks and Regards,

Sanjay Dakshinamoorthy
[Samsung Galaxy Mega] starmaster10:
Try this, install a app called "Active Apps" from the google play store as it is free and open it up and on the first page the heading will be active applications were you can stop running apps, now flip the page to page 2 by swiping across the screen or tapping on the little arrow on the right side.

On the second page the heading at the top will be package manager and this is were you can un-install apps, but you can also bring up the apps properties, you will see the icons of apps on the left side of the screen, but do not tap on the icon itself but tap on the name of the app which is right beside the app icon and that app properties will open and in this properties part (it is like task manager look) and if you see the move to SD button light up then that app should be able to be moved to your SD card..give this a try and see if it works for you. :)
[Samsung Galaxy Mega] sholsten:
Did you have any Sim issues when you 1st used this phone?
[Samsung Galaxy Mega] sanjay_2001:
i tried it... i am not getting move to SD option....
[Samsung Galaxy Mega] sanjay_2001:
till now i did not receive any sim issue...
[Samsung Galaxy Mega] sholsten:
Ok. Mine didn't work at first. I had to install the Sim card upside down for it to work.
[Samsung Galaxy Mega] starmaster10:
Does your phone recognize the SD card and did it ask to format it as i believe it has to be formatted to a fat32 filing system unless that has changed now..or can you format it with your pc and then try it in your phone and see if you can move apps to it, also make sure the SD card is fully inserted all the way as if not it can cause problems also.

If nothing is on this SD card i would totally reformat it and then try it in your phone also. :good:
[Galaxy S 4 General] theq86:
As you may already know, the latest Samsung firmwares came with a new secured bootloader. You can recognize it in download mode easily. It states: Knox warranty void: 0x0 or 0x1.

As for now, there is no way to reset that flag from 0x1 to 0x0.

Then I read in a comment of Chainfires post concerning that flag, that as long as you do not try to downgrade to a non secured bootloader, this flag will not change. He claims to have that information directly from Samsung.

https://plus.google.com/u/0/+Chainfire/posts

Has anyone already experience with rooting an "untouched" S4 which has the secured bootloader and can confirm or decline that?

- - - - - - - - - -

Conclusions and Facts about KNOX-enabled firmwares (based on statements from chainfires post and it's comments above, ans based on this thread)

Not possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://xdaforums.com/showthread.php?t=2444671, not confirmed)

Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1

Flashing unsigned or modified images via odin will set knox to 0x1

Samsung stated, resetting the flag is impossible

KNOX is mandatory and can not be completely removed

Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so

Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)

KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty

Assumptions on how KNOX flag in bootloader works:

Some experts think, an eFuse is involved. (http://en.wikipedia.org/wiki/EFUSE). An eFuse is mostly only incremential. Even unwriteable by low level tools or JTAG. But it is still not proven, that eFuse is used.

Knox technical information:

https://www.samsungknox.com/overview/technical-details
[Galaxy S 4 General] bungadudu:
Also interested in this..

(don't really have high expectations though... )
[Galaxy S 4 General] coligulus:
I used the CF Auto Root to root an unlocked i9505 and the flag changed. I have since un-rooted and restored to factory settings however the flag remains the same and no Knox container can be created on the device now. :mad:

If anybody has an update to a solution for this that would be greatly appreciated.
[Galaxy S 4 General] DjeMBeY:
My status changed to 0x1 after flashing full NON-ROOTED , UNTOUCHED XXUDMGG with STOCK KERNEL MH1!!! :/

In my case STOCK KERNEL triggered this flag! When I tried to downgrade the FW it always failed in Odin and KNOX WARRANTY wasn't increased...

It's really confusing and it looks like Samsung is lying to us....
[Galaxy S 4 General] bungadudu:
Lie about what?
[Galaxy S 4 General] nfsmw_gr:
You flashed stock firmware and you voided KNOX Warranty?

Damn...:(

I wish you good luck in trying to figure out what to do now!
[Galaxy S 4 General] harise100:
In the same Chainfire Google+ post, somebody mentioned there could be a so called 'eFuse'.

Like a normal fuse, a piece of hardware gets broken beyond repair. The 'e' means that this can be triggered and checked by software.

But I am no expert, this is just hearsay.
[Galaxy S 4 General] DjeMBeY:
About details... This flag should change ONLY if you try to downgrade the bootloader but it's not the case...

Yeah, I'm really angry! :/

I simply repacked MGG and included previous STOCK Kernel MH1... KNOX WARRANTO VOID = 0x1

WTF Samsung????!!????!!! :/
[Galaxy S 4 General] theq86:
seems samsung also checks kernel and recovery binaries. whenever something tries to bypass knox the flag is incremented.

OT: It sucks and I really will sell S4 for Nexus 5 when it's released :mad:
[Galaxy S 4 General] gsmyth:
I think Samsung's aim was to make the Knox functionality as 'secure' as possible and it seems to have worked (for now) and so is fulfilling its intended purpose. When I first heard about it, it seemed to be something intended for business/enterprise mobile use, so wasn't expecting it to roll out to all consumer handsets (especially not fully enforcing it).

Once the flag is incremented does that mean that the knox functionality can no longer be used? I know we all want to have a choice, but are the current consequences just that we are unable to downgrade firmware?
[Galaxy S 4 General] jas0nuk:
Interesting. Offtopic... I remember the Xbox 360 used a similar thing, 192 fuses and one was blown every time the bootloader and/or dashboard was updated, eventually they started using this to prevent downgrades and detect tampering.

They want Knox-enabled firmwares to run on totally secure, untampered phones. Not surprising, really.
[Galaxy S 4 General] theq86:
Well, I am always a fan of full reversibility. It's like a flaw to me to have a visual mark that I changed something.

If that Knox flag would touch the warranty only in case you used the phone in a company, and would not change anything for normal users I could live with is. But how to distinguish exactly between private and corporate usage?

It's unfair to be forced this way...
[Galaxy S 4 General] exprxp:
Does anyone know hot o downgrade ABOOT.MBN

I tried to do JTAG with an old bootloader and now i have no power at all, If I do JTAG with a new bootloader, then phone works fine again.

Even all partition from a good old phone I have copied to new I9505 and as soon flash pass, no power up at all.

Any idea how to downgrade ABOOT.MBN and good scripts to do that?

Thanks.
[Galaxy S 4 General] theq86:
Another indicator for an eFuse. Even with JTAG you can not reprogram the fuse chip. It could be a check somewhere in the low level firmware, or even in PBL for the knox warranty state...

Remember, it could have been there since S4 release. Just that the new bootloader enabled the fuse thing.
[Galaxy S 4 General] exprxp:
What I haven't tried yet to replace eMMC chip, I think that KNOX security inside that chip. I tried to do JTAG via USB Recovery tool for QDLOAD device. When my phone works fine I just shot Resistor on a board and phone will go into QDLOAD by itself.

I will try all ways then I can write you back the status of my job.
[Galaxy S 4 General] theq86:
I'm very interested in the qdload thing. If I got it right, you can do jtag via usb? how ? what tools needed ?
[Galaxy S 4 General] Estoroth:
So basically you flashed a modified and thus nonofficial firmware? :)
[Galaxy S 4 General] trveller72:
SAFE with Knox

I am not a developer so I just add here a few links from Engadget:

It's an IT manager's pipe dream, of sorts. A comprehensive collection of features that include Security Enhanced (SE) Android, secure boot, TrustZone-based Integrity Monitoring (TIMA) for protecting the kernel, Single Sign On (SSO) and that application container concept made famous by BlackBerry, just to name a few

Feb 2013 - Samsung announces SAFE with Knox

http://www.engadget.com/2013/02/25/samsung-safe-with-knox/

May 2013 - Samsung Knox gets official DoD approval for government use

http://www.engadget.com/2013/05/03/samsung-knox-gets-official-dod-approval-for-government-use/

Sept 2013 - Samsung opens up Knox security platform to all consumers - HAPPY people!

http://www.engadget.com/2013/09/04/samsung-opens-up-knox-security-platform-to-all-consumers/

http://www.engadget.com/2013/09/04/lookout-knox/

So it is a 'Feature' - we still should have the option to say 'No thanks'.
[Galaxy S 4 General] Ryanrioz:
darn it.. Samsung :x :screwy::screwy:

Send my E-960/S4 LTE/N2 GSM and /Galaxy Y to xda
[Galaxy S 4 General] mcduck1:
Does knox warranty change the device status to unofficial? If so, this will also break Miracast/screen mirroring (HDCP fails) permanently until one is able to reset the counter.
[Galaxy S 4 General] Mackovich:
The problem is... Are you willing to take the risks?

I'm not!!
[Galaxy S 4 General] beastobadness:
If you are talking about UV/OV then 'No' but if you are talking about rooting then 'Yes'. I have taken the risk (and I am prepared for the consequences) but I did nothing different to what I was doing before Knox appeared. I went to MH8 and rooted like I normally do, then realized the Knox flag/efuse was triggered. And then thought I wish that I had been informed by samsung because I may have stayed stock (last chance, sort if thing)....

(Me stay stock...ha...that's a laugh! I have shelled out too much money on root apps in playstore for that:D)
[Galaxy S 4 General] Swizzy88:
I just got my device back from repair. I had the 'bloated battery' issue. I got a new battery and the latest firmware with the KNOX flag. I'm not happy.
[Galaxy S 4 General] Mackovich:
I understand the feeling.

I just meant for any people out there if they were willing to root and get their know warranty void and still try to benefit from after sale service...
[Galaxy S 4 General] Nessuno1:
Thanks for this informative thread about this "issue".

There is something I fail to understand though. From my reading (and from the quote in the OP particularly), konx enabled firmwares start with MH1, and you can see that by going to the Odin mode and there you can see 2 new lines about knox stuffs.

Here is the thing : I'm in MH1 (installed via Odin), and there is

no

such "knox" line as you can see in the attached pictures.

I've always used Odin right from the beginning, only for stock firmwares, never rooted, nor installed anything custom. At the moment I happen to have a carrier branded firmware (Orange) because...oddly enough it was the first one to be available then.

So does it really start with MH1 ? Or is it something else that "saves" me from this knox thing ?
[Galaxy S 4 General] beastobadness:
Well in that case yes I am a risk taker but there is a point I won't go beyond! I mean if I was doing something extreme and erroneous to the device (which I am not) then fair enough, I would not take advantage of after sales repair. But I would hope Samsung would honour the hardware warranty for standard repair issues even with the Knox warranty void triggered, afterall it was put in place for business use and BYOD which I have no use for!

---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------

Quote me if I am wrong but I think MH1 introduced the new bootloader but samsung didn't activate Knox till the next firmware came available ie MH8 etc!
[Galaxy S 4 General] cmptrmavn:
Thanks for confirming, much appreciated. I know this is technically the i95XX forum but just to record my experiences with a freshly purchased AT&T SGH-i337 on the MF3 firmware, I went ahead and rooted using the new SDcard method, installed safestrap and everything is a go.
[Galaxy S 4 General] spinky360:
KNOX OFF !!!

eMMC Chip - AFEABB

For this moment ... this is the only solution. Is not a solution suitable for all user's.

Anyhow .... my opinion i will bee with KNOX ...
[Galaxy S 4 General] donalgodon:
As far as I can gather, that's the case, because I (unknowingly) updated via MH1 via Odin, and I did not go to any newer firmware via Odin, and I still have nothing about Knox in my Download mode screen.
[Galaxy S 4 General] Oniyuri:
Ok just to reconfirm; the MH+ ROMs in the dev section are safe, correct?

Me and my Mr are still running stock (which is highly unusual for me). I'm currently on MG4 and he's on MEA.
[Galaxy S 4 General] donalgodon:
I can't confirm that, but I do know that MH1 did not show Knox in Download mode. AS the previous poster indicated, it may be that the MH1 is a Knox bootloader, but that it wasn't activated until MH8.

Can anyone confirm whether this is true? IF it is true, then it means that MH1 locks you to that bootloader and nothing older.
[Galaxy S 4 General] dingila:
Wher is this MH1? Give me link for daonload please! ;)
[Galaxy S 4 General] MaKTaiL:
Guys. What determines if the firmware has Knox bootloader or not is the B or D letter right before the MH*. B stands for the old batch of firmwares, D is the new batch with Knox bootloader.

I9505XXUBMH1 - Old bootloader

I9505XXUDMH6 - Knox bootloader
[Galaxy S 4 General] millionsuns:
i'd like to ask

my note 3 is on MI1, and if i root it then the samsung knox flag status won't be change ?

is that true ?

because i'm not downgrade it to the old bootloader or without a secure bootloader

am i right ?
[Galaxy S 4 General] Oniyuri:
Thanksfor this tidbit of info. Both of our phones are still B and I've taken the steps to cut off the ability to get OTAs.
[Galaxy S 4 General] Syraxius:
I have a SM-N9005 and I'm on N9005XXUBMI6.

It has the KNOX flag in Download mode.
[Galaxy S 4 General] oj_alltagshacks:
I just received a new S4 here in Germany. When I turned it on, I immediately activated Download Modus. It shows Knox Void Warranty 0x00. So far, so good.

Now, I read through this thread and am not sure, if I understood it correctly.

1. Does the fact above mean that I cannot root/install a custom ROM (I would like to install Google Edition) or does this just mean that if I do so, there will be no warranty from Samsung any longer?

2. If it is still possible to install a Custom ROM (which is, what I assume), is it also possible to go back to the stock ROM (I know that this will not reset knox warranty void status, but I don't care) in case I want to sometime?

Many thanks in advance

OJ
[Galaxy S 4 General] Chrisstian:
I have also Note 3 (N9005 model, LTE) rooted with current CWM method.

And unfortunately, KNOX flag has increased to 0x1...
[Galaxy S 4 General] Mackovich:
Did the flag change upoon installing CWM or upon rooting through CMW ?
[Galaxy S 4 General] Stanlehh:
have this as well after the latest firmware update, shucks :(

I9505XXUDMH6 - Knox bootloader
[Galaxy S 4 General] ryanbg:
It has yet to be discovered.
[Galaxy S 4 General] lorenzo122:
We need someone to write this exploit?
[Galaxy S 4 General] phr3ncj:
[MENTION=624762]thatrunks[/MENTION] can u copy here all lines printed in download mode now that has been resetted by sammy? exynos or snapdragon?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 General] s14sh3r:
[MENTION=624762]thatrunks[/MENTION] Are you sure they didn't just give you another phone?
[Galaxy S 4 General] lorenzo122:
He said "i9505", snapdragon 100%.
[Galaxy S 4 General] MemoryController:
Does anyone have Galaxy S4 schematics + memory map? Plus what the hell is at 0x91000000 ? I see references to it that secure boot state is controlled by whether the value there is 0x12345678, 0x43218765, 0x87654321 or something else. Hmm maybe it's set there by SBL3? Since I see QUALCOMM SECUREBOOT: NON-SECURE BINARY being printed after comparison.... Would be great if someone with extra-knowledge or jtag hooked up could chime in. Or if someone has JTAG pinout. If I could get a i9505 for parts and hook it up to my jlink then we could work better on this.

EDIT: I thought I could update this post with some info.

set_tamper_fuse_cmd is at aboot+0xbaf0 AND

get_tamper_fuse_cmd is at aboot+0xbb4c

set_tamper_fuse_cmd is called at one place and the get_... at 2 places, with different arg. It's not the vanilla get_tamper_fuse_cmd found in LK source, as that one doesn't take any args.

I am starting a new thread with only technical info, as it will make it easier to attract devs that know much more about this stuff than me.
[Galaxy S 4 General] Surge1223:
Theres not much at 0x91000000, though there is some obscure data, what is it that you were expecting there?

Link me to your thread and ill post data on whats at 0x91000000 etc.
[Galaxy S 4 General] Brooklynsour:
[MENTION=4939386]Surge1223[/MENTION] I sent him pm, link to your thread not sure if he seen it alrdy just tryna get as many "knowledgeable" ppl on board to assist ya
[Galaxy S 4 General] MemoryController:
http://xdaforums.com/showthread.php?t=2644865

I used viewmem and all I got was zeroes. Probably it's remapped before the kernel executes.
[Galaxy S 4 General] thatrunks:
Unfortunately I got some bad news. This morning my colleague dropped my phone in the water, accidentally... sorry guys...

So I got nothing now. It is sent for repairs.....

No I was sure it was mine. Same IMEI number, screenprotector and my custom backcase and they told me it was the same phone.

I don't know if I can believe them... that is something you will never know
[Galaxy S 4 General] MemoryController:
Wow I find that hard to believe as I can clearly see the call to TrustZone to blow the fuse in the bootloader code. If they aren't lying then it's a clusterf-.
[Galaxy S 4 General] bungadudu:
Lol

Of course your phone will look like before.

Would've you expected they will retain your screen protector and backcase?

It's very possible the swapped the motherboard...

Only way to make sure they didn't, is to first make a small sign on a knoxed motherboard before sending it in service, and check for the sign after they give it back to you with knox 0x0.
[Galaxy S 4 General] thatrunks:
O that is handy indeed, I'll keep that in mind :).

Yes, I asked them if they swapped the motherboard and they said not. But then again, I don't know if I can trust them...
[Galaxy S 4 General] malybru:
Mod Edit

Thread cleaned

Just another quick reminder for those who did not see it last time:

I am going to keep this thread clean for the Research only.

All other knox questions go to the Q&A THREAD

Thank you

malybru

Forum Moderator
[Galaxy S 4 General] xclub_101:
You can still have both - imagine that you have the knox flag not as a direct bit stored in a single place (qfuse) but instead as two bits that have to match - one in qfuse one one in some other place, and the "warranty void" is reported when those no longer match. But of course if you are Samsung you do not want things to be that simple, so you might want to make it on more than one bit and also the match to be more "one way" so when you have one bit blown you do not automatically know what value to write in the matching copy (I can think of many ways to do it based on stuff like public-key cryptography and ID-numbers that are unique to each CPU or chipset).
[Galaxy S 4 General] JaCh0o:
Useful security hint for jTag

maybe thats useful ?

for jtag users... (i do not have jtag)

http://www.anyclub.org/2012/05/how-to-enabledisable-secure-boot.html
[Galaxy S 4 General] timberwolf60:
Thank for th information. But due to cost and technical knowledge involved which was not practical to a user like me. The better way for me was sold my i9505 and i9506 and get Sony z1 which was more enjoyable than Samsung phone. Knox can't be solved and warranty definitely void in Singapore. Cheer!

Send from my C6903 using TapatalkPro

my Sg device: Z1 rooted136 ROM by NUT with 2.7.92 dualrecovery, mod by GavityBox 2.9.6. Samsung S2 standby for Z1 when Z1 no power.
[Galaxy S 4 General] Nessuno78:
Gonna send mine in to get it 0x0 and sell it (getting a upgrade from my profider)

Note 3 or il just wait for the S5.

Will post here if i manage to find out whats up or if they will tell me some info about how they reset it.

Next to that il mark some parts on/in my phone with an uv marker.

so we can see if they did a software trick or swapped parts.

Il keep you guys posted.
[Galaxy S 4 General] bungadudu:
If you're to uv mark something just try on the sim card slot/micro SD slot.

Fingers crossed!
[Galaxy S 4 General] Nessuno78:
I will make some photo's later on what i will be marking.

and im not gonna send it it but gonna pass by them.

Mby i can bribe them :angel:

If already had my note 2 compleetly appart so i know what to mark :P

Id rather just see what they would do to my phone first hand hahaha.

Ah well like i said il keep you guys posted.
[Galaxy S 4 General] latouffe:
Any news? :)
[Galaxy S 4 General] euros60:
Samsung can't void our warranty

I found that Samsung cant void our warranty even if after a change in the firmware / software part of our terminal : http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31999L0044:FR:HTML this european directive from 25 May 1999 (1999/44/CE) said clearly that the warranty can't be void by the constructor if the buyer change the terminal's system / boot / frimware. But it's juste for Europe :/
[Galaxy S 4 General] pitastrudl:
nothing new....

Sent from my GT-I9505
[Galaxy S 4 General] Ghorin:
I don't see what you say in the text. Whart part of it is it please ?
[Galaxy S 4 General] bungadudu:
Because there isn't.

You really think in 1999 they were thinking about rooting and changing phone's firmwares? :)) and would put that in an EU directive? :lol:

Same old crap regurgitated every now and again by people who have no idea about the legal system.
[Galaxy S 4 General] Ghorin:
Oh i dis notre see the year 1999 !!! You are right man :)
[Galaxy S 4 General] EclipseX:
And? The law didn't change after 1999

Enviado do meu GT-I9505 através de Tapatalk