how can I debug a failed restore from a full adb backup of non-rooted phone?

How can I check / see why a full backup did not work for restoring with adb?

The long story:

#

Hello there,

I need some info on how or if it is possible to make use of my full adb restore file or I just throw it away and restart fresh of my device. Device is allview viper v1 (16Gb) -

NO ROOT and not interested in rooting it.

I believe I made a few versions of good back-ups including at least one good full backup including apks by using UBT (1.3.2 version if I am not mistaking).

My problem: I can't restore the phone by using any of the created ab files by using adb which drives me nuts.

It's worth to mention that in between I upgraded the phone software from 4.2 to 4.4 by using the producer's update images... I did a factory reset with 4.4 and re-installed most of the apps I had. I even copied most of the data from a file-sync backup...

Every time I try to use adb restore I get to the screen to input (now 2 passwords which basically are the same), I get the message "restore starting" and quite fast "restore finished" on the phone screen though while using the full back-up I definitely see that adb is still accessing / reading the file for longer time...

What I tried further: I used abe (android backup extractor by tweaking their .sh script) to create both standard individual .ab-s but also kitkat compatible ones (with abe pack-kk) with no luck in restoring the apps and their data.

It is quite annoying since after converting to .tar and un-tar-ing I can see that the backups seem ok and I can even see the sqlite data and xml settings for the apps but I do not know how to import those to the new OS running on the phone.

I tried this using both USB storage, picture mode, etc., input only the desktop pass and afterwards inputing both of the asked passwords.

So the question is: can I restore the data (about 32Gb including the pics and docs) or should I delete all the "working" files I created and put it on the "learn by error"?

Should I try to downgrade to 4.2. (if it is even possible..) and try the adb restore there? <-- this I discovered already that is not possible

Some update to the info below: - on the initial 4.2.x version of the running android I had most of my apps moved to the external sdcard (sdcard0) - that was their location (.assec) when I did the adb backups - in the meantime I checked more of my backups and they seem OK - I could uncrypt the ab to normal tar archives and see the contents of apps and shared folders

#