Develop Bugs

[Q] Getting phone warranty ready

My phone is giving me issues and I am trying to send it in to get it exchanged via warranty. I was running virgin rom 4.4 but flashed back to stock 4.2.2, a friend of mine stupidly let get the update to 4.3 so i spent a while trying to root it to run triangle away. I ended up finding and using the chain fire auto root, ran triangle away and reset the device.
System status:Custom
Knox kernel lock: 0x0
know warranty void : 0x1
csb-config-lsb: 0x30
I was wondering, what else would need to be done to unroot and prep it to be shipped back in?

Knox warranty void: 0x1 is impossible to reset as of now.
Sent from my SGH-M919 using Tapatalk

Once you let OTA install 4.3 you have Knox and rooting it trips it. In order for you to send it back you would have to be at 0 count which its already too late since your count is ×1. I'm sure sooner or later someone will find a way to reset the counter but as of now its a no go. Sorry about your luck.
Sent from my SGH-M919 using xda app-developers app

Since you're already on the mk2 bootloader you may as well go ahead and odin flash the mk2 tar. Be sure to Factory Reset in custom recovery before flashing with odin to avoid "Device Status: Custom."
From what I've read, Asurion (the primary insurance company for 3 of the big 4 US Carriers) doesn't even check for KNOX. With that in mind, you may also receive a phone with the KNOX flag tripped.
As long as you have stock rom image, stock recovery, it should read Device Status: Official under Settings > More > About Device > Status.
That's all they look for. They don't bother with download mode.

help soft brick 4.3

ok so heres the deal.....I updated my tmobile s4 to 4.3...than I used cf auto to root and then I installed wicked 9.1 everything was working good.....tried to go back to 4.2.2 via official firmware via oden...well it failed and now phone is soft bricked and says run firmware recovery thru oden...well I installed drivers but phone will not connect to oden......what do I do?? I kinda figured I need to download 4.3 off firmware but cant seem to find it anywhere any help would be greatly appreciated

jonandjanette said:
ok so heres the deal.....I updated my tmobile s4 to 4.3...than I used cf auto to root and then I installed wicked 9.1 everything was working good.....tried to go back to 4.2.2 via official firmware via oden...well it failed and now phone is soft bricked and says run firmware recovery thru oden...well I installed drivers but phone will not connect to oden......what do I do?? I kinda figured I need to download 4.3 off firmware but cant seem to find it anywhere any help would be greatly appreciated
Click to expand...
Click to collapse
When you updated from 4.2.2 to 4.3, Samsung made it so you cannot go back to 4.2.2 anymore. 4.3 brings the addition of KNOX. KNOX pretty much tells the carrier or manufacturer if the phone has been rooted and warranty has been voided. 4.2.2 doesn't have KNOX and Samsung made it to where you couldn't downgrade. You can only restore back to 4.3.
Here is the 4.3 stock Odin Tar:
https://copy.com/1yJkfBBGa4VwTzl

Vigz said:
When you updated from 4.2.2 to 4.3, Samsung made it so you cannot go back to 4.2.2 anymore. 4.3 brings the addition of KNOX. KNOX pretty much tells the carrier or manufacturer if the phone has been rooted and warranty has been voided. 4.2.2 doesn't have KNOX and Samsung made it to where you couldn't downgrade. You can only restore back to 4.3.
Here is the 4.3 stock Odin Tar:
https://copy.com/1yJkfBBGa4VwTzl
Click to expand...
Click to collapse
gotcha...tynm.....also what does knox warranty void 0x1 does it mess up the phone or just mean the warranty is now void

jonandjanette said:
gotcha...tynm.....also what does knox warranty void 0x1 does it mess up the phone or just mean the warranty is now void
Click to expand...
Click to collapse
Yes, it means warranty is void. There are developers that are trying to see if they can revert this back to 0x0 and get warranty back.

Vigz said:
Yes, it means warranty is void. There are developers that are trying to see if they can revert this back to 0x0 and get warranty back.
Click to expand...
Click to collapse
That's cool...well thanks everyone, phone is back up and kicking, now the only issue is the Sean android kernel on the start up screen due to the warranty void 0x1

4.3 Update... DOH!

So like an idiot I upgraded to 4.3 without reading up on it first. I used ODIN to flash the 4.3 root66 version and my 'warrenty bit' changed to 1. From what I have read the way that I did it shouldn't have triggered that. I've been reading forum after forum in a way to reset the bit and I guess it is an efuse. With that being said does anyone have a way to successfully downgrade the bootloader to get rid of the Warrenty Bit 1? I don't care if it bricks the phone if I can send it in for warranty and get another one that is status 0.

I think you are out of luck. There is no way to reset that bit period.
Now if you tried to flash Root66 for UVDMD5, your phone for sure will brick. I am not sure if the Service personnel can salvage it.
I think Water damage may be covered by all carrier insurances.

I may have a problem too. I recently rooted my S3 with root66 4.3 stock rom from unrooted 4.1.2 with Odin. I don't see KNOX anywhere in the phone. The phone works but I just can't make or receive calls. The update probably updated the modem. Is it safe to downgrade it back to my original unrooted 4.1.2 using Odin? This is what i see in download mode:
PRODUCT NAME: SGH-T999V
CURRENT BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
If I can't downgrade the firmware, can I downgrade the modem? The modem maybe causing problems with making/receiving calls. I'm also worried if the BOOTLOADER line is related to KNOX.

cd964 said:
I may have a problem too. I recently rooted my S3 with root66 4.3 stock rom from unrooted 4.1.2 with Odin. I don't see KNOX anywhere in the phone. The phone works but I just can't make or receive calls. The update probably updated the modem. Is it safe to downgrade it back to my original unrooted 4.1.2 using Odin? This is what i see in download mode:
PRODUCT NAME: SGH-T999V
CURRENT BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 0
BOOTLOADER RP SWREV: 1
If I can't downgrade the firmware, can I downgrade the modem? The modem maybe causing problems with making/receiving calls. I'm also worried if the BOOTLOADER line is related to KNOX.
Click to expand...
Click to collapse
No you cannot downgrade with Odin.. What I suggest you do first is backup any files you want to keep, re-Odin the 4.3 firmware, after that reboot to recovery and do a factory reset and reboot.. If you still encounter problems them flash a 4.1.2 ROM.. That's pretty much the only way to downgrade, you can try downgrading modems if there's a different 4.3 modem for your device
Sent from my SGH-M919 using Tapatalk

Addition. You can flash a 4.1.2 Rom VIA RECOVERY ONLY. Do not flash it via Odin.

I might have made things worse by installing TWRP before reading the responses. The phone started updating on its own right after I flashed TWRP and rebooted. Now it says:
CURRENT BINARY DOWNLOAD: Yes (1 Count)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: Enabled
Warranty Bit: 1
BOOTLOADER RP SWREV: 1
I guess it was the KNOX bootloader from the root66 4.3 rom in the phone that detected the change and decided to update the phone plus change the counts. So probably there's no way of downgrading now and I would just have to deal with a rooted 4.3 which sucks. The phone can make calls/receive calls now but the signal is weak and constantly cuts out plus the battery drain is horrendous. Some apps won't even download to, or install or work with the phone.
Using TWRP for recovery of the 4.1.2 official stock rom would probably brick my phone since the bootloader will probably take over again.

[Q] Help me choose correct files and order for Odin-ing

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

[Q/A] Answers Added - OTA's/Updates, rooting & tripping Knox? - other questions

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