Do you wanna know if you can unlock your bootloader? Then this is the thread for you.
Use this tool here: Bootloader Certificate Check
Here's how you will know if you can use the boot loader unlock tool. Follow all instructions on screen of the tool when you run it.
If you get at the end, "SEMC SIMLOCK CERTIFICATE"
Then yes can, you can use the SEMC_qd8250 unlock batch file to unlock tool yours.
If you unlocked with SETOOL, then yes, you can too, I'm not sure what message that gives as yet, but I will proceed to find out.
But if you get, "SIMLOCK CERTIFICATE NOT RECOGNIZED"
then NO, you CANNOT, I repeat, you CANNOT unlock your bootloader, not as yet at least, when you can I will update this thread. IF you attempt unlocking it with this message, then you WILL lose your radio signal, and will only be able to restore this if you unlock via SETOOL, which I am unsure how to go about doing doing, since nothing has been said about this.
Can the mods help by stickying this thread please so all persons with this question can see? Thank you.
I'll try it, thanks!
thanks for this info i get this now i can unlock my bootloader SEMC SIMLOCK CERTIFICATE
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:
Hello everyone,i have a big problem.
The first time i've tried to unlock the bootloader (following the guide of this section) i've check with s1Tool,and everithing whas ok.Then i started the flashtool end click to plugin and i've run the bl unlock.The ploblem is that after that action flashtool looks like stuck (because nothing happened) and i close flashtool and unplug the device.The device now works ok,but the option on the flashtool for unlock the bootloader just disappear,i can't unlock the bl anymore .I've checked if the bl was unlocked with s1Tool and it says it is locked.
What can i do now to unlock the bl?
l_anfeta92 said:
Hello everyone,i have a big problem.
The first time i've tried to unlock the bootloader (following the guide of this section) i've check with s1Tool,and everithing whas ok.Then i started the flashtool end click to plugin and i've run the bl unlock.The ploblem is that after that action flashtool looks like stuck (because nothing happened) and i close flashtool and unplug the device.The device now works ok,but the option on the flashtool for unlock the bootloader just disappear,i can't unlock the bl anymore .I've checked if the bl was unlocked with s1Tool and it says it is locked.
What can i do now to unlock the bl?
Click to expand...
Click to collapse
I think something might have messed up with kernel or rom.
If you want to unlock I suggest you to go to stock 2.1 or 2.3.3 and the bl unlock plugin should appear again.
Thanks man
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