Hello again!
The possible fix is available on Live, the new Android applet version is 7.11.8.
Please feel free to try it and give us a feedback whether it solves the issue.
Regards,
Sandor
We have Uninstalled, Reinstalled, Cleared Cache, Factory Reset, Enabling Secure Folder, Manually Activating Device Admin for the App and about every accessible security setting on the tablet. Each time it is the same result...Launch App from Tablet > Enter PIN generated Tech Desktop Console > Connecting > Waiting For Technician > Brief display of who the Technician is > Unfortunately Rescue Has Stopped.
kgilliamjr We continue to investigate this problem, and I will update the thread as more info becomes available.
kgilliamjr Would you be able to help us create a case for your scenario? Ideally we'd like some screen recordings from both ends, the device model, and log files...
sv5 I have a full log file and we have reviewed it. The issue we believe is related to the Samsung Experience version 9.5 returning a NULL value for the baseband version. This field is required by Rescue + Mobile for Android and crashes on the NULL value for baseband version.
In the Settings > About tablet > Software Information we expect to see the baseband version but no baseband section is even available.
Samsung Galaxy Tab A (2017) - SM-T380
Android Version: 8.1.0
Samsung Experience Version: 9.5
Thank you for your extra info, very useful!
The unknown baseband is a kind of common Samsung issue, I found this article, could you try it?
https://androidflagship.com/33304-restore-null-imei-fix-not-registered-on-network-galaxy-s9
