Database Develop

Root Xperia Z and still get OTA?

Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Use pro features of SuperSU or OTA Rootkeeper to protect your root, then when you OTA update you should be fine. Try not to modify anything in the System partition otherwise OTA will probably fail (is my understanding), or if you do (i.e. renaming various apks/odex files to .bak), make sure you put them back before OTA updating, in case they need to be patched.

Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.

As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..

alias_neo said:
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.
Click to expand...
Click to collapse
So I can make a nandroid backup with only root? Using Rom Manager app. Or do I need to unlock the bootlocker? If I can, then I can just recover from nandroid that are stock, update then backup again, change systemlibs etc?
Sent from my C6603 using xda app-developers app

babylonbwoy said:
As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..
Click to expand...
Click to collapse
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app

UnLucky12 said:
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2

alias_neo said:
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2

alias_neo said:
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe so. Buy don't quote me on that, like I said, never used it.
Sent from my C6603 using Tapatalk 2

It's the same if you use Sony Update Service or PC Compagnon, PCC contain other tool, while SUS only update. Also you can use Flashtool by Androxyde (here on XDA) to flash firmware converted in ftf format. Sony also relased it's own tool named flashtool to flash unlocked bootloader mobile because you can't use SUS/PCC when it's unlocked.
Read this thread "All the info you need before you begin" http://forum.xda-developers.com/showthread.php?t=2153167

Cwm recovery disappeared

Every time I install cwm recovery and I flash anything it disappears
Locked bootlaoder stock 4.2.2 rooted
Sent from my C6602 using xda app-developers app

Install [NUT]'s dual recovery. As far as I know it's the only one that works properly with 4.2.2.
http://forum.xda-developers.com/showthread.php?t=2261606
Sent from my C6603 using Tapatalk 2

This happens because the recovery actually is not associated with the kenel/bootloader.
It is actually installed on the android system. However, you can avoid this by flashing the recovery again after each time you flash an new rom.
Before you reboot, for sure.

SmoothSal said:
This happens because the recovery actually is not associated with the kenel/bootloader.
It is actually installed on the android system. However, you can avoid this by flashing the recovery again after each time you flash an new rom.
Before you reboot, for sure.
Click to expand...
Click to collapse
I was going to say that, but the OP states he is on a stock rooted rom, therefore it hasn't been lost because /system was overwritten.
It is true, however, that the recovery I linked to is the only one that works after the first time booting into it on stock 423 roms. If you look in the thread for CWM for locked bootloaders, you will see people complaining of the same problem as the OP.
Edit: http://forum.xda-developers.com/showthread.php?p=43035613
Sent from my C6603 using Tapatalk 2

If you use busybox 1.21 that problem can occure. Install 1.20.2
Sent from my C6603 using Tapatalk 4 Beta

kingvortex said:
Install [NUT]'s dual recovery. As far as I know it's the only one that works properly with 4.2.2.
http://forum.xda-developers.com/showthread.php?t=2261606
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
I installed this specific dual recovery it keeps disappearing also

eryen said:
If you use busybox 1.21 that problem can occure. Install 1.20.2
Sent from my C6603 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use 1.20.2 busy box

kingvortex said:
I was going to say that, but the OP states he is on a stock rooted rom, therefore it hasn't been lost because /system was overwritten.
It is true, however, that the recovery I linked to is the only one that works after the first time booting into it on stock 423 roms. If you look in the thread for CWM for locked bootloaders, you will see people complaining of the same problem as the OP.
Edit: http://forum.xda-developers.com/showthread.php?p=43035613
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
SmoothSal said:
This happens because the recovery actually is not associated with the kenel/bootloader.
It is actually installed on the android system. However, you can avoid this by flashing the recovery again after each time you flash an new rom.
Before you reboot, for sure.
Click to expand...
Click to collapse
I noticed that this happens after I mount the system permission as writable
any ideas why ?

fish droid said:
I installed this specific dual recovery it keeps disappearing also
Click to expand...
Click to collapse
If you're just installing mods with it, then it shouldn't disappear. If it does, then report it in the thread.
If you mean it disappears when installing a custom rom, then that is normal.
It says this in the OP of the dual recovery thread -
[QUOTE ]
When installing custom ROMs:
Be sure to flash lockeddualrecovery2.5.1-RELEASE.zip after installing the ROM and before you reboot, this way you will not lose recovery![/QUOTE]
Sent from my C6603 using Tapatalk 2

kingvortex said:
If you're just installing mods with it, then it shouldn't disappear. If it does, then report it in the thread.
If you mean it disappears when installing a custom rom, then that is normal.
It says this in the OP of the dual recovery thread -
[QUOTE ]
When installing custom ROMs:
Be sure to flash lockeddualrecovery2.5.1-RELEASE.zip after installing the ROM and before you reboot, this way you will not lose recovery!
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2[/QUOTE]
no it disappears after i mount the system permissions as writable and reboot
of course i know that i should flash the dual recovery after i install a new rom
but this happened before with cwm and twrp

Firstly, (from what I am reading in various threads), the versions of CWM and TWRP available in the development section do not work properly with 4.2.2 and will definitely disappear after a reboot in 4.2.2 based roms.
Have you installed version 2.5 of the dual recovery, as that is required for 4.2.2 roms? Earlier versions will also disappear after a reboot, I believe.
If so, have you manually updated your version of busybox? This can stop the dual recovery working according to what [NUT] Says in his thread.
If none of that applies, go report it to [NUT] in the dual recovery thread. I'm sure he will be happy to help.
Sent from my C6603 using Tapatalk 2

All works fine now after unlocking my bootloader
Sent from my C6603 using xda premium

LBE Privacy Guard -> boot loop -- help?

Hi,
i just installed LBE privacy guard (on stock 434 FW rooted, unlocked BL). Unfortunately that app decided to go haywire on my phone, sending it into a boot loop.
Stupid enough i didn't make a backup before installing that thing (why would anyone?).
Is there any way to get this thing off the device without razing it completely? I can access TWRP and flash/fastboot.

Use flashtool to reflash a stock 434 ftf. Just don't wipe /data and you shouldn't lose any of your settings/apps. You will have to root again though.
Sent from my C6603 using Tapatalk 2

kingvortex said:
Use flashtool to reflash a stock 434 ftf. Just don't wipe /data and you shouldn't lose any of your settings/apps. You will have to root again though.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
I tried that, reflashing the FTF, however the app was still there and it was still autostarting. But in TWRP i found the advanced>file manager and removed the .apk (good that i had TWRP flashed).

waaahsabi said:
I tried that, reflashing the FTF, however the app was still there and it was still autostarting. But in TWRP i found the advanced>file manager and removed the .apk (good that i had TWRP flashed).
Click to expand...
Click to collapse
Oh well. Glad you got it sorted.
Just FYI, everywhere I've seen LBE Privacy Guard mentioned there are people complaining that it causes reboot loops on Jelly Bean roms just like you experienced, so I'd give it a miss in future.
Sent from my C6603 using Tapatalk 2

Here on XDA there is a translated LBE Security Master. It has some useless stuff but it has still that privacy control.
Sent from my Xperia Z using XDA premium.

I had the same problem. delete the apk in the internal memory. look to where you find them. then it boots normally again.
My problem was solved.
Greets Stefan
Sent from my C6603 using xda premium

Looking out for a 4.4 (KitKat) Flashable-ZIP

For my new 2013 it is already available. But i need it for my for my fathers 2012 WiFi only version.
Unlocked, rooted and with custom recovery.
Sent from my Nexus 7 using xda app-developers app

I am looking for the same thing. Might take a day for someone to post it.
Sent from my Nexus 7 using Tapatalk 4

Ever heard of the word "please", fellas?

Me too, please
Wysłane z mojego HTC One przy użyciu Tapatalka

rapunzel11 said:
For my new 2013 it is already available. But i need it for my for my fathers 2012 WiFi only version.
Unlocked, rooted and with custom recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
TheSopranos16 said:
I am looking for the same thing. Might take a day for someone to post it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
adam_pl said:
Me too, please
Wysłane z mojego HTC One przy użyciu Tapatalka
Click to expand...
Click to collapse
Here you go. http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
Sent from my Nexus 5 using Tapatalk

That's one way. But not the way i want to do. Btw it will be easier to flash the complete image via Toolkit.
Sent from my Nexus 7 using xda app-developers app

would like that as well. Probably it will appear today. Fingers crossed.
Sent from my Nexus 7 using Tapatalk 2

Now i've flashed the factory image with Android Toolkit aka Nexus Toolkit. After that i reflashed the Custom Recovery.
Sent from my Nexus 7 using xda app-developers app

rapunzel11 said:
Now i've flashed the factory image with Android Toolkit aka Nexus Toolkit. After that i reflashed the Custom Recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Does it wipe whole data, including user data?
Right now I use stock 4.3 only with root and custom TWRP recovery. It would be the best for me to flash .ZIP file with rooted 4.4 trough recovery

At the beginning you have to choose if you want to format the user data. But ur right, the easiest way for those with custom recovery is a flashable ZIP.
Sent from my Nexus 7 using xda app-developers app

rapunzel11 said:
At the beginning you have to choose if you want to format the user data. But ur right, the easiest way for those with custom recovery is a flashable ZIP.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
For a Wi-Fi tablet, you really generally only have to push /system and maybe /boot through fastboot. It's two terminal commands, which is rather faster much of the time. That said, that presumes familiarity and comfort with the fastboot tool.

rapunzel11 said:
At the beginning you have to choose if you want to format the user data. But ur right, the easiest way for those with custom recovery is a flashable ZIP.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Especially that I don't want to backup all my aps with TB. And I don't even know it there's root already for N7's kitkat so I could restore all apps with Titanium Backup

Going back to stock and flashing the OTA using TWRP was the easiest method for me, now I got 4.4 rooted with OC and perfectly running.
Sent from my Nexus 7 using XDA Premium 4 mobile app

All y'all are overcomplicating this. There is nothing magical about the google script and download. Its just 4 partition images (boot, system, data and recovery) and batch file that runs a simple script to flash them. We already have the data we want and the recovery we want. So pull the images out of the file (they are buried under three compressions...its ridiculous). Pull boot.img and system.img. Then boot to recovery and factory reset. Then boot to bootloader. Then in a terminal on your PC, fastboot flash boot boot.img then fastboot flash system system.img. The reboot to recovery and flash the latest supersu.zip. The reboot, setup and restore with Titanium. Done. No need to ditch your recovery or blow away the media section of data.
Caveat...this assumes you are already on bootloader 4.23. There is no new bootloader for KK.

Can someone post power.grouper.so from /system/lib/hw 4.3 version? can't flash 4.4 because custom kernel and that file is unexpected contents... flashing stock kernel didn't help

Waiting patiently, I know it'll be out eventually and I'm in no rush. My tablet's usb connection hasn't worked in a long time, it charges fine but lsusb never registers anything. It's a hardware problem, I replaced the screen last month and I noticed the plug was slightly damaged.
TL;DR Some of us can only upgrade from a flashable zip, no usb connection means no fastboot
Thanks

mrplowdan said:
Waiting patiently, I know it'll be out eventually and I'm in no rush. My tablet's usb connection hasn't worked in a long time, it charges fine but lsusb never registers anything. It's a hardware problem, I replaced the screen last month and I noticed the plug was slightly damaged.
TL;DR Some of us can only upgrade from a flashable zip, no usb connection means no fastboot
Thanks
Click to expand...
Click to collapse
That sucks, sorry to hear that. My USB is getting rickety. I use a wireless charger on my S4 to try to keep down the wear and tear.
Sent from my Nexus 7 using XDA Premium HD app

Hmm seems as though no one has been able to make a flashable zip for any nexus 7 bootloaders... I suppose I should try to get back onto the stock version of android that matches my current bootloader without loosing custom recovery, get rooted, temp disable root, get back to stock recovery, get the OTA, restore root, get twrp back

mrplowdan said:
Hmm seems as though no one has been able to make a flashable zip for any nexus 7 bootloaders... I suppose I should try to get back onto the stock version of android that matches my current bootloader without loosing custom recovery, get rooted, temp disable root, get back to stock recovery, get the OTA, restore root, get twrp back
Click to expand...
Click to collapse
There's a fishable stock 4.4 rom here if that is any good to you?
http://forum.xda-developers.com/showthread.php?t=2529136
Sent from my GT-I9505 using Tapatalk

Thanks dude :good:

[Q] Bootloader, before rooting... [SOLVED.NEED TO LOCK THREAD]

Hi there, I'm new here. I'd like to ask anyone who know about blootloader. I have one issue with my phone. A few days ago, (more accurate - 1-2 weeks) I did rooting for my phone Xperia Z. Before that, I checked the configuration, and then I was allowed to unlock it. But now, (after rooting) i'm not able to do that anymore. How to understand that?
Before rooting was writting : „Allowed to unlock bootloader: Yes“
After : „No“.
What the hell happend ?
Does software update will solve this issue with my phone ?
What I shloud to do ?
I'm going to attach photo after rooting. I had contacted Sony HELP, but they said that I should search help anywhere else, 'cause they don't know anything about it or they can't say.
Maybe they can't answer 'cause I'm living in another country in which there's no Sony phone centre, only the main.
Any suggestions?

Did you root using this method - http://forum.xda-developers.com/xperia-z/development/root-xperia-z-zl-tablet-z-lb-ub-t2186368?
If so, you will see this written in the first post -
if u had an unlockable bootloader device, after using this method the device will be detected as LOCKED or unlock not possible!!! (to fix this use this fix)
Click to expand...
Click to collapse
Also, Sony support will not help with problems caused by you unofficially modifying the software on your phone, no matter where you live.
Sent from my C6603 using Tapatalk

Think so
kingvortex said:
Did you root using this method - http://forum.xda-developers.com/xperia-z/development/root-xperia-z-zl-tablet-z-lb-ub-t2186368?
If so, you will see this written in the first post -
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I did with this method: https://www.youtube.com/watch?v=nsh51O1ImMM
I used fast rooting or whatever is it
How I need to flash it ? I'm newbie at Android. :/
Do I need just replace that file with Root Explorer to it's file original destination? Thanks for reply.
EDIT: By the way, do I need upload META-IN folder too? :?
-- Sorry If I'm writting bad in English --

The method in that video is indeed the method that I linked to. You need to flash the file in recovery.
Try XZDualRecovery If you need a recovery. It should work, but I cannot be 100% on that as it seems you're on quite an old 4.1 firmware version.
Sent from my C6603 using Tapatalk

Another question
kingvortex said:
The method in that video is indeed the method that I linked to. You need to flash the file in recovery.
Try XZDualRecovery If you need a recovery. It should work, but I cannot be 100% on that as it seems you're on quite an old 4.1 firmware version.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I have that recovery already. It's needed to have SD card? Can I flash it though the phone memory ? Yes, I've 4.1.2 version. Awaiting for KitKat. Is there's any possibility to brick the phone? 'Cause I'm scared to try that then if so.

Yes, just put it on your internal SD. You will not brick your phone by flashing that file.
Sent from my C6603 using Tapatalk

data
kingvortex said:
Yes, just put it on your internal SD. You will not brick your phone by flashing that file.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Will it erase my all data in MicroSD card?

No.
Sent from my C6603 using Tapatalk

kingvortex said:
No.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
I don't find the DualRecovery file. I have XZRecovery already, but Its freezes as I push Install..

LaurynasVP said:
I don't find the DualRecovery file. I have XZRecovery already, but Its freezes as I push Install..
Click to expand...
Click to collapse
So, to be clear...
You downloaded the file from this post, rebooted into recovery, selected it and tried to flash it? If so, I have no idea why it would freeze up.
Sent from my C6603 using Tapatalk

kingvortex said:
So, to be clear...
You downloaded the file from this post, rebooted into recovery, selected it and tried to flash it? If so, I have no idea why it would freeze up.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
No. I trying to enter „Install“ menu in Recovery mode. I can't go into „Install“ section where I need to flash that .zip
EDIT : WORKED AS WELL.!!! THANK YOU VERY MUCH. ADDED THANK ON EVERY YOUR POST!!!!! MODS CAN LOCK THIS THREAD!!!!