What are the chances of the device getting rooted then? I noticed the GS4's bootloader was locked but it was able to be rooted. I don't need custom ROM's just root. Any answer would be appreciated.
Thanks!
Bump
I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.
mircury said:
I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.
Click to expand...
Click to collapse
Is the T-Mobile one has att LTE band ?
According to the FCC lab report, yes it does.
mircury said:
According to the FCC lab report, yes it does.
Click to expand...
Click to collapse
But there is no real world confirmation yet.
daraj said:
But there is no real world confirmation yet.
Click to expand...
Click to collapse
That is correct. No one knows for sure yet. All we know is that it has the correct radio and bands. Hopefully it will work the same as the S4.
After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.
None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.
designgears said:
After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.
None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.
Click to expand...
Click to collapse
Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?
daraj said:
Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?
Click to expand...
Click to collapse
As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable
With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.
I would assume we can flash boot/recovery/modem.
designgears said:
As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable
With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.
I would assume we can flash boot/recovery/modem.
Click to expand...
Click to collapse
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
daraj said:
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
Click to expand...
Click to collapse
Ya, it seems like the kernel is encrypted, I have been unable to rip it apart with any current methods.
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
daraj said:
Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)
Click to expand...
Click to collapse
Pikezer1337 said:
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
Click to expand...
Click to collapse
Yup..if the old root exploit still works (if it does not, then pretty much toast). The bootloader *cannot* be replaced yet (even in S4), if you were lucky and had the earlier bootloader then you could "loki" run custom roms/recoveries. Otherwise the only option appears to be the "kexec" type method (safestrap), yuk..get one without a bootloader lock (hoping T-MO does not lock it and allows unsigned kernels and recoveries)..
Although I don't understand why ATT would this, the above methods for S4 has made people who didn't understand the process fully to go back to Samsung//BB service centers to reflash the stock f/w.
Pikezer1337 said:
So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?
Click to expand...
Click to collapse
Actually getting root is going to be difficult. An unpatched exploit will be needed. Rom's and kernels will be the extremely difficult part. Samsung's credibility is on the line for a secure business solution with KNOX so you better believe they are going to make it hard if carrier's like ATT decide to lock down their devices like they have.
Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.
Pikezer1337 said:
Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.
Click to expand...
Click to collapse
Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?
daraj said:
Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?
Click to expand...
Click to collapse
I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled. There is already a dev working on striping knox out in the dev section.
Geez, it's just hard imagining a phone like the Note 3 never having root access. But hey if that's what happens, I guess there's nothing you can do.
mircury said:
I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled.
Click to expand...
Click to collapse
That's correct. If a bootloader is unlocked and you ODIN flash a custom recovery and install su and push super su. The kernel is not SELinux permissive, then we just need to wait for the source drop, compile a new kernel. The important thing is the bootloader unlock and knox security allowing unsigned kernels and recoveries. From the S4 T-MO thread it appears that the T-MO version allows that..so it will not be a big deal..ATT ones of course you are pretty much toast.
Related
on my stock mj7 9005 i have secureboot:none
does this mean my kernel is unlocked?
gazeddy said:
on my stock mj7 9005 i have secureboot:none
does this mean my kernel is unlocked?
Click to expand...
Click to collapse
That is a little strange, mine is ENABLED (CSB) - can you post a picture with all the text from download mode?
xclub_101 said:
That is a little strange, mine is ENABLED (CSB) - can you post a picture with all the text from download mode?
Click to expand...
Click to collapse
photo taken just uploading now
gazeddy said:
photo taken just uploading now
...
Click to expand...
Click to collapse
That is weird, never heard of S2, T2, R2, A2 and P0 - I wonder if that is some early engineering bootloader. In that case it might be interesting to have it saved so as to research more on the Knox stuff.
What region/CSC is that? Anything specific (carrier or similar)? I guess you are not rooted? If you are in no hurry for that I would suggest to wait 2-3 more days and maybe somebody like Chainfire might drop a private message.
xclub_101 said:
That is weird, never heard of S2, T2, R2, A2 and P0 - I wonder if that is some early engineering bootloader. In that case it might be interesting to have it saved so as to research more on the Knox stuff.
What region/CSC is that? Anything specific (carrier or similar)? I guess you are not rooted? If you are in no hurry for that I would suggest to wait 2-3 more days and maybe somebody like Chainfire might drop a private message.
Click to expand...
Click to collapse
it was o2u branded but i debranded and upgraded to mj7
gazeddy said:
it was o2u branded but i debranded and upgraded to mj7
Click to expand...
Click to collapse
and no im not rooted and yes i want root.
but a few more days wont hurt
gazeddy said:
and no im not rooted and yes i want root.
but a few more days wont hurt
Click to expand...
Click to collapse
Hmm, if you still MUST root and you can't wait any longer and nobody else offered any better advice - I think in the process you should at least try a few things.
For instance you could test if SECUREBOOT: NONE will let you downgrade the bootloader - if you can install with Odin (preferably a slightly older one) a stock ROM like BTU MI7 (after completely wiping cache and everything else) then at least your immediate problem would be solved (even if the SECUREBOOT would be re-enabled - URDLV should work). Another option might be to downgrade to your original O2U firmware. In either case it would be interesting to see how SECUREBOOT and the S, T, R, A and P flags would change.
But obviously there is no warranty of any kind that something bad couldn't still happen
xclub_101 said:
Hmm, if you still MUST root and you can't wait any longer and nobody else offered any better advice - I think in the process you should at least try a few things.
For instance you could test if SECUREBOOT: NONE will let you downgrade the bootloader - if you can install with Odin (preferably a slightly older one) a stock ROM like BTU MI7 (after completely wiping cache and everything else) then at least your immediate problem would be solved (even if the SECUREBOOT would be re-enabled - URDLV should work). Another option might be to downgrade to your original O2U firmware. In either case it would be interesting to see how SECUREBOOT and the S, T, R, A and P flags would change.
But obviously there is no warranty of any kind that something bad couldn't still happen
Click to expand...
Click to collapse
i have write protection enabled though
gazeddy said:
i have write protection enabled though
Click to expand...
Click to collapse
I might be confusing things but my feeling is that write protection means that certain places can only be written by code in bootloader itself (so in Odin, not in recovery, or any rooted ROM). And that was implemented with a software one-way / hardware 2-way switch, that gets to a "write enable" position after a hardware reset, but is set to "write protected" before the code jumps to the next stage after bootloader. If that was not possible then no update of the bootloader itself would have been possible.
My concern is not that much about writing the bootloader itself (which some people have anyway reported by means of JTAG-like methods) but instead about what the older bootloader would do after the next hardware reset - seeing the corresponding stock kernel and recovery would be fine, but the main question remains about what it will think about the combination S2, T2, R2, A2 and P0 + SECUREBOOT:NONE.
My S4 has the original firmware (MDL) and I have since installed a custom recovery (the loki method). I am now running GoldenEye 4.3, which is based off the Internation S4. I love it. I love what my phone can do. Anyway, I downloaded triangle away and it says the binary is official and the counter is 0. I did not see Samsung Knox Warranty 0x0 or 0x1 anywhere. Would I have this if I did the original OTA update to 4.3 from AT&T? I'm guessing its best never to upgrade and stay far away from the knox crap. So much for the Galaxy S5 then. ):
Why did Samsung ever have to implement the Knox 0x0 crap? If its so important to them voiding people's warranties, then why didn't they originally do it when the S4 launched?
As of right now, is my bootloader knox free, since I have a 4.3 rom on it? Would triangle away work if I ever needed to send it in?
Why is there a different root method or custom recovery for each firmware version on the i337?
MattMJB0188 said:
My S4 has the original firmware (MDL) and I have since installed a custom recovery (the loki method). I am now running GoldenEye 4.3, which is based off the Internation S4. I love it. I love what my phone can do. Anyway, I downloaded triangle away and it says the binary is official and the counter is 0. I did not see Samsung Knox Warranty 0x0 or 0x1 anywhere. Would I have this if I did the original OTA update to 4.3 from AT&T?
....With pushed OTA the Bootloader would add a Knox warranty flag to the download mode screen.
I'm guessing its best never to upgrade and stay far away from the knox crap. So much for the Galaxy S5 then. ):
Why did Samsung ever have to implement the Knox 0x0 crap?
....Military, Govt. & Corporate sales. The consumer warranty part is just gravy for them.
If its so important to them voiding people's warranties, then why didn't they originally do it when the S4 launched?
As of right now, is my bootloader knox free, since I have a 4.3 rom on it? Would triangle away work if I ever needed to send it in?
....Afaik no. Recent postings indicate it's not 4.3 compatible. Check your. ROM thread for Knox status.
Why is there a different root method or custom recovery for each firmware version on the i337?
Click to expand...
Click to collapse
...Not the firmware as much as model specific differences force incompatability where it exists.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pc103 said:
...Not the firmware as much as model specific differences force incompatability where it exists.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
So, not every S4 will have the knox counter?
MattMJB0188 said:
So, not every S4 will have the knox counter?
Click to expand...
Click to collapse
For the record: Triangle Away is not compatible with any locked bootloader and I don't believe it resets KNOX yet anyways. I think that if you have loki exploit you can use it, but I'm not entirely sure. It's only for the flash counter anyways.
The reason root and recovery methods are different is because with each new firmware Samsung patches the old security flaws that let us have root and recovery in the first place. I don't know if that's at their discretion or at the carrier's request (the locked bootloaders are at carrier request and Samsung must update the security on them to protect their business interests).
Not every S4 gets the KNOX counter, only those with the bootloader from the 4.3 update.
DeadlySin9 said:
For the record: Triangle Away is not compatible with any locked bootloader and I don't believe it resets KNOX yet anyways. I think that if you have loki exploit you can use it, but I'm not entirely sure. It's only for the flash counter anyways.
The reason root and recovery methods are different is because with each new firmware Samsung patches the old security flaws that let us have root and recovery in the first place. I don't know if that's at their discretion or at the carrier's request (the locked bootloaders are at carrier request and Samsung must update the security on them to protect their business interests).
Not every S4 gets the KNOX counter, only those with the bootloader from the 4.3 update.
Click to expand...
Click to collapse
So when the AT&T S4 received its official OTA update from AT&T, did it include knox?
MattMJB0188 said:
So when the AT&T S4 received its official OTA update from AT&T, did it include knox?
Click to expand...
Click to collapse
It did. With the warranty bit newly added.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pc103 said:
It did. With the warranty bit newly added.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Wow. What a shame. It looks like they are doing everything to stop custom roms and root. After the loki method, it got really hard. Seems like more devices would be bricked now, than they would before.
I am wondering why they are cracking down so much now. The AT&T Galaxy S2 (i777) and S3 had unlocked bootloaders and huge development communities.
+1 now many are thinking of ditching their carriers & mfr in favor of costlier, but mod friendlier alternatives truer to Android's progressive core concept.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pc103 said:
+1 now many are thinking of ditching their carriers & mfr in favor of costlier, but mod friendlier alternatives truer to Android's progressive core concept.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, but its still never the same with another carrier's device. For example, I used the T-Mobile Note 3 on AT&T and the experience was not so great. Sure, I had custom recovery and root, but it had that knox warranty thing. It also struggled tremendously holding onto an LTE signal. The overall signal was poor.
Purchasing the international S4 comes with the trade off of loosing LTE. I am hoping with the S5, Samsung includes all major LTE bands with it, so those of us who want to modify our devices can get AT&T LTE.
Hello all,
I searched the forums round and round, and couldn't find my answers so I hope you will be able to help me out.
i'm looking for a new phone and decided I want to go with the S5. that was before i learned about KNOX and it's wonderful ways.
i'm a heavy modder, who will most definitely use a custom recovery and ROM/kernel.
my questions are:
1. would it be possible to flash a custom recovery / rom / kernel / modem despite KNOX being preset?
2. other then getting this 0x1 and voiding my official warranty, are there any other result to this? will something not work?
3. assuming I get an unlocked international phone, is there any need to mess/change my FW? or is that just part of guides for rooting without tripping KNOX ?
Basically, I want to be sure that I could do whatever I want to the phone without getting stuck or turning it unusable because of KNOX. my current phone is a Nexus 4 and it has been heaven. I want to preserve this feeling
thanks for the help guys, appreciate it!
Did you tried Towelroot method for rooting your device? I heard that doesn't trigger knox..
I would imagine my rooting the phone is the least of my worries.
as far as I know - and this is one of my questions - flashing a custom recovery and or rom will 100% trip KNOX.
not that I care, I just need to know if this is true..and my other questions as well
thanks!
A brief answer
If you - as you say "i'm a heavy modder" Samsung phones are not for you
I've heard tales of people having issues flashing modems when knox is triggered. I have not checked that out for myself Joe have I searched any further into the matter.
I plan on breaking knox soon though because screw knox.
Sent from my SM-G900F using Tapatalk
chainbr3ak said:
A brief answer
If you - as you say "i'm a heavy modder" Samsung phones are not for you
Click to expand...
Click to collapse
This answer really worries me to be honest.
could you elaborate?
I don't really care about KNOX, and as long as I can mod away and jump back and forth between modems/roms/kernels - I don't care for the warranty.
If indeed there is truth in the matter, and modem flashing will become a problem if KNOX is tripped, then this would be a deal breaker for me on this phone.
anyone care to add more info here?
Amornik said:
This answer really worries me to be honest.
could you elaborate?
I don't really care about KNOX, and as long as I can mod away and jump back and forth between modems/roms/kernels - I don't care for the warranty.
If indeed there is truth in the matter, and modem flashing will become a problem if KNOX is tripped, then this would be a deal breaker for me on this phone.
anyone care to add more info here?
Click to expand...
Click to collapse
You can, but you will always have problems like network, connection,calls, bugs and so on
Samsung devices do not provide the old pleasure as previously
Knox killed freedom of developers and people who like customizations
I would really appreciate an answer from someone who knows for sure.
does tripping KNOX disables the option to upgrade/downgrade the modem?
Amornik said:
I would really appreciate an answer from someone who knows for sure.
does tripping KNOX disables the option to upgrade/downgrade the modem?
Click to expand...
Click to collapse
No, KNOX tripping is only at the moment a warranty void solution for samsung. its like the flash count flags.
basically if you trip knox. you're already in it. you do what you want
Amornik said:
I would really appreciate an answer from someone who knows for sure.
does tripping KNOX disables the option to upgrade/downgrade the modem?
Click to expand...
Click to collapse
I bought my phone with ANCE firmware and the KNOX was tripped in the first hour by CF-AutoRoot. Now I'm on ANG2, flashed with Odin and the modem is updated correctly.
Dark_Avenger said:
I bought my phone with ANCE firmware and the KNOX was tripped in the first hour by CF-AutoRoot. Now I'm on ANG2, flashed with Odin and the modem is updated correctly.
Click to expand...
Click to collapse
Now i'm a bit confused when you say you upgrade the FW, you mean the modem baseband, right ?
Amornik said:
Now i'm a bit confused when you say you upgrade the FW, you mean the modem baseband, right ?
Click to expand...
Click to collapse
Exactly, but with full stock image flush (including bootloader). The full stock tar.md5 form sammobile includes the modem/bootloader/rom. I think that the important thing is to have a modem which is compatible with the bootloader (same version). Didn't try to mix different bootloader/modem(baseband) versions.
Tripping KNOX will only disable the feature which allows you to store some data on a encrypted part of the device (Mostly comercial use) when KNOX is tripped any data stored on the 'special' partition is destroyed.
So there are only 2 things that will be affected, your warranty (Not a problem in Europe) and the special partition that I explained earlier.
Sent from my SM-G906S using XDA Premium 4 mobile app
Thanks guys, excellent replies !
So...I did it !
I went and bought a brand new S5, and tripped KNOX within the hour. Man, did it feel sooo good !
custom recovery up, rom up, here we go!
Good day.
Even though i will lose warranty, i'm thinking about rooting my Exynos Galaxy S8.
From what i have read in some post, Samsung pay, SHealth and secure folder will stop working with knox tripped.
Don't care about Samsung Pay, as it is not available in my country, but the other two apps, is it possible to make them work again somehow? Maybe with Magisk?
Thank you.
As far as I know there is a way to make it seem like Knox is enabled using it but I'm not 100% sure
On batman Rom s health still works fine . You have no chance of using secure folder with root
MGfusion said:
As far as I know there is a way to make it seem like Knox is enabled using it but I'm not 100% sure
Click to expand...
Click to collapse
Custom roms and kernels fake the Knox counter it in actuality it is till tripped
sofir786 said:
Custom roms and kernels fake the Knox counter it in actuality it is till tripped
Click to expand...
Click to collapse
Ah I see, my fault
Just the title
EarthMonster said:
Just the title
Click to expand...
Click to collapse
rooting a Samsung phone almost always ‘trips Knox’
(permanently blows an e-fuse) and voids the warranty
dezborders said:
rooting a Samsung phone almost always ‘trips Knox’
(permanently blows an e-fuse) and voids the warranty
Click to expand...
Click to collapse
Even using magisk + custom recovery? I've heard things like Netflix don't usually work with root but this way it does.
U cant have your cake and eat it too.
Knox being broken shouldn't void warranty under EU consumer laws. But you best do your due diligence and not just take my word for it.
Sent from my EVR-L29 using Tapatalk
EarthMonster said:
Just the title
Click to expand...
Click to collapse
The answer is no. At least nothing publicly available.
Theres plenty of USA s10+ owners who would be all over if it was possible since we cant even unlock the BL which means stuck waiting around for alternate root methods
dezborders said:
rooting a Samsung phone almost always ‘trips Knox’
(permanently blows an e-fuse) and voids the warranty
Click to expand...
Click to collapse
This is not true. It depends on "how" you root. Finding a way to root without unlocking the BL and using custom boot/recovery usually does not trip Knox. Of course these methods are becoming more and more rare. For example I rooted s8/s8+ USA variants back when they launched which was using a few vulns, certain signed samsung firmware and system root and Knox was fine. They also can root USA Note 8 devices using other means without tripping Knox. I also rooted USA N9 on combo firmware without tripping knox/warranty bit.
Heck even unlocking bootloader sometimes doesnt trip Knox until you actually flash custom firmware. Typically if you use Magisk root or TWRP on an unlocked bootloader then you definitely will trip Knox. Point is that it's possible to root without tripping knox as it has been done many times over the years. Nowadays though most people just buy unlockable variants so it's really all anyone sees or knows about most the time.
EarthMonster said:
Even using magisk + custom recovery? I've heard things like Netflix don't usually work with root but this way it does.
Click to expand...
Click to collapse
Lol
Seeing as how magisk patched firmware and TWRP specifically require an unlocked BL which is exactly what trips knox your answer is no. That will 100% trip your knox flag.
As far as Netflix (and many other companies) they are always trying to be as secure as possible. Theres many who find ways to get around those types of issues. It's just a cat n mouse game sometimes i.e devs get it working then Netflix breaks it again then users find a way to get around it etc etc
elliwigy said:
This is not true. It depends on "how" you root. Finding a way to root without unlocking the BL and using custom boot/recovery usually does not trip Knox. Of course these methods are becoming more and more rare. For example I rooted s8/s8+ USA variants back when they launched which was using a few vulns, certain signed samsung firmware and system root and Knox was fine. They also can root USA Note 8 devices using other means without tripping Knox. I also rooted USA N9 on combo firmware without tripping knox/warranty bit.
Heck even unlocking bootloader sometimes doesnt trip Knox until you actually flash custom firmware. Typically if you use Magisk root or TWRP on an unlocked bootloader then you definitely will trip Knox. Point is that it's possible to root without tripping knox as it has been done many times over the years. Nowadays though most people just buy unlockable variants so it's really all anyone sees or knows about most the time.
Click to expand...
Click to collapse
What you say is true anything is “possible”
However as the OP is on the O2 network he has an Exynos chipset.
Is it currently possible to root an Exynos S10+ without tripping Knox ?
I stopped rooting about 5 years ago so don’t know of a way right now
dezborders said:
What you say is true anything is “possible”
However as the OP is on the O2 network he has an Exynos chipset.
Is it currently possible to root an Exynos S10+ without tripping Knox ?
I stopped rooting about 5 years ago so don’t know of a way right now
Click to expand...
Click to collapse
ive never owned one.. i imagine most just unlock bl.. but from wat my sources tell me there is easy root on exynos without tripping knox.. I am not able to provide details tho as they are private methods.. they use it for business and such apparently so take it with a grain of salt lol
exynos are notoriously known to b a lot easier to root than SD variants
Sent from my SM-N976V using Tapatalk