@dupdup: my mistake - somehow I had in my mind that you we’re doing this on a Linux system - I’m not sure whether there is such a thing in a Mac. If anthony’s method doesn’t work, here’s a couple of ways that should work around bash (=terminal) not finding the adb you installed:
- Open a terminal in the location where you installed/unpacked the android-tools (i.e. where you double clicked), or navigate there using
cd, as incd /home/user/path/to/tools/. You should then be able to run adb and fastboot from bash without messing with the path if you put./immediately in front of it, like:./adb reboot bootloader. - In a similar vein as above, you can tell bash where to look each time you run a command. The advantage is that this can be done from any location, but you have to type the full path each time, e.g.
/home/user/path/to/tools/adb reboot bootloader - Bash has a list of places (=folders) to look for commands, you can add custom entries that only affect the current terminal session like so:
PATH=$PATH:/home/user/path/to/tools/. After this just runningadb reboot bootloadershould work within that session. - As an addendum to the above, if you want this to set up to run at every terminal you open, then there’s usually a hidden file in your home folder where bash keeps its settings - I’m not sure which one mac uses: popular options that I know of are
.bashrc,.profile, and.bash_profile. Verify that whatever you put in actually works first, as changing it in the wrong way can potentially have messy side effects.
I solved it in the end by NOT queueing the modem zip and the lineage build and then flash, but by flashing them one by one. So, in my case step 3 and 4 of ‘When coming form any other OS’ (