-
Notifications
You must be signed in to change notification settings - Fork 788
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
Failure on Updating Symlinks after several reboots post initial bootstrap #278
Comments
can you zip and upload /var/mobile/Library/Logs/CrashReporter ? |
Can I retract WifiLQMMetrics files from the zip file? I cannot seem to find what they contain, but I am worried about them containing nearby wifi SSIDs and other information that could pinpoint my location. I've looked at all the other log files and I am comfortable sharing those ones, but am unsure about the Wifi ones. |
sure, no problem |
Here you go! |
yes. did you clean the CrashReporter files after the failure of "update symlinks"? |
I don't think I did, will the logs appear after rerunning or do I need to reboot and then bootstrap again? |
yes please |
No files appeared or were updated from what I can see in Filza, both after bootstrapping without rebooting and bootstrapping after rebooting. I do have the capabilities to run xcode with a debugger, if trollstore installed apps lets them be debugged by xcode, though I don't really know how to use a debugger nor to allow apps to be debugged if xcode doesn't work out of the box, so I would need to be helped through all that. |
what was the last working version of Bootstrap?
what was the last working version of Bootstrap on your device ? |
1.2.6 is the only version I have had on this device. I did have it working, and was able to restore the boostrap environment once after a single reboot (when my phone died), but after the multiple reboots, I cannot get it to go. |
I'm guessing that for some reason bootstrap's environment is corrupted. |
There is only one environment. |
and make sure these file exists in your device : |
All of those files exist where they should be, however the /bin/sh symlink is pointing to a .jbroot- directory that doesn't exist. Some other symlinks in jbroot:/bin/ also point to invalid locations as well. I wonder if there is a way to easily search for all of them without having a full terminal available. |
can you show me that the full path of /var/containers/Bundle/Application/.jbroot-xxx, |
The full path is |
Okay, quick update, it seems like a lot of files are pointing to the wrong location. Once /bin/sh is fixed, would the updating symlinks command automatically resolve the incorrect symlinks to point to the current |
updatelinks.sh relies on these symlinks, which should link to relative paths instead of absolute paths: |
I resymlinked those two files (actually the /usr/lib/.jbroot one was fine), and reran bootstrap, and it errored out in the exact same way. jbroot:/bin/sh now is pointing to the same invalid location as before... is there a file that sets the ID value of the .jbroot- folder? |
I think you need to fix these symlinks as well: |
unfortunately I just ran out of Screen Time on my phone, I can test those as well tomorrow. I can confirm for you that .jbroot was already pointing to ".", but I don't know about bin's .jbroot |
ok let me known if there any progress |
Okay, fixing all those symlinks fixed the issue. Should I close this issue since I manually resolved the problem? Or should I leave it open for further investigation for why this occurred encase this is an actual bug with Bootstrap? |
1: If your device suddenly reboots/shuts down during boot, then the updatelinks process will be interrupted and one part of .jbroot will be updated but another part may not be updated. and updatelinks depends on the .jbroot mentioned above, so this will cause updatelinks to fail to start normally again. 2: If you reinstall the "dash" package (which provides /bin/sh), the symlink to /bin/sh will change from a relative path to an absolute path. (due to the way procursus's bootstrap is built, it may automatically reinstall the dash package when you use apt to update packages.) this is an imperfection of updatelinks. we plan to make it a standalone executable without relying on .jbroot |
Work? |
I have this issue on my iPhone, too. My device is iPhone 13 Pro with iOS 17.0. I tried to uninstall Bootstrap then reinstall, but this time it only hangs on "Finalizing Bootstrap". Though I just used BS to tweak a few apps, I still need BS strongly. Thanks in advance. |
Device Model
iPhone 12, A14
iOS Version
16.6.1
Bootstrap Version
1.2.6
Serotonin Version
No response
What happened
After initially bootstrapping, I rebooted my phone several times to try to get something else to work. During this I did not bother to bootstrap again, and rebooted probably like 5 times. Now, every time I try to bootstrap using the app, the process fails on the Updating Symlinks step, with a “code(255)” message box appearing. I was expecting to be able to re-bootstrap without running into issues. I currently have not tried to fully uninstall Bootstrap, since I would prefer to keep my configurations and installed packages.
Screenshot of error:
Log output
Acknowledgement of README and FAQ
The text was updated successfully, but these errors were encountered: