Database Develop

[Q] Safe to OTA update rooted 10.3.1.A.0.244

Hi!
I have a C6603 on 10.3.1.A.0.244 Generic. The device has a locked BL (so stock kernel), but it is rooted and has a custom recovery installed.
Now the OTA Updater tells me 10.3.1.A.2.67 is available. Is it safe to apply this update or will it softbrick the device, since it is rooted and has a custom recovery image installed?
Best regards

In my experience, It's safe, but you'll lose root and your custom recovery. You'll need to reinstall both the recovery and re root it.

Thanks for both of you
I have similar issue here BUT:
C6602
10.3.1.A.0.244
I have unlocked bootloader and dual recovery
When attempting to install the new OTA update, it fails when using the system update option on the device and when trying to update using the PC Companion, it says: The phone contains modified software that cannot be updated
should re-locking bootloader solve this issue?

SudaDreamS said:
Thanks for both of you
I have similar issue here BUT:
C6602
10.3.1.A.0.244
I have unlocked bootloader and dual recovery
When attempting to install the new OTA update, it fails when using the system update option on the device and when trying to update using the PC Companion, it says: The phone contains modified software that cannot be updated
should re-locking bootloader solve this issue?
Click to expand...
Click to collapse
In order to update the phone via PCC, yes. You must be on locked bootloader
Sent from my SGP321 using xda app-developers app

JesusMcCloud said:
Hi!
I have a C6603 on 10.3.1.A.0.244 Generic. The device has a locked BL (so stock kernel), but it is rooted and has a custom recovery installed.
Now the OTA Updater tells me 10.3.1.A.2.67 is available. Is it safe to apply this update or will it softbrick the device, since it is rooted and has a custom recovery image installed?
Best regards
Click to expand...
Click to collapse
My personal experience : OTA will not install because you have custom recovery: will just reboot and gives the error on installation.
However if I'm rooted and on the stock recovery, OTA installs absolutely OK and does NOT break root (just reinstall SuperSU from the GMarket and update binaries after the update)
Saying so, I can NOT give any guarantee that the root will stay in your particular case, it's just my personal experience.

[Q] Rooting 4.3 Problem

Hey guys i know there is probably an answer in here somewhere but ihave looked everywhere and tried all possible options to get this working. After my pc companion nagging at me to upgrade i bit the bullet and upgraded to JB 4.3 10.4.B.0.569
Afterwards i then found out that it had relocked bootloader and unrooted my phone..
So i went through the sony normal way of unlocked bootloader first of all... this is where i've hit a snag.. first time the Command promp told me it had failed then itried again with my KEY and it said DONE.... now my phone was stuck in a terrifying bootloop. So i then flashed 4.3 firmware using flashtools, and repaired my phone through sony center.... again.. tried to unlock bootloader and was stuck in boot loop. I have re flashed about 4 times and tried to unlock 4 times... still getting boot loops....
Any one care to shed some light on this?
Many thanks
Chris

Bootloader
Is bootloader unlock allowed?

Have you tried relocking it again using flashtool?
Sent from my C6603 using XDA Premium 4 mobile app

Hey
I was playing around with 4.3 all last night and managed to get root on my Z with locked BL,
Here is how I did it..
(Locked bootloader, skip unlocking if already unlocked)
- Flash the .67 firmware via flashtool
- Root 4.2 as you would have
- Unlock your bootloader and Backup the TA partition to relock this without losing any DRM keys
- Using flashtool flash the new firmware .569 (4.3)
- Then flash Doomlords advanced stock kernel
- Boot 4.3 and power down
- Using the recover installed with the kernel flash a superSU.zip from somewhere around here.
- Reboot and you now should have root
[Locked bl]
- Reflash ONLY just .569 kernel from the FTF
- Power on and Restore your TA partition to relock your boot loader and return everything back to normal..but with some root
As for your bootloader not unlocking properly i would first check to see if an unlock is allowed

when i try to flash 4.2 67 firmware..i just got bootloop..please someone help me..what have i done wrong..i still in LB..

Wipe data when flashing.
Sent from my C6603 using Tapatalk

Just unlock your bootloader through Flashtool when on newest firmware, flash advanced stock kernel, root,flash back stock kernel and re-lock your bootloader. should be working for you, and it wont take that much time :good::good:

kuboweb said:
Just unlock your bootloader through Flashtool when on newest firmware, flash advanced stock kernel, root,flash back stock kernel and re-lock your bootloader. should be working for you, and it wont take that much time :good::good:
Click to expand...
Click to collapse
If the warranty and features such as Bravia Engine 2 are important to anyone, please don't just follow this. Your DRM keys that allow BE2 to work and your warranty will be permanently lost.
Follow the earlier post in this thread and downgrade, root and backup your TA partition BEFORE unlocking the bootloader.
Sent from my C6603 using Tapatalk

[Q] Stuck at the Sony Logo!

Ok! I am stuck at the sony logo then a screen appears saying that something went wrong while i was updating the device.
all I did was flash a wrong recovery image for my old phone & then this happened
what I tried:
1. tried to update from the flash tool (didn't work)
2. tried the sony PC companion & it didn't work either, it either says that I have modified software that can't be updated or says that my system doesn't have any updates
my phone is ZR C5502, bootloader was unlocked when I flashed the wrong recovery image.
Please help me I need the phone to work
Thanks in Advance

Teeeee said:
Ok! I am stuck at the sony logo then a screen appears saying that something went wrong while i was updating the device.
all I did was flash a wrong recovery image for my old phone & then this happened
what I tried:
1. tried to update from the flash tool (didn't work)
2. tried the sony PC companion & it didn't work either, it either says that I have modified software that can't be updated or says that my system doesn't have any updates
my phone is ZR C5502, bootloader was unlocked when I flashed the wrong recovery image.
Please help me I need the phone to work
Thanks in Advance
Click to expand...
Click to collapse
Did you take the backup of DRM keys and TA partition while unlocking bootloader? Sony PC comp does not support unlocked phones. you will have to restore the DRM keys and TA partition.
If you have lost both of these, then flash custom kernel and stock or AOSP based ROM using flashtool. search in forums for more info

Thank You!
I Had the Backup & tried Relocking the Bootloader but the PC companion couldn't help me, anyway, I flashed a flash custom kernel and stock ROM using flashtool, thank you so much :good:

Cant restore TA after relock bootloader in WIN 10

Help me please i cant restore TA
But i have relock my bootloader via flashtool and success
With my Backup TA tools My PC didnt detect ADB permission and then i tried in other PC but after detect there was an error .dll
Help me master
And sorry for bad english
Thanks

Unable to flash TWRP Recovery to an Xperia Z1 C6906

I've been trying to do this all night and am just having no luck. I was able to downgrade to Android 4.4.4 using C6906_14.4.A.0.157_Generic_US.ftf via FlashTool, and I was able to use KingRoot to gain root and FlashTool sees this, but when I look in the system menu it tells me that the bootloader is not unlockable, as well when I attempt to run the TWRP app with root and flash the TWRP image it says FLASH FAILED. I attempt to unlock the bootloader using FlashTool only to get errors such as:
WARN - ERR_SEVERITY="MINOR";ERR_CODE="0025";ERR_DYNAMIC="Wrong parameters";
ERROR - Processing of loader.sin finished with errors.
ERROR - null
I just want to be able to flash TWRP so I can install a custom 9.0 ROM and bring a little life back to this old device. Any suggestions?

Did you solve this?
I have the same problem