Z5 Compact Update [32.2.A.0.305] MM 6.0.1 fails

[sausages1]

I am wondering if anybody can offer any advice with the following issue... So my device indicated that update 32.2.A.0.305 is available. However, after going through the update process, the phone restarts and displays the error message, "Could not install new software version. Please try again." I've tried 3 times now with no success. Now, I have encrypted the handset which I'm guessing may be be problem but, unlike with the Z1 Compact, I am unable to decrypt the handset to perform the update. From here I guess the only way is to perform a factory reset, install the new update, restore all data and settings etc and I'm golden. However, I have Google Authenticator installed with active key-pairs inside it... So how can I perform this security update without losing all Google Authenticator codes?

Also will this update fix the fingerprint scanner?  It works for around 3 hours after restarting the phone, then I get the error message, " Fingerprint hardware not available."

I really liked my Z1 Compact and it was the best phone I had for over 2 years.  However, so far, I am unimpressed with all of the issues with the Z5 Compact and i would really like to get it working flawessly.

Thanks in advance to anybody that takes time of of their day to read my post and hopefully offer solutions.

[Christofer]

Hi @sausages, sorry to hear that you've been unable to update your device.

Do you have access to a PC? I would then recommend you to update your device using Xperia Companion. If you connect your device while Xperia Companion is running on the PC it will automatically check if any update is available and ask you if you wish to update.

Regarding the fingerprint sensor, if you still experience this behaviour after performing the update I'm afraid it is likely hardware related. If that is the case then the device needs to be examined by an authorised service center. Your Local support team can help you proceed with this, if need be, if you contact them directly.

Let me know if you were able to update your device.

[sausages1]

Hi Cristofer,

Yes I do have a PC, although I'm runing Linux, not Windows or MacOS unfortunately.  I should be able to try this out on a friends windows PC.

I would like to just check though.  Will this definately allow me to perform updates on an encrypted handset or are we just rying to see if this works?

[Christofer]

Encrypting the device will not stop making it possible to update it. In fact, most devices that comes with Android 6.0 pre-installed out of the box will be encrypted by default. This is because Google has decided that it is mandatory from here on.

If you don't have easy access to a Windows or Mac PC you can first try clearing data for the Software Update app in your device. You can find it in Settings > Apps > [menu] > Show system, tap the app in the list, then tap on Storage and select Clear data. Reboot your device after doing this and it should scan for updates and notify of the update again after a little while. If you experience the same error again I do recommend that you use a PC to update.

[NeoBeum]

If I was bothered id roll back and Stay with 253, if you haven't experienced a gamma/display issues, 305 gave me issues, I would stay on 253. Unless you want the August Google security patch. Or you have something older than 32.2.a.0.253

[sausages11]

Hi Christofer,

Apologies for the delay, also for some reason when I logged back into this site it asked me for a new alias as my old one was taken!  Im really not sure whats going on there...

First of all, I want to respond to your statement, " Encrypting the device will not stop making it possible to update it."  This is absolutely FALSE.  As I explained, the option to unencrypt the device is not even there.  You cannot unencrypt the device to install updates.  I could however unencrypt the SD card, which has unfortunately renered all contents on it to be corrupted.  The items are still there but i am unable to open/access them.

I tried connecting the device to a PC as you suggested.  However the update still did not install.  The problem seems to come when the device needs to be restarted and you are required to enter the encryption key...  This seems to interrupt up update process somehow.

Now, after many hours of trying I did manage to update my device.  First of all I backed evrything up and performed a factory reset.  Now I connected to the internet to update.  Unfortunately no new updates were found and I tried resetting the goolge.framework app as advised in many threads online.  Nothing worked.  After waiting fo 48 hours, still no updates were found do I was forced to download the latest update/image from a well know resource for the xperia range.  This involved downloading the new image (2.6Gb) as well as some other software, enabling usb debugging and flashing the new image to my device.  The good new is that I am now running the very latest update with the November security patch and Build Number 32.2.A.5.11.

I would like to express my deep dissapointment with the Sony Z5 Compact to date.  Like I said, i had the Z1 Compact and it was the best phone I ever had..  The Z5 Compact wil probably be my last Sony device now though after this recent problem.  The device had been a complete letdown due to the lack of ability to uninstall updates if you value high security and encrypt the device, the fingerprint scanner being faulty from day 1 and the blatant incompetence from Sony support ( no offense ).  You seem completely oblivious to these issues and even more oblivious as to their solution.

Now perhaps you can help me with this next issue.  Have these things been fixed in the latest update?  If I encrypt this device again will I have the option to unencrypt it to install updates and also Android 7.0 when it rolls out?

Regards.

[sausages11]

NeoBeum,

Thanks for your input.  Howver I have found a workaround and I'm now running Build 32.2.A.5.11.  You can see how I did this in my lates post reply to Christofer.

Regards.

[NeoBeum]

If you do upgrade to Nougat, I recommend backing everything up manually, and flashing the ROM 

If you flashed the firmware you have now, it's basically the same process

I rarely do major upgrades over the top of existing firmware

There were many hours spent on  the phone to Microsoft about Windows 10 being half assed installed for similar reasons