The u20a is the 850MHz/1900MHz/2100MHz version of the Mini Pro, I figured I'd start a thread to help consolidate information specific to this version of the handset.
If you live in the US, Canada, Central and South America (Check with your carrier), New Zealand (Using NZ Telecom) or Bangladesh, this is the version you want for 3G support.
For Australian's this is the version to buy for use on Telstra and 3 Hutchinson. For Vodafone Au they use both 850 and 900 as well as 2100MHz, if you never go regional you may benefit from the u20a as Vodafone are now deploying 850MHz for infil of some of their their 2100MHz urban networks, their regional and fringe services are 900MHz mostly and require a u20i. Optus is 2100/900 only so you'd want a u20i.
Officially language support for all u20a models seems to be English, Spanish, Portuguese and French with American specific customisations to those languages in most builds.
The u20a currently available in the Australian Market via carriers 3 and Telstra.
As far as I know it is (or will be) available in Canada via Rogers, Through SE and various carriers in Argentina, Brazil, Chile, El Salvador, Peru, Columbia, Mexico and also other parts of Central and South America.
There appears to be a Sony US Generic firmware out now, so it looks like the Mini Pro has been released there or is due to be soon, hopefully it wont take too long to track down the CDF number for this model.
Firmwares and variants list. (needs updating)
Code:
U20a VIVO-1-2-5 CDF1238-9793 1239-7565 Vivo BR/Black
U20a WORLD-1-2-5 CDF1237-6083 1239-7456 Movistar PE/Black
U20a WORLD-1-2-5 CDF1237-6745 1238-2489 Claro PE/Black
U20a WORLD-1-2-5 CDF1238-0148 1238-2495 Comcel 3GSM CO/Black
U20a WORLD-1-2-5 CDF1238-2298 1239-2226 3 AU/Black
U20a WORLD-1-2-5 CDF1238-8213 1239-7684 Customized BR/Black, 1239-7686 Customized BR/Red
U20a WORLD-1-2-5 CDF1238-9769 1239-7432 Telemovil SV/Black
U20a WORLD-1-2-5 CDF1238-9785 1239-7563 Claro BR/Black, 1240-1219 Claro BR/RED
U20a WORLD-1-2-5 CDF1238-9789 1239-7712 Movistar CL/Black
U20a WORLD-1-2-5 CDF1239-0004 1239-7718 Entel PCS CL/Black
U20a WORLD-1-2-5 CDF1239-0006 1239-7701 Claro CL/Black
U20a WORLD-1-2-5 CDF1239-0083 1239-7453 Movistar MX/Black, 1241-2786 Movistar MX/Red
U20a WORLD-1-2-5 CDF1239-2457 1239-2229 Telecom NZ/Black
U20a WORLD-1-2-5 CDF1239-2460 1238-4468 Customized GEL/Black, 1239-6209 Customized GEL/Black, 1240-1185 Customized GEL/Black, 1240-1188 Customized GEL/Red
U20a WORLD-1-2-5 CDF1239-5023 1238-9150 Telstra AU/Black, 1243-2969 Telstra AU/Pink
U20a WORLD-1-2-5 CDF1239-7520 1239-7437 TELCEL GSM MX/Black, 1240-1215 TELCEL GSM MX/Pearl White, 1241-8383 TELCEL GSM MX/Red, 1243-1507 TELCEL GSM MX/Pearl White, 1243-1509 TELCEL GSM MX/Black, 1243-1510 TELCEL GSM MX/Red
U20a WORLD-1-2-5 CDF1240-8130 1240-8004 Movistar GT/Black
U20a WORLD-1-2-5 CDF1242-5721 1242-5537 Customized BD/Pearl White, 1242-5539 Customized BD/Red, 1242-5540 Customized BD/Black
http://www.ptcrb.com/ctiastaff/complete/view_complete_request.cfm?modelid=17493
Root/Debrand info:
The usual tricks work as for the u20i from my experience so check the debrand and root threads etc. The 2.1 update appears to carry a payload for for the 3G radio hardware, as there are multiple reports of u20i software disabling 3G on u20a's, crossflashing is therefore not advised.
Any additional/updated information welcome especially if you have a u20a with a CDF not listed above or can correct or expand existing CDF's
(I decided to remove the CDF's for proto firmware for the time being, as they were carrier branded, I couldn't confirm their authenticity and the brick risk on a regular u20a was high even if they were correct).
Brazil (CDF1238-8213) seems to be the most frequently updated firmware of the generics, running about 4-6 weeks behind UK for the translation additions into Brazilian Portuguese. There is some inherent safety with this as you're unlikely to get bombed with an unrootable update without warning from the UK people getting it a few weeks before.
SE BR seems to be the division with its act together the most and all u20a American versions should support the same language set. (English, Canadian French, Brazil Portuguese, Latin Spanish).
Brazil Generic however uses a qwerty Portuguese/Spanish latin keyboard, to switch to a qwerty English layout, the following needs to be done. So root the phone using your method of choice and make sure usb debugging is turned on. (USB debugging is your safety line if you screw up, it should always be turned on immediately after you flash a new firmware and left on.)
Here you will edit one file and replace another file, I recommend you make copies of the originals before you mess with them.
Firstly edit /system/usr/keyboard-config/keyprint.xml.
Where it says "QWERTY Portuguese" change to "QWERTY"
and the line <script name="latin" keyboard="qwerty-br"> you'll replace the "qwerty=br" to qwerty-en so it reads <script name="latin" keyboard="qwerty-en"> (This changes the keymap for "Default Input" if that is checked in the locale settings and you're in English you'll have qwerty English layout)
For 1.6 Copy /system/usr/keychars/mimmi/keyprints/qwerty-en.kcm.bin to /system/usr/keychars/qwerty.kcm.bin
You need to replace the qwerty.kcm file, you can copy over it or you can rename the original then copy in qwerty-en.kcm.bin and rename it to qwerty.kcm.bin)
(This makes the layout qwerty English, across the board even with "Default Input" off)
On 2.1, SE Brazil didn't include the English qwerty layout, so you'll need to get the .kcm file here.
In this case it's just a drop in replacement for mimmi_keypad.kcm.bin found in /system/usr/keychars/
I personally just did everything above in root explorer because I'm lazy and careful, you may wish to use adb for file operations and do the editing of keyprint.xml on your pc.
After you're done, switch to another language in the phones locale settings and switch back to English, you should then have a English qwerty keyboard.
WARNING: If you need the qwerty english layout on Brazil firmware, keep the following in mind. Every time you update the phone, you will need to root and change the keymap. In the event of an unrootable update you will be stuck with the Portuguese/Spanish layout, so apply updates with some degree of caution.
If you're not comfortable with this, the best firmware option for the qwerty English layout is the CDF1239-2460 GEL firmware, which sadly thus far hasn't seen a single update. The other option is to crossflash to UK Generic for the u20i, I'm unsure if changing to firmware for the u20i model could potentially impact operation of the gsm radio hardware at some stage, at the moment there appears to be no difference in operation of the unit on either firmware.
If you do get stuck on an unworkable firmware, Davinci Team or Omnius can get you back, if you're careful though it shouldn't come to this.
Brazil Generic 1.6 files (not decrypted) from the \blob_fs directory on SEUS/PC Companion for those who wish to update via that method.
http://www.megaupload.com/?d=CSLYZY5Q
Decrypted Brazil u20a 2.1 http://www.megaupload.com/?d=OXMYJ1X0
now i have a U20i but my 3g network need a U20a so i will tray to flash it changing the prop.deb, if my 3g work after that change this mean both hardware are the same..
are some one already make this change and have 3g working??
the diferrence is software or hardware??
Pretty sure the radio hardware is different as there are two distinct models.
i make the change the phone work very good but no 3g, so its a hardware issue..
for all: its very safe to pass between u20i to u20a and come back already done by me...
but this no change the 3g bands
Usually with SE phones the A is just the America version (like for Rogers, at&t etc)
So I do find it a bit odd that when you change it to the U20i version that you lose 3G.
No loss of 3G atm, my concern more was as the two phones have diff radio hardware, software for one may at one stage cause probs if used on the other. It may be a baseless worry and SE may just work on one branch of software for the both phones, or perhaps anything that governs 3G data is set in stone when it leaves the factory.
Not that I like bumping threads, but major updates to the first post made it seem worthwhile.
I have the U20i and I've updated the build.prop file on my phone to the generic UK one and it still says my phone is up to date, when it is not
aPaullyG:
how is the procedure to debrand my X10 Mini Pro (U20a) from Brazil?
I read you mencioned "exploid" and "build.prop". I flashed my X10 (X10a) using the exploid method. Is there any guide teaching me how to do this on my X10 Mini Pro??
Thanks in advance!
aPaullyG said:
If you live in the Americas (North, Central and South), New Zealand (Using NZ Telecom) or Bangladesh, this is the version you want for 3G support.
Click to expand...
Click to collapse
A small correction. The only operator in Brazil which supports this frequency range is VIVO (Movistar, Telefonica). All other operators are using European band allocation. So in fact there are U20a and U20i on the Brazilian market.
vlissine said:
A small correction. The only operator in Brazil which supports this frequency range is VIVO (Movistar, Telefonica). All other operators are using European band allocation. So in fact there are U20a and U20i on the Brazilian market.
Click to expand...
Click to collapse
Então, vlissine...
Thanks for the heads up about the models running different frequencies here in Brazil...
I´ve got a U20a, from VIVO, compilation number 1.1.A.0.9, and I wish to debrand the phone firmware. Can you help me?
I read the topic about the debrand using ADB, but I must confess I´m unaware of SU and root procedures, therefore I´m very affraid to brick my phone.
If you could help...
Thanks in avance!
andrebotinha said:
Então, vlissine...
Thanks for the heads up about the models running different frequencies here in Brazil...
I´ve got a U20a, from VIVO, compilation number 1.1.A.0.9, and I wish to debrand the phone firmware. Can you help me?
I read the topic about the debrand using ADB, but I must confess I´m unaware of SU and root procedures, therefore I´m very affraid to brick my phone.
If you could help...
Thanks in avance!
Click to expand...
Click to collapse
Use Omnius. Fast, reliable and works like a charm. I am not sure they have U20a rom though, check with them first. Mine is U20i.
vlissine said:
Use Omnius. Fast, reliable and works like a charm. I am not sure they have U20a rom though, check with them first. Mine is U20i.
Click to expand...
Click to collapse
Thank you for this advice... I'll give it a try... I'll google it and start looking for it right now!
I'll come later with results...
vlissine said:
The only operator in Brazil which supports this frequency range is VIVO (Movistar, Telefonica). All other operators are using European band allocation. So in fact there are U20a and U20i on the Brazilian market.
Click to expand...
Click to collapse
Thanks, info updated.
andrebotinha said:
aPaullyG:
how is the procedure to debrand my X10 Mini Pro (U20a) from Brazil?
I read you mencioned "exploid" and "build.prop". I flashed my X10 (X10a) using the exploid method. Is there any guide teaching me how to do this on my X10 Mini Pro??
Thanks in advance!
Click to expand...
Click to collapse
Yep check the debrand thread here. The guide is using build.prop edited for generic UK, for generic Brazil u20a you can substitute that with the one from the first post in this thread.
Just to let you guys know U20a Brazil 2.1 update finally came through today. Other updates for the region shouldn't be too far behind with luck.
Could you be so kind to upload the firmware? Stuck on edge here, miss having 3g in my phone.
My X10 mini PRO comes with the number 1239-0006, i get it from Claro Chile, its all black with Chrome parts!
pacoguevara said:
Could you be so kind to upload the firmware? Stuck on edge here, miss having 3g in my phone.
Click to expand...
Click to collapse
NP, just checkin out the decyrpt tool now, haven't used it before. Hopefully what it has spat out is usable.
Thanks. Hope you undestand it. Tried to decrypt my original fw, but got stuck renaming the files. Couldn't tell what was what.
Hi All,
This is my first post so take it easy on me! I have an AT&T X10a which I have debranded using DaVinci Team's client to X10a R2BA026 0001 CUSTOMIZED GEL/LUSTER WHITE NAM_1 firmware. I have a few questions:
1. What region is this firmware for? N. America or S. America?
2. Is this the generic firmware for N. America (or whatever region it is for)?
3. When do I expect my 2.1 update?
Sorry if my questions are naive but, I am dieing to get my hands on 2.1!
Thanks all!
Anyone? Come on guys, I know some of you can help me out please?
it says NAM_1, should stand for North America Generic
DangerPanda said:
it says NAM_1, should stand for North America Generic
Click to expand...
Click to collapse
Hi DangerPanda,
Thanks for your reply. But, almost all of the X10a firmware I found on davinci say NAM_1. Please see below. Does that mean they are all generic? I have highlighted the one which I have flashed. Will I be able to update to 2.1 when it is released using PC companion or SEUS or will I have to flash back to my at&t firmware? I want the generic 2.1 for the X10a. Thanks!
X10a R2BA026 0001 BAND 1-2-5/GENERIC LAM/SENSUOUS BLACK NAM1
X10a R2BA026 0001 CLARO BR/LUSTER WHITE NAM1
X10a R2BA026 0001 CLARO BR/SENSUOUS BLACK NAM1
X10a R2BA026 0001 CLARO DO/SENSUOUS BLACK NAM_1
X10a R2BA026 0001 CLARO PE/SENSUOUS BLACK NAM1
X10a R2BA026 0001 CUSTOMIZED BD/SENSUOUS BLACK NAM1
X10a R2BA026 0001 CUSTOMIZED GEL/LUSTER WHITE NAM_1
X10a R2BA026 0001 CUSTOMIZED GEL/SENSUOUS BLACK NAM_1
X10a R2BA026 0001 CUSTOMIZED MEL/LUSTER WHITE GENERIC
X10a R2BA026 0001 CUSTOMIZED MEL/SENSUOUS BLACK GENERIC
X10a R2BA026 0001 GENERIC LAM/LUSTER WHITE NAM1
X10a R2BA026 0001 GENERIC LAM/SENSUOUS BLACK NAM1
X10a R2BA026 0001 TELCEL GSM MX/LUSTER WHITE NAM1
X10a R2BA026 0001 TELCEL GSM MX/SENSUOUS BLACK NAM1
I am tired of waiting for the update to be released. Should I flash the Global generic 2.1 or wait it out when the X10a generic comes out?
Any news on the North America firmware?
heard it is already out
personally I want LAM xD
alankstiyo said:
heard it is already out
personally I want LAM xD
Click to expand...
Click to collapse
It is out for Rogers in Canada. The generic North/South American is not out yet. I just checked PC companion and OTA and nothing yet.
Not sure if this is where i should post this but i was trying to return my x10 mini pro to its normal state, which the past 2 days would leave me with 2.0.A.0.504 as its build version and the baseband was M76XX-TSNCJOLYM-53404006
Only just as of roughly 35 minutes ago, i had used the same program SEUS from sony ericsson to repair my x10 mini pro. I restarted my phone and checked its settings to find that my model was still U20a with the same firmware version but with a new baseband version number and the new 2.1.1.A.0.6 build version...
Your best bet is to use the flashtool.
http://forum.xda-developers.com/showthread.php?t=928343
Why do you want to use 2.0.A.0.504 vs. 2.1.1.A.0.6? The latest firmware is 2.1.1.A.0.6.
leftAlone said:
Your best bet is to use the flashtool.
http://forum.xda-developers.com/showthread.php?t=928343
Why do you want to use 2.0.A.0.504 vs. 2.1.1.A.0.6? The latest firmware is 2.1.1.A.0.6.
Click to expand...
Click to collapse
No I am just showing people that in Australia if you are on Telstra and have an x10 mini pro that they have released that update now...
We were stuck with 2.0.A.0.504 for months...
i flashed the E15_nAa-11_2.6.29.6-nAa-11.ftf on my xperia x8 so that i could install update-cm-9.0.0-V02-X8-KANG rom. Now i want to revert back to original se rom but there is conflict with the base bands meaning i have to use X8i_2.1.1.A.0.6_Baseband_015 to be able to install but this base band usually doesn have xrecovery so one has to install xrecovery but my current system doesn allow xrecovery to install. am stuck any help?
aulterra said:
No I am just showing people that in Australia if you are on Telstra and have an x10 mini pro that they have released that update now...
We were stuck with 2.0.A.0.504 for months...
Click to expand...
Click to collapse
I hope you've seen this already : http://forum.xda-developers.com/showthread.php?t=1125587
viutalic said:
i flashed the E15_nAa-11_2.6.29.6-nAa-11.ftf on my xperia x8 so that i could install update-cm-9.0.0-V02-X8-KANG rom. Now i want to revert back to original se rom but there is conflict with the base bands meaning i have to use X8i_2.1.1.A.0.6_Baseband_015 to be able to install but this base band usually doesn have xrecovery so one has to install xrecovery but my current system doesn allow xrecovery to install. am stuck any help?
Click to expand...
Click to collapse
Root your device first! Otherwise it is impossible!
My phone is rooted and I have miniCM7pro_v21 installed but:
Recently I wanted to install this ROM on my x10 mini pro : http://forum.xda-developers.com/showthread.php?t=1206625
and when I'm trying to flash it using Clockworkmod I'm getting this abort info:
Code:
Amend scripting (update-script) is no longer supported. Amend scpritping was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 Gingerbread based recovery. please switch to edify scripting (updater-script and update-binary) to create working update zip packages.
and I don't know what to do from here.
second issue: miniCM7Pro-2.1.9-mimmi will flash but in the end it won't work- booting stops on Sony Ericsson.
Also I cannot flash latest naa kernel using flashtool because it shows some error about kernel.sin not valid or sth(later I will post detailed info when I'll come home and try to flash it once again)
can anyone help me?
btw is it normal to this phone to work on battery less than one day?
rzepa90 said:
My phone is rooted and I have miniCM7pro_v21 installed but:
Recently I wanted to install this ROM on my x10 mini pro : http://forum.xda-developers.com/showthread.php?t=1206625
and when I'm trying to flash it using Clockworkmod I'm getting this abort info:
Code:
Amend scripting (update-script) is no longer supported. Amend scpritping was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the clockworkmod 3.0 Gingerbread based recovery. please switch to edify scripting (updater-script and update-binary) to create working update zip packages.
and I don't know what to do from here.
second issue: miniCM7Pro-2.1.9-mimmi will flash but in the end it won't work- booting stops on Sony Ericsson.
Also I cannot flash latest naa kernel using flashtool because it shows some error about kernel.sin not valid or sth(later I will post detailed info when I'll come home and try to flash it once again)
can anyone help me?
btw is it normal to this phone to work on battery less than one day?
Click to expand...
Click to collapse
The ROM u want to install (2.1.1.Clean.0.0 V5) will be flashed by xrecovery only not by CWM as in instructions it is mentioned there...
Also minicm7-2.1.9 will only be working if u first install nAa kernel (for this u will have to unlock ur bootloader ) otherwise u will get a bootloop...
Refer to this for and read instructions carefullyv http://forum.xda-developers.com/showthread.php?t=1415026
deanshu93 said:
The ROM u want to install (2.1.1.Clean.0.0 V5) will be flashed by xrecovery only not by CWM as in instructions it is mentioned there...
Also minicm7-2.1.9 will only be working if u first install nAa kernel (for this u will have to unlock ur bootloader ) otherwise u will get a bootloop...
Refer to this for and read instructions carefullyv http://forum.xda-developers.com/showthread.php?t=1415026
Click to expand...
Click to collapse
so: I need to unlock my bootloader(flash back to stock android than unlock bootloader) than I have to flash with naA kernel stock android after that install miniCM7-2.1.9. But as I said- I can't flash that kernel because of error(Ill post it in about 2h)
how to replace cwm with xrecovery?
rzepa90 said:
so: I need to unlock my bootloader(flash back to stock android than unlock bootloader) than I have to flash with naA kernel stock android after that install miniCM7-2.1.9. But as I said- I can't flash that kernel because of error(Ill post it in about 2h)
how to replace cwm with xrecovery?
Click to expand...
Click to collapse
No you need not to go to stock ROM to unlock bootloader just follow the thread & please carefully read the instructions unless you can brick the phonehttp://forum.xda-developers.com/showthread.php?t=1462278
Then to install the kernel refer to this and read the instructions carefullyhttp://forum.xda-developers.com/showthread.php?t=1415012
OK, right now I'm trying to unlock bootloader. S1tool says :
Code:
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1240-1863_R4B
FILESYSTEM VERSION: VFE-1-8_2.1.1.A.0.6
SERIAL NO: CB511R8WJJ
SEMC SIMLOCK CERTIFICATE
Elapsed:14 secs.
but I don't really understand whats in s1tool written about unlocking because when I compare my output with "how it should look" there are some differences. So, can I unlock the bootloader or not? btw, my operator does not install any simlock by default
I got same error as here http://forum.xda-developers.com/showthread.php?t=1280937 I don't know what to do now- "rerooting" and reflashing didnt help
If you want to install 2.1.1.Clean.0.0 V5 you need xrecovery.
Read this post http://forum.xda-developers.com/showthread.php?t=1179614
rzepa90 said:
OK, right now I'm trying to unlock bootloader. S1tool says :
Code:
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1240-1863_R4B
FILESYSTEM VERSION: VFE-1-8_2.1.1.A.0.6
SERIAL NO: CB511R8WJJ
SEMC SIMLOCK CERTIFICATE
Elapsed:14 secs.
but I don't really understand whats in s1tool written about unlocking because when I compare my output with "how it should look" there are some differences. So, can I unlock the bootloader or not? btw, my operator does not install any simlock by default
Click to expand...
Click to collapse
In the s1tool details, it is showing that the phone hasn't been rooted yet
RUNNING S1_EROM VER "R8A029"
Click to expand...
Click to collapse
Are you sure rooting was successful? Try Using SuperOneClick, that had worked for me: http://forum.xda-developers.com/showthread.php?t=950324
rzepa90 said:
OK, right now I'm trying to unlock bootloader. S1tool says :
Code:
Welcome to S1 identify tool
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1240-1863_R4B
FILESYSTEM VERSION: VFE-1-8_2.1.1.A.0.6
SERIAL NO: CB511R8WJJ
SEMC SIMLOCK CERTIFICATE
Elapsed:14 secs.
but I don't really understand whats in s1tool written about unlocking because when I compare my output with "how it should look" there are some differences. So, can I unlock the bootloader or not? btw, my operator does not install any simlock by default
Click to expand...
Click to collapse
As its SEMC SIMLOCK CERTIFICATE in the output of s1tool.. Run the msm7227-semc.cmd button in my tool.. Follow the instruction carefully..
Note: install the ggsetup.exe .. Its there as attachement in the main thread
Sent from my U20i using xda premium
Now it's working, I haven't got time for couple of weeks but yesterday I finally managed to flash new kernel. I had to find older version of flashtool- that was the solution
regarding battery yes. with normal to heavy use youll be lucky if it can last 15 hours. but with some tweaks and tools it can last for days
(Sorry for the double post, I don't think where I posted previously was correct and I think it got zero reads!)
So, I was given this AT&T branded X10a to use to help out a family member, I am not sure how long it has been out of service (maybe a year or so)
So far what I have done:
Used PC companion to return to stock
Obtained SIM unlock from AT&T (used defunct Verizon SIM to get prompt and entered code, appears to have worked)
Installed Flashtool and can recognize phone
Installed S1 Tool and verified connectivity
Currently s1tool returns
8/16/2012 16:51:14 RUNNING S1_EROM VER "R8A013"
8/16/2012 16:51:14 SOFTWARE AID: 0001
8/16/2012 16:51:14 LOADER AID: 0001
8/16/2012 16:51:17 FLASH ID: "002C/00B3"
8/16/2012 16:51:17 LOADER VERSION: "R4A024"
8/16/2012 16:51:17
8/16/2012 16:51:17 MODEL (from GDFS): X10a
8/16/2012 16:51:17 SOFTWARE VERSION: 1238-0269_2.1.A.0.492
8/16/2012 16:51:17 CUSTOM VERSION: 1237-3761_R31B
8/16/2012 16:51:17 FILESYSTEM VERSION: ATT-1-2-5-6_2.1.A.0.492
8/16/2012 16:51:17 SERIAL NO: xxxxxx
8/16/2012 16:51:17
8/16/2012 16:51:17 SEMC SIMLOCK CERTIFICATE
8/16/2012 16:51:17 Elapsed:18 secs.
Click to expand...
Click to collapse
Firmware : 2.1-update1
Baseband : 2.1.65
Kernel : [email protected]#1
So, my questions are more on what should I attack first! Not sure if I should:
Root -> BL Unlock -> Debrand to some generic from Flashtool
Debrand -> Root -> BL Unlock
Root -> BL Unlock -> Custom ROM
I am just a little confused on what direction I should head first with the rest of this. I was looking at the FeraLab New Gen ROM and it said that you needed Baseband of 2.1.71 as a requirement.
Seems like there are a couple of choices for root (flashtool and superoneclick) and a couple for recovery (Xrecovery and the two in flashtool). Just trying to decide what is best. As above I don't know if I should Root now before updating or update to one of the generic 2.3 roms then root... decisions decisions.
Thanks for any and all help.. I have been doing some searching just think I am overwhelmed with information starting on this phone. (my EVO and EVO Shifts were pretty straightforward I thought, this phone just seems to have a different way of doing things)
tschwenke said:
(Sorry for the double post, I don't think where I posted previously was correct and I think it got zero reads!)
So, I was given this AT&T branded X10a to use to help out a family member, I am not sure how long it has been out of service (maybe a year or so)
So far what I have done:
Used PC companion to return to stock
Obtained SIM unlock from AT&T (used defunct Verizon SIM to get prompt and entered code, appears to have worked)
Installed Flashtool and can recognize phone
Installed S1 Tool and verified connectivity
Currently s1tool returns
Firmware : 2.1-update1
Baseband : 2.1.65
Kernel : [email protected]#1
So, my questions are more on what should I attack first! Not sure if I should:
Root -> BL Unlock -> Debrand to some generic from Flashtool
Debrand -> Root -> BL Unlock
Root -> BL Unlock -> Custom ROM
I am just a little confused on what direction I should head first with the rest of this. I was looking at the FeraLab New Gen ROM and it said that you needed Baseband of 2.1.71 as a requirement.
Seems like there are a couple of choices for root (flashtool and superoneclick) and a couple for recovery (Xrecovery and the two in flashtool). Just trying to decide what is best. As above I don't know if I should Root now before updating or update to one of the generic 2.3 roms then root... decisions decisions.
Thanks for any and all help.. I have been doing some searching just think I am overwhelmed with information starting on this phone. (my EVO and EVO Shifts were pretty straightforward I thought, this phone just seems to have a different way of doing things)
Click to expand...
Click to collapse
1) upgrading to 2.3.3. upgrading will upgrade your baseband to .71 so you can install custom roms easily: many ways to do it.
[a] officially using pc companion or SEUS. you can download them using google. pretty straightforward to use.
using flashtool. Download 2.3.3 firmware from this thread: http://forum.xda-developers.com/showthread.php?t=1749426
unzip the file to get an ftf file and flash through flashtool.Use this guide on how to flash via flashtool:http://forum.xda-developers.com/showthread.php?p=19685019
2) You should root your phone(flashtool will be easier as you have already installed it) and follow this guide to unlock your bootloader : http://forum.xda-developers.com/showthread.php?p=19685019#post19685019
3) after you unlock you need to flash the kernel via flashtool.
two types of kernels
[a] stock based kernel for stock based roms: doomkernel v6,th kernel etc (its your choice).
doomkernel comes with both xrecovery and cwm preinstalled.
xrecovery- install stock based roms
cwm-install cm based roms
but you should check what recovery to use in rom thread
cm based kernels- for cyanogen(cm) roms. eg fxp kernel, kCernel etc.
check the rom thread what kernel to use.
choose your rom, and install recommended kernel via flashtool and install rom through recommended revovery
EDIT: next time ask questions in Q & A section
Thanks exactly what I needed, especially being so far behind in what has happened over time, starting late on phones is always fun! Yeah, the title and rules for other thread it seemed right, but obviously wasn't, then I went general and now moved to Q&A. So I guess I got two lessons out of this!
Again, thanks (meter updated!)
tschwenke said:
Thanks exactly what I needed, especially being so far behind in what has happened over time, starting late on phones is always fun! Yeah, the title and rules for other thread it seemed right, but obviously wasn't, then I went general and now moved to Q&A. So I guess I got two lessons out of this!
Again, thanks (meter updated!)
Click to expand...
Click to collapse
no problem.
heere to help you
post here if you have any other doubts