Hello all,
It has been a little while since I have messed around with this device. I currently have OF6 installed and running with eningeering bootloader, AOU kernel, TWRP, and stock rom of OF6
Can I flash new custom roms on this and have them work okay even though it is the older bootloader? Would it possibly trip Knox as well?
Someone mentioned before that you could not flash the newest version from samsung with the bootloader removed without tripping knox supposedly. Is that true? I can remove the bootload from samsung odin files to flash but really don't want to trip knox on here to use Samsung Pay later.
Any input would be greatly appreciated.
Related
So I recently used CF Autoroot to root my T-Mobile GS3 SGH-T999 and I heard that if you try to downgrade to android versions before 4.3 your phone will be hard bricked. So with my knox counter tripped I was wondering can I flash a rom that is on 4.2.2 I want to flash the MIUI rom. Thanks in advance.
You can flash any custom Rom via Custom Recovery. Nothing bad will happen as they have only Rom and Kernel.
However just never flash Pre-4.3 Samsung firmwares via Odin. Those contain the older bootloader. If you tried to flash older bootloader, you get hardbrick.
Perseus71 said:
You can flash any custom Rom via Custom Recovery. Nothing bad will happen as they have only Rom and Kernel.
However just never flash Pre-4.3 Samsung firmwares via Odin. Those contain the older bootloader. If you tried to flash older bootloader, you get hardbrick.
Click to expand...
Click to collapse
Thanks for the answer been wanting to try MIUI for so long was scared of hard brick
Quxus said:
So I recently used CF Autoroot to root my T-Mobile GS3 SGH-T999 and I heard that if you try to downgrade to android versions before 4.3 your phone will be hard bricked. So with my knox counter tripped I was wondering can I flash a rom that is on 4.2.2 I want to flash the MIUI rom. Thanks in advance.
Click to expand...
Click to collapse
I know to get rid of the trip count I used triangle away. I installed, opened the app, followed the set up, reboot and count was back to zero.
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 currently have my SGS 3 stock rooted with TWRP 2.7 installed. The version of 4.3 I have installed doesn't contain the KNOX bootloader. I'd like to keep it that way should I decide to later move onto a custom rom. From what I've read, if KNOX is installed I won't be able to do that. Is this correct?
I've searched for 4.4 without KNOX, but I haven't been able to find anything. Does anyone here know if it is available? I don't have any major issues with the 4.3 stock rom. I did noticed that my battery drains slooowly if I'm using navigation and it's plugged in. I think that that issue may be due to the iBolt car dock I'm using. I don't think it allows anything over 1 amp for charging.
Should I just go ahead and installed a custom rom that is 4.4?
Thanks
I believe that KNOX doesn't restrict you from installing a 4.4 based ROM, but once you have KNOX you will not be able to downgrade to 4.3 or earlier release. An attempt to do so will permanently brick the phone.
stopeject said:
I believe that KNOX doesn't restrict you from installing a 4.4 based ROM, but once you have KNOX you will not be able to downgrade to 4.3 or earlier release. An attempt to do so will permanently brick the phone.
Click to expand...
Click to collapse
You can install any rom zip on knox as long as you do not downgrade the boot loader via tar files or any other method that flashes every part of the phone.
Thanks stopeject and oeyhdownsouth.
So I rooted using chainfires method for my Tab S 8.4 wifi (T700) and it tripped Knox (0x1). I know there is no way to currently reset it and there is a bounty out for it. No big deal on tripping it, I wanted to root anyways and want to try out CM12 eventually. After doing some research it appears Knox gets tripped when unofficial firmware or recoveries get flashed via Odin. Knox is not tripped when you flash official Samsung firmware. I had a few questions though I can't seem to get a clear answer on and was hoping to find some or get a discussion going at least about Knox for the Tab S.
Questions and Answers
- Are you still able to receive OTA updates on a stock rooted rom/recovery with Knox tripped?
A: No, not while rooted, "Operating System on your device has been modified in an unauthorized way. Try downloading software updates using Samsung Kies on your PC" Unsure if Knox prevents it but most likely does not.
- Will you lose root if you can get OTA updates?
A: No OTA Updates allowed on rooted devices. Reports have stated that flashing the official firmware update via odin will unroot the device but maintain data, most likely kies is the same when updating. However if a bootloop occurs after flashing, you may need to wipe data and cache via stock recovery.
- If knox is tripped (0x1), if I flash a custom recovery (TWRP/CWM) or use chainfires method to root again will it trip Knox again (0x2)?
A: YES & NO, Knox will not read (0x2) if unofficial img's are flashed via Odin but reports on other devices have stated it will read {0x1(2)}
- If yes can you trip Knox too many times, rendering device inoperable or bricked?
A: NO, tripping Knox only informs if warranty has been voided by flashing unofficial firmware/recovery/img files and root kernals via Odin. When the knox warranty void status is tripped, the knox software will no longer work.
- What is tripped specifically in Knox (for the Galaxy Tab S), an efuse, or is it software or binary code?
A: Most likely an eFuse. There is no way to reset the flag counter as it is believed to be an eFuse that once gets blown it stays damaged and cannot be reset.
***New Questions***
- Will flashing a custom recovery img (TWRP/CWM) via ADB trip Knox (0x1)?
A: Yes, it will trip Knox.
Thanks to all who answer and contribute.
If there are any new questions, updates to be added or wrong information to be corrected please let me know.
No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!
DUHAsianSKILLZ said:
No OTAs when you are rooted on custom rom. Dont worry, someone will make a stock custom rom to flash with twrp Or you can odin flash stock lollipop and root with twrp
If you do the ota it will probably not install because of root.
If you flash a custom recovery, or root again.. Knox will stay 0x1. It wont change.
Knox is like a check when booting up your device. Its more like uhh protection. If you install custom stuff then you dont get protection. Knox was a security feature that samsung included. Its really not needed as it really doesnt work. Thats why people trip it. I highly doubt its used for security but I think its just used to detect if warranty has been void or not. Its not something that you should worry.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.
how do you make the knoxx counter back to zero ??
methslushee said:
Thanks, I figured Knox is nothing more than just a feature to let Tech's know if the warranty had been voided. Also I figure that flashing the updates myself when they come out would be the best option. Thanks again.
Click to expand...
Click to collapse
is there a limit to knox number and how can it be made to zero again to retain warranty
[email protected] said:
is there a limit to knox number and how can it be made to zero again to retain warranty
Click to expand...
Click to collapse
Read post two above yours. It can not be reset to zero once it's tripped.
Even if you root and trip knox, although you cannot receive official ota's, you can still use samsung kies to still recieve the updates.
updated OP with answers to questions.
Stupid Knox. This is one "feature" of Samsung devices which makes me less likely to purchase them in the future.
For the new question, flashing any custom recovery with odin or adb will trip knox. Flashing stock should not trip
Hello All,
I am currently looking at different ways to try and update my device to dojc or doj7. Right now it is on DOH6 and seems like I have a few random glitches with the way it works and crashes. I am rooted currently with engineering bootloader with a custom recovery. I am thinking of one of two paths and wondering what might be the better of the two options in your opinion.
First, create a firmware file to flash with Odin that does not have the bootload file in it and flash that. Then root the device again the same way I did with the DOH6 root method and engineering bootloader. Stay on that install from Samsung and just root it.
Second, install a custom rom with that new version as a base (I think I remember seeing some stock rooted roms). and then upgrade the modem only with odin. Not sure if there is anything else other that the modem that would need to be updated with Odin.
I am just not sure if that second option would work if the firmware is too different to work with it. Any opinions on which might be the better option? How have you been able to update to DOJ7 or DOJC and root without worrying about Knox? And input would be greatly appreciated.
Couldn't you just flash a custom Rom and flash the new modem with Odin?
Would that work okay guys? I think that should be fine and leave the bootloader on 5.0 engineering and it won't trip Knox.