[Q] How to tell if I tripped flash counter? - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

Hi.
I recently unrooted my girlfriend's Sprint S4 and she wants to trade it in for a new S4 via insurance because the screen is cracked but how can I tell if I tripped the flash counter and if Sprint would be able to tell that it was at one time rooted? Or will I be alright? How can I tell/what do I need to do?
Thanks!

Go to your About phone in settings and then click status and scroll to the bottom and see if it says custom or official that is the first thing that sprint might see that it has been rooted. Also check your bootloader and see if it says custom/official and all this can be reset with triangle away except for the KNOX count but i dont think that will matter as long as the rest has been reset.

If you're filing an Assurion claim, I've returned 2 rooted phones running custom software and never had a problem. A cracked screen isn't caused by rooting.

Related

[Q] Root Question related later ota

after a few hours searching, I am still a bit confusing on following question:
1. trip rootchecker
If I do not choose do this during rooting, in other word, I only have adb shell root.
a) should I still be able to install twrp and flash other rom? my impression is "yes", am I right?
b) But if I choose do this, then my warranty is gone. If I later flash back the stock,
will this be wiped and "forget"? i.e. the warranty is back?
Or is this "root checker" will send somthing to LG once it is tripped, hence warranty
is permanently voided?
2. ota
It seems once rooted, one can not take any ota, right? even the kitkat in future?
would "trip rootchecker" matter in this case?
even though thanks to thecubed, it seems we do have a solution.
If you choose not to trip the root checker, root will not work properly and neither will the apps that require it.
It doesn't send any info to LG or your carriers. All it does is... If in the future you break your phone somehow and take it into your carrier store to get it fixed, they will check the phone to see if it's ever been rooted. If it's been tripped, it'll give a number code on the screen to tell them it either was rooted in the past but isn't anymore, is currently rooted, or was never rooted.
Then it will be at the store's discretion on whether or not they'll help you out or make you pay full price to fix it or get it replaced.
I don't know how it is for the G2, but I know awhile back some newer HTC phones got S-OFF which allowed them to reset the root checker to make the device think it's never been rooted. Our phones may have a similar method out there somewhere... Though probably not as it'd be fairly big news. I am however, willing to bet that there is a crack team or two working on disabling that for our devices.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

[Q] Bell apps show up on my Rogers phone

Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
rezadue said:
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
Click to expand...
Click to collapse
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Gage_Hero said:
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Click to expand...
Click to collapse
rezadue said:
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Click to expand...
Click to collapse
You have to go into download mode to see the text.
Sent from Black<3's I337 running Foxhound ROM
Put the phone in download mode and no small text.
Now that the phone is not rooted, can I put it in download mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
rezadue said:
Oh, and one other question. Now that the phone is not rooted, can I put it in recovery mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
Click to expand...
Click to collapse
Not to ODIN it no. Root not required.
Found the other thread, you have spoken of. It seems like that guy got bloatware from Bell INSTEAD of Rogers. I have blaotware from Rogers(ok
) AND Bell(Not ok).
http://forum.xda-developers.com/showthread.php?t=2422497
Almost same issue here on my N900W8. My phone is working fine and rooted, except I got the Rogers AND Bell apps too before rooting and flashing CWM (only way I knew of at the time to force boot following seandroid enforcing error). I data wiped, downloaded and flashed the labeled "Rogers" stock ROM from SamMobile, and first time I ever saw bloatware from two carriers on any phone.
I disabled the Bell apps thinking that was all, but instead of 4G, I get H+. LTE connects fine outdoors, but H+ seems slightly slower than the 4G I'm used to. Which makes me wonder if LTE speeds are impacted too, hope not. Anyway, it's a bother because I am rarely in an LTE zone.
Tomorrow, I will try unrooting with SuperSU (is this even important if I'm wiping & flashing?), data wiping with CWM, re-flashing same file from SamMobile and not flashing anything more, and trying emergency recovery with Kies. Anyone know if this will work or change anything in the end? Or is Kies 3 also affected by the Knox counter? CSC (OYA) is the same as the non-rooted up-to-date S4 in the house.
Thanks
OP, have you tried using someone else's SIM card? Just a thought.

Help with messed up phone

Let me first off say in download mode somehow i believe ive tripped knox... my Knox warranty void is set to 0x1 and i dont think theres anything fixable there.
My main problem is im having a very hard time keeping my phone on most the time it boots in and freezes shortly after seeing the screen.. sometimes making a buzzing noise out of the speaker.
I went from rooted 4.3 to the leaked NC2 and somehow picked up this problem. On friday it started the reboot crap again and said something in yellow like warrenty void : Kernel then went to a screen saying software not approved that i needed to take it to a VZW store. Im back to 4.3 currently and rooted with the problems still existing.
I dont mind the tripped knox as long as i can figure out the rebooting... Im just about to the point of opening another line just to get a new phone since i have no insurance on this one
UrGonnaDie said:
Let me first off say in download mode somehow i believe ive tripped knox... my Knox warranty void is set to 0x1 and i dont think theres anything fixable there.
My main problem is im having a very hard time keeping my phone on most the time it boots in and freezes shortly after seeing the screen.. sometimes making a buzzing noise out of the speaker.
I went from rooted 4.3 to the leaked NC2 and somehow picked up this problem. On friday it started the reboot crap again and said something in yellow like warrenty void : Kernel then went to a screen saying software not approved that i needed to take it to a VZW store. Im back to 4.3 currently and rooted with the problems still existing.
I dont mind the tripped knox as long as i can figure out the rebooting... Im just about to the point of opening another line just to get a new phone since i have no insurance on this one
Click to expand...
Click to collapse
yeah knox is tripped did you update the bootloader like required to go to the leaked nc2? i would try loading a nc2 rom again follow directions.

[Q] Reading the custom binary counter

Hello all, I've got a AT&T S4 sgh-i337 with the locked mk2 bootloader. Bought new, still under warranty (well.. supposedly
I'm trying to go back to bone stock to return it; I think I did because when going into odin download mode, I see the following:
PRODUCT NAME: SGH-I337
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
I did lots of reading and found some info I don't completely understand (go figure haha). I read that even when the S4 does not DISPLAY the binary counter, said counter is still there and reviewed when the phones are returned.
My 2 questions are...
1) if the custom binary counter is indeed there, is there an adb shell command I can run to READ the counter?
2) if the binary counter is there and I need to reset it... will the triangle away method work with my locked (and "unlockable" mk2 bootloader? -- under supported devices for triangle away, I see "Samsung Galaxy S4 AT&T SGH-I337 UNLOCK BOOTLOADER".. I'm afraid they meant to say "UNLOCKED" bootloader... in which case, I'd be out of luck.
Thanks a bunch!
R
No one knows? any info or guidance? Thanks
The following is just my opinion.
Both Samsung and AT&T offer a 1 year warranty on the Galaxy S IV phones. Since you are on MK2, I would guess your phone is at least 1-1/2 years old, so any worry about the warranty is pointless, since the phone is no longer under warranty.
You want to return the phone to AT&T? If that is the case (you don't state where) then the likelihood of anyone checking any of the counters is extremely unlikely, let alone any hidden counter, if it exists.
In my opinion, I wouldn't worry about it. Just flash it back to full stock, whichever version you can put your hands on, and you'll be fine.
creepyncrawly said:
The following is just my opinion.
Both Samsung and AT&T offer a 1 year warranty on the Galaxy S IV phones. Since you are on MK2, I would guess your phone is at least 1-1/2 years old, so any worry about the warranty is pointless, since the phone is no longer under warranty.
You want to return the phone to AT&T? If that is the case (you don't state where) then the likelihood of anyone checking any of the counters is extremely unlikely, let alone any hidden counter, if it exists.
In my opinion, I wouldn't worry about it. Just flash it back to full stock, whichever version you can put your hands on, and you'll be fine.
Click to expand...
Click to collapse
Thank you very much for taking the time to reply creepyncrawly! Much appreciated.
I was going to return it to Samsung as I bought it refurbished at BB a couple months back.. I believe they honor the 1hr warranty on factory refurb phones (but I might be wrong)
Anywho.. I kept working on it, testing new stuff, different stuff and finally was able to get everything working nicely by forcing it to take the I337UCUFNB1 upgrade.
Thank you again, cheers!

[Q] Custom rom install history - Samsung Warranty Service - i9505

Hi.
I can't find answer to this. I know that triangle away delete the number of installed custom roms but does they have any way to check that i had custom roms? I know the issues with samsung and warranty policy so i want to be sure that i can fight back if they refuse to fix my phone because of knox. (overheating) If they do this, this will be my last samsung phone.
Triangle Away worked when all the S4 had was the flash counter, but it doesn't do anything when it comes to the Knox flag. Once the Knox flag is tripped by installing a custom recovery, it stays tripped. There is no way to reset it. So Samsung has an easy way to check.
If warranty is a concern, there are ways to root that do not trip the flag. However, you're stuck with Touchwiz.
Strephon Alkhalikoi said:
Triangle Away worked when all the S4 had was the flash counter, but it doesn't do anything when it comes to the Knox flag. Once the Knox flag is tripped by installing a custom recovery, it stays tripped. There is no way to reset it. So Samsung has an easy way to check.
If warranty is a concern, there are ways to root that do not trip the flag. However, you're stuck with Touchwiz.
Click to expand...
Click to collapse
Oh i know it (i used to change firmware on old sony ericsson phones). I can lie about the knox since some people get it changed by samsung tools, thats why im asking if they have any other way than knox, like under bootloader. My phone is overheating because of hardware problem, i want to be prepared for service reject (stories about rejecting repair of defective screen etc.).
They might not even check the flash counter. You can give it a shot. The worst that might happen is that they send it back (Unless they repair it without consulting with you and charge you for it).
My phone also gets pretty hot when playing games and the phone is charging at the same time. It burns my finger if I keep it in one place, literally.
I guess that's how they intended it to work..
@VanHelsing091: I misunderstood your question. Sorry about that. As GDReaper points out, they may not even check for a tripped Knox flag. If they don't, there's really no way we know of that they can tell if the device has had a custom ROM flashed.
@GDReaper
But mine is getting 50 degrees on main screen, watching photos etc. over 65 while doing anything else, over 70 while charge and using chrome even on locked cpu clocks under 1300mhz.
@Strephon Alkhalikoi
Thanks. If they refuse to repair my phone on warranty because of knox - that will be a lie (damaging phone by custom rom... sure, without touching OC in kernel tools), so i wanted to be sure if i can lie too about phone history, it happened before triggering knox anyway.
Im hoping for the best and good service, if not then i may start one of those big posts about company vs user. Thanks again.

Categories

Resources