Recently I've rooted my device. That was okay...
But yesterday after installing the ClockworkMod, Private mode don't working anymore..
So please I need help here..
Sent from my SM-G900H using Tapatalk
No Knox, no private mode.
It stops working when Knox flag is tripped.
There's no current way to reset it.
Sent from my Nexus 7 using Tapatalk
Masum56k said:
Recently I've rooted my device. That was okay...
But yesterday after installing the ClockworkMod, Private mode don't working anymore..
So please I need help here..
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Private Mode will work if you rooted but still use stock kernel
It WILL NOT work if you use custome kernel
drakester09 said:
No Knox, no private mode.
It stops working when Knox flag is tripped.
There's no current way to reset it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Private mode was working fine, before I flashed with ClockworkMod..
Only rooting was fine..
babygau said:
Private Mode will work if you rooted but still use stock kernel
It WILL NOT work if you use custome kernel
Click to expand...
Click to collapse
I found somewhere is that, Xposed framework crashedcrashed the private mode & S Health app..
It looks like after I installed Xposed, all problems start from here..
Now please tell me, How can I solve it? I mean, how can I go back to Stock
Sent from my SM-G900H using Tapatalk
Can I use this method to go back to stock?
http://www.editandroid.com/how-to-flash-stock-firmware-and-unroot-samsung-galaxy-s5-all-variants/
Sent from my SM-G900H using Tapatalk
Masum56k said:
Can I use this method to go back to stock?
http://www.editandroid.com/how-to-flash-stock-firmware-and-unroot-samsung-galaxy-s5-all-variants/
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Yes, it's completely trustworthy.
For your issue, try to delete cache and data of "s health" and "health service". this issue is very common for those using custom rom or custom kernel
babygau said:
Yes, it's completely trustworthy.
For your issue, try to delete cache and data of "s health" and "health service". this issue is very common for those using custom rom or custom kernel
Click to expand...
Click to collapse
That means I don't need to handle with kies..
Sent from my SM-G900H using Tapatalk
As I mentioned, once you trip Knox flag Private Mode stops working.
There is no current way to restore the Knox flag, it won't work by just restoring to stock.
He is using stock kernel.
drakester09 said:
As I mentioned, once you trip Knox flag Private Mode stops working.
There is no current way to restore the Knox flag, it won't work by just restoring to stock.
He is using stock kernel.
Click to expand...
Click to collapse
Then, How to go back to Stock kernel?
Sent from my SM-G900H using Tapatalk
Masum56k said:
Then, How to go back to Stock kernel?
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
You are using stock kernel. The recovery is what you changed when you flashed CWM.
That will not solve your issue with Private Mode. That is caused by Knox.
PS: This is my last reply on this subject... it's getting repetitive.
drakester09 said:
As I mentioned, once you trip Knox flag Private Mode stops working.
There is no current way to restore the Knox flag, it won't work by just restoring to stock.
He is using stock kernel.
Click to expand...
Click to collapse
This is not true. it's deodexed roms that break private mode. Take a look at my rom at the t-mobile forums. I used kind of a hybrid approach and have private mode working 100%.
Sent from my SM-G900T using Tapatalk
Can you link to it please? Wouldn't mind a look
Sent from my SM-G900F using XDA Premium 4 mobile app
well private mode was working for me after root and custom recovery.. and it stopped the second I installed xposed... i didn't install any rom nor kernel...
did you guys try disable xposed - reboot and turn on private mode?
tp2215 said:
This is not true. it's deodexed roms that break private mode. Take a look at my rom at the t-mobile forums. I used kind of a hybrid approach and have private mode working 100%.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Really?
Well... I'm running stock rooted and Private mode stopped working the day I rooted.
I'll take a look.
Edit: I read the thread... now I can imagine why, I had xposed installed since I rooted.
Thanks for the clarification.
drakester09 said:
Really?
Well... I'm running stock rooted and Private mode stopped working the day I rooted.
I'll take a look.
Click to expand...
Click to collapse
You may have installed the deodexed base. it should be working if the framework apk are still odexed.
Sent from my SM-G900T using Tapatalk
tp2215 said:
You may have installed the deodexed base. it should be working if the framework apk are still odexed.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Pure stock rooted. I haven't installed any rom - there are none for the redheaded child a.k.a Exynos variant G900H
Using stock rom, kernel and rooted also install cwm recovery but private mode doesn't works, is there a way to fix this, i remember after root the device the private mode was working, after install xpose it was broken, and unistall xpose and wanam didn't work, tel model is g900h octa version
What cause the problem? Custom recovery, root, xpose, knox or something else
It's 100% xposed. .. just uninstalled xposed and rebooted via xposed installer and straight after reboot private mode works without a problem.... well have to wait for rovo to fix it... If it's possibles
Sent from my SM-G900F using Tapatalk
Uninstall xpose and no fix also factory reset not work,
Rooted and then broken screen mirroring, shealth broken(i fixed it), now private mode is not working also cant get firmware updates... wth , if you use samsung device and want to root think again,
Sent from my SM-G900H using Tapatalk
volkie1912 said:
Uninstall xpose and no fix also factory reset not work,
Rooted and then broken screen mirroring, shealth broken(i fixed it), now private mode is not working also cant get firmware updates... wth , if you use samsung device and want to root think again,
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
You must have done something wrong... private mode is working for me and i am rooted with custom recovery
Sent from my SM-G900F using Tapatalk
Related
Thought I would share cuz it took me forever to figure it out but if you want to get rid of that custom padlock after root...you can use the Wanam Xposed Module. Just go into security hacks and check "fake system status" to make it"official" again. This might be old news but it took me forever to find something that worked.
???Sent from my stock yet Divalicious Note 3 using xda app-developers app???
Wanam does nothing on my note 3 your trick didn't work nor does any other feature this app offers. Strange
Sent from my SM-N900V using Tapatalk
raveniselizabeth said:
Thought I would share cuz it took me forever to figure it out but if you want to get rid of that custom padlock after root...you can use the Wanam Xposed Module. Just go into security hacks and check "fake system status" to make it"official" again. This might be old news but it took me forever to find something that worked.
???Sent from my stock yet Divalicious Note 3 using xda app-developers app???
Click to expand...
Click to collapse
Sorry, but the news is beyond old.
Sorry, but the news is beyond old.
So old it doesn't work
Sent from my SM-N900V using Tapatalk
mtnbst said:
Sorry, but the news is beyond old.
So old it doesn't work
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
It does work, just did it this morning. Are you familiar with how to enable modules in the Xposed framework app (Go to modules and make sure that is is checked, then reboot.) Also for this particular module (And most that mess with boot stuff) a second reboot is required to see the changes.
Yep. .. That did it. .. Thanks
Sent from my SM-N900V using Tapatalk
mtnbst said:
Yep. .. That did it. .. Thanks
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Are you on a custom ROM? I had it working on stock then flashed a ROM and it stopped; or should I say it worked intermittently . After this latest OTA I decided to remain stock and it's working fine again on every reboot ... Not saying that this is your issue, just thought I'd throw it out there.
Sent from my Nexus 7 using Tapatalk 4
YankInDaSouth said:
Are you on a custom ROM? I had it working on stock then flashed a ROM and it stopped; or should I say it worked intermittently . After this latest OTA I decided to remain stock and it's working fine again on every reboot ... Not saying that this is your issue, just thought I'd throw it out there.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'm on stock MJE. Wanam is working now that I updated the module.
Sent from my SM-N900V using Tapatalk
Lol. I only used custom roms to be able to theme certain things....with wanam it works best on stock which so far keeps the phone working at its best for me anyway. Xposed is awesome IMO.
???Sent from my precious Samsung Galaxy Note 3???
Another great module for Xposed is called "Unicon". Lets you change your icons everywhere on your phone...even the lockscreen shortcuts and some settings icons. Uses icons from almost any launcher theme without having to change launchers.
???Sent from my precious Samsung Galaxy Note 3???
I've had this icon ever since I rooted this puppy. Never goes away. Even when I odin back to full stock firmware. Wanam only masks this. But it does not work for me, regardless. So how does one actually get this to go away other than odin stock flash? Cuz if I ever need to revert back for warranty, it's still gonna be there on my phone.
♢NoteIII♢
My note 3 is running the belgian 4.4.2 I downloaded from Sam mobile and flashed with odin, though the phone says it is a custom rom and when I click check for updates it also says phone is modified.
Anyone know what the problem is here and how I can restore ota updates?
The phone was rooted when i was on 4.3 but I have flashed first the Polish and then the Belgian 4.4s via odin
Sent from my SM-N9005 using Tapatalk
sweatingmytittsoff said:
My note 3 is running the belgian 4.4.2 I downloaded from Sam mobile and flashed with odin, though the phone says it is a custom rom and when I click check for updates it also says phone is modified.
Anyone know what the problem is here and how I can restore ota updates?
The phone was rooted when i was on 4.3 but I have flashed first the Polish and then the Belgian 4.4s via odin
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
downgrade to 4.3 of ur region it may solve the problem.
:good:
Thought you couldn't downgrade? I may as well wait for the UK 4.4 now
Sent from my SM-N9005 using Tapatalk
x102x96x said:
downgrade to 4.3 of ur region it may solve the problem.
:good:
Click to expand...
Click to collapse
You can't go back to JB from KK... You may as well have said to connect to Kies and let that fix it...
To the Op, check if your Knox warranty void has been tripped, if it has you may as well root and install a custom rom and/or recovery, or at the very least xposed framework.
You can't reset theKnox but you can use a mod to trick the system into thinking its official which will allow OTA updates. You may need a couple of things to be active so the OTA will install but I'll let you look that up.
ultramag69 said:
You can't go back to JB from KK... You may as well have said to connect to Kies and let that fix it...
To the Op, check if your Knox warranty void has been tripped, if it has you may as well root and install a custom rom and/or recovery, or at the very least xposed framework.
You can't reset theKnox but you can use a mod to trick the system into thinking its official which will allow OTA updates. You may need a couple of things to be active so the OTA will install but I'll let you look that up.
Click to expand...
Click to collapse
thanks for info
i wanna know thr s no way to downgrade or thr s some special and difficult ways!?!?
:good:
x102x96x said:
thanks for info
i wanna know thr s no way to downgrade or thr s some special and difficult ways!?!?
:good:
Click to expand...
Click to collapse
Nope, once the bootlader has been upgraded there's no way to go back....
So once knox has been Tripped you cant get ota updates even on an official rom?
Sent from my SM-N9005 using Tapatalk
sweatingmytittsoff said:
So once knox has been Tripped you cant get ota updates even on an official rom?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
You can get OTA, just not if it's rooted and status is custom....
ultramag69 said:
You can get OTA, just not if it's rooted and status is custom....
Click to expand...
Click to collapse
thats my problem mate, Im not rooted, im on stock and it still says custom even after I have reflashed with odin.
am i missing something?
sweatingmytittsoff said:
thats my problem mate, Im not rooted, im on stock and it still says custom even after I have reflashed with odin.
am i missing something?
Click to expand...
Click to collapse
Used to read about a bug on samsung phones where if it contains too many files it would show system status as modified. Try transfer as much as your files from phone memory into sdcard then remove it. Then check again system status. It sounds crazy but i'm pretty sure that's my understanding from the thread
Rosli59564 said:
Used to read about a bug on samsung phones where if it contains too many files it would show system status as modified. Try transfer as much as your files from phone memory into sdcard then remove it. Then check again system status. It sounds crazy but i'm pretty sure that's my understanding from the thread
Click to expand...
Click to collapse
il give it a try bud cheers
Still says the same, device is modified ?
Sent from my SM-N9005 using Tapatalk
If you have an SD Card remove it then boot up. Sometimes causes issues.
Sent from my SM-N9005 using XDA Premium 4 mobile app
That's what I just did from the post above and it hasn't changed anything, I also reflashed the rom with odin and it's still the same...
Sent from my SM-N9005 using Tapatalk
Strange, when flashing back to complete stock everything goes back to official (bar knox of course) - did you try the xeo? It's possible if you've used another firmware (carrier or country) the device may not like it.
Also a complete wipe may help too.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Well when I reflashed and it didn't work I did a factory reset and cleared the cache to no prevail.
What's the xeo mate?
Sent from my SM-N9005 using Tapatalk
Mine is the same. I went to stock because my official kit kat came out. VIA O2 germany.
Still says custom. Might root and try triangle away. Not sure if I want to re set all back up again today though
Sent from my SM-N9005 using XDA Premium 4 mobile app
Has KK implemented a non return to official status then?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Not sure but maybe if I install the btu when that comes out it will go back to official
Sent from my SM-N9005 using Tapatalk
Possibly, if they've changed it. That's put the sh...ter up everyone now.. darn Samsung! ! Blergh. . They love alienating people huh.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hey guys! So i just switched from a sprint note 3 to a verizon note 3. I NEED root but my company uses mobile iron. Is there a way to use it and keep root?
Also whats the best way to root this? All I want is root no custom recover.
haha good bc cystom recovery isn't possible atm on retail verizon note 3. seems like vroot is the only way to go right now without tripping knox but do ur research.
Sent from my SM-N900V using Tapatalk
defusEDtech said:
haha good bc cystom recovery isn't possible atm on retail verizon note 3. seems like vroot is the only way to go right now without tripping knox but do ur research.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
believe it or not I like the stock rom (this is the first phone I have ever been able to say that with)
So vroot... hmmm I shall look into it. But I still need to know about the mobile iron.
well I should have been more specific we can flash roms and some mods with safestrap (a sorta of custom bootloader workaroundl). but we do not have the ability to flash custom kernels.
Sent from my SM-N900V using Tapatalk
Try Rootcloak to hide root from the app. Works for another MDM software similar to that.
Edit:
Use the one from xposed framework. In not sure if the one from the play store works.
Can you link me to it?
Sent from my SM-N900P using Tapatalk
NissanNick said:
Can you link me to it?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2574647
Sent from my SM-N900V using Tapatalk
Ok so kingo did not work.. Vroot. Did the trick. I did a factory reset after that and now I'm rooted. I loaded the new framework and root cloak. I will let you all know of it works.
Sent from my SM-N900P using Tapatalk
hello..
i got note 3 sm n9005 (uk model),i tried to root my phone odin says pass,but it wont go to recovery mode it restarts and stuck on screen saying recovery is not seandroid enforcing" in red and another in yellow saying" set warranty bit.it wont let me root my phone,,,pls help me with this
thanks
That means you have succesfully put a custom recovery on your phone via odin. Stock wont show anything, but anything other than stock, that will show. I can only assume your on JB(4.3) still and have flashed a recovery for KK(4.4)
Im from the uk too, using chenglus 11/21 recovery on my jb rom.
Sent from my SM-N9005 using Tapatalk
Make sure you are using the right cf auto root file. One is for 4.4 and the other is for 4.3.
edit: didn't read it completely, what did you use to root your phone?
Sent from my SAMSUNG-SM-N900W8 using xda app-developers app
I've never used cf auto root. To root my first rom ( stock rom) i just flashed a custom recovery, and then flashed a superuser zip inside cwm
Sent from my SM-N9005 using Tapatalk
celderic said:
I've never used cf auto root. To root my first rom ( stock rom) i just flashed a custom recovery, and then flashed a superuser zip inside cwm
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Did that worked? As far as I know to flash a custom recovery you have to be rooted first.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Yes works fine. Have done it a few times on the n9005, and many times on other devices. You don't even need a rom to flash a custom recovery, or stock recovery for that matter.
Sent from my SM-N9005 using Tapatalk
celderic said:
Yes works fine. Have done it a few times on the n9005, and many times on other devices. You don't even need a rom to flash a custom recovery, or stock recovery for that matter.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
When I first got mine it will not flash cwm without rooting it first but mine was N900W8 so might be different situation.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
hey_joe said:
When I first got mine it will not flash cwm without rooting it first but mine was N900W8 so might be different situation.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Really? Im suprised, never heard of that before. Although i only read information related to my device, the n9005.
Sent from my SM-N9005 using Tapatalk
After root and applying wanam x posed I am not able to get into my private mode. My fingerprint is recognized, but I get the message that private Mode failed please try again. Any suggestions?
Sent from my SM-G900V using XDA-FORUM, powered by appyet.com
I'm having the same issue, I haven't been able to figure it out yet.
Sent from my ROOTED Galaxy S5
Ok cool. At least I'm not the only one.
Sent from my SM-G900V using XDA-FORUM, powered by appyet.com
Interesting discovery. All the research I've done on this issue points to the phone using ART. I checked the setting and my phone says it's using dalvik. So I figured maybe I can just try switching it to ART then switching it back. So I switched the setting to ART then reboot the phone, after it came back on I went to that setting and it still says dalvik. I tried it a couple times with the same result. It must be related to our issue somehow, just not sure why or how to fix it.
Sent from my ROOTED Galaxy S5
Afaik root breaks private mode. Same thing happened to people who used cfroot.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
It looks like it's just the framework that breaks it. When I uninstall the framework it starts working again. I guess no xposed if we want private mode. [emoji20]
Sent from my ROOTED Galaxy S5
briantacker said:
It looks like it's just the framework that breaks it. When I uninstall the framework it starts working again. I guess no xposed if we want private mode. [emoji20]
Sent from my ROOTED Galaxy S5
Click to expand...
Click to collapse
i had a issue after i installed framework my txt where showing sending on my phone..had to unistall xposed
Is there a tweak in framework to be done to achieve private mode again? A module that I don't know of?
Sent from my SM-G900V using XDA-FORUM, powered by appyet.com
Odin80 said:
Is there a tweak in framework to be done to achieve private mode again? A module that I don't know of?
Sent from my SM-G900V using XDA-FORUM, powered by appyet.com
Click to expand...
Click to collapse
When xposed installer is installed on our device private mode breaks. Only option to fix this is to disable and uninstall all molecules and uninstall exposed. I have the sprint varient and this was the only fix. If a custom rom has native mods then I think it shoudl work but as of right now I dont think theres a fix with private mode and xposed installer yet.
Sent from my SM-G900P using XDA Free mobile app
briantacker said:
Interesting discovery. All the research I've done on this issue points to the phone using ART. I checked the setting and my phone says it's using dalvik. So I figured maybe I can just try switching it to ART then switching it back. So I switched the setting to ART then reboot the phone, after it came back on I went to that setting and it still says dalvik. I tried it a couple times with the same result. It must be related to our issue somehow, just not sure why or how to fix it.
Sent from my ROOTED Galaxy S5
Click to expand...
Click to collapse
Xposed will not run in ART. It will automatically toggle your runtime back to Dalvik if it is installed. This is by design.
Sent from my SM-G900V using Tapatalk