Hey,
Im performing a restart to Note 4, and this error message shown at start and dissappear after 5 sec.
Picture added. (yellow line said: "Set Warranty Bit: karnel")
I had installed NamesLess Rom & Karnel
Now i tried to flash other rom (SimplRom) but no change about error message.
Any idea how to fix this please?
TheDrag0n said:
Hey,
Im performing a restart to Note 4, and this error message shown at start and dissappear after 5 sec.
Picture added. (yellow line said: "Set Warranty Bit: karnel")
I had installed NamesLess Rom & Karnel
Now i tried to flash other rom (SimplRom) but no change about error message.
Any idea how to fix this please?
Click to expand...
Click to collapse
this error is caused by lack of reading.
If you search before posting, this kind of error does not occur
It just stands there because your knox is triggered.
When you flash a custom firmware and/or root you phone, it gets flagged as 'modified' once forever and you can't recover the former status any longer, which means you can't use knox and, to some extent, depending upon the country where you bought your phone, your warranty is over.
lucaoldb said:
It just stands there because your knox is triggered.
When you flash a custom firmware and/or root you phone, it gets flagged as 'modified' once forever and you can't recover the former status any longer, which means you can't use knox and, to some extent, depending upon the country where you bought your phone, your warranty is over.
Click to expand...
Click to collapse
thank you for the comment.
Flash a stock kernel.that s all you need
Related
I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.
Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.
Hi!
I have been rooting with CF autoroot and cwm (old version 6.0.4?) and Omega V.19. Been having alot of issues with closed calls and freezing. 3-finger recovery/download mode have not worked either. Have to go by "restart meny"... When apps is looking to yppgrade my cwm it doesn't find any for my model!? And so on!!!
Now I have tried to role back to stock (so I can claim warranty), but no succses!
After many attempts I got TW recovery on it, but can only access using the restart meny. Everytime i start it i get seandroid enforcing, kernel bit somthin something... In download mode I try to flash with odin stock 4.1.2 but get fail all the time. Even though I have not gone past Omega V19 i also have knox void 0x1!???
What to do?
Edit:
Got CWM touch in now but no luck witht the rest. As Odin fails I get "unsupport dev_type" on my phone. But I have chosen the nordic version i9505!?
Edit2:
With the exact same basbandversion xxuame2 it worked! but no it doesn't get passed the "samsung" startscreen;( And without being able to go into download mode via restart meny inside the rom I cant flash it!? I have restarted several times and taken out the battery...
Edit3:
So I have got 4.2.2 now. It's not working good howe ever. No WIFI and no calls. BTW it was a two finger combo (without meny) to get into recovery/download mode. How do I get rid of the text up top to the left on the screen on boot? Doesn't look "stock" to me;(
How do I return it to stock. I have no triangle or counter , just binary custom and the 0x1...
gcbossen said:
Hi!
I have been rooting with CF autoroot and cwm (old version 6.0.4?) and Omega V.19. Been having alot of issues with closed calls and freezing. 3-finger recovery/download mode have not worked either. Have to go by "restart meny"... When apps is looking to yppgrade my cwm it doesn't find any for my model!? And so on!!!
Now I have tried to role back to stock (so I can claim warranty), but no succses!
After many attempts I got TW recovery on it, but can only access using the restart meny. Everytime i start it i get seandroid enforcing, kernel bit somthin something... In download mode I try to flash with odin stock 4.1.2 but get fail all the time. Even though I have not gone past Omega V19 i also have knox void 0x1!???
What to do?
Edit:
Got CWM touch in now but no luck witht the rest. As Odin fails I get "unsupport dev_type" on my phone. But I have chosen the nordic version i9505!?
Edit2:
With the exact same basbandversion xxuame2 it worked! but no it doesn't get passed the "samsung" startscreen;( And without being able to go into download mode via restart meny inside the rom I cant flash it!? I have restarted several times and taken out the battery...
Edit3:
So I have got 4.2.2 now. It's not working good howe ever. No WIFI and no calls. BTW it was a two finger combo (without meny) to get into recovery/download mode. How do I get rid of the text up top to the left on the screen on boot? Doesn't look "stock" to me;(
How do I return it to stock. I have no triangle or counter , just binary custom and the 0x1...
Click to expand...
Click to collapse
SOLVED;
"Official" 4.4.2 via odin solved all my issues Do I have a knox problem now, I dont know!?
Boot to download mode and check.
Knox Warranty Void is probably triggered. 0x1
Anyway, it does'nt really matter.
Yeah if you tried any root method and/or installed a custom ROM Knox Warranty Void would be triggered and after researching there's no way to fix that. The warranty void doesn't affect the phone's performance at all so really nothing to worry about.
KNOX WARRANTY VOID now has a new flag in braces after it. I don't know what it means yet, but after a clean update the number was (0) and after applying cf-autoroot it was (4). I have not experimented further but I think this is either a flash counter (If it is, it seems to count modified partitions or sth. like that) or a bitset describing the modified partitions. Any takes on that from any of you?
I also now see the DCM START message whenever I enter Download Mode and sometimes have some strange behaviour after exiting it. The Tab starts with a completely black Screen. Touches are possible because you can hear the feedback, but the display illumination seems not to turn on.
lowtraxx said:
KNOX WARRANTY VOID now has a new flag in braces after it. I don't know what it means yet, but after a clean update the number was (0) and after applying cf-autoroot it was (4). I have not experimented further but I think this is either a flash counter (If it is, it seems to count modified partitions or sth. like that) or a bitset describing the modified partitions. Any takes on that from any of you?
I also now see the DCM START message whenever I enter Download Mode and sometimes have some strange behaviour after exiting it. The Tab starts with a completely black Screen. Touches are possible because you can hear the feedback, but the display illumination seems not to turn on.
Click to expand...
Click to collapse
You will probably find this is something to do with Knox 2...
Hi to all,
sorry to use the bold character but it's REALLY an unbreakable enigma. It regards My fiancee Galaxy s5 g900f no brand ITV and that one of another user.
The thread in wich we found to be in the same situation is T H I S.
The phone was never touched, modified or altered in anyway as my fiancee doesn't even know what "root" or "rom" means. It was bought in november 2014, used with whatsapp, facebook and two games.
It was updated using wifi OTA to lollipop BOA3 ITV. Update was successful, she didn't wipe data as there were only 4-5 apps on it and the phone was working normally. It stayed this way for more than one month, no problems at all.
It was never touched in anyway, never diverted from the original. A very noob utilization to clarify.
At mid April one day when the phone was on the table in standby , we saw it rebooting. Then worked normally.
The day after it, two more reboots while doing anything , on the third one it appeared "SET WARRANTY BIT KERNEL" and BEGAN TO BOOTLOOP.
The bootloop starts right after "Samsung Galaxy s5 powered by android " and never ends.
Sometimes it gets stuck at "set warranty bit kernel".
THE PHONE ENTERS DOWNLOAD MODE always when pressing vol down,home,power.
IT DOESN'T ALWAYS ENTERS RECOVERY MODE. Sometimes gets stucked in "booting recovery. Recovery is not selinux enforcing. Set warranty bit recovery"
Me and one other guy on androidforums have tried everything:
-1. wipe cache, data and dalvick from stock recovery (it was difficult to enter it but done multiple times)
-2. flashing with ODIN stock images (OFFICIAL ITV FOR ME) . Kitkat and Lollipop officials. ALWAYS GREEN LIGHT PASS!
2.1 Updating bootloaders when going from kitkat to lollipop and viceversa.
2.2 Checking repartitioning using the right ITV PIT files.
2.3 wiping before and after that.
-3 flashing from KIES in FW UPGRADE MODE and emergency mode.
-4 flashed custom recovery. It gets stuck multiple times but the other guy managed to boot into Philz, formatting every partition,
-5 installing CYANOGENMOD 12 but it loads the cyanogen bootanimation for 1 sec, then bootloop.
With lollipop it gets stuck on the samsung bootloader logo.
With kitkat it gets to samsung bootanimation (led and audio working) but never ends.
ONE TIME IT MANAGED TO ARRIVE TO "upgrading android applications 1 of 1" for 2 seconds then bootloops (and it was data clean! so what app is it upgrading?!?)
the status in Odin mode is
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0*1 (1)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
But it was never modified with anything! and it stays this way after an original rom flash! (shouldn't be at least reporting "official" ?)
SAMSUNG SERVICE IN ITALY REFUSED TO REPAIR IT SAYING THAT WARRANTY IS VOID DUE TO CUSTOM MODS.
Don't know what to do. I've tried almost everything.
WE BEG FOR YOU HELP , PLEASE.
P.S. sorry if I have mistaken the thread section or the title
oile said:
Hi to all,
sorry to use the bold character but it's REALLY an unbreakable enigma. It regards My fiancee Galaxy s5 g900f no brand ITV and that one of another user.
The thread in wich we found to be in the same situation is T H I S.
The phone was never touched, modified or altered in anyway as my fiancee doesn't even know what "root" or "rom" means. It was bought in november 2014, used with whatsapp, facebook and two games.
It was updated using wifi OTA to lollipop BOA3 ITV. Update was successful, she didn't wipe data as there were only 4-5 apps on it and the phone was working normally. It stayed this way for more than one month, no problems at all.
It was never touched in anyway, never diverted from the original. A very noob utilization to clarify.
At mid April one day when the phone was on the table in standby , we saw it rebooting. Then worked normally.
The day after it, two more reboots while doing anything , on the third one it appeared "SET WARRANTY BIT KERNEL" and BEGAN TO BOOTLOOP.
The bootloop starts right after "Samsung Galaxy s5 powered by android " and never ends.
Sometimes it gets stuck at "set warranty bit kernel".
THE PHONE ENTERS DOWNLOAD MODE always when pressing vol down,home,power.
IT DOESN'T ALWAYS ENTERS RECOVERY MODE. Sometimes gets stucked in "booting recovery. Recovery is not selinux enforcing. Set warranty bit recovery"
Me and one other guy on androidforums have tried everything:
-1. wipe cache, data and dalvick from stock recovery (it was difficult to enter it but done multiple times)
-2. flashing with ODIN stock images (OFFICIAL ITV FOR ME) . Kitkat and Lollipop officials. ALWAYS GREEN LIGHT PASS!
2.1 Updating bootloaders when going from kitkat to lollipop and viceversa.
2.2 Checking repartitioning using the right ITV PIT files.
2.3 wiping before and after that.
-3 flashing from KIES in FW UPGRADE MODE and emergency mode.
-4 flashed custom recovery. It gets stuck multiple times but the other guy managed to boot into Philz, formatting every partition,
-5 installing CYANOGENMOD 12 but it loads the cyanogen bootanimation for 1 sec, then bootloop.
With lollipop it gets stuck on the samsung bootloader logo.
With kitkat it gets to samsung bootanimation (led and audio working) but never ends.
ONE TIME IT MANAGED TO ARRIVE TO "upgrading android applications 1 of 1" for 2 seconds then bootloops (and it was data clean! so what app is it upgrading?!?)
the status in Odin mode is
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0*1 (1)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLE
UDC START
But it was never modified with anything! and it stays this way after an original rom flash! (shouldn't be at least reporting "official" ?)
SAMSUNG SERVICE IN ITALY REFUSED TO REPAIR IT SAYING THAT WARRANTY IS VOID DUE TO CUSTOM MODS.
Don't know what to do. I've tried almost everything.
WE BEG FOR YOU HELP , PLEASE.
P.S. sorry if I have mistaken the thread section or the title
Click to expand...
Click to collapse
facing exactly the same problem , any Devs kind enuff to enlighten us on this ?
No one could help?
Looks like a broken NAND(The 16GB storasge of the device) chip to me... It should be replaced with a new one to fix the problem. Repartitioning it won't fix it at all and 1 thing you've done wrong is flashing it with custom ROMs after it broke. You should have claimed warranty first before you tried the custom ROMs solution.
Now the only solution to this is approach samsung again and ask how much would it cost you replacing your S5's NAND. Nothing can be done here software wise. The explanation you made points only to this problem.
Being stuck in "Samsung Galaxy s5 powered by android" only means that the kernel won't even load at all and you flashing the kernel with stock & CM version and still encountering this issue only means it's a NAND problem.
I claimed the warranty repair before trying custom rom. I haven't had the possibility to try custom roms at all because the phone is not mine. But xtaeyeon who has the same problem did and cyanogenmod didn't boot.
Now, being you so kind giving your advice, is there any possibility to restore broken sectors on the nand? Or is there a way to have the nand chip only replaced? Do you know any repair center that can do that without buying a new motherboard?
It is so strange that it came out of nowhere exactly the same problem for me, xtaeyeon and another guy on a Spanish forum who changed the board to have it repaired.
As we are on different countries I couldn't tell if there's such a way for you to do that. Here in our country local phone technicians buy broken phones and salvage their parts to repair phones such as this. Hence if you were here I could say yes there's a way to fix it without having to replace the board.
Next is you said that you didn't flash custom ROMs on that device then why not claim for a warranty repair then? Is it out of warranty already? If it's still under warranty then I suggest you return it for replacement to them. You have every right to have it fixed for free and if they say that warranty is void because you modified the software then insist that you didn't and have a real technician from samsung decide.
As for restoring broken sectors... I don't think this is the problem at all. Cause if it is the filesystem configured on the NAND should have isolated the bad sectors automatically and allocate the files to good sectors indeed. I believe that the NAND chip here is totally broken like when you transfer files in there the file you transferred gets corrupted.
oile said:
I claimed the warranty repair before trying custom rom. I haven't had the possibility to try custom roms at all because the phone is not mine. But xtaeyeon who has the same problem did and cyanogenmod didn't boot.
Now, being you so kind giving your advice, is there any possibility to restore broken sectors on the nand? Or is there a way to have the nand chip only replaced? Do you know any repair center that can do that without buying a new motherboard?
It is so strange that it came out of nowhere exactly the same problem for me, xtaeyeon and another guy on a Spanish forum who changed the board to have it repaired.
Click to expand...
Click to collapse
Samsung said it is out of warranty because of Knox 0x1 and "custom" condition of binary and system. But it was never Flashed with anything different than the lollipop ota.
I don't know what to do. If it really is the new motherboard, my fiancé cannot afford it cause the Galaxy s5 was a gift. :/
oile said:
Samsung said it is out of warranty because of Knox 0x1 and "custom" condition of binary and system. But it was never Flashed with anything different than the lollipop ota.
I don't know what to do. If it really is the new motherboard, my fiancé cannot afford it cause the Galaxy s5 was a gift. :/
Click to expand...
Click to collapse
If you live in the EU the knox thing is irrelevant, they're required to service you anyway by law.
You have a right to flash the OS of your choice in EU. Sometimes they try to get rid of customers, basically they have an unofficial policy of avoiding giving you free service when possible. You just need to literally tell them you won't take no for an answer (this makes miracles happen) and that you won't leave until you get the service they owe you.
But if you live outside of EU, well, then I don't know.
Has anyone run into this problem before?
I can't use Samsung Pay. The app "Knox Status for Samsung" shows my phone is still 0x0 (Knox has not been tripped).
When I try to use Samsung Pay, I get "Connection error: Failed to connect to server. Try again later". This has been happening for a couple weeks.
I tried using Odin to go back completely to stock and still nothing. On some attempts on different Official Firmwares, I've gotten the error message: "Access denied: unauthorized modifications have been made to your device".
I called Samsung and talked to support who was of no help and who said I'd be contacted within a couple days. That was over a week ago and they never got back to me.
Edit: Just a side note, the "My Knox" app tells me my phone is not compatible with it.
Has anyone ever run into this problem?
I've sorta noticed this too. Not too your extent. (never used "Samsung pay" nor "my Knox", myself.) But I think the recovery stays set for "hero" or something after we've flashed the eng boot. Even after stock kernel
Maybe it's just me..