Nothing Phone (2) stuck in EDL / Firehose init failure — any advice?
Hi everyone,
I’m trying to recover a Nothing Phone (2) that no longer boots normally. The phone shows no screen output, does not enter fastboot/recovery, and gives no visible sign of life from button combinations.
However, it does enter Qualcomm EDL mode and is detected on Windows as:
Qualcomm HS-USB QDLoader 9008
What I’ve confirmed so far:
Device: Nothing Phone (2), European variant, 256GB
Qualcomm driver installed: 2.1.2.2
The Nothing Flash Tool detects the COM port
The .ntpi package is accepted and parsed successfully
Metadata, Patch, RawProgram, KeyMap, and FileIndex are extracted successfully
The phone disconnects/reconnects during the expected Sahara → Firehose transition
The problem is that the flash process always fails at the Firehose initialization stage with:
Firehose Read multiple Command data loss
then:
Failed to Get Init Input
and finally:
Firehose Read Input Failed: 4
This happens consistently at almost the exact same point, around 27 seconds after starting the flash attempt.
I have reproduced the issue with:
Different computers
Correct Qualcomm drivers
Different USB ports/cables
Nothing Flash Tool v1.4.0.0 with an older Phone (2) .ntpi
Nothing Flash Tool v2.5.1.0 with 22111U_release_user_20240628_043001.ntpi
Both setups reach the same Firehose-stage failure.
Has anyone seen this exact error before on the Nothing Phone (2)? Does it usually mean a wrong/incompatible Firehose/programmer/package, or could this indicate UFS/storage initialization failure?
Any advice from people who have successfully recovered a Phone (2) from EDL would be appreciated.
