Database Users

[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

Remove "Device has been modified"

I am so new, and so sorry, but this might be simple for others.... I am trying to undue what I did like 6 months ago. I know I downloaded something from the web from here (drawing a blank on the name, but it looked like the "anarchy A", it was just a quick easy way to ROOT. I don't think I did anything else, I know I never added a custom ROM. Can someone just tell me where to check to see what is modified. Then maybe I will be able to undue the rest.

hisandherturbo said:
I am so new, and so sorry, but this might be simple for others.... I am trying to undue what I did like 6 months ago. I know I downloaded something from the web from here (drawing a blank on the name, but it looked like the "anarchy A", it was just a quick easy way to ROOT. I don't think I did anything else, I know I never added a custom ROM. Can someone just tell me where to check to see what is modified. Then maybe I will be able to undue the rest.
Click to expand...
Click to collapse
Did you root your phone? Or did you install custom recovery? Or custom kernel? All of these may lead to the "Device has been modified" message.
You may also want to check for the Knox Warranty Status with Phone INFO ★Samsung★ app.

I did "root" it... it was a software root, I can not remember what it was called..... like I tried to explain, it looked like an "A".
thank you for the APP... KNOX is 0x0.... what else can I look at?

If you keep your phone, it really does not matter, but If you are going to sell it, then flash full image with Odin, it will bring everything back to stock, removing the root, all the red letter messages, etc. If you need help with using Odin, let us know.

TowelRoot was the software I used....

vndnguyen said:
Did you root your phone? Or did you install custom recovery? Or custom kernel? All of these may lead to the "Device has been modified" message.
You may also want to check for the Knox Warranty Status with Phone INFO ★Samsung★ app.
Click to expand...
Click to collapse
TowelRoot is the software I used... also, I am pretty sure I didn't install any recovery.... isn't there somewhere I can look to see what is/was done?

hisandherturbo said:
TowelRoot is the software I used... also, I am pretty sure I didn't install any recovery.... isn't there somewhere I can look to see what is/was done?
Click to expand...
Click to collapse
Hummh, you may need to post all screenshots from Phone INFO ★Samsung★ app for further investigation. Without the detailed info, no one can say anything for sure.

Here are some, is this enough?

hisandherturbo said:
Here are some, is this enough?
Click to expand...
Click to collapse
Not really enough, but I didn't see anything abnormal in your device info.
May be the reason is because your device has been rooted .
Try the following:
- Reflash the stock firmware. You will lost root.
- Or use Wanam Xposed > Security hacks > Fake system status.

Actually the very first screen you posted clearly says charger info requires root and it's blank so it doesn't seem like you have a root ATM and none of the 4 screens posted has Knox info, again its first page on the phone info (general info header) on the bottom, should say Knox warranty void 0 (good) or 1 for flag being tripped.
---------- Post added at 02:39 AM ---------- Previous post was at 02:24 AM ----------
Actually the very first screen you posted clearly says charger info requires root and it's blank so it doesn't seem like you have a root ATM and none of the 4 screens posted has Knox info, again its first page on the phone info (general info header) on the bottom, should say Knox warranty void 0 (good) or 1 for flag being tripped.

I really appreciate the help!
I "un-did" the towelroot, and KNOX does say 0X0.....
Here are the other screen shots....
If I remember correctly.... before when the towelroot was there, root info says I was rooted, and my device status was NOT custom.... so, I think it was something other then the root that did it.

My KNOX is still 0
I've tried to "factory data reset" from both the Android software and also the boot up screen (after I wiped the cache).
No matter what I do Device Status is still "custom"
There has to be something/somewhere I am missing.....

Here is a picture of my download page.... showing the custom status

For future searches.... FIXED..... I Downloaded Samsung KIES 3... and let it update the firmware... then I was official.

New firmware z1s, nov 9th 14.4.b.0.56

Someone tell me what it is. I wanna keeo root, lol, dont feel like going through all that

From online research, It's just to fix some bugs and a slight performance increase. I don't know if it will break root because I'm not rooted
Sent from my C6916 using XDA Premium HD app

I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.

mariussilverwolf said:
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
Click to expand...
Click to collapse
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.

TrunkleBob said:
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
Click to expand...
Click to collapse
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.

mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
How did you install it easily, i keep getting could not be verified

mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.

anyway to decompile this update to see what files are there?
im getting could not be verified as well, trying via sony update center on PC, im rooting with xposed as well
arghhh before i was able to use root-cloak on the sony update app and download updates... seems i cant do that anymore. how did you get to install while rooted? @mariussilverwolf ?

same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?

I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.

chriscosta77 said:
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
Click to expand...
Click to collapse
It is broken, on latest minor ota through pc companion update, not restore, and trying to root with easy root but it isn't working
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
nickcaper said:
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
Click to expand...
Click to collapse
I just used my cousin's phone as a tester, it breaks root, haven't tested with supersu pro yet with survival mode

i swear, its like these companies dont want us to use the devices the way we want. A simple thing like root and they make it so hard, even impossible on some models. These companies should know by now that there is a niche which desires freedom like rooting.
if i wanted a frggin phone that didnt have root or a locked os or bootloader id get a dam iphone.
im seriously NOT buying another phone from a store.
ill make sure i get something i can work with the way i want. its already stupid expensive as it is just out the box all locked up and full of bloat wear.
it takes a stupid amount of time and effort just to make these devices do what we want.
which is something that i shoulda got when i paid for it..
looks like i wont be updating sh.... t till i know i can use my device freely.. the way i want.

Unrelated to the root conversation, I'm stock, but my data is acting a bit weird since the update. Did this update change the radios?
Sent from my C6916 using XDA Free mobile app

4.4.4 root
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it

Your question.
Johann Broseph said:
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Click to expand...
Click to collapse
Please just use the search feature, you can easily find the root method. The root method is even on the first page of this topic.

For reference (since my root access remained post update) here's what I have enabled in SuperSU settings:
* Enable SuperUser
* Show Notifications
* Auto-refresh apps and logs tab
* Enable su during boot
* Mount namespace separation
* Trust system user
* Enable permission warning
* Enable Pro
As I mentioned in a previous thread, root was obtained using towelroot on 4.4.4. I haven't run into any issues with root-check invalidating any installs since. The OTA installed without any error messages. I can inject audio into /system/media/notifications and I can create new folders on the root directory that remain after reboot. Maybe I got lucky? I hope by sharing this that other people can duplicate my findings and we can find a way for everybody to maintain a working root solution after this update.

TrunkleBob said:
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
Click to expand...
Click to collapse
I've been doing some digging and discovered I'm missing a file. Following the original directions for rooting, I created a script and have Script Manager executing it at startup.
The first command is:
Code:
su -c "/system/xbin/kill_ric.sh"
This fails because that file does not exist on my phone. Anyway to get that back?

I had a huge problem with this yesterday and long story short, you cannot use the easy root method if this update is applied. I had to use the flash tool to get the last ftf files and start over from scratch. Avoid this if you can.

I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...

gqukyo said:
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
Click to expand...
Click to collapse
only way to get the notification off is to go into settins then look for apps then look for update center. click on it and click on the clear cache. only problem now is. you will need an app like sd maid or something that stops that app from starting automatically when the phone turns on. this is what i do.. it works... you wont get anymore notifications unless you manually make it check.... i use sd maid...

LED control on stock with any app!

Thanks to an idea from the dev of GravityBox, we can now have full LED control on stock with almost any LED control app. I tested it with GravityBox, and a few ghetto LED control apps from the play store and they all worked perfectly!
This also enables the LED to light up when charging.
You can either use the flashable zip, or replace the file manually. To replace it manually download the file attached to this post, place it in /system/lib/hw/ and replace the file that is already there. Make sure it has the same permissions as the other files, and then reboot.
This has only been tested on 5.1.1 (I'm running LYZ28E).
And no, it doesn't blink. Either the CM team hasn't cracked it yet or the LED drivers are just not there to make it blink.
A flashable ZIP has also been added to this post. ZIP created by @spacetaxi

Thanks! Seems to be working fine on LMY47Z as well. :good: Did some quick tests on my Nexus 6 and will try to regularly use it now instead of LightFlow Pro.

Does led blinking work without light flow?

Unfortunately it doesn't seem so.

So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.

OKAstro said:
So you still need to install an LED apk besides this? Why not just use Light Flow in the first place with having to do this?
Not being critical...just confused on my end.
Click to expand...
Click to collapse
Because a lot of people have issues with LightFlow since you have to do some really ghetto things to make it work. This guarantees that it will work and allows you to use any app you want.

OKAstro said:
So you still need to install an LED apk besides this?
Click to expand...
Click to collapse
No, this is my setup: Stock rom, rooted, modified lights.shamu.so installed, Xposed installed, GravityBox installed. But: All LED related functions in GravityBox are disabled, so I don't think that GravityBox or Xposed has to be installed. I can enable LED notifications e. g. in K-9 settings - and it just works! No GravityBox, Xposed or LightFlow involved. So if the regarding app supports LED notifications there is no need to use a "LED contol app".
Edit: The led *blinking* does not work. Instead the led is switched on permanently during a notification.

OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.

OKAstro said:
OK - I got it now. I use Handcent and K9, and can set their LED notifications as usual now within the respective apk itself. I noticed charging works too.
Very well done...so long Light Flow :good::good:
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
Does this include a battery low/charging/full feature too, or is the native built in one activated when this is installed. Reason I ask is because I didn't do anything for battery LED, plugged it in and am getting a green LED.
Click to expand...
Click to collapse
I believe it supports charging indication as well. I thought it was GravityBox doing it but apparently it is the OS.

Your title is a little misleading.
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.

vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.

I am running Gravity Box and yes it does work, although LED on N6 sucks

vvveith said:
To me stock means no root. You should add the line, (Rooted). Stock is stock, Stock (root required) is not stock. Stock ROM with root would be less confusing.
Click to expand...
Click to collapse
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?

spacetaxi said:
I think that root is currently only needed for the manual installation of the modified lights.shamu.so file. If somebody would build a flashable zip for this file, it should work without root.
Some volunteer out there?
Click to expand...
Click to collapse
That's a very good point. You could actually just do it in recovery if it supports ADB. You can push files over ADB really easily.

Just a tip. In order to get acurate red green blue colors for LED, instead of picking it, use exact hex value then its not going to mix with over colors
Blue #0000ff
Green #00ff00
Red #ff0000

Will this work in Android M?

jodvova said:
Will this work in Android M?
Click to expand...
Click to collapse
I went ahead and pushed it over using ADB and recovery on my phone running Android M. So far it seems to be working fine, though you won't be able to alter the light without an application that supports it.

A few reasons.
GrayBoltWolf said:
Stock rooted is stock with the SuperSU app installed.
At any rate why are you not rooted? On a Nexus device that is almost a sin since it is so easy.
Click to expand...
Click to collapse
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.

vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Who was denied warranty with unlocked bootloader? I haven't experienced that on any of my phones yet, even none Nexus devices

vvveith said:
My original reason for getting a Nexus device was to not have bloatware and to not get penalized for unlocking a bootloader, since originally I was told that Google would not lock bootloaders on Nexus devices. The first turned out to be true, the second proved false and I've already seen people getting denied warranty service for having a unlocked bootloader even though they factory reset and removed SU and other root related programs before sending it in. Somehow they were still able to tell it was rooted. But the only reason I've ever applied root was to get rid of bloat, did not have any so did not feel the need to root. Plus originally I was told that all updates come straight from google with no carrier interference, but that also became untrue. So there you have it. No worries though, after using it for almost a year, I've became quite attached to it's size. Until something else comes along with a screen close to this one and great specs, I will stick with it.
Click to expand...
Click to collapse
Google has absolutely no way to tell if you unlocked your bootloader unless you either 1. tell them or 2. send you phone in unlocked.
There have been 0 reports of anyone being denied warranty service on a Nexus device and any that may exist were because the user told Google they were unlocked.
At any rate this mod does not require root, as you can flash it through recovery or over ADB.

Kingroot on top of My KNOX, Working Great! !

I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.

MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.

Having some guys look into this.

doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app

warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L

This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.

I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...

Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.

doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.

gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.

doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L

elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app

not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:

doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L

elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes

I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr

Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.

doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4

Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK

LOL this works?!? how did nobody ever try this until now.. I'm speechless