Database Develop

[APP][ROOT] 4.1 +] Xperia Recovery Manager

This is in conjunction of this little project of mine to build and provide twrp recovery images for all the Xperia devices that I own.
To remind everyone in the very first place, I take no credit for the development of TWRP itself, which is all thanks to the great work of Team Win (@Dees-Troy , @bigbiff et al)
The idea of the app was just that to create a means to donate to me in the first place, and since I didn't want to make a "Hello WOrld" app just to get donations, I thought why not make an app that actually does something useful. Back from then, the app has come to gather a lot of features and is a really handy tool.
[QRCODE]https://play.google.com/store/apps/details?id=in.championswimmer.twrpxperia[/QRCODE]
DOWNLOAD FROM PLAY STORE
What does it do ?
This app downloads a TWRP/CWM recovery image for your device and flashes it to the FOTAKernel partition of your phone.
It also allows you to backup the FOTAKernel and restore it or format it. (in case you want to remove TWRP later on)
Dafuq is FOTAKernel ?
FOTAKernel is a partition on XPeria phones which contains a recovery-like bootsystem that is used to perform OTA (over the air) upgrades of your ROM from SONY. (If you have ever upgraded your ROM via the Sony Update Centre on your device, then your device reboots into the fotakernel which flashes the new android version to your phone.
Once bootloader is unlocked, FOTAKernel is of no use anymore as OTA is not supported. It can be very cleverly used now as a pseudo recovery partition of the device.
Which devices are supported ?
Xperia T, V, Z, ZL, Tablet Z (Wifi and LTE both) are currently supported. ***Xperia ZR, SP, Z1 and Z Ultra are supported too now ****
What are the requirements ?
For the app to flash TWRP to FOTAKernel, you just need root and unlocked bootloader. But for TWRP to boot and work, you need to be on a kernel that supports the "extract_elf_ramdisk" method. Almost all kernels for custom ROMs like AOKP/CM/FXP/PAC/AOSPA/Omni have support for this feature. Among stock kernels, DoomKernel supports this. Please ask your kernel developer if FOTAKernel recovery support is present (and demand it to be added if not )
What are the advantages of this method ?
Every time you flash a kernel, the recovery gets changed, because the recovery is present in the kernel. But if we are hotbooting a recovery in the fotakernel partiton, then even after flashing a new kernel (given that it supports extract_elf_ramdisk), your recovery is not changed. Thus even if the kernel's inbuilt recovery is broken, you can continue to use the recovery you have flashed onto your fotakernel.
What if I do not want to (or cannot afford to) buy the app ?
Whatever the app does, can be done manually too using the instructions on this thread
Also the app is completely open source. The sources of the app as well as the sources from which I have built the recovery images are on https://github.com/championswimmer/Xperia_FOTAKernel_Manager_Android_App
Feel free to build yourself a copy from the source. I would appreciate if you do not distribute it though.
I HAZ A PROBLEM WITH DA APP. PLOX FIX IT!!!
Please mention your problem on this thread asap. I will try to fix it. But no promises how soon that will happen. Being a paid app does not mean I will be providing 24x7 support. Again remember, just consider buying the app as donation for my developmental efforts on Xperias, not as a purchase of a premium service

v 0.2.3
added Xperia ZR support

Yo!
Bought your app. It says it did everything successfully.
I first backed up fotakernel, then downloaded img, then flashed.
When i try to boot into recovery, all i get is system reboot. (When using advanced reboot options inside "Rom Toolbox" and such).
My phone is Sony Xperia ZR (dogo).
(Bootloader is unlocked and i got root access)
How do i enter recovery, or does this indicate twrp was not installed?

o-l-a-v said:
Yo!
Bought your app. It says it did everything successfully.
I first backed up fotakernel, then downloaded img, then flashed.
When i try to boot into recovery, all i get is system reboot. (When using advanced reboot options inside "Rom Toolbox" and such).
My phone is Sony Xperia ZR (dogo).
(Bootloader is unlocked and i got root access)
How do i enter recovery, or does this indicate twrp was not installed?
Click to expand...
Click to collapse
You should be running a kernel that supports FOTAKernel usage.
The normal stock kernel does not support that.

Updated the app to v2 which is called "Xperia Recovery Manager" now

championswimmer said:
Updated the app to v2 which is called "Xperia Recovery Manager" now
Click to expand...
Click to collapse
Will you add z1 compact when you got the resources needed?
Edit: Its already out! http://developer.sonymobile.com/dow...s/open-source-archive-for-build-14-2-a-1-114/

o-l-a-v said:
Will you add z1 compact when you got the resources needed?
Edit: Its already out! http://developer.sonymobile.com/dow...s/open-source-archive-for-build-14-2-a-1-114/
Click to expand...
Click to collapse
i would after we get custom kernels for it
before we get custom kernels, it is useless, because launching a recovery from FOTAKernel is possible only when you have a custom kernel.

Rebuilt and reuploaded TWRP images for Xperia Z1 and Z Ultra.
Issues with non-existent /data and /sdcard are resolved now

Don't mount sdcard and ext- card... How can I solved?
Sent from my Xperia Z1 using XDA Premium 4 mobile app

Nothing is being mounted in recovery on my Z1, can't see anything.

Poor little fellow that devices

Does not work on every circiumstance that I tested - open bootloader, closed bootloader, stock kernel, DooMKernel. To me this app is totally useless and no refund was possible, even within 15 Minutes! This App is a total rip-off for me!
Save your money and install ZUDualBootRecovery or a Kernel with FOTA Recovery build-im, what almost all root-Kernel have.

Upgraded to version 3.5
Now also supports PhilzTouch recoveries,
Xperia Z2 and Xperia Z1 compact support added as well.

TimeTurn said:
Does not work on every circiumstance that I tested - open bootloader, closed bootloader, stock kernel, DooMKernel. To me this app is totally useless and no refund was possible, even within 15 Minutes! This App is a total rip-off for me!
Save your money and install ZUDualBootRecovery or a Kernel with FOTA Recovery build-im, what almost all root-Kernel have.
Click to expand...
Click to collapse
Yeah right.
An open source app is a rip off ?
https://github.com/championswimmer/Xperia_FOTAKernel_Manager_Android_App

New update says amami now have TWRP. When downloading through the app, the img file is about 300kB or something, so somethings clearly wrong.

o-l-a-v said:
New update says amami now have TWRP. When downloading through the app, the img file is about 300kB or something, so somethings clearly wrong.
Click to expand...
Click to collapse
thanks for notifying.
fixed

Will you update TWRP images to v2.8.3.0?

Great app, this saved my phone as I could not for my life get it to flash a kernel with TWRP in fastboot mode. BIG thanks!

o-l-a-v said:
Will you update TWRP images to v2.8.3.0?
Click to expand...
Click to collapse
I think I'll get some time to do that over the next week.

championswimmer said:
I think I'll get some time to do that over the next week.
Click to expand...
Click to collapse
Please finally update TWRP for ZL!!! It's still on 2.6.3.0!!! Please, please, please, please!!! Thank you so much!!!

[Root] [Recovery] [Wipe-optional] 4.4.4 KitKat SGP311/312 10.5.1.A.0.283 VMo US, EU1

Xperia Tablet Z 4.4.4 KitKat Rom - Pre-rooted - Includes Recovery
For SGP311 and SGP312 - Wiping is optional​
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
Requirements:
Flashtool 0.9.15.0 or higher
Rooted SGP31X (on any other previous Android version) with custom recovery (i.e. XZDualRecovery) installed.
Previous firmwares up to 4.4.2 can be rooted with towelroot.
If your current Rom doesn't have recovery, follow step 10 of this post: http://forum.xda-developers.com/showpost.php?p=53063218&postcount=14 with tablet in USB debugging mode (step 4 of the same post).
This works on locked or unlocked bootloaders and any customization.
This ROM is pre-rooted and comes with recovery. Other than that it is identical to stock rom.
Download links:
SGP311 US_CA_PR https://mega.co.nz/#F!dhMBkRpC!qAsRR7WXJlKwsUwBuv1vig
SGP311 EU1 https://mega.co.nz/#F!p4FzQaqQ!o88OJPX4SyAYOUM3PMb5_A
SGP312 US_CA_PR https://mega.co.nz/#F!El8QnQxC!BlkadNT5FWGF3dLfCbD4mA
Use the link that matches your tablet model. You only need the zip and ftf files. The txt file is just the checksum if you want to verify that your download is error-free.
Instructions:
0- Backup before you start messing with your tablet!
1- Put system.flashable.zip in /sdcard of your tablet.
2- Keep SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf on your PC.
3- Disconnect any USB cable that may be attached to your tablet.
4- Reboot to recovery. Preferably to TWRP, but you can make CWM work too.
5- Do not wipe anything.
6- Once in recovery, flash system.flashable.zip.
7- It is important to TURN OFF the tablet after this step.
8- Find and use the Power Off option in the recovery and turn your tablet off. In CWM based PhilZ Touch it is under "Power Options" -> "Power Off". In TWRP it is under "Reboot" -> "Power Off". If you see your tablet rebooting, force it to turn off by pushing the power and volume up keys simultaneously (or however else you can!)
9- Open Flashtool 0.9.15.0 (or higher) and click on the flash icon. Choose flash mode.
10- Navigate to where you have saved SGP31X_10.5.1.A.0.283_VMo US_CA_PR_NoSystem.ftf
11- If you do not want your any of your current data to be wiped uncheck all the items under the "wipe" section. My recommendation however is to wipe.
12- Now flash this ftf with your tablet in flash mode. To put your tablet in flash mode, hold the volume down button when it is off and connect with the USB cable to the PC.
13- Reboot. You are now on rooted 4.4.4.
Credits:
I only put the files together. All the credit should go to XDA's [NUT] and DooMLoRD and many others...

Can I flash this on SGP312?

Kindly request if you could make also a flashable zip with any European rom

FiDra said:
Can I flash this on SGP312?
Click to expand...
Click to collapse
You can and it is not going to break your tablet but there are small differences between the two fimwares. I added a link for SPG312 too.

nick2crete said:
Kindly request if you could make also a flashable zip with any European rom
Click to expand...
Click to collapse
I can try when I have time. PM to me your model and your customization code.

Flashed and works good on SGP312
Thanks!

It worked perfect !
Thank you very much !

I wasn't going to update to 4.4.4 until you offered this solution. Swapping kernels,etc., re-rooting, reinstalling recovery was just more work than it was worth and had the potential to brick the device. Your approach is brilliant! Thank you very much.
However, I am not able to boot into recovery.

Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.

Working on 311

najoor said:
OP!!
Click to expand...
Click to collapse
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?

Shanliang- said:
Thank you very much for the easy-to-follow instructions.
It worked perfectly on my SGP312. Fully rooted 4.4.4 Kitkat.
Click to expand...
Click to collapse
How is it performing for you compared to omni rom?

cantenna said:
How is it performing for you compared to omni rom?
Click to expand...
Click to collapse
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.

Shanliang- said:
I wouldn't be able to compare it to Omni as I haven't used it. Actually, I havent used any AOSP 4.4.4 version. But I can say that 4.4.4 stock so far it has worked pretty well.
There's no lag anymore in the options menu.
Battery seems to last as much as it did on 4.4.2, but I'll update this info after some more testing.
Stock launcher feels smoother, although I use Nova Launcher Prime.
I haven't noticed any bugs for now. Perhaps the only thing is a quite short, recurrent distortion in the sound when playing music, but I had that issue in 4.4.2 as well. Haven't found any info on that.
I'll try to report more as I continue using it.
Click to expand...
Click to collapse
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us now

cantenna said:
Tanks man for the feedback. Will you be re-locking the boot loader for the DRM xperia engine, is that possible?
I am really glad that we have this option available to us know
Click to expand...
Click to collapse
yep! it's possble with BackupTA.

I'm surprised to hear there is occasional static sound with a stock ROM from Sony. Can you pleas elaborate as to the problem?
Also, if I follow this tutorial will it automatically relock my boot loader? I'd prefer to keep an unlocked boot loader until I have had opportunity to test drive.
I'm very pleased with my Omnirom ATM. Am curious to try though.
Thanks

Destroyedbeauty said:
Any chance that you can and will release a 10.5.1.A.0.283 deodex package for 311 / 312 versions / firmwares?
Click to expand...
Click to collapse
I've make one for 311/312, you can grab it here :
http://forum.xda-developers.com/xpe...ent/stock-rom-xperia-tablet-z-sgp312-t2876245

Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
Sorry, I do not and I have not tried this ROM yet

tamasrepus said:
Not completely related to the OP, but this is the first time I've upgraded a device that I had encrypted. Following all the steps, my device is now stuck in a bootloop. TWRP is unable to mount the encrypted partition w/ the passphrase I had set.
Anyone else experience this, or better yet have experience with this in general?
Click to expand...
Click to collapse
I got my stock 4.4.4 rooted, but unfortunately not with this ROM. Below are my thoughts on what the problem may be.
system.flashable.zip only includes TWRP 2.6.*, which apparently has issues mounting encrypted partitions. These issues are solved in TWRP 2.7; can the OP update system.flashable.zip to include 2.7?
For those who still want to use this ROM, after flashing system.flashable.zip, I'd immediately install dual recovery before rebooting. I've not tested it myself but it's my theory for what will work.

[Q&A] [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]

Q&A for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can i flash zip or ftf via adb? i'm using cm12 rom.

hi guys,
I bought a Z3C and I just checked the bootloader is not locked .
pen the dialler and enter #*#7378423#*# to access the service menu.
Tap Service info > Configuration > Rooting Status. Bootloader unlock allowed says Yes
I wanted to know if I could flash via Flashtool software directly ?

OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.

savudin said:
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
Click to expand...
Click to collapse
If you didn´t wipe data in recovery, then no data should be wiped. That´s normal.

Yes, that's it. But, did I had to wipe data? I've read that clean install is recommended. I've noticed no problems in the last couple of hours of usage.

Dirty Flash from 23.0.1.A.5.77
I dirty flashed 23.1.A.0.690 from Greatslon MIUI v5 23.0.1.A.5.77 and still have root.
The phone froze and bootlooped a couple of times when i installed and restarted it, but patience was rewarded, as it finally booted.
I can still mount /system as rw both via adb shell, "onboard" terminal and through Root Browser.
Can i be of some help with a logcat, and in case how?
I am a software developer myself, but in a different branch than android. I just can't see through how i should get started with android development.
Great work guys
I guess i should add, that i still have my bootloader locked.
So to summarize:
>Bootloader locked (never unlocked)
>Firmware 23.1.A.0.690 from this thread
>Full root
>System R/W

Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets

Interesting, I did exactly the same but only have partial root, meaning that my system indicates root but I don't have writing permissions. Tried the ADB fix but did not work. Any other suggestions for getting full root again?

FYI: Nut has mentioned that he fixed recovery in his main development thread and will be working on releasing it to everyone soon.

Tnx for ur great work... but i have problem to download from mega site.. and specialy from the folder...
can anyone give me the direct link of [5.0.2] Firmware 23.1.A.0.690 Generic and A.5.77... not the folder link...
and can anyone tell me where exactly save the file we download from mega site ?
i cant find it anywhere...
Tnx alot.. :xX

How to delete recovery when it not working, thanks

Can't try new xposed for lollipop because it require install from recovery. And recovery not working in 5.0.2

air32 said:
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Click to expand...
Click to collapse
edit the build.prop

what if I restore the TA Backup after that?

AndreDNA said:
what if I restore the TA Backup after that?
Click to expand...
Click to collapse
You would only need to restore the TA backup if you've unlocked your bootloader in the past.

I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app

AndreDNA said:
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.

2mal16 said:
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
Click to expand...
Click to collapse
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD

AndreDNA said:
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
Click to expand...
Click to collapse
Go to the thread of NUT dual recovery and (assuming your on a windows pc) download the installer for nut dual recovery. it will let you install the recovery on locked bootloader by running the install.bat file. with this recovery you can then flash a prerooted lollipop zip (you can do it yourself with prf creator, include the newest SuperSU zip and the newest dual recovery zip together with stock lollipop rom) after wiping your phone. people also just flashed over KK but i prefer to do it clean and set up my phone newly again. you will then end up with a phone which has system rw and root on lollipop but the recovery will be gone until NUT fixes it. That is what everybody is waiting for.
So unlocking BL wont really gain you anything except sonys DRM keys not working. it will just introduce an additional step to relock them.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=2261606
to get into recovery just spam the volume up button(or down since it has two recoveries ) when your phone boots and lights up the led.

Magisk and Bootloader

Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You

Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.

Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?

inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.

1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.

Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.

Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again

I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.

Ok.Thank you very much.I will learn more ...

Battery issue after flashing

Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
I followed this:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
with this option:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
I went with the G8441_47.1.A.8.49_CE1.rar firmware, as it seems most compatible. THANK YOU j4nn! Marvelous and relatively simple procedure . Flashed with newflasher (Flashtool doesn't work with XZ1 Compact?).
Rooting worked, but when the phone is on battery it never goes above 20%. It was 100% before and 20% immediately after flashing. Red warning light is on, unless the phone is off and plugged in.
So. I missed the part about omitting persist* and Qnovo*. Somehow my attest keys didn't break (PROVISIONED in service test).
It looks like what happened is I replaced the battery config? Info:
https://forum.xda-developers.com/xperia-x/help/flashed-xperia-x-low-battery-t3441158
https://forum.xda-developers.com/xperia-xa/help/strange-battery-issue-jumping-33-3-0-t3688178
Can't repair with Xperia Companion because unlocked bootloader (no way it could be re-locked, is there? My DRM keys are backed up).
Someone wrote about wiping the Qnovo partition. Any advice on how to do this? fastboot format Qnovo didn't work (looks like it doesn't find that partition)
Unrelated, and sorry if this is a total n00b question, but where on earth is TWRP compatible with this device/FW? j4nn's rooted kernel doesn't play well with TWRP install, so I'm hoping to just fastboot boot recovery.img. I can't find any recovery.img that works - I tried several of these:
https://androidfilehost.com/?w=files&flid=232371
But it just gets stuck on SONY logo, needing soft reset.

ben_pcc said:
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
Click to expand...
Click to collapse
Try this - https://developer.sony.com/develop/open-devices/get-started/flash-tool and report back.

WORKED. Flashed the US firmware with "Software Update Content Erase", battery now seems to be working normal again. Thank you so much!
Another question: I'd love to set this phone up to work with fastbooting TWRP (so, not a TWRP install on the phone). Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods? Preferably compatible with https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711

ben_pcc said:
Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods?[/url]
Click to expand...
Click to collapse
Why use such old FW? If you're sticking with Oreo then you want the FW ending .20 for the latest. An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.

Because I didn't know better. Emma gave me 47.1.A.16.20, I'll stick to that
Would you mind sharing what *img file exactly would work with fastboot that way? I had no trouble finding it for the Z5 compact, but one that would work here is eluding me. For example, if I run:
fastboot boot twrp-3.2.3-0-lilac-1.img
The phone boots up to SONY logo (black on white background) and stays there, unresponsive. Got the file from https://androidfilehost.com/?w=files&flid=286271

ben_pcc said:
Would you mind sharing what *img file exactly would work with fastboot that way?
Click to expand...
Click to collapse
Have you missed this post, which is linked to in the threads you've posted links to? - https://forum.xda-developers.com/showpost.php?p=79880858&postcount=1029

I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious

ben_pcc said:
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
Click to expand...
Click to collapse
From the last page - https://forum.xda-developers.com/showpost.php?p=83844543&postcount=1657
Although I would simply install the latest and use one of the unrooted kernels then root it with Magisk.

Hmm. I was aware of that. I tried several of the twrp*.img files, they all get stuck booting on the SONY logo.
Are you sure this is true:
An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Click to expand...
Click to collapse
I'm wondering if a FW update would solve the TWRP booting problem.
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.

ben_pcc said:
Are you sure this is true:
Click to expand...
Click to collapse
I know it used to be. Done a bit more searching for you https://forum.xda-developers.com/search/thread/3706704?query=fastboot twrp, and found this command...
Code:
fastboot reboot bootloader
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
...I've just tried it, in fastboot mode and it booted TWRP.
ben_pcc said:
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
Click to expand...
Click to collapse
Starting over is always painful but sometimes it's the best option. I have a rooted stock ROM and TWRP installed with no issues, on Oreo or PIE so if you do, then I suggest backing up the essentials and starting again.

YES. Thanks so much SXUsr! You were right after all, I tried a few different TWRP images and they work now. What I was missing was fastboot reboot bootloader. My Z5 Compact doesn't require it.
There was one more thing I had to figure out: data partition is encrypted, and for my (Android 8.0.0) device the TWRP you mentioned fails.
twrp-3.2.3-0-lilac-1.img on the other hand asks for my unlock pattern when it boots up, and backs up fine.
Now that I have a complete backup I'll consider my next steps (possibly flashing a new ROM. Honestly 8.0.0 seems fine, we'll see). Thanks again!!

ben_pcc said:
YES. Thanks so much SXUsr!
Click to expand...
Click to collapse
You're welcome. I've always installed it on this phone so wasn't aware of that command myself either, so we've both learnt something.