Database Users

Recovery is not Seandroid Enforcing

Hello all Xda members, I think I need some help with rooting Galaxy Note 3 [N9005XXUDMJ7[ because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I've used Odin 1.85 to CF Auto Root this device. It says "PASS" on the program , but after the device stucks on the screen I mentioned above .It does not boot after that ; nothing loads too.
I really need someone to save me from this .

Goodluck
Sent from my SM-N9005 using Tapatalk

strawberycake said:
Hello all Xda members, I think I need some help with rooting Galaxy Note 3 [N9005XXUDMJ7[ because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I've used Odin 1.85 to CF Auto Root this device. It says "PASS" on the program , but after the device stucks on the screen I mentioned above .It does not boot after that ; nothing loads too.
I really need someone to save me from this .
Click to expand...
Click to collapse
Use this older file on odin.

It's said pass so it's complete. Either use the older version hey_joe has posted and untick auto reboot. Or try this way >
Once it's rooted and said pass. Turn the phone off, and try and go into recovery then reboot the device. It should boot into Android.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Man do I owe you guys a drink, I signed up just now, just so I could tell you that too!!
I had the exact same issue as strawberry cake and I thought my phone was toast!
Just redid all the steps with the older file, and I have a phone again, a more sweaty brow too...
I wasn't sure if I had signed up before and it took me a while to figure out that I hadn't, and some of them captcha's are ****ing difficult to read!!
But I was determined to get on here and say a thank you to you guys for your most excellent advice.
Although now that I've done that I see I need to enter more captchas just to post, I could be here a while at this rate.
In any case, thank you hey_joe and radicalisto.
Also if anyone else comes across this problem all I did was follow the advice in hey_joe's thread and got my phone back...

bazzertron said:
Man do I owe you guys a drink, I signed up just now, just so I could tell you that too!!
I had the exact same issue as strawberry cake and I thought my phone was toast!
Just redid all the steps with the older file, and I have a phone again, a more sweaty brow too...
I wasn't sure if I had signed up before and it took me a while to figure out that I hadn't, and some of them captcha's are ****ing difficult to read!!
But I was determined to get on here and say a thank you to you guys for your most excellent advice.
Although now that I've done that I see I need to enter more captchas just to post, I could be here a while at this rate.
In any case, thank you hey_joe and radicalisto.
Also if anyone else comes across this problem all I did was follow the advice in hey_joe's thread and got my phone back...
Click to expand...
Click to collapse
Glad we could help

how about seandroid on kitkat bootloader? i wasnt able to flash custom kernels for stock rom 4.4.2. can someone please explain? because after i flashed custom kernels with permissive selinux, the phone wont boot up.
Sent from my SM-N9005 using XDA Premium 4 mobile app

jamesmuking5 said:
how about seandroid on kitkat bootloader? i wasnt able to flash custom kernels for stock rom 4.4.2. can someone please explain? because after i flashed custom kernels with permissive selinux, the phone wont boot up.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which custom Kernels did you try? - I am using a custom kernel on KK now and my phone is working fine.

radicalisto said:
Which custom Kernels did you try? - I am using a custom kernel on KK now and my phone is working fine.
Click to expand...
Click to collapse
what custom kernel do u use? sorry im bad at note 3 stuff
Sent from my SM-N9005 using XDA Premium 4 mobile app

Wasn't the question, but I use this

radicalisto said:
Wasn't the question, but I use this
Click to expand...
Click to collapse
yes i used the exact same one. but when i booted up the phone after flashing the kernel, the bootsplash showed seandroid not enforcing and something about warranty with yellow words. do i need to do something specifically to make sure selinux permissive recoveries and kernels work? thanks so much
Sent from my SM-N9005 using XDA Premium 4 mobile app

jamesmuking5 said:
yes i used the exact same one. but when i booted up the phone after flashing the kernel, the bootsplash showed seandroid not enforcing and something about warranty with yellow words. do i need to do something specifically to make sure selinux permissive recoveries and kernels work? thanks so much
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you use a custom recovery or a custom kernel you will get that, it's normal, means you aren't using a Samsung signed recovery/kernel. - the custom kernel comes permissive by default.

jamesmuking5 said:
yes i used the exact same one. but when i booted up the phone after flashing the kernel, the bootsplash showed seandroid not enforcing and something about warranty with yellow words. do i need to do something specifically to make sure selinux permissive recoveries and kernels work? thanks so much
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are using KK get the latest 1.5 then flash it via recovery, The writings are normal

ok thanks guys i figured out finally after whole day crapping on it. its like if i do a wipe data reset then only it works but thanks so much for supporting me. thanks.
Sent from my SM-N9005 using XDA Premium 4 mobile app

Hi jamesmuking5,
I Try to root my galaxy Note3 N9005 with the new version of android Kit Kat (4.4.3) with this method : (true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html) (sorry I can't add url link, you have to add http) and I have the message you explain "Recovery is not Seandroid Enforcing" and the root doesn't work.
I don't exactly understand you last Answer : If a do a wipe data reset before, this root procedure will works ?
Thanks

THANK YOU!
hey_joe said:
Use this older file on odin.
Click to expand...
Click to collapse
I honestly thought I had buggered my two day old Note 3!... thank you so much for posting this file, saved my ass and made me a very happy bunny!

pwhitrow said:
I honestly thought I had buggered my two day old Note 3!... thank you so much for posting this file, saved my ass and made me a very happy bunny!
Click to expand...
Click to collapse
Np. Enjoy your toy
Sent from my SM-N9005 using xda app-developers app

hey_joe said:
Np. Enjoy your toy
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Like a couple other guys on this thread, I also became a member here purely to say thanks for the fix provided by hey_joe.
If anyone else with the same problem is reading this, just get the Odin version hey_joe posted on the first page.
Remember that you need to go into download mode (Volume Down + Power + Home) again to escape that 3-color, 3-line SEANDROID screen-lockup before you can interface with the older/better version of Odin.
Just adding this comment as it took me a few minutes to understand why Odin couldn't see the phone again. (Why yes, I *am* new to this whole rooting business) ...
All is good now and I confirmed the phone is now rooted with Root Check from Google Play.
Now to delete all this bloatware, specifically the pesky CloudAgent app that kept screwing up my ability to work with the Gallery. The popup "CloudAgent has stopped" has been the bane of my Note 3 existence for the last few days ...

radicalisto said:
Glad we could help
Click to expand...
Click to collapse
I had exactly same problem on the same device, and you guys saved me !! Thanks a lot!!

I have the same thing but my phone works. It only tells me that it's not enforcing seandroid when I go into recovery. Is that normal or did my recovery not install correctly? I can use it to flash files, do backups and such so I think it's working normally. The only issue is that I coulnd't get TWRP to work, I had to find the apk on my Note 2 and flash CWM Touch to have custom recovery and every time I go to reboot from there it says that it needs to fix my root. I haven't seen anything on it, so if I am in the wrong location please direct me to where I need to go. Rooting and all isn't new to me, been doing it since I got my EVO 4G when it was released, but I am by far no expert. This KNOX crap has me kinda flustered. The root appears to stick, I can use ROM Toolbox and do what I want it to do, root checker says I have root and all, just curious about the seandroid stuff and saw this post.

Screen Mirroring is broken in KitKat ROMs becuase of Root!

So toady I found out why Screen Mirroring is broken on KitKat ROMs. It's because of root. Today I wiped my phone to flash the latest 4.4.2 ROM, and after it was installed I checked the Screen Mirroring feature, and it was working all fine, but then as soon as I rooted the device, it doesn't work anymore!
I rooted at first via CF Auto root. Then wiped the device again and rooted via the Philz method posted here, http://forum.xda-developers.com/showthread.php?t=2655544
But the result is same. Screen Mirroring doesn't work. So is there anyone who is rooted here, on a 4.4.2 ROM, using an i9500, and for whom Screen Mirroring works?
I have never got a constructive reply in this regard ever. People don't use that feature or what?

Yeah. We know. If you have a good Google and a poke around XDA, You'll find the file you need and where to put it.
Sent from my GT-I9505 using xda app-developers app

killyouridols said:
Yeah. We know. If you have a good Google and a poke around XDA, You'll find the file you need and where to put it.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Well I am unaware of that. As far as I have seen no one knows the solution! So if you could please enlighten me it will be much appreciated. I have tried this topic, http://forum.xda-developers.com/showthread.php?t=2621550 Didn't do any good.

Screen mirror fixed

Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app

Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

REHolt218 said:
Do you know if Screen Mirroring works with WiDi devices? I have a stock, unrooted SM-P900 and have not been able to get it to connect to the WiDi device on my TV.
Originally my S4 worked but now even it will not connect. Since I don't use this very often i am unsure of when it quit. Probably linked to one of the updates.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I do not. I use a Miracast device

Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Nice! Honestly haven't missed this feature much but glad we have fix now!

rkirmeier said:
Nice! Honestly haven't missed this feature much but glad we have fix now!
Click to expand...
Click to collapse
I do a lot of traveling and this is a great solution for watching movies, when it works. My WiDi device is fairly small and connects to the TV with HDMI. Since WiDi is a direct connect between divices and doesn't depend on the local wifi it works much better than Google ChromeCast.
I just wish I could get it to work again with my Samsung devices.
Sent from my SM-P900 using Tapatalk

Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Wow so this is great news. One question is what effect if any will this have with root.

tonyz3 said:
Wow so this is great news. One question is what effect if any will this have with root.
Click to expand...
Click to collapse
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app

Duly.noted said:
root is unaffected. However you cannot have custom recovery
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Flashed the stock recovery and miracast is working again. So this means we can't load up TWRP?

That is correct. If we can get support for mobile odin then it might be possible to quick swap between the two on the go. As it is I would reccomend making a backup in twrp then reflashing stock recovery. Then if you need to restore just plug up to odin and flash twrp again. They did mention that whatever it was should be fixable to work with twrp. So if they get a fix it should be easy to port over to ours.
Sent from my SCH-I605 using XDA Premium 4 mobile app

Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?

ceomayl said:
This is great news. I held off of rooting because I use screen mirroring every week. Now I have some question, what will happen to my installed apps if I root now? Will i have to re install all of my apps?
Click to expand...
Click to collapse
Root will not affect anything You already have installed
Sent from my SCH-I605 using XDA Premium 4 mobile app

Thx for the fix post. I am going to do it this weekend when i have sometime encase of an unforeseen issues.... But just so i am clear. I am rooted already and when i flash this will anything be lost-such as settings or any of the Xposed modules etc. If so, any suggestions on a backup method...

We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that

esgie said:
We had similiar story on Note 10.1 2012 (N80xx).
No AllShare Cast (old name sammy was using for today's Screen Mirroring...) when custom recovery OR KERNEL (there isn't any yet on NP12s but surely - when it arrives - it will fed up all the users of mirroring... kernel OR mirroring...). Well, getting into technical details, coz I think here we'll hava similiar history:
- tablet - to work with Mirroring - had needed a flash counter reset to zero (using Triangle Away - did u try this one out? I borrowed my dongle to a friend so for a while can't test it...). The reason is that sammy's forced the software to require HDCP to every content possible, even my own screen... - and using HDCP was available only with use of Trusted Zone (mysterious tz.bin partition in sammy's devices...). When flash counter was zero, device had an access to tz and all was working. But...
- standard bootloader was very unkind for modders - if detected custom kernel OR custom recovery, it automatically triggered the counter every boot, so there was no way to effectively reset the counter with custom recovery or kernel. There was some ideas of avoiding this limitation like creating shortcuts to scripts that were flashing kernels and recoveries on the fly, etc, but it still required to reset the counter with Triangle Away (which was and still is performed NOT on-the-fly on the stock kernel, but requires flashing chainfire's custom "kernel + something" and rebooting into the custom boot screen with big danger sign and asterisk etc etc - takes time and sounds dangerous...)
- finally someone found out that flashing the oldest bootloader possible (dunno if it wasn't even a ICS one?) is a brilliant fix for this situation - this bootloader didn't have flash counter auto-trigger mechanism when non-stock recovery or kernel. I use it since today in that device - that is why I do worry flashing last-week kitkat leak, which requires new bootloader... anyway...
- ...Note Pros won't have ICS bootloaders, of course, BUT there was another fix floating around for other devices like s3 and note 2 (never been ported to N80xx, tho..) - a modded libWFD.so library in /system/lib to force turning off HDCP once and for all. It started from Android 4.2+, required disassembling the lib and messing with some assembly code at first (!), however, after difficult beginnings, further mods for different systems and roms were possible more easily, by editing similiar hex patterns in similiar way in the library binary content (and it was not extremely tiring as it required ediiting only three bytes IN TOTAL!).
Hope the last solution will be brought to our devices in the nearest future as it solves the problem in an ultimate way (eh... at least until there comes an update with major changes, causing lib not to work...).
This was a pain, until someone figured out that
Click to expand...
Click to collapse
Sadly our device does not have the wfdengine.lib. None of the kitkat devices appear to. I do know from reading on the 2014 Forum that hdcp was the Culprit. Hopefully work can be done to twrp to allow its use without breaking this feature
Sent from my SCH-I605 using XDA Premium 4 mobile app

Duly.noted said:
Screen Mirror fixed!!
Thanks to a few guys in the 2014 threads I have finally found a fix for screen mirroring. It is simple and easy to do. simply boot into download mode, hook up to odin and reflash the stock recovery and your done! Using my screen beam pro while posting this right now. If you need the stock recovery it can be found here
B3 for wifi
http://forum.xda-developers.com/showthread.php?p=50492301
It should be Known I've only tested on the p900
Sent from my SM-P900 using XDA Premium HD app
Click to expand...
Click to collapse
Please advise, I will have to convert the recovery.img file to a recovery.tar.md5 file in order to flash using odin, correct?

I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX

xdapao3 said:
I am about to buy a Miracast receiver (probably a Netgear PTV3000) but both my Note II and Note Pro 12.2 are rooted.
I run stock Touchwiz ROMs with stock recoveries, so will Miracast work?
This thread has confused me a bit because I thought that even though you have root, as long as you are running a stock ROM and the stock recovery you would be able to use Miracast.
BTW I have seen mentioned elsewhere that with Samsung Allshare Cast you ALSO have to have "Flash Binary" at zero (which at the moment I have on the Note II thanks to Triangle Away but I haven't on the Note Pro since AFAIK I can't run Triangle Away on it nor I will be able to use Triangle Away on my Note II once I update it to 4.3 or KitKat) and that's why I am going with the Netgear or with the Asus dongle.
Anybody can shed some (definitive) light on these issues..? TNX
Click to expand...
Click to collapse
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).

esgie said:
I have written it two posts above.
As far as I can see at the moment, TA works fine with Note Pro 12.2 (at least on a Qualcomm one...).
EDIT:
Here's libwfds.so for Note Pro 12.2 LTE P905, modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..), it seems to work with custom recovery (repacked, not-yet-fully-working TWRP).
Just put it in /system/vendor/lib and replace previous one (also, make sure permissions are 644, root:root).
http://www28.zippyshare.com/v/17510448/file.html
IT WILL PROBABLY NOT WORK ON EXYNOS DEVICES (P900 etc).
Click to expand...
Click to collapse
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install

THEDEVIOUS1 said:
:highfive:
I can confirm that this in fact DOES work...not only only that but it SHOULD be good to go for ANY device with a snapdragon 800 running 4.4.2. I'm actually using it on the LTE variant of the tab pro 8.4 and everything is ok...i tested it for a full 2 hours the other night with TWRP installed & didnt have any problems besides an occassional hiccup when trying to connect. For anybody reading this...i'm not sure if the order is important but i replaced the above file BEFORE i flashed the custom recovery although that shouldnt matter. Also...u MAY need to wipe both caches after u install
Click to expand...
Click to collapse
Nice to know
Btw I replaced it after flashing TWRP, so it should work both ways.
Feel free to post it in the other devices' forums if you find it helpful.

esgie said:
Here's libwfds.so modified by me (based on XXUANC3 stock firmware, can't guarantee it will work on any other firmware than this one..),
Click to expand...
Click to collapse
Really thanks for being so helpful man, but there lies the problem, I can't get a Miracast setup and be at the constant risk that an update breaks it..

Rooting and hyperspace new rim help

I have root access according to root checker via towelroot. .and installed safestrap but every time I restart it says it disabled and when I open the app it say not active. ..I put hyperrom on and no data and wifi..at all..I'm currently on nc1...Someone please help...I flashed my backup so that's what I'm on now..thanks

I'm on i337...nc1...tried almost every method possible

Here's what I'm on

Potter86 said:
Here's what I'm on
Click to expand...
Click to collapse
Download the selinux mode changer and change it to permissive. Then install safestrap
Flash the nc1 module to get Wi-Fi
Sent from my Nexus 5 using XDA Free mobile app

That's what I did and still had no data...at one point I had wifi but couldn't remember which module I had installed at the time...so many that I have triee...unbelievable. ..I was thinking about just using my backup and only restoring data and then putting in an myself if I can find it

And why does safe strap say disabled every time I restart?

Potter86 said:
And why does safe strap say disabled every time I restart?
Click to expand...
Click to collapse
Initially safestrap was developed to provide multi ROM support. It would say enabled only when ROM slot is used.
On i337, KitKat Roms only works with stock slot and so you can ignore that message.
For WiFi, you need to flash the NC1 modules.
For data, you would have to configure the APN

jmjoyas said:
Initially safestrap was developed to provide multi ROM support. It would say enabled only when ROM slot is used.
On i337, KitKat Roms only works with stock slot and so you can ignore that message.
For WiFi, you need to flash the NC1 modules.
For data, you would have to configure the APN
Click to expand...
Click to collapse
Unfortunaly there's a lot of nice modules on here that I need to try and see if one freaking works

Potter86 said:
Unfortunaly there's a lot of nice modules on here that I need to try and see if one freaking works
Click to expand...
Click to collapse
In the general forum go-to index, all things AT&T..... The modules you are looking for are there.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
In the general forum go-to index, all things AT&T..... The modules you are looking for are there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok i finally got my phone up and running with hyperdrive 18...the only issue now is the hyperdrive tweaks are not working???? so i ended up doing the hyperdrive 18.1 update and flashed that...everything fine again now except the tweaks still????

My guess is that flashing the att buildprop apn file is messing up tweaks. Reinstall without doing the att build.prop APN flash. The dev has supposedly built in at support so the separate buildprop flash should not be needed. Just select att during installation.
Sent from my SGH-M919 using Tapatalk

I'm trying to do rls19 now and having same issue... No wifi too... And the built in not working nor any of the ones I can find on the site

Problems getting SElinux to permissive plz help

Let me first start by saying ive done a ton of research and still dont know alot about modifying phones . With that said I tried to search on here for any help and everything I seem to try doesnt work or I hit a dead end. I have a galaxy s5 Active SM-G870A running 4.4.4 kitkat. I am trying to get my appradio 3s touch to work with this phone and have it narrowed down to the fact that my selinux is set to enforcing. My phone is rooted with Towelroot (used a tutorial from wolfdroid.com). As I said Ive searched around on these forums and found a few different things and have tried all of them to no avail. Some of the things Ive tried are as follows , tried the selinux mode changer app (I do have super user permission set to granted) also tried using xposed framework. Last I found a thread on here with instructions
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364
I started to work my way through that. I have Busybox installed and then I tried to work my way to get init.d support. That led to me trying to use Terminal Emulator to add init.d support through the Term-init thread I found. Followed those instructions but now im stuck as I have the Term-init.sh file on my root dir of my sd card but terminal emulator just says it cant find it when I search for it. All in all im just trying to get this phones SElinux set to permissive. Please help point out anything I may have missed because of stupidity, I would really like to use my appradio the way I had originally intended to. Thanks for any and all help also let me know if there is anymore information needed from my end that will "help you" help me.
P.S. Sorry for the long read...

I don't know much about your issue, but having busybox installed is only half the job.......have you opened busybox, run the app and downloaded and installed all the required 'applets'?
Sent from my rooted kn0x0 SM-G900F S5

Yes I have, I installed the applets, first time I tried it said it failed so I changed the dir to just system/bin and tried again and it worked.

I too can't get it to be permissive. Tried pretty much everything I've found and nothing, stays on enforcing

I've done a bit of digging/research on this.......It seems that nobody has had much success in achieving this with a stock setup. The one main app developer according to his thread here on XDA, believes that KNOX may be responsible for the difficulties. The only progress that I've seen is where a developer has written a whole new kernel where the state is set to permissive by default.......
So as far as I can work out, if you need SElinux to be permissive, you'll have to flash one of these custom kernels.....and we all know what that'll do to KNOX........
Sent from my rooted kn0x0 SM-G900F S5

keithross39 said:
I've done a bit of digging/research on this.......It seems that nobody has had much success in achieving this with a stock setup. The one main app developer according to his thread here on XDA, believes that KNOX may be responsible for the difficulties. The only progress that I've seen is where a developer has written a whole new kernel where the state is set to permissive by default.......
So as far as I can work out, if you need SElinux to be permissive, you'll have to flash one of these custom kernels.....and we all know what that'll do to KNOX........
Sent from my rooted kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Thanks for the info, I seemed to find away around my problem for now. . I'm curious what happens when Knox is tripped? I've heard it voids the warranty but other than that what's the big deal if you plan on keeping the phone?

Sams**t get kinda 'iffy' about knox tripped phones.....I read somewhere on here that a knox tripped phone needed a repair, and they refused to do it.....Even though the phone owner offered to pay in full for the repair.....
Sent from my rooted kn0x0 SM-G900F S5

I have a nexus 4 i change the SElinux mode by an app called SElinux mode changer, works fine for me can't say it will work on GS5, but its worth a try
EDIT: IT PROBABLY WON'T WORK ON SAMSUNG DEVICES.

sachin.parmar100 said:
I have a nexus 4 i change the SElinux mode by an app called SElinux mode changer, works fine for me can't say it will work on GS5, but its worth a try
EDIT: IT PROBABLY WON'T WORK ON SAMSUNG DEVICES.
Click to expand...
Click to collapse
According to the app Dev, he thinks that KNOX stops his app functioning properly......
So no, won't work on the S5.......or any other KNOX infected device......
Basically, any high end phone produced by Samsung since the S3.......
https://www.samsungknox.com/en/products/knox-supported-devices
Sent from my rooted kn0x0 SM-G900F S5

keithross39 said:
According to the app Dev, he thinks that KNOX stops his app functioning properly......
So no, won't work on the S5.......or any other KNOX infected device......
Basically, any high end phone produced by Samsung since the S3.......
https://www.samsungknox.com/en/products/knox-supported-devices
Sent from my rooted kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Thanx for clarifying