This command is very useful in Terminal when trying to run an executable.
For some weird reason, macOS sometimes thinks that an executable is a text document filled with weird code, treating it like a document.
When this command is ran, it tells the system to check if the file is an executable, and then convert it if so.
Want to make any executable runnable by just typing it's name in Terminal?
Example 'ideviceinfo', no cd required, no './'
Run this command to copy the executable to the /usr/local/bin directory, so that the Mac will recognize it as a command.
Note that this will not move the executable, just copy it. Your original version will remain in it's directory.
Have you ever run into the issue where your Mac says "bind(): Address already in use Error creating socket for listen port 4444: Address already in use"?
I have run into this annoying issue many times and it simply means that iproxy needs to be quit before it can be used again.
When running this command, it kills iproxy so that it isn't running anymore.
Now, you can run iproxy again just like normal!
If you have the idevicediagnostics executable on your computer (you will most likely have it if you work with iCloud bypasses and hacks)
and you have a device with a cracked screen or a broken power button, then this command is for you!
This command is super useful when can't shut down your device for these reasons.
Go and open up a new Terminal, cd into the directory that the idevicediagnostics executable is is, and paste this command in.
Your device should shut down immediately!
This one can be very useful at times when a device is bricked in Recovery Mode.
Half of the time, if your device is stuck in Recovery Mode, it is because the software on the device is corrupted, or there is something wrong with the device.
But fairly often, all the device needs is a little reminder that it's can still boot up fine without an entire restore.
The only requirement is that you have the irecovery executable on your Mac, which most people working with hacks and bypasses should have.
Using this helpful little command, you can often fix your Recovery Mode issue without a full restore, which in most cases would wipe your data.
Remember to cd into the directory with irecovery before pasting it into the Terminal unless you have irecovery in /usr/local/bin.
Want to get info about your device but in DFU Mode not Normal Mode?.
Using the '-q' argument in iRecovery, you can query info about the connected device without booting it up into Normal mode.
You can get the Serial Number (Recovery Mode), the ECID, the device identifier (ex. iPhone9,1), and the device model name (ex. iPhone 7).
The only requirement is that you have the irecovery executable on your Mac, which most people working with hacks and bypasses should have.
Using this helpful little command, you can get device info in Recovery Mode or DFU Mode. Even if your device is bricked or in a boot loop!
Remember to cd into the directory with iRecovery before pasting it into the Terminal unless you have irecovery in /usr/local/bin.
This command may be one of the most helpful commands to me.
Have you ever plugged your Apple device into your Mac and it just keeps charging, not-charging, charging, not-charging?
This can get SO annoying after a while but with this simple fix, you should be all good in no time.
This command is very helpful if you are seeing the error "[Application name] is damaged. You should move it to the Trash".
When you run the command in Terminal, along with dragging your executable or .app file into the window, you can fix this issue quickly and easily.
The command here is quite helpful if you see the error "permission denied" when running a shell script.
When running this command with your script, it should fix the "permission denied" error.
Website made by Always Apple FTD. Please do not copy any part of this website.