FIRST OF ALL,i would like to thank the_laser for providing us with the tools http://forum.xda-developers.com/showthread.php?t=1253277
I Noticed a lot of confusion here in the process of Unlocking BL -me was one of the confused- so please make sure to do/notice those points before/during unlocking procedure
THIS THREAD IS ONLY FOR CAUTIONS. actual steps are here http://forum.xda-developers.com/showthread.php?t=1254087
THANKS TO 9Lukas5
IF U DON'T KNOW HOW TO USE FLASHTOOL FOLLOW http://forum.xda-developers.com/showthread.php?t=928343
FOR GUIDANCE about SIM lock and which patch to use refer to 9Lukas5's thread and replies.
BUT generally use "qsd8250_semc" if ur phone came
1.pre-unlocked
2.unlocked by code
and use "qsd8250_setool2" if u have unlocked it with "setool"
ANYWAY u can always use the other patch if ur signal is lost after using the first.-i have less knowledge about this issue as my phone came pre-unlocked and didn't try to unlock another one-.
FIRST OF ALL
1.USB Port not broken -can't do any upgrade or unlocking with a broken one-.
2.enabled "unknown sources" from settings/applications
3.enabled "USB debugging" from settings/applications/development. -should display "USB debugging connected" in notifications bar after USB connection IF NOT: pls flash another ROM and root it using aZUZU method as UNlocking won't work for u-.
AFTER FLASHING downgrade aZUZU kernel
4.MAKE sure ur FLASHTOOL -GB ready version- recognize the phone after SE logo displays on ur phone -FLASHTOOL should say "xperia x10 connected" then shows ur busybox version.
5. IF it doesn't recognized ur phone pls...UPDATE ur SE PC COMPANION.
6.if u don't like to update PC companion..USE THIS METHOD as 9Lukas5 describes
You don't need to update pccp or seus. Try the following:
1. open the drivers manager of your pc
2. connects phone in flashmode (without running any program like flashtool, seus or pccp)
3. check if there appears an unkown device, which wasn't there before (if not go on, if yes read under the line in this post further on)
4. no unknown device? Good
5. turn on phone and connect usb cable again and check again for unknown devices
__________________________________________________ ___________________________________
If there is an unknown device, download flashtool 0.3.0.0 (it contains the 2.3.3 adb and flash drivers)
1. In Flashmode is an unknown device: Go to flashtool 0.3.0.0 folder then to drivers and install the exe file you find there
2. After turning on there is an unknown device: extract the x10 drivers archive in the drivers subfolder of flashtool 0.3.0.0 and search manually in that folder for the drivers of the unkown device, then they should be installed.
3. Now check again like I described it above the line for unknown devices, if you can't see them now, try again to unlock your bl.
Click to expand...
Click to collapse
7.be sure u have disabled all antivirus services and turn off ur firewall
8.close flashtool before starting to unlock BL
9.kill all processes named adb.exe by ur task manager "ctrl+alt+delete/start task manager/processes/sort by name/then kill adb.exe"
DURING UNLOCKING PROCEDURE
10.IF messages like "killing adb server..error" appears. pls make sure again u did points 6+7+8.
11.U HAVE TO WAIT A while and phone reboots in the process
DURING FLASHING Doom kernel v4.0 or stock
12. if messages like start flashing then abort flashing -with GB ready FLASHTOOL- or sending loader then along wait after flashing kernel .sin-with older FLASHTOOL - then u haven't probably unlocked ur BL . SO PLS don't bother ur self trying to re flash the kernel and check if ur bootloader is still locked
DID U follow steps+cautions?!!
13.to CHECK the status of ur bootloader pls download s1tool from
press "DO job" then connect ur phone in flash mode -green LED light-.
14. IF ur phone is UNLOCKED then status should be like this:
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 "r8A033"
NOTICE THE LOWER CASE letter "r" in "RUNNING S1_EROM VER "r8A033""
14.IF it isn't unlocked u would see UPPER CASE "R" like "R8A033" then try again with more caution then refer back to the thread
AFTER COMPLETEING THE PROCEDURE
15.of course u will see "XPERIA" Logo instead of "SONY ERICSSON" what Doomkernel u chose -v04b or v04-FS-.
16. 'SE' logo stll appears in cases:
1.u still on ur old kernel.
Or
2.u flashed Doom's stock kernel for unlocked bl.
Hi, very good for scared ones to have that thread. One suggestion, I added it to my how-to just now, but it's not needed to update pccp or seus, you only need the 2.3.3 adb/flash drivers. I have uploaded a file which only contains the drivers and explained in the third post of my how-to how to check if a driver update is needed and how to make it. Much easier as use the crappy se programs^^
Regards,
L
romasalah said:
15.of course u will see "XPERIA" Logo instead of "SONY ERICSSON" what ever the kernel u chose -stock or v4.0-.
Click to expand...
Click to collapse
You won't on stock.
Maybe we need to clear up the confusion in the OP when S1tool says SEMC SIMLOCK CERTIFICATE?
Sent from my X10 using XDA App
Blagus said:
You won't on stock.
Click to expand...
Click to collapse
FIXED..STOCK will show "SE" as usual
ballubas said:
Maybe we need to clear up the confusion in the OP when S1tool says SEMC SIMLOCK CERTIFICATE?
Sent from my X10 using XDA App
Click to expand...
Click to collapse
sorry don't get it..did u meant when sim is locked?
my s1tool is :
RUNNING S1_EROM VER "r8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO:
SEMC SIMLOCK CERTIFICATE
Elapsed:6 secs.
and it's unlocked
there has been people asking what does "SEMC SIMLOCK CERTIFICATE" mean, maybe in the op it can be said that its ok to un lock the bootloader with "SEMC SIMLOCK CERTIFICATE"
romasalah said:
sorry don't get it..did u meant when sim is locked?
my s1tool is :
RUNNING S1_EROM VER "r8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO:
SEMC SIMLOCK CERTIFICATE
Elapsed:6 secs.
and it's unlocked
Click to expand...
Click to collapse
ballubas said:
there has been people asking what does "SEMC SIMLOCK CERTIFICATE" mean, maybe in the op it can be said that its ok to un lock the bootloader with "SEMC SIMLOCK CERTIFICATE"
Click to expand...
Click to collapse
This is the information I have been trying to confirm. So I go ahead and use semc bat file? Seems like so much you have to look out for.
Sent from my x10i using XDA App
i hope this is not the start of endless threads of how too's. 9Lucas5 has created one already for members. surely any new information can be added there.
http://forum.xda-developers.com/showthread.php?t=1254087
this is what im trying to clear up!
lunarjetman1 said:
This is the information I have been trying to confirm. So I go ahead and use semc bat file? Seems like so much you have to look out for.
Sent from my x10i using XDA App
Click to expand...
Click to collapse
lunarjetman1 said:
This is the information I have been trying to confirm. So I go ahead and use semc bat file? Seems like so much you have to look out for.
Sent from my x10i using XDA App
Click to expand...
Click to collapse
ballubas said:
there has been people asking what does "SEMC SIMLOCK CERTIFICATE" mean, maybe in the op it can be said that its ok to un lock the bootloader with "SEMC SIMLOCK CERTIFICATE"
Click to expand...
Click to collapse
MY experience in SIMunlock isn't so much but i added some hints to the thread if there is some evident additions pls post them....
there's a member who used "qsd8250_setool2" for locked sim and had no signal then used "qsd8250_semc' and it worked and restored his signal back
about what S1TOOL SAYS:
Mine displayed: SEMC SIMLOCK CERTIFICATE
and i could unlock it
Some others display:NOT RECOGNIZED SIMLOCK CERTIFICATE
can't assure that they can't unlock bl... I say try to unlock ur SIM first
And...As i said previously,there r member who unlocked his bl with locked SIM
romasalah said:
there's a member who used "qsd8250_setool2" for locked sim and had no signal then used "qsd8250_semc' and it worked and restored his signal back
Click to expand...
Click to collapse
Me too!!
I actually got cought in the confusion of "SEMC SIMLOCK CERTIFICATE"; I thought that it meant that my phone was unlocked using setool2 (because my phone was already unlocked when I bought it, and I don't know how it was unlocked). Anyways with "qsd8250_setool2" I lost the signal and with "qsd8250_semc" I was able to restore it, but only thanks to that post that you mention, because otherwise I would have panic and would't be able to do anything else
I checked my phone with the s1 tool and it showed lower case r, but at boot it still show the Sony Ericsson text Is anyone aware of this? Is my phone bootloader unlocked?
wizoxt said:
I checked my phone with the s1 tool and it showed lower case r, but at boot it still show the Sony Ericsson text Is anyone aware of this? Is my phone bootloader unlocked?
Click to expand...
Click to collapse
It is indeed, you just haven't flashed a 'real' custom kernel yet.
wizoxt said:
I checked my phone with the s1 tool and it showed lower case r, but at boot it still show the Sony Ericsson text Is anyone aware of this? Is my phone bootloader unlocked?
Click to expand...
Click to collapse
If you haven't flashed any custom kernel for unlocked bl yet, your bl is unlocked, but the se kernel is still used --> se logo appears. If you want to disappear the se logo, flash custom kernel for unlocked bl.
Regards,
L
9Lukas5 said:
If you haven't flashed any custom kernel for unlocked bl yet, your bl is unlocked, but the se kernel is still used --> se logo appears. If you want to disappear the se logo, flash custom kernel for unlocked bl.
Regards,
L
Click to expand...
Click to collapse
aR_ChRiS said:
It is indeed, you just haven't flashed a 'real' custom kernel yet.
Click to expand...
Click to collapse
Ahh.. Forgot to mention that I did flashed the DoomLord's custom kernel for bootloader unlocked.. But the situation remain unchanged I was just curious if my BL is unlocked properly
try reflashing the kernel and have an eye on it it gives you any security error, if yes, your bl isn't unlocked. Or test with the s1 tool from the laser, if you can't see a lower case letter, bl isn't unlocked yet.
Regards,
L
wizoxt said:
Ahh.. Forgot to mention that I did flashed the DoomLord's custom kernel for bootloader unlocked.. But the situation remain unchanged I was just curious if my BL is unlocked properly
Click to expand...
Click to collapse
Make sure u flashed the kernel properly....Doom had posted a stock kernel for Unlocked BL ,don't use it. Did u followed links on Lukas's thread?!!
Sent from my X10i using XDA App
romasalah said:
Make sure u flashed the kernel properly....Doom had posted a stock kernel for Unlocked BL ,don't use it. Did u followed links on Lukas's thread?!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
why shoudn't he use the stock kernel from doom?
9Lukas5 said:
why shoudn't he use the stock kernel from doom?
Click to expand...
Click to collapse
No problem to use STOCK kernel
Related
hi all,
i want to ask you a way to relock the bootloader?
the method described by SpyderX didn't work for me while i unlocked the bootloader via the method he described!
for details i have did the following:
i unlocked bootloader via his method
i didn't change stock kernel
i run S1tool =====> didn't find any button called restore!
i couldn't relock bootloader...
i only need to lock my bootloader to check something with the radio chip with the SE dealer over here.
EDIT: forgot to mention that i have X10 mini pro
how to relock boot loader:
1. Flash stock kernel or stock ROM with flashtool v 0.2.9.1 Beta
2. Run S1Tool and choose the RESTORE option until there is a message to turn off and connect phone to pc
3. Turn off the phone and connect to the pc, wait until the process is complete.
4. please be sure to check by S1Tool.
Here i have the S1Tool with RESTORE option, to relock bootloader. All kredit to the Laser For the tool, and don't forget to press thanks button if i can help you.
Sorry for my bad English
stiv8785 said:
how to relock boot loader:
1. Flash stock kernel or stock ROM with flashtool v 0.2.9.1 Beta
2. Run S1Tool and choose the RESTORE option until there is a message to turn off and connect phone to pc
3. Turn off the phone and connect to the pc, wait until the process is complete.
4. please be sure to check by S1Tool.
Here i have the S1Tool with RESTORE option, to relock bootloader. All kredit to the Laser For the tool, and don't forget to press thanks button if i can help you.
Sorry for my bad English
Click to expand...
Click to collapse
man thanks for the tool but i had something else happening now!
in the s1 version it's locked R8A028 but my phone was R8A029!
why the change of the last digit!
minachvim said:
man thanks for the tool but i had something else happening now!
in the s1 version it's locked R8A028 but my phone was R8A029!
why the change of the last digit!
Click to expand...
Click to collapse
Thats ok, you can read in spyderX thread. here :
If the line RUNNING S1_EROM FROM VER "#8A02$" has a lowercase "r" letter replacing the "#" (RUNNING S1_EROM FROM VER "r8A02$"), your bootloader was not successfully relocked . If it has an uppercase "R" replacing the "#" (RUNNING S1_EROM FROM VER "R8A02$"), your bootloader has been successfully relocked .
Note: The value of the "$" is dependent on an unknown factor. The unknown factor doesn't matter to us.
stiv8785 said:
Thats ok, you can read in spyderX thread. here :
If the line RUNNING S1_EROM FROM VER "#8A02$" has a lowercase "r" letter replacing the "#" (RUNNING S1_EROM FROM VER "r8A02$"), your bootloader was not successfully relocked . If it has an uppercase "R" replacing the "#" (RUNNING S1_EROM FROM VER "R8A02$"), your bootloader has been successfully relocked .
Note: The value of the "$" is dependent on an unknown factor. The unknown factor doesn't matter to us.
Click to expand...
Click to collapse
so the 8 and 9 doesn't affect the phone at all?? or it affects the phone in some way??
minachvim said:
so the 8 and 9 doesn't affect the phone at all?? or it affects the phone in some way??
Click to expand...
Click to collapse
yes, it doesn't matter.
I have repeatedly Unlock and relock bootloader.
stiv8785 said:
yes, it doesn't matter.
I have repeatedly Unlock and relock bootloader.
Click to expand...
Click to collapse
mmm thanks
do you know what does the 8 and 9 means??? i'm trying to find what does it mean but no one explain it!
minachvim said:
mmm thanks
do you know what does the 8 and 9 means??? i'm trying to find what does it mean but no one explain it!
Click to expand...
Click to collapse
Ahem.. The unknown factor doesn't matter to us!
Does not matter.
The other day I unlocked bootloader and did flash the phone on ST18i_4.1.A.0.562_ (1252-5332) using the flashtool and after that I returned the phone to (ST18) _4.0.2.A.0.42_CE.ftf and he turned on normaly,after that problem occurred when i update over wireless to 2.3.6 and then more would not turn on, every time I tried to light a single LED is lighted up, and nothing more, I tried many times to do update with several firmwares and publish flastool each time it is completed but the phone still will not start and then I tried to unlock the bootloader and then try the update again on (ST18) _4.0.2.A.0.42_CE.ftf and the problem is that we s1 tool throws the following message when I click restore:
Welcome to S1 tool.
NEXT TO CONNECT PHONES
X10 Xperia, Xperia Mini E10, E15 Xperia X8, U20 Xperia Mini Pro
LT15 Xperia ARC, NEO MT15 Xperia, Xperia PLAY R800
PRESS AND HOLD "BACK" BUTTON ...
PLEASE ATTACH Turned OFF PHONE NOW
RUNNING S1_EROM VER "r9A021"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0098/00B3"
LOADER VERSION: "R4A069"
FAILED TO FIND RESOURCE
look here, http://forum.xda-developers.com/showthread.php?t=1492805 it might help
Try s1tool that what I used to unbrick my ray
Sent from my ST18i using xda premium
You bricked ur phone
If you don't know how to solve this i think you have to go to easy way.
Wotan server.
Download wotan client. And register an account they will give u a free credit.
Then open wotan server will say connect phone u have to click volume down while connecting usb to ur Xperia Ray then will detect your phone..
Then u can chose which country and which rom you want to install..
Thank you all for such quick answers and I just solved the problem so I took off a new S1 tool that did restore successfully and after that I am very surprised that the phone is turned on first, I guess that the problem was that I did update directly from the phone via Wireless but with the unlocked bootloader
zoransc said:
Thank you all for such quick answers and I just solved the problem so I took off a new S1 tool that did restore successfully and after that I am very surprised that the phone is turned on first, I guess that the problem was that I did update directly from the phone via Wireless but with the unlocked bootloader
Click to expand...
Click to collapse
yeah, u are right ... but how did u unlocked ur phone ? Via website of sony or with s1tool and testpoint?
With S1 tool
so meaning that if u unlock ur bootloader using the test point method, u still cant update ota?
Well it would not be able to answer with certainty
fota brick?
from what i see, i think u unlocked ur bootloader, then did a OTA. haha i did that the other day and i was freaking out. dont worry, heres ur solution
go here
http://forum.xda-developers.com/showthread.php?t=1126358
in here, theres a version of flashtools that can fix ur brick. its easy
the multiupload link is dead, but theres a mirror on page 15
u must thank this person for reuploading it shprakash
www.mediafire.com/?h2dwrz18mujx765
good luck
Hey,
Yesterday I flashed my old software (stock kernel with cwm, and minicm7 pro v21) to nAa kernel 2.6.29.6 ics and cm9 port for x10 mini pro. First few hours I had problems with flashtool (sin error). I decided to reunlock bootloader. Everything went perfect. I flashed succesfully new kernel, then through cwm installed ROM. I had some problems with booting, but finally got it up. But then a new problem appeared. It seems like my phone re-locked SIMLock... It's really strange because I bought it from Era operator in Poland (now it's T-Mobile), already unlocked. I am using Orange SIM card, and till yesterday it was running perfectly. Can somebody help me please?
I tried this solution: http://forum.xda-developers.com/showthread.php?t=1591785
but no effects..
Ok, I've managed to relock bootloader and restore stock ROM and kernel. Seems to work fine. I'll try to install nAa kernel and cm9 again, and if it'll pass, you can close topic
Ok, it's working fine Still Sim unlock message, but I can just dismiss it and it works
/Close
yeah all we do is selecting dismiss...
Sent from my U20i using xda premium
earglass said:
Ok, I've managed to relock bootloader and restore stock ROM and kernel. Seems to work fine. I'll try to install nAa kernel and cm9 again, and if it'll pass, you can close topic
Click to expand...
Click to collapse
STOP MESSING WITH YOUR F****** bootloader... once it's unlocked, and your phone still works fine, leave it unlocked. If you unlock your bootloader for the first time, check if your phone still works on the software you are running, don't just unlock it and flash something else, check first. If it still works, do whatever you want, if it doesn't, relock it and pray your phone is still a phone.
Flashing stock will work on locked or unlocked bootloaders, no need to mess with that at all. ONLY relock it when you want to take it back to your provider for repairs under warranty. LEAVE IT ALONE!!!!!
(PS, it wouldn't hurt if this advice was in a sticky post, too many people unlock their bootloader without checking if their phone still works afterwards)
FYI: The bootloader of your phone works the same as on your computer, it contains the information needed to start your operating system. If you decide to install Linux on your PC your bootloader needs to be changed from when you were running Windows. The hardware manufacturer of your phone wants to make sure your phone remains a phone, in order to provide support and warranty, that's why they lock the bootloader.
I know what is bootloader ;] You show me only that you can't read carefully :/
I said that phone worked on minicm7, of course unlocked bootloader etc.
After flashing nwe kernel, mobile network went down, and it was still down when I flashed back old kernel, whole backup, even when I flashed stock os.
Somehow Simlock locked itself and relocking bootloader (an then unlocking again ;p) was the only thing, that worked from what I've searched
I did read carefully... you said you were on stock kernel, and you had to unlock your bootloader in order to flash nAa kernel and new ROM (you said re-unlock, like you had it unlocked and then locked it again, bootloaders don't lock themselves once they're unlocked), and then your phone stopped working as a phone
All I'm saying is, unlock your bootloader and check if your phone still works before flashing new kernel and rom, saves a lot of trouble.
Totally agree ;] I think I didn't write it clearly at first post, my bad I was confused, because this mobile network (simlock relocked somehow) about a year after unlocking bootloader and changing rom to custom one But in fact, I was still on stock kernel, and changed it for the first time just few days ago. Did not see any connection, but I study programming and I can see so many exceptions of logic that I'm not suprised ;D
cheers
You're welcome... And from what i know from unlocking bootloaders, it wasn't your sim-lock that stopped your phone from working, but a disabled radio-chip. Don't think it would have worked on a t-mobile simcard either, i guess the way your phone was sim-unlocked just isn't compatible.
Similar problem
Hi, I am sorry for hijacking this thread, but I was looking for a solution to my problem and ended up here and you seem more than savvy, can you please advise me , I copied and pasted below the description of my problem taken out of my original thread. thanks
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
How to Unlock Sim after unlocking BootLoader?
Hi, today I successfully unlocked the bootloader on my xperia x8 via flashtool put on custom kernel nAa 14 and miniCM7 Yay
Everything is fine apart that I want to change network because they have much better deals etc.
I went to the 3 network shop and tried to put in the Sim, it took it in loaded but wouldnt register with the network , in fact I tried last week when I was on stock kernel and gingerxperia and it asked for ''unlock code'', today it didn't ask for unlock code took it in but wont register.
I guess there must be some sim lock or something. I kindly ask you if you could give me and advice so I can be at peace.
Maybe it is unlocked but something to do with Radio pehaps nonetheless my current Network works fine.
here's my S1 LOG if any good. after unlocking BL of course
Welcome to S1 identify tool
16/09/2012 17:16:15
16/09/2012 17:16:15 TO CONNECT NEXT PHONES
16/09/2012 17:16:16 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
16/09/2012 17:16:16 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
16/09/2012 17:16:16 PRESS AND HOLD "BACK" BUTTON...
16/09/2012 17:16:16
16/09/2012 17:16:16 PLEASE ATTACH TURNED OFF PHONE NOW
16/09/2012 17:16:16
16/09/2012 17:16:30
16/09/2012 17:16:30 RUNNING S1_EROM VER "r8A029"
16/09/2012 17:16:30 SOFTWARE AID: 0001
16/09/2012 17:16:30 LOADER AID: 0001
16/09/2012 17:16:33 FLASH ID: "0020/00BC"
16/09/2012 17:16:33 LOADER VERSION: "r4A060"
16/09/2012 17:16:33
16/09/2012 17:16:33 MODEL (from GDFS): E15i
16/09/2012 17:16:33 SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
16/09/2012 17:16:33 CUSTOM VERSION: 1241-3730_R2B
16/09/2012 17:16:33 FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
16/09/2012 17:16:33 SERIAL NO: CB511S0EXH
16/09/2012 17:16:33
16/09/2012 17:16:33 SEMC SIMLOCK CERTIFICATE
16/09/2012 17:16:33 Elapsed:17 secs.
daithy said:
Hi, I am sorry for hijacking this thread, but I was looking for a solution to my problem and ended up here and you seem more than savvy, can you please advise me , I copied and pasted below the description of my problem taken out of my original thread. thanks
...
16/09/2012 17:16:33
16/09/2012 17:16:33 SEMC SIMLOCK CERTIFICATE
16/09/2012 17:16:33 Elapsed:17 secs.
Click to expand...
Click to collapse
You've got a Sony Ericsson supplied simlock certificate, not one from a carrier, so your phone seems to be simlock-free. Not sure what is going on with the 3 network that it won't work on your phone.
SmG67 said:
You've got a Sony Ericsson supplied simlock certificate, not one from a carrier, so your phone seems to be simlock-free. Not sure what is going on with the 3 network that it won't work on your phone.
Click to expand...
Click to collapse
Thanks for your reply
So what you are insinuating is that theoretically everything should be fine there hmmm, well I definitely needed an unlock code last week.
daithy said:
Thanks for your reply
So what you are insinuating is that theoretically everything should be fine there hmmm, well I definitely needed an unlock code last week.
Click to expand...
Click to collapse
Yeh, it's a bit weird, because normally you get a simlock-not-recognised in S1Tool with simlocked phones, the SEMC Simlock certificate is the standard factory issued one, that is not touched by a carrier. maybe you could ask your previous provider if they could provide you with a code, but if it wasn't simlocked in the first place i don't think they can.
SmG67 said:
Yeh, it's a bit weird, because normally you get a simlock-not-recognised in S1Tool with simlocked phones, the SEMC Simlock certificate is the standard factory issued one, that is not touched by a carrier. maybe you could ask your previous provider if they could provide you with a code, but if it wasn't simlocked in the first place i don't think they can.
Click to expand...
Click to collapse
As a matter of fact I requested the unlock code 7 days ago before changing kernels and ROM, I am still waiting for it, but problem is that it doesn't ask for it no more, so the question is where do I put the unlock code once received from my network provider.
daithy said:
As a matter of fact I requested the unlock code 7 days ago before changing kernels and ROM, I am still waiting for it, but problem is that it doesn't ask for it no more, so the question is where do I put the unlock code once received from my network provider.
Click to expand...
Click to collapse
It is possible that that feature is missing from the ROM, going back to stock will definitely let you input it, and once that is done you can go and do whatever you please
SmG67 said:
It is possible that that feature is missing from the ROM, going back to stock will definitely let you input it, and once that is done you can go and do whatever you please
Click to expand...
Click to collapse
Ok, if I understand you correctly, I need to flash the stock kernel back on and put on gingerxperia rom I was using last week. then go to the shop shove in the SIM card it will ask for unlock code ,I will pop in the provided unlock code, reflash kernel back to nAa 14 restore my minicm7 and happily ever after?.....:cyclops:
So do I need to relock my bootloader or can I leave open without harming my device. just to be sure
daithy said:
Ok, if I understand you correctly, I need to flash the stock kernel back on and put on gingerxperia rom I was using last week. then go to the shop shove in the SIM card it will ask for unlock code ,I will pop in the provided unlock code, reflash kernel back to nAa 14 restore my minicm7 and happily ever after?.....:cyclops:
So do I need to relock my bootloader or can I leave open without harming my device. just to be sure
Click to expand...
Click to collapse
yes, right on, if you got the unlock-dialog with that gingerxperia rom, it will work.
There is no need to ever lock the bootloader again, unless you somehow still have warranty and want to have the phone repaired. In that case, put original firmware back on and relock the bootloader
SmG67 said:
yes, right on, if you got the unlock-dialog with that gingerxperia rom, it will work.
There is no need to ever lock the bootloader again, unless you somehow still have warranty and want to have the phone repaired. In that case, put original firmware back on and relock the bootloader
Click to expand...
Click to collapse
You Sir have been the most helpful, thanks for your help.
Leave the thread open as I will come back here in a fews days with the result, to help others experiencing the same problem.
BTW just tried my friends O2 sim and exactly the same issue as 3 Network sim. Unlock code bring it
Just a little update, today I reverted back to the awful stock kernel and put in the gingerXperia rev3 Rom and after being a few days on minicm7 yuck its really sluggish and cumbersome cant wait to go back to minicm7. Anyway tried to put in 3 network sim and its asking for the unlock code which is good. I should receive the code very soon tomorrow or the day after. Will keep you updated
daithy said:
Just a little update, today I reverted back to the awful stock kernel and put in the gingerXperia rev3 Rom and after being a few days on minicm7 yuck its really sluggish and cumbersome cant wait to go back to minicm7. Anyway tried to put in 3 network sim and its asking for the unlock code which is good. I should receive the code very soon tomorrow or the day after. Will keep you updated
Click to expand...
Click to collapse
As promised, only today did I receive the unlock code, shame on you Meteor, yes I will mention the name. Final result is success
It did work, exactly as advised.
thank you
So... I'm on a st15i, locked bootloader, and I decided to unlock it.
Test point method sounded perfect.
I followed tutorials step by step, and here's my S1Tool log:
Code:
DETACH USB CABLE FROM PHONE
REMOVE BATTERY FROM PHONE
ATTACH TESTPOINT
PRESS "READY", THEN ATTACH USB CABLE TO PHONE
PROCESSING ...
REMOVE TESTPOINT NOW, THEN PRESS "READY"
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_LOADER VER "R4A062"
LOADER AID: DEAD
FLASH ID: "00EC/00B3"
LOADER VERSION: "r4A069"
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:40 secs.
What the hell does that mean? Not recognized SIMlock certificate?
My bootloader is unlockable: I'll attach a screen of my Service Menu.
So why couldn't I unlock it?
I think you done it incorrectly...but why don't you just use official unlock bootloader?
XDA Premium sent this message from owner of Sk17I
Why should I lose DRMs if I can avoid it? Even though I don't care about them, it's still an avoidable loss
Feanor88 said:
So... I'm on a st15i, locked bootloader, and I decided to unlock it.
Test point method sounded perfect.
I followed tutorials step by step, and here's my S1Tool log:
What the hell does that mean? Not recognized SIMlock certificate?
My bootloader is unlockable: I'll attach a screen of my Service Menu.
So why couldn't I unlock it?
Click to expand...
Click to collapse
From what i see in that screen shot, it looks like you have successfully unlocked your bootloader. Otherwise in service menu, it would say "Bootloader unlock allowed: No"
loCe45 said:
From what i see in that screen shot, it looks like you have successfully unlocked your bootloader. Otherwise in service menu, it would say "Bootloader unlock allowed: No"
Click to expand...
Click to collapse
Hmmm... No. Wrong. There's really no way to know if you successfully got bootloader unlocked by test point method, other than to try flashing a kernel.
If unlocking is done by Official Sony method, it says the
Code:
Rooting Status:
Boot Loader Unlocked: Yes
If unlocking is done via test point method it says:
Code:
Rooting Status:
Boot Loader Unlocked allowed: Yes
...just as it stated before the attempt to unlock.
And if bootloader is not unlocked, but possible, it still says:
Code:
Rooting Status:
Boot Loader Unlocked allowed: Yes
This is because, test point method is not actual bootloader unlocking, and it's like a patch.
@feanor: Try to do a repair using PCC. If it says that you are using a modified software, then yipee, your bootloader is unlocked. If it starts the repair process, then cancel the repair process (Oops, my bootloader is still locked :-|).
As the next step, you can try the test point method again, but if you are afraid, then head on to Sony Official website and do it the official way.
Thanks,
Rick
One last question: what happens if I just try to flash a custom kernel and my bootloader is locked? Does the process just fail, or do I brick my phone?
Feanor88 said:
One last question: what happens if I just try to flash a custom kernel and my bootloader is locked? Does the process just fail, or do I brick my phone?
Click to expand...
Click to collapse
Custom kernel is unsigned, installation will not start.
Feanor88 said:
One last question: what happens if I just try to flash a custom kernel and my bootloader is locked? Does the process just fail, or do I brick my phone?
Click to expand...
Click to collapse
That should be a brick. Though I am not sure. You would rather test if your bootloader is unlocked by trying to repair using PCC. It's better, right? Less amount of risk involved.
Oh no. Wait a second. It flashed to me now. You can not really test that way. As the repair will occur without fail if your bootloader is unlocked via test point method. :-|.
I really have no idea now, as to how to test if bootloader is successfully unlcoked when attempted via test point method.
Perhaps someguyfromhell help? Lets wait and see.
Thanks,
Rick
Sent from my SK17i using XDA
Someguyfromhell said:
Custom kernel is unsigned, installation will not start.
Click to expand...
Click to collapse
Someguyfromhell spoke.
Ok, think I'll try flashing a custom kernel... let's see what happens
Well, just to be sure I tried the "Identify" feature with S1Tool... here's the log
Code:
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R9A021"
SOFTWARE AID: 0001
SIMLOCK STATE: "TAMPERED"
LOADER AID: 0001
hash not supported []
Elapsed:5 secs.
I suppose my phone can't be unlocked at all via test point... maybe it's because I have THIS phone........
Sorry for digging this topic, but I face the exact same problem in my LWW.
It said (and still says) "Bootloader unlock allowed: Yes", don't know why couldn't S1Tool unlock it, though.
Months ago, when I purchased the phone, I unlocked network via FastGSM (using test-point too):
Youtube v=FgYAZoqsk9E (sorry, can't post links)
When I first connected the USB cable while holding test-point, my PC didn't even asked for drivers, guess Fast GSM software uses the same and installed them when I unlocked network.
Thanks in advance!
What does your phone say about Bootloader Unlock Allowed in Service Menu(*#*#7378423#*#*)?
Someguyfromhell said:
What does your phone say about Bootloader Unlock Allowed in Service Menu(*#*#7378423#*#*)?
Click to expand...
Click to collapse
ricardo_r said:
It said (and still says) "Bootloader unlock allowed: Yes"...
Click to expand...
Click to collapse
Anyways, forget about my post. With further research I came to the conclusion that that message on s1tool means that my bootloader is actually "unlocked", and that's due to FastGSM test-point unlocking.
Take a look at this thread (post #4 onwards). So, "test-point" bootloader unlocking in fact is not an "unlock" per se but rather a "patching" to the BL. So that also explains why my phone didn't get bricked when I updated to ICS 4.0.4 via PC Companion.
If you would take my suggestion, you could add in your FAQ topic this little piece of information so that users who had unlocked their phones' network via FastGSM or Wottan, don't need to worry about BL.
I've already flashed Krsh kernel and everything went without any itches. Great!
Thanks a lot for your help and your tutorials!:good:
PS: I couldn't also find a "flash.cmd" file anywhere as you mention on the "Flash kernel" section of your FAQ thread, so I just executed the commands as mentioned in Cyanogenmod's Wiki page for LWW:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
ricardo_r said:
Anyways, forget about my post. With further research I came to the conclusion that that message on s1tool means that my bootloader is actually "unlocked", and that's due to FastGSM test-point unlocking.
Take a look at this thread (post #4 onwards). So, "test-point" bootloader unlocking in fact is not an "unlocking" per se but rather a "patching" to the BL. So that also explains why my phone didn't get bricked when I updated to ICS 4.0.4 via PC Companion.
If you would take my suggestion, you could add in your FAQ topic this little piece of information so that users who had unlocked their phones' network via FastGSM or Wottan, don't need to worry about BL.
I've already flashed Krsh kernel and everything went without any itches. Great!
Thanks a lot for your help and your tutorials!:good:
PS: I couldn't also find a "flash.cmd" file anywhere as you mention on the "Flash kernel" section of your FAQ thread, so I just executed the commands as mentioned in Cyanogenmod's Wiki page for LWW:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
Click to expand...
Click to collapse
Yea, I'm tired so I missed it.
The 2nd command is not needed, the first one can also be just "fastboot flash boot boot.img". And this flash.cmd is only, if you use my Kernel Installation Package(which currently is not available, got some problems).
Ok, thanks a lot for your help, mate!:good:
Hi!
I use flashtool for flashing my SE x10i
When i wanted to flash a new firmware, i clicked on BLRelock.ftf by mistake....... Since than i haven't got radio capability. When I turn it on, it says "Please insert a sim card". If it matters my phone was debranding....
I tried lots of method, but I always failed.
Please somebody help ASAP.!
Thank you the answers in advance :'(
Hey there, i have this same issue, except my x10i kps rebooting or just freezes up whilst dn sumin with it, eg, running apps. I received phone frm my boet, we bth have no knowledge as to what had hapnd to the phone, bt suspect water damage, because if i take the cover off the bk, those pink dots on the white paper that shows that there has bn water intrusion, well at least thats what i think it myt be. I have 4 batteries, bt none undr a 2.5yr and oldest 2008, thats 5 years old. Bt sumin also tells me i shd try to purchase a new battery. No matr what sim i pt in it wont register. Bt look, i received it dead as a doornail, and nw it runs bt cnt kp running stable. I too used flashtool, i pt phone in debug n unknwn sources. It seems to lock up while this debug nw runs. i have rooted, im nt sure whether i did succesful recovery, i upgraded from 2.1 to 3 havn to flash several times. Because it freezes or restarts so i end up with no choices i cn think abt. If the debug runs successfully whats next? Turn it off and then? I just aint getn nowhere? I thought maybe phne puln too much power frm batries, bt it even reboots, restarts or freezes when on a normal ericson charger, or with laptop usb cable attached. I dnt knw what to do? Bt im gna have a onceover again, maybe i misd sumin bt that radio part, i hardly knw how these things work, bt im all ears to any ideas. Thanx in advance
Terrence
Sent from S3Terry, Galaxy SIII GTI9300, using 8ta/Telkom Mobile.
tibcic1994 said:
Hi!
I use flashtool for flashing my SE x10i
When i wanted to flash a new firmware, i clicked on BLRelock.ftf by mistake....... Since than i haven't got radio capability. When I turn it on, it says "Please insert a sim card". If it matters my phone was debranding....
I tried lots of method, but I always failed.
Please somebody help ASAP.!
Thank you the answers in advance :'(
Click to expand...
Click to collapse
Get s1tools and identify your device. Post log here.
Sent from my X10i using xda app-developers app
I had a similar problem. I wanted to lock the bootloader and i've clicked restore in s1tool. After relock bootloader my SEMC SIMLOCK CERTIFICATE changed to SETOOL2 SIMLOCK CERTIFICATE. I do not know why. Phone died. I try different things. Once again i've unlock the bootloader using qsd8250_setool2.cmd file. After that, my X10 alive.
Like epulrevo says, first check phone by s1tool. I bet that you will have SETOOL2 SIMLOCK CERTIFICATE.
epulrevo said:
Get s1tools and identify your device. Post log here.
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
Here it is :
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 "R8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1236-4638_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB511PP192
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:19 secs.
tibcic1994 said:
Here it is :
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 "R8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1236-4638_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CB511PP192
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:19 secs.
Click to expand...
Click to collapse
U need to unlock your phone again.
Sent from my X10i using xda app-developers app
epulrevo said:
U need to unlock your phone again.
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
Thank you for your answer
I might be a little bit stupid, but one more question:
Do I have to unlock the bootloader or debranding my phone?
tibcic1994 said:
Thank you for your answer
I might be a little bit stupid, but one more question:
Do I have to unlock the bootloader or debranding my phone?
Click to expand...
Click to collapse
Unlock bootloader, because your bootloader is relock improperly.
Sent from my X10i using xda app-developers app
epulrevo said:
Unlock bootloader, because your bootloader is relock improperly.
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
Can you write down how can I do that? And which program do you recommend? Just because all of my trying failed I tried to do it with flashtool and s1tool too.
I wanted to ask, with the debranding files available which wd i choose for South Africa cause i still have this problem. Kp getn your simcard does nt allow connections to this network? And the sim will pick up 4 networks i cn chose from, bt when i chose appropriate network thats the message i get. And the signal bar has a red x above it. I cn still use the phone for data via wifi bt its a phone also made for calls? Also another thing i lost my mem card with my xRecovery on it, the FT icon for recovery remains faded, cn i make another recovery? When i let FT reboot to recovery then it will either nt boot unless i remove the batry or it will basically just reboot bk to android, bypassing the recovery boot, it did work when i had my other mem card... hope im nt imposing here with that q. Thanks for any advice in advance.
Sent from S3Terry, Galaxy SIII GTI9300, using 8ta/Telkom Mobile.