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...
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
My Note 2 was on stock 4.1.2, never rooted or flashed anything. And I have upgraded to 4.3 via OTA.
Before downgrading, everything was fine in Download Mode.
Today, I downgraded back to stock 4.1.1 (from Sammobile), and in Settings, Device Status says Modified.
In Download Mode, KNOX Warranty Void: 1, Custom Binary Download: Yes - 1, System Status and Current Binary: Custom.
So I wonder why my phone is detected as it has been hacked when everything is stock.
KNOX by nature disables you from downgrading your firmware. By doing so you've tripped it and raised a flag of 0x1. It doesn't matter whether you were rooted or stock. It's all the same.
So I have read these 2 threads talking about how to downgrade the bootloader, making it KNOX free.
One is for AT&T model and the other is for international model.
On the AT&T thread, they are flashing the old bootloader from 4.1.2.
The files they are using are sbin (I don't know the extension), tz.img, sboot.bin, and param.bin.
I found sboot.bin and tz.img from the 4.1.2 stock firmware (downloaded from Sammobile).
http://forum.xda-developers.com/showthread.php?t=2500823
http://forum.xda-developers.com/showthread.php?t=2502464
Double-post. Deleted.
Greetings!
I urgently need help to verify what files and in what order to flash to restore my GF's Note2:
It's a GT-7100 that is still on 4.1.1 and eMMC Brickbug Check app reports it as SDS vulnerable... original firmware, execpt for Exynos Abuse, SuperSU and AFwall+, but that was apparently enough to trigger "modified" state and so prevent OTA updates. Installing Wanam Exposed to hide modificatioon did not work, so we unrooted, but forgot to reverse Exynos Abuse fix. Now we're still unable to OTA, but without root as well
I think the next best step will be to flash to 4.3 via Odin and then apply saferoot from cosmyndemeter.
To prevent any warranty issues, I would prefer to keep the phone knox-free, which means that 4.4 update is not an option, and I need the botloader to keep to version mj5 or below.
I got N7100XXUEMK9_N7100VIAEML2_VIA.zip from sammobile.com, which seems applicable (region- and operator-wise), and BL_MJ5_DN3.rar for the unknoxed bootloader.
If I simply flash those two files, will that already trigger a reaction from knox (preventing any future BL-upgrades) or am I safe as long as the phone does not reboot between the two flash processes?
LordHelmchen138 said:
Click to expand...
Click to collapse
Here's what I know.sorry if i cant answer all.
-Stock firmwares from sammobile or other site already have a bootloader included with it, no need to flash other BL.
-Not sure if the bootloader from the MK9 is MJ5 or below, please search.
-Knox enabled bootloaders are upgradable, but can no longer have downgrade.
-If based from your search that MK9 base has a bootloader MJ5 or below, you are good to go.backup and flash via odin.
-Else, find an older rom base with BL MJ5 or below from sammobile.
Good luck. ^.^
Sent from my GT-N7100 using XDA Premium 4 mobile app
Well... I decided to go a longer way that seemed a bit safer:
- got N7100XXDLL4_N7100VIADLL2_VIA from sammobile, which is still exynos-abusable.
- rooted with exynosAbuse
- installed Mobile Odin
- flashed the aforementioned N7100XXUEMK9_N7100VIAEML2_VIA with Mobile Odin, relaxing in the knowlege that Mobile Odin will not flash the bootloader
- flashed the aforementioned mj5 bootloader only with Odin
- unsuccessfully flashed UPDATE-SuperSU-v1.94.zip with Mobile Odin. I guess this was stupid
- rooted with saferoot
result:
rooted phone on 4.3 , so far so good.
Phone Info app reports:
Code:
Knox Warranty Void: 0x0
Bootloader Version: N7100XXUEMJ5
Baseband Version: N7100XXUEMK9
PDA Version: N7100XXUEMK9
CSC Version: N7100VIAEML2
Only my noobishly overoptimistic attempt at rerooting is now visible:
Code:
CUSTOM BINARY DOWNLOAD: yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: custom
WARRANTY BIT: 0
Can anyone reassure that mj5 bootloader means that knox warranty void cannot trigger, so using triangle away is safe ? I'm still slightly worried that the bootloader simply does not display the knox bit, but that it is still 'primed' in the background and just waiting to blow up...
LordHelmchen138 said:
Code:
Knox Warranty Void: 0x0
Bootloader Version: N7100XXUEMJ5
Baseband Version: N7100XXUEMK9
PDA Version: N7100XXUEMK9
CSC Version: N7100VIAEML2
Only my noobishly overoptimistic attempt at rerooting is now visible:
Code:
CUSTOM BINARY DOWNLOAD: yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: custom
WARRANTY BIT: 0
Can anyone reassure that mj5 bootloader means that knox warranty void cannot trigger, so using triangle away is safe ? I'm still slightly worried that the bootloader simply does not display the knox bit, but that it is still 'primed' in the background and just waiting to blow up...
Click to expand...
Click to collapse
Knox warranty void 0x0 means the bootloader didn't trigger the Knox but honestly after a point we should all stop caring about Knox ( unless you use it for business purposes or still under warranty ). Now you can flash any custom KitKat ROM and be on Mj5 bootloader. Only thing is that phone won't charge when turned off ( draw back of mj5 and other jelly bean bootloaders ) only being on KK boot loader can charge your phone when turned off . here you got two options if you only flash nd3 bootloader after upgrading to custom KK ROM it will trigger Knox and it will show 0x1 or you can flash the official stock KK rom via odin that will flash the ND3 boot loader and knox remains 0x0 since its an official ROM . So it depends on you what do you plan on doing on your note II ,if you want to try newer ROMs or stick to 4.3 based ROMs
Sent from my GT-N7100 using Tapatalk
Well, the phone is not mine, and there's still about six months of warranty left. So yes, I still have to care about knox
As it stands, 4.3 and mj5 bootloader look fine, so it's only the flash counter and system :modified that I want to take care of.
Sent from my D5503 using XDA Free mobile app
For my version P601 (android 4.3) there is no ota update. I see that there are 4.4.2 roms on Samfirmware. If I update my tablet over Odin, do Knox registry some change regarding void if guaranty? I don't need root or recovery change, only stock fw update.
Thanks.
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".