Xperia X10 Forum

Hello,
I'm fairly coherent when it comes to this type of stuff, but currently i have no access to a windows PC, so i haven't been able to try. was wondering before going out and borrowing one, do the common methods of debranding to region generic firmware still work with a phone already running 2.1, baseband 2.0.46? i might just give it a shot on my dads windows 7 pc tomorrow when i go for dinner, but if there is any issues with doing so in the 2.1 firmware i would rather not, this is my home/mobile phone and my only connection to my social circle of friends/family, as i am almost never home.
Any information is greatly appreciated.
apologies in advance if i missed this somewhere, been googling for a few days, mind you after work when im barely awake...
Cheers.
Ty.

Honestly, I don't understand what you are trying to say or ask. Can you be more specific in a clear English language?

I think I understand, is your phone provider branded and you want to debrand it but your hesitant because your running 2.1?
If this is the case then flashing any of the available generic 2.1 firmwares from XDA using Flashtoll will debrand your handset with no detrimental effects to the phone.
I suggest you have a look here at Androxyde and Bin4ry's Flashtool which also has some regional generic firmwares.

Hope that helps.

Swyped from my ZDZ Froyo X10i with Tapatalk Pro

wolf87ca wrote:do the common methods of debranding to region generic firmware still work with a phone already running 2.1, baseband 2.0.46? i might just give it a shot on my dads windows 7 pc tomorrow when i go for dinner, but if there is any issues with doing so in the 2.1 firmware i would rather not

From here, I understand that you want to debrand your operator-branded phone. And by common methods, I'm interpret that you are referring to the 1.6 methods. No they do not work. You have to either change the customer fingerprint from 1.6, and flash a debranded firmware by tricking SEUS (only at 1.6) or you have to do what JayJ suggested, which is to use flashtool.
Flashtool is really easy. Download it, download the firmware you want to flash, copy it into the firmware folder, click flash, connect to flash mode, follow onscreen instructions

There is multiple ways in doing this.
FlashTool is by far the easiest, but also limited to what's available.

With CDA numbers you can change to any specific region you want as long as you stay within your X10a or X10i region.
Because changing the CDA on an X10a to an X10i will render the device non-recognizable to SEUS and PCC (which is the programs you need to work in this scenario).

In the latest update of SEUS they've made us CDA changers have to change the build.prop as well as the cust.prop.

So the old 1.6 method is still viable just slightly changed from default.prop to build.prop & cust.prop now.

arkedk wrote:There is multiple ways in doing this.
FlashTool is by far the easiest, but also limited to what's available.

With CDA numbers you can change to any specific region you want as long as you stay within your X10a or X10i region.
Because changing the CDA on an X10a to an X10i will render the device non-recognizable to SEUS and PCC (which is the programs you need to work in this scenario).

In the latest update of SEUS they've made us CDA changers have to change the build.prop as well as the cust.prop.

So the old 1.6 method is still viable just slightly changed from default.prop to build.prop & cust.prop now.

Not required to change anything in the "cust.prop" file. (I don't even know if it exists ). Just change in the build.prop and you are all done.

prathaban wrote:

arkedk wrote:There is multiple ways in doing this.
FlashTool is by far the easiest, but also limited to what's available.

With CDA numbers you can change to any specific region you want as long as you stay within your X10a or X10i region.
Because changing the CDA on an X10a to an X10i will render the device non-recognizable to SEUS and PCC (which is the programs you need to work in this scenario).

In the latest update of SEUS they've made us CDA changers have to change the build.prop as well as the cust.prop.

So the old 1.6 method is still viable just slightly changed from default.prop to build.prop & cust.prop now.

Not required to change anything in the "cust.prop" file. (I don't even know if it exists ). Just change in the build.prop and you are all done.

Nope since SE updated SEUS it is necessary, else SEUS will just say you got the latest software without giving you the button for re-installing.

I wrote the whole process down long ago over at XDA, you can check it out here:
http://forum.xda-developers.com/showthread.php?t=824711

arkedk wrote:Nope since SE updated SEUS it is necessary, else SEUS will just say you got the latest software without giving you the button for re-installing.

I wrote the whole process down long ago over at XDA, you can check it out here:
http://forum.xda-developers.com/showthread.php?t=824711

Since when you think that it's necessary? I haven't tried it for few months, but I'm pretty sure that the cust.prop file is out of the scope.

prathaban wrote:

arkedk wrote:Nope since SE updated SEUS it is necessary, else SEUS will just say you got the latest software without giving you the button for re-installing.

I wrote the whole process down long ago over at XDA, you can check it out here:
http://forum.xda-developers.com/showthread.php?t=824711

Since when you think that it's necessary? I haven't tried it for few months, but I'm pretty sure that the cust.prop file is out of the scope.

Since they updated SEUS to check both build.prop and cust.prop for matching CDA's. Which they did from version 2.11.3.5.

arkedk wrote:

prathaban wrote:

arkedk wrote:Nope since SE updated SEUS it is necessary, else SEUS will just say you got the latest software without giving you the button for re-installing.

I wrote the whole process down long ago over at XDA, you can check it out here:
http://forum.xda-developers.com/showthread.php?t=824711

Since when you think that it's necessary? I haven't tried it for few months, but I'm pretty sure that the cust.prop file is out of the scope.

Since they updated SEUS to check both build.prop and cust.prop for matching CDA's. Which they did from version 2.11.3.5.

Interesting! I didn't know that. Seems I learned new thing today . Thanks.

Thanks for all the info,
Yes essentially I was just looking to flash my firmware to x10a generic, I was half asleep and kinda incoherent, so I apologize for the confusion, I had seen the android 1.6 method, but did not think it would work with the 2.1 firmware. What I will probably end up trying is the flashtool method, although back to working 7 days a week so that will have to wait for now.
Thanks again for all the input though.
Cheers.