Database Develop

[Help needed!] L09C635B361 can't update via either OTA or TWRP.

Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.

Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck

xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.

One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?

On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?

The screenshot for the 3 zip files.

oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.

lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:

Can you switch from CE1 to customUK without losing data?

I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?

Tron510 said:
I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?
Click to expand...
Click to collapse
You can flash new firmware without loosing your data. Use Xperiafirm to download the firmware of your choice. If you are looking for UK firmwares to flash, I would go with '1310-6856 Customized UK' as this is unbranded and you won't get any carrier bloatware in it.
Unpack newflasher into the same folder as the firmware. If you don't want to loose your data remove userdata_XFLASH.sin. Then start newfalsher.
I don't think OTA updates will work as you're in the worng region, but I'd be happy if someone corrected me on that.
I would hold off flashing until the new 47.1.A.5.51 is available for UK Customized, it should be any day now.

yip im on UK Customized, and its taking ages for the rollout to happen, but I think i will just wait as I found that when I changed regions before . The region that I switched to got rolled out at a different time the next rollout out.
I guess sony change the regions for very release.
OTA will work for you i.e you will get the UK Customized OTA if your in the states.

billbond4 said:
yip im on UK Customized, and its taking ages for the rollout to happen, but I think i will just wait as I found that when I changed regions before . The region that I switched to got rolled out at a different time the next rollout out.
I guess sony change the regions for very release.
OTA will work for you i.e you will get the UK Customized OTA if your in the states.
Click to expand...
Click to collapse
Thanks,
and it shouldn't undo the us oem fix from before?

Nope, it will stay on whatever region your using currently

Tron510 said:
I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?
Click to expand...
Click to collapse
I called Sony and asked them this question. "If I buy a UK phone from England and use it in the US, will updates take away the fingerprint sensor?" This was the answer, "No. If you install Sony Xperia Companion to your computer and do your updates that way, it will always update to UK version specs."

Hi, i would like to do a flash from UK/HK rom to CE1. Is there risky regarding TA or anything else ? Could i loose my camera and fingerprint usage ?
Thx
Sent from my G8441 using XDA-Developers Legacy app

zegoo said:
Hi, i would like to do a flash from UK/HK rom to CE1. Is there risky regarding TA or anything else ? Could i loose my camera and fingerprint usage ?
Thx
Sent from my G8441 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The answer to your question is 5 posts up
& no you won't loose your TA keys

Oops !
Thx a lot, not seen...
Sent from my G8441 using XDA-Developers Legacy app

zegoo said:
Oops !
Thx a lot, not seen...
Sent from my G8441 using XDA-Developers Legacy app
Click to expand...
Click to collapse
and you do continue to get OTA updates of the region/brand you flashed.

After using newflasher to update to customized DE 47.1.A.7.1 saving my userdata with no problems, i decided to update to the newest 47.1.A.8.49 using the same method, and am having a few problems. first, when i startup, memory app and software update both have errors and stop. then settings have weird characters instead of %s.
I tried flashing back to .7.1 but went into a bootloop.
I flashed back to .8.49 and it works, but still has those problems that initally made me try flashing back to .7.1
Any ideas?
thanks

wonder if i'm doing something wrong when trying to preserve user data.. i'm trying to go from CustomUK (my phone is on 47.1.A.2.374) to Custom CE1 (which is on A.8.49). i downloaded the firmware files via XperiFirm, and removed the user data.sin file. I also replaced the OEM.sin file with the US version, then used newflasher. but my phone gets stuck in a boot loop, and i have to resort to wiping user data.

Tron510 said:
After using newflasher to update to customized DE 47.1.A.7.1 saving my userdata with no problems, i decided to update to the newest 47.1.A.8.49 using the same method, and am having a few problems. first, when i startup, memory app and software update both have errors and stop. then settings have weird characters instead of %s.
I tried flashing back to .7.1 but went into a bootloop.
I flashed back to .8.49 and it works, but still has those problems that initally made me try flashing back to .7.1Any ideas?
Click to expand...
Click to collapse
I did the same, flashed the DE 47.1.A.7.1, it worked perfectly. Then last night I got an OTA update via 'sony update' on my phone. I let it do it's thing and it's been working fine ever since. Perhaps go back to 7..1 and let Sony update it?
itspoots said:
wonder if i'm doing something wrong when trying to preserve user data.. i'm trying to go from CustomUK (my phone is on 47.1.A.2.374) to Custom CE1 (which is on A.8.49). i downloaded the firmware files via XperiFirm, and removed the user data.sin file. I also replaced the OEM.sin file with the US version, then used newflasher. but my phone gets stuck in a boot loop, and i have to resort to wiping user data.
Click to expand...
Click to collapse
Pretty sure it would have worked if you had just removed the userdata.sin. I moved from different firmware & region using this method and it worked fine. I don't know what OEM.sin does, but mixing them up from different regions is probably the issue.

The attached screen shot shows some of the text errors in my update. Anyway to fix this kind of stuff?
Thx

this explains why i couldn't flash back to .7.1.

I'm on Customized UK .2.374 with the US OEM file. It's a US model on Cricket Wireless. So far I haven't been notified of any OTAs, even after checking in settings several times over the last few days, but Xperifirm shows .5.51 as being available for Customized UK. Based on the replies in this thread, it sounds like I'm supposed to get the UK OTA, but it hasn't shown up yet.
Has anyone in the US on the UK firmware with US OEM file actually seen an OTA yet? Ideally I'd like to keep getting OTAs and avoid flashing every update...
(This would be so much less painful if Sony had just enabled the fingerprint scanner in the US...)

Have you tried with the Xperia Companion on a PC?

Didgesteve said:
Pretty sure it would have worked if you had just removed the userdata.sin. I moved from different firmware & region using this method and it worked fine. I don't know what OEM.sin does, but mixing them up from different regions is probably the issue.
Click to expand...
Click to collapse
I have a US model XZ1C and had to copy the US model OEM.sin file when flashing to the CustomUK firmware.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
jrbmed08 said:
I'm on Customized UK .2.374 with the US OEM file. It's a US model on Cricket Wireless. So far I haven't been notified of any OTAs, even after checking in settings several times over the last few days, but Xperifirm shows .5.51 as being available for Customized UK. Based on the replies in this thread, it sounds like I'm supposed to get the UK OTA, but it hasn't shown up yet.
Has anyone in the US on the UK firmware with US OEM file actually seen an OTA yet? Ideally I'd like to keep getting OTAs and avoid flashing every update...
(This would be so much less painful if Sony had just enabled the fingerprint scanner in the US...)
Click to expand...
Click to collapse
I was in the same boat. I was on the CustomUK firmware with US OEM file, and after I saw Xperifirm update to .5.51, i never saw it update via OTA on my phone. Ended up flashing to the Customized CE1 version since that is up to date on .8.49

itspoots said:
I have a US model XZ1C and had to copy the US model OEM.sin file when flashing to the CustomUK firmware.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
I was in the same boat. I was on the CustomUK firmware with US OEM file, and after I saw Xperifirm update to .5.51, i never saw it update via OTA on my phone. Ended up flashing to the Customized CE1 version since that is up to date on .8.49
Click to expand...
Click to collapse
Thanks. Do you think it's because we're not on a UK carrier or because of the hybrid firmware from flashing the US OEM file?
Anyone else on the same setup...please let us know if you're also not getting OTAs.

jrbmed08 said:
Thanks. Do you think it's because we're not on a UK carrier or because of the hybrid firmware from flashing the US OEM file?
Anyone else on the same setup...please let us know if you're also not getting OTAs.
Click to expand...
Click to collapse
The OTA's are checked based on a combination of the parameters found in the OEM partition and the system partition.
Specifically these found in the /oem/system-properties/cust.prop file:
ro.semc.version.cust=1310-4371
ro.semc.version.cust_revision=R8B
And these in the /system/etc/prop.default file:
ro.semc.version.sw=1307-7511
ro.semc.version.sw_revision=47.1.A.2.324
It builds a web query from the parameters like this:
http://fuas.sonymobile.com/fuas/services/updates?cdfId=CUST&cdfVer=CUST_REVISION&channel=cable&clientName=Xperia%20Companion%20Win&clientVersion=1.7.2.0&devId=IMEI&lang=en-US&model=G8441&securityState=HWC_Yoshino_Com_001&swId=SW&swVer=SW_REVISION&tac_mc=NO_IDEA&updateFormat=image
You can see the complete URL for your phone in the Xperia Companion logs.
Just look for a line starting with: http://fuas.sonymobile.com
So although you have an older SW_REVISION, if it's newer than the firmware available for CUST then a firmware update isn't offered.
What this means is that Sony is providing OTA's that are essentially based on your OEM region and the US region only has version 47.1.A.2.324 available.
So if you have newer firmware than that, you aren't offered the update.
This also means that if you are offered an update, it will be the US version of the OTA which may cause problems when it tries to patch binaries from a different region's partition.
I haven't been able to get my hands on any OTA files yet, so I don't know what's in them or probability of an OTA breaking a phone with mixed region firmware bits.

How to force update to v. 47.2.A.2.33

Hi,
I have received an email notification from SONY stating that there was an update available for my device (v. 47.2.A.2.33) and described a few ways to proceed with the update - however, none worked. All methods stopped right in the beginning stating "no updates available".
SONY support could not help, either. They were asking me for patience until the update reaches me and I will be notified - but I had already been notified...
Anyway, is there a way to bypass the waiting line and force-get the version now, instead of waiting (who knows for how long)?
The device is an operator-free version, so I am not tied to any vendor mercy.
Thank you.
Kind regards,
Csani

Just use Xpericheck to download the firmware version you want. Then use NewFlasher to flash it.
No need to rooting, unlocked bootloader or anything fancy.

Csani said:
is there a way to bypass the waiting line and force-get the version now, instead of waiting (who knows for how long)?
Click to expand...
Click to collapse
Just upgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.2.A.4.45 buld that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason. Customised version is a good option as doesn't contain any provider bloatware. My choice would be Customized DE.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.

Can somebody tell me EXACTLY (or give me the link for it) the explanation of what's the difference between a regular stock rom and its Customised DE counterpart? It was my understanding deleting pre-installed apps like Facebook or Spotify (not just disable them) was impossible, flashing customised roms solves the problem?

Dany XP said:
Can somebody tell me EXACTLY (or give me the link for it) the explanation of what's the difference between a regular stock rom and its Customised DE counterpart? It was my understanding deleting pre-installed apps like Facebook or Spotify (not just disable them) was impossible, flashing customised roms solves the problem?
Click to expand...
Click to collapse
Customized DE is a regular stock rom. It just means that it's meant for the German market and not tied to any operator like Vodaphone etc. Customized UK would be for the UK market and so on.
There's not much difference between the customizations (although operator specific ones probably won't work with other ones and you shouldn't flash them). Some don't have all the features (US might not have fingerprint sensor enabled, some don't have VoLTE...). All have some preinstalled apps (or bloatware if you wish) mut the actual apps might vary - some have more, some less and some just ha e different useless **** instead of other.
So the "Customized xx" here refers to stock rom, not a custom rom. You can flash any Customized x for your phone even with a locked bootloader but "Custom ROM" like LineageOS or AOSPExtended would need an unlocked bootloader.
Also if you want to remove the bloatware completely you'll need root (and unlocked bootloader). But before you do that, please back up TA and read carefully about how it changes your phone in ways that can't be reversed.

Is there any other place to download the .ftf file?
Xpericheck.com redirects me to alfafile.net but I don't have premium account and cannot download the file

jelenn said:
Is there any other place to download the .ftf file?
Xpericheck.com redirects me to alfafile.net but I don't have premium account and cannot download the file
Click to expand...
Click to collapse
Pretty sure flashtool can make one from the files you download from Xperiafirm

Worked, thanks

vofferz said:
Customized DE is a regular stock rom. It just means that it's meant for the German market and not tied to any operator like Vodaphone etc. Customized UK would be for the UK market and so on.
There's not much difference between the customizations (although operator specific ones probably won't work with other ones and you shouldn't flash them). Some don't have all the features (US might not have fingerprint sensor enabled, some don't have VoLTE...). All have some preinstalled apps (or bloatware if you wish) mut the actual apps might vary - some have more, some less and some just ha e different useless **** instead of other.
So the "Customized xx" here refers to stock rom, not a custom rom. You can flash any Customized x for your phone even with a locked bootloader but "Custom ROM" like LineageOS or AOSPExtended would need an unlocked bootloader.
Also if you want to remove the bloatware completely you'll need root (and unlocked bootloader). But before you do that, please back up TA and read carefully about how it changes your phone in ways that can't be reversed.
Click to expand...
Click to collapse
So in customized I still have facebook, Spotify and all that crap? Too bad

Dany XP said:
So in customized I still have facebook, Spotify and all that crap? Too bad
Click to expand...
Click to collapse
Yes. And you probably have the "Customized xx" rom already on your device (unless you have an operator specific ROM).

XZ1 comapct roll back from Pie to Oreo and save personal data & apps

Hello,
Is there a way to roll back to Oreo from 47.2.a.4.45 (Pie) saving all personal data and apps untouched?

SonyVLT25ISonyVLT25I said:
Hello,
Is there a way to roll back to Oreo from 47.2.a.4.45 (Pie) saving all personal data and apps untouched?
Click to expand...
Click to collapse
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.1.A.16.20 build that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.

Didgesteve said:
Just downgrade it yourself, you won't damage the phone or change your warranty status.
Look on Xperiafirm and find a 47.1.A.16.20 build that is for your region, although any EU region would be fine, US versions have fingerprint and VoLTE disabled for some reason.
Download Newflasher and put it in the same folder as the firmware you downloaded from Xperiafirm
Delete Userdataxxx.sin and files ending in .ta . This will ensure that you don't lose any personal data. Also delete persist*.sin to avoid losing android attest key.
Then start newflasher.exe and follow instrctions.
You might need a copy of the Sony driver
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
Click to expand...
Click to collapse
Sorry if I'm being too annoying and big thanks for helping me out.
Just to confirm once more. To insure that a personal data, installed apps and apps' data/cache remains intact after rolling back to Oreo from Pie I need to delete these files prior to flashing old firmware:
All files with ".ta" extention
Userdata.sin
Appslog.sin
Diag.sin
Qnovo.sin
Ssd.sin
Persist.sin (especially this one to keep SOMC FIDO Key & SOMC Attest key )
Is it correct, or I missed something?

Didgesteve said:
I would make a backup with Xperia transfer before you do anything, if the phone is glitchty after your rebuild, then factory reset it and then restore from the backup.
Click to expand...
Click to collapse
Too bad I'm unable to start any in-phone app (except settings) right now, as the desktop is stuck on "Phone is starting...", probably because of Substratum themes (like you've answered in other post).
Also when I am connecting the phone to PC and starting Companion, it says that my phone is locked and I need to unlock it with password or fingerprint, but the thing is it is unlocked... I have tried to disable the password through settings, but upon password confirmation I cannot get to the next screen, there is no transition...

SonyVLT25ISonyVLT25I said:
Sorry if I'm being too annoying and big thanks for helping me out.
Just to confirm once more. To insure that a personal data, installed apps and apps' data/cache remains intact after rolling back to Oreo from Pie I need to delete these files prior to flashing old firmware:
All files with ".ta" extention
Userdata.sin
Appslog.sin
Diag.sin
Qnovo.sin
Ssd.sin
Persist.sin (especially this one to keep SOMC FIDO Key & SOMC Attest key )
Is it correct, or I missed something?
Click to expand...
Click to collapse
I'll be honest when I used Newflasher I didn't bother with any of the .ta files, just Userdataxxx.sin and Persist.sin, I don't knon what the .ta files do and it didn't make any difference to me, I got prefect flash, no loss of data. I copied the .ta files instructions from someone else, I can't find the original thread now, but I don't think you delete all of them, espesially not the one in the boot folder.

Is there a way to backup all data with other software other than Companion?

Didgesteve said:
I'll be honest when I used Newflasher I didn't bother with any of the .ta files, just Userdataxxx.sin and Persist.sin, I don't knon what the .ta files do and it didn't make any difference to me, I got prefect flash, no loss of data. I copied the .ta files instructions from someone else, I can't find the original thread now, but I don't think you delete all of them, espesially not the one in the boot folder.
Click to expand...
Click to collapse
So no need to delete "Appslog.sin", "Diag.sin", "Qnovo.sin", "Ssd.sin"? Just delete "Userdata.sin" and "Persist.sin" and all ".ta" files from Root directory?

SonyVLT25ISonyVLT25I said:
So no need to delete "Appslog.sin", "Diag.sin", "Qnovo.sin", "Ssd.sin"? Just delete "Userdata.sin" and "Persist.sin" and all ".ta" files from Root directory?
Click to expand...
Click to collapse
Yes, that will get you downgraded without losing your data

Didgesteve said:
Yes, that will get you downgraded without losing your data
Click to expand...
Click to collapse
Flash complete. Now my phone reloading after Maintenance sign (the one with a screwdriver), nothing else happens :crying::crying::crying:

SonyVLT25ISonyVLT25I said:
Flash complete. Now my phone reloading after Maintenance sign (the one with a screwdriver), nothing else happens :crying::crying::crying:
Click to expand...
Click to collapse
Try reflash, but take out nothing but the two .sin files, ignore the .ta files. That worked for me.

Took out from firmware root directory files: "persist_X-FLASH-ALL-C93B.sin" and "userdata_X-FLASH-CUST-C93B.sin" and flashed once more. Same thing.
Firmware folder with Newflash looks like on the screenshot in the attach

So I have flashed back to Pie 9 again, my phone started up, I'm again stuck at "Phone is starting..." screen and Companion says that my phone is locked.

SonyVLT25ISonyVLT25I said:
Took out from firmware root directory files: "persist_X-FLASH-ALL-C93B.sin" and "userdata_X-FLASH-CUST-C93B.sin" and flashed once more. Same thing.
Firmware folder with Newflash looks like on the screenshot in the attach
Click to expand...
Click to collapse
Did you do a backup with Xpria Transfer?
Try and download the firmware again perhaps the original download was corrupted. Also, try to flash without taking out Userdata, perhaps there is something that is not backwards compatable. Although I'm sure there would have been reports on the forum if that was the case
Then restore with X Transfer.
If all else fails use Xperia companion to repair your phone.

Didgesteve said:
Did you do a backup with Xpria Transfer?
Try and download the firmware again perhaps the original download was corrupted. Also, try to flash without taking out Userdata, perhaps there is something that is not backwards compatable. Although I'm sure there would have been reports on the forum if that was the case
Then restore with X Transfer.
If all else fails use Xperia companion to repair your phone.
Click to expand...
Click to collapse
Unable to use Xperia Transfer, as the phone is stuck on "Phon is starting...", unable to get to apps. Even after pushing alternative Launcher through ADB.
Unable to fix through Xperia companion, as it says that my device is locked and I need to use a fingerprint, while it is unlocked. :crying::crying::crying:

SonyVLT25ISonyVLT25I said:
Unable to use Xperia Transfer, as the phone is stuck on "Phon is starting...", unable to get to apps. Even after pushing alternative Launcher through ADB.
Unable to fix through Xperia companion, as it says that my device is locked and I need to use a fingerprint, while it is unlocked. :crying::crying::crying:
Click to expand...
Click to collapse
You have to make the Xperia transfer backup at the begining before you start, it's too late now.
I'd say the only thing you can try is to flash again and wipe the phone. Don't delete Userdata and let the phone factory reset.

I think it would be plausible to assume that going back to previous version would need a factory reset as there could be a vulnerability in an older fw that could let people gain control and access the data without a proper password (or something).
Also j4nn mentions the necessity of flashing userdata when downgrading to a firmware where gaining temp root is possible on the TA backup thread.

Downgrade without data loss?

Hi all,
Is it possible to downgrade to previous version, without data loss. Because battery backup is worst. Before this new update, I used get 3 days backup. now its less than 2 days. I am not a gamer.

srk_srinivas said:
Hi all,
Is it possible to downgrade to previous version, without data loss. Because battery backup is worst. Before this new update, I used get 3 days backup. now its less than 2 days. I am not a gamer.
Click to expand...
Click to collapse
I can't say for sure as I've never done it.... But here's the info from Asus website
'Version Android 10 downgrade to P (WW) 2020/03/162.22 GBytes
ROG Phone II Software downgrade from Android 10 to Android 9 for WW SKU only*
*Please follow steps and ensure to backup data before downgrade.
Steps of Update:
1.Download the patch pack.
2.The system will detect new firmware.
3.After executing the patch, the system will reboot once.
4.When the system boot on, the firmware version will be recover to Android P.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
*System upgrade may cause part of data missing, please backup your important data before system upgrading.'
It's not very clear about whether you will be factory reset or not - it just says you may lose part of your data. Backup as much as you can 1st.
However, 1) are you on the latest 2009.49 build? 2) If you are already, how long is it since you updated? 3) Also, are you rooted with magisk? 4) Although you used to get 3 days use, do you know how much screen-on-time and idle time approximately that you used to do over those 3 days?
1)+2) If you have only just updated, you need to allow a good few days for the update to 'settle' in. Then judge the battery life once it's settled. For me (I also don't really game - I only play non-demanding Bike Race several times per day) I'm getting a pretty consistent 9 hours screen-on-time with wifi/bluetooth/data etc always enabled and no extra battery tweaks, which I think is pretty good.
3) If you are rooted with magisk/magisk manager installed, check under magisk hide that Google services isn't hidden. This can cause a certain degree of extra consumption, probably not a vast amount, but it's for sure higher with Google stuff hidden.

Use raw file with pc
But backup always recommended!

Thanks for the replies. I will try and let you know.

srk_srinivas said:
Thanks for the replies. I will try and let you know.
Click to expand...
Click to collapse
If you use the downgrade to pie method provided by asus it will format your data.

shahram Ali said:
If you use the downgrade to pie method provided by asus it will format your data.
Click to expand...
Click to collapse
Thanks for the advise, I will try next week after taking backup. Is there any alternative way to downgrade?

srk_srinivas said:
Thanks for the advise, I will try next week after taking backup. Is there any alternative way to downgrade?
Click to expand...
Click to collapse
Just download the raw(stock rom without data wiping) Version that you want to downgrade and all will be good hopefully thanks to asus that we ain't stuck at new bootloaders xD

shahram Ali said:
Just download the raw(stock rom without data wiping) Version that you want to downgrade and all will be good hopefully thanks to asus that we ain't stuck at new bootloaders xD
Click to expand...
Click to collapse
Hi, may I ask where did you download the down grade RAW firmware without wiping data? I also need it. Which versions did you down grade from and to? Thanks.