Database Develop

Camera Error - Cannot connect to camera

Ok, so everything was working fine yesterday. I woke up this morning and decided to play a little 'world of photo'. It FC's, so I mess with it for a little bit before just trying to open my normal camera. When I try to open my camera, it puts the screen in sleep mode, so I have to hit the power button and unlock the screen like normal, then it gives me the error "Cannot connect to camera".
My phone is rooted and flashed with the latest Cyanogen business, but like I said, nothing was altered, updated, downloaded, etc. My camera just stopped working. Anyone have any thoughts or ideas? Really hoping to get this resolved without having to contact HTC, as I'm sure the unlocked bootloader screen will cost me a small fortune.
If I open an alternative camera app, it opens, but doesn't work. I can back out and then go to my default camera and it works until I close it. Then it won't open again without having to go through the steps of opening the other app, etc.

I'd try a nandroid restore.

Tried it already. Tried restoring back to original, wiping, everything else. Nothing worked. Camera wasn't working all morning, now all of a sudden it's working again. Guess I'll just count my lucky chickens and chalk this up as a win...

Well, my happiness was short lived. Still having the same problem. I'm really not sure what exactly it could be. But the fact it worked the one time today gives me hope.

also having this problem. tried a nand backup and also wiping and re-flashing the gapps and the cm-5.0.4.1 update.. still nothing

it seems my camera went bad somehow, tried even flashing the stock rom, nothing... i'm calling htc, crap my phone is unlocked.. wish me luck.
update: yeap, im getting a replacement. they put $529 on hold on a credit card, send you the device and once they get the "damaged" device they release the funds... meh..

Hey velazcod, you think we can get an update on his this worked out? I'm having the same camera problem and I too am bootloader unlocked. I'd like to hear how HTC handled your unlocked device.

sorry for not posting a status before... so here is what happened:
- Called HTC and they didnt have any issues replacing the phone since the issue seemed to he a hardware issue. They have been nice about this, depends on the hardware issue, I guess if you burn the motherboard they will probably get *****y.
- You can send it to get repaired or replaced, both are in warranty, unless they find some other issue (water damage, etc). However, if you decide to get it replaced they would take your credit card, and put $528 on hold for a few days until they get the original phone back. They dont actually charge it to the credit card, just an authorization, it all depends in your bank, for example my bank (chase) put the money back in my account after 5 days.
- Anyway, I got my "new" N1, and I double checked everything before unlocking the bootloader and doing our stuff. The phone was crap, it was slow and the sticker on the battery cover seemed like it was removed, maybe a refurbished unit. I called and *****ed about it, and they said I needed to send my original phone back, and then later on request another replacement. I kept *****ing because I could live with a bad camera for a few weeks, but not with a slow phone
- Anyways, in the end they allowed me to send back that refurbished unit. After a few weeks i had no response from them and I had to call them, a day after i got my new phone, this time it was good, so i unlocked it, did my thing, factory reset the original phone and sent it on its way.
- It all seemed good for a few weeks, until i got a call from HTC saying that I needed to pay for a repair fee ($60 something) because they had found the problem had been user damage. the girl had no idea how to back that up, and i kept saying that i had never drop the phone or broken the camera in purpose (which is true). She said she was going to escalate the issue and I would get a call back. Still waiting.
In the end I got my new phone and we are all happy, but be careful, I love HTC but don't let them screw you.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

$60 isn't that bad. I would be interested in exactly what they found.

yes that isnt that bad. and i would pay it no problems if it really was my fault. but really, i take care badly of my phones and i had never drop or have done anything to my phone that would cause this camera issue.
besides, the girl that called me had no idea what really happened or what they found, when they call me i will post the info here.

Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.

moto211 said:
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
Click to expand...
Click to collapse
Well, keep in mind that it could be a placebo effect, and you think you are fixing it by fiddling the SD card but its not real.
The reason I tell you that is because, when the issue started happening for me, I would get that error randomly, and then it started happening more frequently until it totally stopped working.
Also, the Camera app not detecting the SD card gets an error when you try to take a picture and it actually says the specific SD card error. Try taking the SD card out and try it out, you will get a visual of the camera on the display, but when you try to take the picture it gives out the "SD card not detected" error... on the other hand, you might be experiencing something totally different.
This error "cannot connect to camera" also comes with the camera app not loading completely and visual of the camera not loading on the screen. Also try loading up the Barcode Scanner, you should get a similar error and no visual of the camera.

I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.

moto211 said:
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
Click to expand...
Click to collapse
I see what you mean. Makes sense, keep us posted.

Update:
So, although the fix I previously mentioned did work, I started having other issues that indicated that the actual camera hardware was failing. When I would start up the camera app the camera image displayed on the screen started showing color distortion. Sometimes it would do that and sometimes it wouldn't. I noticed that if it wasn't distorted, I could lightly squeeze the sides of the phone and the image would become distorted and would not go back to normal after I stopped squeezing. I figured that indicated hardware issues but decided to try a low level format on my memory card just in case it was an issue of bad blocks on the card. The format didn't fix anything. A few hours later, the camera died and never came back. I started a ticket with HTC for an advanced replacement. I received my new phone on Friday and am sending back the old one today. I restored it to unrooted factory ROM and recovery image. I will keep you guys posted as to what, if any charges they try to stick me with.

moto211 said:
Update:
So, although the fix I previously mentioned did work,......
Click to expand...
Click to collapse
crap, that's what i thought. that sucks. keep us posted :-/

Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.

moto211 said:
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
Click to expand...
Click to collapse
Good to hear that.
On my case, I was never contacted again by the "escalated rep"... but I just checked my ticket/case and it seemed to have been closed, so I guess good news.

Hello Guys,
I am having the same problem as you both had. Í am seeing the same symptoms such as not able to run the camera app. My phone screen goes blank when i try to open the camera app and the bar scanner program says it cannot connect to the camera and that I might need to restart my device. I have tried to use previous roms and removed the sd card but nothing seems to work. I am wanting to send it in for repair but I wanted to know what else I should do to my phone besides reflashing the stock rom. Did either of you have the amonRa recovery program and how did you remove it if you did. Is there anything else I should do?
Thanks.

I got the original shipping rom package from modaco and renamed it PASSIMG.zip and flashed it from the bootloader. It restored everything to stock...recovery, radio, and os.

HELP XDA! Phone Reboot's if using 3g Data

Hey,
My AT&T rooted nexus one is still randomly rebooting if I use 3g data. I am in Costa Rica and the 3g is on the 850 band. I also have to add the apn "kolbi3g".
So basically I can use the phone for anything and it works great, but if I add the apn and start using the 3g heavily I will get a reboot, sometimes it will reboot vibrate 7 times and I have to pull the battery. I have tried 2.1 and 2.2 rooted and not also cyanogen 6 all the same problem.
If I do *#*#4636#*#* and select the wcdma only it runs the 3g better but reboots way more, sometimes the instant I place load on the connection. However if I select wcdma "unkown" the 3g works much better I can use it sometimes 30min at a time without a problem.
So any ideas what I could try? Is there a kernel that will up the volt's a bit just help stability? Or anything else I could try? Data roaming is off, I have tried both off and on, no difference that I can tell.
Thanks a lot this is driving me crazy! Just got this phone Sunday too sick to my stomach of the thought I spend $600 on this phone if I can't get 3g to work

How about radio image???
It is currently on baseband 4.06.00.12_7. Is there a more current radio?

I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.

Cabarnacus said:
I came across this multiple reboot issue on a (locked) Vodafone UK Nexus.
It booted into the OS (lockscreen) and as soon as data connected it looped back to the last couple seconds of the animated Nexus logo.... and again.... and again.
I powered down the unit (battery pull), booted into bootloader (voldown+power) and selected clear storage (voldown,voldown,power) then (volup) to confirm.
This deletes the user data and you have to sign in and set up the phone again but it certainly fixed the issue. My only guess is some user data became corrupt and the kernel panicked and forced a partial reboot.
Give it a try and lemme know.
Click to expand...
Click to collapse
Just did that (had the phone plugged into wall charger), and the second I got to the home screen it rebooted then vibrated like 6 or seven times. Seems to do it worse when it is plugged in. And now it won't even boot up even after pulling the battery, it vibrates 6-7 times.
I am really worried about this, any other ideas??? I will try anything! Thanks for the help

Update! Now the phone just reboot when I do anything period with it plugged in. Just like posted in another thread on this section!
Please any ideas I am very desperate and very sick to my stomach!

Hmmm very strange.
I'm aware from what you were saying on the other thread that you've got an unlocked bootloader and you're wondering what to do on the warranty front.
If you've really tried different combinations of stock and custom firmware and having the same issue I'm tempted to say its a hardware issue.
Many people have returned their unlocked phones with no comeback from HTC some have reported that they have noticed the unlocked bootloader and have issued a motherboard repair as part of the fix because of this.
Although im unsure of the additional cost (if any) i would definitely recommend going through the warranty repair route with HTC. They won't say no and send you back the same broken phone. And who knows, if its a confirmed hardware issue they may just replace it as a goodwill gesture.

Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.

Cabarnacus said:
Other than that I don't have any more ideas.
A nexus support thread has a popular answer referring to the clear storage fix.
http://www.google.de/support/forum/p/android/thread?tid=40f52d29e9c4177e&hl=en
Just make sure you are definitely clearing the storage FROM THE BOOTLOADER before calling HTC. It is the first thing they will make you do before accepting a return anyway.
Click to expand...
Click to collapse
Ok thank you so much sir. I am so glad to hear that I may still have a chance at getting it replaced! It was very fullish of me to unlock it, I know, it is just that I figured it was software and could be fixed by unlocking. It is going to cost me $$$ to get this to the States, but that is life. If I still can't get it to work I will call htc and let you know what they say

Little update here. I cleared storage again and just simply disabled data, I have been using the phone for a couple of hours on work without any problems. Next thong I am going yo yty is another friends 3g similar card and see if it still reboots on that sim, if it does then I am calling HTC.
Also still open to any other ideas you guys may have.

News? Maybe i Hope!

So new update, says security. Well it's 1125.5 MB that's some security anyone know what it is yet?
Of course now I can edit now that's it's too late.

Ok can't edit on app. It's updated and good news is it's 7.1.1. Trouble I had was didn't realize it wasted my straight talk apn settings. New clock font on lock screen. Launcher 3 is totally different check it out is nice. Drag to left for Google now feed :highfive:

This phone is getting no XDA love.

fr4nk1yn said:
This phone is getting no XDA love.
Click to expand...
Click to collapse
I was thinking that right after I posted. Full update and crickets well I knew what I was getting into when I got this phone was hoping that there would still be talk on here about things.

NeWCuLTKiNG said:
I was thinking that right after I posted. Full update and crickets well I knew what I was getting into when I got this phone was hoping that there would still be talk on here about things.
Click to expand...
Click to collapse
I guess without root XDA members don't give a screw.
Fir this phone the other forum is much more active.

What are your thoughts and experiences on the update so far? WiFi seems much faster battery seems just as good.

Just got the update yesterday myself. was excited to see that it was 7.1.1 but got annoyed fast that it broke my admittedly already broken Bluetooth. (wouldn't turn on) But after backing everything up and a little bit of stumbling through the "restore" part of a full reset everything is running great as far as i can tell. I like the new launcher but i don't like that I can't do away with the "most recent" apps thing at the top. i just don't use it and don't wan't it there if I'm not going to use it.

The update broke my phone. Hooray.
**edit** Ok, so updated the phone. I got an error saying Recovery was unreadable, booted in bootloader mode... Rebooted, same thing. Shut off the phone. It recommended to use Software repair from Verizon... So plug in the USB-C, fire up the phone... It boots up to the splash screen and freeezes... Then 10 minutes later, REBOOTS TO RECOVERY?!
So I try and do what I can in recovery, but to no avail. So I reboot it again... And let it go. It bootloops 4-5 times and eventually boots up! So I thought, cool. It's fixed. Nope! I reboot, and I'm back in phone limbo. Stupid POS. :\

So I factory reset... And now the phone is even more broken than before. YAY!!!! This is the worst update ever.

karendar said:
So I factory reset... And now the phone is even more broken than before. YAY!!!! This is the worst update ever.
Click to expand...
Click to collapse
Is this the one you used
https://www.verizonwireless.com/support/knowledge-base-209216/
There is a old version for phones before 2013 and a newer that you can full erase and install fresh

NeWCuLTKiNG said:
Is this the one you used
https://www.verizonwireless.com/support/knowledge-base-209216/
There is a old version for phones before 2013 and a newer that you can full erase and install fresh
Click to expand...
Click to collapse
It's not working with my Surface Book. I'll have to try it from another computer at home... I have a weird behavior when I leave my SIM card and SD card inside the phone on top of that: Once every 3 times I reboot, phone doesn't boot anymore. Getting annoyed with all of this.

karendar said:
It's not working with my Surface Book. I'll have to try it from another computer at home... I have a weird behavior when I leave my SIM card and SD card inside the phone on top of that: Once every 3 times I reboot, phone doesn't boot anymore. Getting annoyed with all of this.
Click to expand...
Click to collapse
Do you have a spare sd sounds like it's going bad or needs to be formatted. If you can I'd wipe everything internal external and fresh install

karendar said:
The update broke my phone. Hooray.
**edit** Ok, so updated the phone. I got an error saying Recovery was unreadable, booted in bootloader mode... Rebooted, same thing. Shut off the phone. It recommended to use Software repair from Verizon... So plug in the USB-C, fire up the phone... It boots up to the splash screen and freeezes... Then 10 minutes later, REBOOTS TO RECOVERY?!
So I try and do what I can in recovery, but to no avail. So I reboot it again... And let it go. It bootloops 4-5 times and eventually boots up! So I thought, cool. It's fixed. Nope! I reboot, and I'm back in phone limbo. Stupid POS. :\
Click to expand...
Click to collapse
Remove your sim car tray before boot, guess the update doesn't like our CA network (had the same issue, but did it again when I plugged it to charge this after noon)

NeWCuLTKiNG said:
Do you have a spare sd sounds like it's going bad or needs to be formatted. If you can I'd wipe everything internal external and fresh install
Click to expand...
Click to collapse
Other threads say it's an issue with Samsung SD cards (Which I have). Whenever I boot without it, everything is fine... Problem is I still can't restore from the Software assistant app, all I can do is factory reset from recovery.

Anyone here have a Moto Z force Droid and has 7.1.1 installed? Also will need knowledge of using adb shell and linux command to dump partitions (dd). My phone is in dire need of help. :\ Thanks!
---------- Post added at 06:35 PM ---------- Previous post was at 06:00 PM ----------
And for anyone who hasn't upgraded, can you use the method here to capture the OTA URL:
https://www.androidsage.com/2016/01...pture-ota-update-url-for-your-android-device/

karendar said:
Anyone here have a Moto Z force Droid and has 7.1.1 installed? Also will need knowledge of using adb shell and linux command to dump partitions (dd). My phone is in dire need of help. :\ Thanks!
---------- Post added at 06:35 PM ---------- Previous post was at 06:00 PM ----------
And for anyone who hasn't upgraded, can you use the method here to capture the OTA URL:
https://www.androidsage.com/2016/01...pture-ota-update-url-for-your-android-device/
Click to expand...
Click to collapse
What about a trip to Verizon or talk to moto

karendar said:
Other threads say it's an issue with Samsung SD cards (Which I have). Whenever I boot without it, everything is fine... Problem is I still can't restore from the Software assistant app, all I can do is factory reset from recovery.
Click to expand...
Click to collapse
Did it fix the Bluetooth issue (what was your annyway?)
Me 2 since start of July, I got nothing but trouble with wireless... A very bad 2,4gz reception, no more 5gz visible, and no Bluetooth...
As for Verizon assistant, did you manage to make it work ? I think I'll give it a try...
---------- Post added at 01:12 AM ---------- Previous post was at 12:39 AM ----------
Mr.roots said:
Did it fix the Bluetooth issue (what was your annyway?)
Me 2 since start of July, I got nothing but trouble with wireless... A very bad 2,4gz reception, no more 5gz visible, and no Bluetooth...
As for Verizon assistant, did you manage to make it work ? I think I'll give it a try...
Click to expand...
Click to collapse
After reading on Verizon website, I just realized that it takes up to a week after an update before you can use the assistant...
I also paid a premium for that samsung micro SD 128gb Evo... But also hope it can fix our z force droid Bluetooth issues...
Can't wait to see if the assistant can fix it (do you think a re-install without the SD card can change something ?)

NeWCuLTKiNG said:
What about a trip to Verizon or talk to moto
Click to expand...
Click to collapse
Long trip to go across the border for Verizon... (I don't have a Verizon account) and Moto is a last resort if the software assistant can't fix my issue.

Anyone else noticing improved battery life after the update? I did a full factory reset after the update because it broke my Bluetooth but its been running great for me. Today might just be a fluke so ill keep a close eye over the next few days but so far it seems to be doing better with idle drain and drain with light usage.(web browsing, music, pictures, ect.)

jetman36 said:
Anyone else noticing improved battery life after the update? I did a full factory reset after the update because it broke my Bluetooth but its been running great for me. Today might just be a fluke so ill keep a close eye over the next few days but so far it seems to be doing better with idle drain and drain with light usage.(web browsing, music, pictures, ect.)
Click to expand...
Click to collapse
I didn't get your luck, since the first small update in beginning of July, nothing but trouble, phone overheat (huge drain) reboots often (more drain) and weird unused app battery usage... Since August update, no improvement same thing...
I used to be able to make 2 days or a little more if I'm lucky... Now barely a day... ?

5.6 update bricked my Fire Tablet 7 5th Gen

Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.

CaptainPatterson said:
Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.
Click to expand...
Click to collapse
Yes - I have (indirectly) seen this on numerous unrooted Amazon Fire devices from several generations following a major OTA update. In most cases the device is NOT recoverable unless the bootloader is unlocked (not possible on 5th-7th gen devices). Boils down to a borked update which is not totally unexpected given the manner in which they are engineered and administered by Amazon. Clearly a very high percentage work without issue. Still sucks if you're a member of the substantial minority...regardless of size. You can try giving Amazon support a call...they might throw you a coupon that can be used against a future purchase (including deeply discounted Amazon/Fire devices during "Black Friday" week).

Just an update on this...
After a few days of not being able to use it I powered it on for the umpteenth time and it properly went through factory reset mode. I was able to manually download the 5.6 update again and it is finally back to normal. Funny thing is I now have even less internal storage than before but at least it is working now. That was a huge inconvenience and I still have no clue what happened.

STOP - Read before doing OTA of Android Pie

I tried an OTA of Android Pie tonight, this was from EE UK.
First the system update couldn't verify, so I had to hard power off the phone, on powering on it re-installed and loaded up.
I unlocked the phone from the lock screen and it went to "Android Starting" and after a few moments rebooted.
Now the phone loads up but I can't unlock it, I just get constant PIN incorrects. It's a software issue because you never get to the limit of pin attempts, or the forgotten password option.
Contacted Sony, they've heard of it numerous times today, can't do anything about it.
They'll tell you to use Sony Companion to backup and restore, which you can't do unless the phones unlocked. So basically demand a full reset all data lost.
Update at your own risk, maybe consider removing device pin before the update if you can.

Same problem here in France.
There's a thread on talk.sonymobile: https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Can-t-access-phone-after-updating/td-p/1351581/page/2
So far no working solution.
The french sonyxperia twitter account is also useless.

No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...

zwan33 said:
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
Click to expand...
Click to collapse
backup ur photos/videos and make a factory reset, everything works flawlessly for me.

rideti.me said:
So basically demand a full reset all data lost.
Click to expand...
Click to collapse
It's a painful lesson, but backing up everything before doing anything is a must, even when doing something like an OTA update which you expect to work. I'm just waiting for a customized UK ftf to become available and will be doing a complete wipe which alleviates any unforeseen conflicts.

I had full backup, the corruption was in the pincode, therefore encryption control is lost. The backups are encrypted, I've recovered apps, messages, contacts etc.... But none of the appdata was recoverable without de-crypt.

I feel lucky: I used the repair function because I did not want to have all those small issues usually coming with a big OTA update. I did not expect such a big problem though.
Not to shove it in the face of all the people having this annoying issue, but I can confirm that with a fresh install everything is smooth and I haven't experienced any "big" bug as of yet. The phone seems even faster than with Oreo.
To be honest, besides the long process to reactivate the app of my bank, I don't even mind resetting all my apps every now and then, I noticed that it preserves battery life and performances. But I do understand that this may not be an option to some of you...

TechIntrigue said:
Just curious, why wait for the customized UK version? Does that have any benefits over the other firmware releases?
Click to expand...
Click to collapse
TBH, I'm not so sure, about either. Having read yesterday that the Singapore fw only has the Amazon app as bloat I'm going to install it today.
EDIT: Going back to Oreo as Substratum doesn't work without root.

Has anyone affected managed to do a full reset ?