You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title said, "Very high storage usage after downgrading." and "Jailbreak's don't work after downgrading." can be fixed. It's because of the old system snapshot is still in rootfs, and keeping take up space. You can use command "snappy -f / -l" to check that. For those people who never jailbreaded in the old system, the snapshot should named "com.apple.os.update-". And for those people who used checkra1n loader app or unc0ver, It should named "orig-fs". Checkra1n loader will check the snapshot whether it matches the current system version. So we just need to delete this snapshot to fix the unjailbreakable issue and release the space.
To delete the snapshot (whatever the name is), you should run command "snappy -f / -d $(snappy -f / -l | sed -n '2p')".
The text was updated successfully, but these errors were encountered:
yes, i can confirm this method with deleting snapshot working, also u can jailbreak with checkra1n version 0.9.2, this version will allow installing cydia, then u can boot with 0.9.8 and all working fine
As the title said, "Very high storage usage after downgrading." and "Jailbreak's don't work after downgrading." can be fixed. It's because of the old system snapshot is still in rootfs, and keeping take up space. You can use command "snappy -f / -l" to check that. For those people who never jailbreaded in the old system, the snapshot should named "com.apple.os.update-". And for those people who used checkra1n loader app or unc0ver, It should named "orig-fs". Checkra1n loader will check the snapshot whether it matches the current system version. So we just need to delete this snapshot to fix the unjailbreakable issue and release the space.
To delete the snapshot (whatever the name is), you should run command "snappy -f / -d $(snappy -f / -l | sed -n '2p')".
The text was updated successfully, but these errors were encountered: