[Android Software/Hacking General [Developers Only]] cowsngrass:
I've updated SALT to v2.0-7

Had some issues with v1.2-5 that continues with this new one.

After doing a backup and closing SALT, I can't re-open it until after I reboot my computer. The only time this occurs is after I backup the phone. Other SALT functions do not cause this. The error message is:

Failed to run /SALT/salt as user root

unable to copy the user's Xauthorization file​

Can't verify the backup (log below)... error is "no valid image files..."

The first backup I did (yesterday on v1.5) was a Full Backup. I did get a message that made me wonder if there was not enough space, but the results of the md5sum verification showed no errors. I haven't gotten any more messages concerning disk space, so I assume all is well...

I'm running LinuxMint 18.3 (just updated from 18.2 yesterday)

SALT meets my needs until it's time to try to modify the phone. Just thought this info might be important. Thanks again for all your effort.

Debug Log follows:

2018-01-03 16:21:52: Starting SALT v2.0-7:STABLE!

****************************************************

2018-01-03 16:21:52: F_EGO: started

2018-01-03 16:21:52: F_EGO: /tmp/salt.lock created

2018-01-03 16:21:52: DEVCON before: 99

2018-01-03 16:21:52: F_CHKDEVCON: started

aarch64

2018-01-03 16:21:53: F_CHKDEVCON: Device seems to be connected!

2018-01-03 16:21:53: RET: 0

2018-01-03 16:21:53: DEVCON after: 0

2018-01-03 16:21:53: EXPERIMENTAL: 0

2018-01-03 16:21:53: F_GETINFO: started

2018-01-03 16:21:53: F_CDARB: started

2018-01-03 16:21:54,389 partitions: INFO: Wrote 1048576 bytes to -

2018-01-03 16:21:54: F_CDARB:

2018-01-03 16:21:54: F_CDARB: DEVARB=2, DEVARBEMPTY=0

2018-01-03 16:21:54: F_CDARB: ended

2018-01-03 16:21:54: F_CKUSU: started

2018-01-03 16:21:54: F_LAFEXEC: started with these arguments: grep 'slub_debug=FZP' /proc/cmdline

2018-01-03 16:21:55: F_CKUSU: USU=1 (1=yes, 0=no)

2018-01-03 16:21:55: F_CKUSU: ended

battery_level:100 device_sw_version:VS98627C secure_device:S device_factory_version:VS98627C_00 model_name:VS986 target_country:US 2018-01-03 16:21:55: F_GETINFO: ended

2018-01-03 16:21:55: parsing usu:1

2018-01-03 16:21:55: parsing arb:2:0

2018-01-03 16:21:55: parsing battery_level:100

2018-01-03 16:21:55: parsing device_sw_version:VS98627C

2018-01-03 16:21:55: parsing secure_device:S

2018-01-03 16:21:55: parsing device_factory_version:VS98627C_00

2018-01-03 16:21:55: parsing model_name:VS986

2018-01-03 16:21:55: parsing target_country:US

2018-01-03 16:22:08: F_BACKUP: started with these arguments:

2018-01-03 16:22:16: F_BACKUP: choosen backup type was 2, Basic, 92160 KB

2018-01-03 16:22:20: F_BACKUP: choosen target directory was /tmp

#/dev/mmcblk0p1 (modem)

0:15:88064

0:31:88064

(Many files later...)

#All finished

2018-01-03 16:23:19: F_MSGOK: started

2018-01-03 16:23:21: Backup completed successfully

2018-01-03 16:23:21: 0

2018-01-03 16:23:22: F_MSGOK: started

2018-01-03 16:23:24:

Your device supports md5sum verification!

Do you want to verify your just created backup?

2018-01-03 16:23:24: 2

2018-01-03 16:23:24: F_BACKUP: VERANS was 2

2018-01-03 16:23:24: F_VERIFYBAK: started

2018-01-03 16:23:24: F_VERIFYBAK: detected files:

2018-01-03 16:23:24: 1

2018-01-03 16:23:24: detected files: -> 0

2018-01-03 16:23:24: F_MSGE: started

2018-01-03 16:23:37: ERROR: F_VERIFYBAK: No valid image files found

(valid are: bin, img, image, mbn, mmcblk0p*)!

2018-01-03 16:23:37: 0

2018-01-03 16:23:37: F_EXIT: started

2018-01-03 16:23:37: EXIT: F_VERIFYBAK: exited with code 3

2018-01-03 16:23:41: F_ADVMENU: started

2018-01-03 16:23:44: getlog script started