Not sure why you're quoting my post to say this. I was trying to put him on the right track to flash everything manually. I never suggested any script except for Google's own flash-all. Unfortunately, I haven't had the chance to go this process myself on taimen, which is why I suggested in an earlier post that someone else might chime in with a full list of commands.
Yes, again sorry, I wasn't going after you directly, it just made me realize that a lot of people quote that script as if it were big and complicated, and it's just 3 individual flash commands in a row with some reboots, pauses, and comments. It would be nice if folks would just post those inline with their other instructions so the user could watch each one and verify that it didn't fail before rebooting bootloader and moving on. Not likely to matter when things are done right and there's no corruption or glitches, but it helps to be a little cautious and avoid making things worse! Anyway, thanks for helping, carry on!
---------- Post added at 07:56 AM ---------- Previous post was at 07:32 AM ----------
Yes, I have my bootloader entirely unlocked. I'm not sure what the underlying issue was, but I used my functioning twrp to do a factory reset and then just went through the same steps to root etc. It's working now, so that's good!! Also, it seems to be a common issue when trying to run the script on Mac, I remember seeing on Google that this happened to many others. Thank you for the reply though!
From what I recall reading, that is mainly because people do not set their adb up to be executable from anywhere. The recommended method to get the latest install probably does not update your PATH to add a path to adb and fastboot. Since the script just calls "fastboot" but does not have the full path (/usr/local/bin/fastboot usually), it will fail unless you make the hacky move of copying your files to the adb folder and running it from there. You'll see people also have to modify the commands to add "./" in front to tell it to run from the current directory. All of this is solved by a proper installation where /usr/local/bin is added to your PATH. For most folks, they are using the 'bash' shell, and can fix this in FUTURE sessions by adding this to ~/.bashrc:
(That will also add your own personal bin folder to your path - a good place to put your custom scripts if you ever have any, and harmless if you don't.)
You can also run that directly on the command line to fix the current session.
If you put your adb and fastboot somewhere "strange", you can find them again the brute-force way by scanning the drive:
find / -type f -name "fastboot*" -ls
/usr/local/bin/fastboot -> /usr/local/Caskroom/android-platform-tools/27.0.1/platform-tools/fastboot