So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I rooted the phone with activeroot (still on 4.2.2 stock rom) and have since unrooted it with superSU.
I am having problems with the touchscreen and samsung has confirmed warranty coverage and gave me a shipping label but I want to be totally sure it a-ok before I send it in.
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also the status says custom? When the phone WAS rooted it said official ??? seems bass ackwards.
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
CaseyR22 said:
So I bought this i537 used a while back, the previous owned never registered it with samsung but I did when I bought it so I do have a warranty on it. I know it was previously rooted then unrooted before I bought it but I don't know if it ever had a custom rom on it. I have rooted the phone with activeroot (still on 4.2.2 stock rom).
When I boot into odin mode there is no KNOX status, is that normal for this device? Did 4.2.2 not come with knox on this device?
Also, I would like to reload stock 4.2.2 via ODIN just to make sure everything is kosher before sending it it, would this void my warranty?
My phone is also sim unlocked, i imagine this is okay as far as warranty goes? Would reflashing with ODIN break my sim unlock?
Thanks so much!
Click to expand...
Click to collapse
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Devo7v said:
Let's start from the top:
This phone came with MF2 (4.2.2), which was then immediately updated to MF3 (4.2.2). Both of these versions came with Knox enabled. If he just rooted then he probably didn't trip the Knox flag, but there could have been other things he did or tried to do that did trip the flag.
If it is indeed the i537, I can guarantee he did not flash a custom ROM. The i537 has a locked bootloader which means no custom recovery and no custom ROMs. However there is the ability to use TouchWiz-based ROMs, if you want to learn more about this and how it works read about SafeStrap.
We do not have official 4.2.2 stock firmware available to flash. We have a pre-release of 4.2.2, a pre-release of 4.3, official 4.3, and an OTA to go from 4.3 to 4.4.2. You can read more about the different firmwares in the i537 Firmware Thread.
Flashing firmware with Odin will erase your SIM unlock, but you can either enter the unlock code again or there are other methods that can be used. I'm not familiar with SIM unlocking so you'll have to do a little searching.
You never mentioned what you're sending the phone in for. I would try flashing the MF1 firmware first to see if it's a software issue. If it's a hardware issue then unfortunately you'll have to send it in.
Click to expand...
Click to collapse
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
CaseyR22 said:
Thank you for the quick response. I edited the first post to add more details but you must've already quoted me before I hit send.
Basically the problem is the screen will randomly detect 1, 3 or 5 nonexistent touches across the center of the screen (confirmed by enabling "show touches" in the developer options). While this is happening the touchscreen becomes unusable, rebooting several times will eventually fix it but the problem comes back randomly, sometime within a couple minutes and sometimes after several hours.
I did confirm my device is running MF3 and it is absolutely a i537. I'm using the phone on straight talk not ATT so I have not received any OTA updates beyond this point.
So,anyhow I understand I can fix the device status:custom with triangleaway but I don't understand why there is no KNOX counter in ODIN mode and how this may effect my warranty.
Also, if I did ODIN to 4.3 or 4.4 would this trip the knox counter? (Assuming it isnt tripped already).
Thanks for your input, truly appreciated!
Click to expand...
Click to collapse
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Devo7v said:
It sounds like it might be a software issue so it would be worth it to try to flash the official 4.3 firmware. Flashing official firmware shouldn't trip the Know flag, but I'm not really an expert on Knox. I have read that Knox being tripped doesn't affect warranty repairs.
Click to expand...
Click to collapse
Thanks, I went ahead and flashed 4.3 via ODIN and the KNOX status is showing 0x0 so that is a good sign. Has only been about a half hour so I cant say whether or not the touchscreen issue is fixed yet but I will post back and update what happens after a day or so.
Another plus is the update finally got rid of that god awful default font on 4.2 (changing the system font wouldn't change the fontface for plain text in the browser).
Quick update in case anyone is having a similar problem with "phantom touches" in the future.
After flashing to 4.3 the touchscreen problems have continued so i do believe it is a hardware problem that will require disassembly to fix.
Also the phone keeps trying to download the OTA update to 4.4 but I've heard bad things about the update so far so I've left my wifi turned off.
Going to be stuck using a windows 8 phone for a week or while my phone is out for warranty repair.
There is an app in the play store called phone info. There it tells you your knox status without root or being in download mode.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
One final update in case anybody runs into similar problems in the future. Samsung confirmed it was a hardware problem and fixed the phone 100% free of charge under warranty.
It appears they replaced everything which is pretty awesome because I now have a brand new digitizer and bezel without a single scratch or scuff on them. Also my usb port cover flap was feeling pretty worn/sloppy so now thats new and even the USB port itself looks brand new which tells me the motherboard was replaced. I can tell they peeled the old serial/IMEI sticker off the old phone and stuck it on this one.
Surprisingly they didn't update it to 4.4 while it was there which kind of sucks because I'm nervous about doing it myself after reading horror stories on the forums.
Anyway I'm very pleased with Samsung's support!
Related
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
RobbieHag said:
This is my first Android phone i have owned for a few years now and i made the mistake of doing the OTA update to 4.3. I would love to root this phone because that was a big reason why i got it. I hated waiting for a jailbreak for my iPhone and i want a phone that i have control over. is it possible to "downgrade" from the OTA update to the leaked update? or even downgrade back to 4.2.2? I have looked around but cant find anything to helpful for the galaxy s4 active. also reading around multiple people say they end up having issues after downgrading or the KNOX counter going from 0x0 to 0x1, therefore voiding warranty.
Click to expand...
Click to collapse
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Devo7v said:
While the OTA upgraded Android to 4.3 it also included a new bootloader. The new bootloader prohibits "downgrading" to a firmware version below ML2. Currently there is no way to downgrade with the locked bootloader. However there is a new thread just started by @TransformixS4 that is looking at injecting root into the ML2 Odin files, so it may be possible in the future to root ML2. There are a couple threads in the regular S4 forums exploring ways to exploit the bootloader and flash custom kernels.
Back to your situation: you're completely stuck. Next time you see there is an update or OTA check XDA before you install it. There are a couple threads that explain the pros and cons of any updates. There is also a thread summarizing all the AT&T i537 firmwares which will be updated in the future and you may find useful.
Click to expand...
Click to collapse
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
You're only allowed to delay the update 4 or 5 times before it installed automatically. You can prevent it from upgrading in the future by freezing some system apps with Titanium Backup. I don't remember which ones right now, but if you search it's pretty easy to find.
Caboose27 said:
My issue was I kept telling it not to upgrade, and then it went ahead and did it anyway! On 4G, not wifi even. I was so mad when I got home and started reading that all the stuff I downloaded to root it *that day* would no longer work.
Click to expand...
Click to collapse
Just checking, you do have the i537 not i9295, right?
Rooted the phone, decided I didn't really care or need to have a phone rooted. Phone was fine. So I decided to grab the stock ATT firmware and reload it via Odin. All goes well until the very end when the phone tells me:
SECURE CHECK FAIL : system
Pretty sure this is related to the locked boot-loader. I cannot get into recovery mode, and I cannot boot into regular android, but I can get into download mode. It just fails after nearly completing everything using different Odin versions, and I've used two different firmware files. I was on 4.4.2 and had all of the latest ATT OTA updates.
Everything is still listed as official and KNOX is 0x0 and KNOX Warranty void is 0x0. I guess Kies emergency firmware recovery doesn't work with the Note 3.
What are these Odin files, and where did you obtain them? Add far as I know there is no Odin flashable file for 4.4
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
I tried unrooted with SuperSU and it still shows custom, KNOX still shows 0x0 the real issue is how to remove customer and get back to official without bricking.
raduque said:
You're going to have to visit a Samsung kiosk at a Best Buy and see if they can fix it. If not, you're probably screwed, and will have to try for a replacement, or send to Samsung for service.
Click to expand...
Click to collapse
This was the recommendation from my local att corporate store. It's also what worked. The Samsung consultant let me restore my phone with her computer. She didn't realize how to get it into download mode. Either way, the Samsung program flashed the phone. It was super easy to use. Certainly meant for an non tech person. Same instructions as doing an emergency firmware recovery within Kies.
Hi,
Few months ago I've upgraded my 9305 to 4.3 and rooted it without a problem (and disabled KNOX)
Bulid: JSS15JI9305XXUEML8
BASEBAND:I9305XXUEMK1
KERNEL:3.0.31-2051278 [email protected]#1
Todat, I have returned to factory default, but this time I could not perform any root: Using ODIN 3.07/3.09 and CF-Auto-Root-m3-m3zh-gti9305, as well as Kingo, did not help.
Rooting process was fine and the device has restarted, but the phone was not rooted and KNOX cannot be removed
I've tried it several times, while all rooting process were reported by odin as "success" but actually, nothing.
Please advice. I'm nearly desperate...
Thanx
bubulit2000 said:
Hi,
Few months ago I've upgraded my 9305 to 4.3 and rooted it without a problem (and disabled KNOX)
Bulid: JSS15JI9305XXUEML8
BASEBAND:I9305XXUEMK1
KERNEL:3.0.31-2051278 [email protected]#1
Todat, I have returned to factory default, but this time I could not perform any root: Using ODIN 3.07/3.09 and CF-Auto-Root-m3-m3zh-gti9305, as well as Kingo, did not help.
Rooting process was fine and the device has restarted, but the phone was not rooted and KNOX cannot be removed
I've tried it several times, while all rooting process were reported by odin as "success" but actually, nothing.
Please advice. I'm nearly desperate...
Thanx
Click to expand...
Click to collapse
Hey don't know whether this might help as i am total noob but i am trying to catch up with it all. but with all the reading i have been doing to root i9305 i think this might be the best way.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249 . if i am totally off with my help i do apologise.
Good luck
Have you tried flashing a recovery and installing SuperSU
bubulit2000 said:
Hi,
Few months ago I've upgraded my 9305 to 4.3 and rooted it without a problem (and disabled KNOX)
<SNIP!>
Thanx
Click to expand...
Click to collapse
Hi, long time lurker, been on hiatus for a bit since knox came in, but looking at trying to root my current phone.
Can I ask where and how you manage to disable KNOX? I've got 4.3 with KNOX after sending in my phone for warranty repair, and didn't wish to accidently screw things up messing with KNOX.
If you can point me to the right direction so I can disable KNOX it would be awesome. as my current stock rom is crap.
Cheers,
grungypoo said:
Hi, long time lurker, been on hiatus for a bit since knox came in, but looking at trying to root my current phone.
Can I ask where and how you manage to disable KNOX? I've got 4.3 with KNOX after sending in my phone for warranty repair, and didn't wish to accidently screw things up messing with KNOX.
If you can point me to the right direction so I can disable KNOX it would be awesome. as my current stock rom is crap.
Cheers,
Click to expand...
Click to collapse
He means disabling the Knox security features I believe. Supersu does this automatically after installing and activating it.
To the best of my knowledge I still dont think anyone has found a way to disable the Knox flag in the Booltloader. So if you already have stock Samsung 4.3 on the phone, then you will get a Knox warranty void flag if you mod it.
^ Thanks for the clarification. I totally thought I missed something... lol.
Got phone at launch, rooted for awhile, bricked with custom rom. Didn't realize how much a pain in the a%^ samsung became went back to stock and left it, but tripped knox, have tried clicking software update occasionally since then, but nothing ever happens. I'm still on COF6. Does tripping knox completely kill updates? It does nothing after clicking update, thanks.
I was rooted and went back to stock and was able to update. The latest is OJ7.
carnivalrejectq said:
I was rooted and went back to stock and was able to update. The latest is OJ7.
Click to expand...
Click to collapse
Was your Knox tripped though?
Yes, several times over too because i screwed up rooting the first time and had to try again, and then i tried all the roms out while rooted. I went back to stock specifically to try to the OJ7 update when it came out.
Been on Xtrestolite for months now and at first it was great, but the battery drains quickly now, can't answer phone calls and fast charging doesn't work (works on other devices).
Basically, I want to use this thread to go back to stock: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
The MM update for T-mobile is coming out soon so I am interested in the stock version of that (so my phone calls work).
My question is basically that I updated the modem and the bootloader to the Xrestolite ROM and the ROM thinks my phone is an S6 edge (just a regular S6).
If I use ODIN to flash stock on my device, does it also flash the stock modem and bootloader for my cell phone provider as well? (USA T-Mo.)
Are there any additional steps I need to do to go back to the stock modem/bootloader/anything else? Will I be able to update to MM OTA?
darklime said:
Been on Xtrestolite for months now and at first it was great, but the battery drains quickly now, can't answer phone calls and fast charging doesn't work (works on other devices).
Basically, I want to use this thread to go back to stock: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
The MM update for T-mobile is coming out soon so I am interested in the stock version of that (so my phone calls work).
My question is basically that I updated the modem and the bootloader to the Xrestolite ROM and the ROM thinks my phone is an S6 edge (just a regular S6).
If I use ODIN to flash stock on my device, does it also flash the stock modem and bootloader for my cell phone provider as well? (USA T-Mo.)
Are there any additional steps I need to do to go back to the stock modem/bootloader/anything else? Will I be able to update to MM OTA?
Click to expand...
Click to collapse
You can restore original firmware using Samsung Kies or Smartswitch.
cwhiatt said:
You can restore original firmware using Samsung Kies or Smartswitch.
Click to expand...
Click to collapse
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
darklime said:
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
Click to expand...
Click to collapse
I have no idea. I always restored via Kies.
darklime said:
I plan on using ODIN to flash the original firmware. Does the original firmware include the original bootloader and modem or do I have to do those separately?
Click to expand...
Click to collapse
The full stock firmware package will have bootloader and modem. It will take you to basically like you just bought it except Knox will stay tripped.
Sym_Link said:
The full stock firmware package will have bootloader and modem. It will take you to basically like you just bought it except Knox will stay tripped.
Click to expand...
Click to collapse
Thanks for the reply! Since knox is tripped, will I be able to do OTA updates or download apps like Samsung Pay or Android Pay? I heard there is a method like using the app called "Triangle Away" to remove the knox tripped counter.
darklime said:
Thanks for the reply! Since knox is tripped, will I be able to do OTA updates or download apps like Samsung Pay or Android Pay? I heard there is a method like using the app called "Triangle Away" to remove the knox tripped counter.
Click to expand...
Click to collapse
You will be able to get OTA update with tripped knox if fully stock. Samsung Pay will not work if knox is tripped. Android Pay will work if not rooted( it will also work with systemless root and a couple changes to su file but then you are no longer stock and no OTA). There is currently no way of resetting knox short of replacing phone.
s89281b said:
You will be able to get OTA update with tripped knox if fully stock. Samsung Pay will not work if knox is tripped. Android Pay will work if not rooted( it will also work with systemless root and a couple changes to su file but then you are no longer stock and no OTA). There is currently no way of resetting knox short of replacing phone.
Click to expand...
Click to collapse
I'm going to try to use triangle away as an attempt to reset knox. Should I flash the stock firmware first then try Triangle away or vice-versa?
darklime said:
I'm going to try to use triangle away as an attempt to reset knox. Should I flash the stock firmware first then try Triangle away or vice-versa?
Click to expand...
Click to collapse
S6 is not listed as a supported device for triangle away. I would not waste my money trying it. Just flash stock firmware. Only loss is Samsung pay.
s89281b said:
S6 is not listed as a supported device for triangle away. I would not waste my money trying it. Just flash stock firmware. Only loss is Samsung pay.
Click to expand...
Click to collapse
That sucks. I really wanted to try it out. MM is coming out for my S6 in my country soon so I'm hoping battery and RAM management is better because recently on my ROM that was oh-so popular drains the hell out of my standby time and I cannot make/answer phone calls at times. At least I can try Android Pay. Thanks for answering my questions.