Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qdl: failed to initialize libusb: Permission denied #83

Closed
rarenicks opened this issue Nov 21, 2024 · 4 comments
Closed

qdl: failed to initialize libusb: Permission denied #83

rarenicks opened this issue Nov 21, 2024 · 4 comments

Comments

@rarenicks
Copy link

Hi,
I am trying to recover my Qualcomm RB5 device using QDL model
I am able to see the device in lsusb :
Bus 001 Device 004: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Also set the proper udev rules for the device, still facing the permission issue.
"qdl: failed to initialize libusb: Permission denied"

I have given all required permission for the device, but the issue looks not with the device permission but with the qdl not being able to use libusb.

Host system :
Description: Ubuntu 22.04.5 LTS
Linux helios 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Installed qdl using snap "snap install qdl"

Thanks,
Avdhesh

@ndechesne
Copy link
Contributor

Please check https://docs.qualcomm.com/bundle/publicresource/topics/80-70014-253/ubuntu_host.html?vproduct=1601111740013072&versionId=1befb000-28cc-4b51-8b35-81601178edee, in particular the section "Update udev rules
". If that works for you, we should update the README file accordingly.

@rarenicks
Copy link
Author

Hi
I was able to run qdl after building it from github source

During flashing "./qdl prog_firehose_ddr.elf rawprogram?.xml patch?.xml"

Got this error :

[PROGRAM] flashed "aop_a" successfully
LOG: INFO: Calling handler for program
[PROGRAM] flashed "tz_a" successfully
LOG: INFO: Calling handler for program
[PROGRAM] flashed "hyp_a" successfully
Unable to open BTFM.bin...failing

Do you have any idea about this error or point me in the right direction ?

@ndechesne
Copy link
Contributor

Hi I was able to run qdl after building it from github source

Are you saying that you have a different behavior when you build from source vs when you are using the Ubuntu snap package? Or have you also modified the udev rules, as I pointed out earlier?

During flashing "./qdl prog_firehose_ddr.elf rawprogram?.xml patch?.xml"

Got this error :

[PROGRAM] flashed "aop_a" successfully LOG: INFO: Calling handler for program [PROGRAM] flashed "tz_a" successfully LOG: INFO: Calling handler for program [PROGRAM] flashed "hyp_a" successfully Unable to open BTFM.bin...failing

Do you have any idea about this error or point me in the right direction ?

the BTFM.bin file is referenced in one the rawprogram XML files, and needs to be 'flashed', but is missing from your local folder.

@andersson
Copy link
Collaborator

Hi I was able to run qdl after building it from github source
[..]
Unable to open BTFM.bin...failing

Do you have any idea about this error or point me in the right direction ?

QDL used to simply skip flashing partitions where it could find the files referenced, with the side effect of users reporting that what seemed to be a successful flash would actually have left old content in some of the partitions. So the tool will now instead abort if it can not find any of the referenced files.

You can opt in to the old behavior by specifying the --allow-missing argument when launching qdl.

Looks like your original issue has been resolved as well, so I'm closing this for now.

Thanks,
Bjorn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants