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:
Related
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
Since beginning I have bootloader not possible to unlock.
Since I used Wotan “Xperia neo Unlocker” to debrand my phone when I input *#*#7378423#*#* I see now that say bootloader unlock allowed.
When I connect phone to computer pressing the menu button I have blue light.
Can I just by this assume that my bootaloader is unlocked?
One way will be to try install something only allowed for unlocked bootloader but I don´t want to mess my phone or if is not unlocked simple nothing happen?
Thanks
It would seem that it's unlocked
How to check is bootloader is unlocked
pedrofigo said:
Can I just by this assume that my bootaloader is unlocked?
Click to expand...
Click to collapse
How to check is bootloader is unlocked:1. Download S1Tool (attached)
2. Un7zip and Run s1tool.exe and click on DO JOB
3. Connect phone to PC with pressed "back" button
4. Now you wiil see something like this in the program window:
Code:
9/9/2011 21:41:44 Welcome to S1 identify tool
9/9/2011 21:45:13
9/9/2011 21:45:13 TO CONNECT NEXT PHONES
9/9/2011 21:45:13 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
9/9/2011 21:45:13 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
9/9/2011 21:45:13 PRESS AND HOLD "BACK" BUTTON...
9/9/2011 21:45:13
9/9/2011 21:45:13 PLEASE ATTACH TURNED OFF PHONE NOW
9/9/2011 21:45:13
9/9/2011 21:45:46
[COLOR="Red"]9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"[/COLOR]
9/9/2011 21:45:46 SOFTWARE AID: 0001
9/9/2011 21:45:46 LOADER AID: 0001
9/9/2011 21:45:49 FLASH ID: "002C/00BC"
9/9/2011 21:45:49 LOADER VERSION: "R4A045"
9/9/2011 21:45:49
9/9/2011 21:45:49 MODEL (from GDFS): X8
9/9/2011 21:45:49 SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
9/9/2011 21:45:49 CUSTOM VERSION: 1241-3178_R1B
9/9/2011 21:45:49 FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
9/9/2011 21:45:49 SERIAL NO: CB511SPH7Q
9/9/2011 21:45:49
9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE
9/9/2011 21:45:49 Elapsed:36 secs.
5. Look to line "RUNNING S1_EROM FROM VER "#8A029"" You will see small or capital R letter
small r - bootloader unlocked
capital R - bootloader locked
PS Sorry for my english
Thanks for reply.
Suing S1 tool like you said here is what I get
Is locked or not my bootloader?
Having r like you said is unlocked? Correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
Yes. Small r - Unlocked bootloader. Don't update firmware via FOTA
It seems that is not unlocked.
If it is unlocked, u can see a "yes" instead of "allow"
harveyxia said:
It seems that is not unlocked.
If it is unlocked, u can see a "yes" instead of "allow"
Click to expand...
Click to collapse
lol?
It always(of course on not branded phones) show "Yes", it never shows allow
After unlocking BL, nothing change in service menu, if it showed "Bootloader unlock allowed:Yes" than after unlocking it will show same
If it says "Bootloader unlock allowed:No" means that your fastboot is disabled, and after enabling it it will show "Bootloader unlock allowed:Yes" then you can ether unlock it(BL) yourself, or person who enabled your fastboot via setool for example.
Yes is unlocked.
I already have connection with flastool.
Now just wait for courage…lolol….to try something like a different kernel ;-)
Thanks for your comments.
So, have you tested if it accept custom kernels?
Don't be afraid, you can't kill it, just flash it and see if it boots. Download setCPU and try to move frequency higher.
I'm curious, in that Unlocker by wotan server, do you need to use test point?
Madfysh said:
So, have you tested if it accept custom kernels?
Don't be afraid, you can't kill it, just flash it and see if it boots. Download setCPU and try to move frequency higher.
I'm curious, in that Unlocker by wotan server, do you need to use test point?
Click to expand...
Click to collapse
Yes I am using NightElf Kernel and also tried [ROM] Neo |Team Xperia/SE.TWEAKED| V1.0 |23/02/12| (don´t like it).
NightElf Kernel has a great performance and is also very good battery friend. Last night, in 6 hours I only lost 4%.
Wotan unlocker first intend was to unlock my phone from network. It was branded. Before use Wotan unlocker I had: Bootloader unlocker allowed: NO. After I have yes and of course network unlocked. I used a software that I download and need to make a shunt between earth pin on phone and the second one….I believe is similar to S1tool.
I did the same, network sim unlock via test point. But, PCC has not worked since. It knows I've done something. SUS works sometimes. I have tried using flashtool, relock ftf and adb sony relock and none of this changed anything. Can I unpatch or correct the patch and unlock officially? I'd really like to do that.
Thanks for any info I don't know much about test point.
SharpnShiny said:
I did the same, network sim unlock via test point. But, PCC has not worked since. It knows I've done something. SUS works sometimes. I have tried using flashtool, relock ftf and adb sony relock and none of this changed anything. Can I unpatch or correct the patch and unlock officially? I'd really like to do that.
Thanks for any info I don't know much about test point.
Click to expand...
Click to collapse
You shouldn't have any problem with PCC or SEUS if you unlocked BL using s1tool.
And what do you mean by "network sim unlock via test point"?
I used a paid software (4SE) to remove the network lock on my phone, so I could use other networks. It confirmed if I wanted to unlock my bootloader as well. I didn't know much about it but knew that doing that would allow custom kernels etc. so I clicked yes.
The network lock is gone, perfect. But only through chatting with others I've learned that the bootloader is 'patched' not fully unlocked. No method that I've tried properly modifies the patch, yet. I checked the log files in C/programfiles and found the log file says it did use an S1 tool. The paid part is of course network unlocking not the bootloader part.
PCC has never worked since. The exact message it says is something like 'unable to start software components or software'. I've read extensively on that and the only hint I've found is that it may be related to a modified bootloader. I've Windows 7 and now 8 beta on my computer also and on that version it gives the same message now. I've uninstalled, updated java etc. everything I'm sure it's the phone not the computer.I'm sure it detects something.
SUS works some days. It's so strange whether I use stock SE 2.3 or a mod version it changes whether to say:
1. There is no new software for your phone
2. No new software, would you like to reinstall anyway?
I've no clue what that's about.
1) so when you clicked yes in 4SE, you needed to use testpoint right? though it's strange that 4SE used s1tool for that..
2) "unable to start software components or software" is down to PCC, not your phone.
3) SEUS is also strange, I tried few days ago, it also didn't let me repair software, telling me that I have latest. I could swear that, one time before, it asked me if it should repair it anyway.
And now to your main question(if I understood you right ), yes, you can "unpatch it", use restore option in s1tool, that is if 4SE really used s1tool to patch your bl, which is still strange to me, but maybe that's how they made it I expected they will use their own BL unlock.
Thank you very much for helping me understand! Other people will likely find this information in the future!
4SE I believe is done by the Da Vinci Team which is much more known.
1. Yes I used test point!
2. Good to know it's PCC and not my phone. Very good...
3. I have tried 'restore' and it says 'nothing to restore'. But I'm sure that I can work on that.
Here's the log if it reveals anything I don't yet understand:
4SE - client 1.7.6
Checking connection...
Connecting server using license447...
License name: 1 Day License
Time left: 23 hours
Selected model: Xperia™ mini (ST15)
Selected operation: Unlock
Selected interface: USB (BOOTROM)
Checking USB driver status...
Remove battery. Link the TestPoint to GND and then plug USB cable
Connected to USB2
You can now release the keys and allow the process to run. Do not disconnect the phone
Device identification...
Connecting DLOAD...
Sending Preloader...
Connected to USB2
Sending LoaderTEST...
Chip:MSM7x30 Model:ST15i IMEI:358*********** AID:0001 Color:BROWN
DEVICE_ID: 0CE2*******************
EROM:
Uploading logic MSM7x30:
Detecting flash type...
ID: 98B3 (Toshiba)
Chip: Undefined 8192 Mbit NAND
Logical address: 0x00000000
Size: 1056 Mb
Logical block size: 0x40000
Logical blocks count: 0x1000
OTP: LOCKED
Reading TA security data...
Opening TA...
Reading SIMLock data...
Processing SIMLock signature...
Opening TA...
Writing SIMLock data...
Writing S1boot image...
Shutting down device...
Operation completed successfully. You can disconnect the phone now
FINISHED [52sec]
Yup, you are correct about who made 4SE, "old" guys in SE world
Hm, interestingly.. it says that your color is BROWN, and that even before unlocking procedure. Usually in Xperia's brown means that unit is prototype at least if it says that without any modifications. But in older SE phones brown meant also another thing, so maybe they are calling it like that even if it's not proto.
Out of curiosity, can you download omnius from here: http://www.omnius-server.com/ and try identify your phone(after pressing identify, in connection method use first option, so that you don't need to mess with test point, I'm not quite sure what info you would get with tp identify ), and post log here(of course mask your IMEI), or you can just say if it says brown or red.
Also, you can download s1tool from here: http://www.4shared.com/archive/xjhXIDXh/s1tool.html
and also try to identify with it.
But to go back on your first post in this thread, what is your main question? I kinda lost it in all this talk
You are not sure if your BL is unlocked or?
mine is?
how about mine? after flashing 4.0.4 global rom I flash lockbootloader xperia2011 to make sure its locked again and when I enter service info menu theres no status shown about my bootlock. I mean really its nothing. Before when i was in GB .42fw rooted, it has a status of bootloader: YES. now its gone
johnraziel said:
how about mine? after flashing 4.0.4 global rom I flash lockbootloader xperia2011 to make sure its locked again and when I enter service info menu theres no status shown about my bootlock. I mean really its nothing. Before when i was in GB .42fw rooted, it has a status of bootloader: YES. now its gone
Click to expand...
Click to collapse
how did you unlocked it in the first place? official method from sony dev page?
Madfysh said:
how did you unlocked it in the first place? official method from sony dev page?
Click to expand...
Click to collapse
oh sorry madfysh I confuse myself. I didnt do any unlocking procedure in the past. All I do is root GB .42 fw and then flashed 4.0.4 when it was released the I flashed lockbootloader to make sure I havent unlocked my bootloader. The problem is, I cant update or repair via PCC or SUS after flashing the global rom. Is my bootloader unlocked? since its gone from the SI menu?
Madfysh said:
Yup, you are correct about who made 4SE, "old" guys in SE world
Hm, interestingly.. it says that your color is BROWN, and that even before unlocking procedure. Usually in Xperia's brown means that unit is prototype at least if it says that without any modifications. But in older SE phones brown meant also another thing, so maybe they are calling it like that even if it's not proto.
Out of curiosity, can you download omnius from here: http://www.omnius-server.com/ and try identify your phone(after pressing identify, in connection method use first option, so that you don't need to mess with test point, I'm not quite sure what info you would get with tp identify ), and post log here(of course mask your IMEI), or you can just say if it says brown or red.
Also, you can download s1tool from here: http://www.4shared.com/archive/xjhXIDXh/s1tool.html
and also try to identify with it.
But to go back on your first post in this thread, what is your main question? I kinda lost it in all this talk
You are not sure if your BL is unlocked or?
Click to expand...
Click to collapse
The main thing I'm looking to do is unpatch or just properly unlock my phone.
Here's the log from Omnius:
Code:
Action journal
16:42:56 . The action started waiting for the user
16:43:26 . The action finished waiting for the user
16:43:26 Connecting via SEMC USB Flash Device (USB2)...
16:43:26 Device driver version: 2.2.0.5
16:43:26 Detected chipset: MSM7X30
16:43:26 Boot mode: EROM
16:43:26 EROM version: 1241-3656 R9A021
16:43:26 IMEI: 35**********
16:43:26 Device ID: 0CE2********************
16:43:26 Minimum loader AID: 0001
16:43:26 Color: Red SEMC
16:43:26 Phone rooting by manufacturer is enabled.
16:43:26 i Unsigned flashing is disabled.
16:43:26 Sending loader...
16:43:26 Waiting for loader response...
16:43:28 Phone model (from TA): ST15i
16:43:29 Current CXC (from TA): 1244-2098_4.0.2.A.0.62
16:43:29 Current CDA (from TA): 1249-6223_R3D
16:43:29 Current FS (from TA): WORLD-i_4.0.2.A.0.62
16:43:29 i The phone is not locked to a network.
16:43:29 i Simlock origin: Unknown simlock origin, 734D7C4A9D088D9464B644C627E96237193B3437
16:43:29 s Successfully done.
16:43:29 . The action entered shutdown phase
16:43:29 . The action reported success
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
I see it says RED here...
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
Hi everybody! I'm new at this forum, i come from xperia x8 forum, and I have problems with custom kernels. I have a xperia Neo V, and I just cant connect the phone in fastboot mode. I'm not sure if it is properly bootloader-unlocked, as in the oficial sony's webpage it said that cdma devices cannot be unlocked (check http://unlockbootloader.sonymobile.com/), and I think that is the standard in Europe isn't it? (I'm from spain). Also, I checked the service menu and it also indicates that the bootloader cannot be unlocked.
Anyway i tried through the testpin-s1 tool method and everything seemed to work fine, i got the output with the two lowercase "r", but not the messages showing the model, software version, custom version, filesystem version and serial number, as said in vimjam's guide (check the post regarding unlock BL here: http://forum.xda-developers.com/showthread.php?t=1409269).
When I try to connect it in fastboot mode it just shows the sony ericsson logo and starts to charge, not showing any blue led. I know that this happens in locked devices, but the two lowecase "r" in s1 tool indicate that it is unlocked, so i dont understand... Can someone tell me if my phone is properly unlocked, or if custom kernels can be flashed connecting the device in flash mode (as it does work for me)? Thanks in advance
Eventhough your bootloader is now unlocked, your fastboot is still locked, you have sim-locked phone and you need to pay to unlock it.
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
danygarss said:
ok, so you mean I have to sim-unlock my phone in adition to bl-unlock to connect it in fastboot mode? can this be done in wotanserver or i have to take it to some tech service?
Click to expand...
Click to collapse
Yes, you can use wotanserver.
Madfysh said:
Yes, you can use wotanserver.
Click to expand...
Click to collapse
Hi,I managed to unlock my bootloader using msm7227_semc.cmd method.However when I tried to enter fastboot I couldnt
as my sim was locked.I paid for unlock via S1 tool and now have an unloked phone.However when I identify the phone to check
the status of the bootloader I only get one r "Look For Line RUNNING S1_EROM VER "r8A029" but the loader version has a
R .Is my bootloader still unlocked? I have tried getting into fastboot mode but nothing seems to happen.Can you please guide me?
Thanks for reading .Your reply is much appreciated.
i have a x10 mini pro (NOT X8) which is 10w45(under the battery) can i unlock my bootloader safety ....and if it can unlock .what should i do for the next step ..i want to know it ..thanks.....sorry for my english
645827884 said:
i have a x10 mini pro (NOT X8) which is 10w45(under the battery) can i unlock my bootloader safety ....and if it can unlock .what should i do for the next step ..i want to know it ..thanks.....sorry for my english
Click to expand...
Click to collapse
Yes, the warning is for phones on or after 11w29.
Find S1Tool and press the identify button, it will give information about your phone. If it has SEMC Simlock certificate it is safe to unlock your bootloader, which you can do with Flashtool.
If it has 'unknown simlock certificate' it may disable your networking capabilities, so in that case it would still be unsafe.
bootloader
I used another tool (attachment)
just plug in the phone with debugging turned on and then open "msm7227_semc" from the zip and follow the instructions. When finished, just reboot your phone and you have a unlocked bootloader
Do you want to know what the point of an unlocked bootloader is? Or have I misunderstood your question?
Use the SE tweaker tool for unlockin bootloader. The link is there in my signature.
Sent from my X10MiniPro using xda premium