Closed mc-17 closed 2 weeks ago
Weirdly enough, I don't see this with the following beta7 IPSW
[IPSW Info]
===========
Version = 18.0
BuildVersion = 22A5346a
OS Type = Development
FileSystem = 090-28877-084.dmg.aea
SystemOS = 090-28396-099.dmg.aea
AppOS = 090-28378-122.dmg
RestoreRamDisk = [090-27766-125.dmg 090-27884-122.dmg]
Devices
-------
iPhone 13 Pro Max
> iPhone14,3_D64AP_22A5346a
- TimeStamp: 14 Aug 2024 21:44:37 PDT
- KernelCache: kernelcache.release.iphone14
- CPU: A15 Bionic (ARMv8.5-A), ID: t8110
- BootLoaders
* iBEC.d64.RELEASE.im4p
* iBoot.d64.RELEASE.im4p
* iBSS.d64.RELEASE.im4p
* LLB.d64.RELEASE.im4p
* sep-firmware.d64.RELEASE.im4p
The problem IPSW is:
https://updates.cdn-apple.com/2024SummerSeed/fullrestores/062-64346/BB6E07F7-70FE-4E42-BE5C-B69FE7CF4243/iPhone16,1_18.0_22A5346a_Restore.ipsw
This might be a macOS 15 thing - I find that hdiutil detach <mount> -force
will make it work, perhaps flipping the force flag on the unmount might resolve this.
Ya I've seen dmgs get stuck occasionally or if you interrupt it and it'll put the already extracted DMG in a weird state.
I thinking trying to force might work. I thought I already was? Or changed it back to not force for some reason that I cannot remember.
However, since I am constantly testing the same, IPSWs over and over again, sometimes with crashes. I get these stuck DMGs is pretty often.
I always delete them if they're on the file system still. And then manually unmount to fix.
Which definitely is not a great solution for end users if they're seeing it happened too
added force
to the call in Extract, I probably should always force
but again, I feel like I was, and then decided to not make that the default? 🤷
https://github.com/blacktop/ipsw/commit/7480ed5381413f457e52fbbcbc3ba51edfed4f42
pushed an new release, let me know if it made a difference for you
pushed an new release, let me know if it made a difference for you
This does appear to work, thanks! However it's also occurring in other places (such as ipsw diff
when extacting DSCs, with the same ipsw mount
workaround fixing it).
Might it be worth flipping the force
flag default (at least for RO images perhaps if you want to play it safe)?
we'll see how this fairs ;)
https://github.com/blacktop/ipsw/commit/a1e10bfaabf9ab38f237ff5568eeee7eb9f808bf
feel free to open again, if the issue isn't resolved
What happened?
Tried to extract DSC from iOS 18 beta 7
e41a72d49fd246fed0110e4342672bafc709e76c
- IPSW hashby running
ipsw extract -d <ipsw>
, and it fails.If I instead run
ipsw mount sys <ipsw>
and then this command, it succeeds:I assume it's some sort of race from mounting to then looking for the DSC. Weirdly enough, I don't see this with beta 8 (hash
ae42ef0e7ffda7a625a1d5f3e578be1cbcec5633
)How can we reproduce this?
ipsw extract -d <ipsw>
ipsw mount sys <ipsw>
and then the commandipsw version
Search
Code of Conduct
Additional context
No response