So I can find the stock firmware and flash it on to my tablet, correct?
But that will not untrip the Knox , correct?
Correct
Related
so, i'm reading this forum for 2 days now and i didnt get any answer.
i installed stock XXUBMJ7 (4.2.2) firmware with odin. Before i new anything about knox and stuff, I rooted, and get knox waranty void 0x1.
then i installed again XXUBMJ7 firmware with odin and didnt root again. (because i hate warnings at the boot). i still have 0x1.
now, I have two questions and i need simple answer.
1. Can I install newer stock (4.2.2) XXUBMK3 firmware with odin? will it work?
2. can i root my installed stock XXUBMJ7 firmware again and then install [CWM][ROM]GT-I9195XXUBMK3 deodexed, with no knox bootloader? will this work?
thanks
anyone?
vesolec1 said:
anyone?
Click to expand...
Click to collapse
U can install new one no problem i think .
But your Knox flag will remain so u can not reset it
Hello,
I want to ask or confirm something for me.
Now i am on stock 4.3,not-rooted,Knox flag=0
If i decide to ignore this KNOX flag and warranty i can :
Root it - using Kingo root Correct?
Flash custom recovery - Witch one ,because i read that some have problem with custom.
Flash custom ROM- Phoenix (let say). Correct?
After rooting i will be able to disable KNOX ,witch after flag 1 will start showing some notifications. Correct?
After KNOX flag 1 the only thing i am not be able to use is KNOX (application) -Correct? I don't use it at all.
Thanks for every respond!
P.s
Is there any other way to flash bootloader except Odin? And if yes HOW?
Asking because :
KNOX is flag in the Bootloader. My idea is - Flashing old bootloader trough Odin-not possible.
BUT if the is other way(not odin) to flash it until KNOX is 0,maybe later it will stay 0 when stock is flashed trough ODin
I tryed on mine 4.3 and knoxed it anyway. CF root seems to not work properly anymore.
But who gives a ****. Knox is justa bunch of crap.
I have my P601
If I flash another country (P601) official firmware via PC ODIN
will it trip KNOX to 1 ?
It shouldn't, no. However if the 10.1 is anything like the Note 3 then you have to be careful about bootloaders...
If you are trying to downgrade the software to a lower firmware version to root with URDLV then you can in fact trigger Knox as the bootloaders don't match and you can't go to an older firmware...
Hi guys I am new to this tablet so any advice but be appreciated.
If i update to kitkat I am told the knox security feature would be installed too.
What if I leave my note 8.0 on 4.2 and root and use custom roms and then if I decide to unroot and flash kitkat, would knox be triggered due to historic custom roms?
fazzxx said:
Hi guys I am new to this tablet so any advice but be appreciated.
If i update to kitkat I am told the knox security feature would be installed too.
What if I leave my note 8.0 on 4.2 and root and use custom roms and then if I decide to unroot and flash kitkat, would knox be triggered due to historic custom roms?
Click to expand...
Click to collapse
Pretty sure flashing a custom recovery will trip knox. No way around it. http://forum.xda-developers.com/showthread.php?t=2800290
Ok thanks what if I just root and not flash a custom rom, would this trigger the knox?
fazzxx said:
Ok thanks what if I just root and not flash a custom rom, would this trigger the knox?
Click to expand...
Click to collapse
It depends on the rooting method you use. The one I used to root 4.4.2 after I updated via Odin was Chainfire's CF-Auto-Root and that tripped KNOX because it installs an unsigned (by Samsung) custom recovery temporarily before re-flashing the stock version.
I've never used Kingo but they claim to be able to root the Note 3 without tripping the KNOX flag so their method using an Android vulnerability to gain temporary root might work for the Note 8.0 as well.
My suggestion would be to use these forums and Google to research all the current methods for rooting the Note 8.0 and make sure there are users who have done it successfully with the KitKat boot loader installed and not tripped the KNOX "warranty" indicator.
Based on the KNOX articles I've read it appears that flashing, or even booting, an insecure kernel can set the eFuse switch which is said to be "impossible" to reverse, so flashing custom kernels and ROM's is out even if you can get root with the stock ROM without tripping the indicator.
I can understand the requirement for KNOX in high security environments but automatically voiding the warranty is just encouraging users to brick their devices in ways that prevent the KNOX flag from being accessed. Perhaps Samsung's position is that once the eFuse flag is set even their service centers cannot reverse it so the device is not able to reconditioned and sold since a tripped KNOX flag also disables some security features in the stock ROM.
Edit: I just read your OP again and if you don't flash the 4.4.2 (KitKat) bootloader and root with CF-Auto-Root you should be fine, even flashing custom kernels and ROM's, and still go back to a completely stock configuration using Odin to install the stock 4.2.2 ROM and TriangleAway to reset the flash counter. AFAIK there is no check of any historical data when the KNOX enabled 4.4.2 bootloader is installed but I would make sure that TriangleAway has successfully reset the flash counter before upgrading just to be safe.
ramjet73
I have a Note 3 and im trying to figure out the process of rooting without tripping the Knox Counter. I rooted my Note 2, years ago and has been awhile. Also like to know is there a "triangle away" method to reset the counter.
Model: SM-900T
Android: 5.0
Baseband: N900TUVUFOL1
Kernel: 3.4.0-6005498
Knox: 2.3
Thanks in advance
As far as I know, there is no way to root without tripping Knox.
If the phone is not under warranty, tripping knox should not be an issue. I have tripped Knox on a few phones and have never had an issue.
I asked the same question a while back, and only just 2 days ago rooted my SM-N900T knox 0x0. Asked: Here.
To achieve root on the note 3 without tripping knox you must downgrade from the Lollipop firmware OB6, or FOL1 to NE6 using PC Odin.
Once downgraded to NE6 download and use TowelRoot. This will unlock root without tripping knox, NE6 was the last vulnerable firmware for towelroot on the t-mobile note 3.
Make sure you are flashing official t-mobile firmwares only for kitkat/lollipop when using PC odin.
Flashing any custom recovery, kernal, rom, bootloader, or no longer supported android version (4.3 jellybean) will trip knox.
You can use sammobile to get official firmwares, or if you're risky there are likely download mirrors scattered through the internet.
Once you're rooted on kitkat NE6, to get back to Lollipop and keep root you'll need Mobile Odin Pro to flash FOL1 with the latest Super SU Zip v2.46. (instructions first page of this thread: Here.)
Rooting seems to require some gonads and research first.
When using PC Odin I left options default (Auto Reboot and F. Reset Time).
When using Mobile Odin Pro (or maybe flashfire) make sure to uncheck EverRoot!
Flashfire is the newer free mobile odin pro I think. You might be able to use it in place of Mobile Odin Pro and instead of the supersu zip in addition to flashing FOL1 it comes with an option to inject SuperSU.
I recommend sticking with mobile odin pro for confirmed results. MOP does not support Lollipop.
Note that once you're rooted and upgrade to Lollipop your android system status will change from normal to custom. This prevents future OTA updates.
Root survives factory reset, but flashing official firmware with pc odin will make your phone genuine again as long as you didn't trip knox.
Downgrading to kitkat will very likely require a factory restore. Possibly also when upgrading back to Lollipop.
Note that the XPosed framework on lollipop and samsung touchwiz stock roms does not seem supported.
It seems some people have flashed a Deodexed rom and unofficial xposed to have it working. I made a single attempt and was unable to have it working.
I assume you could stay on kitkat and manage to get xposed working easy.
If you decide to use xposed, do not try to flash the framework without mobile odin pro, or flashfire.
Using a custom recovery, or flashing anything custom with PC Odin will trip knox.
Look over the information around to get a comfortable understanding and good luck!
Proceed only with the understanding that you could always on accident trip knox, or brick your phone.
I believe there is no known way to reset knox flag to 0 on the SM-N900T.
For future readers using a newer firmware than FOL1 it may no longer be possible to pc odin downgrade to kitkat without tripping knox.
So there is no way of downgrading without tripping knox
You can downgrade to kitkat NE6 using PC odin from t-mobile lollipop firmware OB6/OL1. (OL1 being the latest lollipop firmware, OB6 a version older). Once on kitkat NE6 firmware u can use towelroot to gain root and you will not trip knox. Unless you manage to check an option somewhere during this process that would cause you to trip knox. .
As stated, I achieved downgrading/rooting without tripping knox just a couple days ago from the current latest t-mobile galaxy note 3 (SM-N900T) firmware FOL1.
I then upgraded back from KitKat NE6 to Lollipop FOL1 using mobile odin pro.
You can probably downgrade to any 4.4 kitkat firmware, NOT 4.3 jellybean, just fine without tripping knox if you have a kitkat, or lollipop firmware up to FOL1.
I'll try it later, I also want to know if custom roms are possible
From what I've read you can install a custom rom as long as it has a stock kernel, otherwise you trip knox. You would need to flash with flashfire, or mobile odin pro though...
I've only used the stock firmware on my note 3 so don't completely know about using a custom rom.
I don't think a custom ROM can be flash via Odin. A custom ROM requires a custom recovery and a custom recovery will trip Knox on a stock KK or LP AFAIK.
Ohh ok. This is all sorta new to me as well. I had just assumed mobile odin pro could because FlashFire is its "successor".