Comments on: Verizon’s FOTA & Its Dangerous, Dirty Little Secret

By: Follow-Up: MetroPCS Forces Automatic Update on Samsung Indulge | PhoneNews.com

Thu, 19 May 2011 13:26:18 +0000

[...] type of automatic forced update is the first one to be found on an Android device and is dangerous, as a broken download or bad update risks damaging the phone to the point where it will not [...]

By: Joe

Joe — Thu, 03 Jun 2010 15:48:47 +0000

I know this is an older thread but it is now June of 2010 & My Gzone Boulder has the same issue with Auto updating. Also it seems any firmware above 14 or 15 seems to have alot of issues & there does not seem to be a way to Downgrade the firmware =(

By: Humberto Saabedra

Humberto Saabedra — Wed, 17 Jun 2009 02:07:55 +0000

Just to add some info, the fimware is in fact directly taken from Casio’s KDDI build and modified for Verizon so there is no generic firmware at all for flashing.

By: Christopher Price

Christopher Price — Thu, 14 May 2009 23:50:09 +0000

Billy, there is no generic firmware available… so, you can’t. It would take PCD or Casio Hitachi to leak both the service tools, and the generic firmware to enable this.

There actually may not be a generic firmware in existence. The phone originated on KDDI in Japan, and the Verizon firmware is suspected to be modified from that.

By: Billy

Billy — Thu, 14 May 2009 23:24:02 +0000

All I want to do is hack my boulder and get modify veriozons horrifically terrible firmware. How can this be done?

By: T-Mobile G1 Update Causes All Text to be Entered As Commands | PhoneNews.com

Sun, 09 Nov 2008 09:54:32 +0000

[...] update also echos our previous coverage of Verizon’s FOTA implementation, which can be used to update devices without the [...]

By: Verizon FOTA Issues Persist, Customer Council Objects, FCC PSAPs Concerned | PhoneNews.com

Sun, 02 Nov 2008 04:35:57 +0000

[...] Our original reporting on Verizon Wireless’s issues surrounding forced firmware updates have sparkedÂ controversy. [...]

By: Chevy Volt’s Battery, its Moral Hazard, and My Solution | Christopher Price .net

Sun, 02 Nov 2008 03:07:04 +0000

[...] you’re in a natural disaster, or in a dangerous situation… it’s just as bad as a derelict cell phone that decides to update brick itself. So, give users a little bit of leeway, but set requirements [...]

By: Boulder Owner

Boulder Owner — Sun, 19 Oct 2008 14:32:33 +0000

If everyone is saying it just updates before prompting you, you just might have a defective phone. I have a Boulder along with many coworkers at my company, and none out of the 39 devices we purchased from Verizon gave us any problems with not prompting twice first. But go ahead and take the 1-2 examples you have and keep feeding the fire; deterring other people from getting what we all here at our company as a well put together device. The very few people whom are actually experiencing a problem not prompting first: Get off your lazy ___ and get a warranty replacement! Gies. All the time you spent complaining on this blog, you could have already exchanged the device, and had your problem fixed already.

By: Christopher Price

Christopher Price — Sat, 20 Sep 2008 04:25:27 +0000

We don’t have an update just yet… but I would agree that people should file an FCC complaint against this. When enough people file them, they are quite effective.

And, despite mob wisdom, it’s actually pretty simple to do… just go to fcc.gov and take 15 of your minutes to help make the wireless industry better.