[TUT] Disable SElinux in Touchwiz 4.3 - Sprint Samsung Galaxy S III

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.

Related

Device not booting after first ROM flash

Hi guys, I am very new to this community and this is my first post. So this is what happened:
I had my One X for about 4 months now, and I was starting to want something new so I rooted it and unlocked the bootloader everything went just fine. So I realized root isn't the only big thing you can do to tweak your device so I wanted to flash a custom ROM. I wanted to customize it so I used this guide: http://forum.xda-developers.com/showthread.php?t=1611349 to customize CMOD 10 based on Jelly Bean and flash it to my device. So I finished my custom ROM and wanted to flash it to my device. So I used this guide: http://forum.xda-developers.com/showthread.php?t=2069904 (post 2 only (of course)).
At first when I tried to flash my custom ROM I didn't make any backup because I had Titanium backup and I thought that it does the same thing as recovery backup (now I know it doesn't) so I don't have the stock ROM on backup. I was disappointed that the device won't boot, it only shows the boot screen "HTC quietly brilliant". And then I saw boot.img I didn't knew what to do with it so I read about it and found out that I need to flash the boot.img before I flash the ROM. So I deleted everything again and done it all over again, but I flashed boot.img that came with the CM 10 first and then flashed the ROM itself. I've done everything correctly and my device still won't boot. It's over 20 minutes and still showing the "HTC quietly brilliant" like before the boot.img.
What should I do and very much thanks for the helpers I don't want to lose my device. :crying:
EDIT: I forgot to mention that this is my first android device.
Try - fastboot erase cache - while in fast boot
Sent from my HTC One X using xda premium
Clean install? Try to clear cache in recovery.
Boot to bootloader (voldown and power). On the top you should see hboot version. What is it?
Also, does fastboot say OKAY when boot.img is flashed?
Sent from my EndeavorU using xda app-developers app
cleancorekiller said:
Try - fastboot erase cache - while in fast boot
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Already tried it. And this is CM10 I downloaded it from their github can't be broken.
THX for the replay BTW.
revolve narytia
TToivanen said:
Clean install? Try to clear cache in recovery.
Boot to bootloader (voldown and power). On the top you should see hboot version. What is it?
Also, does fastboot say OKAY when boot.img is flashed?
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Already tried to clear cache... A LOT.
HBOOT version is: 1.39.0000
And yes it does say OKAY when boot.img is flashed.
And I already tried clean install a lot.
Okay matey, here's your problem:
You need a special boot.img for your newer hboot version. Check post # 9308 in CM10 thread for link.
Unfortunately GPS doesn't work with this boot.img.
Edit: right post number
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Okay matey, here's your problem:
You need a special boot.img for your newer hboot version. Check post # 1308 in CM10 thread for link.
Unfortunately GPS doesn't work with this boot.img.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
You are my new god. I will pray for you everyday.
THANK YOU I will report if this will work. Do you know when or where will there be a one with working GPS?
Tomervutx said:
You are my new god. I will pray for you everyday.
THANK YOU I will report if this will work. Do you know when or where will there be a one with working GPS?
Click to expand...
Click to collapse
LOL, just click the thanks button.
Gps will be fixed when slow-ass HTC releases the JB kernel source code. Until then, you can use Trip's CM10 or IceColdJelly 4.2.1 for working GPS.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
LOL, just click the thanks button.
Gps will be fixed when slow-ass HTC releases the JB kernel source code. Until then, you can use Trip's CM10 or IceColdJelly 4.2.1 for working GPS.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Mind sharing a link? will save me a lot of time.
link
TToivanen said:
link
Click to expand...
Click to collapse
You saved my life. Thank you again!
TToivanen said:
link
Click to expand...
Click to collapse
It's not working... I clean installed my customized CM10 ROM and then the boot.img you gave me. (I tried vice versa too). It's booting and then restarting to recovery mode.
Probably something went wrong when you customized it. What exactly did you do? Why not just download it as it is?
And when you talked about github.... you mean you built it from source?
TToivanen said:
Probably something went wrong when you customized it. What exactly did you do? Why not just download it as it is?
And when you talked about github.... you mean you built it from source?
Click to expand...
Click to collapse
I did built it form source. I got in a folder 3 files: 2 folders: system and META-INF 3rd file is boot.img.
I probably don't know what to put in update.zip (what folders) would you tell me?
I customized some colors, battery skin on the status bar and fonts. I also customized build.prop and added adrenaline script so I got another folder named "data".
could you tell me how to pack it all to update.zip? I guess my problem is that.
P.S. I also sign it after packing it to update.zip with auto-signer using java.
THX in advance!
Here's one idea: Download the pre built zip of the rom and use it as a template. Replace all the folders inside with your own, custom ones.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Here's one idea: Download the pre built zip of the rom and use it as a template. Replace all the folders inside with your own, custom ones.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
I tried it this is the result... Don't you have an experience with ROM building?
Not sure if you understood correctly.
I meant you should dl the rom from get.cm and then replace the files with the ones you built and modified.
If this is exactly what you did, then I'm out of ideas.
I, in fact, haven't built a rom from source in my life.
Sent from my EndeavorU using xda app-developers app
TToivanen said:
Not sure if you understood correctly.
I meant you should dl the rom from get.cm and then replace the files with the ones you built and modified.
If this is exactly what you did, then I'm out of ideas.
I, in fact, haven't built a rom from source in my life.
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
I haven't built it from source. I downloaded the base CM10 mod and edited it's files and compressed and flashed to my device. But I am checking another option.
Why not flash the rom as it is and put your own stuff to system afterwards with adb or an file explorer ?
MeLViN-oNe said:
Why not flash the rom as it is and put your own stuff to system afterwards with adb or an file explorer ?
Click to expand...
Click to collapse
I am editing it with dsixda kitchen and I found out what was my problem... I added Adrenaline script and I need to add support to that through dsixda-android kitchen. Any idea how?

[MOD] Enable Native Tethering without limits

The following Mod will unlock all APNs for editing, and allow you to tether using the Stock Built-in tethering:
For this to work, you must be rooted, and have busybox installed.
This is confirmed working on T-Mo software version 1.12.531.19 It may work for others, but they should probably have their own Settings.apk mod done to avoid issues.
People were having problems installing this via ADB, so I have made a flashable zip to simplify the process:
Step 1:
Flash this via recovery: http://www.cheatersedge.org/android/m8/TetherZip.zip
Click to expand...
Click to collapse
Step 2:
Once your phone has rebooted, go into Settings -> Mobile Data -> Access point names.
Select the one for "T-Mobile Data" Which should now be editable.
Scroll down, and change the APN protocol from IPv6 to IPv4.
Select Menu and hit "Save"
Click to expand...
Click to collapse
OLD Instructions:
Step 1:
Download the following modded Settings.apk to the root of /sdcard/: http://www.cheatersedge.org/android/m8/Settings.apk
Click to expand...
Click to collapse
Step 2 (Via ADB):
Code:
adb shell
su
mount -o remount,rw /system
sed -i s/pcweb.tmobile.com/fast.t-mobile.com/g /system/customize/ACC/default.xml
cp /sdcard/Settings.apk /system/app/Settings.apk
chmod 644 /system/app/Settings.apk
mv /system/app/Settings.odex /system/app/Settings.odex.bak
reboot
Click to expand...
Click to collapse
Step 3:
Once your phone has rebooted, go into Settings -> Mobile Data -> Access point names.
Select the one for "T-Mobile Data" Which should now be editable.
Scroll down, and change the APN protocol from IPv6 to IPv4.
Select Menu and hit "Save"
Click to expand...
Click to collapse
Step 4:
Enjoy fully working tethering over the normal APN.
Click to expand...
Click to collapse
Step 5:
Someone else should make a flashable zip *Hint* step 3 can be done with sqlite3 in the command line but... I am feeling lazy .
Click to expand...
Click to collapse
Fenny said:
The following Mod will unlock all APNs for editing, and allow you to tether using the Stock Built-in tethering:
For this to work, you must be rooted, and have busybox installed.
This is confirmed working on T-Mo software version 1.12.531.19 It may work for others, but they should probably have their own Settings.apk mod done to avoid issues.
Click to expand...
Click to collapse
How would you go about getting this to work on a deodexed ROM? I just attempted the walkthrough with ARHD 3.4 and it didn't work, my APN settings are still locked
Fenny said:
The following Mod will unlock all APNs for editing, and allow you to tether using the Stock Built-in tethering:
For this to work, you must be rooted, and have busybox installed.
This is confirmed working on T-Mo software version 1.12.531.19 It may work for others, but they should probably have their own Settings.apk mod done to avoid issues.
Click to expand...
Click to collapse
Is there an elaborate explanation to step 2? I'm new to HTC and have never used terminal or adb. Was blessed on my Razr HD. Thank you.
Sent from my HTC One_M8 using Tapatalk
The_Blue_Bomber said:
Is there an elaborate explanation to step 2? I'm new to HTC and have never used terminal or adb. Was blessed on my Razr HD. Thank you.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You would enter those commands through the command prompt where you have your android sdk set up.
hawaiianboi said:
You would enter those commands through the command prompt where you have your android sdk set up.
Click to expand...
Click to collapse
Okay. Thank you
Sent from my HTC One_M8 using Tapatalk
nonmindo said:
How would you go about getting this to work on a deodexed ROM? I just attempted the walkthrough with ARHD 3.4 and it didn't work, my APN settings are still locked
Click to expand...
Click to collapse
ARHD probably has a different Settings.apk. The APN unlocking magic is in my modded Settings.apk. I have patched it to simply ignore the "readonly" value in telephony.db.
Sent from my HTC One_M8 using Tapatalk
I'm assuming you'll still have to use a VPN to encrypt your HTTP headers, or spoof your useragent to show up as a mobile device. Otherwise, T-Mobile will mark unencrypted traffic as tethering anyway. I would love to be wrong on this one, but I don't think it's _that_ simple otherwise.
Also, I find the replacing and modifying of files to be easier in Recovery than when booted into the system. System has some annoying write protection to deal with.
Sent from my HTC One_M8 using Tapatalk
blakejohnson86 said:
I'm assuming you'll still have to use a VPN to encrypt your HTTP headers, or spoof your useragent to show up as a mobile device. Otherwise, T-Mobile will mark unencrypted traffic as tethering anyway. I would love to be wrong on this one, but I don't think it's _that_ simple otherwise.
Also, I find the replacing and modifying of files to be easier in Recovery than when booted into the system. System has some annoying write protection to deal with.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
User agent spoofing is still required. Particularly if you are trying to use IE. Just spoof the same Desktop UA string that mobile chrome spoofs, and you are all set.
You can also change the protocol by doing:
Code:
sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db
update carriers set protocol='IPV4V6' where protocol = 'IPV4';
Sent from my HTC One_M8 using Tapatalk
What is the best way to install Busybox so I can get this working? I get crashes/reboots/errors when trying to install busybox.
I assume that because the system is read-only.
@Turge can you do this on ViperM8 setting.apk rom?
Sent from my HTC One_M8 using Tapatalk 2
epsix said:
@Turge can you do this on ViperM8 setting.apk rom?
Sent from my HTC One_M8 using Tapatalk 2
Click to expand...
Click to collapse
I can do a writeup if you need one,
But for now: Hint: look for the string "readonly" in Settings.
captainreynolds said:
What is the best way to install Busybox so I can get this working? I get crashes/reboots/errors when trying to install busybox.
I assume that because the system is read-only.
Click to expand...
Click to collapse
You'll need root. Grab the busybox installer from the google play store, it's the easiest way
I tried this and it isn't working for some reason. As far as I can tell all commands worked, but the APN is still locked. Running the same software version as the OP. Rooted/Busybox are installed.
DrownedElf said:
I tried this and it isn't working for some reason. As far as I can tell all commands worked, but the APN is still locked. Running the same software version as the OP. Rooted/Busybox are installed.
Click to expand...
Click to collapse
Same here. Also after I did this, every time I boot my phone. It says limited service on the lock screen. Never seen that before.
Sent from my HTC One_M8 using Tapatalk
The_Blue_Bomber said:
Same here. Also after I did this, every time I boot my phone. It says limited service on the lock screen. Never seen that before.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Which ROM are you running?
Sent from my HTC One_M8 using Tapatalk
Fenny said:
Which ROM are you running?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just stock rooted.
Sent from my HTC One_M8 using Tapatalk
The_Blue_Bomber said:
Just stock rooted.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Look in /system/app is there a Settings.odex there?
Sent from my HTC One_M8 using Tapatalk
Fenny said:
Look in /system/app is there a Settings.odex there?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes
Sent from my HTC One_M8 using Tapatalk
The_Blue_Bomber said:
Yes
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Wait... did you install this from recovery? If you run those commands from recovery you need to mount system first.
(Advanced -> mounts)
That file should not have been there.
Fenny said:
Wait... did you install this from recovery? If you run those commands from recovery you need to mount system first.
(Advanced -> mounts)
That file should not have been there.
Click to expand...
Click to collapse
No, I just ran adb while the phone was on. Was I not supposed to?
The_Blue_Bomber said:
No, I just ran adb while the phone was on. Was I not supposed to?
Click to expand...
Click to collapse
No, that is fine, it should have worked then. Verify that Settings.apk contains a classes.dex, and delete the Settings.odex file.

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.

hotspot

i have s6 sprint unlocked living outside USA and using sim other than sprint. i updated my phone to MM but i am not able to use hotspot as there is no option in settings for wifi tether ... pls help
Try THIS
1619415 said:
Try THIS
Click to expand...
Click to collapse
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
tdhite said:
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Your old one still works
1619415 said:
Your old one still works
Click to expand...
Click to collapse
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
tdhite said:
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Kernel Auditor has init.d emulation that's what I'm using, I just copied the code from the script and put it in
tdhite said:
I am also putting out (soon) a zip flash that will correct the phone for wifi hotspot and also enabling init.d support. If you are rooted, you are welcome to test it out.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Thank you, i will wait for the zip file ☺
tdhite said:
Yea, but init.d support is needed in stock ROM so it can do its work every boot to make sure it sticks. Besides, nice to have busybox support while we hack up some base setups on the way to real Roms.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Are you just going to make a kernel?
1619415 said:
Are you just going to make a kernel?
Click to expand...
Click to collapse
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
tdhite said:
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
Click to expand...
Click to collapse
I'll check it out later, thanks man:good:
tdhite said:
Yes, working on that. But the flash needs no kernel update (it modifies /init.rc to inject init.d support into stock or other roms missing init.d support).
It's up: http://forum.xda-developers.com/showpost.php?p=65864177&postcount=8
For kernels, I will use the same basic model, inject the kernel and any necessary init.rc support into the existing boot.img, not require a complete boot.img load. I also dislike modifying start scripts in /system/etc to try to inject init.d support because /init.rc can do it much easier and more controllably.
You are welcome to look at the flash in the above post to see how the tools in the "tools" directory perform boot.img extraction, explosion, fixup, then repack if that's not familiar. Only diff with a kernel is to replace the zImage with the custom kernel in the repack command. Makes the flash much smaller since I don't have to carry the ramdisk just for a kernel update.
Click to expand...
Click to collapse
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Screenshot
omar_31091 said:
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Click to expand...
Click to collapse
Screenshot
omar_31091 said:
Dude, i tried both the files, installed from twrp but none of them worked still no hotspot...
On lollipop i had no such issue of hotspot.
Click to expand...
Click to collapse
Are you rooted? Please attach the file at /data/local/tmp/tdh-hotspot.log so i can see what it is doing. On your phone.
Here is what my OTA had after flashing the mod -- hotspot is there.
Sent from my SM-G920P using Tapatalk
Yes ..
tdhite said:
Are you rooted? Please attach the file at /data/local/tmp/tdh-hotspot.log so i can see what it is doing. On your phone.
Here is what my OTA had after flashing the mod -- hotspot is there.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yes, i am rooted
Ok, thinking the db update might be too late in the boot process for the settings app to pick it up.
Can you reboot and resend that log file and also check settings again?
Sent from my SM-G920P using Tapatalk
tdhite said:
Ok, thinking the db update might be too late in the boot process for the settings app to pick it up.
Can you reboot and resend that log file and also check settings again?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
I installed it again restarted 2-3 times nothing has change in the settings, maybe i should wait for the custom rom to come....

[DISCONTINUED][TOOL] Zenfone Toolkit for Kitkat WW 2.22.40.540

Description
This toolkit is an integrated pack tool for Zenfone 5 base on latest kitkat SKU WW 2.22.40.540. All file is come from the original firmware. None of them modified. So it wont harm your phone. Do not change any single file inside or the script will not run.
For Lollipop version check here :
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
How to run
Just extract to any folder and run Zenfone_Toolkit_2.22.40.540.exe then select what you need to do. We know almost all of selected choice do. I wont explain everything here.
Menu Selected Tool as seen on attachment
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
This is the flashable stock ROM Pre-root 2.22.40.540 with SuperSU v2.65. Backup your data first before select this tool, because the script will erase all incl your data before flash system.img
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash ryanjms07 Kernel
15. Install Intel Android USB, ISocUSB and Asus PClink
Credit :
1. @shakalaca aka Shaka Huang for root, unroot, unlock and relock bootloader.
2. @ryanjms07 for Kernel Kitkat.
3. @X AnwarMov for twrp 3.0
Download
Zenfone Toolkit Kitkat
Next Revision
Adding some extra feature on menu.
Updating SuperSU v2.76, DT2W, enable RW MicroSD, Xposed, Busybox v1.241
Attention
Use this tool at your own risk.
Will this solve freezing issue getting after unlocking bootloader??
Mir Shahjahan said:
thanx man
Click to expand...
Click to collapse
You welcome
Sent from my ASUS_T00F using XDA-Developers mobile app
Good Job Kabanjahe Thanks..
unas1990 said:
Good Job Kabanjahe Thanks..
Click to expand...
Click to collapse
You welcome
Sent from my ASUS_T00F using XDA-Developers mobile app
Is this tool still available? I only see md5 file in the link above..
Thanks
Sent from my Xiaomi Redmi 3 using XDA Labs
anggabastian said:
Is this tool still available? I only see md5 file in the link above..
Thanks
Sent from my Xiaomi Redmi 3 using XDA Labs
Click to expand...
Click to collapse
I will upload it to night for the new release
Sent from my ASUS_T00F using XDA-Developers mobile app
anggabastian said:
Is this tool still available? I only see md5 file in the link above..
Thanks
Sent from my Xiaomi Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Done
Sent from my ASUS_T00F using XDA-Developers mobile app
Thank you very much
nttL said:
Thank you very much
Click to expand...
Click to collapse
You welcome
Sent from my ASUS_T00F using XDA-Developers mobile app
Hello, I have a common problem with my devise being not the only one connected to PC/emulated.
"Error: more than one device/emulator" - I have an additional offline emulator and i cant track what created it.
I was able to correct this issue by adding
adb -s (dev. serial) wait-for-devices
adb -s (dev. serial) reboot bootloader
(or "-d" if there is only one physical device)
In .bat files in similar programs, but this package is a bit too complicated for me and i am not sure how and where to correct this. Any advice?
Voronko said:
Hello, I have a common problem with my devise being not the only one connected to PC/emulated.
"Error: more than one device/emulator" - I have an additional offline emulator and i cant track what created it.
I was able to correct this issue by adding
adb -s (dev. serial) wait-for-devices
adb -s (dev. serial) reboot bootloader
(or "-d" if there is only one physical device)
In .bat files in similar programs, but this package is a bit too complicated for me and i am not sure how and where to correct this. Any advice?
Click to expand...
Click to collapse
i write the script using new adb platform 1.035. The script will still running on the background even you close the window. You need to choose menu EXIT when you done.
For me v1.035 more better than v1.032.
Every menu already test and work very well
Sent from my ASUS_T00F using XDA-Developers mobile app
Thank you very much.
Can't wait for next version which is with Xposed Module.
As of now i am having problem to install the Xposed Module in this firmware WW 2.22.40.540.
The "Install / Update" is grey out and there is few red sentences on top of the button.
williamstans said:
Thank you very much.
Can't wait for next version which is with Xposed Module.
As of now i am having problem to install the Xposed Module in this firmware WW 2.22.40.540.
The "Install / Update" is grey out and there is few red sentences on top of the button.
Click to expand...
Click to collapse
You welcome..
As i only have 1 zenfone 5 to test this, and now for daily use on .87 stock. Need some extra time to update this tool again.
Thank you for using my tool.
Sent from my ASUS_T00F using XDA-Developers mobile app
sorry, i'm a bit confused. do i have to download all three files from that link or just 1. i'm new to this root kind of stuff and not an IT guy either
supercell12 said:
sorry, i'm a bit confused. do i have to download all three files from that link or just 1. i'm new to this root kind of stuff and not an IT guy either
Click to expand...
Click to collapse
1. rar file is all integrated tool.
2. md5 is a file to check nr 1 file for sure.
3. fix.rar is an fix script for nr 1. This file already in nr1. Its just a fix.
Sent from my ASUS_T00F using XDA-Developers mobile app
help it seems when I try to download from the link I need permission from owner to download it.
Can you please grant access? already sent a request.
I can't download "Zenfone_Toolkit_2.22.40.540.bat"
can someone who downloaded it can please upload it on mediafire or google drive(with no permissions) and send me or PM me the link. really need this badly. would greatly appreciate it.
chowking202 said:
help it seems when I try to download from the link I need permission from owner to download it.
Can you please grant access? already sent a request.
Click to expand...
Click to collapse
Sorry i will upload it tonight, my drive is over limit

Categories

Resources