Database Develop

[FIRMWARE] Xperia Z (C6603) 10.1.A.1.350_SG_UNBANDED FTF

Managed to download and convert the firmware from SG, using the method taught in this forum. http://forum.xda-developers.com/showthread.php?t=2188129
Been able to flash back to stock using flash tool.
Respect and thanks to all who had been making this a great community.
Just want to contribute back and hoping to help someone.
http://www.mediafire.com/?y2rm1x5y47h1eh3

timchew said:
Managed to download and convert the firmware from SG, using the method taught in this forum. http://forum.xda-developers.com/showthread.php?t=2188129
Been able to flash back to stock using flash tool.
Respect and thanks to all who had been making this a great community.
Just want to contribute back and hoping help someone.
http://www.mediafire.com/?y2rm1x5y47h1eh3
Click to expand...
Click to collapse
You do realise that if for example your phone had TMobile ROM on it it will download the TMobile ROM in that tutorial. I have done it myself. I am with Telstra (in Australia) and I followed that tutorial and as soon as I flashed the ROM I downloaded I saw the Telstra splashscreen.
xl VipeR lx said:
Just to clarify further. It would be three firmware. Three would be pised off if sony unbranded everyone lol. They have carrier agreements. So your ftf would be three branded
Click to expand...
Click to collapse

I am afraid I am a noob here on that. I had just followed the tutorial to the T and created a FTF that can be flashed with flashtool. Been using this for the past two weeks when ROMs can't be rooted/CWM can't be installed.

timchew said:
Managed to download and convert the firmware from SG, using the method taught in this forum. http://forum.xda-developers.com/showthread.php?t=2188129
Been able to flash back to stock using flash tool.
Respect and thanks to all who had been making this a great community.
Just want to contribute back and hoping to help someone.
http://www.mediafire.com/?y2rm1x5y47h1eh3
Click to expand...
Click to collapse
Bro, sorry, but is this really unbranded, i.e. not telco based?

timchew said:
I am afraid I am a noob here on that. I had just followed the tutorial to the T and created a FTF that can be flashed with flashtool. Been using this for the past two weeks when ROMs can't be rooted/CWM can't be installed.
Click to expand...
Click to collapse
All I'm saying is that I followed the tutorial word for word and VipeR lx is right when he clarified things up that if your XZ is branded you would still get the downloaded ROM branded, just like what happened to me. Luckily there's a unbranded ROM for Australia which made it possible for me to de-brand my XZ. I do have the Telstra ROM saved so if ever I had to send it away for warranty repairs I can always flash the Telstra ROM back.

Me too. I used the update services software to download. After downloading the file and flashing with flash tool, there is no indication that this firmware is linked to any Telco.
Maybe if someone can flash and report?
Sent from my C6603 using xda app-developers app

timchew said:
Me too. I used the update services software to download. After downloading the file and flashing with flash tool, there is no indication that this firmware is linked to any Telco.
Maybe if someone can flash and report?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I flashed this and screwed it seems. It's a demo set's firmware
Once the screen dims and try to go off, the demo video starts up. I don't know how to get rid of this even after I flash my original FTF's system :'(

LiveSquare said:
I flashed this and screwed it seems. It's a demo set's firmware
Once the screen dims and try to go off, the demo video starts up. I don't know how to get rid of this even after I flash my original FTF's system :'(
Click to expand...
Click to collapse
Strange, bro.
Did you even manage to get into the setup? 5 steps to setting up your phone? I had that demo video. but after setting up the phone, all is well.
I had tried this firmware a few times after installing ROMs that are based on the 434, as somehow, I lose 3G with these ROMs. I couldn't even root the phone with the method described.
So I flashed back to the stock 350 firmware and root the phone and install the CWM recovery in the phone again.

timchew said:
Strange, bro.
Did you even manage to get into the setup? 5 steps to setting up your phone? I had that demo video. but after setting up the phone, all is well.
I had tried this firmware a few times after installing ROMs that are based on the 434, as somehow, I lose 3G with these ROMs. I couldn't even root the phone with the method described.
So I flashed back to the stock 350 firmware and root the phone and install the CWM recovery in the phone again.
Click to expand...
Click to collapse
I wanted to debrand as mine is attached to SingTel. I flashed this over my existing setup and didn't do a wipe. Now it has screwed up that I can't turn the screen off at all (finally I killed that some demo application and off now). Luckily didn't loose data except the home screen setup.
I will have to reinstall the whole thing tonight.

Is that the retail demo you are talking about?
You can turn it on off by dialing *#*#73556673#*#*
Sent from my C6602 using xda premium

LiveSquare said:
I wanted to debrand as mine is attached to SingTel. I flashed this over my existing setup and didn't do a wipe. Now it has screwed up that I can't turn the screen off at all (finally I killed that some demo application and off now). Luckily didn't loose data except the home screen setup.
I will have to reinstall the whole thing tonight.
Click to expand...
Click to collapse
Why not flash to any other FTF? Mines attached to Starhub,I flashed to other .434 FTF :angel:

gm007 said:
Is that the retail demo you are talking about?
You can turn it on off by dialing *#*#73556673#*#*
Sent from my C6602 using xda premium
Click to expand...
Click to collapse
Yes, but this is actually the demo unit firmware. No update even to .434
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Thraxzzz said:
Why not flash to any other FTF? Mines attached to Starhub,I flashed to other .434 FTF :angel:
Click to expand...
Click to collapse
I'm looking for unbranded Singapore firmware.

LiveSquare said:
I wanted to debrand as mine is attached to SingTel. I flashed this over my existing setup and didn't do a wipe. Now it has screwed up that I can't turn the screen off at all (finally I killed that some demo application and off now). Luckily didn't loose data except the home screen setup.
I will have to reinstall the whole thing tonight.
Click to expand...
Click to collapse
U did flash with flash tool and not recovery right? If you do flash with flash tool, all data is lost.
I think this is unbranded as the apps from M1 which I got this phone from is not present in the FTF after flashing with flash tool.
Sent from my C6603 using xda app-developers app

timchew said:
Me too. I used the update services software to download. After downloading the file and flashing with flash tool, there is no indication that this firmware is linked to any Telco.
Maybe if someone can flash and report?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Who knows maybe the M1 apps in your phone was not integrated to the ROM and it was only installed on top. I can't really tell. I just know that when I did the tutorial I still got the Telstra ROM.
Also using the Flashtool you have a choice of wiping data if you don't untick the boxes before you flash.
EDIT:
There is the
(FTF) C6603 10.1.A.434 Cust ID 1270-1412_R6A Singapore available in that thread. The handset apparently is from M1 so I'm not sure if it's branded or not.

shadowboy23 said:
Who knows maybe the M1 apps in your phone was not integrated to the ROM and it was only installed on top. I can't really tell. I just know that when I did the tutorial I still got the Telstra ROM.
Also using the Flashtool you have a choice of wiping data if you don't untick the boxes before you flash.
EDIT:
There is the
(FTF) C6603 10.1.A.434 Cust ID 1270-1412_R6A Singapore available in that thread. The handset apparently is from M1 so I'm not sure if it's branded or not.
Click to expand...
Click to collapse
Thanks for the info on flash tool! Always thought u had to lose data when flashing with flash tool.
Downloaded the ftf using updates services, then it should be unbranded, right? Do u suggest I remove this thread then? Thanks!
Sent from my C6603 using xda app-developers app

timchew said:
Thanks for the info on flash tool! Always thought u had to lose data when flashing with flash tool.
Downloaded the ftf using updates services, then it should be unbranded, right? Do u suggest I remove this thread then? Thanks!
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
No don't remove the thread. If you didn't get M1 apps after following that tutorial then the M! apps must have been installed on top of the ROM that's probably why you never got any M! apps when you reflash.
Keep this thread it's always a contribution that you made and plenty of people will have use for it.

timchew said:
U did flash with flash tool and not recovery right? If you do flash with flash tool, all data is lost.
I think this is unbranded as the apps from M1 which I got this phone from is not present in the FTF after flashing with flash tool.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I flashed with flashtool and there is option not to wipe.
This firmware is confirmed not the generic as I have seen this SI/CDA number in the demo set. Retail sets (so far I've seen) begins with 1270, but if you notice this begins with 1272. Moreover, none of the retail sets will run the "demo" video when you start your phone and worst is that it won't let your phone to switch off the screen.
I don't know how you ended up with this firmware on your handset!

LiveSquare said:
I flashed with flashtool and there is option not to wipe.
This firmware is confirmed not the generic as I have seen this SI/CDA number in the demo set. Retail sets (so far I've seen) begins with 1270, but if you notice this begins with 1272. Moreover, none of the retail sets will run the "demo" video when you start your phone and worst is that it won't let your phone to switch off the screen.
I don't know how you ended up with this firmware on your handset!
Click to expand...
Click to collapse
Not sure, Bro. But all I could say was I followed the tutorial and got the FTF file which I had been using a couple of times without issues.
Sent from my C6602 using xda app-developers app

Alright I am new to the XZ, i use to have the X Play a long time ago, but havent messed with BL unlock, flashing, rooting or anything in awhile. I had a question, if i unbrand my TMobile XZ to an unbranded version, will i then be able to unlock my BL? Or does that remain unlockable regardless?

Hi before you do anything make sure to perform a backup of your DRMs via Backup TA. Then you are free to do whatever you want.
Sent from my C6603 using Tapatalk 4 Beta

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] unlocking bootloader

hello, i have the xperia z1 on 4.3 build 14.2.A.0.290. it was updated through sony pc companion. It is currently completely stock. but i have a couple of n00b questions, so please take it easy on me, i have done lots of reading and i am just confused now.
how do i unlock my bootloader if my pc can not find the " s1 fastboot driver" ? / whats the easiest way?
once unlocked, can i flash a rom that is capable of root? or already has root?
i used to flash roms with my old phone but that was basic compared to this stuff, its a big step up from motorola defy to the xperia z1. so please take it easy on me, i have been lurking around here for ages but im just so confused now. but i thank anyone who can help in advance!
thank you

s.t.25 said:
hello, i have the xperia z1 on 4.3 build 14.2.A.0.290. it was updated through sony pc companion. It is currently completely stock. but i have a couple of n00b questions, so please take it easy on me, i have done lots of reading and i am just confused now.
how do i unlock my bootloader if my pc can not find the " s1 fastboot driver" ? / whats the easiest way?
once unlocked, can i flash a rom that is capable of root? or already has root?
i used to flash roms with my old phone but that was basic compared to this stuff, its a big step up from motorola defy to the xperia z1. so please take it easy on me, i have been lurking around here for ages but im just so confused now. but i thank anyone who can help in advance!
thank you
Click to expand...
Click to collapse
I installed [TOOL]Minimal ADB and Fastboot [7-18-13] and had no problems getting fastboot to talk.
Once you're unlocked, you can flash any custom kernel and any ROM you like. There's a thread on how to unlock 4.3, but it's not for beginners. You're better off just flashing a pre-rooted ROM.

Thank you for your help. I've managed to unlock it but I ended up using flash tool as I found a guide to show how to install the required drivers for the s1 fastboot. So now I am on the hunt for roms, would you or anyone else suggest a rom that is better on battery life but still very snappy? Thank you again, I do appreciate it
Sent from my C6903 using xda app-developers app

s.t.25 said:
Thank you for your help. I've managed to unlock it but I ended up using flash tool as I found a guide to show how to install the required drivers for the s1 fastboot. So now I am on the hunt for roms, would you or anyone else suggest a rom that is better on battery life but still very snappy? Thank you again, I do appreciate it
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Personally I'm using Pure Stock by iHackers http://forum.xda-developers.com/showthread.php?t=2579270
Highly recommend. :angel:

Thank you very much, the minimal version looks perfect for me, but before I do install the minimal one, could you tell me how to go about creating a backup of my rom / data n stuff at the moment. Because I understand that because my bootloader is unlocked, I don't have to install a recovery? But surely it's easier to create a backup with recovery and reinstall that at a later date than to install another stock ftf and losing all my data.
Sent from my C6903 using xda app-developers app

s.t.25 said:
Thank you very much, the minimal version looks perfect for me, but before I do install the minimal one, could you tell me how to go about creating a backup of my rom / data n stuff at the moment. Because I understand that because my bootloader is unlocked, I don't have to install a recovery? But surely it's easier to create a backup with recovery and reinstall that at a later date than to install another stock ftf and losing all my data.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
I would root your current ROM, install TiBu, and use that to backup. Otherwise, you can flash a recovery and use that to do a complete backup. On your next ROM, TiBu (Pro, probably) can restore from either kind of backup. I hope you knew to backup the TA partition before unlocking the bootloader!

C6606 (T-Mobile USA) pre-Rooting questions

Hi All,
I have T-Mobile branded C6606 and have been considering rooting so that I can flash a c6603 stock ROM. I know the bootloader is locked on the device but here is my question:
If I flash a stock ROM and basically make the phone act as a 6603, will I get updates directly from Sony for example will I be able to upgrade to 4.3 or 4.4 via PC Companion or OTA ? I'm assuming this is with the bootloader remaining locked.
Also, assuming I decide to root and flash using a stock ROM are there any CONS...ie. Wifi or NFC issues ?
Thanks!

goon3r said:
Hi All,
I have T-Mobile branded C6606 and have been considering rooting so that I can flash a c6603 stock ROM. I know the bootloader is locked on the device but here is my question:
If I flash a stock ROM and basically make the phone act as a 6603, will I get updates directly from Sony for example will I be able to upgrade to 4.3 or 4.4 via PC Companion or OTA ? I'm assuming this is with the bootloader remaining locked.
Also, assuming I decide to root and flash using a stock ROM are there any CONS...ie. Wifi or NFC issues ?
Thanks!
Click to expand...
Click to collapse
No issues. It will perform as a 6603. Only thing you will loose is wifi calling... I'm typing this from a 6606 right now on rooted 4.3 ES firmware.
You need to flash a (.67) or (.74) rom first, root it, install recovery, and then you can install a (.569) pre-rooted rom. Make sure you set your apn correctly for mms functioning.
You can use this as your final update for now:
http://forum.xda-developers.com/showthredad.php?t=2583333
Please post questions in q&a section next time.
Sent from my C6603 using XDA Premium 4 mobile app

Thanks for the info Grogg.
I'm curious though, why is it that I should install the older (.67 or 74) ROM first ? I was actually planning to root, install CWM then simply find a Generic unbranded ROM to flash.
GROGG88 said:
No issues. It will perform as a 6603. Only thing you will loose is wifi calling... I'm typing this from a 6606 right now on rooted 4.3 ES firmware.
You need to flash a (.67) or (.74) rom first, root it, install recovery, and then you can install a (.569) pre-rooted rom. Make sure you set your apn correctly for mms functioning.
You can use this as your final update for now:
http://forum.xda-developers.com/showthredad.php?t=2583333
Please post questions in q&a section next time.
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

goon3r said:
Thanks for the info Grogg.
I'm curious though, why is it that I should install the older (.67 or 74) ROM first ? I was actually planning to root, install CWM then simply find a Generic unbranded ROM to flash.
Click to expand...
Click to collapse
Because you cannot root the 4.3 roms directly without an unlocked bootloader. The way I described is the only option for now.
Sent from my C6603 using XDA Premium 4 mobile app

Im on existenzv5 locked bl rooted c6606 tmobile running great

So I flashed a stock 6603 ES ROM (10.31.A.2.67), been testing it and no issues so far. Happy to get rid of some of the T-Mobile bloatware.
Since 4.3 is already out for the C6603 , I was expecting an OTA or PC Companion to prompt me to update to 4.3 (shows 6603). Am I missing something here ?
I haven't rooted or done anything else apart from the ROM Flash. To be honest I don't have much desire for Custom ROMs or need Root access, just a desire to get faster updates and less bloat. If I can get a stock 4.3 on the device I may leave it like that. The most important thing for me though is to just be able to get updates.
Wondering if I should start a new thread in the QA forum or if a MOD can simply move this one.

goon3r said:
So I flashed a stock 6603 ES ROM (10.31.A.2.67), been testing it and no issues so far. Happy to get rid of some of the T-Mobile bloatware.
Since 4.3 is already out for the C6603 , I was expecting an OTA or PC Companion to prompt me to update to 4.3 (shows 6603). Am I missing something here ?
I haven't rooted or done anything else apart from the ROM Flash. To be honest I don't have much desire for Custom ROMs or need Root access, just a desire to get faster updates and less bloat. If I can get a stock 4.3 on the device I may leave it like that. The most important thing for me though is to just be able to get updates.
Wondering if I should start a new thread in the QA forum or if a MOD can simply move this one.
Click to expand...
Click to collapse
There may or may not be an update available depending on the customization number you flashed. Either way, if you flashed a stock ftf then you will receive updates as they become available for your customization number.
Sent from my C6603 using XDA Premium 4 mobile app

Ok. Ignorance on my part. I was under the impression that the builds were generic enough that all would be eligible for updates.
The FTF I used was from this page:
http://forum.xda-developers.com/showpost.php?p=45856753&postcount=1
Can you point me at or recommend an FTF then ? I'm going to be giving the phone to a family member in a few weeks and just want them to at least be able to get regular updates.
GROGG88 said:
There may or may not be an update available depending on the customization number you flashed. Either way, if you flashed a stock ftf then you will receive updates as they become available for your customization number.
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Generic ES 4.3 has been released. You should be getting an update to (.569). You can check firmware versions here:
http://forum.xda-developers.com/showthread.php?p=42234656
There is an ftf available for that update though, so you could go that route.
Download here:
http://forum.xda-developers.com/showthread.php?p=48974188
Sent from my C6603 using XDA Premium 4 mobile app

While I wait for the 4.3 ROM in that link (taking 3+ hours so far), I decided to try a generic UK Rom.
http://forum.xda-developers.com/showthread.php?t=2404211
I got prompted for an OTA update which completed fine, no prompt for 4.3 since though. Is it just a case of waiting or am I missing something ? When I use flashtool I am leaving everything at default only excluding baseband.
GROGG88 said:
Generic ES 4.3 has been released. You should be getting an update to (.569). You can check firmware versions here:
http://forum.xda-developers.com/showthread.php?p=42234656
There is an ftf available for that update though, so you could go that route.
Download here:
http://forum.xda-developers.com/showthread.php?p=48974188
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

goon3r said:
While I wait for the 4.3 ROM in that link (taking 3+ hours so far), I decided to try a generic UK Rom.
http://forum.xda-developers.com/showthread.php?t=2404211
I got prompted for an OTA update which completed fine, no prompt for 4.3 since though. Is it just a case of waiting or am I missing something ? When I use flashtool I am leaving everything at default only excluding baseband.
Click to expand...
Click to collapse
You can try rebooting and checking again. Did you ever perform a factory reset? If not, do it.
Also, the baseband really doesn't need to be excluded. I've seen no benefits in keeping any of the t-mobile garbage.
Sent from my C6603 using XDA Premium 4 mobile app

Refer to this thread http://forum.xda-developers.com/showthread.php?t=2311211
There will be some folder you may have to delete from PCC data because it is cached and PCC will still see your device with the old customization. It is explained in that 1st post.

GROGG88 said:
You can try rebooting and checking again. Did you ever perform a factory reset? If not, do it.
Also, the baseband really doesn't need to be excluded. I've seen no benefits in keeping any of the t-mobile garbage.
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I took your advice and reflashed with baseband and also did the factory reset. The baseband left me with weak LTE in areas where I normally have full bars. In the end the update still didn't show allowing me to move to 4.3. I ended up just flashing the 4.3 ES rom that you linked to and have been liking it so far.
I really would like to have a better understanding of how/why I wasn't getting the update prompts.
SmallsXD said:
Refer to this thread http://forum.xda-developers.com/showthread.php?t=2311211
There will be some folder you may have to delete from PCC data because it is cached and PCC will still see your device with the old customization. It is explained in that 1st post.
Click to expand...
Click to collapse
I actually looked into this, but at one point after flashing but didn't have any folder to delete. Also, after the last flash I connected to a brand new laptop that had never had PCC installed or seen the phone before and the result was the same. No update could be found.
I appreciate the suggestions so far, I'd love to know what else I can try though as I'd like to have the phone get regular updates independent of T-Mobile.

GROGG88 said:
Generic ES 4.3 has been released. You should be getting an update to (.569). You can check firmware versions here:
http://forum.xda-developers.com/showthread.php?p=42234656
There is an ftf available for that update though, so you could go that route.
Download here:
http://forum.xda-developers.com/showthread.php?p=48974188
Sent from my C6603 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here are the steps I am taking to root my tmobile c6606 on a c6603 4.3 rom. It has been unsuccesful. I would like help.
I have used flashtool-0.9.13.0-windows tool.
I use it to successfully install Xperia Z (C6603)_10.4.B.0.569_Generic ES tft.
It is fully fuctional and works with no problems.
However.
I have tried the Root_with_Restore_by_Bin4ry_v33 tool that roots the C6606 succesfully when I have the original factory rom installed.
BUT when I have this 4.3 Generic ES rom installed it will not root. It says I need to enable USB Debugging. I do that. The the phone shows it is in that mode, but the root program will not see it in that mode.
Therefore, rooting can not occur..
What do I do?
Id like to root so I can install my special apps and remove bloat.
Thanks

nickcaper said:
Here are the steps I am taking to root my tmobile c6606 on a c6603 4.3 rom. It has been unsuccesful. I would like help.
I have used flashtool-0.9.13.0-windows tool.
I use it to successfully install Xperia Z (C6603)_10.4.B.0.569_Generic ES tft.
It is fully fuctional and works with no problems.
However.
I have tried the Root_with_Restore_by_Bin4ry_v33 tool that roots the C6606 succesfully when I have the original factory rom installed.
BUT when I have this 4.3 Generic ES rom installed it will not root. It says I need to enable USB Debugging. I do that. The the phone shows it is in that mode, but the root program will not see it in that mode.
Therefore, rooting can not occur..
What do I do?
Id like to root so I can install my special apps and remove bloat.
Thanks
Click to expand...
Click to collapse
You cannot root any 4.3 rom directly without unlocking the bootloader. As you have a C6606, you cannot do that.
You will have to downgrade to a 4.2.2 rom, root, then flash a prerooted 4.3 rom.
This information is readily available all over this section, so a search probably would have got you the information you needed.
Forum rules.
Sent from my C6603 using Tapatalk

Why does it work better rooted ?

Hi peeps.
I was rooted a while back. Had problems with phone freezing mostly when using camera.
Sooo i unrooted, relocked bootloader and then used the Sony update to repair. So ive been on .757 pure stock and i got more problems with that, touchscreen was weird from time to time. It rebooted once a day and it didnt matter wich task i was doing it seems (when rooted it only happened during use of camera and mostly AR effects). So now i became random reboots.
Well i rerooted now and now i can use the AOSP brower again(thank god for that) and most things i wanna have working are working. Havent tested it for that long yet when rerooted but keeping fingers crossed that it will work like it should. Possibly some random reboots wich i dunno whats causing them.
But isnt it strange.
I was wondering about something though. Scrolling seems not so smooth when rooted, but that might be placebo kicking in.
/Jonas

I was wrong It worked just as bad with rootaccess now. So I repaired the phone again with Sony update.
I just wanna get rid if this phone now, it gives me me a headache!!!
Sent from my C6903 using XDA Free mobile app

if you get reboots on Custom Roms with Custom Kernels, well, it's not strange to me, it happen many time, BUT if you get random reboots on Stock, then I will should be worry about it. For all the other reasons you have to have them less on stock, if you really still have all this issues then I will replace it via warranty. I heard some Xperias was not fixed with any Firmware.

Well that's just it. I have reboots on stock rom with stock kernel. Usually once every day. I can't get rid of it. I've repaired and repaired and it is still the same.
Here is the funny part, the warranty of the phone expired one month before I even bought it when I was in touch with Sony. I have abit of an argue with my retailer atm since he says it's software related. And im saying I wanna return it. And get either money back or a new working phone.
Sent from my C6903 using XDA Free mobile app

Reflash stock rom via flashtool. It sounds like your just repairing the device. Do factory reset and flash stock rom.do a back up first.
Sent from my C6906 using XDA Free mobile app

I am on .136 stock (4.3), no root, no unlocked bootloader... all works fine...I have read so many people complaining about newer updates to .681 or .757 .... I do not see any point updating to newer versions, as I am not missing anything major with .136

Jonas740 said:
Hi peeps.
I was rooted a while back. Had problems with phone freezing mostly when using camera.
Sooo i unrooted, relocked bootloader and then used the Sony update to repair. So ive been on .757 pure stock and i got more problems with that, touchscreen was weird from time to time. It rebooted once a day and it didnt matter wich task i was doing it seems (when rooted it only happened during use of camera and mostly AR effects). So now i became random reboots.
/Jonas
Click to expand...
Click to collapse
That isn't anything to do with rooting m8, how you flash your phone and what you flash onto your phone, the apps you use or don't use and your actual habits you have, these are some of the things which cause random reboots and problems for the most part, the other is bad luck and hardware issues.
Particular devices did have some rebooting issues, I myself haven't had one in a long time so i don't get them at all, whether i'm on a custom rom or an AOSP rom, I do get the occasional slow down but there isn't a phone out there or PC for that matter that never slows down at any time.
What I would say to do is to clean up your internal and external memory and download a tried and tested rom, lets say monxified 6.0.3
Go back to 534 and re-root, install a custom recovery and flash that bad boy (don't forget to perform a full wipe, factory, cache and dalvic) use a full FTF to fill in the blanks using flashtool (avoid flashing system and TA , exlude wiping with flashtool) Do not restore using recovery either.
Don't flash a custom kernel either, just let the system boot and see how it runs, install one or two apps (not a massive restoration using titanium) Avoid xposed for now and reboot the phone.
See if you can leave it like that for a while and see if you get any random reboots.
Do it by the numbers methodically and you should be fine
Good luck

How do I wipe everything with flashtool.
Last time I rooted I flashed 681 with flashtool. Had strange reboots then aswell.
Let me say this, I have unlocked the bootloader and I do not have backup on my TA. Wouldn't older roms then 681 mess up my phone? Bootloader is relocked with flashtool and I ain't rooted and I don't have CWM installed anymore.
So easiest way to clear the phone would then be? And I want to use Stable Sony rom.
Guide me step by step like if was a complete idiot
Sent from my C6903 using XDA Free mobile app

Jonas740 said:
Let me say this, I have unlocked the bootloader and I do not have backup on my TA. Wouldn't older roms then 681 mess up my phone? Bootloader is relocked with flashtool and I ain't rooted and I don't have CWM installed anymore.
Click to expand...
Click to collapse
If you don't have TA then I don't understand why you relocked your bootloader with Flashtool, it not make sense to me.
Jonas740 said:
So easiest way to clear the phone would then be? And I want to use Stable Sony rom.
Click to expand...
Click to collapse
Unlock Booltloader, Flash a Stock FTF and wipe everything, then proceed with the steps to gain Root.
Jonas740 said:
Guide me step by step like if was a complete idiot
Click to expand...
Click to collapse
You know the steps. ..LOL..

I locked just for camera tests.
But when you say "wipe". Doesn't flashtool already wipe all if I flash a stock rom?
Sent from my C6903 using XDA Free mobile app

Jonas740 said:
I locked just for camera tests.
Click to expand...
Click to collapse
Without DRM Keys the test is useless, but maybe you know now from fact that it not change.
Jonas740 said:
But when you say "wipe". Doesn't flashtool already wipe all if I flash a stock rom?
Click to expand...
Click to collapse
Yes, this is what I meant, just click on Wipe Data, Appslog and Cache. Still not a full format of your system partition but this is what it do to make a clean installation.

Well I did that a few days after I received my phone. I had the same problems back then. I actually did just that one hour before making this post aswell. Hoping it would work good, which it didn't.
If the phone would have been in my possession a little longer I would run it over with my car. Now it's quite new so I won't do that but I'm really tired of it and it's so boring have to send it to my retailer for repairs and w8 forever. Then when I get it back. I BET that they only will flash new software and test it for five min and ship it back and it will still have the same problem.
Been there done that alot of times with other things
Sent from my C6903 using XDA Free mobile app

(Comment removed. Made a stupid derp)

I was thinking rolling back to 4.3 though to see if that would be more stable. Noticed that, if the phone don't reboot in a day wich it normally does then the touch is acting weird instead.
And last night I stopped it from rebooting, I pressed the power button to turn of screen when it frooze and that cancelled the reboot. But after that I noticed some apps with camera didn't work.
Sent from my C6903 using XDA Free mobile app

I think something like a Tool to format the entire system partition will be useful but in your case I think it will not help much.

Mega wipe Google it. Back up first as it'll nuke your memory.
Sent from my C6903 using XDA Premium 4 mobile app

Well now I have wiped the phone using cvm. And I flashed 4.3 instead hoping the phone will be stable. If it ain't it's going in the bin
I do miss the emoji keyboard, but that's about it. Know if it's possible to get that on 4.3?
Phone feels alot faster on 4.3, the camera reacts faster and tbh the pictures look better. No problems so far, hoping it will work. Battery time is also ALOT better!
Sent from my C6903 using XDA Free mobile app