ipsw VS idevicerestore

Compare ipsw vs idevicerestore and see what are their differences.

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
ipsw idevicerestore
2 21
1,478 1,206
- 1.1%
9.8 7.6
3 days ago 29 days ago
Go C
MIT License GNU Lesser General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

ipsw

Posts with mentions or reviews of ipsw. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-09.
  • A 17-line C program freezes the Mac kernel (2018)
    7 projects | news.ycombinator.com | 9 Dec 2022
    In theory I have all of those, but currently I have none, so it's manual work. Your best friend in diagnosing a kernel crash is a KDK. If you have one that matches your build, it will have symbols in it. With a little bit of math you can take the backtrace in the crash log and slide it appropriately to match the binary. Personally I use LLDB for this. Here's an example of what this looks like on an x86-64 kernel (Apple silicon has its own math but it's largely the same): https://github.com/saagarjha/unxip/issues/14#issuecomment-10.... The kernel is typically compiled with optimization, so there's a lot of inlining and code folding, but with function names, source files, and instruction offsets it's pretty trivial to match it to the code Apple publishes.

    In this case I do not have a KDK for that build. In fact Apple has been unable to produce one for a couple of months, a inadequacy which I have repeatedly emphasized to them because of how critical they are for stuff like this. Supposedly they are working on it. Whatever; in lieu of that I got to figure out how good the tooling for analyzing kernels is these days, which was my real goal anyways.

    For this crash log I downloaded the IPSW file for your build, 22A400. All of them get linked on The iPhone Wiki, e.g. https://www.theiphonewiki.com/wiki/Firmware/Mac/13.x. Once you unpack the IPSW (it's a zip file) there are compressed kernelcache files inside. Apple changed the format of these this year so most of the tooling breaks on it, but https://github.com/blacktop/ipsw was able to decompress them. Then I loaded it in to Binary Ninja, which apparently doesn't support them either but compiling this person's plugin (+166 submodules, and a LLVM & Boost build) gets it to work: https://github.com/skr0x1c0/binja_kc.

    From there you can load up the faulting address from the crash log and see what the function looks like. In this case, a bunch of junk has been inlined into it but there's a really obvious and fairly unique string reference for "invalid knote %p detach, filter: %d". From there, you can compare it against the actual source code to see which one matches the "shape" of the function you're looking at. I happened to also pull up an older kernel which did have a KDK available and then compared its assembly to the new one to match it up to ptsd_kqops_detach. The disassembly of the crashing code is obviously doing a linked list walk so you can figure out exactly which line it is from that.

    If I wasn't lazy I might also fire up a debugger to see why the function had walked off the end of the list but without KDKs things get pretty bad, not that they're very good to begin with. I don't have a m1n1 setup (I should probably do this at some point) and the things I do have, like remote debugging or the VM GDB stub, are not really worth suffering through for a Hacker News comment.

  • [Question] Can a downloaded 14.8.1 OTA be manually updated via iTunes? Device is iPhone SE (2016)
    1 project | /r/jailbreak | 6 Dec 2021
    Github: https://github.com/blacktop/ipsw Release: https://github.com/blacktop/ipsw/releases Instructions/Website: https://blacktop.github.io/ipsw/

idevicerestore

Posts with mentions or reviews of idevicerestore. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-10.

What are some alternatives?

When comparing ipsw and idevicerestore you can also consider the following projects:

micromdm - Mobile Device Management server

docs - Hardware and software docs / wiki

unxip - A fast Xcode unarchiver

upb - a small protobuf implementation in C

quill - Simple mac binary signing from any platform

ideviceinstaller - Manage apps of iOS devices

macOS-Simple-KVM - Tools to set up a quick macOS VM in QEMU, accelerated by KVM.

mbp-2016-linux - State of Linux on the MacBook Pro 2016 & 2017

ifuse - A fuse filesystem to access the contents of iOS devices

tpm2-tools - The source repository for the Trusted Platform Module (TPM2.0) tools

Winterbloom_Castor_and_Pollux - A Juno-inspired dual oscillator

netmuxd - An alternative to usbmuxd just for networking