Install Verizon firmware

[KurtStam]

Hey guys,

I just bought a Verizon badged G1100 router and it turns out it has Frontier firmware installed.

Active firmware is 01.03.01.12
Backup firmware is 01.04.00.10-FTR

I guess the active firmware is Frontier too as it still says frontier in the web interface.
I tried the advanced/fwupgrade link to install the Verizon tar, but it says it is invalid firmware.

1. Does it have to be a signed archive?
2. Is there another way to install the Verizon firmware?

Thanks
--Kurt

[Brandonv101]

@KurtStam I think the firmware needs to be signed and I am not sure at the moment if there is a way to install the Verizon firmware on a Frontier unit or vise-versa. If you can send me a link to the Frontier firmware I can try it on my replacement G1100 which had new firmware pushed to it when I had a tech visit a while back.

It's the same hardware it should allow any supported firmware unless it needs to be signed by frontier.

[KurtStam]

@Brandonv101 Thx Brandon

My router is running 01.03.01.12. The only signed version that comes close I found here
https://github.com/devttys0/binwalk/issues/256
http://bitcast-a.bitgravity.com/2wire/cms/DOWNLOAD/upgrade/frontier/D4A928/1.03.02.02/bhr4_release_01.03.02.02-FTR_firmwareupgrade.bin.signed

One thing I noticed is that the size of the frontier archives is about 43 MB, while the Verizon ones are double that. (https://www.verizon.com/support/consumer/internet/open-source-software-portal?CMP=DMC-CVZ_ZZ_ZZ_Z_DO_N_X00366). The /#/advanced/fwupgrade stops uploading at 55577565

1. I've noticed that when I upload the larger (unsigned) Verizon tar file the log says:
   Oct 29 03:27:30 2017 user.err<11> frontier4: Lui.Glue: Aborting since file is larger than max file size(55574528): 55577565
   So even before it checks the signature the upload fails.

2. When I try to use a frontier archive it does finish the upload, but then it fails, and the log says:

Oct 29 03:29:14 2017 user.err<11> frontier4: System: gpg:  
Oct 29 03:29:14 2017 user.err<11> frontier4: System: encrypted with RSA key, ID 3F881C75 
Oct 29 03:29:14 2017 user.err<11> frontier4: System: gpg:  
Oct 29 03:29:14 2017 user.err<11> frontier4: System: decryption failed: secret key not available 

So it clearly checks the signature after the upload.

I think using fwupgrade with a larger (and unsigned) Verizon archive is probably not going to work.

But I'm open to suggestions on what else to try!

[Brandonv101]

@KurtStam Thanks for all this useful info! I think it needs a signed firmware with gpg key or it could be that there is a hard limit on the file size on the frontier unit to prevent it being used with Verizon firmware. Maybe GenieACS and setting up a TR-069 may allow you to forcefully push the Verizon firmware?

[mzpqnxow]

@Brandonv101 is there a good guide anywhere on doing this with GenieACS? I have the 3 components of GenieACS up and running and I've pointed my config file to the GenieACS server but I'm not seeing anything happening (via tcpdump nor via the GenieACS GUI)

[Brandonv101]

@mzpqnxow Unfournately there is no good guide on doing this with GenieACS. I would like to write one but I have a lot of problems even getting GenieACS setup in a VM.

Usually if you try to powercycle the router you should see some info in the GenieACS logs. It should connect to the TR-069 server on bootup.

If I can only get a working premade VM image then I might be able to make the basis for a proper guide.

[mzpqnxow]

Curiously I’m not even seeing an attempt at a connection outbound- maybe a typo on my part. In any event, thanks

…

On Mon, Nov 13, 2017 at 15:45 Brandon Veerasammy ***@***.***> wrote: @mzpqnxow <https://github.com/mzpqnxow> Unfournately there is no good guide on doing this with GenieACS. I would like to write one but I have a lot of problems even getting GenieACS setup in a VM. Usually if you try to powercycle the router you should see some info in the GenieACS logs. It should connect to the TR-069 server on bootup. If I can only get a working premade VM image then I might be able to make the basis for a proper guide. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHpRZOLYWtkgsRu-dlgaTEAVF0of0rVwks5s2KpPgaJpZM4QJhu_> .

[Brandonv101]

@mzpqnxow No problem. If you need some more help maybe send over some logs and I can take a look.

[EricPHassey]

As @KurtStam I am also having the same problem. Verizon Fios G1100 router with Frontier Firmware. Would love to upgrade the firmware to the latest Verizon one. I'm willing to help out as best as I can. The firmware is all publically available from Fios, so it's just a matter of signing it, I presume to resolve this.

[anidev]

I am in this same boat as well. Looking at the Verizon page, it seems the massive 110mb download is just the source files, as opposed to the frontier firmware which appears to be the compiled binary image, which would explain why the Verizon download is so much larger. So far I haven't been about to find the Verizon firmware binaries anywhere, and I suspect if they were found the signing keys wouldn't match anyway.

[mholmes10]

I found my original FIOS-G1100 router (the coax interface stopped working) and plugged it in off-net and found it has firmware version 1.3.0.47.64
Would that copy help out?

[jameshilliard]

Maybe, what's it show under http://192.168.1.1/#/advanced/fwrestore ?

[mholmes10]

it shows
Active Firmware version 1.3.0.47.64
Backup Firmware version 1.2.1.36.84

I have to confess that I'm a bit of noob, but can follow directions well.

Like I said it broke shortly after upgrading to this router from the MI424WR, and has been off the net ever since (kept it in case).

[jameshilliard]

the setup to pull the keys is somewhat complex, do you have a linux system or linux VM I could remote into?

[jameshilliard]

Hmm, actually looking at how they are versioning it's probably unlikely the firmware is old enough, the stepstone is 1.2.0.36.98.0 and I think it would need to be older than that to have the keys I'm looking for.

[mholmes10]

I have a raspberrypi and ubuntu box that I could expose externally so you could remote in and connect the old router to.

If files would help... sounds like they may not be old enough.