blobsaver v3.0 Beta

[airsquared]

The full release of v3.0 is out, please download it from here.

---

There's some major changes in this version, so please report any feedback or issues you encounter with this version here.

Note that:

• This new version stores saved devices differently, so you will need to import your presets from older versions of blobsaver using the "File" menu if you would like to restore them.
• The version number says v2.6, but it's actually a 3.0 beta. This is to differentiate from when the full version is released.
• Because it's a beta, it will prompt you that a new update (v2.5.5) is available, even though that's an older version. To avoid the prompt, you can just click "ignore this version" the next time you see it.
• When the normal release of v3.0 is out, it will show a similar prompt to upgrade to v3.0 which you can download from the releases tab like normal.
• Java is no longer required starting in the v3.0 beta, so you can uninstall it if you like

Downloads:
macOS: blobsaver-2.6.dmg (if it says the app cannot be opened, try this)
Windows: blobsaver-2.6.exe
Linux: blobsaver_2.6-1_amd64.deb, blobsaver-2.6-1.x86_64.rpm, blobsaver-2.6.tar.gz

Changelog

• Read both the generator and APNonce from devices, so blobs can be saved on unjailbroken devices with a known generator/ApNonce pair (major thanks to @nyuszika7h for discovering this!)
• Now uses the system scheduler for saving blobs in the background instead of having blobsaver run constantly in the background, reducing system resource usage (launchd on macOS, task scheduler on Windows, systemd timers on Linux)
• Presets are now called saved devices, and support an unlimited number of devices
• Added feature to export/import saved devices to/from XML
• Allow optionally specifying a generator
• Fix getting stuck in recovery mode when trying to read APNonce
• Improved performance and error handling
• Added support for some devices that I missed previously
• Java is now included and does not require a separate installation (also updated to Java 16)
• UI updates
• Add basic & anonymous analytics that can be disabled from the "Help" menu
• A lot of other misc. fixes and enhancements + major code cleanup/reorganization

[EdgeXS]

Thanks for this. Just downloaded.

Issues:

• install: it didn't allow to run on the mac and i had to resign it using sudo codesign --force --deep --sign - /Applications/blobsaver.app
• when adding multiple devices. The force check is greyed out. (had to restart a few times before the force check wasn't greyed out)
• when background mode is enabled there is no menulet blobsaver icon however the activity monitor does the process running not sure if this is by design?
• when in background mode, if you reopen the app you don't get the blobsaver window. This is even true when you select the window nothing happens. But if you close it a shadow window appears before quitting. Reopening app allows you to see the window again.

Working

• background process seems to be working: when 1 minute frequency is created it goes and creates blob for devices for multiple devices.

[airsquared]

Does this bug with the window happen on 10.15 too, or just 10.14.6?

[joostiphone]

I had exactly the same issue not able to open it (in Dutch MacOS (11.2.3) says it's damaged and needs to be removed). So I used the command @EdgeXS mentioned and now it opens using control+open.

[airsquared]

It seems that I can't do anything about it saying the app being damaged, unless I pay for an Apple Developer account to sign the app. I just added a link to the wiki page with a solution.

[CoocooFroggy]

It seems that I can't do anything about it saying the app being damaged, unless I pay for an Apple Developer account to sign the app.

Not sure if this is the same issue, but with FutureRestore GUI, I just had CI do codesign --remove-signature FutureRestore\ GUI.app after jpackage which solved it from appearing as damaged. Then right click > Open worked fine.

[airsquared]

Thanks for the solution, it does seem to be working now.

[PencilNotPen]

The new saved devices menu looks good, thanks! Importing my presets from 2.5.5 didn't seem to bring Apnonces for devices which had them specified. Imported presets with specified Apnonces have the Specify Apnonce box ticked, but show no Apnonce in the box below. Not sure if the interface is not displaying it when it is imported successfully, or if it really is not imported with the rest of the preset information. Not the end of the world if it's just 2.5.5->3.0.0 as only have to re-add for max 10 devices, but hopefully they'll be preserved correctly through future updates, when users may have many device presets saved, and may not notice the Apnonces have gone, saving invalid blobs as a result. Cheers!

[EdgeXS]

importing from 10.15 without Apnonce works. Seems to work. Can restore occur without the Apnonce?

[PencilNotPen]

A12+ devices need to have specified an Apnonce for valid blobs. A11- don’t.

[airsquared]

I just fixed the bug with not importing the apnonce correctly, please try the latest beta.

[EdgeXS]

I'd add one request under the frequency its to specify a specific time for it to run. Since i have a system that isn't always on which will be my blob machine and it helps to verify the process is working based on a specific time frame for traceability.

[airsquared]

In addition to the time you set it at, blobs are also automatically saved on every boot. If your computer is shut down when your interval passes blobs will automatically be saved on the next boot, this way you don't need to worry about if your computer is off.

[EdgeXS]

great thanks. even better.

[bs286692]

For the Windows version:

1. The app no longer minimizes to the tray where it can run in the background.

2. Users should be able to change the sort order rather than defaulting to alphabetical sorting only.

3. Part of the app is cut off at the bottom and I I cannot resize the window.

4. Please put the version number in the file name for the Windows version as you have for the MacOS and Linux versions, e.g. blobsaver-windows-2.6.exe.

Thanks

[airsquared]

I think I found the problem, please try the latest one again.

[bs286692]

It seems to be working! I tried both starting and stopping background.

[airsquared]

Thanks for helping me test!

[bs286692]

No problem at all. It's awesome to have background saving working.

Question: What happens if there's an error saving, e.g. disk full, network unreachable, etc.? Will the scheduled task trigger blobsaver.exe to alert the user?

[airsquared]

It currently doesn't alert the user, but if there is was problem on the last run it will show in the Windows Task Scheduler. There should also be logs stored here, but I haven't checked to confirm this for sure.

In the specific case of the network being unreachable, it will postpone the task until a network connection is achieved. (at least according to my understanding of the options in Windows Task Scheduler)

I am considering adding support for system notifications to alert the user if something goes wrong in a future version of blobsaver.

[Absolucy]

When 3.0 is released, could you perhaps submit a cask to Homebrew? So it can be installed via brew install --cask blobsaver?

[airsquared]

Created a PR.

[airsquared]

blobsaver v3.0.1 is now in Homebrew cask.

[CoocooFroggy]

You may want to specify an image for the .dmg. Otherwise, it's just Duke.

You can do this with jpackage [...] --icon /blobsaverMacIcons.icns.

[buitim]

I'm digging the update so far! Would it be possible to save the generator as a part of a saved device? Or maybe that's just a bug on my end.

[airsquared]

Realized I forgot to add that, it should be in the latest beta now.

[oooooooooooooooo]

When trying to read apnonce from jailbroken device instead of manually inputting it the device was booted into recovery mode and was not booted out. It is currently stuck in recovery mode.

Device is iPhone 12 mini on ios 14.3 using the Unc0ver jailbreak

UPDATE: Managed to exit out of recovery mode using Reiboot. Being more than a little dumb I tried again in a non-jailbroken state. Same issue but once the device rebooted to recovery mode after Blobsaver tried exiting out I just used Reiboot again on the side and everything worked perfectly.

[airsquared]

Did it give an error or just silently fail?

[oooooooooooooooo]

Silent, it just stalled until blobsaver just stopped trying

[airsquared]

I think I've found the problem, please try the latest beta.

[ghost]

What if I don't have systemd (gentoo OpenRC users rise up)?

[airsquared]

If you don't have systemd, you can also manually set it up using cron if you like. Once you have everything setup for background saving, instead of clicking "start background", set up a cron job that calls the blobsaver executable with the --background-autosave argument.