Database Develop

[Q] How can I dump the firmware from the current phone system

I tried to search it but no luck.
I have a Xperia TX and I want to dump the firmware out from it.
is it possible to do that. it's a unlocked stock firmware and not a ROOTed phone.
Thanks

xcody said:
I tried to search it but no luck.
I have a Xperia TX and I want to dump the firmware out from it.
is it possible to do that. it's a unlocked stock firmware and not a ROOTed phone.
Thanks
Click to expand...
Click to collapse
Read the second post in the all in one thread about creating a ftf file.
That will give you the latest software on a ftf file. However, if you have an update due and want to back up the system you are on its trickier.
Best bet is to do an adb pull of system and use dsixdas kitchen to convert it to a .zip file. But you will need to be rooted and have cmw to restore it.
My advice (As its given in the all in one thread) is to make an ftf as soon as you get your phone or as soon as you update in order to be able to flash it back when you want.
The ftf files you make from this method are completely stock.
EDIT
Unlocked but not rooted? What would be the point in doing that?

Thanks gregbradley,
It's unlocked because I got it as unlocked. not root because it's for my wife. she doesn't need a root phone. lol
Anyway, I guess this can't be done without rooting the phone. nvm then.
gregbradley said:
Read the second post in the all in one thread about creating a ftf file.
That will give you the latest software on a ftf file. However, if you have an update due and want to back up the system you are on its trickier.
Best bet is to do an adb pull of system and use dsixdas kitchen to convert it to a .zip file. But you will need to be rooted and have cmw to restore it.
My advice (As its given in the all in one thread) is to make an ftf as soon as you get your phone or as soon as you update in order to be able to flash it back when you want.
The ftf files you make from this method are completely stock.
EDIT
Unlocked but not rooted? What would be the point in doing that?
Click to expand...
Click to collapse

xcody said:
Thanks gregbradley,
It's unlocked because I got it as unlocked. not root because it's for my wife. she doesn't need a root phone. lol
Anyway, I guess this can't be done without rooting the phone. nvm then.
Click to expand...
Click to collapse
Ahh, you dont mean unlocked, you mean sim unlocked. Unlocked for devs means bootloader unlocked.
also, you do not need to be rooted to make a ftf file.
read the instructions in the link

Hi Gregbradley,
I tried to search the forum and googled it also, but I only can find the way to make ftf from the file that downloaded by using Sony PC Companion or SEUS. But not from the phone itself.
What I need is the firmware from the phone.
gregbradley said:
Ahh, you dont mean unlocked, you mean sim unlocked. Unlocked for devs means bootloader unlocked.
also, you do not need to be rooted to make a ftf file.
read the instructions in the link
Click to expand...
Click to collapse

xcody said:
Hi Gregbradley,
I tried to search the forum and googled it also, but I only can find the way to make ftf from the file that downloaded by using Sony PC Companion or SEUS. But not from the phone itself.
What I need is the firmware from the phone.
Click to expand...
Click to collapse
take a backup using recovery and use that system. img in dsixdas kitchen
but that involes rooting.
As i said in previousposts, thats why it should be done as sooner rather later.
Listen, just update and use the new firmware, dont sweat it

[Q] C6906 - Flashing .290 branded to .290 generic

Hello,
I recently bricked my Z1 and just got it back from warranty repaired. It is a C6906 that they upgraded to 4.3 (.290) however it is branded to BELL and I wish to flash the unbranded generic so I don't have as much bloatware/fast updates.
Since I do not wish to brick the device again and go through this again and so I am looking for advice to do this in a way that is guaranteed. With flashtool if I flash "C6906 14.2.A.0.290 Generic CA 1276-7484_R2B" would I have any issues at all? Just load up Flashtool - select the ftf and just use the default settings and plug in the Z1 while holding down the volume button.

I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.

eclyptos said:
I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.
Click to expand...
Click to collapse
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.

magwart said:
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.
Click to expand...
Click to collapse
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.

eclyptos said:
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.
Click to expand...
Click to collapse
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Edit: Successfully flashed. Thanks again.

magwart said:
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Click to expand...
Click to collapse
No direct root, like Vroot or 360, for .290 at the moment, just a method to get full root for Locked Bootladers. To do that you have to downgrade, root, install recovery then update to .290 again, a bit longer to get root on your phone, sure this method working for C6902/3 but should work for C6906 too, just check.

Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol

akusokuzan said:
Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol
Click to expand...
Click to collapse
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.

eclyptos said:
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.
Click to expand...
Click to collapse
Lol yeah, when I was trying to update with root, it didn't go so hot. That thread wasn't stickied until after the debacle. Sounds good though, thanks!

Revert to stock.

I want to return to stock 12.0.A.2.254 firmware from an unlock XSP with cm10.1 and i have an ftf file (I downloaded from the inernet) as well as the flashtool to do so but I heard that flashing a stock ftf will relock the bootloader.Therefore I have three questions:
1) Will any ftf file work? Do I need a specific one for my phone? Will a Generic ftf from any country work?
2) If the bootloader is relocked,Will it be unlocked the same way as it was before? will the same codes (unlock key/IMEI) be used as when I unlocked the phone for the first time?
3) Is there a way to flash stock ftf without the bootloader getting relocked? If so then can someone give me detailed instructions?
I don't mind losing root access as long as the booloader is unlocked therefore I personally wanna go with the third method but I have got no Idea on how to go about it.Some help would be EXTREMELY appreciated.
Also I want to apologize if something like this has been asked before but I was not able to find a similar topic or a topic that could answer my questions.
Thanks.
P.S
I just found a "loader.sin" file in the ftf that I have.I don't know if it has anything to ddo with the bootloader or not.So will including that in the flashing sequence relock the bootloader? Does "loader.sin" have anything to do with the booatloader? Should I exclude it while flashing the ftf and will that result in a faulty flash?
Help would be appreciated.

It won't re-lock your phone's bootloader.
Any ftf will do but advisable to use back the one with same customization version that your phone came with originally.
Tapatalked from my Xperia

Rycon33 said:
It won't re-lock your phone's bootloader.
Any ftf will do but advisable to use back the one with same customization version that your phone came with originally.
Tapatalked from my Xperia
Click to expand...
Click to collapse
I dont know my customization number.I mever checked for it neither did i back it up.Is there anyway to find it in cm or is it lost forever?

Then just flash any generic ftf for your phone model C5303 and it will also be fine. It will also be fine.
Tapatalked from my Xperia

delete please
Please delete this thread

[Q] Unable to downgrade to .534 after mainboard change!

I have rooted my Z1 many times without problem, first downgraded to .534, root with Bin4ry's root tool, then flash the .zip file from recovery and flash stripped .ftf with FlashTool.
By rooting this way I can keep my bootloader locked.
A couple of weeks ago I had to send my phone for repairs when the call speaker gave up and they changed the mainboard (new IMEI).
After this I can not downgrade to .534 anymore! It will stuck at a bootloop, with only the Sony logo showing. Downgrading to .257 (the version after .534) is no problem though.
I have tried many different .534 tft-files, including NUT's.
Any ideas? Could this new mainboard be incompatible with the oldest firmwares? Sounds unlikely to me.
Thanks!

dape16 said:
I have rooted my Z1 many times without problem, first downgraded to .534, root with Bin4ry's root tool, then flash the .zip file from recovery and flash stripped .ftf with FlashTool.
By rooting this way I can keep my bootloader locked.
A couple of weeks ago I had to send my phone for repairs when the call speaker gave up and they changed the mainboard (new IMEI).
After this I can not downgrade to .534 anymore! It will stuck at a bootloop, with only the Sony logo showing. Downgrading to .257 (the version after .534) is no problem though.
I have tried many different .534 tft-files, including NUT's.
Any ideas? Could this new mainboard be incompatible with the oldest firmwares? Sounds unlikely to me.
Thanks!
Click to expand...
Click to collapse
If it's incompatible with 534 then i'd be surprised, my guess is that it's a dodgy download and you should re-download the FTF file or an alternative and make sure it's the only thing that your computer is doing at the time, even check the MD5 checksum if it's available.
Are you flashing the full FTF file when downgrading and allowing for a wipe?
Only problem i've had when downgrading is losing the IMEI but after you've rooted , installed a custom recovery and installed a custom rom that'll come back anyway.

dladz said:
If it's incompatible with 534 then i'd be surprised, my guess is that it's a dodgy download and you should re-download the FTF file or an alternative and make sure it's the only thing that your computer is doing at the time, even check the MD5 checksum if it's available.
Are you flashing the full FTF file when downgrading and allowing for a wipe?
Only problem i've had when downgrading is losing the IMEI but after you've rooted , installed a custom recovery and installed a custom rom that'll come back anyway.
Click to expand...
Click to collapse
Thanks, yes I have tried with 5 different .534 ftf-files, all of them resulting in this bootloop. I am doing a full flash with wipe. Downgrading to .257 is working fine though, but then I cant root.
I am running out of ideas

dape16 said:
Thanks, yes I have tried with 5 different .534 ftf-files, all of them resulting in this bootloop. I am doing a full flash with wipe. Downgrading to .257 is working fine though, but then I cant root.
I am running out of ideas
Click to expand...
Click to collapse
Are you branded? What model is the phone C6903? C6902?
don't forget the obvious stones

dladz said:
Are you branded? What model is the phone C6903? C6902?
don't forget the obvious stones
Click to expand...
Click to collapse
It's not branded. No SIM-lock, Generic_NCB customization. C6903.
Now I have tried with older versions of FlashTool and I tried other USB-ports too, but no success. Newer firmwares then .534 flashes just fine.

dape16 said:
It's not branded. No SIM-lock, Generic_NCB customization. C6903.
Now I have tried with older versions of FlashTool and I tried other USB-ports too, but no success. Newer firmwares then .534 flashes just fine.
Click to expand...
Click to collapse
Which version of flashtool are you using currently? I've found that some firmwares just don't like the older flashtools.
What about different USB cables? Shouldn't make any difference but I thought I'd ask. I find it odd the way it'll work for newer but not older firmwares, perhaps someone else should chime in with an idea.
I'm all out, as this isn't something i've come across and everything i'd try myself i've told you.

dladz said:
Which version of flashtool are you using currently? I've found that some firmwares just don't like the older flashtools.
What about different USB cables? Shouldn't make any difference but I thought I'd ask. I find it odd the way it'll work for newer but not older firmwares, perhaps someone else should chime in with an idea.
I'm all out, as this isn't something i've come across and everything i'd try myself i've told you.
Click to expand...
Click to collapse
Thanks for your help.
Now I have tried with another computer and another USB-cable, and also tried to flash the older .526 and .518 firmwares. Tried FlashTool 0.9.1.6 and .5 and .4.
Same result.
Seems very strange that this new mainboard should not be compatible with these firmwares?

dape16 said:
Thanks for your help.
Now I have tried with another computer and another USB-cable, and also tried to flash the older .526 and .518 firmwares. Tried FlashTool 0.9.1.6 and .5 and .4.
Same result.
Seems very strange that this new mainboard should not be compatible with these firmwares?
Click to expand...
Click to collapse
It does seem strange and i'm pretty much out of ideas myself for you m8. Mad one that.

dladz said:
It does seem strange and i'm pretty much out of ideas myself for you m8. Mad one that.
Click to expand...
Click to collapse
Thanks anyway, I hope somebody else has an idea

dape16 said:
Thanks anyway, I hope somebody else has an idea
Click to expand...
Click to collapse
click thanks dude,
Hope you work it out
Just had a thought, can't you now root later firmwares?

dladz said:
click thanks dude,
Hope you work it out
Just had a thought, can't you now root later firmwares?
Click to expand...
Click to collapse
I dont think it is possible to root any firmware later then .534? Not without unlocking bootloader?

dape16 said:
I dont think it is possible to root any firmware later then .534? Not without unlocking bootloader?
Click to expand...
Click to collapse
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery

gregbradley said:
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery
Click to expand...
Click to collapse
Thanks, but I have tried both vroot and Bin4ry's root tool on .257. Didn't work. Is there any other method for rooting?
Edit: Sorry, didn't see the link in your signature, will try that.

dape16 said:
Thanks, but I have tried both vroot and Bin4ry's root tool on .257. Didn't work. Is there any other method for rooting?
Edit: Sorry, didn't see the link in your signature, will try that.
Click to expand...
Click to collapse
DO NOT USE VROOT!!!!
It send your IMEI number to an IP address in china..
I cant believe people still do not know this

gregbradley said:
DO NOT USE VROOT!!!!
It send your IMEI number to an IP address in china..
I cant believe people still do not know this
Click to expand...
Click to collapse
Well, I tried vroot because it is in the first posts in the "Ultimate Xperia Z1 Guide" sticky thread.
Since I have always used Bin4ry's tool, I guess I have not noticed any thread about vroot being dangerous.

gregbradley said:
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery
Click to expand...
Click to collapse
Right now I have .257 firmware flashed which is a 4.2.2.
I have tried to root with Bin4ry, vroot, Kingo, and [NUT]s recovery, but it is not possible.
Everywhere I look people say that it is a must to downgrade to .534 when rooting with a locked bootloader.
What have I missed?
Thanks,

257 was the first one that closed that exploit, you have to go back further.
I know you say 534 does not flash for you, but what error does flashtool give?

gregbradley said:
257 was the first one that closed that exploit, you have to go back further.
I know you say 534 does not flash for you, but what error does flashtool give?
Click to expand...
Click to collapse
Thank you, I misunderstood an thought .257 was rootable too.
No error in Flashtool, flashes fine but is stuck on bootloop with Sony logo.
Tried .518, .526 and .534

make sure you do not exclude any part of the FTF and wipe everything,
Can you get a log from the phone?
Make sure you backup and clean your sdcard (So there is no trace of recovery files on there)

gregbradley said:
make sure you do not exclude any part of the FTF and wipe everything,
Can you get a log from the phone?
Make sure you backup and clean your sdcard (So there is no trace of recovery files on there)
Click to expand...
Click to collapse
I have cleaned the internal sdcard and tried without external sdcard and simcard.
Don't think it is possible to get a log file from the phone while in bootloop?
If my new mainboard is incompatible with .534 and older, I guess other users would have the same problem?

Newbie question on Rooting X Performance

My X performance is now running Nougat. I am going to downgrade it back to 6.0.1. And therefore I downloaded the FlashTool. I can install the Flashmode Drivers and Fastboot Drivers. But I can't find the Xperia X Performance drivers in flashtool-0.9.23.1-windows. Do I need to manually download the drivers from https://developer.sonymobile.com/downloads/drivers/xperia-x-performance-driver/ and right click on .inf to install the drivers in Windows?
Secondly, since I never unlock my bootloader, I am going to backup using the backupTA_v2 via the Dirtycow. However, I wonder if I restore the TA partition after I root my phone, would the root also go away? Basically, I want to have my Xperia X performance in root state while having the original TA partition in place so that I can run the PS4 remote play app. As far as I understand, all the DRM recovery patch out there don't fix the PS4 remote play app.
Thanks.

sdugoten said:
My X performance is now running Nougat. I am going to downgrade it back to 6.0.1.
Thanks.
Click to expand...
Click to collapse
Let me know how you go, and how you got the MM ROM? I'm interested but I can't seem to find any MM ROM for my model and country variant.

chris_j26 said:
Let me know how you go, and how you got the MM ROM? I'm interested but I can't seem to find any MM ROM for my model and country variant.
Click to expand...
Click to collapse
I havent' start yet because no one answer my question.
Here is the rom.
http://www.xperiablog.net/forum/resources/categories/xperia-x-performance-dual.102/

If you want to install fastboot driver on windows 7 or later, you must reboot with driver signature enforcement disabled. Here is the video shows you how to install driver.
Restore TA partition will not lose your root access.

sdugoten said:
I havent' start yet because no one answer my question.
Here is the rom.
Click to expand...
Click to collapse
Does this mean I can flash any country variant rom to my phone ?

chris_j26 said:
Does this mean I can flash any country variant rom to my phone ?
Click to expand...
Click to collapse
Yes. Just download the FTF that match your phone model and flash it into your phone using Flashtool.

chris_j26 said:
Let me know how you go, and how you got the MM ROM? I'm interested but I can't seem to find any MM ROM for my model and country variant.
Click to expand...
Click to collapse
Step by step guide
https://forum.xda-developers.com/xperia-x-performance/help/xperia-x-performance-root-7-0-ps4-t3598774

So for backing up the ta does it matter that I will flash UK variant marshmallow on my Australian firmware phone? Sorry I know it sounds like a noob question.

chris_j26 said:
So for backing up the ta does it matter that I will flash UK variant marshmallow on my Australian firmware phone? Sorry I know it sounds like a noob question.
Click to expand...
Click to collapse
We backup TA partition because we want to keep SONY's special functions AFTER unlocking bootloader.
If you just want to flash different variant firmware, you don't need to unlock the bootloader, just find the FTF file and flash it into your phone.

f870103 said:
We backup TA partition because we want to keep SONY's special functions AFTER unlocking bootloader.
If you just want to flash different variant firmware, you don't need to unlock the bootloader, just find the FTF file and flash it into your phone.
Click to expand...
Click to collapse
Ah but I'd like to downgrade to marshmallow(of available UK variant) and then unlock bootloader, root and then XPosed. So is TA even relevant for me?

chris_j26 said:
Ah but I'd like to downgrade to marshmallow(of available UK variant) and then unlock bootloader, root and then XPosed. So is TA even relevant for me?
Click to expand...
Click to collapse
Yes. Since you want to unlock bootloader, backing up TA partition is relevant to you. But you can only backup TA partition on Marshmallow (because SONY fix the dirtycow on Nougat). So you should downgrade first, then backup TA partition, then unlock bootloader.

f870103 said:
Yes. Since you want to unlock bootloader, backing up TA partition is relevant to you. But you can only backup TA partition on Marshmallow (because SONY fix the dirtycow on Nougat). So you should downgrade first, then backup TA partition, then unlock bootloader.
Click to expand...
Click to collapse
Thanks for the tips ?