Put fastboot and adb in any folder you want. Then in control panel, advanced system settings, environmental variables, edit the path to include the folder that fastboot/adb are in. Then it doesn't matter where the twrp.img is relative to fastboot/adb. Open a power shell in the folder twrp is in and do what you want with it. If you ran snoop's script adb will be in a folder adb.
I am using Magisk v20.1 on my OnePlus 7 Pro running 10.3.0.
It turns out that v20.2 is causing me problems which I haven't figured out yet, and so I want to stay at v20.1 for the moment.
I need to reflash my ROM, and normally, I would do so via OTA followed by an installation of the "TWRP A/B Retention Script" via Magisk, which I subsequently would follow with INSTALL->INSTALL->Install to inactive slot(after OTA).
However, the "Install to inactive slot(after OTA)" procedure only appears under "UPDATE" now, due to the fact that v20.2 is available, and there is no "INSTALL". Therefore, invoking "Install to inactive slot(after OTA)" seems to only be possible if I also upgrade to Magisk-v20.2, which I don't want to do.
Is there any way for me to perform the "TWRP A/B Retention Script" and "Install to inactive slot(after OTA)" procedures while still keeping my Magisk version at v20.1?
Thank you very much.
I'll just leave this here...
All credit to @pkgnex for the time and effort spent on this thorough Lollipop(+) refresh of the old "Dev Team" init.d scripts. Thank his post below.
Edit: Rehosted - https://basketbuild.com/devs/osm0sis/scripts/
Edit 2: BasketBuild seems dead again, so attaching the old installer (with outdated scripts) below for posterity, and also pkgnex's updated versions in a simple (non-flashable) zip.
Thanks for sharing your works. I'm not a dev or advanced user, so I don't know what to do with a lot of your projects, but I'm interested in learning. It's just been challenging so far, finding info that meets me where I'm at, so it's been a slow process.
Anyways, I wanted to contribute something here and give back. I tried my hand at getting these updated scripts into a flashable zip form. Seems to be ok. Let me know if I messed up. I basically just edited the old zip installer. The zip size is as big as it is cause I read that flashable zips should be archived on "store" compression. But I don't think that's necessarily true, and TWRP will flash them if they're stored on "normal" compression too. But I figured it was better to error on the side of caution.
I appreciate you using the idea as a learning process, but there is no such thing as /system/etc/init.d anymore, so neither zip will work. Normal compression should work totally fine, by the way.
That said, I also don't want them up in a zip (that works, the old one is there for posterity), or I would have done it myself, so please take it down; those scripts haven't been updated since Lollipop or Oreo, so I wouldn't necessarily trust them all on a modern device.
Those who do want to tinker with them should be able to place them themselves in the appropriate directory for their ROM/root. That way they also know what to do if/when things go wrong.
Hopefully you understand, and don't find this discouraging. Scripting is super handy, and can be pretty fun, so keep it up! Your best bet might be to go to my Complete Shell Script update-binary replacement thread and start by learning to piece together your own installer with the functions I've provided.
|automation, batch, flashable zip, script, tool|
|Thread Tools||Search this Thread|