Develop Bugs

[Q] Help with enabling init.d support for Jelly Dream 4.5 on Locked bootloader

Hello all, I am about to install part 1 of 2 for jelly dream 4.5, and because my phone has locked bootloader, MXY1997 says I need to enable init.d support. I have never done this process before and I need someone to help a noob out. If someone could give me a link or type out a procedure that would be great.
Thanks, Alex.

anyone??

Just install the ROM, it has built in init.d support.
There is no point in installing init.d before the ROM installation, it gets deleted in the process of installing the ROM anyway.

Someguyfromhell said:
Just install the ROM, it has built in init.d support.
There is no point in installing init.d before the ROM installation, it gets deleted in the process of installing the ROM anyway.
Click to expand...
Click to collapse
I have done that, but now I don't have CWM to install part 2 of the rom.

mandris said:
I have done that, but now I don't have CWM to install part 2 of the rom.
Click to expand...
Click to collapse
I always use this to enable init.d support on stock kernel
http://forum.xda-developers.com/showthread.php?p=20574274
But I do not get y u are enabling init.d support
There is no point in this as far as I kno
Sent from my LT18i using xda app-developers app

mandris said:
I have done that, but now I don't have CWM to install part 2 of the rom.
Click to expand...
Click to collapse
Install cwm with x-parts than flash part 2
No need for enabling init.d support
Sent from my LT18i using xda premium

[TUT] Disable SElinux in Touchwiz 4.3

Hello guys, and even though many are on a stock rooted 4.3 Rom, people including me will still have slight limitations to what we can do because of SElinux being enabled.
1st: you have to flash a pre rooted mk3 rom. OTA update will not work.
2) next, download terminal emulator for android.
3) one your in type "su". Ignore the other text.
4) next type"setenforce 0"
Then your done! Make sure to close the session so your battery will last.
If you get a notification to reboot to restore SElinux, dismiss it and it won't pop up again.
Enjoy your fully unlocked system!
Sent from my SPH-L710 using xda app-developers app
Hit that thanks if I helped!

Here is a picture for reference:
Sent from my SPH-L710 using xda app-developers app

nick benedetto said:
Hello guys, and even though many are on a stock rooted 4.3 Rom, people including me will still have slight limitations to what we can do because of SElinux being enabled.
1st: you have to flash a pre rooted mk3 rom. OTA update will not work.
2) next, download terminal emulator for android.
3) one your in type "su". Ignore the other text.
4) next type"setenforce 0"
Then your done! Make sure to close the session so your battery will last.
If you get a notification to reboot to restore SElinux, dismiss it and it won't pop up again.
Enjoy your fully unlocked system!
Sent from my SPH-L710 using xda app-developers app
Hit that thanks if I helped!
Click to expand...
Click to collapse
ILU
This should work on Galaxy S4 as well, right?

Good call on this trick. I just updated to 4.3 and this was up there on my todo list.

Just a note for everyone, this is predisabled in my rom, which the two other MK3 roms are based on
So need to do it manually if you flash the MK3 roms we have right now, but good info nick!

What is SElinux and why should it be disabled?
Sent from my SPH-L710 using Tapatalk

Is this the thing in the about phone settings that says SE for Android Permissive.
Sent from my SPH-L710 using XDA Premium 4 mobile app

bstangs1 said:
Is this the thing in the about phone settings that says SE for Android Permissive.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, it's set to enforce by default, but I changed it to permissive by default

Ok cuz mine says permissive so that's ok right and by the way im on ur 4.3 rom and it runs smooth, so far no issues with mine. Thanks.
Sent from my SPH-L710 using XDA Premium 4 mobile app

I installed your stock rooted rom and it was on enforced. So if anyone has this issue then refer to my tutorial.
Sent from my SPH-L710 using xda app-developers app

Should work on any android device running 4.3+. Let us know if it worked.
Sent from my SPH-L710 using xda app-developers app

masaidjet said:
What is SElinux and why should it be disabled?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
@masaidjet selinux is a low level security mechanism for android. But samsung turned it into a b¡T©h and it will Force close any app that request system permissions in a stock touchwiz rom. Disabling it will give it full acess to the system again like in MD4.
Sent from my SPH-L710 using xda app-developers app

wouldn't it revert to enforcing after rebooting your device? Is there a configuration file that we can modified? TQ.

xbean said:
wouldn't it revert to enforcing after rebooting your device? Is there a configuration file that we can modified? TQ.
Click to expand...
Click to collapse
Unpack boot.img > ramdisk > init.rc
Look for "init.svc.boot"
Find the line that says "setenforce 1" and change the 1 to a 0
Save, recompile boot.img, and flash the new boot.img with selinux disabled in the kernel

How do I flash the recompiled boot.img into the phone? ODIN or CWM? I don't have ZIP file or MD5 file. Which option should I choose? TQ.
CNexus said:
Unpack boot.img > ramdisk > init.rc
Look for "init.svc.boot"
Find the line that says "setenforce 1" and change the 1 to a 0
Save, recompile boot.img, and flash the new boot.img with selinux disabled in the kernel
Click to expand...
Click to collapse

I found your guidelines here http://forum.xda-developers.com/showthread.php?t=2319018 . Are you referring to executing unpack command to unpack boot.img using the tools in the above URL? TQ.
CNexus said:
Unpack boot.img > ramdisk > init.rc
Look for "init.svc.boot"
Find the line that says "setenforce 1" and change the 1 to a 0
Save, recompile boot.img, and flash the new boot.img with selinux disabled in the kernel
Click to expand...
Click to collapse

xbean said:
I found your guidelines here http://forum.xda-developers.com/showthread.php?t=2319018 . Are you referring to executing unpack command to unpack boot.img using the tools in the above URL? TQ.
Click to expand...
Click to collapse
Yup, that's what I meant
And to flash the new boot.img, you can just make it into a flashable zip and stick your new boot.img in there to flash

Excellent. I've extracted the kernel, modified & recompiled the kernel. TQ.
CNexus said:
Yup, that's what I meant
And to flash the new boot.img, you can just make it into a flashable zip and stick your new boot.img in there to flash
Click to expand...
Click to collapse

Not working.
I tried this on CM11 and it did nothing for me. Guess it doesn't work for custom ROMs.

Possible Root Method for 5.1.1, Need Help..

Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.
I used the root method from CF-autoroot.
Once it failed I pulled the battery and flashed SuperSU-v2.19zip..
Now I get the binary update notification...
If I can just get some help from anyone that knows what they are doing that would be awesome..
Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing
BTW: I got the 64 su file from root junky...

I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk

samep said:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..

z31k said:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
Click to expand...
Click to collapse
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Edit 2: if using custom kernel, don't need liboemcrypto.so
Sent from my SM-N910P using Tapatalk

samep said:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app

pbedard said:
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.
I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.
Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
Sent from my SM-N910P using Tapatalk

Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app

Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??

pbedard said:
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?

Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?

z31k said:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
Click to expand...
Click to collapse
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk

samep said:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.

z31k said:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
Click to expand...
Click to collapse
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk

samep said:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.
So with all that said, i really appreciate your help. Its a great step at a fresh direction.

HTC 10 - Getting SELinux Permissive

I have a couple apps that need selinux permissive but attempting any past methods seems to throw an error during boot that the "android system has experienced an error and must be reset/wiped" (or something like that).
My last HTC One, M7 and M8 (m8 on marshmallow), I could just use init.d to enforce permissive. When I do it on my rooted, s-off htc 10, I get that error during bootup if I use init.d. If I run the script post boot up, the apps work fine however I need it to be permissive by default.
Is this due to the new security and encryption issues?
I see lee's ROM has permissive but his scripts would not work for me either.
Does anyone know how to get permissive working or provide a script to flash for those of us who need it?
Does system need to be RW for it to work? If so, is there a script for the 10 to do that as well?
Thank you!

MNoisy said:
I have a couple apps that need selinux permissive but attempting any past methods seems to throw an error during boot that the "android system has experienced an error and must be reset/wiped" (or something like that).
My last HTC One, M7 and M8 (m8 on marshmallow), I could just use init.d to enforce permissive. When I do it on my rooted, s-off htc 10, I get that error during bootup if I use init.d. If I run the script post boot up, the apps work fine however I need it to be permissive by default.
Is this due to the new security and encryption issues?
I see lee's ROM has permissive but his scripts would not work for me either.
Does anyone know how to get permissive working or provide a script to flash for those of us who need it?
Does system need to be RW for it to work? If so, is there a script for the 10 to do that as well?
Thank you!
Click to expand...
Click to collapse
Same here bro

Raqib1994 said:
Same here bro
Click to expand...
Click to collapse
I ended up using an app called init.d scripts support. Its available in the app store.
After installing it you create a folder with all of your scripts in it. You can then set in the app when you want the scripts to run...automatically, delayed, specific conditions, etc.
I just threw a permissive script in the folder and boom, working perfectly! Let me know if you need the script if you end up taking this route.

MNoisy said:
I have a couple apps that need selinux permissive but attempting any past methods seems to throw an error during boot that the "android system has experienced an error and must be reset/wiped" (or something like that).
My last HTC One, M7 and M8 (m8 on marshmallow), I could just use init.d to enforce permissive. When I do it on my rooted, s-off htc 10, I get that error during bootup if I use init.d. If I run the script post boot up, the apps work fine however I need it to be permissive by default.
Is this due to the new security and encryption issues?
I see lee's ROM has permissive but his scripts would not work for me either.
Does anyone know how to get permissive working or provide a script to flash for those of us who need it?
Does system need to be RW for it to work? If so, is there a script for the 10 to do that as well?
Thank you!
Click to expand...
Click to collapse
Raqib1994 said:
Same here bro
Click to expand...
Click to collapse
MNoisy said:
I ended up using an app called init.d scripts support. Its available in the app store.
After installing it you create a folder with all of your scripts in it. You can then set in the app when you want the scripts to run...automatically, delayed, specific conditions, etc.
I just threw a permissive script in the folder and boom, working perfectly! Let me know if you need the script if you end up taking this route.
Click to expand...
Click to collapse
you could flash this in recovery after the first complete boot of leedroid rom...
SeLinux-Permissive_fix -- > https://www.androidfilehost.com/?fid=24591000424945158

SacredDeviL666 said:
you could flash this in recovery after the first complete boot of leedroid rom...
SeLinux-Permissive_fix -- > https://www.androidfilehost.com/?fid=24591000424945158
Click to expand...
Click to collapse
Thats great! Thank you.
Has this been tested on stock ROM? The update-binary is encoded so I was trying to make sense of it.

MNoisy said:
Thats great! Thank you.
Has this been tested on stock ROM? The update-binary is encoded so I was trying to make sense of it.
Click to expand...
Click to collapse
yeaps it should....
you mentioned you are on Lee or you asking in general would it work for stock?

SacredDeviL666 said:
yeaps it should....
you mentioned you are on Lee or you asking in general would it work for stock?
Click to expand...
Click to collapse
I am on stock 1.80.617, NOT on Lee. I am asking if this works for stock. When he first released his ROM his permissive did not work when I tried (If I recall trying it correctly) but this was on his initial builds.

MNoisy said:
I am on stock 1.80.617, NOT on Lee. I am asking if this works for stock. When he first released his ROM his permissive did not work when I tried (If I recall trying it correctly) but this was on his initial builds.
Click to expand...
Click to collapse
yeaps it should...

MNoisy said:
...Let me know if you need the script if you end up taking this route.
Click to expand...
Click to collapse
It looks like I need it, thanks.

Bill Gamble said:
It looks like I need it, thanks.
Click to expand...
Click to collapse
Attached

MNoisy said:
Attached
Click to expand...
Click to collapse
Looks like it not attaching. Pm me your email

MNoisy said:
Looks like it not attaching. Pm me your email
Click to expand...
Click to collapse
Thanks, anyway. It turns out that the following works just fine:
Code:
#!/system/sh
setenforce 0

[MOD][SU.D SCRIPT] Use Decrypted device and have working mobile network

UPDATE: Thanks to @squid2's insight, there's a better method that should work for everyone. Just download the attached script, remove the .txt extension, and drop into your su.d folder with proper permissions. For more information, see here and here.
------------------------------
This is all thanks to @nkk71, btw. Right now the fix is very hacky but I'm sure ROM devs will find a more appropriate fix soon.
I'm not sure if I want to reveal the fix publicly in case HTC's spies are monitoring the thread, lol....probably better safe than sorry. But go visit nkk71's profile and buy him many beers for figuring this out. And also find some posts by him and click "Thanks."
WARNING: Dragons ahead! Anything you flash to your device is done at your own risk!
EDIT: Alright, I'll publish a flashable zip here based on the 1.53.617.5 US Unlocked Edition. I've been testing the mod/hack for a few days now and have seen no ill effects. It should work fine on ROMs using that base.
I have NO IDEA if it'll work on ROMs using an International/Europe base or on CDMA. If you really want to try it, make sure you make a backup first! You will need to "Format Data" in TWRP and flash the standard SuperSU zip to remove forced encryption (or do it manually, if you know how).
Let the bricking begin!
P.S. Thanks of course also go to @Chainfire for SuperSU and su.d!

Just let the ROM cooks know =)

ChronoReverse said:
Just let the ROM cooks know =)
Click to expand...
Click to collapse
They already do

I don't really find it hacky, just another workaround
Unfortunately, due to personal reasons, I have personally decided not to share this.
(I know you above all others will understand)
It is not a secret, I have a certainly made it public (or so I thought) enough.
Unfortunately the controversy, I'm not willing to deal with... An innocent "share", turned ugly
I fully endorse this method, though I only had 7 mins of testing, before things got very ugly, a very very very very very very very very very very unfortunate incident.
So be it.
The method is still sound, and anybody who wishes to use it, I have neither any objections, just please test it.
Thanks
nkk71
Sent from my HTC 10 using Tapatalk

nkk71 said:
I don't really find it hacky, just another workaround
Unfortunately, due to personal reasons, I have personally decided not to share this.
(I know you above all others will understand)
It is not a secret, I have a certainly made it public (or so I thought) enough.
Unfortunately the controversy, I'm not willing to deal with... An innocent "share", turned ugly
I fully endorse this method, though I only had 7 mins of testing, before things got very ugly, a very very very very very very very very very very unfortunate incident.
So be it.
The method is still sound, and anybody who wishes to use it, I have neither any objections, just please test it.
Thanks
nkk71
Click to expand...
Click to collapse
You think I should post it? Or do you think HTC might find it and try and change their method?

Captain_Throwback said:
You think I should post it? Or do you think HTC might find it and try and change their method?
Click to expand...
Click to collapse
In my humble opinion, go for it
I doubt HTC will change the code, and it is a workaround [emoji2]
Unless something is being changed... Elsewhere (doubt it) , I Personally, have briefly tested and accept it
Sent from my HTC 10 using Tapatalk

nkk71 said:
In my humble opinion, go for it
I doubt HTC will change the code, and it is a workaround [emoji2]
Unless something is being changed... Elsewhere (doubt it) , I Personally, have briefly tested and accept it
Click to expand...
Click to collapse
Done.
This should be fun, lol. Let the brickings begin!

Captain_Throwback said:
Done.
This should be fun, lol. Let the brickings begin!
Click to expand...
Click to collapse
Well I did, trip verity,verified, and a few other things [emoji4]
Oh, wait, I was testing some thing els [emoji23]
Sent from my HTC 10 using Tapatalk

Looking at the logic in the HTC RIL library, in Pythonic pseudocode, it goes something like this:
Code:
if property_get("ro.crypto.state") != "encrypted":
if property_get("persist.radio.current.cnv", default="-1") == "-1":
if htcril_db_property_get("current.cnv") != "-1":
htcril_db_property_set("current.cnv", "-1")
Other libraries then query the htcril DB via the library, and behave differently if the current.cnv property is set in the DB. Based off this, I would guess that doing the following would have a similar effect without needing to hack the library:
Code:
setprop persist.radio.current.cnv 0
I haven't tried this, but I'm curious if restoring the stock libhtcril_db.so and setting this property would work.

squid2 said:
Looking at the logic in the HTC RIL library, in Pythonic pseudocode, it goes something like this:
Other libraries then query the htcril DB via the library, and behave differently if the current.cnv property is set in the DB. Based off this, I would guess that doing the following would have a similar effect without needing to hack the library:
I haven't tried this, but I'm curious if restoring the stock libhtcril_db.so and setting this property would work.
Click to expand...
Click to collapse
Brilliant! That works! Much easier/cleaner solution than hacking the lib
EDIT: Posted script in the OP. Bedtime!

Can anyone remind me/us the pros and cons of decrypting?
Sent from my Nexus 5 using XDA-Developers mobile app

Captain_Throwback said:
You think I should post it? Or do you think HTC might find it and try and change their method?
Click to expand...
Click to collapse
This?

So boot into TWRP, format data and flash regular SuperSu? What are the permissions for the Script ?

squid2 said:
Looking at the logic in the HTC RIL library, in Pythonic pseudocode, it goes something like this:
Code:
if property_get("ro.crypto.state") != "encrypted":
if property_get("persist.radio.current.cnv", default="-1") == "-1":
if htcril_db_property_get("current.cnv") != "-1":
htcril_db_property_set("current.cnv", "-1")
Other libraries then query the htcril DB via the library, and behave differently if the current.cnv property is set in the DB. Based off this, I would guess that doing the following would have a similar effect without needing to hack the library:
Code:
setprop persist.radio.current.cnv 0
I haven't tried this, but I'm curious if restoring the stock libhtcril_db.so and setting this property would work.
Click to expand...
Click to collapse
Captain_Throwback said:
Brilliant! That works! Much easier/cleaner solution than hacking the lib
EDIT: Posted script in the OP. Bedtime!
Click to expand...
Click to collapse
Nice :good:
Strangely enough, I couldn't get the property to stick, but I edited the init.rc directly, didnt use the su.d... maybe I put it in the wrong place

Black_Eyes said:
So boot into TWRP, format data and flash regular SuperSu? What are the permissions for the Script ?
Click to expand...
Click to collapse
Permissions for su.d scripts are 0700. If you want to put the script there while in recovery and you're using systemless root, you can use @osm0sis SUmount zip to mount the su.img and then the TWRP File Manager to copy the script over and change perms. Flash the SUmount zip again to unmount su.img, and then reboot.

Captain_Throwback said:
Permissions for su.d scripts are 0700. If you want to put the script there while in recovery and you're using systemless root, you can use @osm0sis SUmount zip to mount the su.img and then the TWRP File Manager to copy the script over and change perms. Flash the SUmount zip again to unmount su.img, and then reboot.
Click to expand...
Click to collapse
the flashable zip if i want to try on international rom...
i boot into twrp formata data to remove encryption flash super 2.65 stable flash your script and boot will that do?

SacredDeviL666 said:
the flashable zip if i want to try on international rom...
i boot into twrp formata data to remove encryption flash super 2.65 stable flash your script and boot will that do?
Click to expand...
Click to collapse
Don't use the zip. That's the old hack. Use the script. You have to manually place it.
And use the latest SuperSU Beta, not the stable.

Captain_Throwback said:
Don't use the zip. That's the old hack. Use the script. You have to manually place it.
And use the latest SuperSU Beta, not the stable.
Click to expand...
Click to collapse
okay thank you so i would use the latest supersu 2.74beta zip from recovery.
the script isn't downloading for me when i click on it just opens a page with below message
#!/system/bin/sh
# Allow mobile network while decrypted
# thanks @squid2 from XDA for the easy fix!
setprop persist.radio.current.cnv 0
... from pc i am..

SacredDeviL666 said:
okay thank you so i would use the latest supersu 2.75beta zip from recovery.
the script isn't downloading for me when i click on it just opens a page with below message
#!/system/bin/sh
# Allow mobile network while decrypted
# thanks @squid2 from XDA for the easy fix!
setprop persist.radio.current.cnv 0
... from pc i am..
Click to expand...
Click to collapse
Right-click and Save As....

Captain_Throwback said:
Right-click and Save As....
Click to expand...
Click to collapse
thanks got it!!!
place the script in system/su.d folder with the permissions/boot to recovery format data/flash latest supersu beta 2.74 and the let boot finish.....
at htc green logo now...fingers crossed... by the way i was on system mode su prior to trying this mod.
now optimizing the apps...lee's r82 international
---------- Post added at 01:38 PM ---------- Previous post was at 01:16 PM ----------
@Captain_Throwback
came back as encryped only....
the script permission i gave was rwx r-x r-x