Related
I have a Canadian Telus GS4 running SlimKat, and would like to return it to stock for a warranty replacement on the "SIM card not detected" issue that I'm having.
I would like to confirm that the steps I am taking to do so are correct and possibly get some help troubleshooting some issues I am having along the way.
Step 1:
Download stock firmware from this thread http://forum.xda-developers.com/showthread.php?t=2269304
Step 2:
Download Odin 3.07 from this thread http://forum.xda-developers.com/showthread.php?t=2258628
Step 3:
Flash stock firmware via Odin.
Now on to the Questions and issues I am having.
Question 1: Is it necessary to reset the binary counter to 0? If so, then what are my options?
I understand that Triangle Away will do the trick, but it warns that I must be using a stock kernel to be safe. I am currently running SlimKat. Do I need to return to stock using the above method, then re-root, then use Triangle away...THEN return to stock again? This feels like the long way around, are there other options?
Question 2: Does it matter which stock firmware I flash via Odin?
According to http://www.sammobile.com/firmwares/1/?model=SGH-I337M&pcode=TLS#firmware there are 3 options of stock firmwares. Is the latest (from the link I pasted above in my "Step 1") alright, or should I go back to 4.2?
Thanks for checking this out! Hopefully this can help others with the same problem.
L_B said:
I have a Canadian Telus GS4 running SlimKat, and would like to return it to stock for a warranty replacement on the "SIM card not detected" issue that I'm having.
I would like to confirm that the steps I am taking to do so are correct and possibly get some help troubleshooting some issues I am having along the way.
Step 1:
Download stock firmware from this thread http://forum.xda-developers.com/showthread.php?t=2269304
Step 2:
Download Odin 3.07 from this thread http://forum.xda-developers.com/showthread.php?t=2258628
Step 3:
Flash stock firmware via Odin.
Now on to the Questions and issues I am having.
Question 1: Is it necessary to reset the binary counter to 0? If so, then what are my options?
I understand that Triangle Away will do the trick, but it warns that I must be using a stock kernel to be safe. I am currently running SlimKat. Do I need to return to stock using the above method, then re-root, then use Triangle away...THEN return to stock again? This feels like the long way around, are there other options?
Question 2: Does it matter which stock firmware I flash via Odin?
According to http://www.sammobile.com/firmwares/1/?model=SGH-I337M&pcode=TLS#firmware there are 3 options of stock firmwares. Is the latest (from the link I pasted above in my "Step 1") alright, or should I go back to 4.2?
Thanks for checking this out! Hopefully this can help others with the same problem.
Click to expand...
Click to collapse
I had the exact same issue with the sim slot. But having the AT&T variant and MDL firmware is a rarity. If I sent mine into Samsung they would upgrade my bootloader to the more secure on and give me the official 4.3 update. I didn't want to loose my custom recovery, so I took it to a local iFixit workshop. Know the guy there and he fixed my iPhone 4S a few years back. Said it would be no problem for him to replace my entire sim slot for $10.
Hopefully you can find someone locally to do this for you. If you send your phone in, count on it coming back with a more secure bootloader (knox).
MattMJB0188 said:
I had the exact same issue with the sim slot. But having the AT&T variant and MDL firmware is a rarity. If I sent mine into Samsung they would upgrade my bootloader to the more secure on and give me the official 4.3 update. I didn't want to loose my custom recovery, so I took it to a local iFixit workshop. Know the guy there and he fixed my iPhone 4S a few years back. Said it would be no problem for him to replace my entire sim slot for $10.
Hopefully you can find someone locally to do this for you. If you send your phone in, count on it coming back with a more secure bootloader (knox).
Click to expand...
Click to collapse
I am quite uneducated on the knox bootloader. I understand what it is but I didn't know it would be on the Telus firmware. A quick google search shows that it would be around 15 bucks for me to get the SIM slot fixed up. Not a huge deal...but my phone is still under warranty.
EDIT: Update - I replaced the SIM card reader in the phone and am still having the SIM card undetected issue. Either I received a faulty SIM card reader, or there are other issues with the phone.
L_B said:
I am quite uneducated on the knox bootloader. I understand what it is but I didn't know it would be on the Telus firmware. A quick google search shows that it would be around 15 bucks for me to get the SIM slot fixed up. Not a huge deal...but my phone is still under warranty.
EDIT: Update - I replaced the SIM card reader in the phone and am still having the SIM card undetected issue. Either I received a faulty SIM card reader, or there are other issues with the phone.
Click to expand...
Click to collapse
Then you might want to send it in to Samsung. I'd rather you have a phone lol. I believe the 4.3 update will only give you knox, which keeps track of custom firmware. Your bootloader will not be locked. Sorry for the confusion.
MattMJB0188 said:
Then you might want to send it in to Samsung. I'd rather you have a phone lol. I believe the 4.3 update will only give you knox, which keeps track of custom firmware. Your bootloader will not be locked. Sorry for the confusion.
Click to expand...
Click to collapse
I do plan on sending it in but am having trouble returning it to stock... :S never had to do it before and Odin is giving me trouble
EDIT: Update - my Odin was freezing at "SetupConnection" for the longest time. Went to a different computer and it worked... flashed MK6 firmware (might have been a mistake to pick mk6?) but not the phone is back to stock and knox counter is at 0x0.
L_B said:
I do plan on sending it in but am having trouble returning it to stock... :S never had to do it before and Odin is giving me trouble
EDIT: Update - my Odin was freezing at "SetupConnection" for the longest time. Went to a different computer and it worked... flashed MK6 firmware (might have been a mistake to pick mk6?) but not the phone is back to stock and knox counter is at 0x0.
Click to expand...
Click to collapse
Well my point was that once you get the phone back from Samsung, they will always know if you flash a custom recovery by the knox. Unless your phone had knox before? But if its at 0x0 you have nothing to worry about.
MattMJB0188 said:
Well my point was that once you get the phone back from Samsung, they will always know if you flash a custom recovery by the knox. Unless your phone had knox before? But if its at 0x0 you have nothing to worry about.
Click to expand...
Click to collapse
I need to do more reading on knox, but I didnt see anything about the knox flag in download mode when I was on the custom firmware and recovery, I think going from custom to the most recent MK6 firmware for the I337M put the indiciation there.
Thanks for your help.
It's also interesting to point out that since I flashed back to stock with odin, my SIM card issue has gone away for the time being. I'll update if it comes back haha.
I dont understand way they would deny a warranty on a phone that has a non-standard rom on it.
I mean if the sim slot is bad, its bad - not that some app made it bad, or the removal of ATT Navigation software caused it to break.
*yeah yeah I know, in the EULA it states stuff about circumventing the OS voids warranty
It just seems anal to spend a lot of time examining the entire OS and partitions when they can just toss in a sim card and recreate issue and just fix it.
...then again, I am not Samsung
atari800 said:
I dont understand way they would deny a warranty on a phone that has a non-standard rom on it.
I mean if the sim slot is bad, its bad - not that some app made it bad, or the removal of ATT Navigation software caused it to break.
*yeah yeah I know, in the EULA it states stuff about circumventing the OS voids warranty
It just seems anal to spend a lot of time examining the entire OS and partitions when they can just toss in a sim card and recreate issue and just fix it.
...then again, I am not Samsung
Click to expand...
Click to collapse
I was under the impression that if the knox counter read 0x1 than they would not touch the phone, regardless if you touched it or not.
I have not seen a post that someone's phone was returned not fixed with a note/reason that the phone was modified outside of specification. Also imagine a dumpster of fixable phones that are untouched due to knox flag was triggered?
atari800 said:
I have not seen a post that someone's phone was returned not fixed with a note/reason that the phone was modified outside of specification. Also imagine a dumpster of fixable phones that are untouched due to knox flag was triggered?
Click to expand...
Click to collapse
Wasn't that the whole point of knox? If it reads 0x1 then the warranty is void?
Knox is an overall security layer, helping promote Android devices in the workplace.
For more info - read this
atari800 said:
Knox is an overall security layer, helping promote Android devices in the workplace.
For more info - read this
Click to expand...
Click to collapse
Well the knox flag in download mode is... "knox warranty void"
That's how it reads, or something like that.
True it can show that, but outside of chainfires explaination of how it is blown and "what has been hearing about Samsung service centers". If you read his article, there is a lot of maybes, mights, and even ends his article with "take it with a grain of salt".
Their are a lot of mad people in his chat, but I didn't find anyone saying they got denied. Samsung can do what they want, but they know word of mouth is as big as advertising is. One person saying "I installed a program, it broke is my phone and Samsung is not honoring the warranty" has a huge impact on people regardless if they know and/or understand rooting.
Knox security void can mean the phone can no longer be certified for enterprise grade applications or environments. That the security mechanism is tainted thus considered broke and not repairable.
Just my point of view - I have total respect for chain fire
Edit: Additional info
The Magnuson-Moss Warranty Act (1975) says that to refuse warranty, the company must prove that the problem with phone (or any other device that fails) was the caused by the customer.
So a defective sim card reader (unless obviously damaged by a consumer) should be covered where a modified corrupted partition table causing a boot failure (and also not a wide spread incident) may not be covered as this is more of a damage from a "non-friendly" application caused by the consumer.
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
pworcester said:
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
Click to expand...
Click to collapse
OK. It took me from ANF4 to ANI1!
pworcester said:
OK. It took me from ANF$ to ANI1!
Click to expand...
Click to collapse
and from ANI1 to ANK1! Sweet!!
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
yes it just causes to end your guarantee in case you take it to samsung service
benveq said:
yes it just causes to end your guarantee in case you take it to samsung service
Click to expand...
Click to collapse
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
pworcester said:
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
Click to expand...
Click to collapse
Its good to get more confirmation, in any case. There seems to be a good amount of mixed info about KNOX. So thanks for posting it.
redpoint73 said:
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
Click to expand...
Click to collapse
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
thebobmannh said:
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
Click to expand...
Click to collapse
You're right, I wasn't completely clear on the details of the situation (once modded, I don't believe in OTAs) so thanks for clarifying.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
pworcester said:
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
Click to expand...
Click to collapse
Again, thanks for the clarification.
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Sent telepathically
RiverCity.45 said:
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Click to expand...
Click to collapse
Weird, all I did was root my T900 (via Odin), without installing a custom recovery, and was subsequently unable to take an OTA. I didn't really mess with it after that -- I switched to CM shortly after -- but that was my very limited experience. Could have been a fluke.
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
RiverCity.45 said:
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
Click to expand...
Click to collapse
Great info, thanks! THis is my first Samsung / Knox device so still learning the basics.
Would it be safe to dirty flash (flash without wiping /data, only /cache and dalvik) latest stock ROM over older stock ROMs (modified with custom recovery)?
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
cmstlist said:
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
Click to expand...
Click to collapse
Yep. You can get a stock ROM and flash it with ODIN. Knox won't be tripped and you will loose root. Other thing you can do is stay rooted, and flash with ODIN the new ROMs as soon as they are available. Instead of re-flashing the same ROM you are on right now, so you can get an OTA, why not wait until a new ROM is released and flash that new ROM then? You can reroot then, if you want (towelroot). Of course you have to keep an eye on the forum so you know when a new ROM is available. Or check samfirmware from time to time :good:
Good to know. I don't know if Lollipop is ever on the agenda for Tab Pro, but if so I'd imagine there won't be a way to get it Towelrooted.
HELP!!! U.S. version of sm-T520
I have the Sm-T520nzwaxar. I needed to flash a firmware to revert it to stock. I was aware of the region based firmwares, but I still flashed one. The process failed near the end. Odin said "Failed" and my tablet remained in download mode, didn't boot. Now, I have a tablet that is pretty damn bricked. It will only go to a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and Download Mode.
I have determined that there is no such firmware for T520nzwaxar, despite being the U.S. model. The only thing I can hope for now is that such a file does exist or another firmware from another country would work.
PLEASE any help that can be given to a frimware that would work with this would be HUGELY appreciated.
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Reflashing stock rom and without root your device again.
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Wow
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
Deroot your device and flash stock rom..... try and post your feedback here
Joku1981 said:
Reflashing stock rom and without root your device again.
Click to expand...
Click to collapse
more instructions please,how to reflashing ?
VaRyOss said:
more instructions please,how to reflashing ?
Click to expand...
Click to collapse
You can easily search on the q&a section on how to reflash your phone. But if you don't know how to do that, I suggest you read a LOT before you attempt to reflash.
Your original post shows that you have absolutely NO idea about how to do anything to your phone and keep it in a working state, or what any modification implies.
If you lost knox, there is absolutely NO way to get it back. Reflashing to stock will have NO impact on the state of the knox. If the knox flag is triggered, then your knox apps have stoppped functioning and, like I said before, there is ABSOLUTELY NO WAY to reverse that.
I really don't know why the others told you to reflash to stock. I thought it was general knowledge that once you lose knox, it cannot be reversed and you also lose the knox apps.
I know i repeated myself a couple of times, but with your kind of people, repetition is the only way to make oneself understood.
Good luck dude!
VaRyOss said:
Hy,i recently root my samsung note 3 sn9005 and after that i see KNOX it wasnt work annymore,i can open the aplication,the loading screen apper but then sudenly it just close...anyone know how to fix this?
Click to expand...
Click to collapse
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.
ShadowLea said:
To my knowledge every Root related thread mentions, very explicitly, that rooting prevents you from using the KNOX app.
Which makes perfect sense, since KNOX is a security container meant for storing secure data. Once you root, no part of the device is truly safe from tampering.
Once the KNOX flag is 0x1, The KNOX app is disabled and can not be restored. If you want to use KNOX, I'm afraid you'll have to buy a new device. The 0x1 flag can't be reset.
Click to expand...
Click to collapse
uhmm....k..i understand that. there is another app. similar to KNOX?
i find a app. in magazin play called "Knoxx",work's close anought for me. For people who want to know is the one with a yellow K
I have a Verizon S5 that currently has g900VVRU1B0A8 on it.
Recently the screen has started flashing green and not coming on whrn the power button is pressed.
Im not sure if this is hardware or software so I factory reset it and the issue is still there, maybe not as frequent though.
Do you think it would do any good to upgrade it, can i just odin a new firmware on now, as long as im not going backwards?
If this is a stock factory phone that has never been rooted I would venture a guess that your phone is failing from a hardware standpoint. If it is still under warranty I would replace it before trying any rooting/flashing ... If you want to root it however, DO NOT take the OTA upgrade. That will put you on the latest build but you will not be able to go backwards and root it after taking the update. The version you are currently on can be rooted. And no, you can not just flash a new firmware. If you want to root, you have to follow the steps in the rooting threads and revert back to NCG first to root. Don't flash anything without reading everything thoroughly and understanding what you are doing BEFORE you flash anything.
Oh, its been heavily screwwed with, used to be mine but i gave it to my wife.
Knox is tripped and it says custom on boot.
I took it back to stock when i gave it away....just thinking a updated driver may help.
Been out of the scene for awhile, what are my options?
f4u5t said:
Oh, its been heavily screwwed with, used to be mine but i gave it to my wife.
Knox is tripped and it says custom on boot.
I took it back to stock when i gave it away....just thinking a updated driver may help.
Been out of the scene for awhile, what are my options?
Click to expand...
Click to collapse
Just because it says custom on boot doesn't really mean knox is tripped. All my earlier root versions said that without being tripped. Download the Samsung phone info app from the play store. Run that and if knox says 0x0 it is not tripped. It doesn't really matter though if the phone is out of warranty.
This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
JMBush1007 said:
This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
Click to expand...
Click to collapse
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
gunz.jones said:
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
Click to expand...
Click to collapse
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
JMBush1007 said:
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
Click to expand...
Click to collapse
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
gunz.jones said:
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
Click to expand...
Click to collapse
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
JMBush1007 said:
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
Click to expand...
Click to collapse
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
gunz.jones said:
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
Click to expand...
Click to collapse
Alright, thanks for the reassurance.
Unfortunately, after apparent successful attempts using odin, the phone is still exhibiting the same behavior with closed app notifications, not showing the keyboard at times, and restarting. Guess I will be make a service request tomorrow, unless you have any other ideas?
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
CVertigo1 said:
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
Click to expand...
Click to collapse
I tried flashing QC5 a few different times, and also QA4 after that, and it just kept rebooting after the initialization screen. I loaded all 4 files, and got (1 succeeded / 0 failed) message from odin each time.
However, just now I went on Verizon's support chat to get a warranty replacement issued. I entertained Jennifer, the tier two from the windy city, and booted up in safemode. Everything seems to be working fine now! Although I did get a few close app notifications after changing from high performance mode to optimized.. but the phone is still up and running fine since then. I've been able to text and make calls for the first time since running the update yesterday morning. I'm hoping everything stays stable.
Also, I'm wondering whether it makes sense to try running the update again through the phones system update mechanism.
Thanks for the help!
The only option now is to force factory reset and clean out everything after flashing
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
CVertigo1 said:
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
Click to expand...
Click to collapse
Yes, yes, and yes. I did a factory reset and everything has been erased. I tried using both at different times. My last one was with QA4, and I used CSC_VZW iirc.
My phone is still going strong with no reboots since I started it up this morning!
Welp, things still seem to be running smoothly.
I do keep getting update notifications though. I'm tempted to press my luck and install the update.
Opinions? I'd be a lot more confident had it started working immediately after I flashed with Odin. The fact that I finally turned it off for the night after it cycled through several boot loops with different installs makes me wonder what the problem/solution actually was.
I guess I'll try it. It is still under warranty, and would probably be best to find out if there's an issue with it now rather than later.
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
iBolski said:
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
Click to expand...
Click to collapse
Yup, ran the update and everything is good!
Thanks for all the help, everyone.