search

linux-msm / qdl

BSD 3-Clause "New" or "Revised" License
196 stars 76 forks source link

Waiting for EDL Device #15

Closed luke-shields closed 1 month ago

luke-shields commented 3 years ago

Hi there, I am attempting to flash a Jiophone 2 F300B Device however the QDL tool doesn't seem to be recognising it

./qdl --debug --storage emmc --include '~/Downloads/LYF-F300B-001-01-21-230818' '/home/luke/Downloads/LYF-F300B-001-01-21-230818/boot_images/build/ms/bin/8909/emmc/unsigned/prog_emmc_firehose_8909_ddr.mbn' '/home/luke/Downloads/LYF-F300B-001-01-21-230818/common/build/bin/asic/sparse_images/rawprogram_unsparse.xml' '/home/luke/Downloads/LYF-F300B-001-01-21-230818/common/build/patch0.xml' Waiting for EDL device /dev/bus/usb/001/009 /dev/bus/usb/001/009

Despite the device reading the correct ID Vender and ID Product

Bus 001 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

ModemManager has been stopped

jwinarske commented 3 years ago

Is the device in question fused?

SnikhilK commented 1 year ago

Faced a similar issue and this solved it~

Note the correct ID Vendor and Product ID from lsusb Ex: Bus 001 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Modify the android.rules sudo nano /etc/udev/rules.d/51-android.rules

Add this line, if not added already: SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="XXXX", MODE="0666", GROUP="plugdev"

Here replace XXXX --> with the Product ID from lsusb output, ex:9008

Now reload the rules :

sudo udevadm control --reload-rules
sudo service udev restart
sudo udevadm trigger
jwinarske commented 1 year ago

Also be sure to disable modem manager

sudo systemctl disable ModemManager
Andoramb commented 7 months ago

Hey :)

I'm running this in a virtual environment on Proxmox. I followed these steps, but I get a simple disconnect on dmesg: qcserial 2-1:1.0: device disconnected

The flashing never starts after that. How should this behave in a VM env?

I tried to attach by ID, by USB port, but always the same

jwinarske commented 7 months ago

@Andoramb your issue isn't related to the topic. Create a new issue please. In your case I suspect your virtual environment is not correctly setup for USB. You have a number of options to confirm that. Also strace -f is your friend. Also make sure modem manager is not running. Create new issue with correct title, and put your results there. Cheers

Andoramb commented 7 months ago

Thanks @jwinarske! I thought it might be related, but there are a lot of variables here. I'll doublecheck and create a new issue, if it's still relevant.

Thanks for the quick response 👍