Can I get my warranty back after flashing CWM recovery
Yes, actually you can redeem warranty if you do anything to your phone including rooting, flashing custom ROMs/kernels, flashing new stock firmwares and practically anything thats related to development.
You just need to reset your bin counter and flash latest stock firmware of your region and send it to customer care, they cant even find a trace there..
hitme987 said:
Yes, actually you can redeem warranty if you do anything to your phone including rooting, flashing custom ROMs/kernels, flashing new stock firmwares and practically anything thats related to development.
You just need to reset your bin counter and flash latest stock firmware of your region and send it to customer care, they cant even find a trace there..
Click to expand...
Click to collapse
Thanks for helping me.
My Galaxy S4 stopped working and I'm planning to send it back to get a replacement. However, I rooted my phone before this happened and I'm planning to un-root it before sending it back. I was planning on using the Triangle Away app as well to reset the flash counter but apparently I need to unlock the bootloader first. I read in this thread that you can flash a recovery and root the phone at the same time.
Would using that tool help me in unlocking the bootloader so that I can use the Triangle Away app to reset the counter and un-root my phone using Odin afterwards? The topic creator mentioned that TWRP will auto-lok anything you flash and works as a bootloader unlock but can anyone confirm this? I bricked my Galaxy S3 two weeks ago and don't want to face the same problems with this newly aquired Galaxy S4.
Is it worth it to go through all the trouble to just reset the flash counter or would un-rooting the phone be enough to send the phone back for a replacement?
http://forum.xda-developers.com/showpost.php?p=42320414&postcount=2
Thanks, that guide looks really helpful. I do have one question though, it seems the Triangle Away app needs the boot loader unlocked in order to run successfully on the AT&T Galaxy S4 so what would be a good and simple way to unlock the bootloader and is there a way to check whether or not mine is unlocked? Would running the CASUAL tool take care of this (even if my device is already rooted)?
What guide/method did you use to root? Did you not use the bootloader exploit at that time?
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Un-Rooting
Zernell said:
I used the Motochopper tool located on this thread. I hadn't researched enough to know about the CASUAL tool at the time
Click to expand...
Click to collapse
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
pharrisworth said:
Go Here to unroot without flashing
http://androidtechy.com/index.php/2013-04-28-19-55-53/how-to-diy/48
Click to expand...
Click to collapse
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Un-Rooting
Zernell said:
Hmm...yeah I can see that method would probably work, but that wouldn't reset the flash counter to 0 would it? If the seller happens to notice that, then they won't send me a replacement and will probably tell me my warranty is void; hence why I'm trying to get the Triangle Away app to work but need the boot loader unlocked first in order to do that.
Click to expand...
Click to collapse
Well if all you did was ROOT the flash counter shouldn't be affected. Iused the same tool. I took the additional step of replacing Superuser with SU user. to rid myself of the "custom" unlocked symbolon boot up. However, the phone was NEVER really unlocked.
Thanks for the replies! I managed to un-root the phone by just flashing the AT&T stock firmware using Odin. Hopefully the binary counter won't be an issue.
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.
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.
Hey!
Sad to say that my trusty Note 4 which ive had since its release is being traded in for a shiney new Note 9. I got £200 as a trade in with samsung..but it clearly states that the phone must not be unlocked or tampered with..just wondering if anyone could advise me on how to return the phone so that no one will know that i unlocked it? Many thxs! ?
Afraid that the 0x1 knox will never go back to 0x0. As for the stock software, yes, it's possible to flash it with Odin.
I'm going to assume that by unlocking, you mean that you've rooted and possibly installed a custom ROM. You can revert back to stock by flashing a stock firmware with Odin, but unfortunately there's no way to reset the Knox warranty bit you triggered by booting a custom recovery and/or kernel, back to 0x0 (which is very likely to be what they will be looking at).