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.
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
Hi guys!!
I tried to follow this guide, but I can't continue, I stuck in step 5 of Unlocking the Bootloader.
I have install android-sdk and added the line in udev correctly.
Note that I'm using Ubuntu!
My Phone:
Code:
Model ------------> SK17i
Android version --> 2.3.4 (official ROM, obviously)
Build version ----> 4.0.2.A.0.62
Bootloader -------> Locked :(
PD: This device is Vodafone!
Hi, i can be wrong but i think there is no drivers for linux.
When you hold your volume button up and connect your phone, S1 BOOT device should appear, and you must have driver for it.
Only then it will detect your phone and successfully communicate with it.
Qarl said:
Build version ----> 4.0.2.A.0.62
Click to expand...
Click to collapse
Been told that the .62 version can not be rooted with flashtool. Had same problem as you yesterday.
felixnutella said:
Been told that the .62 version can not be rooted with flashtool. Had same problem as you yesterday.
Click to expand...
Click to collapse
He want's to unlock the bootloader first, not rooting!
Go to Phone, enter this *#*#7378423#*#*
Then choose Service Info-Configuration
Bootloader unlock allowed, is it Yes or No?
Also, is your phone locked to a network?
Someguyfromhell said:
Go to Phone, enter this *#*#7378423#*#*
Then choose Service Info-Configuration
Bootloader unlock allowed, is it Yes or No?
Also, is your phone locked to a network?
Click to expand...
Click to collapse
The bootloader (of my device) is locked, Unlock allowed = NO.
I think that my phone is locked by network, Vodafone is very stupid!!
Thank you!! Regards!!
Exactly, since it says Unlock Allowed: No, then you cannot unlock it with official method.
If you can use other operator SIM in that phone, then phone doesn't have network lock, if you can't use other SIM, then phone has network lock.
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 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.
Here is my question.
Are there any members, in this awesome community, that have SE Tool 2 and that can properly unlock my bootloader?
Here is a little more, if you need to know.
Initially
-X10A stock 2.1 and SIM locked to Rogers
-Unlocked bootloader using a guide by the_laser (Worked as intended! Showed SEMC Certificate)
-Rooted, installed Clockwork recovery and flashed to CM7, then tried CM9 later on. (Worked well, no issues).
-Decided to get SIM unlocked. (At local phone repair shop).
-Flashed back to stock 2.1. (The repair guy said only 2.1 was supported in order to SIM unlock).
-He SIM unlocked with 4SE. (Tried another non-Rogers SIM, worked as intended).
-I got home and checked with S1 tool, Not recognized SIM lock certificate! Use SE Tool 2.
-I tried to use Flashtool to unlock the bootloader however it complains about a certificate and aborts.
Now I`m stuck as I cannot reload any other ROM`s!
I`d like to know if anyone can assist me restore my SEMC certificate using SE Tool 2. I`ll gladly pay for the service!
Thanks guys and have a super day!
Edit: Running S1 tool shows:
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_2.1.A.0.435
CUSTOM VERSION: 1232-9897_R8B
FILESYSTEM VERSION: WORLD-1-4-8_2.1.A.0.435
SERIAL NO: CB511K106G
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:5 secs.
SS-XIII said:
Here is my question.
Are there any members, in this awesome community, that have SE Tool 2 and that can properly unlock my bootloader.
Here is a little more, if you need to know.
Initially
-X10A stock 2.1 and SIM locked to Rogers
-Unlocked bootloader using a guide by the_laser (Worked as intended! Showed SEMC Certificate)
-Rooted, installed Clockwork recovery and flashed to CM7, then tried CM9 later on. (Worked well, no issues).
-Decided to get SIM unlocked. (At local phone repair shop).
-Flashed back to stock 2.1. (The repair guy said only 2.1 was supported in order to SIM unlock).
-He SIM unlocked with 4SE. (Tried another non-Rogers SIM, worked as intended).
-I got home and checked with S1 tool, Not recognized SIM lock certificate! Use SE Tool 2.
Now I`m stuck as I cannot reload any other ROM`s!
I`d like to know if anyone can assist me restore my SEMC certificate using SE Tool 2. I`ll gladly pay for the service!
Thanks guys and have a super day!
Click to expand...
Click to collapse
Do not use those tools if used wrong it could mess uo your network. use this guide:http://forum.xda-developers.com/showthread.php?t=1821750 and ONLY flashtools from now on.
mine shows Not recognized SIM lock certificate and the bootloader is unlocked... you got a "r" or a "R" on RUNNING S1_EROM FROM VER "#8A02$" ????
SS-XIII said:
Here is my question.
Are there any members, in this awesome community, that have SE Tool 2 and that can properly unlock my bootloader.
Here is a little more, if you need to know.
Initially
-X10A stock 2.1 and SIM locked to Rogers
-Unlocked bootloader using a guide by the_laser (Worked as intended! Showed SEMC Certificate)
-Rooted, installed Clockwork recovery and flashed to CM7, then tried CM9 later on. (Worked well, no issues).
-Decided to get SIM unlocked. (At local phone repair shop).
-Flashed back to stock 2.1. (The repair guy said only 2.1 was supported in order to SIM unlock).
-He SIM unlocked with 4SE. (Tried another non-Rogers SIM, worked as intended).
-I got home and checked with S1 tool, Not recognized SIM lock certificate! Use SE Tool 2.
Now I`m stuck as I cannot reload any other ROM`s!
I`d like to know if anyone can assist me restore my SEMC certificate using SE Tool 2. I`ll gladly pay for the service!
Thanks guys and have a super day!
Click to expand...
Click to collapse
brenty108 said:
Do not use those tools if used wrong it could mess uo your network. use this guide:http://forum.xda-developers.com/showthread.php?t=1821750 and ONLY flashtools from now on.
Click to expand...
Click to collapse
-I read your tutorial and I agree with your method on using Flashtool for unlocking the bootloader. I didn't use that option a few years ago when I first started becoming an Android user. Either way, I'm stuck with the big "R" as seen in S1 tool. Thanks for the reply.
sergio_f said:
mine shows Not recognized SIM lock certificate and the bootloader is unlocked... you got a "r" or a "R" on RUNNING S1_EROM FROM VER "#8A02$" ????
Click to expand...
Click to collapse
-I just added the output from S1 tool to my original post. Yes, I now have the big "R". I had the little "r" before I took the phone in for SIM unlocking. I wonder if his computer made a back-up of the original certificate. If so, perhaps it can be put back into the phone some how. Thanks for the reply.
sorry my question, only now i saw your log showing the big R
SS-XIII said:
-I just added the output from S1 tool to my original post. Yes, I now have the big "R". I had the little "r" before I took the phone in for SIM unlocking. I wonder if his computer made a back-up of the original certificate. If so, perhaps it can be put back into the phone some how. Thanks for the reply.
Click to expand...
Click to collapse
ok
only now i saw your log showing the big R
i bought mine in second hand, i think it was unlocked the bootloader before purchase , then i made a sim unlock and i had no problems with it
000000k said:
only now i saw your log showing the big R
Click to expand...
Click to collapse