When fastboot devices does not get device ID as response, best not to go on.
On Windows this is most likely a drivers issue. Windows is likely to provide a simple driver but for this job you need what is described perhaps as “combination driver”
Open a Windows Device manager window alongside your terminal. Look out for your phone becoming a “ Problem device” as you switch it to Fastboot mode.
Now run Windows update with the “problem device” selected.
Yes the driver is the issue- there is a yellow triangle next to the Android device in the Windows Device Manager.
But when I right click on it and select ‘update driver’ the two search options- Windows Update and my local drives don’t find anything.
Well I didn’t get far! Cannot flash the partitions as per the instructions.
(tried fastboot flash dtbo dtbo.img and always get ‘cannot load’)
Obviously this next stage (Partitions) is a huge problem looking around this forum…I don’t even know what ‘partitions’ are…
From the instructions: 1. First unzip the /e/OS Recovery file linked in the section marked Downloads for instantnoodlep . The following files would show up in the location where you unzipped the contents of the eRecovery zip file
dtbo.img*
vbmeta.img*
The problem is that unzipping that e/OS Recovery file does definitely does not give me two files called dtbo.img and vbmeta.img
It gives me six files all named something different.
But even if I go over to Lineage and get the files that correspond- they don’t flash either
I did try flashing these two you list:
dtbo-e-2.4.1-t-20241010439852-community-instantnoodlep.img
vbmeta-e-2.4.1-t-20241010439852-community-instantnoodlep.img
but no joy.
How does it know where these files are located on my computer?
I will check my installation of SDK Platform Tools though I did download it yesterday…