Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backing up has issues and doesn't work with Serotonin and Roothide Bootstrap #43

Open
theoccurrence opened this issue Jan 24, 2024 · 4 comments

Comments

@theoccurrence
Copy link

For starters, IAmLazy has issues writing to .../.jbroot.../var/jb/var/mobile/Documents, due to write permissions. This is easily enough fixed by filza, even tho other tweaks don't seem to have that issue, because there already was stuff present from other tweaks in this directory.

After giving the folder full write permissions for everyone, IAmLazy runs into a new error. Apparently it can't create a package list. But unfortunately this time, it doesn't state a directory which permissions I could change.

@L1ghtmann
Copy link
Owner

Hey, thanks for reporting these!

The permissions error occurs when the mobile directory is not owned by mobile. Surprisingly, this happens quite frequently even on other jb solutions.

The second error, related to package lists, is occurring because the service I rely on for bootstrap package resolution -- Canister -- appears to be reporting HTTP 521. I've reported this to the owner and will hopefully have it resolved shortly.

@theoccurrence
Copy link
Author

Hey, thanks for reporting these!

The permissions error occurs when the mobile directory is not owned by mobile. Surprisingly, this happens quite frequently even on other jb solutions.

The second error, related to package lists, is occurring because the service I rely on for bootstrap package resolution -- Canister -- appears to be reporting HTTP 521. I've reported this to the owner and will hopefully have it resolved shortly.

Thank you for the quick reply. I really want IAmLazy to work, because indeed, I am lazy. Updating Roothide Bootstrap completely resets everything, like restoring root fs. This would save me a lot of repetitive monkey work.

Oh, also the package seems to cause problems with dpkg ¯_(ツ)_/¯

image

This has been exactly the same with older versions as well.

In case this matters somehow, I am using an iPhone 12 Pro Max on iOS 16.4 with Roothide Bootstrap and Serotonin to inject tweaks into Springboard.

@L1ghtmann
Copy link
Owner

L1ghtmann commented Jan 24, 2024

That issue is occuring because IAmLazy has not been built to support the roothide package scheme. Copying in what I sent to someone else recently: while I would love to support all jailbreak types and versions, there are a couple of items preventing me from doing so. The primary reason is that the roothide package scheme was formulated against the wishes of those who maintain the jailbreak packaging framework (i.e., build systems, repos, and package managers) and thus I feel obligated to avoid supporting it. I myself am a frequent contributor to the build systems and have had discussions with Tuan regarding this and feel that his unwillingness to compromise or follow a more logical path that avoided further fragmentation was unwise. Additionally, the repo that IAmLazy is hosted on does not support the roothide package scheme, so I would be unable to officially distribute the update alongside other versions. Lastly, it was announced that Bootstrap will support regular rootless, following roothide's merge with Procursus, and that rootless v2 will redefine the rootless package scheme, making roothide's package scheme obsolete. Given these factors, I feel like it may be futile to attempt to add support for the current roothide-based Bootstrap, but hope to add support for it in coming versions.

Edit: that being said, you are free to build your own version with the scheme should you want to and IAmLazy should build out-of-the-box on all platforms Theos is supported on.

@L1ghtmann
Copy link
Owner

Apparently it can't create a package list.

This should be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants