[Android Head-Units] donaldta:
TLDR: If you have a version of the .68 update with more than 4 files then delete it and re-download a copy from the current links provided in the initial post or the wiki page.

Okay, I don't want to beat a dead horse but it is apparent there has been a few unknown variables leading up to what I am unofficially dubbing "Frankengate". This post (hopefully) will finally clarify the root of the broken GPS caused by a version of the .68 update created from a well intended yet misguided attempt to provide a more "complete" update.

I have compiled and summarized the issues concerning the update that has caused a soft-brick GPS functionality. It is only a soft-brick since it can be recovered by installing the .23 firmware and performing a factory reset. However, do not perform a model change or MCU update with the .23 version, as it has been known to cause a hard-brick of the MCU which ruins the functionality of all the stock apps that pertain to multimedia, swc controls, bluetooth, and any other low level function that is facilitated by the MCU.

We'll start with the original .68 update from the manufacturer which is posted at http://betopseller.com/img/dvd/newandroidupgrade.zip (md5 sum: 17ed9bf6d6d8cb06d99dcd8d639ebc95). This update only contains the following four files:

8baf147e-ea4a-11e2-b181-000c29ba27c0

8d8d1b1a-ea4a-11e2-a661-000c29ba27c0

8e3513e2-ea4a-11e2-8a0f-000c29ba27c0

8ffd2eb4-ea4d-11e2-b23a-000c29ba27c0

Since the number of files in this update only contained four files, it was considered a "minimal" update when juxtaposed to some of the past versions which contained more files. In order to make it a "complete" version of this update, the missing eight files from the previous updates were added to the archive as if they were differential updates.

8a36a6ca-ea4a-11e2-9fda-000c29ba27c0

8b1b92f8-ea4a-11e2-8ad4-000c29ba27c0

8c46e290-ea4a-11e2-859a-000c29ba27c0

8ce18b2e-ea4a-11e2-b8f8-000c29ba27c0

8f1149c0-ea4a-11e2-9029-000c29ba27c0

8fd2d810-ea4a-11e2-b31e-000c29ba27c0

1951add2-f1f3-11e2-b192-000c29ba27c0

fa6e4352-ec9e-11e2-9ffd-000c29ba27c0

The twelve files version of the .68 update was then uploaded to various file distribution hosts as "android-4.1-2.6.68-complete.rar". The original four files version of the update was also uploaded and renamed to "android-4.1-2.6.68-minimal.rar". However, as feedback from various forum users came through claiming the .68 update broke the GPS functionality, we later found out that the "complete" update did not originate from the manufacturer. Instead it was "Frankensteined" from earlier versions. At that point, all copies and links for the "complete" and "minimal" updates were removed.

After a little time, the original versions of the updates were again made available except for the .23 and .68 versions. The .23 was held back because it was confirmed on at least two occasions that it caused a hard-brick of the MCU upon a model change or MCU update. The .68 version was held back because of the GPS problems reported. The idea was to limit access of these version via private message, so that each person could be made aware of the problem associated with the update before downloading it.

It soon became apparent that this method of distribution was more of an inconvenience to both sides, so it was suggested to make them available with a password which suggests that the user would have enough clues towards issues related to the update. Unfortunately when the .68 update was made available with this mechanism, it was a copy of the 12 files "complete" version now named "android-4.1-2.6.68.rar" (md5: a0093839321bfb03956c3ceee34d8626). After verifying this, the files have been replaced with the original four file version with the same name but now with the md5 sum: 72a6fc69f723782f46d0f7abaecf260e.

At this point here is the tally which suggest statistically that the GPS problems were more likely due to the 12 file "complete" version NOT the original 4 file "minimal" version.

Broken GPS with .68 "minimal":

Broken GPS with .68 "complete": [MENTION=5603471]pgarrity18[/MENTION] (1579), [MENTION=5507055]atijasa[/MENTION] (1277), [MENTION=5641403]scubee[/MENTION] (1194), [MENTION=5669580]smallie42[/MENTION] (1506),

Broken GPS with .68 "unknown": [MENTION=5657731]NickNoltePop[/MENTION] (1546), [MENTION=5679258]Lexsus1983[/MENTION] (1522), [MENTION=5669989]mmm1961[/MENTION] (1409), [MENTION=5563417]gghghgh[/MENTION] (1181), [MENTION=5653239]latino-7[/MENTION] (1152)

Working GPS with .68 "minimal": [MENTION=3066536]TOMMYX2[/MENTION] (1731), [MENTION=304291]Black6spdZ[/MENTION] (1730), [MENTION=1255922]ransu[/MENTION] (1333), [MENTION=5507055]atijasa[/MENTION](1298),

Working GPS with .68 "complete":

Working GPS with .68 "unknown":

If there is anyone on this list or not on this list and would like to be represented with more accurate information then just verify which version you had or have used.​

Hopefully, that will clear up the confusion about the the various updates which were made available.

In light of the current situation, can you try downgrading to the .23 firmware, performing a factory reset then updating to whatever version you feel most comfortable. As, I understand from the previous posts that after applying the 12 file version of the .68 update it may take a several attempts to revert to the .23 firmware.