Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status
This is the error code I receive when i try to run the "particle doctor" and put the device in DFU Mode.
I can do "particle setup" and everything seems well to me, but the device blinks a strange led: half blu and half red...
Can anyone help to recover my Photon?
Thank you!
Have you searched for that "error" message in this forum?
The answer will still be the same as it was on all the others before yours.
This is called magenta and indicates Safe Mode which usually points towards an incompatibility between application firmware and Device OS.
I do searched and tryed all the solutions found in this forum but it’s still not working.
Also, in build.particle.io I can’t see the firmware on the Photon. It’s not indicated.
But in console.particle.io Diagnostic Test tells everything is fine with my Photon… 
I’m using Particle CLI on Win10
Any advice is welcome! 
The standard response to anything to do with "Invalid DFU suffix signature" is: "This is only a warning and can be ignored entirely"
The docs do show this image
This is where you see what Device OS is currently installed on the device and the dropdown list lets you select what version the firmware you may build will be targeting.
If you want to know what the currently installed application firmware is, you can use particle serial inspect to find out, but it's usually not important when you can just flash a properly targeted version to your device (which should be possible while breathing magenta).
Or you just run this with most recent CLI (currently 1.31.0) installed
particle flash --usb tinker
particle update
particle flash --usb tinker
(yes tinker before and after for safe measure)
After that your device should come back breathing cyan.
Nope.
That image is what I would like to see. But I see this one instead:
I can successfully signal my Photon but I can’t flash anything on it. I already said I tryed all the solutions indicated, and all of them have been unsuccessfull.
If I try to run those CLI commands I just received the Error message I’m compaling with in this post.
Is there a way to break this loop? 
I don’t know what happened with my Photon. Done nothing hasty. I have too other Photon that have been mistreat, comparing to this one, and they all work perfectly
What DFU drivers are you using? (I recommend libusbK)
What is the full output of these commands (in DFU Mode)?
particle --version
particle update -v
particle flash --usb tinker -v
And what does particle serial inspect return in Listening Mode?
Particle Serial Inspect:
Platform: 6 - Photon
Modules
Bootloader module #0 - version 2, main location, 16384 bytes max size
Integrity: FAIL
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 207, main location, 262144 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 207, main location, 262144 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: FAIL
System module #1 - version 207
Bootloader module #0 - version 7
User module #1 - version 2, main location, 131072 bytes max size
UUID: 2BA4E71E840F596B812003882AAE7CA6496F1590CA4A049310AF76EAF11C943A
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 1
User module #1 - version 2, factory location, 131072 bytes max size
UUID: 2BA4E71E840F596B812003882AAE7CA6496F1590CA4A049310AF76EAF11C943A
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 1
Particle version:
1.31.0
dfu-util 0.8
DFU version 011a
If I try to run these
particle update -v
particle flash --usb tinker -v
the update start and end with DFU Error
Thank you for your time
The bootloader seems to be invalid.
If I’m not mistaken you should see version 101 not 2 with a system version 207
Download this bootloader binary
https://github.com/particle-iot/firmware/releases/download/v0.7.0/bootloader-0.7.0-photon.bin
and flash via Listening Mode
particle flash --serial bootloader-0.7.0-photon.bin
Thank you so much!
Your advice let me escape that loop! Now, serial inspect is fine in each part.
I have some trouble with Wifi module that seems to be off…
You’ll hear me soon if I can’t solve by myself! O:)
Thank you!
I still have some trouble but cannot say why..
My Photon, now, breath green.
Particle Doctor fail in Wifi hotspot step:
Reset Wi-Fi hotspot name in listening mode
? Select Continue when ready Continue
The Doctor didn't complete sucesfully. undefined
I've already unclaimed this Photon (I don't see it anymore in cloud nor in build IDE) and changed Keys.
I tryed to claim this Photon again using Particle App but it stops at the last step: Verifying product ownership. In build IDE it says I can't claim that device.
Particle serial inspect still sees no problem.
How can I solved?
Thank you again!
What happens when you put the device in Safe Mode?
Unclaiming/reclaiming a device does virtually never help solving connection issues, so don’t even try 
Due to lack of insight on what application your device is currently running my guess would be that your code is starving the cloud process from processing time and hence the connection drops.
Breathing green indicates WiFi.ready() but !Particle.connected() - usually because the application does “demand” it that way.
There aren’t enough <3 for you! 
Ok, in safe mode I could claim my device by app. Even from cloud i can see it running good (Diagnostic says everything looks good).
Now, what’s the clever step? Can I flash something in safe mode, to erase the application that is maybe the root of my connection problems?
I don’t have any idea of what application it is… too times passed by!
Yes you can, or you could use particle flash --usb tinker or particle flash --serial tinker to put back the factory default application.
Done! It works perfectly!
Thank you again and more!
sir i got this error when i tried using the command
"Error writing firmware: File does not exist and no known app found"
Have you downloaded that file and is it there where you are running that command from?
BTW, now we are already at version 1.1.0
Yes sir i have downloaded that file.the located at downloads of my computer
Then you either need to cd into the Downloads folder or provide the entire path to CLI - how would CLI know where you placed the file without being told?