Put your script to:I have historically built ROMs and before that I was a flash junkie, so re-setting up a device was a VERY common occurrence.
In a way, what I have done is even easier (ie delete two settings instead of noting and entering 10 specific setting values), the problem is that I would like to simply drop in my boot-scripts onto the device, and have it auto configure the device; no manual intervention/config. For eg, I use to have a script when I was rebuilding then clean re-flashing one HIGHLY customisable rom, that returned all my selected customisation adjustments (100 or so manual settings) so the phone returned back to its look-and feel just by running a shell script, instead of the palava of delving deep and returning and searching. I could also use it to transfer the selected settings between devices running the same ROM or to an extent, between two closely related ROMs, as they shared commits on settings/features.
The other thing that concerns me, if it is not accepting my little attempt to set it back on an existing APN, after creating a new one from scratch, for the same reason, it may not accept the setting for proxy, and I would be in the same situation. I haven't checked the logcat for clues, and I will leave this as a problem for "Future @DiamondJohn" to handle... My phone is up and running, I have had recent hell with a bootloop and no PC to fix, and a cracked screen, am not looking to upgrade too soon to A13, so am prepared to leave it be or fix it when/if it becomes an issue again. And it wasn't a total deal-breaker anyway, just annoying.
What I have reaslised, I have my old device, its A8-Oreo, but I think it had the same issue. It will be a hassle to swap the SIM card out-in-out-in between the devices, but doable, or maybe get a $2 starter SIM with minimal or no credit; rather than the hassle of swapping sims between phones. Actually, I have an old pay-as-you-go SIM somehwere? with no credit left that I may be able to use for testing this change; the setting only not the results. I also have a spare device (cheap ebay purchase, same as daily, Google 4A 4G) running A13 as a tester, that I could check with. I have options, but now that it works as expected, it has consumed enough time. I do like the size of this phone, I would of gone smaller if available with other features. Its a good device and stiull gets a lo9t of love on youtube, but the screens are prone to break, as my repair guy said first thing when I showed him; and its the SECOND screen I have broke.
PS: I checked my host building script that was missing the comment character on listing the source files, and it DID have the code that should of included the comment at the start of those lines.so thats at a higher priority to fix now, or in this case understand what the heck is going wrong; ie what am I doing wrong...
/data/adb/modules/hosts
and name it service.sh or post-fs-data.sh and reboot
TJW recommends using service.sh but some modules need certain actions to execute earlier hence they use and/or post-fs-data.sh (find more about how/when Magisk executes these scripts in Developer Guide on the Magisk GitHub)
Go to the /data/adb/modules folders and find their scripts there
---
The way as above you will (mis)use again the folder from Systemless hosts module
You can also name your script whatever, like myScript.sh and put it to one or the other folder (again, Magisk execute the scripts it finds there at a different stage of booting):
/data/adb/service.d
or
/data/adb/post-fs-data.d
Or you can make your own module - minimalistic zip for your module is attached
Unzip, put your script (with the name as described above), re-zip (structure of the zip file must remain the same - inspect also zip files from the other modules), eg here:
'Flash' - ie, install from Magisk app (but don't become addicted again)
Edit the module.prop (author, description)
See where it goes when you install and where it moves upon reboot.
See what happens if you change id in the module prop, etc
Last edited:
