Database Users

Screen Mirroring does not work with Custom Status (ROOT_Status) Need official status

Hi Guys,
I have just realised something, this is nothing to do with KNOX, it is only the official status thing that changes when you have a custom Kernel or Custom rom.
Screen Mirroring does NOT work when you are in Custom Status, this happened to be the same when I googled and found S4 was the same post after post after post of people stating the same thing (I get an error or hardware device error when screen mirror starts or it will start for 4 seconds then stop.
For people wanting to see their status -
You can see this in Download Mode or You can see this in ABOUT DEVICE > STATUS> Scroll all the way down to bottom.
There is a solution which worked on the S4, where you were able to change status from custom back to Official, Yes KNOX is still tripped if you have tripped it but the status is able to be changed back to official
Can someone please direct me to a way we can get official status back on the S5, I love my kernel and my tweaks, and I love my latest firmware I dont care about Knox. For the people who are scared about Knox, I was able to change my phone for a new phone because of a defect and this is after I triggered knox, I was sent a new phone and I placed the old phone in the bag and sent it back, guess what ? I tripped knox again lol (who cares) most of the time when you go to swap your phone they don't check.
All I want is the official status back so I can get my screen mirroring working, this is an awesome feature

Anyone?
Am I the only person with a rooted Knox-tripped S5 with custom , Recovery,Kernel & want to use screen mirroring?
S5 Development is no where near the type of dev we had when the S3 came out, pretty sad.
I think now that the HTC + LG are up in terms of hardware many people left the samsung scene leaving less devs in the area.

Hi,
I have same promlem here. when I open screen mirroring tv and phone connects and suddenly disconnect and shows a error ''screen mirroring cant start caused by a hardware problem''.
I have sm g900h stock kernel+xtrestolit rom+cwm recowery

works fine for me

btemtd said:
Am I the only person with a rooted Knox-tripped S5 with custom , Recovery,Kernel & want to use screen mirroring?
Click to expand...
Click to collapse
No, you aren't. For me with Knox tripped and custom recovery, kernel and NeatROM2.3 it works fine and I am in custom status.

Using Xposed app "Wanam Xposed", you can set your status to Official under the "security Hacks" section of the app.

[Q][HELP][GT-I9515]Knox counter reset, is it possible?

Hi, I have just bought S4 I9515 and it seems I acted with rooting too fast. Unfortunately my phone has issue with frequent rebooting. I would like to send it to service with warranty but after rooting knox counter switched to 0,1.
Is there any way to reset knox counter or eliminate rebooting issue?
Thanks in advance for help.
Sebalos

Did you try installing the firmware again through Odin? There's no way to reset the Knox flag once tripped.

1. But isnt it possible for now or it is not supposed to be elaborated within the closest future at all?
2. Where and how could I find firmware for my phone model each original not branded and designated for telcom provider Play for Poland? What shall I check,verify and take into account during firmware compatibility validation?
3. Regarding issue with rebooting is any xda dev working on it or samsung? Is it supposed to be solved? I heard the issue can be related to battery.
4. Shall I maybe try to send to samsung service counting they will ignore knox counter? Do you know how much expensive could be such repair?

1. It's not possible for us to do it, at all. The Knox flag is set, as best as the userbase can fathom, via an EFuse. Once tripped, that's it unless Samsung can reset it.
2. http://www.sammobile.com is where you can get the firmware for your device. There is a firmware checker on the site, that when you enter the model number of the phone and the country, it will pull up the firmware you are supposed to have. Another portion of the site can pull up all the available firmwares worldwide for a particular model. You'll have to go over there and look.
3. What issues with rebooting? I have an I9505 so I have no idea what you're referring to. Flashing the stock ROM for your device may cure the reboot issue.
4. You can send it in if the firmware flash doesn't fix it. If Poland is a member of the EU, and I believe it is, supposedly Samsung may not refuse warranty service on the basis of the Knox counter being tripped. I caution you however that I am not a citizen of Europe, so what I have heard is simply hearsay. You'll want to confirm the truth before taking any action. Cost of the repair? Unknown, because it's impossible to know what could be causing the issue. If it's a problem with firmware they'll likely flash it, charge for the privilege, and send it back. If they have to replace the motherboard, that will be expensive.

Thanks a lot for your effort and all the best in the New Year if applicable for you
Regarding issue #3 my phone is randomly rebooting by itself. It can even do during a call :/

S8 G950F with Stock ROM detected as Custom OS by Google Apps Device Policy

This is a weird one and I have a case with Google open, unfortunately you need to talk with all the levels of support before you can talk to someone that actually knows anything.
Got a Galaxy S8 SM-G950F, decided to play around with it so unlocked the bootloader and flashed a few ROMs and such. Decided to use it for work so I returned it to stock flashing the original stock rom for my carrier with Odin and then disabled OEM Unlock.
All good and peaches but when I tried to use my work G Suite account I got a cannot create work profile error blaming a Custom OS install (first attached image).
Keep in mind I am the G Suite Admin for my company and I know we don't check for unlocked bootloaders, custom roms and root and we have lots of people on custom roms, there is a specific option for that so I am sure we don't enforce that. But even if, the device has knox triggered but is now fully stock as you can see in the second attached image.
I have since tried a Samsung Smart Sync restore as well, but it didn't fix the issue, everything on my device says it is stock and in an official status, Google is clueless as well so far.
Not much hope anyone met this as it seems to be fairly mind blowing and unique, but worth a try

bubbl3 said:
This is a weird one and I have a case with Google open, unfortunately you need to talk with all the levels of support before you can talk to someone that actually knows anything.
Got a Galaxy S8 SM-G950F, decided to play around with it so unlocked the bootloader and flashed a few ROMs and such. Decided to use it for work so I returned it to stock flashing the original stock rom for my carrier with Odin and then disabled OEM Unlock.
All good and peaches but when I tried to use my work G Suite account I got a cannot create work profile error blaming a Custom OS install (first attached image).
Keep in mind I am the G Suite Admin for my company and I know we don't check for unlocked bootloaders, custom roms and root and we have lots of people on custom roms, there is a specific option for that so I am sure we don't enforce that. But even if, the device has knox triggered but is now fully stock as you can see in the second attached image.
I have since tried a Samsung Smart Sync restore as well, but it didn't fix the issue, everything on my devices says it is stock and in an official status, Google is clueless as well so far.
Not much home anyone met this as it seems to be fairly mind blowing and unique, but worth a try
Click to expand...
Click to collapse
Wouldn't be surprised if this is Knox related. Once Knox is tripped it is permanent. That's why if you try to open s health on a Knox tripped stock firmware it says it won't open because it's rooted even though it's not rooted

sofir786 said:
Wouldn't be surprised if this is Knox related. Once Knox is tripped it is permanent. That's why if you try to open s health on a Knox tripped stock firmware it says it won't open because it's rooted even though it's not rooted
Click to expand...
Click to collapse
Never been a problem in the past with Google, unless they started to check for Knox. Still, we have the "Compromised Devices" check disabled, should be considered a bug if their app is triggered by that

bubbl3 said:
Never been a problem in the past with Google, unless they started to check for Knox. Still, we have the "Compromised Devices" check disabled, should be considered a bug if their app is triggered by that
Click to expand...
Click to collapse
The thing is, a lot of the newer Samsung's once Knox is tripped that's it, it can't be hidden unless by custom rom and kernel, older devices like the s3 and s4 you could reset the Knox counter, and most other phones root is easily hidden, and bypassed. But Knox is on a boot loader level, the app can't do anything to change that, and I doubt it will ever be fixed.

yes it is true, since the galaxy s7 , knox counter is hardware so once its broken its permanent, no matter if you are on custom/stock/rooted/unrooted rom or firmware. once knox is broken I highly suggest to use custom rom

I actually got in touch with Samsung and they confirmed that Knox shouldn't matter for Google Apps unless they check for it, but we have the option to check for it disabled on the admin side.
We also have 2 users with rooted S7 that don't have this issue.
I bet this one will be messy to sort out, if ever...

Solution?
bubbl3 said:
I actually got in touch with Samsung and they confirmed that Knox shouldn't matter for Google Apps unless they check for it, but we have the option to check for it disabled on the admin side.
We also have 2 users with rooted S7 that don't have this issue.
I bet this one will be messy to sort out, if ever...
Click to expand...
Click to collapse
Did you ever solve this issue? I have more or less same problem on S8 with Pie

DRDSVK11 said:
Did you ever solve this issue? I have more or less same problem on S8 with Pie
Click to expand...
Click to collapse
Did not resolve and sold the phone before any custom rom was available. After being escalated to an engineer, we used apt to check the events in real time on the phone and we noticed that Samsung intercept the request from G Suite MDM to encrypt the storage to use its own knox based encryption and becuase of the knox counter it fails.
Nothing Google can do, not sure if a custom rom would solve, definitely you would need at least a completely custom kernel to avoid this trick that Samsung is pulling off, good luck!

probably knox is stipped but that shouldnt affect google apps as safetynet doesnt rely on knox maybe you could try actually using a custom rom with custom kernel that spoofs knox 0x0

I dont know if this work on all devices, but i know the solution, replace ManagedProvisioning apk, usually on /system/priv-app/ , take a replacement from stock aosp gsi from phhuson (you must pick correct gsi for example like your android version and architecture must be the same). this little trick is working on my stock j7 prime oreo.

[Q] Magisk and fake Knox 0x0

Premise: I have a rooted Note 4 and this is the first time that I'm trying to better understand Magisk and its functions.
I'm Italian and I'm going to buy the new Galaxy Note 9. In Italy you can take advantage of a "super value program" with which you can give back your old smartphone in order to obtain a cashback on the buy of the new smartphone.
I'd like to give back my Note 4, but I'm afraid that rooted smartphone cannot be accepted (not sure about this point).
For this reason, I'm going to flash back the original firmware, but the problem of Knox 0x1 will be still present. I know about efuse etc (I read a lot about that)... What I need is a way to hide/fake the counter. I read that Magisk was used for this purpose on other "Galaxy smartphones" in order to allow the use of apps like Samsung Pay. My question is (finally): is it possible to use Magisk to hide/fake the Knox counter on the official firmware of my Note 4?

No, after note 3 there is no way to hide knox status.

I can't make calls anymore

I bought a used note 10+ but it was rooted i didn't like the root so i unrooted it but apparently i did something wrong so i tripped nox 0x1 but i don't really care about Samsung services but after that the not registered on network thing started to appear can someone help i can't find a way to fix that do i need to repair the imei some how or what should i do