I recently got photon kit from my lecturer which was bought in 2015. I tried to setup the photon with my android for the first time the photon was detected and was set up with particle app. The problem here is tinker page is unavailable. when i tried to reflash the tinker there was an error:“tinker reflash error”.
Welcome to the community - this is the right place to ask 
When you want to master Particle devices you should get CLI which is the Swiss Army Knife for these devices.
With a device from 2015 it’s highly likely that the device OS is out of date and you should update to the most recent version.
To do that you’d put your device in DFU Mode and then run
particle update -v
If you only want to reflash Tinker you can do that (also in DFU Mode)
particle flash --usb tinker -v
1 Like
if i try to update it is showing me this error
"An error occurred while attempting to update the system firmware of your device:
Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release!!!
Error during download get_status"
and my device is breathing magneta and the function calls are not working after it has become magneta.
Breathing magenta suggests your device is in Safe Mode (for whatever reason) which means your code is not running.
How do i update my firmware sir for the error mentioned above?
In the other thread you mentioned updating the bootloader, that would be a first step.
You can also put the device in Listening Mode and run particle serial inspect and post the output here to see whether there are other issues too.
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 1102, main location, 262144 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 204
System module #2 - version 1102, main location, 262144 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: FAIL
System module #1 - version 1102
Bootloader module #0 - version 7
User module #1 - version 4, main location, 131072 bytes max size
UUID: E54BE10B93EB07F1C8DCB9EAEECA0E33189ED07E8D6475FFA55F3962534559F6
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 108
User module #1 - version 2, factory location, 131072 bytes max size
UUID: F2E770BD00BF17180A08084B002208491A7001230B7007490A70074A1370074B
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #2 - version 1
The two FAIL lines in your inspect log should be resolved first.
And as said above
(mind the note in the other thread about the bootloader version too)