Just manually updated to build QD1A.190821.014 Face Unlock was working fine before uodating now it won't let me Unlock for the life of me. I can still register my face just can't do the actual unlocking with it. It says Can't verify face Everytime.
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Falargi said:
I am having the same problem. This issue started after I flashed the November image. Would that be a problem caused by magisk?
Click to expand...
Click to collapse
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
RLKirk said:
I'm not sure. I rooted it as soon as I flashed it. Maybe I will unroot it when I have more time and see what happens.
Click to expand...
Click to collapse
That's exactly what I did too. Let me know how it goes. I'll probably do the same.
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
This happened to me. The .007.A3 flash fixed it.
murphyjasonc said:
When you flashed the November Image did you flash the correct one? As in you said you flashed the .014 version but was that the version you were on before? I have seen several posts where people were on the .007 and flashed the .014 or vis versa and it borked the face unlock. From what I have seen if you were on one of the other images you should be able to flash say the .007 version and it will fix the issue. If you are not sure which version you were on before it wouldn't hurt to try.
Click to expand...
Click to collapse
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Falargi said:
I will try that. Thanks.
Should I go back to October and then flash November image then?
Sorry... Noob here
Click to expand...
Click to collapse
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
RLKirk said:
Yeah I was definitely on 007 before. I flashed 014 just assuming it was the newest so it would stop bugging me about the failed update. Where do I remove the -W at?
Click to expand...
Click to collapse
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
murphyjasonc said:
You edit the flash-all.bat file. The -w will be towards the end. Just delete it and save. Make sure you keep only one space between each word when you remove it. If the spacing is wrong it will fail. Then you can click on the file to flash like normal without wiping.
Click to expand...
Click to collapse
Cool thanks dude
murphyjasonc said:
You should be fine flashing the .007 image over the .114. I know it will work if you clean flash by leaving the -W in. It should work taking the -W out. That just basically wipes all user data.
Click to expand...
Click to collapse
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Falargi said:
It worked. Since I'm on T-Mobile I thought I would take .014, I guess I was wrong. Face unlock working again...
Thanks a lot.
Click to expand...
Click to collapse
Glad I could help. :good:
I sent my Pixel 4 XL back in for a warranty replacement because of this issue. I wasn't sure if it was hardware related or not. Didn't want to take a chance on it being a hardware defect. I was on the November security update. I updated it as soon as I set up my phone so I didn't have a chance test it out on the October update.
murphyjasonc said:
Glad I could help. :good:
Click to expand...
Click to collapse
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
https://support.google.com/pixelphone/thread/21769134?hl=en/
Falargi said:
I'm having the same issue again.
Just flashed December image. I flashed .016A1.
Which the correct image for me?
I wish Google could make this easier.
Click to expand...
Click to collapse
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
murphyjasonc said:
Which image were you on before? Google isn't making it easy this time around. You flashed the image for Japan and Taiwan. Depending on your carrier you should flash either the 011 or the 012.A1. Here is what Google support says
Pixel 4 (XL):
T-Mobile, Fi, EMEA: QQ1B.191205.011
Japan & Taiwan: QQ1C.191205.016.A1
All other carriers: QQ1B.191205.012.A1
There is a bug with the December image also. If you flash the December image with the -W doing a complete wipe face unlock will not work. If you remove the -W and upgrade from November it will do like it should. That was my experience anyway. If you did happen to wipe your phone on the December image you will have to flash the November image with the -W. Set your phone up again and the flash the December image without the -W and it will be fixed.
Click to expand...
Click to collapse
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Falargi said:
I was on .007.A3 (November) but I'm on T-Mobile.
I will try fishing November again and do as you said.
Thank you
Click to expand...
Click to collapse
I think your best bet is to flash the 011 image. I would try flashing it first with the -W removed. You might get lucky and save yourself some time. If that doesn't work then flash November again and go from there.
Is this issue related to root? I had a fresh install with the latest December patches (qq1b.191205.011) that did not work with Face Unlock. However, that attempt was also rooted in the typical fashion with Magisk. After performing a full re-install of qq1b, I was able to use Fack Unlock normally. I'll re-apply root later today and let you know if that was the tipping point.
Related
Based on the updates shown at Sprint (Phone Carrier in the USA), the Android 5.0.1 update (15 December 2014) should be released today for the Nexus 5
Let us hope it will solve many of our issues since the Lollipop update.
Source : http://support.sprint.com/support/a...AndUpdateTheSoftwareVersionOnYourGoogleNexus5
Let's hope that's true!
They gave a clear shot at the date of 5.0. I hope they are right again.
F5 F5 F5 F5
https://developers.google.com/android/nexus/images
markp99 said:
F5 F5 F5 F5
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
This time I'll wait for the OTA. Configure everything again is something boring.
ReeSilva said:
This time I'll wait for the OTA. Configure everything again is something boring.
Click to expand...
Click to collapse
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
BRiANj64 said:
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
Click to expand...
Click to collapse
I've heard about, but always exists a fear that it don't works |smile|
BRiANj64 said:
You know that you can remove the -w from the flash-all .bat or .sh to not remove any user data?
Click to expand...
Click to collapse
FYI.. removed that -w when flashing my nexus 7.. did nothing, it wiped everything anyway
orthonovum said:
FYI.. removed that -w when flashing my nexus 7.. did nothing, it wiped everything anyway
Click to expand...
Click to collapse
This is what Im talking about.
Don't just remove -w
Open up the .zip and remove userdata.img from it.
Of course this only works if you leave your bootloader unlocked. I leave mine locked for security. Don't want someone getting my data if I lose my phone, force them to wipe to unlock it.
Flashing userdata wipes your sdcard ya noobs
ReeSilva said:
This time I'll wait for the OTA. Configure everything again is something boring.
Click to expand...
Click to collapse
Same here since it only took 2 days to get it on my nexus 7.
Pezmet said:
Same here since it only took 2 days to get it on my nexus 7.
Click to expand...
Click to collapse
Nexus 5 5.0.1 image not posted yet on the Google firmware page. Last years Moto G does have 5.0.1 though
Same here I'll wait for the OTA this time around rather flash the image, basically because i can't be bothered flashing
gee2012 said:
Nexus 5 5.0.1 image not posted yet on the Google firmware page. Last years Moto G does have 5.0.1 though
Click to expand...
Click to collapse
Yes the reasons of the delay are weird since it is the same build name, hence no later fixes should be there so the wait was kind of useless.
ixon2001 said:
Same here I'll wait for the OTA this time around rather flash the image, basically because i can't be bothered flashing
Click to expand...
Click to collapse
5.0.1 OTA for the Nexus 10 was only 8,4MB, so don`t expect too much.
I'll wait for the ota. I can't be bothered to flash again.
Pls pls just update the radio to powerhog on 4G
It takes less than a minute to Fastboot flash system, boot and radio(in case we get a new one). Not sure why all the drama.
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little odd that it says this after using Mofoverify is all. (See picture below)
GreaterLesser said:
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little old that it says this after using Mofoverify is all. (See picture below)
Click to expand...
Click to collapse
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Official for me
GreaterLesser said:
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little old that it says this after using Mofoverify is all. (See picture below)
Click to expand...
Click to collapse
Hmm, I ran Mofoverify but not Mofo, just like you, and my status didn't change. That's curious for sure.
johnbravado said:
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Click to expand...
Click to collapse
Okay I just wanted to make sure my phone isn't messed up or anything. My nexus 6 still hasn't arrived yet.
cenobite138 said:
Hmm, I ran Mofoverify but not Mofo, just like you, and my status didn't change. That's curious for sure.
Click to expand...
Click to collapse
And now I'm worried again.
johnbravado said:
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Click to expand...
Click to collapse
If you flash it back to stock reboot a couple of times, reboot fastboot a couple of times and let us know if it changed back.
Nope stays: Modified.
Harry44 said:
If you flash it back to stock reboot a couple of times, reboot fastboot a couple of times and let us know if it changed back.
Nope stays: Modified.
Click to expand...
Click to collapse
Did you flash all partitions or just a specific partition?
GreaterLesser said:
Did you flash all partitions or just a specific partition?
Click to expand...
Click to collapse
In system status is says official in bootloader software status is custom
All:
boot
bootloader
gpt.bin
logo.bin
radio
recovery
all the system images.
:crying:
I downgraded to the stock release firmware. Im wondering if O update via the OTA to latest if it will change.
Finally got it back but recovery says qe 0/1
Mine does not say modified after running mofoverify. Nor did it matter whether I entered the bootloader from button-press or adb.
Harry44 said:
In system status is says official in bootloader software status is custom
All:
boot
bootloader
gpt.bin
logo.bin
radio
recovery
all the system images.
:crying:
I downgraded to the stock release firmware. Im wondering if O update via the OTA to latest if it will change.
Finally got it back but recovery says qe 0/1
Click to expand...
Click to collapse
I was worried about that...
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
First flash this file and then Rom. That's right?? Or its other way around
karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..
Wouldn't this procedure downgrade some performance on the device?
Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs
Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk
puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..
snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus
snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk
it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)
I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
I'm no expert on the matter but I had to do a factory reset to get it to work again. Maybe flashing the boot.img from the December update might do it
pwnsicle said:
I'm no expert on the matter but I had to do a factory reset to get it to work again. Maybe flashing the boot.img from the December update might do it
Click to expand...
Click to collapse
Really hope I don't have to do a factory reset. It takes forever to completely set everything up again.
Delete. My old tired eyes missed a part of your post. Carry on lol.
czonin said:
I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
Click to expand...
Click to collapse
You might have the wrong update version installed. This happened to me with the Nov releases. Try flashing a different version. I'm willing to bet it fixes it.
Are you running a custom kernel or stock?
brandon5491 said:
You might have the wrong update version installed. This happened to me with the Nov releases. Try flashing a different version. I'm willing to bet it fixes it.
Click to expand...
Click to collapse
I'm pretty sure you're right. Trying a different version now.
Edit: I was on the wrong version but i've flashed the correct one and re-setup face unlock and it still isn't working.
Alcolawl said:
Are you running a custom kernel or stock?
Click to expand...
Click to collapse
Stock, rooted.
czonin said:
Stock, rooted.
Click to expand...
Click to collapse
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Alcolawl said:
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Click to expand...
Click to collapse
yep had this issue earlier and only factory reset helped.
Alcolawl said:
Unfortunately I've seen this happen to one other person. A factory reset was the only way he was able to fix it.
Click to expand...
Click to collapse
ceelos218 said:
yep had this issue earlier and only factory reset helped.
Click to expand...
Click to collapse
Ya I couldn't find any way to fix it. Ended up having to factory reset and it's all working now.
czonin said:
Ya I couldn't find any way to fix it. Ended up having to factory reset and it's all working now.
Click to expand...
Click to collapse
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
---------- Post added at 10:35 AM ---------- Previous post was at 10:26 AM ----------
tonyfiore75 said:
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
Click to expand...
Click to collapse
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
tonyfiore75 said:
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Same here. Went to factory kernel and all is well.
I had to factory reset to fix this. No flashing stock dtbo, stock boot image, or even reflashing stock factory images worked. Even with the -w I had no face unlock. I had to factory reset again after flashing factory images with the -w flag to fix it. It works now though.
czonin said:
I've had a Pixel 4 XL since launch and just did a fresh install of the December update. Now my face unlock no longer works. I get "Can't verify face. Try again" every time. I've tried deleting face data and setting it up again and numerous reboots. Any ideas?
Click to expand...
Click to collapse
Same thing here. Unlock was working well right up until I flashed the Dec. update. I'm on 191205.012.A1 build for AT&T (my carrier). Stock, rooted, ex kernel. I'm going to try the stock boot image route when I get home tonight. What a PITA.
tonyfiore75 said:
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Which kernel did you switch to? There isn't an EX Kernel thread for the P4 XL (yet) to corroborate and report this. Mentioning @flar2 in hopes he sees this and can look into it.
EDIT: Flashing Kirisakura kernel 2.1.0 restored face recognition using my existing face profile.
v12xke said:
Which kernel did you switch to? There isn't an EX Kernel thread for the P4 XL (yet) to corroborate and report this. Mentioning @flar2 in hopes he sees this and can look into it.
EDIT: Flashing Kirisakura kernel 2.1.0 restored face recognition using my existing face profile.
Click to expand...
Click to collapse
Yup - that's exactly what I did as well. Worked like a charm. I'm waiting to see if another EX Kernel version comes out soon (keeping track on the EX app itself).
tonyfiore75 said:
I'm having the same issue but I think I'd rather live without Face Unlock than have to do a factory reset, re-root, etc. Back to the pattern for me!
---------- Post added at 10:35 AM ---------- Previous post was at 10:26 AM ----------
Never mind. It was Elemental X kernel that broke Face Unlock. I flashed another kernel and Face Unlock is working again. :good:
Click to expand...
Click to collapse
Thanks a lot, tonyfiore75!
Somehow I wanted to do a backup of the stock kernel before flashing Elementalx after flashing Dec 2019 update. Restored and face unlock works again!
wrongway213 said:
I had to factory reset to fix this. No flashing stock dtbo, stock boot image, or even reflashing stock factory images worked. Even with the -w I had no face unlock. I had to factory reset again after flashing factory images with the -w flag to fix it. It works now though.
Click to expand...
Click to collapse
Same thing for me
Flashed Dec update with factory images and it broke face unlock. Had to factory reset through the app settings to get it working again.
I hear that the updated FrankenKernel works. RQ10. https://forum.xda-developers.com/showpost.php?p=81165507&postcount=109
Edit: Look for 10.1 later in the thread. There is a minor update.
Edit: Just read the thread, there is also a 10.3 update!
I'm currently on rooted:
XQ-AT51_Customized UK_1321-7192_58.0.A.0.1040_R8A
Looking to update to:
XQ-AT51_Customized UK_1321-7192_58.0.A.3.31_R8A
What's the best way to do this?
Research seems to suggest delete all .TA files aswell as the userdata file and if that works, to flash an extracted/pactched boot.img that I've already prepped. Though some users mention that they then get a decryption error resulting in the need to fully wipe.
I'd be grateful to hear from anyone who has successfully updated their Xperia 1 ii (with Flashtool or newflasher?).
Many thanks
Bump - anyone successfully updated their rooted firmware yet?
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Montane said:
I assumed by flashing to Customized UK we would still get updates pushed to the phone? I flashed my new device last week to 58.0.A.3.39 and assumed if I wanted to update it'd ask me through my settings. Do I have to manually do this now?
Click to expand...
Click to collapse
Hmm I thought that by being rooted/bootloader unlocked it's messed with the system updates. See attached, as Xperia Assist says there's an update available yet then clicking via Software Update it says I'm up to date.
I'm on 58.0.A.0.1040 customized UK and yet there's 58.0.A.3.39 available via Xperifirm
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Winrahr said:
I updated my AT52 from 3.31 to 3.39 with newflasher. Worked fine. Haven't tried to remove the userdata file to not lose all my stuff though, gonna try that for the next update.
Basically I downloaded with xperifirm and just ran newflasher and went through the prompts, didn't remove any files because I wanted to flash all partitions. Then patched the boot.img from that firmware and flashed through fastboot.
Click to expand...
Click to collapse
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
cd993 said:
Cheers. I'm curious if there's a way to update without wiping data, but I guess a good clean flash is not a bad thing, albeit timely
Click to expand...
Click to collapse
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Winrahr said:
Removing userdata_X-FLASH-CUST-2389.sin from the directory before running newsflasher should be equivalent to a dirty flash. But I've never tried it since this is my first Sony device since the Z1.
Click to expand...
Click to collapse
Thanks yeah I may try that, or just stick to clean flashes
Montane said:
I guess it's a whole new flash then. Backup and go again. Like you said. Timely
Click to expand...
Click to collapse
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
cd993 said:
Thanks yeah I may try that, or just stick to clean flashes
Yup, though a thought is to perhaps get a sd card and use that for most data. Least that way when internal storage gets wiped, the sd card would be untouched. Not been able to do that for a while!
Click to expand...
Click to collapse
Feels good to have an sd card to put all your backups on again doesn't it haha. I will not miss having to back up the internal storage slowly through USB2.0 just in case I have to wipe the entire storage.
I'm going to try a dirty flash on the next firmware update and hopefully I don't soft brick it again. Not having TWRP is new and scary to me.
Bump
With an updated firmware slowly rolling out (the one adding the RAW support and July security update) patch) etc, anyone managed to update when bootloader unlocked and rooted, avoiding losing data?
If I have to do a clean flash it wouldn't be the end of the world but I would love to avoid the hassle of (even with the usage of Swift Backup etc) and little things like not losing my autobrightness settings which have been learning my usage etc
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
YandereSan said:
As others have said, delete the userdata file to make sure that partition isn't erased. I don't think dirty flashing is as a big of a deal as people are making it out to be nowadays.
Just make sure you extract and pre-patch the new boot image with Magisk before you flash.
Click to expand...
Click to collapse
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Newflasher guy gets mad when you talk about anything other than flashing every file so I'll post my update here.
Removed persist.sin and userdata.sin from the 3.88 update and ran through newflasher v33. Booted right back up and lost no data. YMMV.
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
By "rooting" for WiFi calling did you just flash another customization or did you unlock the bootloader? AFAIK there's no reason to root for getting WiFi calling as flashing another firmware is the easiest way.
Montane said:
I'm no pro to all this but I rooted for WiFi calling when I first got the phone. The other day I saw the update for Raw on my phone and updated just fine!?
Click to expand...
Click to collapse
Do you mean to say you received at OTA update notification via the system update option when rooted? Or you did a manual flash via newflasher?
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Montane said:
I'll shutup. I flashed my stock Xp1 ii from O2 XQ_AT51 to enable wificalling for Vodafone etc.
Click to expand...
Click to collapse
If you unlocked your bootloader then you will not be able to take OTAs. You do not need to have bootloader unlocked to flash another stock firmware (ie through flashtool or newflasher). You do need to have bootloader unlocked to obtain root privileges.
cd993 said:
Thanks for the response.
When the time comes I'll certainly give that a go, though will indeed br sure to make a full backup in case.
I'm still hoping for someone to comment confirming this method works as I've read that some users get a decryption error, but I'll give it a go soon and post back ?
Click to expand...
Click to collapse
I unlocked my Xperia 1 II, downloaded the latest raw update from XperiFirm, deleted the userdata file, put the phone into download mode (vol. down + power), flashed via NewFlasher v33.
Phone booted up perfectly fine. Running the latest update and have raw option for all 3 cameras.
The only time your device will wipe is when you first unlock the bootloader. Otherwise, you shouldn't have any issues updating it.