As it turned out, all the other apps had their corresponding
.json file missing. Not a big deal: As badp's answer shows, one can simply use
adb restore to restore the backups. But as not everybody might have the SDK (or even a minimal ADB) installed (or even a computer available -- one might be on a journey), my answer will take a different approach.
What we need
First, you will need to make a backup of some app, to get a working
.json file. As the question states, there was such one from the Adobe Reader. To visualize it for you, this is what the corresponding file (
com.adobe.reader.json) looks like:
You will also need:
Of course, you could also perform the steps below from your Linux computer; using a different OS, take care for the file's encoding and line breaks.
What we do
I pick an example app here: Kindle for Android. In the question's screenshots, it's listed close to the Adobe Reader as
com.amazon.kindle. For your apps, just pick the corresponding values based on this example:
com.amazon.kindle/com.amazon.kindle.json with an editor
Adobe Reader by
Kindle for Android for
label (actually, you can put anything here -- but might prefer to know what you've got :)
- optionally, replace the
versionName accordingly (it will work without)
- save the file
I'm not sure what
flags stand for, so we better don't touch those. We also can safely ignore the rest:
- "enabled"="true" should mean "this app is enabled (i.e. not frozen)"
- "system"="false": It's no system app (matches: Kindle is no system app)
- "locked"="false": This app is not "protected"
- "date" obviously holds a Unix timestamp (most likely that of the backup)
- "apk"="false": Ah, data only (Cabon's default is to not include the
.apk with the backup, to speed things up)
- "backup"="true": Is this a joke? What else could it be?
Now, first let's see whether Carbon accepts our trick. If it correctly lists up Kindle for Android as being available for a restore, you might want to repeat above steps for your other backups as well.