Forums - No Permissions for jflash

2 posts / 0 new
Last post
No Permissions for jflash
Join Date: 18 Jan 20
Posts: 7
Posted: Sun, 2020-01-19 01:08

Hello everyone!

I am running the bash file and this is the output that i get:

Linux Version
Linux t-p-maker-2-ub-ww-n 4.15.0-74-generic #83~16.04.1-Ubuntu SMP Wed Dec 18 04:56:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Linux Shell
[Info]: /bin/bash
Intrinsyc Technologies Corporation
JFlash Updater for the apq8096-drone & 
Build Version 
openjdk full version "1.8.0_232-8u232-b09-0ubuntu1~16.04.1-b09"
Java Version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-8u232-b09-0ubuntu1~16.04.1-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
Checking device connectivity status...
Bus 002 Device 006: ID 05c6:901d Qualcomm, Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 002: ID 03f0:094a Hewlett-Packard Optical Mouse [672662-001]
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[SUC] - Found a fully booted Device Bus 002 Device 006: ID 05c6:901d Qualcomm, Inc. 
Attached USB device ID List
error: insufficient permissions for device
Looking for [apq8096-drone]
Booting into fastboot for jflash utility...
adb server is out of date.  killing...
* daemon started successfully *
error: device not found
No suitable product found


when I run adb devices this is the output:
adb devices
List of devices attached
9b3d4257 no permissions
I have looked into why the error is shown in the bash file and found that in the line of product searching it runs 
adb shell getprop
and the reuslt is "error: insufficient permissions for device".
how can I get the permissions to run the script?


  • Up0
  • Down0
Join Date: 18 Jan 20
Posts: 7
Posted: Sun, 2020-01-19 03:28

I have solved the problem. 

The problem was in the adb server, for some reason it restarted without root permissions and so couldn't get connection to the device.

I added the following lines:

beofore the line which is for me line no. 168

modelIdApq=$( adb shell getprop |  tr -d '[:space:]' )
I added the following lines:

sudo adb kill-server
sudo adb start-server
  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.