Upgrade from B0A8? - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

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.

Related

[Q] Returning to Stock for Warranty - Correct?

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.

[Q] Stuck w/ Set Warranty Bit: Kernel & S4 Logo

Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.
Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms

Knox Warranty Void=1 and OTA's

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.

Custom status after failed root

Hi guys, I tried to root my note 4 a couple of months ago with a one touch root app, I know it was stupid and I usually don't trust stuff like that but I thought I'd have a crack. The root attempt failed and my device kept functioning as normal so I didn't really give it a second thought, until I just realized yesterday that my phone should have updated to Melbourne by now and it hasn't, so I checked the status and sure enough it had been changed to custom. I also noticed that every time I boot into recovery it briefly says that it is updating, then says the update failed before coming up with the usual recovery menu. Is there a simple way to get back to official and get the update without wiping my device? It is not rooted, stock os and stock recovery, thanks for any help, it won't matter too much soon as I have pre ordered a note 7, but it would be nice to sort it out anyway.
since the status is already "custom", why not try root it using CF autoroot?
or if you still not sure, why not flash a stock rom using odin?
Thanks for the reply cacingbesar, I'd like to stay stock and get OTA updates, is it possible to odin flash a stock rom without rooting or wiping my phone and get official status and OTA updates back?
dicko101 said:
Thanks for the reply cacingbesar, I'd like to stay stock and get OTA updates, is it possible to odin flash a stock rom without rooting or wiping my phone and get official status and OTA updates back?
Click to expand...
Click to collapse
here is the problem : your device status is already CUSTOM.
correct me if I'm wrong, but it doesnt mean that you are using a custom ROM, its your knox that is tripped.
and because of that status, you cant get OTA.
staying with stock ROM is fine, but since knox already tripped and you cant get OTA, why not root it? optimize your phone the way you want.
or go custom ROM if you interested.
again.....correct me if I'm wrong, since I'm not a pro in this matter.

Need to return phone to original state..

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).

Categories

Resources