Related
I was just looking at the About Device/Status page, and this entry at the bottom that says that the phone has been modified. I did root so what does someone who hasn't rooted say? Did ATT just make it easy to determine if the phone's been rooted?
Sent from my SAMSUNG-SGH-I747
questions and answers, doh!
http://forum.xda-developers.com/forumdisplay.php?f=1631
Device Status: Normal
These phones have a flash counter so they can easily tell if its been modified which voids your warranty
After doing some research on rooting the SGS3, it appears that not only there is a flash counter but also the rom itself may also contain a special flag as well. So to truly be rid of the evidence of rooting, not only would you have to reset the counter (which we don't have the ability to do yet) but it looks like you would also have to reflash the full stock firmware and wipe the phone. I got that from reading about the Triangle Away app, which won't work for the US versions of the SGS3, but I think the idea may still apply.
Thread belongs in Q&A. An that's where it's going to be
So, I've noticed quite a few restrictions when using apps and it's getting on my nerves.
I've been thinking about rooting my i9505 but I'm a little concerned.
I would not like to void my warranty, as far as I know there's a way to root your device without altering the binary counter (whatever that is, not that much clarification about it), but I'd like to make a full backup of the out of the box state of the phone.
So that in case anything goes wrong or I have to send it to samsung for warranty concerns or if I simply want to, I can restore the device to 100% as it was before.
Haven't really been able to find complete guides or necessary info on this matter, any advice?
My device is a GS4 i9505.
Shebee said:
So, I've noticed quite a few restrictions when using apps and it's getting on my nerves.
I've been thinking about rooting my i9505 but I'm a little concerned.
I would not like to void my warranty, as far as I know there's a way to root your device without altering the binary counter (whatever that is, not that much clarification about it), but I'd like to make a full backup of the out of the box state of the phone.
So that in case anything goes wrong or I have to send it to samsung for warranty concerns or if I simply want to, I can restore the device to 100% as it was before.
Haven't really been able to find complete guides or necessary info on this matter, any advice?
My device is a GS4 i9505.
Click to expand...
Click to collapse
Hi,
Look HERE
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.
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.
I just picked up a brand new A710M duos and it upgraded to 6.0.1 on first use.
I don't see anything about this model here on XDA so im wondering if anyone could point out if its Rootable, bootloader unlock, etc.
Its a sweet little phone and is totally awesome looking. One of the best looking Samsung devices I've used so far.
I'm a Nexus user so I'm used to simple unlocks.
Thanks for any help provided.
you rarely have any unlocking to do with samsungs, bootloaders are 99% of the time unlocked, and flashing is piss easy
root is not really hard to achieve, the problem is, there is an eFuse inside that seems to trigger itself (KNOX) whenever you touch the sensitive partitions (system, recovery). KNOX triggered means warranty is done.
that said, you can flash TWRP with Odin, and flash SuperSU through it, and root you will have.