Database Users

About phone status:Modified.?

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

[Q] [SOLVED] Disabling "Device Status - Custom" Scanning

This question is mostly aimed at the Devs, but if there's already a thread out there, please simply point me in the correct direction - thanks.
The question: How do we disable the scan that checks /system for modifications and marks the phone as "custom" ?
Disclaimer: I'm not interested in warranty fraud - that's just silly. I just want to be able to run custom kernels or delete bloatware (instead of freezing) and still retain the nice Galaxy S4 logo on startup... not the ugly "Custom" padlock/logo.
As mentioned by @scott14719 in this post, disabling the scan altogether may cause other problems (won't know until we try?). However, it seems clear to us that this scan, upon determining that the /system is indeed customized, throws a red flag that is read by the bootloader upon next startup. My goal here would be to either disable the scan altogether, or somehow permanently disable this red flag.
Not knowing much about the scan itself, here's some more observations that might help:
Most critically, the padlock/"custom" boot screen is NOT triggered until this scan is run and the system is flagged.
The scan runs immediately upon startup and finishes within about 38 seconds of uptime. Might take longer if more files have been added to /system or if more apps are running on startup (and slowing it down).
If you quickly go look at the Device Status in About Phone within the first 38 seconds of startup, you can see that it is "scanning" at this time.
It seems that the scan does not run again until the next system startup.
A custom recovery does not trigger "custom".
A custom kernel triggers the "custom".
Freezing bloatware does not trigger the "custom".
I once uninstalled a lot of bloatware, and this triggered "custom". I haven't checked to see if it's any system apps that trigger it, or if only certain apps are monitored.
Having busybox and/or Superuser properly in-place will trigger "custom".
All this being said, can anyone offer some more insight into this scan, and more ideally: has anyone found a way to disable it?
EDIT:
Thank you everyone for your replies. I've finished a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700

I think that splash screen is compiled into the kernel or aboot on these phones but im not 100% sure, there are a few threads in the s3 area about changing the splash but it requires an unlocked boot loader.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2257058
Sent from my GT-I9505 using xda app-developers app
Try this also.

If code can be located and then changed to report "official" no matter what the scan returns, it would be a huge hurdle.

C13v3r0n3 said:
I think that splash screen is compiled into the kernel or aboot on these phones but im not 100% sure, there are a few threads in the s3 area about changing the splash but it requires an unlocked boot loader.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------
http://forum.xda-developers.com/showthread.php?t=2257058
Sent from my GT-I9505 using xda app-developers app
Try this also.
Click to expand...
Click to collapse
I believe you are correct in that the only way to remove or modify the boot screen itself would be to have an unlocked bootloader. However, I believe that we should be able to keep it from ever showing the "custom" screen, simply because it's clear that the system doesn't check for "custom" during the time that this screen is shown. Rather, it's fed by a variable or tidbit of code somewhere.
Also, regarding the thread you linked: this of course works fine... until you make any modifications to /system. I've used this method a few times myself, even. But once I uninstall masses of bloatware or install a custom kernel, this method won't work anymore until the changes are restored.
scott14719 said:
If code can be located and then changed to report "official" no matter what the scan returns, it would be a huge hurdle.
Click to expand...
Click to collapse
Without an unlocked bootloader, I believe this is the only way we can accomplish this... apart from preventing the scan to begin with, of course.

Aou, here is an interesting read that I think may, at least partly, apply to our device...
http://forum.xda-developers.com/showthread.php?p=38934760
I haven't had a chance to check the entire thread or the links within that thread but it seems like some people have already put some thought into this. Maybe something can be built on top of this.
**Edit**
It seems that we are definitely thinking about this the correct way. This is a post about the Verizon S3 bootloader unlock but the custom screen is discussed heavily between pages 7 and 12.
http://forum.xda-developers.com/showthread.php?t=1769411&page=7
post 68 seems to show exactly the point where the code for custom or official exists on that phone. I am willing to bet it is very similar on the AT&T S4. However, reading these threads shows me that some very smart guys (including Adam Outler) are way deeper into understanding this than I could ever be. Though, maybe it shows that there is hope for this after all.

Im am sure the local android badasses will figure it out, we have some beast devs around here.
Sent from my GT-I9505 using xda app-developers app

That is interesting - I jumped straight from the S2 to the S4, so I had no idea about SysScope. Out of curiosity, I froze the following two apps and restarted:
EdmSysScopeService.apk
SysScope.apk
Upon restart, I had the "Custom" status. Also, it took a lot longer for the "Device status" to finish Scanning. but now shows custom.
I'll play with this a bit more...

Aou said:
That is interesting - I jumped straight from the S2 to the S4, so I had no idea about SysScope. Out of curiosity, I froze the following two apps and restarted:
EdmSysScopeService.apk
SysScope.apk
Upon restart, I had the "Custom" status. Also, it took a lot longer for the "Device status" to finish Scanning. but now shows custom.
I'll play with this a bit more...
Click to expand...
Click to collapse
Another interesting post...
http://forum.xda-developers.com/showpost.php?p=29227801&postcount=107
and
http://forum.xda-developers.com/showpost.php?p=29244923&postcount=109
Again, this is not from our phone but it seems pretty damn close. This post is from the second link I posted above.

scott14719 said:
Another interesting post...
http://forum.xda-developers.com/showpost.php?p=29227801&postcount=107
and
http://forum.xda-developers.com/showpost.php?p=29244923&postcount=109
Again, this is not from our phone but it seems pretty damn close. This post is from the second link I posted above.
Click to expand...
Click to collapse
It might still be applicable. Going to bed for now, but it sounds like the devs in this thread you linked to have managed to accomplish exactly what I'm after here. I wonder if any of them have posted more details elsewhere...

Again from the Verizon S3 thread...
http://forum.xda-developers.com/showthread.php?t=1781471
This has more to do with the counter, but the areas of code are the same.
Of course, that is if the Verizon S3 has a similar code as the AT&T S4.
**EDIT**
Some more information about Sysscope from the Note II forum. This just helps to show what it scans and why it returns "custom". The code will still need to be located and modified for the S4 (similar as described in one of the links I posted in one of my above posts about the S3) in order to keep the phone as "official".
http://forum.xda-developers.com/showthread.php?t=2285894
This post also helps to show why just freezing, deleting, or modifying syscope will still return a "custom" status. Other processes are at work to make sure syscope is authentic. That is why the code which decides what is returned (after the scan) needs to be modified.

TRY THIS: http://forum.xda-developers.com/showthread.php?p=42062451#post42062451

Aou said:
This question is mostly aimed at the Devs, but if there's already a thread out there, please simply point me in the correct direction - thanks.
The question: How do we disable the scan that checks /system for modifications and marks the phone as "custom" ?
Disclaimer: I'm not interested in warranty fraud - that's just silly. I just want to be able to run custom kernels or delete bloatware (instead of freezing) and still retain the nice Galaxy S4 logo on startup... not the ugly "Custom" padlock/logo.
As mentioned by @scott14719 in this post, disabling the scan altogether may cause other problems (won't know until we try?). However, it seems clear to us that this scan, upon determining that the /system is indeed customized, throws a red flag that is read by the bootloader upon next startup. My goal here would be to either disable the scan altogether, or somehow permanently disable this red flag.
Not knowing much about the scan itself, here's some more observations that might help:
Most critically, the padlock/"custom" boot screen is NOT triggered until this scan is run and the system is flagged.
The scan runs immediately upon startup and finishes within about 38 seconds of uptime. Might take longer if more files have been added to /system or if more apps are running on startup (and slowing it down).
If you quickly go look at the Device Status in About Phone within the first 38 seconds of startup, you can see that it is "scanning" at this time.
It seems that the scan does not run again until the next system startup.
A custom recovery does not trigger "custom".
A custom kernel triggers the "custom".
Freezing bloatware does not trigger the "custom".
I once uninstalled a lot of bloatware, and this triggered "custom". I haven't checked to see if it's any system apps that trigger it, or if only certain apps are monitored.
Having busybox and/or Superuser properly in-place will trigger "custom".
All this being said, can anyone offer some more insight into this scan, and more ideally: has anyone found a way to disable it?
Click to expand...
Click to collapse
As others pointed out throughout the thread, the file responsible for checking the system status at boot is SysScope. There are various ways of trying to "full" the system into believing that it was NOT modified when in fact it was but one that has been working fine on my Note 2 as well as the S4, uses an XPosed Framework module called...yeah, you guessed it, SysScope.
Furthermore, if you're not familiar with XPosed Framework you'll be in for a NICE surprise as, once the framework installed it gives you the possibility of installing many other modules - real goodies, and I mean real goodies!!!
A word of caution: DO NOT INSTALL any version of XPosed Framework prior to 2.1.4- it'll soft brick your S4.
Take a look at the attached screenshot. Needless to say that my phone is heavily customized/modified.

Awesome! I would still like to know how to modify the code manually ( incase people don't want to use XPosed for whatever reason), but this is getting pretty close to the objective and I think will work for most. Thank you.

Here something very interesting. All credit goes to Mr. Impossible. I have not tried this so it should be interesting to see how well it works.
http://forum.xda-developers.com/showpost.php?p=42098246&postcount=729

scott14719 said:
Awesome! I would still like to know how to modify the code manually ( incase people don't want to use XPosed for whatever reason), but this is getting pretty close to the objective and I think will work for most. Thank you.
Click to expand...
Click to collapse
This SysScope Xposed module says its re-enables logcat'ing for SysScope. Maybe with this enabled, you can tell what functions need modifications. But if something else is monitoring SysScope's integrity, the rabbit hole may get pretty deep. The advantage of something like Xposed is that the apps are not modified so something checksum'ing them won't notice anything different.
For what its worth, I restored my device using Odin and rooted it. Followed the common steps to replace SuperSU with Superuser and rebooted a couple of times until the "custom" message was gone. I booted into recovery, installed CM10.1 and never looked back. My phone boots with the standard logo now each time because CM doesn't have SysScope.

romracer said:
This SysScope Xposed module says its re-enables logcat'ing for SysScope. Maybe with this enabled, you can tell what functions need modifications. But if something else is monitoring SysScope's integrity, the rabbit hole may get pretty deep. The advantage of something like Xposed is that the apps are not modified so something checksum'ing them won't notice anything different.
For what its worth, I restored my device using Odin and rooted it. Followed the common steps to replace SuperSU with Superuser and rebooted a couple of times until the "custom" message was gone. I booted into recovery, installed CM10.1 and never looked back. My phone boots with the standard logo now each time because CM doesn't have SysScope.
Click to expand...
Click to collapse
The Xposed module for SysScope does appear to work well. I agree that it would be nice to know how to modify a stock (or TW-based) ROM such that SysScope is removed without the other apps noticing.
I'm thinking that in your case, romracer, the bootloader last knew your status to be "official" - and because SysScope (and other related checks for it) are completely gone, the bootloader has no way of knowing otherwise. Interesting. I wonder if there's something we can do to these handful of apps to "neuter" them, keeping them from reporting to the bootloader that the status is Custom.

Sweet! It worked! No longer showing custom icon!!

Update: I've got a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700

Aou said:
Update: I've got a working solution here: http://forum.xda-developers.com/showthread.php?t=2333700
Click to expand...
Click to collapse
Awesome, I knew you would get it going.

Has anyone been able to automate this procedure to make it more simple? Seems like quite a bit involved to get it done. Would like to see the Custom status gone for good but wouldn't mind a simpler solution
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] reset system status on AT&T GS4

My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?

scmagee said:
My GS4 "system status" is custom. Does anyone know how to reset it on a AT&T GS4?
Click to expand...
Click to collapse
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.

reset system status on AT&T GS4
Plexicle said:
It will be a while before we learn how to reset the count. I mean, we just figured out how to unlock it like a week ago.
Click to expand...
Click to collapse
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.

scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.

scmagee said:
Thank you for the fast reply. Here is a bit more info. The count is 0. when ever I reboot the phone, the bootloader screen says
"Samsung custom" with a image of an unlocked lock.
All I did to get there was to root it with Dan Rosenberg's root procedure and then I used adb to copy aboot.img to /data/local/tmp.
Then I did a pull of the file from the GS4 to my PC. I did not go any further. I did not do any flashing.
So I am not sure if it was the root procedure that tripped the custom status or the pulling of aboot.img from the device.
I am guessing that the rooting causes the status change.
Click to expand...
Click to collapse
Using the search function and doing some reading would have revealed that this subject is being or has been discussed in several places in the AT&T S4 forum already. I mention this in case you are interested in reading about what has already been discussed about the issue. However, this thread goes a lot more in depth about the issue...
http://forum.xda-developers.com/showthread.php?t=2303022
It is just a beginning but if you have any knowledge to contribute to that thread or if you know anyone that can help it would help greatly.
In short, an APK named Sysscope scans the phone at bootup. There are a few other processes that support sysscope as well. Sysscope uses several methods of checking the phone to see if certain parameters have been changed, deleted, or modified. If it shows that they have, the next boot will show "custom" status and the unlock icon. It appears that a method was found to keep the Verizon S3 Official, but the method needs to be figured out and implemented on the AT&T S4. That is beyond my capabilities. The thread I posted and the threads linked in that post describe this all more in detail.
---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------
Plexicle said:
The "custom" on boot means your bootloader is unlocked (which is required to inject root when it's starting up, like you did when you ran Dan's exploit). Relocking your bootloader will get rid of the image (flashing stock via Odin) but that could also trip the counter behind it, I'm not sure.
Click to expand...
Click to collapse
The bootloader remains locked (unfortunately). Dan's exploit sidesteps the bootloader to allow for custom recoveries and kernels but the bootloader itself remains locked. The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.

scott14719 said:
The bootloader remains locked (unfortunately). The custom and icon appear due to sysScope scanning for changes. I do not think the counter is tripped, but the links in the thread I posted above show where the counter code is located on the Verizon S3. I am thinking it should be in a similar area on the AT&T S4. I have also read that the latest version of triangle away works well on the S4s, but I have not tried it for myself.
Click to expand...
Click to collapse
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.

Plexicle said:
Interesting to know things are working differently with this one. Oh well, that will spice it up a little-- I just got mine, so I'm just now jumping in to how I can help with the problems.
Thanks for the info.
Click to expand...
Click to collapse
Thank you.

The custom status seems to be a scan at the moment. If you Odin back to stock firmware and start from scratch, you will be back to Official status. AOKP doesn't run this check so as long as you Official you can flash AOSP and AOKP freely I'm pretty sure and be safe from the ugly custom status.

Try this:
http://forum.xda-developers.com/showthread.php?p=41955085#post41955085

Need help with rooting Rogers Galaxy S4 I337M

So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!

Pellisco said:
So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!
Click to expand...
Click to collapse
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.

robinsonj said:
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.
Click to expand...
Click to collapse
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.

Pellisco said:
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.
Click to expand...
Click to collapse
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.

robinsonj said:
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.
Click to expand...
Click to collapse
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?

Pellisco said:
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?
Click to expand...
Click to collapse
You may want to look at the top of this page.... http://autoroot.chainfire.eu/ states CF-auto root will trip Knox warranty... if your rooting, you should install a custom recovery and do a nand backup before you do anything else root without backup can have some ill side effects if you mess around with your files/apps... ie delete something that is critical.... of coruse custom recovery trips something else too I forget what it was but I am sure it's been discussed a couple times throughout the forum.... all I can say is read lots.... most times someone can get you out of a jam but I prefer not to go there in the first place.. so I read before I do.... most here will tell you it's the best way.... pay close attention to those who have messed up... good indication of what not to do....

One other thing I noticed was that there are locked boot loaders on certain devices.
So I have been wondering, does the Rogers Samsung Galaxy S4 come with a locked boot loader? Cause if it does, and I try and root my phone, there is a high chance that it will brick the device.

unroot

hello guys,
sorry for the bad english hope everything will be clear.
so i got my new phone 4 -5 month ago.
and my friend rooted it for me (mainly cus of the pokemon go hack), i didnt know the actual risk of rooting so i let him.
when i stoped playing pokemon go and found that that rooting ur device will remove the warrenty from my device i wanted to unroot it.
so i restore to factory settings thinking that it will remove the root, only like a week later i have read that restore to factor settings dos not remove root
so basicly now i want to unroot my phone so it wont cus demage to my warrnty.
i dont know much abut how he rootted my iphone i know he used a youtube video named: Pokemon Go Cheat/Hack for Android - Use a Joystick, WORKS on v0.35.0! ( new users can add links so i coulnt add a link to the youtube video but if u copy and past the youtube video name u could get to the actual video)
and on the descrition it sais This cheat/hack requires an Android device with root & Xposed installed. so im guessing this is what he did.
also i want to note that when useing root checker app it sais - sorry! root access is noy proberly installed on this devices
pleas could u guys help me with guides and tuturials on how to unroot my phone after it has been reset to factory settings so my warrenty wont go off its a new phone =D
ty ty ty
edit:i was thinking mabye the information on the download mode might be helpfull so this is what it sais:
odim mode
download speed : fast
product name: SM-G935F
cuarent binary: custon
system status: custom
fap lock: off
secure donwload :enabled
warenty void : 1 (0x020c) - - - - dos that mean my warranty is off?
ap swrev : b:1 k:0 s:0

With 3rd party insurance, which is usually cheaper anyways, they don't care about KNOX... In fact, Protect My Bubble didn't even make me send back my phones.... So to hell with Knox flag trips and get some better insurance.

anonymoustl said:
With 3rd party insurance, which is usually cheaper anyways, they don't care about KNOX... In fact, Protect My Bubble didn't even make me send back my phones.... So to hell with Knox flag trips and get some better insurance.
Click to expand...
Click to collapse
ok and regarding the fact that root checker sais its not rooted but when u look on the download details it depfenatly suggest its rooted..
what to do to fix that?

Once rooted its irreversible

Your bootloader is unlocked. This is not reversible, and voids the warranty. No way back i'm afraid. You can certainly remove root from your phone. Thats what i did, to be able to use ota´s. In your case this does not matter though, your warranty is still void.

Ati75 said:
Your bootloader is unlocked. This is not reversible, and voids the warranty. No way back i'm afraid. You can certainly remove root from your phone. Thats what i did, to be able to use ota´s. In your case this does not matter though, your warranty is still void.
Click to expand...
Click to collapse
how do i safly remove the root cus i'v heard odin thing is very risky and if something goes worng the phone can get ****ed up

actually, using Odin is very safe. Just follow instructions very carefully, make sure it's for your model number and double check. Go to www.sammobile.com, go to the 'Firmware's' section., type in your model number and search for your country's firmware and download.
Install USB Mobile phone driver. Get Odin. Go into your phone's settings and turn 'ON' USB debugging. Plug your phone to PC with a good quality cable, preferably the one that came with your phone. Don't plug into a USB hub though. Go into Odin download mode (volume down, Home + Power buttons). When you got the BLUE ID:COM box lighted up, it means that it can read your phone so your drivers are all good. Then click on the AP button, browse for the file you got from Sammobile (remember that it must be the same Model as your one ok, any country is fine, just make sure that sm-g935F is for sm-g935F etc). click Start. it should reboot a few times itself and when it says Done, your phone should boot into Android and you go through the setup all over again, losing all data in the process, but you will have a brand new unrooted, error free phone that can get updates OTA. True, your Knox counter will still say 0x1 void, but most warranty don't check that. As long as it says 'Official' which you will have once you flash the stock firmware. hope this helps...