Firmware VR1600v2

SOLVED Go to solution
patchyfog
Level 2

Hi 

Is there an firmware update available for my TP Link Vr1600v2? The installed version is 
0.1.0 0.9.1 v5006.0 Build 190228 Rel.72265n

 

Thanks

2 ACCEPTED SOLUTIONS

Accepted Solutions
David_M
Moderator

Hi @patchyfog 

 

Hardware version: Archer VR1600v v1.0
NBN-FTTN/FTTB/HFC/FTTC = TP-Link VR1600: 0.1.0 0.9.1 v5006.0 Build 180828 Rel.56416n
TPG-FTTB = TP-Link VR1600: 1.1.0 0.9.1 v5006.0 Build 180828 Rel.35294n

 

Hardware version: Archer VR1600v v1.1
NBN-FTTN/FTTB/HFC/FTTC = TP-Link VR1600: 0.1.0 0.9.1 v5006.0 Build 190228 Rel.72265n
TPG-FTTB = TP-Link VR1600: 1.1.0 0.9.1 v5006.0 Build 190305 Rel.72906n

 

You have the latest version for your hardware version already.

 

Thanks,

 

View solution in original post

David_M
Moderator

Hi @patchyfog 

 

I believe V2 is the same is V1.1.

 

Thanks,

View solution in original post

5 REPLIES 5
David_M
Moderator

Hi @patchyfog 


Thanks for your query!


Let me have a look for you, and I will get back to you ASAP.


There is also a new ''TPG Mobile APP'' to help you with various trouble shooting and account issues, via a mobile phone app.
https://www.tpg.com.au/download


Regards,
David_M

David_M
Moderator

Hi @patchyfog 

 

Hardware version: Archer VR1600v v1.0
NBN-FTTN/FTTB/HFC/FTTC = TP-Link VR1600: 0.1.0 0.9.1 v5006.0 Build 180828 Rel.56416n
TPG-FTTB = TP-Link VR1600: 1.1.0 0.9.1 v5006.0 Build 180828 Rel.35294n

 

Hardware version: Archer VR1600v v1.1
NBN-FTTN/FTTB/HFC/FTTC = TP-Link VR1600: 0.1.0 0.9.1 v5006.0 Build 190228 Rel.72265n
TPG-FTTB = TP-Link VR1600: 1.1.0 0.9.1 v5006.0 Build 190305 Rel.72906n

 

You have the latest version for your hardware version already.

 

Thanks,

 

patchyfog
Level 2

Hi @David_M 

 

Thanks for that, however, those you listed were hardware versions v1 & v1.1 - my hardware version is listed as v2.

Are those you listed still applicable? 

 

Thanks

David_M
Moderator

Hi @patchyfog 

 

I believe V2 is the same is V1.1.

 

Thanks,

patchyfog
Level 2

Okay, thanks @David_M