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

[Q] Downgrade to .434?

Hi,
My first post here on XDA! I have a Generic NL .253 Rom (without root, BL locked) flashed on my Z. I want to downgrade it to version .434 so I can root my phone. The problem is, everytime I try to flash it with flashtool, whenever my phone boots up, I get a message saying it's upgrading NFC, then it suddenly reboots. This happens over and over (kind of like a bootloop). I have tried several .FTF files. Also, I don't want to do a clean flash, I have made several backups but I'm afraid they don't live up to my 'backup'-standards. Does anyone know a fix for this?
Thanks in advance!

j0nthn said:
Hi,
My first post here on XDA! I have a Generic NL .253 Rom (without root, BL locked) flashed on my Z. I want to downgrade it to version .434 so I can root my phone. The problem is, everytime I try to flash it with flashtool, whenever my phone boots up, I get a message saying it's upgrading NFC, then it suddenly reboots. This happens over and over (kind of like a bootloop). I have tried several .FTF files. Also, I don't want to do a clean flash, I have made several backups but I'm afraid they don't live up to my 'backup'-standards. Does anyone know a fix for this?
Thanks in advance!
Click to expand...
Click to collapse
So you cannot turn on your phone now?

Ben Ling said:
So you cannot turn on your phone now?
Click to expand...
Click to collapse
Hey, thanks for you reply. Yes, I can. I reflashed my old .253 Generic NL software in between trying other .434 files and it still works fine.
The problem with the .434 is that my phone does boot, but it never properly boots, you know what I mean? It keeps on resetting, and displaying the 'NFC updating' message. Any ideas?
Jonathan

j0nthn said:
Hey, thanks for you reply. Yes, I can. I reflashed my old .253 Generic NL software in between trying other .434 files and it still works fine.
The problem with the .434 is that my phone does boot, but it never properly boots, you know what I mean? It keeps on resetting, and displaying the 'NFC updating' message. Any ideas?
Jonathan
Click to expand...
Click to collapse
so you can start your phone with .253 firmware?
.434 can?

Ben Ling said:
so you can start your phone with .253 firmware?
.434 can?
Click to expand...
Click to collapse
I can start up my phone with .253 firmware, but not really with .434 ('semi-bootloop due to 'NFC update')

j0nthn said:
Hey, thanks for you reply. Yes, I can. I reflashed my old .253 Generic NL software in between trying other .434 files and it still works fine.
The problem with the .434 is that my phone does boot, but it never properly boots, you know what I mean? It keeps on resetting, and displaying the 'NFC updating' message. Any ideas?
Jonathan
Click to expand...
Click to collapse
I'm actually having the exact same issue. I would like to downgrade so I can regain root. I have a feeling to fix the boot loop we would have to wipe the phone. I'm just deciding if I want to try that yet as it sucks redoing everything and the phone is running so good.

Qmann05 said:
I'm actually having the exact same issue. I would like to downgrade so I can regain root. I have a feeling to fix the boot loop we would have to wipe the phone. I'm just deciding if I want to try that yet as it sucks redoing everything and the phone is running so good.
Click to expand...
Click to collapse
Yeah exactly, the backup options are fairly limited since I haven't rooted it yet, and I kinda feel there should be a way around this loop
without having to wipe all my data..

i suggest wipe. it should work when downgrading.. i hope it will work on you both as i downgrade my z after updating to .253 and i dont have any bootloop issues...

Which backup do you think is the best? Pc companion/the pre installed 'backup and recovery' app/Carbon/adb full backup? Does any of these guarantee a full backup? I want to be sure before I try..
Sent from my C6603 using xda premium

j0nthn said:
Which backup do you think is the best? Pc companion/the pre installed 'backup and recovery' app/Carbon/adb full backup? Does any of these guarantee a full backup? I want to be sure before I try..
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I always trust Titanium Backup. Keep all my apps and important settings through several android phones over a few years already.
Sent from my C6603 using xda premium
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
I downgrade to 434 from 253 through Flashtool without wipe, reroot and flash NUT 253 without any problem.
Sent from my C6603 using xda premium

Yeah...the problem is, again, I haven't rooted yet. I know TB is the best, it's just not an option for me right now
Sent from my C6603 using xda premium

[/COLOR]
j0nthn said:
Yeah...the problem is, again, I haven't rooted yet. I know TB is the best, it's just not an option for me right now
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
.434 can be rooted either bin4ry or doomlords method.. and .253 can achieve root using nuts method or wawyed..

So it's possible to root .253 without having rooted before? Did not know that, I will look into that, thanks! This must be new since like today or yesterday, haha
Sent from my C6603 using xda premium

j0nthn said:
So it's possible to root .253 without having rooted before? Did not know that, I will look into that, thanks! This must be new since like today or yesterday, haha
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Coming from .434.. .253 is pre-rooted in there methods.. So try it and follow instructions well..
sent from my C6502 using xda-developers app

julianalexander said:
Coming from .434.. .253 is pre-rooted in there methods.. So try it and follow instructions well..
sent from my C6502 using xda-developers app
Click to expand...
Click to collapse
Yes exactly. But the problem is that I can't get back to .434, I already knew this
Sent from my C6603 using xda premium

j0nthn said:
Which backup do you think is the best? Pc companion/the pre installed 'backup and recovery' app/Carbon/adb full backup? Does any of these guarantee a full backup? I want to be sure before I try..
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Pre installed backup and recovery works great if you're not rooted. Just make sure to check all boxes to backup. Store backup on computer, wipe, flash, root 253 then restore.
Sent from my C6603 using xda app-developers app

I had exactly the same problem and the only solution was downgrade to .434 with a full wipe!
Everything else I tried ended in restart because of the NFC update.
I could restore my system, because I rooted .434 after the clean install,
updated to .253 from [nut] and restored only the data partition from my last nandroid with recovery.
Then everything was as before and works fine.
But trust me, the only solution is downgrading with a full wipe! :good:

Did you try flash kernel/ otakernel from the .434 with flashtool if not try then
I will skip that update (cannot even get it from Sony PC Companion) so wait for 4.2
I dont use NFC and don't need whitebalance calibration.

xchasa said:
Pre installed backup and recovery works great if you're not rooted. Just make sure to check all boxes to backup. Store backup on computer, wipe, flash, root 253 then restore.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Thank you for this, will try it now. Will keep you updated (if you're interested). Also thanks, Desire and donottouch!
Sent from my C6603 using xda premium

j0nthn said:
Thank you for this, will try it now. Will keep you updated (if you're interested). Also thanks, Desire and donottouch!
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
Told yah.. Wiping will do the trick..
sent from my C6502 using xda-developers app

Unable to update .244 from OTA for my Xperia Z

Hi,
I am not able to update my XZ to the latest .244 firmware. Here are some info of my Phone.
1) locked bootloader (it is unlockable)
2) current on .423 firmware.
3) rooted
4) install superSU (with survival mode on)
5) install OTA rootkeeper.
I saw some post stating that they are able to keep root after OTA, so i am hoping to keep my root too after OTA.
please advise.

I have exactly the same problem. Cant do OTA and im states scared to update through PC companion since my friend bricked up the phone.
Sent from my C6603 using Tapatalk 2

Are you running stock .423 odexed? I had this issue when I flashed a deodexed ROM then tried OTA update
Sent from my C6603

Hi,
It is not possible to do a OTA Update after deleting one or more system apps (even stuff like partnerbookmarks).
There are, however, 2 ways to get the Update.
1.) Follow some of the instructions here like this: http://forum.xda-developers.com/showthread.php?t=2287149
There are some other ways posted here at xda. They use the flashtool to flash current firmware.
2.) Use Sony PC Companion, this will work ALWAYS,but: Root will be gone. U can use Doomlords rooting method to get Root again:
http://forum.xda-developers.com/showthread.php?t=2386405
Good luck

hutilicious said:
Hi,
It is not possible to do a OTA Update after deleting one or more system apps (even stuff like partnerbookmarks).
There are, however, 2 ways to get the Update.
1.) Follow some of the instructions here like this: http://forum.xda-developers.com/showthread.php?t=2287149
There are some other ways posted here at xda. They use the flashtool to flash current firmware.
2.) Use Sony PC Companion, this will work ALWAYS,but: Root will be gone. U can use Doomlords rooting method to get Root again:
http://forum.xda-developers.com/showthread.php?t=2386405
Good luck
Click to expand...
Click to collapse
I flashed mine .423 using flashtool, so guests I needed update using pc then...
Sent from my C6603 using xda premium

Flashben said:
I flashed mine .423 using flashtool, so guests I needed update using pc then...
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
PC Update will never fail, the only thing is that you lose root access, which can be easily recovered though.

hutilicious said:
PC Update will never fail, the only thing is that you lose root access, which can be easily recovered though.
Click to expand...
Click to collapse
Yeah, just updated and rooted
Sent from my C6603 using xda premium

PLEASE HELP
my xperia Z , c6602 , got new update .244
tried to update using fone , downloded 175 mb and restrted, updating proceess came up (android logo) automatically rebooted when the progress bar about 75% , not updated same old .423
tried 2 times same issue,
then i tried using sony pc companin(win8), donloaded updated and strted update process, progress bar 90% came up error that update failed,
disconnect phone,
NOW phone didnt boot up
only SONY logo coming and switchs off.
pls help

It could be brick....
Sent from my C6603 using xda premium

Flashben said:
It could be brick....
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
thanks for responce, so what i can do now?

diz_007 said:
thanks for responce, so what i can do now?
Click to expand...
Click to collapse
Hi mate, dont panic. Just follow the instructions on how to flash a stock firmware with flashtool. This is already described here at xda, try searching for it. It will repair your phone but data may be lost.
Look at this: http://forum.xda-developers.com/showthread.php?t=2240614
Sent from my C6603 using xda app-developers app

hutilicious said:
Hi mate, dont panic. Just follow the instructions on how to flash a stock firmware with flashtool. This is already described here at xda, try searching for it. It will repair your phone but data may be lost.
Look at this: http://forum.xda-developers.com/showthread.php?t=2240614
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
thanks.. i tryed repaIR OPTION FROM pc companin, data lost! but updated to latest and good now!

Troubleshoot Doomlord root method (10.3.1.A.2.67)

Hey guys!
I tried rooting using Doomlord's method (http://forum.xda-developers.com/showthread.php?t=2386405) but for some reason the script didn't install supersu or root my phone. Is anyone else experiencing troubles with this or know how to troubleshoot the issue?
This is what I did:
-Opened flashtool and flashed .423 kernel only
-Closed flashtool
-launched Doomlord's script
-script says everything was successful and phone reboots (checked for Supersu and root but nothing)
-flashed back .67 kernel

what firmware are you starting from? Ive found It works best for me to do a full flash of stock 67 firmware, (unbranded) then flash a 423 kernel, then use doomlords root method, but flash the 67 kernel back before actually rebooting to the os. on my phone it will boot with the 423 kernel, but others have reported it not. also is your phone a c6602, 6603, or tmobile 6606? because the 02 and 03 have different firmware versions. also its possible your adb/usb drivers arent set up or working properly, recovery and doomlord can say they installed fine but have no effect if the driver is not doing its thing

Try Kingo, It worked flawlessly! :')
Try this method using Kingo Android Root!
Easy method to root...http://forum.xda-developers.com/showthread.php?t=2460745
Ask me if you need more help.

Do not use Kingo root.
It sends your IMEI and several other pieces of data that it should never need, such as your device ID to a server in China. It is currently not allowed on XDA for that reason.
Sent from my C6603 using Tapatalk

aethervagrant said:
what firmware are you starting from? Ive found It works best for me to do a full flash of stock 67 firmware, (unbranded) then flash a 423 kernel, then use doomlords root method, but flash the 67 kernel back before actually rebooting to the os. on my phone it will boot with the 423 kernel, but others have reported it not. also is your phone a c6602, 6603, or tmobile 6606? because the 02 and 03 have different firmware versions. also its possible your adb/usb drivers arent set up or working properly, recovery and doomlord can say they installed fine but have no effect if the driver is not doing its thing
Click to expand...
Click to collapse
Hey
I'm on 67 and its a 6603. How do I know for sure if my adb/usb drivers aren't set up properly? I previously rooted my phone back on the older firmwares but encountered some issues some I went back to stock and used supersu to unroot.

kingvortex said:
Do not use Kingo root.
It sends your IMEI and several other pieces of data that it should never need, such as your device ID to a server in China. It is currently not allowed on XDA for that reason.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Is that true?

Ali Shayzadag said:
Is that true?
Click to expand...
Click to collapse
Yes. Read the last post in the thread that you linked to.
http://forum.xda-developers.com/showthread.php?p=47188994
You will find that every thread linking to Kingo gets closed at the moment.
They try and justify grabbing all the info that they do on their Facebook page, but I do not trust them and would not give their software full access to my phone.
Sent from my C6603 using Tapatalk

kingvortex said:
Yes. Read the last post in the thread that you linked to.
http://forum.xda-developers.com/showthread.php?p=47188994
You will find that every thread linking to Kingo gets closed at the moment.
They try and justify grabbing all the info that they do on their Facebook page, but I do not trust them and would not give their software full access to my phone.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks Man! You just saved me. I removed it from my PC :/
But I used it root my Xperia Z! Now what should I do? Do I need to reset my phone if that put something also in my phone?
Please help me, I am so tensed now!

It isn't proven that anything bad is pushed to your phone. Only that they grab your device ID/IMEI etc during the rooting process.
I just do not personally trust Kingo for a number of reasons, such as the fact that they hide their company location and registered their website in the US, when they clearly are not from there.
If you're concerned, perhaps you should flash a stock rom either by repairing your phone with PCC/SUS or with Flashtool. That will remove any changes to your phone's system. Then root again with a method by a trusted developer such as DooMLoRD.
Sent from my C6603 using Tapatalk

kingvortex said:
It isn't proven that anything bad is pushed to your phone. Only that they grab your device ID/IMEI etc during the rooting process.
I just do not personally trust Kingo for a number of reasons, such as the fact that they hide their company location and registered their website in the US, when they clearly are not from there.
If you're concerned, perhaps you should flash a stock rom either by repairing your phone with PCC/SUS or with Flashtool. That will remove any changes to your phone's system. Then root again with a method by a trusted developer such as DooMLoRD.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thank you, brother! You saved me :')

kingvortex said:
It isn't proven that anything bad is pushed to your phone. Only that they grab your device ID/IMEI etc during the rooting process.
I just do not personally trust Kingo for a number of reasons, such as the fact that they hide their company location and registered their website in the US, when they clearly are not from there.
If you're concerned, perhaps you should flash a stock rom either by repairing your phone with PCC/SUS or with Flashtool. That will remove any changes to your phone's system. Then root again with a method by a trusted developer such as DooMLoRD.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Dude, thanks for the heads-up. I was about to download & use their tool!
However, the DoomLoRD method dunnae work on my C6603 running .67 firmware? Have you any suggestions, please?

skoop99 said:
Dude, thanks for the heads-up. I was about to download & use their tool!
However, the DoomLoRD method dunnae work on my C6603 running .67 firmware? Have you any suggestions, please?
Click to expand...
Click to collapse
Use this instead - http://forum.xda-developers.com/showthread.php?t=2559009
Sent from my C6603 using Tapatalk

I did - works a treat!
Sent from my C6603 using Tapatalk

[Q] Confirming the Stuff i need to do

NOTE: MODS, i know i could have used an existing thread for this, but i need the information in a proper way and maybe ask some repeated questions.
Hi guys,
I recently bought my first sony phone. Mighty impressed, i must say. Being an old HTC fan, i didnt expect i will ever make a jump, but this phone hooked me.
I have worked a bit for the development of HTC and some other phones, so i know what to look for and where to. Reading all the guides here, this is what i concluded if i want to safely unlock bootloader and flash some CM goodness. Please read my steps and let me know i am doing the right thing:
1. Root (via Doomlord thread guide. Flash old kernel, use exploit, then flash new kernel back)
2. Backup TA partition (for the precious BE2 and other magical SONY stuff)
3. Unlock BL the official or unofficial way, (as it doesnt matter because i can always relock it using TA backup , am i right???)
4. Flash CWM/TWRP etc and enjoy all the custom roms. (never look back)
Much appreciated guys. I will surely contribute with my own flavor of aokp once i get the basics correct. Not so soon.
Regards
neXusPRIME

Yes and Yes.
The steps you described are the proper ones

Yep that's the right steps to do!Have fun unlocking your device

Real benefits of unlocking bootloader? And can I use custom roms without unlocking?
Found it. I need to unlock before flashing non stock custom roms.
Sent from my C5303 using Tapatalk

Secondly, does anyone know a method to skip tracks while sleep mode? I don't want to wake phone each time I want to skip a track
Sent from my C5303 using Tapatalk

neXus PRIME said:
Secondly, does anyone know a method to skip tracks while sleep mode? I don't want to wake phone each time I want to skip a track
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Maybe Xposed Framework can help you out

Hmmm. Then I have to root.... Okay, I'll do that. Any other option?
Sent from my C5303 using Tapatalk

if 4.3 comes via OTA and i have rooted (not Unlocked), will i get the ota and will it install properly?
or do we need a clean untouched device for OTA?

No if your bootloader is untouched it will update you will lose root tho
Sent from my C5303 using XDA Premium 4 mobile app

mrjraider said:
No if your bootloader is untouched it will update you will lose root tho
Sent from my C5303 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can use Voodoo OTA Rootkeepr for that

Rooting will flash custom recovery. How to get back stock recovery after that?
Sent from my C5303 using Tapatalk

neXus PRIME said:
Rooting will flash custom recovery. How to get back stock recovery after that?
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Rooting will not flash a custom recovery it will just install a SuperSu app and su binary. U can use a stock firmware and flash it using flashtool to get back to stock
Sent from my C5302 using Tapatalk

One last question before taking the plunge.
What if i flash a generic stock FTF (for my c5303 ofcourse), but not caring about the branding, will that also be okay for OTAs or will i have to repair/update via PCC SEUS?
In other words, how do i know which branding stock ftf do i need? About Phone page doesnt have that info i think.
I am not worried about system partition or anything, but i want to make sure i have stock recovery of my phone which will guaranteed work when i get the 4.3 OTA.
for rest, ill root, flash CWM and nand backup all things.
btw, it was so so easier on HTC

neXus PRIME said:
One last question before taking the plunge.
What if i flash a generic stock FTF (for my c5303 ofcourse), but not caring about the branding, will that also be okay for OTAs or will i have to repair/update via PCC SEUS?
In other words, how do i know which branding stock ftf do i need? About Phone page doesnt have that info i think.
I am not worried about system partition or anything, but i want to make sure i have stock recovery of my phone which will guaranteed work when i get the 4.3 OTA.
for rest, ill root, flash CWM and nand backup all things.
btw, it was so so easier on HTC
Click to expand...
Click to collapse
You can restore you phone with SEUS also with Flashtool ofcourse.
It does not matter what kind of firmware you flash as long as it is an C5303 one. I had dutch Vodafone Branded and I flashed a Generic EU one without issue the updates will be provide by Sony and not vodafone (my case).

mrjraider said:
You can restore you phone with SEUS also with Flashtool ofcourse.
It does not matter what kind of firmware you flash as long as it is an C5303 one. I had dutch Vodafone Branded and I flashed a Generic EU one without issue the updates will be provide by Sony and not vodafone (my case).
Click to expand...
Click to collapse
Great. Thanks. I'm thinking of creating my own ftf. Just for the sake of it.
Sent from my C5303 using Tapatalk

A little help please!!!
locked BL
rooted stock
installed cwm n twrp for locked bl. took a nand backup.
tried to flash existenze ultra using twrp without wiping anything. Installation completed in 10 sec, which is fishy.
on reboot, phone is stuck on sony logo.
cant enter recovery, only goes into flashmode....
what to do now???
can i recover??

neXus PRIME said:
A little help please!!!
locked BL
rooted stock
installed cwm n twrp for locked bl. took a nand backup.
tried to flash existenze ultra using twrp without wiping anything. Installation completed in 10 sec, which is fishy.
on reboot, phone is stuck on sony logo.
cant enter recovery, only goes into flashmode....
what to do now???
can i recover??
Click to expand...
Click to collapse
Well, that's weird... Flash original .ftf with flashtool?

Nanostray said:
Well, that's weird... Flash original .ftf with flashtool?
Click to expand...
Click to collapse
Used sony update service to repair my phone,
Its back to unrooted stock 254
i think twrp messed something up.
Is it recommended or CWM only works?
on my old phone, twrp was more reliable.
There is something fishy with sony mobiles.
I know the modding stuff is more safe due to flashtool being always available for the rescue, however common stuff such as unlock, TA, recovery and etc are much too complicated for the newcomers.
even being n RC for porting TWRP to two htc phones didnt help me there.
Stuff dont work the first time.
In my case, the problem was,
flashtool worked the second time for flashing 254 kernel
doomlord kit worked the second time for rooting (i really dont know why, but it wasnt related to kit, something up with usb debug n permissions)
installing CWM didnt work the first time as well, (not the fault of installer, rather first time fails coz u give SU permissions just then, so something is missed, 2nd time, the SU permission is already there, so it works)
and ROM flashing almost always needs wipe dalvik/data/cache etc otherwise you might mess something up...
Its a lot safer if i see it one way, because these steps are more foolproof, but on the other hand, a lot more complicated, then say HTC or samsung phones. especially as i havent unlocked my BL so being cautious at every step.
Anyways, all things are fine now, using existenze ultra and enjoying it every bit.
Will step more carefully now on, using above as experience. Thanks all. This thread is closed until i have another problem