SM-N910F "set warranty bit: kernel" - Galaxy Note 4 Q&A, Help & Troubleshooting

I lended the phone with the latest OTA firmware to a friend of mine and he returned it back with "set warranty bit: kernel" on the top left of boot screen.
In the download mode it also reports CUSTOM binary and system so I guess he fu-ked it by flashing either wrong firmware or rooting it.
Is there any way to correct this? ODIN with the latest original 4 files version of firmware?

It's probably time to have "the talk" with your friend. About respecting other people's property, I mean.
You can revert system binary status to Official by either restoring with SmartSwitch or flashing stock firmware with Odin (as mentioned), and possibly wiping. Unfortunately, though, your Knox warranty bit is now permanently locked to 0x1 and nothing can be done about that, short of replacing the motherboard.

Thanks I reflashed the OEM 4-file ROM and the stupid yellow message is history

Still does not explain why and how your "friend" has managed to flash your phone with some dodgy firmware....

Related

[Q] leftover folders to remove?

guys,
My I9505 has a hardware problem: the VOL DOWN is unresponsive.
That's a nasty problem, because rebooting the phone gives a lot of problems (warnings about a custom rom, and then nothing works anymore)
So I'd like to return it, but have to restore the phone for warranty.
I managed to flash latest stock MH8.
Here are my questions:
1. before, I've flashed autoroot - does that make the flashcounter go up?
2. before, I've flashed philz recovery - does that make the flashcounter go up?
3. I've flashed the new stock firmware, but still see a clockworkmod folder. can I safely remove that?
4. are there other folders I've to remove to NOT void my warranty?
5. is it necessary/safe to use triangle away on MH8 with the new bootloader?
thanks for any insights!
mailman
mailman123 said:
guys,
My I9505 has a hardware problem: the VOL DOWN is unresponsive.
That's a nasty problem, because rebooting the phone gives a lot of problems (warnings about a custom rom, and then nothing works anymore)
So I'd like to return it, but have to restore the phone for warranty.
I managed to flash latest stock MH8.
Here are my questions:
1. before, I've flashed autoroot - does that make the flashcounter go up?
2. before, I've flashed philz recovery - does that make the flashcounter go up?
3. I've flashed the new stock firmware, but still see a clockworkmod folder. can I safely remove that?
4. are there other folders I've to remove to NOT void my warranty?
5. is it necessary/safe to use triangle away on MH8 with the new bootloader?
thanks for any insights!
mailman
Click to expand...
Click to collapse
Be VERY VERY careful if you're running the new knox firmware that you don't trip the eFuse and change KNOX Warranty void status.
If you have flashed stock firmware MH8 in Odin I would simply do a factory reset in the STOCK recovery and wipe everything that way and send to repair centre.
Do not flash ANYTHING custom or otherwise, even older Stock firmware in Odin.
If you do you will trip the eFuse, your KNOX warranty status will change and you'll be f***ed mate.
Obagleyfreer said:
Be VERY VERY careful if you're running the new knox firmware that you don't trip the eFuse and change KNOX Warranty void status.
If you have flashed stock firmware MH8 in Odin I would simply do a factory reset in the STOCK recovery and wipe everything that way and send to repair centre.
Do not flash ANYTHING custom or otherwise, even older Stock firmware in Odin.
If you do you will trip the eFuse, your KNOX warranty status will change and you'll be f***ed mate.
Click to expand...
Click to collapse
Thanks, that's very good advice. will keep it in mind.
Do you know the answer to my questions about the flashcounter going up by flashing recoveries in stead of custom roms?
thanks,
mailman

eMMC burst mode: enabled

Hi, i used old philz recovery to restore nandroid backup (without selinux option) and now i have this new line in download mode: eMMC burst mode: enabled
unfotunately now i get red warning everytime i boot with custom kernel (top of the screen, red warning: knox kernel warranty void or so..) it is very annoying.
Can i go back to previous state? when i had no messages at boot with custom kernel or recovery? i flashed with odin MJ7 XEO and even MJ3 leak (without botloader ofc because its blocked when trying). i did full wipe, no help...
i had knox warranty bit void 0x1 science day one cause i tried to flash MGA before i read it will void my warranty so no worry about voiding my warranty now, i can flash everythig - please help me to remove this burst mode! thx
Kriomag said:
Hi, i used old philz recovery to restore nandroid backup (without selinux option) and now i have this new line in download mode: eMMC burst mode: enabled
unfotunately now i get red warning everytime i boot with custom kernel (top of the screen, red warning: knox kernel warranty void or so..) it is very annoying.
Can i go back to previous state? when i had no messages at boot with custom kernel or recovery? i flashed with odin MJ7 XEO and even MJ3 leak (without botloader ofc because its blocked when trying). i did full wipe, no help...
i had knox warranty bit void 0x1 science day one cause i tried to flash MGA before i read it will void my warranty so no worry about voiding my warranty now, i can flash everythig - please help me to remove this burst mode! thx
Click to expand...
Click to collapse
hi there, you should be able to flash a stock 4.3 rom. This is what i did. I no longer get anything come up when booting the phone besides the samsung logo. I however want to get back to a 4.2.2 rom.. None of them work.. I can only flash 4.3 roms.
nixxss said:
hi there, you should be able to flash a stock 4.3 rom. This is what i did. I no longer get anything come up when booting the phone besides the samsung logo. I however want to get back to a 4.2.2 rom.. None of them work.. I can only flash 4.3 roms.
Click to expand...
Click to collapse
Yes i can flash stock 4.3 mj7 system is working, but every time i run philz or use custom kernel i get this annoying red messages on the top of samsung i9505 logo ... and emmc burst mode still is enabled.
Kernel is not seandroid enforcing
Recovery is not seandroid enforcing.
Kriomag said:
Yes i can flash stock 4.3 mj7 system is working, but every time i run philz or use custom kernel i get this annoying red messages on the top of samsung i9505 logo ... and emmc burst mode still is enabled.
Click to expand...
Click to collapse
i only get that message going into download mode.. If just rebooting the phone i get nothing.. Hopefully someone will find a way to reset the phone phone back to default.

Seem to have bricked my phone following DJembey's root method

Hi everyone, I'm desperate here.
I was following DJembey's root method TO THE WORD/LETTER. Everything was fine up until the last bit in changing the 'custom' status to official. The triangle away method didn't work, so I downloaded the 'OFFICIAL_STATUS_MOD' and used odin to try and flash the PDA, but it came up as 'FAIL' and now my phone is stuck on boot mode with 'FIRMWARE UPGRADE ENCOUNTERED AN ISSUE'. I've tried using odin to flash back to the stock rom, but it keeps coming up with 'FAIL'. Rally need help
DJembey's root method:
http://forum.xda-developers.com/showthread.php?t=2255190
jesus1987 said:
Hi everyone, I'm desperate here.
I was following DJembey's root method TO THE WORD/LETTER. Everything was fine up until the last bit in changing the 'custom' status to official. The triangle away method didn't work, so I downloaded the 'OFFICIAL_STATUS_MOD' and used odin to try and flash the PDA, but it came up as 'FAIL' and now my phone is stuck on boot mode with 'FIRMWARE UPGRADE ENCOUNTERED AN ISSUE'. I've tried using odin to flash back to the stock rom, but it keeps coming up with 'FAIL'. Rally need help
DJembey's root method:
http://forum.xda-developers.com/showthread.php?t=2255190
Click to expand...
Click to collapse
what firmware you are trying to root, and what stock firmware you tried to flash?
Here's what it says, this is the firmware I am trying to flash, but just before I did the root guide, I applied all of the official updates through settings >about phone > update, etc. It was still on 4.2.2 and I think it was october edition of the latest firmware (in UK)
samersh72 said:
what firmware you are trying to root, and what stock firmware you tried to flash?
Click to expand...
Click to collapse
So maybe I am trying to flash to an older firmware, is this not allowed?? Also, it says that the PIT partition is missing on ODIN (as seen on the attached picture)
jesus1987 said:
So maybe I am trying to flash to an older firmware, is this not allowed?? Also, it says that the PIT partition is missing on ODIN (as seen on the attached picture)
Click to expand...
Click to collapse
i think you have the secured bootloader (check if you have Knox void 0x0 or something in download mode) if yes, you can not go back to MDM or an old firmware, you can flash new "knoxed" firmware.
note that Triangle away and other stuffs to reset counter or status, wont work on new firmware.
samersh72 said:
i think you have the secured bootloader (check if you have Knox void 0x0 or something in download mode) if yes, you can not go back to MDM or an old firmware, you can flash new "knoxed" firmware.
note that Triangle away and other stuffs to reset counter or status, wont work on new firmware.
Click to expand...
Click to collapse
So, when I go into 'proper' download mode (pressing Vol. Down + Home + power) I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
And for the 'Firmware upgrade encountered an issue...' screen, I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
Hope this helps
jesus1987 said:
So, when I go into 'proper' download mode (pressing Vol. Down + Home + power) I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
And for the 'Firmware upgrade encountered an issue...' screen, I have:
ODIN MODE
PRODUCT NAME:GT-I9505
CURRENT BINARY:Samsung Official
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID:0x1(or t?)
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION:Enable
Hope this helps
Click to expand...
Click to collapse
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE
samersh72 said:
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE
Click to expand...
Click to collapse
At the moment I'm downloading "I9505XXUDMI1-PRE-ROOTED-ODEX-FULL.rar", will this work do you think when I try and flash using ODIN? Hope so!!!
Right, I've tried that firmware, and it's still failing on odin any ideas?
samersh72 said:
it seems you have the secured bootloder, dont use triangle away or somthing else to reset counter and status.
you can flash firmware that begin only with I9505XXUD or I9505XXUE
Click to expand...
Click to collapse
Seems this one doesn't work either...
I've noticed something weird though, I've tried running it a few times, and each time it seems to get a little further in the flash process (it gets to just past modem) then fails.
Hello,
what USB cable are you using?
I have encountered an issue with the original Samsung cable, ("fail" in Odin all the time), but when I switched to another usb cable everything worked from that moment on
Try it, you might have luck.
Zeitraffer said:
Hello,
what USB cable are you using?
I have encountered an issue with the original Samsung cable, ("fail" in Odin all the time), but when I switched to another usb cable everything worked from that moment on
Try it, you might have luck.
Click to expand...
Click to collapse
Funny you should say that...
I restarted my PC, and tried a few USB ports, and cables, and it was still failing. But I stuck at it, and literally doing the same procedure over and over seems to have worked, as it randomly decided to flash fine! This was using the XXUE firmware
Do you still have KNOX WARRANTY 0X1 in download mode?
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Do you still have KNOX WARRANTY 0X1 in download mode?
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, it still says KNOX WARRANTY VOID 0x1 but it also says the binary and system status are official. Is there a way to unvoid?

4.4.4 KitKat to 5.0.1 via ODIN tripped Knox

Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN on my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
EDIT: When I'm performing a factory reset from within the ROM it fails with "dm-verity verification failed..." message and takes me to the Android system recovery. From there I can do the factory reset. I think there is something gone wrong. Ideas on that message?
raupe1337 said:
Hello folks,
today I flashed official Lollipop 5.0.1 via ODIN in my N910-F and accidently tripped my KNOX Counter. So be careful if you do not want to void your warranty.
My phone is carrier branded DTM (T-Mobile) and had latest OTA firmware 4.4.4 *ANK4 on it. Back when i did buy my device I decided to debrand my phone as soon as Lollipop comes out.
So I did and flashed in one step from KitKat (T-Mobile) to Lollipop (Open). From what I read a assumed it would be no problem because it's a newer build but in some way it tripped my Knox Counter to 0x1 (3).
I did use Odin 3.09 as suggested by sammobile but ended up with an error (Fail) at the end of the flashing procedure. I downloaded Odin 3.10 and reflashed without any problems. This might be also considered as a reason for tripping the counter (as it says 3). I checked my counter after 2 factory resets afterwards.
Now I'm actually good to root I guess. Be careful.
Click to expand...
Click to collapse
I never heard of this? You tripped Knox with the official firmware? Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
I don't know why it tripped it. I haven't tripped it even after using Z3X box.
Everytime I use a firmware from sammobile it never tripped any counter of my phones.
marleyb said:
Did you maybe have the wrong options selected in Odin, as you would be the first who is able to trip Knox with official firmware???
Click to expand...
Click to collapse
Had standard options selected which are "Auto Reboot" and "F. Reset Time".
I might think the trip is not caused by flashing but performing a factory reset afterwards which results in "dm-verity verification failed..." message in the recovery menu. From what I know this error is caused by root which I didn't.
Update: Device is now working as supposed. After two failed attempts to flash the firmware via Kies new it worked on a third time. No error on factory reset.
My assumption is that there went something horribly wrong on first time flashing the firmware via ODIN, which preventet the factory reset from performing as usual. Knox detected that inexplicable status and graded it as modified which tripped the Knox counter then. I have no other explanation for this, maybe the 0.01% got real in my case.

How to return Galaxy J5 (2016) from "Custom" to "Official"?

Hello to all of you
Using Odin, I flashed TWRP recovery on a non-rooted Galaxy J5 (2016) J510F (with android 6.0.1) to take a Nandroid backup. I took the backup successfully. Rebooting to android deleted TWRP and replaced it with stock recovery.
Now the system is not rooted (I checked with root checker). "Device status" is "Custom". Also in ODINE MODE, the "SYSTEM STATUS" is "CUSTOM" (look at the attached picture).
Is there a way to change "Device status" and "SYSTEM STATUS" from Custom to Official?
Thanks
You've customized your device by Flashing TWRP, to get Official back you'll have to flash stock recovery back
theashleyd123 said:
You've customized your device by Flashing TWRP, to get Official back you'll have to flash stock recovery back
Click to expand...
Click to collapse
When I boot to recovery mode, stock recovery is there. Is this not enough?
Pretty sure that TWRP is still there somewhere, even if your not able to boot it you flashed it with Odin, reflash the stock boot image with Odin and do a factory erase. Should go back to Official.
theashleyd123 said:
Pretty sure that TWRP is still there somewhere, even if your not able to boot it you flashed it with Odin, reflash the stock boot image with Odin and do a factory erase. Should go back to Official.
Click to expand...
Click to collapse
1. Should I reflash "boot image" or "stock recovery"?
2. Does flashing "boot image" or "stock recovery" (without factory reset and without flashing entire ROM) delete the data?
If you've only modified the recovery then just reflash that no need to worry about boot.img unless you were previously rooted
theashleyd123 said:
If you've only modified the recovery then just reflash that no need to worry about boot.img unless you were previously rooted
Click to expand...
Click to collapse
Where can I download stock recovery.tar for J510F?
Just flash whole FIRMWARE, and you will have Official system status, but that doesn't change Knox 0x1 which means that you have rooted your phone (or modified it in some way) and someone that knows few stuff about android will always checj knox status so it doesn't matter what your system status is.
Ragazzza said:
Just flash whole FIRMWARE, and you will have Official system status, but that doesn't change Knox 0x1 which means that you have rooted your phone (or modified it in some way) and someone that knows few stuff about android will always checj knox status so it doesn't matter what your system status is.
Click to expand...
Click to collapse
Do you mean that after flashing whole FIRMWARE "SYSTEM STATUS" in ODINE MODE will change to "OFFICIAL", but "WARRANTY VOID" will not change to "0x0"?
Knox 0x0 relies on an eFuse which is triggered when you press the volume up key to confirm and then flash something. You cannot change it back, you used to be able to hide it with TriangleAway by @Chainfire but not sure it works now. And Yes you'll have to flash the whole stock firmware from Sammobile to get Official back
theashleyd123 said:
Knox 0x0 relies on an eFuse which is triggered when you press the volume up key to confirm and then flash something. You cannot change it back, you used to be able to hide it with TriangleAway by @Chainfire but not sure it works now. And Yes you'll have to flash the whole stock firmware from Sammobile to get Official back
Click to expand...
Click to collapse
What you said posed a question for me. You said "Knox 0x0 relies on an eFuse which is triggered when you press the volume up key to confirm and then flash something."
Entering into Downloading mode needs pressing volume up key. Does this mean that even flashing official ROM with ODIN voids warranty?
I've actually done it with an S5 I bought once and that too cause 0x1 despite it being 0x0 before and me flashing stock. The device had never been tampered with and the only reason I flashed it with Odin was because I couldn't find a Marshmallow Rom for it at the time other than the stock one just released.

Categories

Resources