Related
This thread is only for the AT&T branded (SM-G900A) device.
If this is not your device, you need to go to the corresponding forum/thread. I realize there are many similarities amongst the G900 variants, but the instructions I provide- as well as the help I can give, are limited to the AT&T (SM-G900A) variant only. Even then the help I can provide is still limited.
Disclaimer:
I am not responsible if you brick, break, or blow up your phone. You assume all and any responsibility for ALL actions you commit to your phone.
1) Xposed Framework
2) WanamXposed
3) Gravity Box
---I advise caution with this, as some of the features are built into the GS5 rom.
4) Greenify
5) X Tether
6) G-TouchWiz
Will post more later!
Notes :
*See the second page on how to activate the built-in wifi tether with Wanam Xposed and X Tether.
*See the second page to help reduce performance issues.
@profcx has pointed out that the "Download Booster Mod" is currently incompatible with the X Tether for Xposed.
Never mind
NM
Downloaded X Tether from Xposed Framework , then go to wanam and click on system and enable "skip provisioning check" and rebooted. It alows me to turn on tethering and mobile Hotspot.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
How to Remove Battery and USB Cover warnings
There has been some complaint about these warnings, so here goes:
1a) Download Xposed
http://repo.xposed.info/module/de.robv.android.xposed.installer
1b) Install it.
1c) Open it up, tap on "Framework," then tap"OK" on the pop up. Then tap "Install/Update"
2) Reboot.
3a) Re Open Xposed, tap "Download, " and search for "G-Touchwiz."
Or go here
http://repo.xposed.info/module/com.gertlily.xposed.touchwiz
3b) Install it. Swipe from left to right and it will show the download options.
3c) Go to the main menu of Xposed, check the box for "G-TouchWiz" then reboot.
4) Find the "G-TouchWiz" app and open it.
5a) Under the "POPUPS" section there is:
"Disable battery cover popup on/off"
"Disable USB Cover popup on/off"
5b) Turn them off. (cryptic, huh?)
5c) Reboot.
Finished. You will notice that they did not annoy you... this time.
(Please hit thanks if I have helped!)
dirtydodge said:
Downloaded X Tether from Xposed Framework , then go to wanam and click on system and enable "skip provisioning check" and rebooted. It alows me to turn on tethering and mobile Hotspot.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My G900A with the Xposed Framework, X Tether, Wanam Kit and Wanam Xposed installed, does not have "skip provisioning check" listed on either of the Wanam modules. Thoughts?
Open wanamxposed then go to System. Then check "Disable Tethering Provisioning"
If you don't have this, tell me what version of wanam you have.
Can somebody post a link or explain the benefits of installing Xposed and or wanam. I'm not a complete rookie but besides the few tweaks already on this thread, what else works on our 900As
Sent from my Nexus 7 using XDA Premium 4 mobile app
What is Xposed Framework?
As far as Xposed/Wanam, these apps allow you to modify visual and technical elements of your phone's rom. These changes are temporary and can be reversed.
The Xposed Framework is intended to bring functions of a custom rom INTO a stock rom. One could say it is an alternative for phones in which the bootloader remains locked.
For more info/tech details of Xposed:
General
http://forum.xda-developers.com/xposed
Info, Versions and Changelog
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
FAQ
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
There are tons of modules, however only a few of them work with the S5 currently. You are free to explore, but use caution and common sense. If it's for an HTC, then don't use it.
This thread was meant to discuss which ones do work.
Well I downgraded my firmware to the G900AUCU1ANCE and now I can only get usb tethering. Amy ideas on how to enable regular tethering (not having to use a usb cable)
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I'm using Greenify and GravityBox. Both seem to work with out errors. I tried Exchange Bypass, didn't work. and I tried Advanced Power Menu, that didn't work either.
How to Force Native WiFi Tether Galaxy S5 (Root)
Decided to edit this post to make more sense.
Follow the steps below to enable the built in wifi tether feature:
1a) If you haven't already, download the Xposed Framework app.
Xposed Framework Installer
1b) Open the app, tap "Framework," then tap "OK." Now tap "Install/Update."
2) Reboot
3a) Open Xposed, then tap "Downloads," then search for Wanam Xposed and X Tether. Alternatively you can go to:
Wanam Xposed Module (Repo)
X Tether Module (Repo)
3b) Once downloaded and installed, open the Xposed app. Tap "Modules." Now check the box next to each module.
4) Reboot. Again.
5) Open Wanam Xposed and tap "System." Then check "Disable Tether Provisioning."
6) Again, reboot.
Your native wifi should now function.
Please hit Thanks if I have helped!
allcaps33 said:
There has been some complaint about these warnings, so here goes:
1a) Download Xposed
http://repo.xposed.info/module/de.robv.android.xposed.installer
1b) Install it.
1c) Open it up, tap on "Framework," then tap"OK" on the pop up. Then tap "Install/Update"
2) Reboot.
3a) Re Open Xposed, tap "Download, " and search for "G-Touchwiz."
Or go here
http://repo.xposed.info/module/com.gertlily.xposed.touchwiz
3b) Install it. Swipe from left to right and it will show the download options.
3c) Go to the main menu of Xposed, check the box for "G-TouchWiz" then reboot.
4) Find the "G-TouchWiz" app and open it.
5a) Under the "POPUPS" section there is:
"Disable battery cover popup on/off"
"Disable USB Cover popup on/off"
5b) Turn them off. (cryptic, huh?)
5c) Reboot.
Finished. You will notice that they did not annoy you... this time.
(Please hit thanks if I have helped!)
Click to expand...
Click to collapse
Worked like a champ, thanks given
allcaps33 said:
As mentioned:
Download Wanam Xposed.
Download Xposed Tether.
Activate these two modules, reboot.
Open Wanam, go to "System," Then check "Disable Tether Provisioning. "
Reboot.
If this does not work:
Carefully deactivate these settings AND modules.
Uninstall the modules, and Wanam, and Xposed.
Unroot.
Reboot.
Update to 2AND3 firmware (Just check for updates.)
Re Root.
Install Xposed, Wanam, and the module listed above.
Perform steps listed above.
Click to expand...
Click to collapse
Well I Uninstalled everything, rebooted, unrooted, reboot into recovery mode wipe cache, reboot tried to install OTA and after it downloaded during the reboot it said update fail. I tried 3 different times with no success. Also before doing all that I reebabled all apps that I previously disabled.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
dirtydodge said:
Well I Uninstalled everything, rebooted, unrooted, reboot into recovery mode wipe cache, reboot tried to install OTA and after it downloaded during the reboot it said update fail. I tried 3 different times with no success. Also before doing all that I reebabled all apps that I previously disabled.
Click to expand...
Click to collapse
Did you follow the instructions for downgrade/unbrick fix at
http://forum.xda-developers.com/showthread.php?t=2785185
Please note that the original instructions have been changed. Read through the entire thread and follow the instructions to fix this. Users have reported that they are able to update once again to the G900AUCU2AND3 firmware once complete. For more questions regarding this, please post in that thread.
I think it's easy to make this mistake but make sure you download WanamXposed and not Wanam Kit, which I think is close to the top which is why I selected it. It seemed to work for me but I started having problems and I realized it was made for aosp ROMs. Just putting it out there.
Just a heads up guys - the Xposed tethering mod is incompatible with the 'download booster' mod from here:
http://forum.xda-developers.com/showthread.php?t=2785410
It's one or the other for now.
Later.
@profcx
Thank you for the heads up!
I will update the OP.
Noticed a performance decrease after doing this. However i can now share my wifi. Not sure what is better.
Performance Issues with Xposed (Solved)
Download and open up your favorite build.prop editor. Or just use a text capable app like ES File Explorer or Rom Toolbox.
1) Navigate to /system/build.prop
2) Go to the line"ro.storagesecure.support"
3) Change the value to "false"
4) Reboot.
Everything should be fine after that.
allcaps33 said:
Download and open up your favorite build.prop editor. Or just use a text capable app like ES File Explorer or Rom Toolbox.
1) Navigate to /system/build.prop
2) Go to the line"ro.storagesecure.support"
3) Change the value to "false"
4) Reboot.
Everything should be fine after that.
Click to expand...
Click to collapse
Can you please clarify exactly what this "ro.storagesecure.support=false" is supposed to fix? Are you saying this will fix the performance issue mentioned in post 18 or will this fix native tether in some cases?
Sent from my SPH-L720T using XDA Premium 4 mobile app
Samsung Xposed Safe Mode script v1.0
What does it do?
This is an init.d script which emulates the xposed safe mode where you can press any button during boot, get a vibrate (to know it detected you), and it will disable all your xposed modules. To be used in case of bootloops because of incompatible modules.
This only disables all modules so that you can boot. It does NOT actually uninstall or disable xposed itself.
Why would I need this?
I talked with the developer of xposed for Samsung, wanam, and apparently, xposed safe mode was disabled for Samsung devices due to a Knox issue (if you disabled xposed, Knox will hate you and refuse to boot the phone). This is good, but if you have a bootloop, AND you're on a bootloader locked device, you have NO CHOICE but to wipe your data. Ouch!! That's a heavy penalty for accidentally installing one malfunctioning module!
Or maybe your phone still is bootloader unlocked, but you're running Samsung xposed and safemode is still disabled for you. Then you'd rather have xposed safemode back just for the ease of not having to go through recovery to fix things.
How does it work?
1. Press any of three buttons during boot (volume keys, or home button). You have 10 seconds from bootup to choose to do this.
2. System will give you 2 short vibrates to tell you it detected it.
3. Press any button 4 more times, each time will give you another short vibration.
4. One long vibration will signal to you that xposed has been disabled.
5. The script will automatically reboot your device in 6 seconds. This is because we can't disable xposed, so xposed will STILL load modules on this bootup, which means you'll still see the bootloop momentarily until you reboot.
Great! How do I install it?
This is an init.d script, so you need init.d support in your phone. Obviously, if you have a bootlocked device, you probably don't have init.d support. This is not a guide on how to get init.d support, but I'll offer you a few tips you can use to search yourself.
- install-recovery.sh, since it's called by init.rc during boot, can be hijacked in order to create an init.d system.
- If install-recovery didn't work, SuperSU also includes an su.d directory which is executed at a similar time. Just throw a script in there, or throw a script in there which enables use of the init.d folder (run-parts /system/etc/init.d).
Anyways, here's how you install it:
- Place the script you downloaded into
Code:
/system/etc/init.d
OR
Code:
/system/su.d
Give the script proper permissions for the folder it's in
- For su.d folder, it is root:root 0700 (rwx------)
- For init.d folder, it could be a variety of permissions. My init.d folder runs as a result of su.d, so I gave it same permissions as su.d. If yours doesn't, then you might want to try root:root 0755 (rwxr-xr-x)
- The important point here is to make sure it's at least root user and group, readable and executable, rwxr-xr-x
Will it work on my device?
It should work on any device really, if you follow the simple instructions. But I've only tested it on the ATT S4 (Lollipop 5.0.1), so I can't guarantee it will work on your device. Test it out and see if it works for you! It probably will!
You saved me!
I'm glad to hear that! I love to hear and see a thanks, so make sure to click the thanks button and maybe write a post too!
Bugs and problems
You know how to report bugs and issues. State all relevant information related to the problem; device, problem in clear detail, with reproducible steps, and anything else you might need.
Related custom xposed builds
Here are a list of Samsung custom xposed builds I know this "safe mode problem" to be present in. (Don't forget, this problem is likely to be in any and all Samsung xposed custom builds due to the nature of the Knox problem).
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
[UNOFFICIAL][5.0][v87.1][03 Dec] Xposed for Samsung Lollipop 5.0.x
[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow
Disclaimer: As usual, while I've made every attempt to make it perfect, there are no guarantee it will work for you. By using this, you agree not to hold me accountable in case something bad happens to you (or it didn't save your device)! Do your own testing to make sure it works before you actually need to use it in an emergency!
FAQ
It didn't vibrate
You probably have a different device which places the vibrator in a different location. I don't have your device, so maybe you'll need to help me debug and find where the vibrator is located at.
It didn't work!
What happened? Give me some detailed information about exactly what you did, what happened, and the device you're on!
Some possible problems to investigate are:
Does the script have correct user: owner and permissions?
Is your init.d or su.d system even working? Make sure it is first
Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.
wanam said:
Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.
Click to expand...
Click to collapse
Thank you!
It certainly will help a lot for disabling incompatible modules. Yes, although it doesn't technically disable xposed itself. It's really great that future versions aren't that way!
I actually thought of creating another script which utilizes back and menu key buttons to actually uninstall xposed from backups (an actual disable xposed script of sorts), but I thought it was too much.
Hi,
I have this idea and I like to know your opinion:
- At time the MagiskHide is a good method for use some Apps (wallet?) when you run in Core mode. This is a great function and really works (I hope for a long time). However, when you aren't running in Core mode, for example when Xposed is enabled, if you run one of such Apps it detects the presence of the su/root. So my idea is adding to Magisk the option to "hibernate" the Apps inside the list of MagiskHide when is not running in Core mode. And when the Core mode is on, then automatically "re-enable" the App.
The objective is quite simple: Block the execution of any "sensible" Apps when the detection can be done.
What you think?
If MagiskHide doesn't work on your device unless you activate Core Only Mode there's something wrong. It might be that that's how your device works, or there might be something else...
MagiskHide works perfectly fine, when when not in Core Only Mode.
Xposed though, that's a whole different matter. There's currently no way to hide Xposed, so it is very likely that what happens when you enable Core Only Mode is that the Xposed module gets deactivated and whatever app was triggering no longer do so (since you've deactivated Xposed).
Didgeridoohan said:
If MagiskHide doesn't work on your device unless you activate Core Only Mode there's something wrong. It might be that that's how your device works, or there might be something else...
Xposed though, that's a whole different matter. There's currently no way to hide Xposed, so it is very likely that what happens when you enable Core Only Mode is that the Xposed module gets deactivated and whatever app was triggering no longer do so (since you've deactivated Xposed).
Click to expand...
Click to collapse
Hi @Didgeridoohan,
Thank you for your comment!
However, I feel you misunderstood my suggestion. Let me explain more:
In my phone (at time, with Stock ROM and a Custom kernel), I can run Magisk in both modes: CORE and FULL. Both work like a charm! However, the SafetyNET check only pass in CORE mode (with MagiskHide enabled), not in FULL mode. Obviously, this is because in the FULL mode I run Xposed and the MagiskHide doesn't work.
So, when I like to run some wallet or banking App, I need to boot in CORE mode. This is mandatory!
And when I don't like to use such Apps, then I can boot in FULL mode.
Where is the problem? When running in FULL mode all Apps that can detect su/root are "active". You can use some Xposed modules (like BootManager) for not launching them at boot. However, if the App isn't "hibernated" it can be executed at any moment. And when it's executed, at this moment it detects the root... and fails. Moreover, it not only fails, but it can send a message to the App's provider... and insert you in a blacklist. So a full blocking of the App when running in Magisk FULL mode is necessary.
My idea is a simple "auto-hibernating" of the Apps in the MagiskHide list when running in non CORE mode.
You understand now what, when and why?
manos78 said:
So, when I like to run some wallet or banking App, I need to boot in CORE mode. This is mandatory!
Click to expand...
Click to collapse
Well... Core mode isn't necessary. You should be able to simply deactivate the Xposed module.
But yeah, I get your idea. Can't say much about it though...
Didgeridoohan said:
Well... Core mode isn't necessary. You should be able to simply deactivate the Xposed module.
Click to expand...
Click to collapse
If you want to be completly sure that SafetyNET is OK, then you really need to boot in CORE mode.
So, my idea at time is:
- Include the function "reboot in Core mode" inside the Magisk Tool. The concept is simple: one flag (for example one file like /magisk/.boot_one_shot_in_core) that forces Magisk to boot in Core mode... but only one time (the file is automatically removed after the boot).
- Create a Magisk Module that "hides Apps in the MagiskHide list". This module is as well very simple: it replaces the apks of the Apps in the list by a dummy file. So, when Magisk boots in FULL (normal) mode then the module "hides" the Apps, and you can't use them. However, when Magisk boots in CORE mode, the module is overpassed and the Apps be there (not hidden).
So, the idea is quite simple: the regular boot is booting with Magisk enabled (FULL mode); and when you like to boot in CORE mode it's only one-time... so in the next reboot. And when reboot again you return to the FULL mode.
I found this is the best and simple solution to execute/hide sensible Apps that really need to have SafetyNET enabled.
What you think?
Hi,
Regarding this idea: Create a Magisk Module that "hides Apps in the MagiskHide list. Anyone interested on work on it?
The concept is quite simple: If the module is active, it hides (aka mount fake .apk) all Apps in the MagiskHide list (or in a internal list).
You like this idea?
Hi,
i have an Moto Z with latest stock rom and magisk 14.2 installed via twrp.
The problem: When i tick an app in hide settings, the entry wasnt saved. When i leave magisk and open the hide setting again, the app wasnt enabled for hide, i can tick it again and gain but it wasnt save.
Can someone help, whats the problem ?
IIRC, the Moto Z is one of the devices with a broken f2fs implementation. The Magisk image can't be mounted, so there's no Hide list to save anything to...
IIRC again, you should be able to get it working if you enable Core Only Mode in the Manager settings, but any apps added to the Hide list will be reset on a reboot.
You could also take a look in your device's forum if there are any custom kernels available with a f2fs fix.
Thanks for the explanation. The Moto Z has unfortunately no good dev support. So i found out that after reboot i must untick the hide option in magisk setting and tick again, then i can tick my app for hide and it was remembered, until next boot.
Didgeridoohan said:
IIRC, the Moto Z is one of the devices with a broken f2fs implementation. The Magisk image can't be mounted, so there's no Hide list to save anything to...
IIRC again, you should be able to get it working if you enable Core Only Mode in the Manager settings, but any apps added to the Hide list will be reset on a reboot.
You could also take a look in your device's forum if there are any custom kernels available with a f2fs fix.
Click to expand...
Click to collapse
tasar said:
Hi,
i have an Moto Z with latest stock rom and magisk 14.2 installed via twrp.
The problem: When i tick an app in hide settings, the entry wasnt saved. When i leave magisk and open the hide setting again, the app wasnt enabled for hide, i can tick it again and gain but it wasnt save.
Can someone help, whats the problem ?
Click to expand...
Click to collapse
tasar said:
Thanks for the explanation. The Moto Z has unfortunately no good dev support. So i found out that after reboot i must untick the hide option in magisk setting and tick again, then i can tick my app for hide and it was remembered, until next boot.
Click to expand...
Click to collapse
I am using version 14.0 and have experienced the same problem.
Check the logs stored in the /cache folder to determine the cause.
solution:
Create a folder called /magisk/.core and create an empty file called hidelist in it.
shell command:
mkdir /magisk/.core
touch /magisk/.core/hidelist
I have the same idea but the file system is read only. How to make it rw?
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
dknight178 said:
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
Click to expand...
Click to collapse
Three years later... (I'm still using my Note 3 from 2013, btw)... and did you ever find a solution to this problem? I'm using Magisk 20.3 now, and it still does not keep the "Magisk Hide" option enabled after closing the app.
So enable it, I open the app and go to settings and enable it from there. I must then back out and close the app for the Magisk Hide option to become available under the menu. If I back out of the app again, whatever I had checked as hidden under the "Magisk Hide" menu becomes unchecked again. If I reboot the phone, I have to go back into settings to enable Magisk Hide again.
Any solution for this other than use another device?
Hi! Is there a way to enable/disable a Magisk Module with a script?
I'm using a Xiaomi Mi A1 and I would like to use Measure App. It works only the first time (or so) I disable/enable the module to change device fingerprint. Is it possible to run a script that disables and re-enables the module at boot? Thanks.
Disabling and then enabling a module takes a reboot between every action. It can't be done in one boot...
But, I suspect that this might not actually be the solution you're looking for. Provide more details, please. What module are you talking about? What functionality is it that you're after? What is it that doesn't work? Logs. Etc...
Didgeridoohan said:
Disabling and then enabling a module takes a reboot between every action. It can't be done in one boot...
But, I suspect that this might not actually be the solution you're looking for. Provide more details, please. What module are you talking about? What functionality is it that you're after? What is it that doesn't work? Logs. Etc...
Click to expand...
Click to collapse
Thanks for your quick reply.
I'm using a module that changes device fingerprint to Pixel2 to be able to use Measure app. Measure works properly only one or two times after enabling the module. Then it stops finding available surfaces until I disable, re-enable module and reboot. The same problem occurs if I use your MagiskHide Props Config (great work btw). After disabling-enabling-rebooting Measure works properly again. If I simply reboot without touching the module Measure app starts but it can't find any suitable surface.
Here's a logcat, hope it helps.
Do I understand you correctly? You're talking about disabling/enabling the module in the Magisk Manager, right? And disabling and then enabling right after, with no reboot in-between? If so, that makes no sense, because the only thing disabling the module does is to create a file in the module folder named "disable". On the next boot, Magisk will detect this file and won't load the module. Enabling the module simply deletes the file again, and on the next boot the module will load (since there's no "disable" file)..
I really do believe there's something else going on...
Didgeridoohan said:
Do I understand you correctly? You're talking about disabling/enabling the module in the Magisk Manager, right? And disabling and then enabling right after, with no reboot in-between? If so, that makes no sense, because the only thing disabling the module does is to create a file in the module folder named "disable". On the next boot, Magisk will detect this file and won't load the module. Enabling the module simply deletes the file again, and on the next boot the module will load (since there's no "disable" file)..
I really do believe there's something else going on...
Click to expand...
Click to collapse
I know it makes no sense but it works that way for me and for other people with the same phone/module. I was trying to find a way to automate this process at every boot so that at least the first time (after every boot) I'll use Measure it will work well. Otherwise log keep saying "Received image measurement before corresponding IMU measurement" then app crashes.
I'm 100% sure that it's got nothing to do with creating and deleting a file named "disable" in the module directory... There's something else going on, it's just that noone's figured out what.
Didgeridoohan said:
I'm 100% sure that it's got nothing to do with creating and deleting a file named "disable" in the module directory... There's something else going on, it's just that noone's figured out what.
Click to expand...
Click to collapse
I really don't know but I can reproduce this bug every time. How can I create and delete this file? Is there a path where I can put this file or magisk.img can be mounted? Sorry if it sounds ridiculous, I am not a developer...
If you really want to try you can just place a boot script in post-fs-data.d that creates and deletes the file in the module directory. Something like:
Code:
#!/system/bin/sh
touch <path_to_module>/disable
rm -f <path_to_module>/disable
The path to the module depends on what version of Magisk you're using (although there's backwards compatibility symlinks in place). In the current stable release the modules are in /sbin/.magisk/img, but the current code (in the Canary builds and in future releases) have moved this to /data/adb/modules.
Perfectly working, thanks. I used macrodroid to run the scripts you gave me after every boot.